https://github.com/apache/maven-resources is still at subversion, the github is a readonly mirror.
That's what triggered the discussion: how to move it to git? 1 repository or 4? I came with the suggestion to actually move them. And these repositories are not touched that often, e.g. the text of LICENSE, NOTICE and DEPENDENCIES won't change in general. Only the asf-parent pom might require some maintenance, but should basically be updating plugins. I expect close to no extra work, however they are required with every ASF release that follows the release-policy[1], hence they need a dedicated repository. And I noticed Karl Heinz is PMC, he is familiar enough with maintaining these kind of repositories. If Creadur would not be the right project, which other one would be? thanks, Robert On 28-6-2020 19:14:32, P. Ottlinger <[email protected]> wrote: Hi, thanks for reaching out .... Am 28.06.20 um 13:43 schrieb Robert Scholte: > the Apache Maven team has been maintaining several repositories related to > ASF (meta)files used by Maven projects. > Think of: > - https://github.com/apache/maven-apache-parent (parent pom for ASF projects ) Personally I'd prefer to have this file in the hand of infra/DEVOPS guys as it seems to be connected to ASF's CI infrastructure apart from being the root for most Maven-based projects at ASF. As Creadur's community is rather small I'm unsure if it would fit to have this sensitive project within its reach. But I understand your feeling to move this repo to a different location. Maybe it would make sense to have it in Creadur's hands as many projects run RAT (if they use Maven at all). > - https://github.com/apache/maven-resources ( files/templates required by > every ASF distributable. Think of NOTICE, LICENSE, DEPENDENCIES, DISCLAIMER, > the license header ) I don't really get the sense of that repo with the last commit in 2018 and Github's warning that it is marked deprecated - why should it move to Creadur? Thanks, Phil
