Hi all, Florent André <florent.andre-...@4sengines.com> schrieb am 19.01.2009 12:30:17:
> Hello, > > On Sat, 17 Jan 2009 11:19:27 +0100, Andreas Hartmann <andr...@apache.org> > wrote: > > Hi everybody, > > > > rudolf.korhum...@uniklinik-freiburg.de schrieb: > >> Thorsten Scherler <thorsten.scherler....@juntadeandalucia.es> schrieb am > >> 16.01.2009 13:53:06: > >> > >>> El vie, 16-01-2009 a las 10:40 +0100, > >>> rudolf.korhum...@uniklinik-freiburg.de escribió: > > > > […] > > > >>> The real problem is that we have promising candidates for new > > committers > >>> but we are failing to give the last helping hand. > > > > I agree that we should rather improve the community building efforts of > > the Lenya project than encourage an external community. > > > > The goal of the ASF is to create software in a collaborative way. It > > provides us with the necessary infrastructure. The problem is IMO that > > many contributors have the feeling that (a) becoming a committer is way > > out of their reach and (b) contributing (see [1]) is too complicated. We > > have to work on these issues. > > Open contributions on modules can be a good first step no ? I think its a very good first step. A new svn branch (something like "contributions") like Thorsten proposend filled by patches, would match to the philosophy of the Apache foundation and would be a first step in the right direction. > > > > > > >>>> Just have a look at the drupal Community. They have a little core > >>>> development team and a big community developing modules > >>>> http://www.ohloh.net/p?q=drupal They are very sucessful. > > > ... > > > > BTW, a very important point is the ratio between community size and size > > of the code base. Should we accept modules as soon as there is > > committment to maintain them? In this case, we also have to be ready to > > remove them when the maintenance stops, which raises the question of > > backwards compatibility. > > I think this process is the Darwin selection apply to module : > - if a module is not very useful, and the maintenance stop, nobody will > recode it > - if a module is useful, and the maintenance stop, for sure a person will > recode it if the sources lead is easy to give > - if a module is very useful, the core team will include this in the > distribution pack and the maintain is certain for a long time. > > A clear advertisement on each type of module (not maintain, maintain by > contributors, maintain by core team) can be imagine to inform users on the > status of each module. > > This "natural selection" occur in numbers of open modularized applications > (Drupal, Firefox,...) and give to this project an important variety and > capabilities that, I think, can help lenya to : "[…] a desire to create > high quality software that leads the way in its field". I also think like Andre that a good module concept is a very import thing, to bring creative individuals together to build up a great system. I realized also that in the past good things failed, because people were not able to see the benefits. I remember Simala 67 (http://en.wikipedia.org/wiki/Simula) the first object oriented program language. Only a few people in the 60's realized that object oriented programming is great thing. I have similar problem when I tell people about cocoon and lenya. Now there is a great module concept in lenya 2.0 and setting up the environment for people to use it, is from my point of view very import. We need modules and publications showing then benefits. I also think that it's import to do it in the Apache way to have good quality of contibutions. > > > So, > > - Can we imagine to have a "module contributor zone" on the lenya ASF > hosting ? > -- A vote have to be done ? > > - If this "module contributor zone" is set up, witch kind of process do you > imagine to become a contributor ? > Is it possible to set up a lenya modules subprojekt ? WDYT Rudolf > > Have a good sunny day ! > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org > For additional commands, e-mail: user-h...@lenya.apache.org > >
