Follow the development
posted by Martin Cohen in Development 
December 4th, 2009
Complaints about small information value of our tweets are duly justified. Of course, the problem is that we tell you what has been done, though you still don’t know if we are at 10% or 30% or 99%, if we actually moved back, or what the hell is going on…
You solved the issue by following our progress via our project updates at Google Code. I found that amazing, and a few seconds later, well, logical. However, until now, the updates were only regarding the bugs found during the testing.
From now on, we will be also posting there also our tasks, so you will know:
Before you ask, the tasks will be populated in next few days and their count will stabilize as we are not adding any new features to the release. Some of the tasks may also be divided into more detailed ones.
After having this, our postings to Twitter will have their information value and we all can calm down as much as possible in anticipating the new Intype. We hope that this will be the perfect balance between you being informed, and us progressing steadily with the development.
Comments are locked
We are sorry, but comments for this post are locked. This post is outdated.
1. Deadelus
04.12.2009 at 3:13 pm
Hurray! Thanks!
So when “What is left to be done?” is empty we get a release?
2. Robin Drost
04.12.2009 at 3:29 pm
Finally a blog update, keep it coming!
3. Oscart
04.12.2009 at 3:56 pm
:o It seems that you have work like 3 more years only for the 0.3.5 :(
4. Martin Cohen
04.12.2009 at 4:10 pm
Deadelus: Yes, if we will finish all issues in the list, we’re ready to release.
5. Martin Cohen
04.12.2009 at 4:11 pm
Oscart: If you would have seen our whole list to get into the current stage, you would think it’s for 50 years.
6. Jason Lee
04.12.2009 at 8:13 pm
It’s tooooooooooooo slow your team are.
How can wen beleave you can’t fix the bugs when it happen in the new version.
Look E-Textedit and the other projects,release the new version fast
7. guest
04.12.2009 at 10:38 pm
Hey people why are you saing that. “Too slow…” & “Too slow…” Now we can track progress and seend bug reports and see how many bugs left…for new rel. We have now nice and clean wiki how to write bundles , snippets and themes or maybe in the future plugins.
Intype is near :D
So its better to do some useful job like digg happy news
8. guest
04.12.2009 at 10:41 pm
it was 30 now its 26 issues left !
9. Rawrcasm
05.12.2009 at 4:08 am
I’m so excited..
… and I just can’t hide it.
10. Julio Protzek
05.12.2009 at 5:54 am
Great to have some communication. Even better to know that we will have more communication =D
11. Chriha
05.12.2009 at 6:17 am
@Martin: It’s not just the fact, that YOUR community don’t know what you’re doing. Again, this post is nothing new. You’re talking about something (a platform, which is exclusivley for open source projects) that we’ve already known and that a user of the community (not the intype team) five weeks before this blog post (!) written about. What is so amazing on that!? That’s awful to give such less information and response! It shows the interest and endurance of the community! Remember this!
And the fact, that you still hide your ignorance and the unbelievable delay (e.g. by showing just the last 3 blog posts, ignoring all the comments in every post, no explanations at all, etc.) doesn’t make it better …
@8: You must be kidding. You’re someone of the intype team, right? A wiki … for what? Vaporware?
12. Not a coward
05.12.2009 at 3:32 pm
Regarding @Chrinha’s angry post:
Remember, a Jedi’s strength flows from the Force. But beware. Anger, fear, aggression. The dark side are they. Once you start down the dark path, forever will it dominate your destiny.
13. Pipo Lambert
05.12.2009 at 6:41 pm
Thank you guys! Hopefully we’ll be able to buy Intype on Christmas day :) That would be an amazing present!
14. Deadelus
06.12.2009 at 12:26 pm
@Chriha please.. relax, stop crying stop shouting terms like vaporware just let them do their thing. Not fast enough? go cry somewhere else.
15. Anonymous coward
07.12.2009 at 8:32 am
We’ve already seen such a list before back in 2008. What good is putting up another one of these lists?
http://intype.info/release-todo/
TODO: http://code.google.com/p/intype/issues/detail?id=56&can=1&q=type%3ATask
Twitter: http://twitter.com/intype/status/5361731646
TODO: http://code.google.com/p/intype/issues/detail?id=79&can=1&q=type%3ATask
Twitter: http://twitter.com/intype/status/2867173812
TODO: http://code.google.com/p/intype/issues/detail?id=74&can=1&q=type%3ATask
Twitter: http://twitter.com/intype/status/1911012190
16. Anonymous coward
07.12.2009 at 8:33 am
Also, since there’s no frame of reference to this particular TODO list. What difference does it make over your Twitter posts? You can just add and delete tasks all the time.
17. Code monkey
07.12.2009 at 11:35 am
@16 & 17:
Because contrary to former lists, the devs actively use this one. It’s as simple as that.
18. Anonymous coward
07.12.2009 at 4:47 pm
Why don’t you release some alphas and betas like everyone else ?
19. Brendon Kozlowski
07.12.2009 at 8:14 pm
@19: The next release will be a beta. Consider the previous betas early alpha versions that the team decided to end an open-alpha test on.
@16/17 - Regardless of whether the devs “actively” use this one or not, they have locked features. They will not be adding any features to the list, only finishing off what’s there.
@Chriha - I thought you already said you were never coming back? Regardless, I do somewhat agree with your points. I don’t think it’s a good idea to have a website as a landing spot for other software tool’s pages.
@Martin: A software’s website is supposed to be the central hub of communication between the vendor (you and your team) and its potential customers, or interested parties (us). Although I’m glad we *CAN* find other avenues of information, I personally don’t think that we should have to be doing that. I know I’d much rather get information directly from the team on what’s been done, what’s still left to do, and the interesting things learned along the way (or even questions posed back to us, as many of us are developers). I’d personally only want to subscribe to one RSS feed per topic, I don’t want to have to subscribe to an RSS feed, a twitter account, and find some sort of way to subscribe to a web page (Yahoo tool or IE Web Slice). Although it simply measures one’s true desire to follow a product, perhaps it’s also speaking to the lack of motivation from the vendor to communicate *directly* to the community it is catering for.
I will continue to follow the dev notes from the Google Code project page, but in complete honesty, I’m not really satisfied with the lack of determination to communicate openly to us on a regular basis. I understand it would take time away from development, but I’d rather 2-3 hours taken from development once or twice a month so that we could feel a part of what was going on internally. I would even gladly offer to write such information for you and your team.
20. Anonymous coward
08.12.2009 at 3:45 am
@Code Monkey - Lets just hope this isn’t a flash in the pan, and have it end up the way of the dwindling of the twitter updates.
21. Anonymous coward
08.12.2009 at 5:36 pm
Yawn… Please wake me when you have a new release to show.
22. Anonymous coward
09.12.2009 at 2:43 pm
When ends intype? certain correct date
23. Not a coward
09.12.2009 at 5:33 pm
@23:
Two days ago.
24. Anonymous coward
09.12.2009 at 6:22 pm
Its useless ,you constantly adding new issues and list oscillate between 30 and 35.
as we didnt know nothing , we dont now nothing now…
25. Anonymous coward
09.12.2009 at 8:04 pm
People complaining about slow dev “or is there any, or this is dead” but you just like me coming back here, checking.. you know guys “yes intype” if you just release something we can play around every once in a while then those twitter updates are sensible and so good to be true..
26. Anonymous coward
09.12.2009 at 8:34 pm
No Christmas gift this year :/
27. Well Known Hero
10.12.2009 at 2:43 pm
Just checked back here for the first time in quite a while. I see things are really no further forward ie still no release
28. Captain coward
14.12.2009 at 3:52 pm
If I’m looking at the buglist and reviewing the speed of progress, I don’t see any release in the next few month.
29. cjb
14.12.2009 at 4:30 pm
Each day new bugs are reported and almost none fixed… This is really sad, no progress in last years, just some random news from time to time, to keep people interested :/
30. Anonymous coward
16.12.2009 at 7:27 am
Oh man! ill be waiting on this. Goodluck to intype team! Happy holiday.
31. NOT Anonymous coward
16.12.2009 at 7:03 pm
cjb right, in this speed, one is fixed, 3 new bugs are on way.
1 bug = aproximatly take one week ://
30 bugs = 7,5 months
~ = 7-8 months to new release and it will be still beta…
Btw. Default sign ‘Anonymous coward’ is little offending dont you thins so ?
Only I think so ?