The only issue I've had with the suggestions of offering Gerald assistance is the suggestion of an implementation, Source Forge, rather than of the idea, which is distributed development. I agree that Source Forge would probably be the easiest to set up quickly; however, I've gotten the feeling that Gerald has issues with Source Forge. It wouldn't require the use of that product; distributed development was around long before sourceforge.
Unless Gerald is mostly concerned with maintaining control, I'm certain there's some way Gerald could make use of his more involved happy customers to even out the development process. Two or three people who know parts of the code in detail, with one being allowed to put out a provisional patch set, would be of great benefit, even if it is a far cry from what a full CVS solution such as Source Forge would provide. (I'm thinking of something similar to the way the Linux Kernel development was set up before the bit wizard thingy; I haven't paid attention to its organization since then.) Ed On Wed, 17 Sep 2003, Neal Gamradt wrote: > I think that Gerald has created a wonderful product, I haven't > switched to EmbPerl 2.0 because it is still in beta version. I don't > see anything wrong with the suggestion of a Source Forge project, > however, Gerald may have reasons as to why he would not want to do > this. Since he is still the creator and maintainer of this project > the future of EmbPerl is really up to him. > > Using EmbPerl makes sense for me since I write Perl modules that can > then be used on the web or in local applications, and I can implement > these modules quickly in both cases. Bottom line, It allows me to > make more universal code. However, lately it appears that PHP is > growing very quickly while I don't see huge levels of support for > EmbPerl. I shudder at the idea of using PHP (from early experience it > appears to be a dumbed down version of Perl) and will only do so when > when EmbPerl is no longer being developed or supported. > > I do think that Gerald has a large enough community at his disposal to > maintain and update the great product he has developed. If the Source > Forge project proves to be the best long term solution for keeping > EmbPerl current I am sure that is what will end up happening. > > I don't want to see EmbPerl go away and be forced to use an > alternative, that would be a very sad day. > > Neal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
