https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/RELENG-109 releng <p>As this takes off, if there are several people not just myself interested in maintaing this going forward, then we should perhaps at some point set up a human contact Bot email address - most logically just another <a href="https://lists.opendaylight.org" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org</a> I guess.</p> <p>To limit my own personal email load, I would much prefer <b>NOT</b> to send email FROM this address by the Bot - that's <a href="https://jira.opendaylight.org/browse/RELENG-108" title="From: email address for automated emails by The Bot: bot-noreply@opendaylight.org ?" class="issue-link" data-issue-key="RELENG-108">RELENG-108</a>. This 2nd address would just be mentioned somewhere in the body of automated template bulk emails, with wording like this:</p> <blockquote><p>If you would like to reach a human for any questions about this particular managed topic change, please do not reply to this email, but reach out to the Reporter of JIRA issue $mainJiraURL.</p> <p>If you would like to reach humans for technical issues with The Bot itself (only), then reach out to $bot-owner-email.</p></blockquote> RELENG-109

Bot mailing list as human contact: bot-owner? bot-dev?

Sub-task RELENG-101 Medium Open Unresolved Unassigned Michael Vorburger Thu, 3 May 2018 09:22:17 +0000 Fri, 4 May 2018 20:53:54 +0000 0 2 <p>We could use dev@lists.opendaylight.org it's the generic dev list so would work for this.</p> <p>Well, it depends on whether we can see the two roles being separated – i.e. split development and operations... I would opt for having both the same and use dev@ for now and see where it goes.</p> Development Rank 0|i03e5z: