OpenEuphoria

2. Re: Code Commitee

• Posted by D. Newhall <derek_newhall at yahoo.com> Oct 18, 2006
• 495 views

Vincent wrote:
> 
> Obviously we cant accept everyones unaudited code. Euphoria would begin
> gaining
> to much complexity, bugs, and potential security holes that way. A system
> needs
> to be designed to keep development at a managable pace.
> 
> Some contribution guidelines ought to be establish to protect Euphoria's
> original
> goal of simplicity, performance, and multi-platform nature.
> 
> How does this work in other FOSS languages like Python in Ruby?
> 
> Maybe RDS can establish something simular?

I don't think it will be that challenging.

Rob will control access to the source code. We submit code if he wants to add
it, he can, if he doesn't want to, we can fork.

That's a generalization of how the other projects do it. Everyone has the BDFL
who has the final say on the language (Larry Wall, Guido van Rossum, Yukihiro
Matsumoto, John Ousterhout, Mike Cowlishaw, etc.) plus some trusted core
developers. Everyone else can submit anything but the head guy can always veto
it.

I think coming up with coding and documentation standards and submission
guidelines are the most important part.