Proposal: Mailing List Cull

Adam Farley8 adam.farley at uk.ibm.com
Fri Mar 15 11:08:34 UTC 2019


Hi Alex,


"discuss" <discuss-bounces at openjdk.java.net> wrote on 14/03/2019 20:30:50:

> From: Alex Buckley <alex.buckley at oracle.com>
> To: discuss at openjdk.java.net
> Date: 14/03/2019 20:31
> Subject: Re: Proposal: Mailing List Cull
> Sent by: "discuss" <discuss-bounces at openjdk.java.net>
> 
> On 3/14/2019 4:09 AM, Adam Farley8 wrote:
> > Alex: What I'm imagining is a smaller number of active lists.
> >
> > You're right to assert that active projects should have a mailing 
list,
> > and it is not my intention to imply otherwise.
> >
> > Perhaps less active (read: near-silent), or completed, projects could
> > share a common list, or use one of the more active lists?
> 
> I think that is for each Project to decide, and that the typical 
> decision will be to refer people to the mailing list of the Group which 
> sponsored the Project.
> 

That's a fair comment. Ideally, all of the contacted list owners will 
respond
once an email has been sent out, and they will decide on the right action.

> For example, when the Build Infrastructure Project voted to dissolve 
> [1], someone updated the mailing list page [2] to refer to the Build 
> Group's list, `build-dev`. It was a similar story when the ThreeTen 
> Project voted to dissolve [3][4]. Looking to the future, I imagine the 
> Annotations Pipeline 2.0 Project would decide to stand down 
> `anno-pipeline-dev` in favor of the sponsoring Compiler Group's list, 
> `compiler-dev`, but that the Penrose Project might want to refer people 
> to the Jigsaw Project's list instead of the Core Libraries Group's list.
> 
> Separately:
> 
> Where your JBS issue is recording decisions (e.g. archive sctp-dev), I 
> recommend you link to the thread which actually made the decision.
> 

Good idea. Will add a link next to it for transparency.

> Not sure why java-se-mr-spec-comments or java-se-spec-comments are on 
> your radar. The former clearly has purpose [5] and the latter is clearly 

> associated with the significant java-se-spec-* lists.
> 
> Alex

Those did seem important, but they looked associated with work that been 
resolved.

At a glance, the mr one mentions Spring 2019, and the JEP links mention 
that the last vote is about to finish.

Between that and the last email being in 2015, I presumed the list was due 
for archiving anyway.

Not the case?

- Adam

> 
> [1] 
> https://urldefense.proofpoint.com/v2/url?
> 
u=https-3A__mail.openjdk.java.net_pipermail_build-2Dinfra-2Ddev_2017-2DJuly_004577.html&d=DwICaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=P5m8KWUXJf-
> CeVJc0hDGD9AQ2LkcXDC0PMV9ntVw5Ho&m=rW9U9Vo8dLTAfQrAZPM_bofVOScDo-
> O3WH7QIQMpFzU&s=nDV6gx1hr4RPWYM2J13bsSmhpJiVAn1AugQOYi64TG0&e=
> [2] https://urldefense.proofpoint.com/v2/url?
> 
u=http-3A__mail.openjdk.java.net_mailman_listinfo_build-2Dinfra-2Ddev&d=DwICaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=P5m8KWUXJf-
> CeVJc0hDGD9AQ2LkcXDC0PMV9ntVw5Ho&m=rW9U9Vo8dLTAfQrAZPM_bofVOScDo-
> O3WH7QIQMpFzU&s=O6dw0h3YMboee513VhT-cVOtnk-8irV5sD5P5hpHs_w&e=
> 
> [3] 
> https://urldefense.proofpoint.com/v2/url?
> 
u=https-3A__mail.openjdk.java.net_pipermail_threeten-2Ddev_2017-2DAugust_001623.html&d=DwICaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=P5m8KWUXJf-
> CeVJc0hDGD9AQ2LkcXDC0PMV9ntVw5Ho&m=rW9U9Vo8dLTAfQrAZPM_bofVOScDo-
> O3WH7QIQMpFzU&s=VH6xWwRYxYwOYmXqqdcbPHEHOt40i9LCgjDKbltJuYs&e=
> [4] https://urldefense.proofpoint.com/v2/url?
> 
u=http-3A__mail.openjdk.java.net_mailman_listinfo_threeten-2Ddev&d=DwICaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=P5m8KWUXJf-
> CeVJc0hDGD9AQ2LkcXDC0PMV9ntVw5Ho&m=rW9U9Vo8dLTAfQrAZPM_bofVOScDo-
> O3WH7QIQMpFzU&s=8IY1T_CmIVLqZ5HfA_fOgQ9jBpc8p4XcyKm11QRP50A&e=
> 
> [5] https://urldefense.proofpoint.com/v2/url?
> 
u=http-3A__mail.openjdk.java.net_mailman_listinfo_java-2Dse-2Dmr-2Dspec-2Dcomments&d=DwICaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=P5m8KWUXJf-
> CeVJc0hDGD9AQ2LkcXDC0PMV9ntVw5Ho&m=rW9U9Vo8dLTAfQrAZPM_bofVOScDo-
> O3WH7QIQMpFzU&s=vBi1T53v6RpC7j_9__A-i1AdJIPaBvAGq41bnS-HyNQ&e=
> 
> > This would need to be mentioned on the project page, yes.
> >
> > And speaking of common lists, I keep having to copy the Appendices 
between
> > my emails to ensure changes aren't lost.
> >
> > This invites errors, so here's a JBS Task to store the shared list 
where
> > everyone can tweak it:
> >
> > https://urldefense.proofpoint.com/v2/url?
> 
u=https-3A__bugs.openjdk.java.net_browse_JDK-2D8220662&d=DwICaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=P5m8KWUXJf-
> CeVJc0hDGD9AQ2LkcXDC0PMV9ntVw5Ho&m=rW9U9Vo8dLTAfQrAZPM_bofVOScDo-
> O3WH7QIQMpFzU&s=jsbg8DjAFJW_LDMTdJOD0PG9B76TXUwFUdL7NE5epkk&e=
> >
> > Unsure if this is a misuse of the bug system. I expect someone will
> > complain if it is. :)
> >
> > Best Regards
> >
> > Adam Farley
> > IBM Runtimes
> 

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


More information about the discuss mailing list