On Tue, Jun 13, 2006 at 06:14:47PM +0200, Jiba wrote: > > Is your "democracy" banning people from the pysoy IRC channel because > they might disagree with you
Anyone joining #PySoy or the PySoy mailing lists who does not have the intention to help with the project or use the project is lurking or trolling and will be removed in order to maintain a sane environment. If you want a free-for-all place to rant about PySoy, join ##PySoy or some other channel of your choosing. If you want to stay up on the latest news, http://planet.pysoy.org/ and the respective ticket/wiki items at http://www.pysoy.org/ has all the info you could ever want. > or lying on the pysoy website (is it true that pysoy is *already* used > for artistic, scientific, and educational software ? Yes. I have a large volume of code which previously used Soya and has been converted for API changes. Prehaps you forget that I: * had a student group working with Soya games over the past two years * maintain the only GNU project which depended on Soya * have worked as a guest-teacher in classroom environments using Soya * have written over 60 pages of instructional material for it Much of this Soya only has because I wrote it. Whatever copies you have from the old znoid.com website you're of course free to use, provided you comply with the GNU FDL license (provide attribution/etc). I'll be republishing them on http://www.pysoy.org/ as I have time to adapt them for PySoy's API changes and relabel them. GNU Aetherspace v0.4 will be released at the same time as PySoy 1.0. > It is for Soya, but since you've deliberately been breaking > compatibility in the past few days...). We're under no obligation to provide backwards compatability to Soya, any more than any other 3d engine project does. We never advertised that we would provide backwards compatability to Soya, either, nor implied such to you. All major API changes to PySoy have gone through the process of discussion and debate, several days for everyone to get a chance to weigh-in on their preferences and compare options. Anyone looking at the ticket system or the "API" tag page knows this, it's all public. The major direction we seem to be going in is pruning all the outdated and redundant class functions and attributes. Soya can't easily do this since it'd break older games, but we're under no such restriction. In fact a cleaner API is one of the advantages we get from forking. > That is not democracy for me. Democracy is not having a single person at the lead unilaterally making decidions for the project as a whole. We have multiple people admin access to the website, multiple people the ability to post news, having large decidions like root namespace changes and release schedules be decided by the group instead of an individual. All releases are roughly timed on the roadmap, are open to discussion regarding wether it should be changed, and we have a reasonable timeframe to postpone or provide last-minute patches before any release. Soya does not have this. You are an individual with friends who help with packaging and sections of code you're disinterested in, not a coalition of developers. Soya has always been your personal project. But we've had this conversation. We've gone around and around this issue over the past year, you even agreed to make Soya a community group and relax unilateral control over it, yet have not. I'm done fighting with you on this issue. You don't like this way of working, we don't like your way of working, so now we have two seperate projects. I wish you best of luck with Soya, whatever direction you take it. _______________________________________________ Soya-user mailing list [email protected] https://mail.gna.org/listinfo/soya-user
