Re: sending JIRA mail to commits@maven.apache.org
On Wed, 22 Feb 2006, Brett Porter wrote: I personally think a separate jira list allows for the most flexibility. The same for continuum builds, which sometimes really spam the dev list. I think the dev list should be exclusively used by human posters writing real email, discussing development. Users posting problems (which is the most part of jira mail) doesn't really belong in development discussions. If you have a separate list for everything (users,dev,jira,commits,continuum,announce) everybody can pick the ones they're interested in - everybody happy! (except that you might need to send 8 mails instead of 2 to subscribe if you want everything, but that's a one-time thing.) -- Kenney - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sending JIRA mail to commits@maven.apache.org
+1 for a jira specific list For consistency's sake :) A list for each topic. You choose the information you need. +0 for subscribing to filters from JIRA Why not, but we still need a way to get the issues as soon as they arrive, and not only once a day. +0 for RSS from JIRA filters There again, why not, but RSS is not commonly used enough yet to replace the good ol' mail. -0 (still) for subscribing to commits@ and filter out the actual commits Not everybody can filter his mail that way. ?? for setting up a group in JIRA that get sent all the same mails that [EMAIL PROTECTED] does and can be added there on request I don't get this one :) - Yann What do you think of other solutions: - subscribe to commits@ and filter out the actual commits - subscribe to filters from JIRA (so you get a daily mail of all the open or new issues in a particular project) - use RSS from JIRA filters - set up a group in JIRA that get sent all the same mails that [EMAIL PROTECTED] does and can be added there on request. Or should we have a jira specific list? - Brett
Re: sending JIRA mail to commits@maven.apache.org
Agreed with Yann and John Cheers, Vincent 2006/2/22, Yann Le Du [EMAIL PROTECTED]: +1 for a jira specific list For consistency's sake :) A list for each topic. You choose the information you need. +0 for subscribing to filters from JIRA Why not, but we still need a way to get the issues as soon as they arrive, and not only once a day. +0 for RSS from JIRA filters There again, why not, but RSS is not commonly used enough yet to replace the good ol' mail. -0 (still) for subscribing to commits@ and filter out the actual commits Not everybody can filter his mail that way. ?? for setting up a group in JIRA that get sent all the same mails that [EMAIL PROTECTED] does and can be added there on request I don't get this one :) - Yann What do you think of other solutions: - subscribe to commits@ and filter out the actual commits - subscribe to filters from JIRA (so you get a daily mail of all the open or new issues in a particular project) - use RSS from JIRA filters - set up a group in JIRA that get sent all the same mails that [EMAIL PROTECTED] does and can be added there on request. Or should we have a jira specific list? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: sending JIRA mail to commits@maven.apache.org
+1 for a separate list for flexibility. -Original Message- From: Vincent Siveton [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 22, 2006 7:51 AM To: Maven Developers List Subject: Re: sending JIRA mail to commits@maven.apache.org Agreed with Yann and John Cheers, Vincent 2006/2/22, Yann Le Du [EMAIL PROTECTED]: +1 for a jira specific list For consistency's sake :) A list for each topic. You choose the information you need. +0 for subscribing to filters from JIRA Why not, but we still need a way to get the issues as soon as they arrive, and not only once a day. +0 for RSS from JIRA filters There again, why not, but RSS is not commonly used enough yet to replace the good ol' mail. -0 (still) for subscribing to commits@ and filter out the actual commits Not everybody can filter his mail that way. ?? for setting up a group in JIRA that get sent all the same mails that [EMAIL PROTECTED] does and can be added there on request I don't get this one :) - Yann What do you think of other solutions: - subscribe to commits@ and filter out the actual commits - subscribe to filters from JIRA (so you get a daily mail of all the open or new issues in a particular project) - use RSS from JIRA filters - set up a group in JIRA that get sent all the same mails that [EMAIL PROTECTED] does and can be added there on request. Or should we have a jira specific list? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sending JIRA mail to commits@maven.apache.org
Arnaud HERITIER wrote: +1 for another list [EMAIL PROTECTED] +0 to keep the existing configuration -1 to receive the issues on commits@maven.apache.org Arnaud I agree with Arnaud. -- Dennis Lundberg On 2/22/06, Geoffrey De Smet [EMAIL PROTECTED] wrote: +1 (if I am allowed to vote :) To avoid having a full inbox, I use gmane.org: It turns mailing lists into newsgroups. So actually with this email, I am using the newsgroup gmane.comp.jakarta.turbine.maven.devel . I can't filter that, so it's very hard to follow the conversations. Having a different mailing list (and gmane newsgroup) would fix it. With kind regards, Geoffrey De Smet Emmanuel Venisse wrote: -0 for the same reason. Emmanuel John Casey a écrit : -0 I filter it all into a separate folder anyway, so I don't notice. I would tend to think that jira issues are much closer to the types of discussions which are meant to take place here...commits are more of the ground-level implementation details. I get it all anyway, so if you all have a strong consensus one way or the other, I'll go along. -john Brett Porter wrote: What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sending JIRA mail to commits@maven.apache.org
Kenney Westerhof wrote: On Wed, 22 Feb 2006, Brett Porter wrote: I personally think a separate jira list allows for the most flexibility. The same for continuum builds, which sometimes really spam the dev list. I think the dev list should be exclusively used by human posters writing real email, discussing development. Users posting problems (which is the most part of jira mail) doesn't really belong in development discussions. If you have a separate list for everything (users,dev,jira,commits,continuum,announce) everybody can pick the ones they're interested in - everybody happy! (except that you might need to send 8 mails instead of 2 to subscribe if you want everything, but that's a one-time thing.) I think that is the most sensible approach. Pick what you like and the dev list being humans only I like! When things are clearly separated like this it makes things easier. Case in point: with separate lists each described in the POM you could easily generate the rules for filtering for, say, Thunderbird and put them on the website. Then someone makes a snazzy Thunderbird plugin so that you can just drag and drop the filter on the web page into thunderbird and have it set up your folders and filters for that list! Separating information into meaningful channels is always a good thing. People can take the information from the channel if they like but right now if you don't want it you don't have a choice which I think sucks. -- Kenney - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: sending JIRA mail to commits@maven.apache.org
I vote a big +1 Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 7:11 PM To: Maven Developers List Subject: sending JIRA mail to commits@maven.apache.org What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: sending JIRA mail to commits@maven.apache.org
-1 JIRA is rather important for me to see and I would assume that would be true of anyone on the dev list. I'm less concerned with individual commits. I would personally prefer it the way it is today. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 8:11 PM To: Maven Developers List Subject: sending JIRA mail to commits@maven.apache.org What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sending JIRA mail to commits@maven.apache.org
Jolly good idea. -Jan Brett Porter [EMAIL PROTECTED] 02/21/2006 07:11 PM Please respond to Maven Developers List dev@maven.apache.org To Maven Developers List dev@maven.apache.org cc Subject sending JIRA mail to commits@maven.apache.org What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sending JIRA mail to commits@maven.apache.org
What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett -0 as a non-developer, for the same reasons as Mike. As an external user who wants to keep informed of evolutions, JIRA is as important to me as dev discussions. But SVN commits are way less important. - Yann
Re: sending JIRA mail to commits@maven.apache.org
-0 I filter it all into a separate folder anyway, so I don't notice. I would tend to think that jira issues are much closer to the types of discussions which are meant to take place here...commits are more of the ground-level implementation details. I get it all anyway, so if you all have a strong consensus one way or the other, I'll go along. -john Brett Porter wrote: What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sending JIRA mail to commits@maven.apache.org
That's been my main hesitation to this point, so its good to get this feedback. What do you think of other solutions: - subscribe to commits@ and filter out the actual commits - subscribe to filters from JIRA (so you get a daily mail of all the open or new issues in a particular project) - use RSS from JIRA filters - set up a group in JIRA that get sent all the same mails that [EMAIL PROTECTED] does and can be added there on request. Or should we have a jira specific list? - Brett Yann Le Du wrote: What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett -0 as a non-developer, for the same reasons as Mike. As an external user who wants to keep informed of evolutions, JIRA is as important to me as dev discussions. But SVN commits are way less important. - Yann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sending JIRA mail to commits@maven.apache.org
-1 Anyone subscribed to the dev list should be interested in the evolution and development of the project (otherwise he wouldn't be subscribed). JIRA is a big part of that, it really belongs here. -Lukas Brett Porter wrote: What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sending JIRA mail to commits@maven.apache.org
-0 for the same reason. Emmanuel John Casey a écrit : -0 I filter it all into a separate folder anyway, so I don't notice. I would tend to think that jira issues are much closer to the types of discussions which are meant to take place here...commits are more of the ground-level implementation details. I get it all anyway, so if you all have a strong consensus one way or the other, I'll go along. -john Brett Porter wrote: What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sending JIRA mail to commits@maven.apache.org
+1 (if I am allowed to vote :) To avoid having a full inbox, I use gmane.org: It turns mailing lists into newsgroups. So actually with this email, I am using the newsgroup gmane.comp.jakarta.turbine.maven.devel . I can't filter that, so it's very hard to follow the conversations. Having a different mailing list (and gmane newsgroup) would fix it. With kind regards, Geoffrey De Smet Emmanuel Venisse wrote: -0 for the same reason. Emmanuel John Casey a écrit : -0 I filter it all into a separate folder anyway, so I don't notice. I would tend to think that jira issues are much closer to the types of discussions which are meant to take place here...commits are more of the ground-level implementation details. I get it all anyway, so if you all have a strong consensus one way or the other, I'll go along. -john Brett Porter wrote: What do folks think of doing this to make the dev traffic a bit friendlier to the people just reading the messages? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
