RE: [VOTE] Remove developers from plugins project.xml
> > I don't have time until early June, but would be happy to help you if > you need by then. Same thing for me. We could think about this in June. > > > > Jerome Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Remove developers from plugins project.xml
On Thu, 2004-05-13 at 00:50, Arnaud Heritier wrote: > > > I think you're reaching an interesting point here. > > > > The developer information should be retrieved from an external > > repository, this being an LDAP or a simple global XML file shared by all > > projects. > > > > Otherwise you have a maintenance burdain on big projects. > > > > Furthermore, it introduces unnecessary dependencies. If I travel for a > > while, and my timezone is affected I don't see why I should modify the > > project files. Sounds counterproductive to me. > > > > Hello Jerome, > > It's exactly what I have in mind. > > I think that in a project file we only need to have an id to retrieve the > user and his roles. > I didn't found yet haw we can describe the unique id but I think it is > possible. > For example with an LDAP Directory : > > LDAP > cn=aheritier. > > ldapServerUrl > > > > I would have thought perhaps of something like this: in the project file, only contains either the developer ID either the developer info (to stay backward compatible). Somewhere else in the project file, have a way to define the developer sources. something like type LDAP name My LDAP Server host x mapping-id-property cn type XML name Company XXX developers uri Then the build process tries to find the developer in the sources, iteratively in the list order. Or maybe we need to use a sort of URI to define the ID? ldap:cn=aheritier xml:lacostej and the build process searches according to the matching source locations. etc... It's just a thought, it needs to be refined. It think we need to explore the URI way, it sounds flexible enough to just require a single line in the project file and has supposedly good support in Java. I don't have time until early June, but would be happy to help you if you need by then. > > Jerome > > > > PS: Arnaud I noticed that your reply-to field seems to default to your > > email instead of the list's one when you use your laposte.net account or > > apache.org account. Probably because you override it there. Doesn't do > > it with your axway account. I am not sure if it's a bug or a setting in > > ezmlm. Sound strange to me reply-to should default to the list, > > shouldn't it? > > At home, I overrided the reply-to laposte.net with apache.org to subscribe > to the mailing lists with my apache @. > It's weird because I thought that ezmlm automatically overrided it with the > ML @. strange. Maybe we should look at http://www.ezmlm.org/faq-0.40/FAQ-9.html#ss9.8 Do you want to follow up with that? I am not an Apache developer, and I guess you can find out more what's going on by yourself. J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Remove developers from plugins project.xml
> I think you're reaching an interesting point here. > > The developer information should be retrieved from an external > repository, this being an LDAP or a simple global XML file shared by all > projects. > > Otherwise you have a maintenance burdain on big projects. > > Furthermore, it introduces unnecessary dependencies. If I travel for a > while, and my timezone is affected I don't see why I should modify the > project files. Sounds counterproductive to me. > Hello Jerome, It's exactly what I have in mind. I think that in a project file we only need to have an id to retrieve the user and his roles. I didn't found yet haw we can describe the unique id but I think it is possible. For example with an LDAP Directory : LDAP cn=aheritier. ldapServerUrl > Jerome > > PS: Arnaud I noticed that your reply-to field seems to default to your > email instead of the list's one when you use your laposte.net account or > apache.org account. Probably because you override it there. Doesn't do > it with your axway account. I am not sure if it's a bug or a setting in > ezmlm. Sound strange to me reply-to should default to the list, > shouldn't it? At home, I overrided the reply-to laposte.net with apache.org to subscribe to the mailing lists with my apache @. It's weird because I thought that ezmlm automatically overrided it with the ML @. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Remove developers from plugins project.xml
Arnaud wrote: > Yes. But we use the same declaration for a developer (or contributor) in > several project.xml. > Actually a developer is defined by a name, an email, ... > Someone asked some month ago to have a messengerId. > We can think that it all this data could be retrieved from a single > repository or from an LDAP Directory? > Is it useful to duplicate this data in all project.xml files ?? I think you're reaching an interesting point here. The developer information should be retrieved from an external repository, this being an LDAP or a simple global XML file shared by all projects. Otherwise you have a maintenance burdain on big projects. Furthermore, it introduces unnecessary dependencies. If I travel for a while, and my timezone is affected I don't see why I should modify the project files. Sounds counterproductive to me. Jerome PS: Arnaud I noticed that your reply-to field seems to default to your email instead of the list's one when you use your laposte.net account or apache.org account. Probably because you override it there. Doesn't do it with your axway account. I am not sure if it's a bug or a setting in ezmlm. Sound strange to me reply-to should default to the list, shouldn't it? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Remove developers from plugins project.xml
> > I'm agree with you but the result is that all maven-plugins commiters > are > > developers for all plugins :-( > > Nope. They are potential plugin "developers" that's all. Yes, potentially. > > > > Yes. I think that we can have developers with a commiter role but also > > developers without it. > > That's why we have separated "developers" and "contributors". I don't > see what is the problem with this? Is your problem with the semantic of > the words? > In fact I think that it's difficult to define when a contributor becomes a developer (except if we simply define a developer as a commiter). > > > > My principal concern is that we duplicate users' information even > though > > we > > try with maven to centralize data through repositories :-( > > No. Developers are not the same for different plugins. Yes. But we use the same declaration for a developer (or contributor) in several project.xml. Actually a developer is defined by a name, an email, ... Someone asked some month ago to have a messengerId. We can think that it all this data could be retrieved from a single repository or from an LDAP Directory? Is it useful to duplicate this data in all project.xml files ?? > > > > > Shouldn't we work on a repository used to store contacts (or an API to > > retrieve this from LDAP) or on a mechanism to store users descriptions > as > > artifacts ?? > > I personally don't see the need. > > Thanks > -Vincent > > > > - > 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]
RE: [VOTE] Remove developers from plugins project.xml
> -Original Message- > From: Arnaud Heritier [mailto:[EMAIL PROTECTED] > Sent: 11 May 2004 22:39 > To: 'Maven Developers List' > Subject: RE: [VOTE] Remove developers from plugins project.xml > > > > > -Message d'origine- > > De : Vincent Massol [mailto:[EMAIL PROTECTED] > > Envoyé : mardi 11 mai 2004 18:02 > > À : 'Maven Developers List' > > Objet : RE: [VOTE] Remove developers from plugins project.xml > > > ... > > > > For me, developers are the persons who have commit rights on the > > project. Person who contribute patches are contributors. > > > I'm agree with you but the result is that all maven-plugins commiters are > developers for all plugins :-( Nope. They are potential plugin "developers" that's all. > > > > > > There are some cases where a contributor could be considered a > > developer. For example the AspectJ plugin has been almost completely > > rewritten by Carlos and Carlos is at the level of a developer. But he > > hasn't commit rights. However, what I'd like to do is propose to him to > > become an AspectJ plugin developer. The only problem is that commit > > rights are for maven-plugins in general and not for a given plugin. I'll > > start a discussion on this. > > > Yes. I think that we can have developers with a commiter role but also > developers without it. That's why we have separated "developers" and "contributors". I don't see what is the problem with this? Is your problem with the semantic of the words? > > My principal concern is that we duplicate users' information even though > we > try with maven to centralize data through repositories :-( No. Developers are not the same for different plugins. > > Shouldn't we work on a repository used to store contacts (or an API to > retrieve this from LDAP) or on a mechanism to store users descriptions as > artifacts ?? I personally don't see the need. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Remove developers from plugins project.xml
> -Message d'origine- > De : Vincent Massol [mailto:[EMAIL PROTECTED] > Envoyé : mardi 11 mai 2004 18:02 > À : 'Maven Developers List' > Objet : RE: [VOTE] Remove developers from plugins project.xml > ... > > For me, developers are the persons who have commit rights on the > project. Person who contribute patches are contributors. I'm agree with you but the result is that all maven-plugins commiters are developers for all plugins :-( > > There are some cases where a contributor could be considered a > developer. For example the AspectJ plugin has been almost completely > rewritten by Carlos and Carlos is at the level of a developer. But he > hasn't commit rights. However, what I'd like to do is propose to him to > become an AspectJ plugin developer. The only problem is that commit > rights are for maven-plugins in general and not for a given plugin. I'll > start a discussion on this. Yes. I think that we can have developers with a commiter role but also developers without it. My principal concern is that we duplicate users' information even though we try with maven to centralize data through repositories :-( Shouldn't we work on a repository used to store contacts (or an API to retrieve this from LDAP) or on a mechanism to store users descriptions as artifacts ?? Arnaud > > [snip] > > Thanks > -Vincent > > > - > 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]
Re: [VOTE] Remove developers from plugins project.xml
On Tue, 2004-05-11 at 11:26, Heritier Arnaud wrote: > Hi all, > > I would like to propose that we remove the developers declaration in the pom > for each plugin and that we use only the one in the plugin-parent. > > Why > > Because : > - It will simplify the maintenance. There are approximatively 80 plugins and > 20 or 30 comitters. > - In several plugins we find as developers : God made them, > it's magic ?? > - A lot of reports generated with the developer-activity plugin are incomplete > because it uses the developer list to find our description when we commit a patch or > a change. > - With the time, some comitters stop to support some plugins and the > developper list isn't updated. > > I think it will be simpler to update only one list which will represent in our > case the comitters. > > VOTE : [ ] I want to remove developers from plugins poms and to update the list in > the plugin-parent. > > > For me > [+1] I want to remove developers from plugins poms and to update the list in the > plugin-parent. -1 Don't glob them all together because it is then impossible to tell who did what and if the plugin moves you just have to move the names back into the POM in question. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Remove developers from plugins project.xml
> -Original Message- > From: Heritier Arnaud [mailto:[EMAIL PROTECTED] > Sent: 11 May 2004 17:45 > To: Maven Developers List > Subject: RE: [VOTE] Remove developers from plugins project.xml > > ok for this. > But in this case we must use roles to define this. > We could use entities like it is defined in the wiki ? > http://wiki.codehaus.org/maven/EnsureProjectConsistencyWithEntities#head - > 0334f6bb02fb7b3100b66778b92b875578e0a089 > Won't it be simpler ?? > > > If we keep developers as it is now, is there a rule to add someone as > developer. If a developer (i.e. someone with commit rights) makes a minor change (like add a license header file, change a date, etc), he should probably not add himself as a developer. However, if he makes a feature contribution or fixes some feature bug (vs just change for example the ordering in project.xml) then he could add himself (up to him). Anyway, that's my definition and what I try to follow as a rule. > > If someone apply a patch it is stupid to be considered him as a developer > ?? For me, developers are the persons who have commit rights on the project. Person who contribute patches are contributors. There are some cases where a contributor could be considered a developer. For example the AspectJ plugin has been almost completely rewritten by Carlos and Carlos is at the level of a developer. But he hasn't commit rights. However, what I'd like to do is propose to him to become an AspectJ plugin developer. The only problem is that commit rights are for maven-plugins in general and not for a given plugin. I'll start a discussion on this. [snip] Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Remove developers from plugins project.xml
ok for this. But in this case we must use roles to define this. We could use entities like it is defined in the wiki ? http://wiki.codehaus.org/maven/EnsureProjectConsistencyWithEntities#head-0334f6bb02fb7b3100b66778b92b875578e0a089 Won't it be simpler ?? If we keep developers as it is now, is there a rule to add someone as developer. If someone apply a patch it is stupid to be considered him as a developer ?? > -Message d'origine- > De : Maczka Michal [mailto:[EMAIL PROTECTED] > Envoyé : mardi 11 mai 2004 17:27 > À : 'Maven Developers List' > Objet : RE: [VOTE] Remove developers from plugins project.xml > > > -1 > > If section is missing in some plugins it should > be added there. > > > It should be clearly indicated who is a responsible for each > of the plugins > and who is "the man" which should be contacted > when any changes to plugin are going to be added. It's clear that each > plugin has different developers. > > Michal > > > -Original Message- > > From: Heritier Arnaud [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, May 11, 2004 5:27 PM > > To: Maven Dev (E-mail) > > Subject: [VOTE] Remove developers from plugins project.xml > > > > > > Hi all, > > > > I would like to propose that we remove the developers > > declaration in the pom for each plugin and that we use only > > the one in the plugin-parent. > > > > Why > > > > Because : > > - It will simplify the maintenance. There are > > approximatively 80 plugins and 20 or 30 comitters. > > - In several plugins we find as developers : > > God made them, it's magic ?? > > - A lot of reports generated with the > > developer-activity plugin are incomplete because it uses the > > developer list to find our description when we commit a patch > > or a change. > > - With the time, some comitters stop to support some > > plugins and the developper list isn't updated. > > > > I think it will be simpler to update only one list > > which will represent in our case the comitters. > > > > VOTE : [ ] I want to remove developers from plugins poms and > > to update the list in the plugin-parent. > > > > > > For me > > [+1] I want to remove developers from plugins poms and to > > update the list in the plugin-parent. > > > > > > Arnaud HERITIER > > Axway - Sopra Group > > Axway France Services > > Tél. : +33 (0)1 47 17 22 79 > > Email : [EMAIL PROTECTED] / [EMAIL PROTECTED] > > > > > > > > > > Ce message est exclusivement destiné aux personnes dont le > > nom figure ci-dessus. Il peut contenir des informations > > confidentielles dont la divulgation est à ce titre > > rigoureusement interdite. Dans l'hypothèse où vous avez reçu > > ce message par erreur, merci de le renvoyer à l'adresse > > e-mail ci-dessus et de détruire toute copie. > > This message may contain confidential and proprietary > > material for the sole use of the intended recipient. Any > > review or distribution by others is strictly prohibited. If > > you are not the intended recipient, please contact the sender > > and delete all copies. > > > > > - > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Remove developers from plugins project.xml
I'm -1 because more and more plugins will be considered as standalone projects with their own lifecycle. Thanks -Vincent > -Original Message- > From: Heritier Arnaud [mailto:[EMAIL PROTECTED] > Sent: 11 May 2004 17:27 > To: Maven Dev (E-mail) > Subject: [VOTE] Remove developers from plugins project.xml > > Hi all, > > I would like to propose that we remove the developers declaration in > the pom for each plugin and that we use only the one in the plugin-parent. > > Why > > Because : > - It will simplify the maintenance. There are approximatively 80 > plugins and 20 or 30 comitters. > - In several plugins we find as developers : God > made them, it's magic ?? > - A lot of reports generated with the developer-activity plugin are > incomplete because it uses the developer list to find our description when > we commit a patch or a change. > - With the time, some comitters stop to support some plugins and the > developper list isn't updated. > > I think it will be simpler to update only one list which will > represent in our case the comitters. > > VOTE : [ ] I want to remove developers from plugins poms and to update > the list in the plugin-parent. > > > For me > [+1] I want to remove developers from plugins poms and to update the list > in the plugin-parent. > > > Arnaud HERITIER > Axway - Sopra Group > Axway France Services > Tél. : +33 (0)1 47 17 22 79 > Email : [EMAIL PROTECTED] / [EMAIL PROTECTED] > > > > > Ce message est exclusivement destiné aux personnes dont le nom figure ci- > dessus. Il peut contenir des informations confidentielles dont la > divulgation est à ce titre rigoureusement interdite. Dans l'hypothèse où > vous avez reçu ce message par erreur, merci de le renvoyer à l'adresse e- > mail ci-dessus et de détruire toute copie. > This message may contain confidential and proprietary material for the > sole use of the intended recipient. Any review or distribution by others > is strictly prohibited. If you are not the intended recipient, please > contact the sender and delete all copies. > > > - > 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]
RE: [VOTE] Remove developers from plugins project.xml
-1 If section is missing in some plugins it should be added there. It should be clearly indicated who is a responsible for each of the plugins and who is "the man" which should be contacted when any changes to plugin are going to be added. It's clear that each plugin has different developers. Michal > -Original Message- > From: Heritier Arnaud [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 11, 2004 5:27 PM > To: Maven Dev (E-mail) > Subject: [VOTE] Remove developers from plugins project.xml > > > Hi all, > > I would like to propose that we remove the developers > declaration in the pom for each plugin and that we use only > the one in the plugin-parent. > > Why > > Because : > - It will simplify the maintenance. There are > approximatively 80 plugins and 20 or 30 comitters. > - In several plugins we find as developers : > God made them, it's magic ?? > - A lot of reports generated with the > developer-activity plugin are incomplete because it uses the > developer list to find our description when we commit a patch > or a change. > - With the time, some comitters stop to support some > plugins and the developper list isn't updated. > > I think it will be simpler to update only one list > which will represent in our case the comitters. > > VOTE : [ ] I want to remove developers from plugins poms and > to update the list in the plugin-parent. > > > For me > [+1] I want to remove developers from plugins poms and to > update the list in the plugin-parent. > > > Arnaud HERITIER > Axway - Sopra Group > Axway France Services > Tél. : +33 (0)1 47 17 22 79 > Email : [EMAIL PROTECTED] / [EMAIL PROTECTED] > > > > > Ce message est exclusivement destiné aux personnes dont le > nom figure ci-dessus. Il peut contenir des informations > confidentielles dont la divulgation est à ce titre > rigoureusement interdite. Dans l'hypothèse où vous avez reçu > ce message par erreur, merci de le renvoyer à l'adresse > e-mail ci-dessus et de détruire toute copie. > This message may contain confidential and proprietary > material for the sole use of the intended recipient. Any > review or distribution by others is strictly prohibited. If > you are not the intended recipient, please contact the sender > and delete all copies. > > - > 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]
[VOTE] Remove developers from plugins project.xml
Hi all, I would like to propose that we remove the developers declaration in the pom for each plugin and that we use only the one in the plugin-parent. Why Because : - It will simplify the maintenance. There are approximatively 80 plugins and 20 or 30 comitters. - In several plugins we find as developers : God made them, it's magic ?? - A lot of reports generated with the developer-activity plugin are incomplete because it uses the developer list to find our description when we commit a patch or a change. - With the time, some comitters stop to support some plugins and the developper list isn't updated. I think it will be simpler to update only one list which will represent in our case the comitters. VOTE : [ ] I want to remove developers from plugins poms and to update the list in the plugin-parent. For me [+1] I want to remove developers from plugins poms and to update the list in the plugin-parent. Arnaud HERITIER Axway - Sopra Group Axway France Services Tél. : +33 (0)1 47 17 22 79 Email : [EMAIL PROTECTED] / [EMAIL PROTECTED] Ce message est exclusivement destiné aux personnes dont le nom figure ci-dessus. Il peut contenir des informations confidentielles dont la divulgation est à ce titre rigoureusement interdite. Dans l'hypothèse où vous avez reçu ce message par erreur, merci de le renvoyer à l'adresse e-mail ci-dessus et de détruire toute copie. This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
