Developers, mailing lists, etc. in `pom.xml`

[Volkan Yazıcı <vo...@yazi.ci>]

Today we had a chat with Christian and we are inclined to remove (when
proceeding with the revamping of the site generation gig of mine) the
following information from pom.xml files:

   - issueManagement (Why would anybody check pom.xml for this? We have a
   website and README pointing to JIRA for issues.)
   - ciManagement (Again, why pom.xml? Not to mention the information here
   still points to Jenkins.)
   - developers & contributors (Rather than maintaining developers in every
   single pom.xml, we should stick to a single source: Apache Logging
   Services Project Team page <https://logging.apache.org/team-list.html>.)
   - mailingLists (Again, we have an Apache Logging Services Mailing lists
   page <https://logging.apache.org/mailing-lists.html>.)

Objections? Thoughts?

Re: Developers, mailing lists, etc. in `pom.xml`

[Ralph Goers <ra...@dslextreme.com>]

That stuff is all there because the site plugin requires it. Once we aren’t using that I am fine with pulling it.

Ralph

> On Mar 29, 2022, at 12:46 PM, Volkan Yazıcı <vo...@yazi.ci> wrote:
> 
> Today we had a chat with Christian and we are inclined to remove (when
> proceeding with the revamping of the site generation gig of mine) the
> following information from pom.xml files:
> 
>   - issueManagement (Why would anybody check pom.xml for this? We have a
>   website and README pointing to JIRA for issues.)
>   - ciManagement (Again, why pom.xml? Not to mention the information here
>   still points to Jenkins.)
>   - developers & contributors (Rather than maintaining developers in every
>   single pom.xml, we should stick to a single source: Apache Logging
>   Services Project Team page <https://logging.apache.org/team-list.html>.)
>   - mailingLists (Again, we have an Apache Logging Services Mailing lists
>   page <https://logging.apache.org/mailing-lists.html>.)
> 
> Objections? Thoughts?