On 03/07/07, Matthieu Fertré <[EMAIL PROTECTED]> wrote: > Hi Eddy,
Hello again, > > I am glad that was not ignored. I think we both thought you didn't > > want to talk about this issue. Glad is not the case. > > > > Well, I was very busy these last 2 weeks, and I preferred to have time > to think about it and to talk about this issue when I have a interesting > answer. Better late than never ;-) > > I am willing to tackle the translation stuff. I thought that was > > obvious. > > Well, I distrust obvious things. I have hopped that you can do that but Heh, you are a wise man :-) Now that I have spoken is carved in stone ;-) > was unsure. So please, send email to all translators and and > package/port maintainers to ask them to register to the mailing-list > created especially for them. Sorry, I missed that; I have subscribed and will post a message about it to all translators. Also I am acting as the Debian packager, so I should be listed anyway ;-) > >> I also sent email about the port of Windows and Mac OS X. > > > > I saw that. It is great you try to do it, but if those arches do not > > have an active porter, then maybe we should stop supporting them until > > the problem is solved. I don't think that anyone would mind. And if > > they do, well, they can step up and become the porter ;-) . > > I think these ports should continue. Of course, it's not the high > priority so if nobody is doing the effort on it, it will not be really > supported... But anyway, we should try to find who are the latest > maintainers of these ports to get feedback from them to make the port > easier. I agree. > > Indeed it looked like it; I really like the way you thought about the > > sounds, professionals and the money. That seems like a good idea, I > > wish I had that idea myself ;-) . > > > > Well, that's an idea, but today, we can not base our strategy on that > money. Of course; we should first use what we have. IIRC Adnan was really sad about the sound issue, so maybe he can pick up on that. > Eddy, could you give information about potential issues about > including public domain sounds into Wormux ? Public domain material is by definition free for any kind of use. Note that there are countries where there is no legal frame for such a thing (like Germany, where one can not give up his/her copyright); in such cases the term is legally interpreted as "you are allowed to do what ever you like". So, as conclusion, public domain material is safe for our project. > > If you step up as a leader, people working on features would surely > > agree to your authority and will refrain from working on the stable > > branch if you indicate a feature freeze. It is possible to work on a > > branch ;-) , anyone knows that. The features can be merged after the > > release, if they don't care about working on the release itself. > > Yes, but I don't think branch is the only solution. Some features are Of course, combine that with periodic releases and you'll be close to an ideal recipe for keeping people motivated. All sorts of solutions can be found, as you pointed out, but for now we should look no farther than necessary. > > If it becomes a custom to release every 6 months (or some other fixed > > cycle) people will never feel that their work is in vain, if they miss > > this release they will get into the next. > > I have thought about releasing every 6 months too (good for integration > in most linux distributions). Currently, I was planning to create a > branch at the very beginning of August. On this branch, only > translations, packaging stuffs (fix makefile, fix compilation pb on > different systems) and hiding features should be done. I hope that doing > that we can have all packages and translations updated for the very > beginning of September. There is a catch with this approach: you risk people ignoring the stable branch and work on trunk. I think that late branching from trunk keeps people motivated to work on the stable release and is manageble enough to be able to port fixes back and forth between trunk and the stable branch. Probably the ideal branch lifetime is somewhere between 2 and 4 weeks before the release, after a semi-freeze (non-intrusive changes) or maybe a regular freeze (just bug fixes, commits to disable new code, etc). This way you can have about a month to stabilize the release after 5 months of open development. Just a reminder, nothing is carved in stone, these are just ideas. > But, I can't promise it will be 0.8 since we have some difficult bugs to > solve (I think about bug 8529 on which I have spent 6 hours without any > ideas about the problem..). So perhaps, it will be only a 0.8beta2 If we have 0.8.beta2 and a 0.8beta3 is not a such a big deal than not having any release, IMHO. It takes longer, bad luck, people wanting features should help kicking 0.8 out the door ;-) . -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein _______________________________________________ Wormux-dev mailing list Wormux-dev@gna.org https://mail.gna.org/listinfo/wormux-dev
