> > 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]
