Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

We should start a new vote for issues@. We've already voted to merge dev@ and keep the user lists as is. On 28 March 2017 at 14:18, Paul Benedict wrote: > Yes, I think combining the "user@" and "dev@" variants into two are > appropriate. +1 (non-binding) for me. > >

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Yes, I think combining the "user@" and "dev@" variants into two are appropriate. +1 (non-binding) for me. Furthermore --- and this has always been a scratch of mine to itch (and I raise this about once a year!) -- I would like a dedicated "issues@" mailing list like other Apache projects. The

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

I followed up with infra over the weekend but haven't gotten a response yet. On 27 March 2017 at 20:21, Ralph Goers wrote: > Matt, > > Any update on this? > > Ralph > > On Mar 21, 2017, at 10:27 AM, Ralph Goers > wrote: > > Thanks Matt! >

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Matt, Any update on this? Ralph > On Mar 21, 2017, at 10:27 AM, Ralph Goers wrote: > > Thanks Matt! > > Ralph > >> On Mar 21, 2017, at 10:15 AM, Matt Sicker > > wrote: >> >> No other opinions apparently. I suppose

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Thanks Matt! Ralph > On Mar 21, 2017, at 10:15 AM, Matt Sicker wrote: > > No other opinions apparently. I suppose we'll go with the single list with > bounce messages. I'll follow up with infra later today. > > On 18 March 2017 at 13:12, Ralph Goers

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

No other opinions apparently. I suppose we'll go with the single list with bounce messages. I'll follow up with infra later today. On 18 March 2017 at 13:12, Ralph Goers wrote: > OK. I guess I am fine with the bounce messages. Any other opinions? > > Ralph > > On Mar

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

OK. I guess I am fine with the bounce messages. Any other opinions? Ralph > On Mar 18, 2017, at 8:42 AM, Matt Sicker wrote: > > I got this response from Gavin: > > Hi [~jvz] Sorry but I think I'm going to push back on that last request. > > Merging the lists - no problem >

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

I got this response from Gavin: Hi [~jvz] Sorry but I think I'm going to push back on that last request. Merging the lists - no problem Merging all the subscribers - no problem Creating bounce messages directing people to use the merged target list - no problem People will know in advance this

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Oh, I didn't realise I had a response on how to handle that. Let me follow up with infra. On 16 March 2017 at 21:46, Ralph Goers wrote: > Is there any follow-up to this? > > Ralph > > On Mar 12, 2017, at 9:30 PM, Ralph Goers > wrote: > >

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Is there any follow-up to this? Ralph > On Mar 12, 2017, at 9:30 PM, Ralph Goers wrote: > > 1. That seems fine to me. > 2. Is it possible to do both? I like the idea of annoying the sender but > still allowing the email to be sent. It would cool if it could even

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

1. That seems fine to me. 2. Is it possible to do both? I like the idea of annoying the sender but still allowing the email to be sent. It would cool if it could even add [list] to the start of the subject line. 3. This is the main thing that needs to happen. Ralph > On Mar 12, 2017, at 7:49

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Some things: 1. Archives won't be merged. 2. Infra suggests it might be a better idea to have the old email addresses respond with a canned reply saying that the lists have moved over to dev@, though they can set it up all as aliases if we prefer. 3. Current subscribers from all dev lists would

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Created a request, not sure if it's public: https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-13651 On 12 March 2017 at 17:11, Ralph Goers wrote: > Yes, > > If you could send the request to infra I would appreciate it. > > Ralph > > On Mar 12, 2017,

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Yes, If you could send the request to infra I would appreciate it. Ralph > On Mar 12, 2017, at 1:13 PM, Matt Sicker wrote: > > The vote has been open for 5 days now. Based on the tallies and discussions, > it sounds like we'd like to merge the dev lists but keep the user

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

The vote has been open for 5 days now. Based on the tallies and discussions, it sounds like we'd like to merge the dev lists but keep the user lists as is. Shall we move forward with combining them now? On 10 March 2017 at 12:27, Dominik Psenner wrote: > Total agreement. > >

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Total agreement. On 10 Mar 2017 6:26 p.m., "Ralph Goers" wrote: > This is exactly why we need one dev list. These last two responses dropped > the other lists. This is a horrible way to have discussions that affect > all the sub projects. > > Ralph > > > On Mar 10,

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

This is exactly why we need one dev list. These last two responses dropped the other lists. This is a horrible way to have discussions that affect all the sub projects. Ralph > On Mar 10, 2017, at 9:11 AM, Matt Sicker wrote: > > I'd love to see more unified configurations

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

I'd love to see more unified configurations in all the subprojects. Gary mentioned that as an idea for log4cxx as that would make it useful for his use case where they're using both Java and C++ in various projects. While the programming languages in use here (Java, .NET, PHP, and C++) aren't

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

I think that a vast majority of our users only uses one of the languages we support, and therefore only are interested in one of the subprojects. On Fri, Mar 10, 2017 at 11:23 AM, Dominik Psenner wrote: > We had once the discussion that we wanted all Apache Logging projects

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

We had once the discussion that we wanted all Apache Logging projects to become very similar in their usage, starting with the same or a very similar configuration. Given that we should aim towards one Apache Logging specification and several Apache Logging specification implementations in the

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Guten Tag Ralph Goers, am Donnerstag, 9. März 2017 um 19:24 schrieben Sie: > We use general as mainly an announcement list for topics that might > be of general interest to all logging projects. Generally, these are just > release announcements. And "general-dev@" is not an option because one

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

We use general as mainly an announcement list for topics that might be of general interest to all logging projects. Generally, these are just release announcements. Ralph > On Mar 9, 2017, at 10:37 AM, Matt Sicker wrote: > > Yeah, I agree that the user lists can remain

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Yeah, I agree that the user lists can remain separate as it doesn't cause any issues currently. The main idea here is whether we should merge the dev lists into one, or if we need a common dev list for all devs to subscribe to (general@ doesn't sound appropriate, but I don't know what that list is