You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Anatole Tresch (Jira)" <ji...@apache.org> on 2019/08/25 12:25:00 UTC
[jira] [Updated] (TAMAYA-231) Fix developers and contributors in
POMs
[ https://issues.apache.org/jira/browse/TAMAYA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anatole Tresch updated TAMAYA-231:
----------------------------------
Fix Version/s: (was: 0.4-incubating)
> 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
> Priority: Major
>
> 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
(v8.3.2#803003)