Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B938F200C3A for ; Fri, 17 Mar 2017 04:23:54 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B7B83160B78; Fri, 17 Mar 2017 03:23:54 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3C32A160B8B for ; Fri, 17 Mar 2017 04:23:53 +0100 (CET) Received: (qmail 24538 invoked by uid 500); 17 Mar 2017 03:23:52 -0000 Mailing-List: contact log4php-dev-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4PHP Dev" List-Id: Delivered-To: mailing list log4php-dev@logging.apache.org Received: (qmail 24123 invoked by uid 99); 17 Mar 2017 03:23:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Mar 2017 03:23:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 34BC2C19DF; Fri, 17 Mar 2017 03:23:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.379 X-Spam-Level: *** X-Spam-Status: No, score=3.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_REPLY=1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id WvUFhCibg1Y6; Fri, 17 Mar 2017 03:23:49 +0000 (UTC) Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com [209.85.215.48]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id A0B045FB79; Fri, 17 Mar 2017 03:23:48 +0000 (UTC) Received: by mail-lf0-f48.google.com with SMTP id j90so28063321lfk.2; Thu, 16 Mar 2017 20:23:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XcASPDwp6lsaKoAZ12jmeFkV7mc47eNFQYvoOEsM+LE=; b=WZavpotngPeoS0yMKCqLatEQO0/OXwqExraDj84LTi2twFXT+1iABsp/KE4qD+PKuJ ZAL95EF1HwlgeI2p2BBMShLuIptDm9k5aOXkRJ1096Xa3jXyFpx5ufjZhuYKR9C8JKeW /jAbUIhldtV+Y8xOQq9EjfmMYuVpB1I2dqjN5Wme4mtNqDs+OlOYXmuu4XssiAH4uFxU N3B6CSpxuHfazLUHp66M0A8XLp7Qc2NXSiPvWlh1WC9Emn+QmKO+KTAaSnpsYm1Ng+U+ o3+WaWKUmJrP3M2kZOClU3m5uNvFCz3V8na032WYdYXJ4fQdqW0WqtonUFxpn4bIu8ia yjAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XcASPDwp6lsaKoAZ12jmeFkV7mc47eNFQYvoOEsM+LE=; b=R5/IER1VI8L2c40vBwEJl/6xGIAjlChcJOn++P/HPT2f2L9eIhun8f+i8GlO8++KP2 YH6xuYNaJgRx3Tjir2bP4nrD/h74rWZh8Xg9PZFmeVURHuUe9ubQM7rvX729uNQUOJ+x nl7vFwfsbHDiGVS6/C/IvZSbpPNnOtcJvGY1YBkSzj3tFc5kaXX9ihj8trB+tGhVUkrp e67cOTMvxbZBvghat3HXFKIQnaxW9pUdabGegVfHBmSfdgdHRBWFNEXaXgIBlAyFAdA8 38Tcc5mTpvxr6SEXzZT7ZoCQmzD8Jh/vnxnWoYPd55sNYtCqHftwkEQB052ciiMrCQ0M Yvcg== X-Gm-Message-State: AFeK/H0cnXLGGDUuxo6IXWtR+8UhXPoCI9nLF1+sP72Z61K6zLRBOOewGlg0lK51YBjaUQtlyeHcnHUknvoUKw== X-Received: by 10.25.199.82 with SMTP id x79mr3908095lff.115.1489721026545; Thu, 16 Mar 2017 20:23:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.227.77 with HTTP; Thu, 16 Mar 2017 20:23:45 -0700 (PDT) In-Reply-To: <7C703EEA-24C1-494D-B004-35A90E7FF21B@dslextreme.com> References: <60ae0fb4-16d7-d59a-519e-0664a9cac77f@gmail.com> <3406CF90-67D2-4743-9077-F91F05564F95@dslextreme.com> <621E98A2-C2B6-4FE8-83B0-4F4B1F144F8F@dslextreme.com> <5C3289A8-CDCA-4B29-B4AD-6BD7F56D4ABD@dslextreme.com> <7C703EEA-24C1-494D-B004-35A90E7FF21B@dslextreme.com> From: Matt Sicker Date: Thu, 16 Mar 2017 22:23:45 -0500 Message-ID: Subject: Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@ To: Log4NET Dev Cc: Logging PMC , Log4CXX Dev , Log4J Developers List , log4php-dev@logging.apache.org Content-Type: multipart/alternative; boundary=94eb2c1a19f89a0cb3054ae4b464 archived-at: Fri, 17 Mar 2017 03:23:54 -0000 --94eb2c1a19f89a0cb3054ae4b464 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: > > 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 PM, Matt Sicker wrote: > > 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 ov= er > to dev@, though they can set it up all as aliases if we prefer. > 3. Current subscribers from all dev lists would be automatically > subscribed to the combined list. > > So, use aliases or have the old addresses bounce back and inform senders > to use the new list? > > On 12 March 2017 at 18:31, Matt Sicker wrote: > >> 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, 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 t= he >>> user lists as is. Shall we move forward with combining them now? >>> >>> On 10 March 2017 at 12:27, Dominik Psenner wrote: >>> >>>> 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, 2017, at 9:11 AM, Matt Sicker wrote: >>>>> >>>>> 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 usef= ul for >>>>> his use case where they're using both Java and C++ in various project= s. >>>>> >>>>> While the programming languages in use here (Java, .NET, PHP, and C++= ) >>>>> aren't really compatible with each other, having similar architecture= s and >>>>> plugin systems could help a bit in this regard. Having more inclusive >>>>> conversations about this would be great. >>>>> >>>>> On 10 March 2017 at 04:29, Mikael St=C3=A5ldal >>>>> wrote: >>>>> >>>>>> 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 th= e >>>>>> 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 to become very similar in their usage, starting with the s= ame or a >>>>>>> very similar configuration. Given that we should aim towards one Ap= ache >>>>>>> Logging specification and several Apache Logging specification >>>>>>> implementations in the form of Apache Logging subprojects. That mea= ns all >>>>>>> the devs for all subprojects have to talk more. To me this is a goo= d >>>>>>> reasons to merge the dev mailing lists. Further I don't see why the= same >>>>>>> use case should not apply to the user mailing lists, too. Those mai= ling >>>>>>> lists see very low traffic but all of them need a larger audience. = Just >>>>>>> quoting the last few messages of two user mailing lists I follow: >>>>>>> >>>>>>> log4j-user: the last topic came in a week ago, the topic before tha= t >>>>>>> about two weeks ago >>>>>>> log4net-user: the last topic came in 24 hours ago and the topic >>>>>>> before that a month ago >>>>>>> >>>>>>> Cheers >>>>>>> On 2017-03-09 19:24, Ralph Goers wrote: >>>>>>> >>>>>>> We use general as mainly an announcement list for topics that might >>>>>>> be of general interest to all logging projects. Generally, these ar= e just >>>>>>> release announcements. >>>>>>> >>>>>>> Ralph >>>>>>> >>>>>>> On Mar 9, 2017, at 10:37 AM, Matt Sicker wrote: >>>>>>> >>>>>>> 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 dev= s to >>>>>>> subscribe to (general@ doesn't sound appropriate, but I don't know >>>>>>> what that list is for). >>>>>>> >>>>>>> On 9 March 2017 at 10:26, Ralph Goers >>>>>>> wrote: >>>>>>> >>>>>>>> You should note that while we consider all votes only PMC votes ar= e >>>>>>>> =E2=80=9Cbinding=E2=80=9D. I don=E2=80=99t think that changes much= however. >>>>>>>> >>>>>>>> From a PMC perspective I have to say that keeping the user=E2=80= =99s lists >>>>>>>> separate isn=E2=80=99t likely to be an issue as most of the things= that would need >>>>>>>> to be discussed would be on a dev list anyway. >>>>>>>> >>>>>>>> Ralph >>>>>>>> >>>>>>>> On Mar 9, 2017, at 2:45 AM, Dominik Psenner >>>>>>>> wrote: >>>>>>>> >>>>>>>> The votes are way too scattered over the different mailing lists s= o >>>>>>>> that I didn't even find my own vote. ;-) Therefore I'm trying to s= ummarize >>>>>>>> the current state of the vote: >>>>>>>> >>>>>>>> log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> dev@loggin= g.apache.org >>>>>>>> >>>>>>>> Matt Sicker: +1 >>>>>>>> Ralph Goers: +1 >>>>>>>> Stefan Bodewig: +1 >>>>>>>> Sven Rautenverg: -1 >>>>>>>> Thorsten Sch=C3=B6ning: -0 >>>>>>>> Ivan Habunek: -0 >>>>>>>> Dominik Psenner: +1 >>>>>>>> Remko Popma: +1 >>>>>>>> Mikael St=C3=A5ldal: +0 >>>>>>>> >>>>>>>> Totals so far: >>>>>>>> +1: 5 >>>>>>>> +0: 1 >>>>>>>> -0: 2 >>>>>>>> -1: 1 >>>>>>>> >>>>>>>> log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, general@= -> user@logging.apache.org >>>>>>>> >>>>>>>> Matt Sicker: -1 >>>>>>>> Ralph Goers: +1 >>>>>>>> Stefan Bodewig: -1 >>>>>>>> Sven Rautenverg: -1 >>>>>>>> Thorsten Sch=C3=B6ning: -0 >>>>>>>> Ivan Habunek: -0 >>>>>>>> Dominik Psenner: +1 >>>>>>>> Remko Popma: +1 >>>>>>>> Mikael St=C3=A5ldal: -1 >>>>>>>> >>>>>>>> Totals so far: >>>>>>>> +1: 3 >>>>>>>> +0: 0 >>>>>>>> -0: 2 >>>>>>>> -1: 4 >>>>>>>> >>>>>>>> Sorry to anyone who's vote is missing. >>>>>>>> >>>>>>>> On 2017-03-08 05:20, Matt Sicker wrote: >>>>>>>> >>>>>>>> I may be missing some mailing lists considering I just subscribed >>>>>>>> to half of them less than five minutes ago. >>>>>>>> >>>>>>>> This is a vote to merge the various Apache Logging Services mailin= g >>>>>>>> lists. The proposal is to combine them as follows: >>>>>>>> >>>>>>>> log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> >>>>>>>> dev@logging.apache.org >>>>>>>> log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, general@ >>>>>>>> -> user@logging.apache.org >>>>>>>> >>>>>>>> commits@ and private@ remain the same as before. >>>>>>>> >>>>>>>> The proposal would also suggest that the old emails become aliases >>>>>>>> for the combined email names so as not to lose any future emails. = To >>>>>>>> distinguish between projects, a subject tag can be added such as: >>>>>>>> >>>>>>>> [java] >>>>>>>> [net] >>>>>>>> [cxx] >>>>>>>> [php] >>>>>>>> >>>>>>>> Though I wouldn't think such a tag is required, though it should >>>>>>>> help in gaining the attention of the appropriate audience. >>>>>>>> >>>>>>>> Voting: >>>>>>>> >>>>>>>> +1: Yes, combine the mailing lists! >>>>>>>> +0: Go ahead, don't care that much. >>>>>>>> -0: Don't like it, but not vetoing it. >>>>>>>> -1: No, don't do that! I have a better idea! >>>>>>>> >>>>>>>> This vote follows the same "lazy consensus" (at least 3 +1 binding= , >>>>>>>> no -1/vetoes) we use for general releases and whatnot. The vote wi= ll be >>>>>>>> open for at least 72 hours. >>>>>>>> >>>>>>>> -- >>>>>>>> Matt Sicker >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Matt Sicker >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> [image: MagineTV] >>>>>> >>>>>> *Mikael St=C3=A5ldal* >>>>>> Senior software developer >>>>>> >>>>>> *Magine TV* >>>>>> mikael.staldal@magine.com >>>>>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >>>>>> >>>>>> >>>>>> Privileged and/or Confidential Information may be contained in this >>>>>> message. If you are not the addressee indicated in this message >>>>>> (or responsible for delivery of the message to such a person), you >>>>>> may not copy or deliver this message to anyone. In such case, >>>>>> you should destroy this message and kindly notify the sender by repl= y >>>>>> email. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matt Sicker >>>>> >>>>> >>>>> >>> >>> >>> -- >>> Matt Sicker >>> >>> >>> >> >> >> -- >> Matt Sicker >> > > > > -- > Matt Sicker > > > > --=20 Matt Sicker --94eb2c1a19f89a0cb3054ae4b464 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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 <r= alph.goers@dslextreme.com> wrote:
Is there any follow-up to t= his? =C2=A0

