Proposal: Mailing List Cull

[Adam Farley8]

Hi John, Chris,

Chris: Thanks for telling us. I've created a bucket for "To Be Archived".

John: A reasonable concern. How does this sound for a per-list process?

Step 1) Contact the list owner to see if the list is still needed.
Step 2) If the owner replies in the negative, or the owner does not reply 
to subsequent emails after 1 month, move the list into the "to be 
archived" appendix.
Step 3) Post a message to the list, notifying any residual users that the 
list is to be archived.
Step 4) Update all references to the list from the openjdk website.
Step 5) Mark the list as Archived (via, I presume, the list owner or the 
gb in the event of an absent owner).
Step 6) Move the list into the "Archived" appendix.
Step 7) Cake & Coffee.

Best Regards

Adam Farley 
IBM Runtimes


"discuss" <discuss-bounces at openjdk.java.net> wrote on 13/03/2019 15:48:14:

> From: Jonathan Gibbons <jonathan.gibbons at oracle.com>
> To: discuss at openjdk.java.net
> Date: 13/03/2019 15:51
> Subject: Re: Proposal: Mailing List Cull
> Sent by: "discuss" <discuss-bounces at openjdk.java.net>
> 
> Mailing lists rarely exist in isolation: they are typically associated 
with
> projects and/or repos.
> 
> Without commenting on the merits of removing any individual mailing
> list, if a mailing list is to be removed, there should be due diligence 
to
> update any references to the mailing list, such as on the OpenJDK
> website.
> 
> -- Jon
> 
> On 3/13/19 5:27 AM, Adam Farley8 wrote:
> > (Preface: I may be sending this to the wrong list, so advice on the
> > correct list would be appreciated.)
> >
> > Hey All,
> >
> > There's a lot of mailing lists here, including a few that've been dead 
for
> > 5 years, and I think it's making it hard for contributors to find the
> > right list.
> >
> > Here's a list of mailing lists seeing no/minimal use, and a set of
> > proposals to go with them.
> >
> > Proposal 1: Cull (archive) one or more of these mailing list groups, 
with
> > exceptions made for lists anyone still wants, or actively monitors.
> > Why? Because having 151 non-archived mailing lists makes it harder for
> > people to find the right one. Also makes it easier to find black holes
> > (non-monitored lists) to drop valid bugs into.
> >
> > Proposal 2: Hide the archived mailing lists on the primary "mailing 
lists"
> > view.
> > Why? Because it dilutes the list of active lists and makes finding the
> > right one harder.
> >
> > Proposal 3: Create a short list of the most useful channels to the 
casual
> > contributor, making it easier to find the primary hotspot, JCL, docs
> > lists, etc.
> > Why? Ease of use. Ability to contribute should be based on knowledge 
of
> > the code base, not knowledge of the mailing lists,
> >
> > Proposal 4: Hide the mailing lists whose sole purpose is to display
> > automated messages when a project has been committed to.
> >
> > Proposal 4: Make Proposals 2, 3, and 4 the default view when you click 
on
> > "Mailing lists" from the main page.
> > Why? Ease of use again. One form this could take is: the user clicks 
on
> > "mailing lists" on the primary openjdk page, and sees a minimal list 
of
> > mailing lists, with toggles to show the lists hidden by 2, 3, and 4.
> >
> > Constructive opinions welcome. :)
> >
> > Best Regards
> >
> > Adam Farley
> > IBM Runtimes
> >
> > P.S. Spam and "hep please" don't count as emails.
> >
> > -- Appendix list:
> > 1: Lists with no emails in 2 years or more. (Dead)
> > 2: Lists with no emails inside the last 6 months. (Presumed Dead)
> > 3: Lists with less than 2 emails (average) per month for the past year 
(Rosebud)
> > 4: Lists whose associated project has been completed. (Project 
Completed)
> > 5: Lists to be archived due to owner response or lack of same. (To Be 
Archived)
> > 
> > -- Appendix 1: (Dead)
> > anno-pipeline-dev
> > btrace-dev
> > compiler-grammar-dev
> > cvmi-dev
> > friday-stats-dev
> > graphics-rasterizer-dev
> > guide-discuss
> > icedtea-changes
> > java-se-8-spec-comments
> > java-se-8-spec-experts
> > java-se-8-spec-observers
> > java-se-9-spec-comments
> > java-se-9-spec-experts
> > java-se-mr-spec-comments
> > javadoc-next-dev
> > jep-changes
> > kona-dev
> > lambda-libs-spec-comments
> > lambda-libs-spec-experts
> > lambda-libs-spec-observers
> > penrose-dev
> > penrose-discuss
> > tiered-attrib-dev
> > type-annotations-dev
> > type-annotations-spec-comments
> > type-annotations-spec-experts
> > type-annotations-spec-observers
> > xrender-dev
> > 
> > -- Appendix 2: (Presumed Dead)
> > detroit-dev
> > dio-dev
> > duke-dev
> > graal-changes
> > haiku-port-dev
> > harfbuzz-dev
> > icedtea-test
> > java-se-9-spec-observers
> > java-se-spec-comments
> > jdk-hs-changes
> > jmm-dev
> > nb-projects-dev
> > nio-discuss
> > sandbox-changes
> > sumatra-dev
> > 
> > -- Appendix 3: (Rosebud)
> > asmtools-dev
> > caciocavallo-dev
> > conformance-discuss
> > doccheck-dev
> > jmx-dev
> > jol-dev
> > macosx-port-dev
> > mips-port
> > platform-jep-discuss
> > 
> > -- Appendix 4: (Project Completed)
> > lambda-spec-comments
> > lambda-spec-experts
> > lambda-spec-observers
> >
> > -- Appendix 5: (To Be Archived)
> > sctp-dev

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU