[VOTE] Create a "notifications" mailing list

[Jacopo Cappellato-5]

Rationale: Jira notifications are currently sent to the "dev" list, causing
a lot of traffic and sometimes distracting from actual conversations; the
creation of a "notification" email (similar to the "commits" mailing list)
will solve this problem; in the future we may vote to use the
"notification" list to host traffic coming from buildbot etc... thus the
proposal for naming it "notifications" rather than just "issues"; however
this vote is only about traffic from Jira (we will discuss if we want to
extend the usage of this list in the future).

Please vote,

+1

to create a "notifications" mailing list (i.e.
[hidden email]) and redirect to it all the traffic coming
from Jira notifications.

Otherwise vote -1 to continue to use the "dev" list for Jira notifications.

[Gil Portenseigne]

+1

I actually use mail filter to separate Jira notifications from other dev mails. But i understand that not everyone can use filter...

Gil

On 24/07/2016 14:59, Jacopo Cappellato wrote:

Rationale: Jira notifications are currently sent to the "dev" list, causing
a lot of traffic and sometimes distracting from actual conversations; the
creation of a "notification" email (similar to the "commits" mailing list)
will solve this problem; in the future we may vote to use the
"notification" list to host traffic coming from buildbot etc... thus the
proposal for naming it "notifications" rather than just "issues"; however
this vote is only about traffic from Jira (we will discuss if we want to
extend the usage of this list in the future).

Please vote,

+1

to create a "notifications" mailing list (i.e.
[hidden email]) and redirect to it all the traffic coming
from Jira notifications.

Otherwise vote -1 to continue to use the "dev" list for Jira notifications.

[taher]

+1 this would make things nice and clear

On Sunday, 24 July 2016, Jacopo Cappellato <
[hidden email]> wrote:

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email] <javascript:;>) and redirect to it all the
> traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Michael Brohl-3]

+1

Michael Brohl
ecomify GmbH
www.ecomify.de

Am 24.07.16 um 14:59 schrieb Jacopo Cappellato:

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Jacques Le Roux]

+1 (thought by filtering locally I already resolved this issue)

Jacques


Le 24/07/2016 à 14:59, Jacopo Cappellato a écrit :

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Jacques Le Roux]

Le 24/07/2016 à 15:17, gil portenseigne a écrit :
> +1
>
> I actually use mail filter to separate Jira notifications from other dev mails. But i understand that not everyone can use filter...

Right Gil, we tend to forget others once we have resolved the issue for us :)

Jacques

>
> Gil
>
> On 24/07/2016 14:59, Jacopo Cappellato wrote:
>> Rationale: Jira notifications are currently sent to the "dev" list, causing
>> a lot of traffic and sometimes distracting from actual conversations; the
>> creation of a "notification" email (similar to the "commits" mailing list)
>> will solve this problem; in the future we may vote to use the
>> "notification" list to host traffic coming from buildbot etc... thus the
>> proposal for naming it "notifications" rather than just "issues"; however
>> this vote is only about traffic from Jira (we will discuss if we want to
>> extend the usage of this list in the future).
>>
>> Please vote,
>>
>> +1
>>
>> to create a "notifications" mailing list (i.e.
>> [hidden email]) and redirect to it all the traffic coming
>> from Jira notifications.
>>
>> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>>
>

[Sharan-F]

+1 excellent idea - lately it has been hard to find discussion threads
and messages with all the jira traffic.

Thanks
Sharan

On 24/07/16 14:59, Jacopo Cappellato wrote:

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Julien NICOLAS]

+1 Good idea :)


On 24/07/2016 14:59, Jacopo Cappellato wrote:

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Scott Gray-3]

+1 thanks Jacopo

On 25 July 2016 at 08:38, Julien NICOLAS <[hidden email]> wrote:

> +1 Good idea :)
>
>
>
> On 24/07/2016 14:59, Jacopo Cappellato wrote:
>
>> Rationale: Jira notifications are currently sent to the "dev" list,
>> causing
>> a lot of traffic and sometimes distracting from actual conversations; the
>> creation of a "notification" email (similar to the "commits" mailing list)
>> will solve this problem; in the future we may vote to use the
>> "notification" list to host traffic coming from buildbot etc... thus the
>> proposal for naming it "notifications" rather than just "issues"; however
>> this vote is only about traffic from Jira (we will discuss if we want to
>> extend the usage of this list in the future).
>>
>> Please vote,
>>
>> +1
>>
>> to create a "notifications" mailing list (i.e.
>> [hidden email]) and redirect to it all the traffic coming
>> from Jira notifications.
>>
>> Otherwise vote -1 to continue to use the "dev" list for Jira
>> notifications.
>>
>>
>

[Ashish Vijaywargiya-4]

+1

--
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997


On Sun, Jul 24, 2016 at 6:29 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Deepak Dixit-3]

