I see good arguments either way. Most important to me is clarity and a mandated way forward. This would work well!
If you /don’t/ rename it, ideally it’s PRs should be closed, a “look elsewhere” README added, and then set to “archived” in GitHub settings. As extra step could also rename it logging-log4j1-archived. Best don’t delete it outright: as the source of dozens of other forks that could confuse otherwise happy forkers. Cheers, Leo On Thu, 23 Dec 2021 at 22:35, Ralph Goers <[email protected]> wrote: > In https://issues.apache.org/jira/browse/INFRA-22654 Chris Lambertus has > recommended that we can divorce > the read-only SVN repo from https://github.com/apache/log4j. However, it > will not be able to keep the same > name as all Git repos owned by the logging project must start with > “logging-“. > > So this vote is to: > 1. Delete the apache/logging-log4j1 repo I created last night. > 2. Divorce the apache/log4j repo from SVN. > 3. Rename apache/log4j to apache/logging-log4j1. > 4. Create a branch named “main” from the v1_2_17 tag. > 5. Make main the default branch in GitHub. > > While all votes are welcome Infra needs consensus from the PMC on this > vote so the result will separate > binding from non-binding votes. > > Ralph > > PS - I’ve separated this from the previous vote thread since it was mostly > discussion. If you want to discuss > this please prefix the subject with [DISCUSS]
