Maybe we can separate the code-level discussion and high-level design
discussion. For cod-level discussion, we can use GitHub. For high-level design
discussion, we can use JIRA comments.
I think that makes perfect sense.
Another possibility is to send the GitHub comments to JIRA's worklog.
This would archive GitHub comments while keeping the JIRA comments clean.
Example: https://issues.apache.org/jira/browse/BEAM-5299
You can toggle between "All", "Comments", and "Work Log".
-Max
On 20.11.18 08:56, Joo Yeon Kim wrote:
Thanks Jangho for the quick action!
I agree with Taegeon about the separate usage of GitHub and JIRA comments.
Best,
Joo Yeon
On Tue, Nov 20, 2018 at 4:28 PM Taegeon Um <[email protected]> wrote:
Thanks Jangho!
I agree that we can archive the PR comments in JIRA, but I think attaching
the PR link to the JIRA issue is another archive of the PR discussion.
Some PRs have lots of comments and all comments are appended to the same
JIRA issue.
This makes it hard to parse comments only discussed in JIRA.
Maybe we can separate the code-level discussion and high-level design
discussion.
For cod-level discussion, we can use GitHub. For high-level design
discussion, we can use JIRA comments.
Any thoughts?
Thanks,
Taegeon
On 20 Nov 2018, at 3:29 PM, Jangho Seo <[email protected]> wrote:
Created a JIRA ticket at [1].
Speaking of Hudson comments, I do admit it makes no use for workflows
using GitHub. However I also think GitHub cannot be the 'canonical'
archive of discussions.
While GitBox provides seamless integration between GitHub and ASF code
repository, GitHub itself is not a part of the ASF infra. In this
perspective, forwarding discussions to JIRA makes sense to me.
Still, I want to listen more about it.
By the way, welcome to Nemo, Max!
[1] https://issues.apache.org/jira/browse/INFRA-17279
On 11/20/18 1:09 PM, Byung-Gon Chun wrote:
Jangho,
Could you open a ticket for disabling notification emails first?
We can talk more about Hudson comments meanwhile.
Best,
Gon
On Tue, Nov 20, 2018 at 12:37 PM Jangho Seo <[email protected]> wrote:
Thanks for the opinions.
+1 for disabling notification mails.
Should we open a ticket at INFRA?
Also, I'm okay with disabling Hudson comments at JIRA, although I want
to listen more about it.
Best,
Jangho
On 11/20/18 9:24 AM, Taegeon Um wrote:
Thanks for the suggestion Max!
+1 for disabling them.
I actually don't check Github notification emails :)
Also, we get lots of Gitbot/Hudson comments in JIRA when we open a PR
and
add comments on it [1].
What do you think about disabling the Gitbot/Hudson comments in JIRA?
or
maybe we can disable some JIRA comments (e.g., when we add comments
on a
PR)
Thanks,
Taegeon
[1]: https://issues.apache.org/jira/browse/NEMO-129
2018년 11월 20일 (화) 오전 7:23, Byung-Gon Chun <[email protected]>님이 작성:
Welcome to Nemo, Max!
Good suggestion. Sounds good to me.
Nemoers, we're having too many GitHub notifications. What do you
think
about moving GitHub notification emails to a separate mailing list or
disabling them?
-Gon
On Tue, Nov 20, 2018 at 5:28 AM Maximilian Michels <[email protected]>
wrote:
Hi everyone,
I just joined the mailing list. I'm curious to learn more about
Nemo!
:)
I'm seeing a lot of GitHub notification emails. Yes, I could filter
them
but do you think we could move those to a separate Github/JIRA
mailing
list?
At Apache Beam we even decided to completely disable them.
Cheers,
Max
--
Byung-Gon Chun
