So, as I hope you can tell, things have picked up the pace a little more here at Codaset HQ, and each week is seeing a new release with some damn cool new features, and of course bugs are being squashed as soon as is humanly possible. But how long will this last and when will the beta end?
Well, there are only two more features that I plan to release before the beta is lifted, which will be in time for Christmas. At which point, Codaset will no longer be in beta, and several paid plans (still to be decided) will be available.
So I just want to let you know a little about these two big features...
As you know, Codaset has a Push API, which can call any webhook, or post to twitter when any given Codaset event takes place. Well that's great for getting data, or read actions. But what about being able to programatically make changes to a project? I just love how Twitter has opened up absolutely everything via their API. I am pretty sure that whatever you can do on Twitter's site, can also be achieved with the API. And that is exactly what I want to allow with Codaset.
You should be able to create a new project or new ticket, or update a ticket. How about publishing a blog post, or updating your wiki? That is the plan, and I want to open as much as I can so you guys can play to your hearts content, and create some cool apps and services using the Codaset architecture.
I use Campfire - religiously! It's perfect for collaboration with your team mates. I can paste code, images, even Youtube videos, and they all show up inline in the chat. But Campfire is quite limited, and really could do with a few IRC style features. It's also yet another standalone app.
What I want is my own chat room for each of my Codaset projects, and I want to use it right within Codaset. I also want to be able to reference tickets, wiki pages, blog posts and commits in the chat, and for it to recognize those. Then anyone can come along and join me in my chat room, and we can talk about the project. I can then create a new private room as well. You get the idea.
This will be the next feature on my list, and one that I really love, and I hope will help differentiate Codaset from the competition.
So that is what is in store for the immediate future. Of course, you may see a few smaller features creeping in, but these are the biggest. I would love to know what you think, and what you would like to see.
It would be great if this chat service provides an open API, because I would also be interested to use the chat room within a native app.
Yes, the chat will have an API. :)
The chat feature would be priceless. Especially if it is a persistent chat service. Say if you log out, the conversations your team mates have in that room will still be logged and appear when you come back online. You can pass through them to see what kind of logic they use. I would also allow user-user chat (perhaps limited to team members only).
API development could really boost things and as Google Wave progresses you might look towards integration with it. It's going to be OSS (well in some limited degree I'm sure) and could provide a massive boost to popularity of Codaset as well as the usefulness if integrated properly with extensions, etc.