El vie, 16-01-2009 a las 10:40 +0100, [email protected] escribió: ... > > > > 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.
Since you said they are modules, they should not harm the core, right? Further there is always a risk to damage something but that is what a good community is for. You can be sure that the error will be found and fixed very fast. We can create a new svn branch (something like "contributions") and people can submit patches against it. > > > > 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. Hmm, we already have a distinction between PMC member and committer (that I personally not favor, but it was decide in majority) out of a similar reason but IMO it did not helped to get faster people on board. The real problem is that we have promising candidates for new committers but we are failing to give the last helping hand. > 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. I agree that it would be wonderful to have more modules that are driven by "outsiders" however one big problem is that this modules need to be maintained. I can remember when I worked with different php cms that most modules are snapshots and not maintained anymore. Not trying to say that drupal is like this. > > > > > > > > So, I have a dedicated server and I "can" (not sure) and I like (sure) > > > create such a sharing space. I have an idea to the "structure" of this > > > site, but, before talk a lot, I would like to know : > > > > > > - How do you think about this idea ? > > > > I like your good intentions but there are several problems with the > > suggestion as mentioned above. > > > > > - Do you think you will use such a web site ? or not ? (this question > is > > > important, because I don't want to create a think that will not be > used). > > > > I will keep doing my bits and pieces HERE whenever I can but doubt that > > I find time for anything else. > > > > > - This is opposite to the Apache process ? > > > > Yes as pointed out above. > > > > So I am very interested having a plattform sharing modules an would use it. If we open a contributor module in svn would you provide patches to fill it? The one thing that we definitely cannot do is give the whole world commit access. This still one need to earn via contributions. salu2 -- Thorsten Scherler <thorsten.at.apache.org> Open Source Java <consulting, training and solutions> Sociedad Andaluza para el Desarrollo de la Sociedad de la Información, S.A.U. (SADESI) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
