incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luciano Resende <luckbr1...@gmail.com>
Subject Re: GitHub vs. the mailing lists
Date Wed, 18 May 2016 21:53:23 GMT
On Wed, May 18, 2016 at 1:59 PM, Christopher <ctubbsii@apache.org> wrote:

> On Wed, May 18, 2016 at 12:54 PM Jean-Baptiste Onofré <jb@nanthrax.net>
> wrote:
>
> > Hi Mike,
> >
> > it's what we are doing at Beam.
> >
> > A PR submission result:
> > - to a mail on the mailing list
> > - to a comment in Jira (if the PR contains commit with issue ID).
> >
> >
> The GitHub integration is very useful, as it tracks the GitHub PR activity
> on the mailing list, and optionally, JIRA (if an issue is referenced).
>
> For the JIRA integration, we recently added a few new options [1]:
>
> (default) - add link to PR on JIRA and comment on the JIRA
> "nofollow" - no JIRA integration (mailing only)
> "linkonly" - add link to PR on JIRA
> "worklog" - add link to PR on JIRA, but use worklog instead of comment
>
> The "worklog" is my preferred option because it reduces mailing list spam
> if JIRA is also configured to send email notifications for comments.
>
> [1]: https://issues.apache.org/jira/browse/INFRA-11675
>

I have seen multiple projects, having multiple different configuration,
probably based on the 4 items mentioned above. I would suggest we have one
recommended way where we would see more uniformity, and this recommended
way might suggest that some of these notifications are actually sent to
different lists (e.g. Spark actually has a review list where some of these
notification are sent https://www.mail-archive.com/reviews@spark.apache.org/,
Zeppelin track reviews as JIRA comments, etc), but would give us a central
place to track some of these technical discussions, rather then having to
go following the path from mailing list, to jira, to github, etc....


Thanks

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message