Ralph

On Mar 12, 2017, at 9:30 PM, Ralph Goers <ralph.goers@dslext= reme.com> wrote:

1. That seems = fine to me.
2. Is it possible to do both? I like the idea of anno= ying the sender but still allowing the email to be sent. It would cool if i= t 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 PM, Matt Sicker <boards@gmail.com> wrote:

Some thin= gs:

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 t= hey can set it up all as aliases if we prefer.
3. Current subscri= bers from all dev lists would be automatically subscribed to the combined l= ist.

So, use aliases or have the old addresses bou= nce back and inform senders to use the new list?

On 12 March 2017 at 18:31, Matt = Sicker <boards@gmail.com> wrote:
Created a request, not sure if it's public:=C2= =A0https://issues.apache.org/jira/serviced= esk/customer/portal/1/INFRA-13651
=

= On 12 March 2017 at 17:11, Ralph Goers <ralph.goers@dslextreme.co= m> wrote:
Yes,

If you could send the= request to infra I would appreciate it.

Ralph

On Mar 12, 20= 17, at 1:13 PM, Matt Sicker <boards@gmail.com> 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 lis= ts but keep the user lists as is. Shall we move forward with combining them= now?

On 10 = March 2017 at 12:27, Dominik Psenner <dpsenner@gmail.com> w= rote:
Total agreement.<= /div>

