+1
Am 26.02.19, 13:29 schrieb "Christofer Dutz" <[email protected]>:
In the new Apache Training podling someone came up with something cool ...
How about sending Issue creates to dev@ and issues@ and all updates and
closes just to @issues
This way we are informed for something new coming in and are not spammed by
updates?
I really like this idea
Chris
Am 22.02.19, 16:32 schrieb "Christofer Dutz" <[email protected]>:
Thanks for that ... I just added it to the pom.xml ... should appear in
a while.
Chris
Am 22.02.19, 14:40 schrieb "Otto Fowler" <[email protected]>:
It isn’t listed on the website is it?
On February 22, 2019 at 04:26:08, Christofer Dutz
([email protected])
wrote:
Well we already have a commits@ mailing list ;-)
But if we had a separate list, I would prefer that than directing
things to
commits@.
We intentionally didn't have more than dev and commits as the
incubator
likes it's podlings to have a reduced number of lists at the start
as this
way community is better built. Otherwise you'll just feel lost in
empty
lists.
Chris
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Julian Feinauer <[email protected]>
Sent: Friday, February 22, 2019 9:38:48 AM
To: [email protected]
Subject: Re: [DISCUSS] Send Jira emails to [email protected]?
Hi,
I agree with Chris... I would start with our dev@ list and monitor
it and
go over to a separate list when necessary.
Julian
Am 22.02.19, 09:29 schrieb "Tim Mitsch"
<[email protected]>:
I don’t know the amount of work that has to be spent on creating a
new list
for those kind of notifications.
But with this project continouusly growing and growing maybe also
ticket-count and stuff like this will rise, so i can understand Otto
concern.
If it’s possible (and could be done in a tolerable amount of time)
i like
the idea of splitting mailing-list into dev-stuff (feature and
discussions)
and orga-stuff (issues,commits)
Best
Tim
Von: Christofer Dutz <[email protected]>
Datum: Freitag, 22. Februar 2019 um 09:14
An: "[email protected]" <[email protected]>, Tim Mitsch <
[email protected]>
Betreff: Re: [DISCUSS] Send Jira emails to [email protected]?
I think it's all a volume thing ... I agree that github code review
emails
in some projects (Apache Commons) are super annoying, however do we
only
have a hand full of new issues per month. Didn't think it's worth
creating
a dedicated List for that. And we can always create it and redirect
as soon
as it starts really becoming annoying ... But what do the others
think?
Rather create a separate list?
Chris
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Otto Fowler <[email protected]>
Sent: Thursday, February 21, 2019 4:31:09 PM
To: [email protected]; Tim Mitsch
Subject: Re: [DISCUSS] Send Jira emails to [email protected]?
-1 most projects have an issues@ list for this type of thing.
Dev lists that have build, jira, github stuff spamming them stink.
Does this incubator have:
issues@
commits@
users@
setup or is it just dev@?
On February 21, 2019 at 06:22:52, Tim Mitsch (
[email protected]) wrote:
+1
It would be good to be noticed.
Am 21.02.19, 11:32 schrieb "Christofer Dutz"
<[email protected]>:
Hi all,
today I noticed again that a user seems to have created an issue
and we
didn’t get notified. I would like to have infra configure our
project to
automatically send emails to the dev list …
If there are no objections, I would request this ASAP.
Chris
