I think altogether what is being proposed by Florent is very healthy for the Lenya community.
If this can be done within the existing ASF infrastructure that would be a huge benefit. There are probably many of use who have modules that could be contributed in such a way ;) Regards Vik Florent André wrote: > > On Fri, 16 Jan 2009 10:40:50 +0100, [email protected] > wrote: >> I like the idea having a plattform where it is easy to share modules very >> much. >> >> Thorsten Scherler <[email protected]> schrieb am >> 16.01.2009 09:13:53: >> >>> El jue, 15-01-2009 a las 19:06 +0100, Florent André escribió: >>>> Hi all > ... >>> Why do you think so? The ASF infrastructure is designed to allow exactly >>> this. >>> >>> "Portion of code" should first go into the issue tracker and then >>> committed to the svn. Snippet should go to the wiki. Actually one of my >>> first contributions here on the ASF had been >>> http://wiki.apache.org/cocoon/GETsnippets >>> >>>> Such a site could be good for the community development. >>>> (I don't have enough english words to well express my idea, I hope you >>>> understand :). >>> The lenya community is not as big as we could afford to split this >>> community apart. This may not be your intention but experience shows >>> that exactly this will happen. >> Here I'm not shure. Let me explain it form my point of view. >> I have written some useful litte modules and would like to share them > with >> other people, but I'm not able to understand the whole lenya system in >> deep. So if I would be lenya committer there is a risk for me to damage >> core code. >> > > Yes, this is also my idea. In the ASF submission process, a person have to > be "accept" to can write on the svn, he have to "proof" that he is a good > and implicated people in the project. I don't want to mean that is a bad > concept : it permit a very good quality to ASF project. > > But, it don't allow some "occasional" devel to share their modules (like > rudolf korhummel I think). > >>> The lenya community should be developed here in the mailing list and the >>> infrastructure that the ASF provides for this project. This is a >>> reliable environment for the development process. >> If it would be possible to get a "lenya module committer" with limited >> write access to the repository, the enty barrier for lenya development >> would be lower and there is no risk to damage core code by committers new >> at their job. >> 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. >> I think the new modules concept of lenya 2.0 ist excellent, and it's a >> great chance to get a big community. > > Yes, this is exactly my idea, thanks ! > > Be sure, I don't want to split the community, but I think that it was a > great think to have a less entry barrier for submitting than ASF. I think > that it can create more community participation and module creation. > > To precise my site idea and to respond to Vik, I imagine a more > "development cooperative" tools than wiki (in fact : svn). > > I think to something like that : > - a user create an Account on the "lenya mod sharing" site. So user > automatically have an svn account > - After login on the site, a form allow the user to create a new "project". > Here he can decide the write access in his project (all, restrict to name 1 > / name 2 /, restrict to group1 / group2, ...). > - After form submission, an svn folder is created, codev can begin. > > - For "visitors", the site presents all available modules or templates than > can be downloable. > > As says rudolf.korhummel, "If this is possible with the apache environment > it would be fine", and great. > > Have a good day > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
