You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by Florent André <fl...@4sengines.com> on 2009/01/16 11:20:16 UTC
Re: How to easy share module, snippets, templates, etc?
On Fri, 16 Jan 2009 10:40:50 +0100, rudolf.korhummel@uniklinik-freiburg.de
wrote:
> I like the idea having a plattform where it is easy to share modules very
> much.
>
> Thorsten Scherler <th...@juntadeandalucia.es> 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: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: How to easy share module, snippets, templates, etc ?
Posted by Vik Tara <vi...@propco.co.uk>.
>
> I would like to do that... I'm not sure to have all the require
> competencies... but I can try :)
And I can help!
Vik
Florent André wrote:
> On Fri, 16 Jan 2009 14:49:28 +0100, Thorsten Scherler
> <th...@juntadeandalucia.es> wrote:
>
>> El vie, 16-01-2009 a las 11:20 +0100, Florent André escribió:
>> ...
>>
>>> 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).
>>>
>> If you feel that you have a module that is worth sharing then the best
>> way is to donate it to the lenya project and we add it to the
>> repository.
>>
>
> Yes, but this solution don't facilitate this usecase :
> Two (or plus) lenya users want to develop the same module : an svn is a
> good solution for co-develop this module. So, they have to have a
> "personnal" svn server to do that, with this "potential" risk :
> - creation of many svn server with many adress
> - few visibility of each site module (if one site groups all modules = one
> address = more visibility of each module)
> - increase the difficulty for reuse a still no-maintain module
>
>
>> This way we can make sure that the modules are
>> a) compatible with the ASF license
>> b) ensure community support around the module
>> c) ensure minimum quality of code
>>
>
> I agree, this bullets points are the strong of ASF.
>
> In my mind, the donation to the lenya project occur when the module is
> "mature".
> The "modules site" is like a lab : he is useful for the cooperative
> construction of the module, and when he is stable, this module is put into
> the lenya project.
>
>
>> ...
>>
>>> 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.
>>>
>> Open questions:
>> - who has write access to which part of the svn? Is like Apache Labs
>> where everybody has write access to any project? Or would each module be
>> restricted to the creator?
>>
>
> In my mind :
> We have an svn repository and in this repository we have one folder for
> each modules :
> - repository
> --- module 1
> ----- trunk
> ----- branches
> ----- tags
> ----- exp
> --- module 2
> ----- trunk
> ----- branches
> ----- tags
> ----- exp
>
> So my answers are :
>
>> - Is like Apache Labs where everybody has write access to any project?
>>
> No, the creator of a module can choose who have the write access on his
> module (like described above)
>
>
>> - who has write access to which part of the svn?
>>
> Creator and co-developer of module1 have write access to module1
>
>
>> - Or would each module be restricted to the creator?
>>
> This is "open-restrict" on each module...
>
>
>> - who guarantees that all license issues are met?
>>
> We can imagine an advertise when the user create a new module... the
> creator can be the man who guarantee that.
>
>
>> - who manage this project? Project management
>> and infrastructure?
>>
>
> I would like to do that... I'm not sure to have all the require
> competencies... but I can try :)
>
>
>> who makes sure that people do not abuse the site.
>>
> The good spirits of people and the black-list...
>
>
>> - where does communication happen?
>>
>
> Excuse me, but I don't understand this question.
>
> ++
>
>
>>> As says rudolf.korhummel, "If this is possible with the apache
>>>
>> environment
>>
>>> it would be fine", and great.
>>>
>> If you want the endorsement of the ASF then we need to create something
>> here.
>>
>> salu2
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: How to easy share module, snippets, templates, etc?
Posted by Florent André <fl...@4sengines.com>.
On Fri, 16 Jan 2009 14:49:28 +0100, Thorsten Scherler
<th...@juntadeandalucia.es> wrote:
> El vie, 16-01-2009 a las 11:20 +0100, Florent André escribió:
> ...
>>
>> 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).
>
> If you feel that you have a module that is worth sharing then the best
> way is to donate it to the lenya project and we add it to the
> repository.
Yes, but this solution don't facilitate this usecase :
Two (or plus) lenya users want to develop the same module : an svn is a
good solution for co-develop this module. So, they have to have a
"personnal" svn server to do that, with this "potential" risk :
- creation of many svn server with many adress
- few visibility of each site module (if one site groups all modules = one
address = more visibility of each module)
- increase the difficulty for reuse a still no-maintain module
>
> This way we can make sure that the modules are
> a) compatible with the ASF license
> b) ensure community support around the module
> c) ensure minimum quality of code
I agree, this bullets points are the strong of ASF.
In my mind, the donation to the lenya project occur when the module is
"mature".
The "modules site" is like a lab : he is useful for the cooperative
construction of the module, and when he is stable, this module is put into
the lenya project.
>
> ...
>> 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.
>
> Open questions:
> - who has write access to which part of the svn? Is like Apache Labs
> where everybody has write access to any project? Or would each module be
> restricted to the creator?
In my mind :
We have an svn repository and in this repository we have one folder for
each modules :
- repository
--- module 1
----- trunk
----- branches
----- tags
----- exp
--- module 2
----- trunk
----- branches
----- tags
----- exp
So my answers are :
> - Is like Apache Labs where everybody has write access to any project?
No, the creator of a module can choose who have the write access on his
module (like described above)
> - who has write access to which part of the svn?
Creator and co-developer of module1 have write access to module1
> - Or would each module be restricted to the creator?
This is "open-restrict" on each module...
> - who guarantees that all license issues are met?
We can imagine an advertise when the user create a new module... the
creator can be the man who guarantee that.
>
> - who manage this project? Project management
> and infrastructure?
I would like to do that... I'm not sure to have all the require
competencies... but I can try :)
> who makes sure that people do not abuse the site.
The good spirits of people and the black-list...
>
> - where does communication happen?
Excuse me, but I don't understand this question.
++
>
>> As says rudolf.korhummel, "If this is possible with the apache
> environment
>> it would be fine", and great.
>
> If you want the endorsement of the ASF then we need to create something
> here.
>
> salu2
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: How to easy share module, snippets, templates, etc ?
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
El vie, 16-01-2009 a las 11:20 +0100, Florent André escribió:
...
>
> 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).
If you feel that you have a module that is worth sharing then the best
way is to donate it to the lenya project and we add it to the
repository.
This way we can make sure that the modules are
a) compatible with the ASF license
b) ensure community support around the module
c) ensure minimum quality of code
...
> 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.
Open questions:
- who has write access to which part of the svn? Is like Apache Labs
where everybody has write access to any project? Or would each module be
restricted to the creator?
- who guarantees that all license issues are met?
- who manage this project? Project management and infrastructure? who
makes sure that people do not abuse the site.
- where does communication happen?
> As says rudolf.korhummel, "If this is possible with the apache environment
> it would be fine", and great.
If you want the endorsement of the ASF then we need to create something
here.
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: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: How to easy share module, snippets, templates, etc ?
Posted by Vik Tara <vi...@propco.co.uk>.
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, rudolf.korhummel@uniklinik-freiburg.de
> wrote:
>> I like the idea having a plattform where it is easy to share modules very
>> much.
>>
>> Thorsten Scherler <th...@juntadeandalucia.es> 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: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org