You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/05/01 16:07:05 UTC

[jira] [Commented] (TAMAYA-231) Fix developers and contributors in POMs

    [ https://issues.apache.org/jira/browse/TAMAYA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991004#comment-15991004 ] 

ASF subversion and git services commented on TAMAYA-231:
--------------------------------------------------------

Commit 4e1dbc08a5dfe484da8191b985f82672e0e460f5 in incubator-tamaya-extensions's branch refs/heads/master from [~o.b.fischer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=4e1dbc0 ]

[TAMAYA-231] There are only PPMC during podling.


> Fix developers and contributors in POMs
> ---------------------------------------
>
>                 Key: TAMAYA-231
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-231
>             Project: Tamaya
>          Issue Type: Sub-task
>          Components: Core, Extensions, Infrastructure, Sandbox
>            Reporter: Werner Keil
>            Assignee: Oliver B. Fischer
>             Fix For: 0.3-incubating
>
>
> At least all top level POMs of "incubator-tamaya", "incubator-tamaya-extensions" and "incubator-tamaya-sandbox" mention team members.
> "developers" should only reflect those who actively participate and commit, thus former PMC or Podling members should not be on that list.
> How do we want to handle that in the POMs?
> A possible approach could be the "contributors" part of the POM with a role like "Committer Emeritus" or similar.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)