Re: Open Source, then...?

new topic     » goto parent     » topic index » view thread      » older message » newer message

akusaya wrote:
> Nice to see the Eu went open source, .. at least in the following 2-3
> days after the open source release.
> 
> Now what happens to Eu? Looks like no different from before.
> 
> Maybe some people now already started to make their own version of Eu,
> and in a year maybe 4 different Euphoria derivatives come (e.g.
> Elation, Bliss, Joy, Exhilaration..).. and very possibly none of them
> has a significant market.

I'm sure that will happen, but some of the ideas, code,
and expertise may flow back into the mainstream version.

> I think what is absolutely needed now is a repository of code (where
> people can contribute codes, like other open source projects like
> Firefox). Documentations should be there also, so that users don't
> need to say "There is this mistake in this doc page!" in this mailing
> list anymore.

Yes, that must happen eventually. Maybe soon.

> Currently if one encounters a bug, he/she will report to Rob via this
> mailing list and then Rob will fix it in the next release (which is
> indeed faster but still 2-3 weeks which is too slow!).

I don't think many users want to re-install Euphoria every
2 or 3 weeks. Only developers and testers need quick turn-around.
 
> Having the repository will fix the bug in 1 or 2 days (provided more
> and more people come to understand the C codes).
> 
> Actually everyone can make Eu source code repository but it would be
> better and more courteous if Rob make it himself.
> 
> Any opinions?

Already I expect to incorporate into the official source:

  - the work of Konstantinos Tampouris in
    adding two more C compilers to those supported by the Translator.

  - the Mac OS X  code from Alban Read

  - the install program changes from Juergen Luethje

We will then need people to test these changes.
Mainly I'll be worried if someone's changes break
existing functionality, not whether the new functionality
actually works. I don't have time to fully test other peoples' code.
So we'll need an "under development" version that developers
can work on. I'm not sure whether to set up the code repository
before or after making these initial changes. I'm open to suggestion.

Some procedures for changing the code will emerge.
There's a political process as well as a mechanical
process leading to a change in the source. At the moment,
I'm still a kind of dictator, at least over the "official"
version, but I expect to give up more control as other people
learn more about the internals, and show that they can make
complicated changes without wrecking things. I may become
more of an overall Q/A type of person, rather than a major
initiator of new development. We'll see.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu