Hey Romain, I'm 100% for trying this system, don't misunderstand me.
Bad things first: the thing that I don't want to use very much is the roadmap. Sometimes we have a definite goal, like releasing 0.3.4 in one month. Why ? We release because we did lots of good changes and additions. We have a strict timeline for the first time because of your next article. I don't say it will never happen anymore, but that we didn't see the deadline coming from very far, and we never planned to release after that such and such precisely given features/bugs were done. This is our style, and I don't think we should change it. With this style, we can only have a trivial or lying roadmap. This is our style: savonet is a great hobby, but none of us has it as its top priority. We have tons of idea in the TODO list, and sometimes one of us picks one. For example, short after 0.3.3: I had left the now-called harbor project for later, but balbinus did it, so it's in 0.3.4; at the same time, I was prioritizing more the language and the support of heterogeneous audio formats, and maybe video: I did the language, but in the end we release without the second feature, because I had less time than expected. Now for the good things: I'm 100% for forgetting the TODO (not structured, only seen by devs) and using the tickets instead; I find useful the SVN browser and the ability to visualize changes on the web; and I'll have users submit tickets instead of sf.net reports. Let's try this track, and thanks a lot for it. -- David PS: When I click on the logo it leads me to the unexisting <savonet.dolebrai.net>.
