I think just leave <developer> alone. If anyone feels like they need to be recognized, they can include a <contributor> in their PR.
Robert Dale On Wed, Jan 24, 2018 at 5:01 PM, Stephen Mallette <[email protected]> wrote: > I've read that before. Considering the rule of thumb > > > A good rule of thumb is, if the person should not be contacted about the > project, they need not be listed here. > > how do you interpret that rule (plus the rest of what's written there) with > respect to people who have specific expertise in just one module? they > wouldn't be contacted necessarily about the project as a whole, but they > would likely be a point of contact for that one module. Is that person a > contributor or developer? > > I suppose another question might be, whether anyone really cares about this > recognition in the pom.xml. Does anyone feel that the <contributor> section > is important to maintain? > > Anyway, i'd just like to consistently maintain these two sections of the > pom.xml so that this process isn't all haphazard, which might recognize > someone for a particular contribution, but then unintentionally ignore > someone else who did something similar. > > > > > On Wed, Jan 24, 2018 at 4:27 PM, Robert Dale <[email protected]> wrote: > > > https://maven.apache.org/pom.html#Developers > > > > > > Robert Dale > > > > On Wed, Jan 24, 2018 at 3:23 PM, Stephen Mallette <[email protected]> > > wrote: > > > > > Does anyone have any opinion on how the pom.xml tags <developer> and > > > <contributor> are used? > > > > > > https://github.com/apache/tinkerpop/blob/3.3.1/pom.xml#L58-L111 > > > > > > I don't think we have really kept these sections up to date or have any > > > kind of consistency in terms of who ends under which section. Should > we > > > just say that <developer> is for official apache committers who have > > > submitted changes to the repo and <contributor> is the catch-all for > > anyone > > > else we'd like to recognize (seems like an easy bucketing rule)? > > > > > > If no one has any strong opinion one way or the other, I'll just go > with > > > that (and get the sections fully consistent in terms of all > > > contributors/developers). > > > > > >
