UseBB Community

Please don't be mad at me, but I added a section to the wiki: the Roadmap. This is just my idea and you can shoot it down if you like. However, I like to see a clear path so that when/if I'd like to donate time, I could claim one feature to work on. As it stands, I'm not exactly sure what's coming for 0.6.

Is this documented elsewhere?

Let me know if this is not appropriate.

A roadmap is actually a good idea In my opinion, but of course you need to check with Pc_Freak first.

Sure a good idea but myself I don't really keep a list of what is put in release x and in release y. It's mostly done on the fly. Also listing every new feature is a lot of work (the Changelog also needs to be updated when CVS commits are done).

Or perhaps just have a long feature list of all the upcoming features and mark them off when they're done?

IceNine wrote

Or perhaps just have a long feature list of all the upcoming features and mark them off when they're done?

What, like what IPB is doing?
http://invisionboard.com/?ipb21roadmap
We aren't going to copy their style, I think the changelog is sufficient in this, and so are the threads on upcoming versions. We provide what features are planned in those threads and posts in the announcement forum.

I think we better start thinking of a public TODO list as soon as more than one developer is assigned.

Okay, then I suppose the question that is begging to be asked is, how will a developer (such as myself) take responsibility for a feature/fix? What if I create something that completely destroys another section of what you've created?

Well, to begin with we use CVS, which merges changes made by developers. We don't develop a release off-line but commit each change to the CVS server which will merge it. Before a developer starts working on something he/she should first fetch the latest sources from the CVS server.

I recreated your article under the development section and put some content in it.

http://usebb.sourceforge.net/docs/doku.php?id=development:roadmap