Setup of a [e-mail].a.o mailing list

[Robert Metzger]

Hi,

I wanted to ask if we should set up a [hidden email] list?
It seems that JIRA is sending emails for every activity. And I think our
activity in JIRA is pretty low currently, so the traffic is probably going
up in the future.

Since we do not have a separate users@ and dev@ mailing list, I don't want
to scare away users that are just subscribed for support or because they
are interested.
Or would it be more common to send the JIRA mails to [hidden email] ?

What do you think?

Robert

[Sean Owen]

I think it is helpful to separate automated test / commit
notifications into a separate list, separate from even dev and user.
Especially if there is no dev list, it's essential. I like issues@
myself as a place for automated notifications of all kinds. Later,
consider a dev@ list if it's clear there is a lot of traffic that is
not really user-relevant.

On Wed, Jun 11, 2014 at 5:27 PM, Robert Metzger <[hidden email]> wrote:

> Hi,
>
> I wanted to ask if we should set up a [hidden email] list?
> It seems that JIRA is sending emails for every activity. And I think our
> activity in JIRA is pretty low currently, so the traffic is probably going
> up in the future.
>
> Since we do not have a separate users@ and dev@ mailing list, I don't want
> to scare away users that are just subscribed for support or because they
> are interested.
> Or would it be more common to send the JIRA mails to [hidden email] ?
>
> What do you think?
>
> Robert

[Ted Dunning]

JIRA can also be reconfigured to send only to dev@ on create.




On Wed, Jun 11, 2014 at 4:08 PM, Sean Owen <[hidden email]> wrote:

> I think it is helpful to separate automated test / commit
> notifications into a separate list, separate from even dev and user.
> Especially if there is no dev list, it's essential. I like issues@
> myself as a place for automated notifications of all kinds. Later,
> consider a dev@ list if it's clear there is a lot of traffic that is
> not really user-relevant.
>
> On Wed, Jun 11, 2014 at 5:27 PM, Robert Metzger <[hidden email]>
> wrote:
> > Hi,
> >
> > I wanted to ask if we should set up a [hidden email] list?
> > It seems that JIRA is sending emails for every activity. And I think our
> > activity in JIRA is pretty low currently, so the traffic is probably
> going
> > up in the future.
> >
> > Since we do not have a separate users@ and dev@ mailing list, I don't
> want
> > to scare away users that are just subscribed for support or because they
> > are interested.
> > Or would it be more common to send the JIRA mails to [hidden email]
> ?
> >
> > What do you think?
> >
> > Robert
>

[Henry Saputra]

My 2 cents is we either keep Jira updates to dev@ list or as Ted mentioned
maybe send emails only on create, and postpone issues@ list creation once
we have everything setup or until Jira updates become too noisy in the dev@
list.

Creating issues@ list at this point i believe is too early. I am seeing
good traffic of Jira updates that have not been noise in the dev@ list for
now.



On Wednesday, June 11, 2014, Ted Dunning <[hidden email]> wrote:

> JIRA can also be reconfigured to send only to dev@ on create.
>
>
>
>
> On Wed, Jun 11, 2014 at 4:08 PM, Sean Owen <[hidden email]
> <javascript:;>> wrote:
>
> > I think it is helpful to separate automated test / commit
> > notifications into a separate list, separate from even dev and user.
> > Especially if there is no dev list, it's essential. I like issues@
> > myself as a place for automated notifications of all kinds. Later,
> > consider a dev@ list if it's clear there is a lot of traffic that is
> > not really user-relevant.
> >
> > On Wed, Jun 11, 2014 at 5:27 PM, Robert Metzger <[hidden email]
> <javascript:;>>
> > wrote:
> > > Hi,
> > >
> > > I wanted to ask if we should set up a [hidden email] list?
> > > It seems that JIRA is sending emails for every activity. And I think
> our
> > > activity in JIRA is pretty low currently, so the traffic is probably
> > going
> > > up in the future.
> > >
> > > Since we do not have a separate users@ and dev@ mailing list, I don't
> > want
> > > to scare away users that are just subscribed for support or because
> they
> > > are interested.
> > > Or would it be more common to send the JIRA mails to
> [hidden email]
> > ?
> > >
> > > What do you think?
> > >
> > > Robert
> >
>

[Stephan Ewen]

Hi!

I would actually vote to get the issue@ list started rather soon.

I like all comments and updates being posted on lists (easier to follow),
so I would vote against having only create messages on the lists.

By next week all people will have switched to the Apache infrastructure.
Since we commented quite a bit on issues in the past, I would assume that
issue related traffic will increase soon.

Stephan

[Rajika Kumarasiri]

We should do what other Apache projects do.

Rajika


On Wed, Jun 11, 2014 at 5:27 PM, Robert Metzger <[hidden email]> wrote:

> Hi,
>
> I wanted to ask if we should set up a [hidden email] list?
> It seems that JIRA is sending emails for every activity. And I think our
> activity in JIRA is pretty low currently, so the traffic is probably going
> up in the future.
>
> Since we do not have a separate users@ and dev@ mailing list, I don't want
> to scare away users that are just subscribed for support or because they
> are interested.
> Or would it be more common to send the JIRA mails to [hidden email] ?
>
> What do you think?
>
> Robert
>

