[RFC] How many mailing lists does glibc need or use? Closing 4 lists.

[Carlos O'Donell]

Developers,

Goals:

  - Have one list you subscribe to for announcements.
  - Have one list you subscribe to for development work.
  - Have one list you subscribe to for test results (post-commit).
  - Have one list you subscribe to for developer help.
  - Have one list you subscribe to for VCS state changes.
  - Have one list you subscribe to for bug tracker traffic.

The project has the following mailing lists that are active:

    libc-announce
    libc-alpha
    libc-stable
    libc-help
    libc-locales
    libc-testresults
    glibc-cvs
    glibc-bugs
    glibc-bugs-regex (limited bugs just for regex)
    libc-maintainers@gnu.org

Could we reduce our lists to just:

    libc-announce - Announcements.
    libc-alpha - Development on any branch.
    libc-testresults - Large volume post-commit CI test results.
    libc-help - Developer help
    glibc-cvs - Commit list for monitoring.
    glibc-bugs - Bug tracking to email.
    libc-maintainers@gnu.org - Reaches current and past GNU Project maintainers.

Closing the following 4 lists since they don't meet the above goals:

    libc-stable - Should go to libc-alpha.
    libc-locales - Should go to libc-alpha.
    glibc-bugs-regex (limited bugs just for regex) - Should go to bugzilla or libc-help.

Notes:
- Merging libc-stable traffic to libc-alpha means you have one less
   list to review as a developer. This means just one list to look for
   reviews and one less list to handle for pre-commit CI which can review
   per-branch CI e.g. consistent rules for patch naming so CI can decide
   on the branch. There should be ONE email you can subscribe to for
   development work for master or stable branches or any branch for the
   matter.

- Merging libc-locales traffic to libc-alpha means we don't treat locales
   differently from other development work. Again one less list to review
   and patchwork pre-commit CI can apply automatically. There should be
   ONE email you can subscribe to for development work.

- The glibc-bugs-regex lists traffic should go to glibc-bugs; there should
   be ONE email you can subscribe to for bug tracking traffic.

-- 
Cheers,
Carlos.