+1

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Mon, Jul 25, 2016 at 9:31 AM, Ashish Vijaywargiya <
[hidden email]> wrote:

> +1
>
> --
> Kind Regards
> Ashish Vijaywargiya
> HotWax Systems - est. 1997
>
>
> On Sun, Jul 24, 2016 at 6:29 PM, Jacopo Cappellato <
> [hidden email]> wrote:
>
> > Rationale: Jira notifications are currently sent to the "dev" list,
> causing
> > a lot of traffic and sometimes distracting from actual conversations; the
> > creation of a "notification" email (similar to the "commits" mailing
> list)
> > will solve this problem; in the future we may vote to use the
> > "notification" list to host traffic coming from buildbot etc... thus the
> > proposal for naming it "notifications" rather than just "issues"; however
> > this vote is only about traffic from Jira (we will discuss if we want to
> > extend the usage of this list in the future).
> >
> > Please vote,
> >
> > +1
> >
> > to create a "notifications" mailing list (i.e.
> > [hidden email]) and redirect to it all the traffic
> coming
> > from Jira notifications.
> >
> > Otherwise vote -1 to continue to use the "dev" list for Jira
> notifications.
> >
>

[Pranay Pandey-3]

+1

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Sun, Jul 24, 2016 at 6:29 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Nicolas Malin-2]

Agree, +1

Le 24/07/2016 à 14:59, Jacopo Cappellato a écrit :

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[David E. Jones-2]

+1

-David

> On 24 Jul 2016, at 05:59, Jacopo Cappellato <[hidden email]> wrote:
>
> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.

[Arun Patidar-2]

+1

Thanks & Regards
---
Arun Patidar
Manager, Enterprise Software Development
HotWax Systems
www.hotwaxsystems.com

On Sunday 24 July 2016 06:29 PM, Jacopo Cappellato wrote:

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Jacopo Cappellato-5]

+1

Jacopo

On Sun, Jul 24, 2016 at 2:59 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Rationale: Jira notifications are currently sent to the "dev" list,
> causing a lot of traffic and sometimes distracting from actual
> conversations; the creation of a "notification" email (similar to the
> "commits" mailing list) will solve this problem; in the future we may vote
> to use the "notification" list to host traffic coming from buildbot etc...
> thus the proposal for naming it "notifications" rather than just "issues";
> however this vote is only about traffic from Jira (we will discuss if we
> want to extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>
>

[Mridul Pathak-4]

+1

--
Thanks & Regards,
Mridul Pathak
HotWax Systems
http://www.hotwaxsystems.com

> On Jul 24, 2016, at 6:29 PM, Jacopo Cappellato <[hidden email]> wrote:
>
> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.

[Akash Jain]

+1

Thanks and Regards
--
Akash Jain

On Sun, Jul 24, 2016 at 6:29 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Amardeep Singh Jhajj-2]

+1

Regards,
--
Amardeep Singh Jhajj

On Sun, Jul 24, 2016 at 6:29 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Rationale: Jira notifications are currently sent to the "dev" list, causing
> a lot of traffic and sometimes distracting from actual conversations; the
> creation of a "notification" email (similar to the "commits" mailing list)
> will solve this problem; in the future we may vote to use the
> "notification" list to host traffic coming from buildbot etc... thus the
> proposal for naming it "notifications" rather than just "issues"; however
> this vote is only about traffic from Jira (we will discuss if we want to
> extend the usage of this list in the future).
>
> Please vote,
>
> +1
>
> to create a "notifications" mailing list (i.e.
> [hidden email]) and redirect to it all the traffic coming
> from Jira notifications.
>
> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>

[Jacques Le Roux]

Hi Jacopo, All,

When the new MLs will be ready (I just tried [hidden email] [hidden email] to no avail), we should
update http://ofbiz.apache.org/mailing-lists.html

BTW, did we ask infra for this part : "redirect to it all the traffic coming from Jira notifications"?

Thanks

Jacques

Jacques
Le 28/07/2016 à 16:34, Amardeep Singh Jhajj a écrit :

> +1
>
> Regards,
> --
> Amardeep Singh Jhajj
>
> On Sun, Jul 24, 2016 at 6:29 PM, Jacopo Cappellato <
> [hidden email]> wrote:
>
>> Rationale: Jira notifications are currently sent to the "dev" list, causing
>> a lot of traffic and sometimes distracting from actual conversations; the
>> creation of a "notification" email (similar to the "commits" mailing list)
>> will solve this problem; in the future we may vote to use the
>> "notification" list to host traffic coming from buildbot etc... thus the
>> proposal for naming it "notifications" rather than just "issues"; however
>> this vote is only about traffic from Jira (we will discuss if we want to
>> extend the usage of this list in the future).
>>
>> Please vote,
>>
>> +1
>>
>> to create a "notifications" mailing list (i.e.
>> [hidden email]) and redirect to it all the traffic coming
>> from Jira notifications.
>>
>> Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
>>