plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Sommer <>
Subject AW: [DISCUSS] Send Jira emails to
Date Wed, 27 Feb 2019 12:35:56 GMT
I have to register at the list?

Mit freundlichen Grüßen

Markus Sommer

isb innovative software businesses GmbH
Otto-Lilienthal-Straße 2
D 88046 Friedrichshafen

Tel          +49 (0) 7541 3834-14
Fax         +49 (0) 7541 3834-20
Mobil    +49 (0) 171 537 8437

Mail to

Geschäftsführer: Markus Sommer, Thomas Zeler
Registergericht: Amtsgericht Ulm HRB-Nr. 631624
Important Note: This e-mail and any attachments are confidential, may contain trade secrets
and may well also be legally privileged or otherwise protected from disclosure. If you have
received it in error, you are on notice of its status. Please notify us immediately by reply
e-mail and then delete this e-mail and any attachment from your system. If you are not the
intended recipient please understand that you must not copy this e-mail or any attachments
or disclose the contents to any other person. 
Thank you.

-----Ursprüngliche Nachricht-----
Von: Christofer Dutz <> 
Gesendet: Dienstag, 26. Februar 2019 16:21
Betreff: Re: [DISCUSS] Send Jira emails to

Ok ... I took the liberty of creating the list ... will probably take
up to a day for it to be created. 
As soon as that's done I'll create an issue for setting up the Jira notifications.


Am 26.02.19, 16:15 schrieb "Otto Fowler" <>:

    On February 26, 2019 at 08:06:24, Julian Feinauer ( wrote:
    Am 26.02.19, 13:29 schrieb "Christofer Dutz" <>:
    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
    I really like this idea
    Am 22.02.19, 16:32 schrieb "Christofer Dutz" <>:
    Thanks for that ... I just added it to the pom.xml ... should appear in a
    Am 22.02.19, 14:40 schrieb "Otto Fowler" <>:
    It isn’t listed on the website is it?
    On February 22, 2019 at 04:26:08, Christofer Dutz (
    Well we already have a commits@ mailing list ;-)
    But if we had a separate list, I would prefer that than directing things to
    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
    Outlook für Android<> herunterladen
    From: Julian Feinauer <>
    Sent: Friday, February 22, 2019 9:38:48 AM
    Subject: Re: [DISCUSS] Send Jira emails to
    I agree with Chris... I would start with our dev@ list and monitor it and
    go over to a separate list when necessary.
    Am 22.02.19, 09:29 schrieb "Tim Mitsch" <>:
    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
    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)
    Von: Christofer Dutz <>
    Datum: Freitag, 22. Februar 2019 um 09:14
    An: "" <>, Tim Mitsch <>
    Betreff: Re: [DISCUSS] Send Jira emails to
    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?
    Outlook für Android<> herunterladen
    From: Otto Fowler <>
    Sent: Thursday, February 21, 2019 4:31:09 PM
    To:; Tim Mitsch
    Subject: Re: [DISCUSS] Send Jira emails to
    -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:
    setup or is it just dev@?
    On February 21, 2019 at 06:22:52, Tim Mitsch ( wrote:
    It would be good to be noticed.
    Am 21.02.19, 11:32 schrieb "Christofer Dutz" <>:
    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.

View raw message