On 10 Mar 2017 6:26 p.m., "Ralph Goers" <ralph.goers@dslextreme.com> wrote:
This is exactly why we need one dev list= . These last two responses dropped the other lists.=C2=A0 This is a horribl= e way to have discussions that affect all the sub projects.

<= /div>
Ralph



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, P= HP, and C++) aren't really compatible with each other, having similar a= rchitectures and plugin systems could help a bit in this regard. Having mor= e inclusive conversations about this would be great.

On 10 March 2017 at 04:29, Mikae= l St=C3=A5ldal=C2=A0<mikael.staldal@magine.com>= =C2=A0<= /span>wrote:
I think that a vast major= ity of our users only uses one of the languages we support, and therefore o= nly are interested in one of the subprojects.

On Fri, Mar 10, 2017 at 11:23 AM, Dominik Psenner=C2=A0<dpsen= ner@gmail.com>=C2=A0wrote:

We had once the discussion that we want= ed all Apache Logging projects to become very similar in their usage, start= ing with the same or a very similar configuration. Given that we should aim= towards one Apache Logging specification and several Apache Logging specif= ication implementations in the form of Apache Logging subprojects. That mea= ns all the devs for all subprojects have to talk more. To me this is a good= reasons to merge the dev mailing lists. Further I don't see why the sa= me use case should not apply to the user mailing lists, too. Those mailing = lists see very low traffic but all of them need a larger audience. Just quo= ting the last few messages of two user mailing lists I follow:

