Re: submitting code
- Posted by mattlewis (admin) Oct 01, 2009
- 1846 views
Just as you are allowed to make improvements in Euphoria every day, i am not allowed to make improvements, every day. So it's not far from my mind that the off-topic harrassment which was against me on euphorum stopped only when i took removed all code for task messaging.
This is only because you refuse to participate. I'm not aware of anyone ever pressuring you to remove any code, and certainly any correlation between anything I wrote and anything you posted or removed from your site was pure coincidence.
I realise whatever is submitted is subject to editing, changing, improvements, renaming, etc etc. Code i give to Ry, or he gives to me, or code Unkmar suggests, or vice versa, is understood to be subject to the best use of the application by the recipient. But we don't fight over stuff like is often done here or on the devlist. Some people know of a need for a standard in a topic that does not yet exist in Euphoria, but who wants to bring up that topic in this hostile atmosphere?
I'm having trouble figuring out what the solution to this might be. Should we not discuss things or review code? Should we just put anything and everything into the code base?
What Derek had said as a blanket statement was over-simplified and could have had many caveats added. I added comments where he made the statement. While i respect Derek, i do not respect the process as applied here or some of the participants. More than one person has stated we traded the dictatorship of RobC for an equally frustrating dictatorship. There is just no end of irrelavant "reasons" for some code/functions being refused. Granted, there are some relavant reasons.
I gave pro and con for submitting code in the parent thread, but if Bruce would rather just get on with his job, do not submit code here. Share it with anyone who asks for it, but don't do it in euphorum, the devlist, or the ticket page on this site or sourceforge. There's just too much overhead.
I agree. If Bruce (or anyone else) cannot stand to have his code reviewed by others, he should not submit it for consideration to be added to euphoria. Working on a team / group project is much more challenging than working as an individual.
The development process of euphoria currently woks by consensus. Discussions occur here and on the dev list. It's not uncommon for there to be disagreements (yes, even when you're not involved!). These often get hashed out in sometimes heated discussions. I'm sure the people who've been working as developers would be happy to hear any other ideas about governance of the project, but I think the current process is serving us fairly well right now.
Matt
