netbeans-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emilian Bold <>
Subject Re: The various Apache NetBeans (incubating) mailing lists
Date Thu, 10 Nov 2016 21:14:24 GMT
I have just created
a table describing all the existing NetBeans mailing lists,  as well as a
next action recommendation based on the traffic I saw on the archives.

There are a lot of lists with no traffic that we could immediately make
read-only. A standard message should be created and sent to the list to
notify the list is closed and a pointer to the Apache list.

I also believe we can do an orderly migration of and These are contributor mailing lists so we can begin
announcing the migration and just check for the next months that we have no
discussion there. We should also set a deadline for these lists to become
read-only (say, 3 months from the 1st announcement?).

We should place announcements on the other mailing lists as well but set a
longer read-only dead-line perhaps?

I believe we need an announce@ mailing list for people that only use
nbannounce@ (how many are there?)

I don't know what will happen to nbweekly@ under Apache. @Geertjan: I
assume you managed it mostly alone? I think it's a valuable list, we should
preserve it under Apache.


On Sun, Oct 9, 2016 at 1:50 AM, Bruno Flávio <> wrote:

> On 06/10/16 13:39, Geertjan Wielenga wrote:
> > users: those using NetBeans IDE or building on top of the NetBeans
> > application framework, using tags, e.g., [PLATFORM] or [JAVASCRIPT] etc.
> Perhaps a good way to encourage the use of the tags would be to
> customize the subscription confirmation email with a link to the wiki
> and the general expectations about how the mailing list should be used.
> i.e.:
> Thank you for subscribing the mailing list.
> Many discussions happen on this list at once, as such we strongly
> recommend that you take a few minutes to read [WIKI LINK]. Following
> those guidelines increases the user experience and improves the odds of
> maintaining efficient and helpful conversations.
> Don't forget to add one or more tags to the subject line. For example,
> if you have a question about groovy support in Apache NetBeans, start
> the subject line with  [GROOVY].
> -Bruno

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message