lo= g4j-user: the last topic came in a week ago, the topic before that about tw= o weeks ago
log4net-user: the last topic came in 24 hours ago and the to= pic before that a month ago

Cheers

On 2017-03-09 19:24, Ralph Goers wrote:
We use general as mainly an announcement list for topics that migh= t 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 <boards@gmail.com> w= rote:

Yeah,= I agree that the user lists can remain separate as it doesn't cause an= y issues currently. The main idea here is whether we should merge the dev l= ists 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 li= st is for).

= On 9 March 2017 at 10:26, Ralph Goers=C2=A0<ralph.goers@dslextrem= e.com>=C2=A0wrote:
You should note that while we consider all votes on= ly PMC votes are =E2=80=9Cbinding=E2=80=9D. I don=E2=80=99t think that chan= ges much however.

From a PMC perspective I have to= say that keeping the user=E2=80=99s lists separate isn=E2=80=99t likely to= be an issue as most of the things that would need to be discussed would be= on a dev list anyway.

Ralph

On Mar 9, 2017, at 2:45 AM, Dominik Psenner <= dpsenner@gmail.com<= /a>> wrote:

The votes are way too= scattered over the different mailing lists so that I didn't even find = my own vote. ;-) Therefore I'm trying to summarize the current state of= the vote:

