You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@corinthia.apache.org by jan i <ja...@apache.org> on 2015/01/18 10:44:31 UTC
Jira and tons of mails.
Hi.
Sorry for the tons of mail, but I spent this morning making a couple of
enhancements to jira.
I have added our first (upcomming) release, named it 0.5 (if anybody feels
it should be numbered differently just let me know, I simply picked a
number).
I have added the components I am aware of (if anybody feels we need other
components or they should be named differently, please let know)
I went through all open jira issues, and tried to put release 0.5 on those
I feel should be solved before we make a release. Remark this is purely my
opinion, so please change it if you disagree.
I went through all open jira issues and assigned them to components, and in
some cases also a person. Remark this is purely my opinion, so please
change it if you disagree.
we should in general be better to assign a issue to a person, being
assigned to a issue, does not mean that person has to make it all, but that
person carries the flag for the issue, and make sure it moves forward.
Sorry again for the many mails, but at least you can see what I did this
sunday morning.
rgds
jan i
Ps. I was wondering, should we move jira mail to commits@ to have less
noise in here ?
RE: Jira and tons of mails.
Posted by "Dennis E. Hamilton" <de...@acm.org>.
+1
-----Original Message-----
From: Louis Suárez-Potts [mailto:luispo@gmail.com]
Sent: Sunday, January 18, 2015 17:13
To: dev@corinthia.incubator.apache.org; Dennis E. Hamilton
Subject: Re: Jira and tons of mails.
[ ... ]
> <orcmid>
> Yes, I just got all of my email rules working correctly so I can do
> that too.
> So, works for me. It makes for a noisy mail archive but I suppose
> the folks who use the mirrored lists via other tools must have
> solutions that work for them.
> It's the non-expert subscribers to our only mailing list that
> I worry about a little.
> </orcmid>
>
> [ … ]
When we find that bridge we'll cross it.
note/
When i first set up the OOo Native-Lang lists, I debated between one big party list and discrete lists. The party list was represented most obviously, then, by Mozilla's l10n & i18n list: All languages, all the time. Discrete lists tended to become walled gardens, silos and boredom was the least of their problems.
This kind of problem is easy enough to fix later on and there any number of solutions one can use, not least of which is just informing naive subscribers how to filter noise out. For now, I think we all agree that it's far better to have a noisy room than too much dedicated silence.
louis
>
Re: Jira and tons of mails.
Posted by Louis Suárez-Potts <lu...@gmail.com>.
> On 18 Jan 2015, at 14:02, Dennis E. Hamilton <de...@acm.org> wrote:
>
> -- replying below to --
> From: Louis Suárez-Potts [mailto:luispo@gmail.com]
> Sent: Sunday, January 18, 2015 10:35
> To: dev
> Subject: Re: Jira and tons of mails.
>
> I have no issues with issue messages sent to the dev list. I just turned it
> off for them and routed them to a folder. Were these to contain sizeable
> attachments that my mail client insisted on downloading, that could be a
> problem, at least for some.
>
> <orcmid>
> Yes, I just got all of my email rules working correctly so I can do
> that too.
> So, works for me. It makes for a noisy mail archive but I suppose
> the folks who use the mirrored lists via other tools must have
> solutions that work for them.
> It's the non-expert subscribers to our only mailing list that
> I worry about a little.
> </orcmid>
>
> [ … ]
When we find that bridge we'll cross it.
note/
When i first set up the OOo Native-Lang lists, I debated between one big party list and discrete lists. The party list was represented most obviously, then, by Mozilla's l10n & i18n list: All languages, all the time. Discrete lists tended to become walled gardens, silos and boredom was the least of their problems.
This kind of problem is easy enough to fix later on and there any number of solutions one can use, not least of which is just informing naive subscribers how to filter noise out. For now, I think we all agree that it's far better to have a noisy room than too much dedicated silence.
louis
>
RE: Jira and tons of mails.
Posted by "Dennis E. Hamilton" <de...@acm.org>.
-- replying below to --
From: Louis Suárez-Potts [mailto:luispo@gmail.com]
Sent: Sunday, January 18, 2015 10:35
To: dev
Subject: Re: Jira and tons of mails.
I have no issues with issue messages sent to the dev list. I just turned it
off for them and routed them to a folder. Were these to contain sizeable
attachments that my mail client insisted on downloading, that could be a
problem, at least for some.
<orcmid>
Yes, I just got all of my email rules working correctly so I can do
that too.
So, works for me. It makes for a noisy mail archive but I suppose
the folks who use the mirrored lists via other tools must have
solutions that work for them.
It's the non-expert subscribers to our only mailing list that
I worry about a little.
</orcmid>
[ ... ]
Re: Jira and tons of mails.
Posted by Louis Suárez-Potts <lu...@gmail.com>.
I have no issues with issue messages sent to the dev list. I just turned it
off for them and routed them to a folder. Were these to contain sizeable
attachments that my mail client insisted on downloading, that could be a
problem, at least for some.
louis
On 18 January 2015 at 12:42, Dave Fisher <da...@comcast.net> wrote:
> Olingo does most all of their dev emails through JIRA issues.
>
> It works for them. Same with legal-discuss.
>
> I am for putting them on the dev list. If we do bulk changes then the
> flood can be handled by turning off the notifications.
>
> If the project want these on another mailing list that's ok - I will route
> to the same folder in my mail client.
>
> Regards,
> Dave
>
> On Jan 18, 2015, at 8:44 AM, Dennis E. Hamilton wrote:
>
> > I would prefer that all the noise that JIRA makes for the simplest
> changes go to a separate list.
> >
> > I can handle that locally, and I see I need to fix my email filters and
> put things in a Corinthia/Issues folder better.
> >
> > What I end up having to do is currently, curate what I see in the dev @
> corinthia with what comes to my mailbox because I am following an issue.
> Part of the problem is how some email from ASF systems does not identify
> the source, but the person who performs an action, so it is necessary to
> mine the email headers to figure out what the actual source is and where
> things can go. Then spam filters mess it all up anyhow.
> >
> > I don't think having JIRA notices of the kind we have been seeing go to
> the commits list is helpful. Commits are very different. It would be cool
> if an issue-related commit could cause a JIRA comment tied to the commit,
> but I wouldn't put them all in the same reporting stream.
> >
> > - Dennis
> >
> > -----Original Message-----
> > From: Andrea Pescetti [mailto:pescetti@apache.org]
> > Sent: Sunday, January 18, 2015 06:14
> > To: dev@corinthia.incubator.apache.org
> > Subject: Re: Jira and tons of mails.
> >
> > jan i wrote:
> >> Ps. I was wondering, should we move jira mail to commits@ to have less
> >> noise in here ?
> >
> > Possibly, but it's complex. I mean, the fact that issue metadata change
> > is not relevant to this list, but maybe sending to the dev list
> > (additionally) a notification when a JIRA issue is opened (so when you
> > open an issue both lists are notified, then everything else is on the
> > commits list only) would help. This way the dev list is always
> > up-to-date with respect to development. But I realize this is complex
> > and I'm fine with moving JIRA notification to the commits list or keep
> > them here.
> >
> > Regards,
> > Andrea.
> >
>
>
--
Louis Suárez-Potts
Mobile: +1.416.625.3843 (ET)
Skype: louisiam
Twitter: @luispo
G+: https://plus.google.com/+LouisSuárezPotts
<https://plus.google.com/+LouisSu%C3%A1rezPotts>
Re: Jira and tons of mails.
Posted by Dave Fisher <da...@comcast.net>.
Olingo does most all of their dev emails through JIRA issues.
It works for them. Same with legal-discuss.
I am for putting them on the dev list. If we do bulk changes then the flood can be handled by turning off the notifications.
If the project want these on another mailing list that's ok - I will route to the same folder in my mail client.
Regards,
Dave
On Jan 18, 2015, at 8:44 AM, Dennis E. Hamilton wrote:
> I would prefer that all the noise that JIRA makes for the simplest changes go to a separate list.
>
> I can handle that locally, and I see I need to fix my email filters and put things in a Corinthia/Issues folder better.
>
> What I end up having to do is currently, curate what I see in the dev @ corinthia with what comes to my mailbox because I am following an issue. Part of the problem is how some email from ASF systems does not identify the source, but the person who performs an action, so it is necessary to mine the email headers to figure out what the actual source is and where things can go. Then spam filters mess it all up anyhow.
>
> I don't think having JIRA notices of the kind we have been seeing go to the commits list is helpful. Commits are very different. It would be cool if an issue-related commit could cause a JIRA comment tied to the commit, but I wouldn't put them all in the same reporting stream.
>
> - Dennis
>
> -----Original Message-----
> From: Andrea Pescetti [mailto:pescetti@apache.org]
> Sent: Sunday, January 18, 2015 06:14
> To: dev@corinthia.incubator.apache.org
> Subject: Re: Jira and tons of mails.
>
> jan i wrote:
>> Ps. I was wondering, should we move jira mail to commits@ to have less
>> noise in here ?
>
> Possibly, but it's complex. I mean, the fact that issue metadata change
> is not relevant to this list, but maybe sending to the dev list
> (additionally) a notification when a JIRA issue is opened (so when you
> open an issue both lists are notified, then everything else is on the
> commits list only) would help. This way the dev list is always
> up-to-date with respect to development. But I realize this is complex
> and I'm fine with moving JIRA notification to the commits list or keep
> them here.
>
> Regards,
> Andrea.
>
RE: Jira and tons of mails.
Posted by "Dennis E. Hamilton" <de...@acm.org>.
I would prefer that all the noise that JIRA makes for the simplest changes go to a separate list.
I can handle that locally, and I see I need to fix my email filters and put things in a Corinthia/Issues folder better.
What I end up having to do is currently, curate what I see in the dev @ corinthia with what comes to my mailbox because I am following an issue. Part of the problem is how some email from ASF systems does not identify the source, but the person who performs an action, so it is necessary to mine the email headers to figure out what the actual source is and where things can go. Then spam filters mess it all up anyhow.
I don't think having JIRA notices of the kind we have been seeing go to the commits list is helpful. Commits are very different. It would be cool if an issue-related commit could cause a JIRA comment tied to the commit, but I wouldn't put them all in the same reporting stream.
- Dennis
-----Original Message-----
From: Andrea Pescetti [mailto:pescetti@apache.org]
Sent: Sunday, January 18, 2015 06:14
To: dev@corinthia.incubator.apache.org
Subject: Re: Jira and tons of mails.
jan i wrote:
> Ps. I was wondering, should we move jira mail to commits@ to have less
> noise in here ?
Possibly, but it's complex. I mean, the fact that issue metadata change
is not relevant to this list, but maybe sending to the dev list
(additionally) a notification when a JIRA issue is opened (so when you
open an issue both lists are notified, then everything else is on the
commits list only) would help. This way the dev list is always
up-to-date with respect to development. But I realize this is complex
and I'm fine with moving JIRA notification to the commits list or keep
them here.
Regards,
Andrea.
Re: Jira and tons of mails.
Posted by Andrea Pescetti <pe...@apache.org>.
jan i wrote:
> Ps. I was wondering, should we move jira mail to commits@ to have less
> noise in here ?
Possibly, but it's complex. I mean, the fact that issue metadata change
is not relevant to this list, but maybe sending to the dev list
(additionally) a notification when a JIRA issue is opened (so when you
open an issue both lists are notified, then everything else is on the
commits list only) would help. This way the dev list is always
up-to-date with respect to development. But I realize this is complex
and I'm fine with moving JIRA notification to the commits list or keep
them here.
Regards,
Andrea.