[Ufuk Celebi]

> On 12 Jun 2014, at 14:52, Stephan Ewen <[hidden email]> wrote:
>
> I would actually vote to get the issue@ list started rather soon.
>
> I like all comments and updates being posted on lists (easier to follow),
> so I would vote against having only create messages on the lists.

+1

[Ted Dunning]

You can split the difference here by having creates go to dev and all
messages (including creates) go to issues.




On Thu, Jun 12, 2014 at 2:15 PM, Ufuk Celebi <[hidden email]> wrote:

>
> > On 12 Jun 2014, at 14:52, Stephan Ewen <[hidden email]> wrote:
> >
> > I would actually vote to get the issue@ list started rather soon.
> >
> > I like all comments and updates being posted on lists (easier to follow),
> > so I would vote against having only create messages on the lists.
>
> +1
>

[Stephan Ewen]

+1 for Ted's suggestion

That sounds to me like the best solution.

[Ufuk Celebi]

> On 13 Jun 2014, at 00:55, Stephan Ewen <[hidden email]> wrote:
>
> +1 for Ted's suggestion
>
> That sounds to me like the best solution.

+1

[Robert Metzger]

+1

Can one of the mentors request the issues@flink. mailing list via the mlreq
form? https://infra.apache.org/officers/mlreq/incubator


On Fri, Jun 13, 2014 at 7:51 AM, Ufuk Celebi <[hidden email]> wrote:

>
> > On 13 Jun 2014, at 00:55, Stephan Ewen <[hidden email]> wrote:
> >
> > +1 for Ted's suggestion
> >
> > That sounds to me like the best solution.
>
> +1
>

[Stephan Ewen]

Seems that no one is opposed to that.

Do the mentors approve?

[Henry Saputra]

Looks like good compromise.

I will create issues@ list by EOD if no more comment, then will create
JIRA for INFRA to split the email notifications (I am not sure if we
can do the split in the JIRA admin)

- Henry

On Tue, Jun 17, 2014 at 8:00 AM, Stephan Ewen <[hidden email]> wrote:
> Seems that no one is opposed to that.
>
> Do the mentors approve?

[Robert Metzger-2]

Thank you.

We can not change the notifications ourselves, so Infra has to do that.


Sent from my iPhone

> On 17.06.2014, at 22:36, Henry Saputra <[hidden email]> wrote:
>
> Looks like good compromise.
>
> I will create issues@ list by EOD if no more comment, then will create
> JIRA for INFRA to split the email notifications (I am not sure if we
> can do the split in the JIRA admin)
>
> - Henry
>
>> On Tue, Jun 17, 2014 at 8:00 AM, Stephan Ewen <[hidden email]> wrote:
>> Seems that no one is opposed to that.
>>
>> Do the mentors approve?

[Henry Saputra]

Request created:

"
Submitted request(s)

{
  "version": 4,
  "type": "podling",
  "private": false,
  "subdomain": "flink",
  "outhost": "flink.incubator.apache.org",
  "localpart": "issues",
  "domain": "apache.org",
  "moderators": "[hidden email],[hidden email],[hidden email]",
  "muopts": "mu",
  "replytolist": true,
  "notifyee": "[hidden email]",
  "message": "Please route JIRA creation for Apache Flink incubating
to dev@ list and all other JIRA messages (including creation) to the
new issues@ list."
}

svn add -- input/flink-issues.json

A         input/flink-issues.json

svn add -- input/flink+.json

A         input/flink+.json

svn commit --no-auth-cache --non-interactive -m
'[hidden email] mailing list request by hsaputra via
140.211.11.72' -- input/flink-issues.json input/flink+.json

Adding         input/flink+.json

Adding         input/flink-issues.json

Transmitting file data ..

Committed revision 912983.

Next steps: We will create the lists and email
[hidden email] once we have done that. There is <em>no
need</em> to file a JIRA.
"

Will file INFRA ticket to route JIRA creation to dev@ and the rest to
issues@ list.

Thanks,

Henry


On Tue, Jun 17, 2014 at 2:41 PM, Robert Metzger <[hidden email]> wrote:

> Thank you.
>
> We can not change the notifications ourselves, so Infra has to do that.
>
>
> Sent from my iPhone
>
>> On 17.06.2014, at 22:36, Henry Saputra <[hidden email]> wrote:
>>
>> Looks like good compromise.
>>
>> I will create issues@ list by EOD if no more comment, then will create
>> JIRA for INFRA to split the email notifications (I am not sure if we
>> can do the split in the JIRA admin)
>>
>> - Henry
>>
>>> On Tue, Jun 17, 2014 at 8:00 AM, Stephan Ewen <[hidden email]> wrote:
>>> Seems that no one is opposed to that.
>>>
>>> Do the mentors approve?

[Stephan Ewen]

Perfect, thanks Henry!

[Henry Saputra]

Hi All,

The issues@ list is created and I created INFRA ticket [1] to reroute
the JIRA emails.

Thanks,

Henry


[1] https://issues.apache.org/jira/browse/INFRA-7935

On Thu, Jun 19, 2014 at 5:30 AM, Stephan Ewen <[hidden email]> wrote:
> Perfect, thanks Henry!