log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -&g=
t; dev@logging.apache.org
<= p>Matt Sicker: +1
Ralph Goers: +1
Stefan Bodewig: +1
Sven Rautenve= rg: -1
Thorsten Sch=C3=B6ning: -0
Ivan Habunek: -0
Dominik Psenner= : +1
Remko Popma: +1
Mikael St=C3=A5ldal: +0

Totals so far:
= +1: 5
+0: 1
-0: 2
-1: 1

log4j-user@, log4php-user@, log4ne=
t-user@, log4cxx-user@, general@ -> user@logging.apache.org

Matt Sicker: -1
Ralph Goers: +1
Stefan Bodewig: -1
Sven Rautenverg: -1
Thorsten Sch=C3=B6ning: -0
Ivan Habunek: -0
Dominik Psenner: +1
Remko Popma: +1
Mikael St=C3=A5ldal: -1

Totals so far:
+1: 3
+0: 0
-0: 2
-1: 4
Sorry to anyone who's vote is missing.

On 2017-03-08 05:20, Matt Sicker wrote:
<= /div>
I may be missing some maili= ng lists considering I just subscribed to half of them less than five minut= es ago.

This is a vote to merge the various Apache Loggi= ng Services mailing lists. The proposal is to combine them as follows:

log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -= >=C2= =A0dev@l= ogging.apache.org
log4j-user@, log4php-user@, log4net-user@, = log4cxx-user@, general@ ->=C2=A0user@logging.apache.org

c= ommits@ and private@ remain the same as before.

Th= e proposal would also suggest that the old emails become aliases for the co= mbined email names so as not to lose any future emails. To distinguish betw= een projects, a subject tag can be added such as:

= [java]
[net]
[cxx]
[php]

=
Though I wouldn't think such a tag is required, though it should h= elp in gaining the attention of the appropriate audience.

Voting:

+1: Yes, combine the mailing lists= !
+0: Go ahead, don't care that much.
-0: Don't= like it, but not vetoing it.
-1: No, don't do that! I have a= better idea!

This vote follows the same "laz= y consensus" (at least 3 +1 binding, no -1/vetoes) we use for general = releases and whatnot. The vote will be open for at least 72 hours.

--=C2=A0
Matt Sicker <boards@gmail.com>





--=C2=A0
Matt Sicker <boards@gmail.com>
<= /div>




--=C2=A0
3D"MagineTV"=C2=A0

Mikael St=C3=A5ldal
Senior software developer=C2=A0

<= /div>
Magine TV
mikael.staldal@magine.com= =C2=A0 =C2=A0=C2=A0
Grev Turegatan 3= =C2=A0|=C2=A0114 46 Stockholm, Sweden=C2=A0=C2=A0|=C2=A0=C2=A0=C2=A0www.magine.com=C2=A0

Privileged and/or Confidential Information may be contain= ed in this message. If you are not the addressee indicated in this message<= br>(or responsible for delivery of the message to such a person), you may n= ot copy or deliver this message to anyone. In such case,=C2=A0
you shoul= d destroy this message and kindly notify the sender by reply email. =C2=A0= =C2=A0



--=C2=A0
<= div class=3D"m_6771486501010604734m_-1881564693080257539m_91123052436934760= 3m_1692403371272423231m_3942731476876971817gmail_signature" data-smartmail= =3D"gmail_signature">Matt Sicker <boards@gmail.com>




--
=
Matt Sicker <boards@gmail.com>




--
M= att Sicker <boards= @gmail.com>


--
Matt Sicker <boa= rds@gmail.com>





--
Matt Sicker &l= t;boards@gmail.com>
--94eb2c1a19f89a0cb3054ae4b464--