You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iotdb.apache.org by Xiangdong Huang <sa...@gmail.com> on 2018/12/01 13:10:21 UTC
Using mail list or Issues management (e.g., Github, or JIRA) for
source code discussion?
Hi,
When we host our source codes on Github, we can use the `issues` pages to
manage all the issues -- not only the bugs, but also new features that we
want to implement. Then, when we submit a Pull Request, the PR can link a
corresponding issue easily.
But, as Apache says "if it didn't happen on-list, it didn't happen.", I
would like to know which type of discussions should appear in the mail
list, and when to use Github's issue management (or JIRA) is better?
By the way, I don't find any tool which can sync github's issues with mail
list automatically. :(
Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Re: Using mail list or Issues management (e.g., Github, or JIRA) forsource code discussion?
Posted by 吴晟 Sheng Wu <wu...@foxmail.com>.
Hi
There is no absolute way. In Apache, "if it didn't happen on-list, it didn't happen.". Definitely YES.
At the same time, you could choose to use GitHub issues to do bug report or feature discussions, like SkyWalking[1] did.
That is because, all issue comments are archived in mail list already, such as skywalking's notifications@s.a.o[2]
My point is, the community could choose. JIRA, GitHub issue or dev ml. My only suggestion is, don't use JIRA and GitHub issue at the same time,
to avoid confusing people.
Hypothesize your discussion in GitHub issue, dev ml is still needed, when you do release, you will need it. So if some important notification needs to be
shared in the community, you could choose both GitHub issue and dev ml.
[1] https://github.com/apache/incubator-skywalking/issues?q=is%3Aissue+label%3Aquestion+is%3Aclosed
[2] https://lists.apache.org/list.html?notifications@skywalking.apache.org
------------------
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108
------------------ Original ------------------
From: "Xiangdong Huang"<sa...@gmail.com>;
Date: Sat, Dec 1, 2018 09:10 PM
To: "dev"<de...@iotdb.apache.org>;
Subject: Using mail list or Issues management (e.g., Github, or JIRA) forsource code discussion?
Hi,
When we host our source codes on Github, we can use the `issues` pages to
manage all the issues -- not only the bugs, but also new features that we
want to implement. Then, when we submit a Pull Request, the PR can link a
corresponding issue easily.
But, as Apache says "if it didn't happen on-list, it didn't happen.", I
would like to know which type of discussions should appear in the mail
list, and when to use Github's issue management (or JIRA) is better?
By the way, I don't find any tool which can sync github's issues with mail
list automatically. :(
Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
AW: Using mail list or Issues management (e.g., Github, or JIRA) for
source code discussion?
Posted by Christofer Dutz <ch...@c-ware.de>.
Just some feedback from my side as we were having similar discussions on the PLC4X project.
The thing is, if technical discussions are held on GitHub, in PRs or in Jira, getting an overview of what's happening requires to register to all of these and to continuously monitor all of these systems.
Also did we try out the code reviews of GitHub and had these forwarded to the dev list. This resulted in mornings with 100 new emails because every single comment to every single line of a PR resulted in a separate Email (not quite what we wanted).
So now we're discussing technical things where people should be involved on the dev-list and implementation specific stuff we think is not worth wasting the other project members time in PRs and Jira issues.
Chris
Am 03.12.18, 12:59 schrieb "Xiangdong Huang" <sa...@gmail.com>:
Hi,
Thanks for the information.
I think the two suggestions are good:
1. Move discussions about big PR or design details to the dev list:
> If a PR is a big change, or if discussion veers into into design details
rather than just code, we expect our committers to say "let's move this to
the dev list".
2. a weekly or monthly report for reporting how many PR or issues are
resolved is useful.
I think we can try like this for a while to see whether it is useful :D
Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Bertrand Delacretaz <bd...@apache.org> 于2018年12月3日周一 下午5:45写道：
> Hi Kevin,
>
> On Sat, Dec 1, 2018 at 6:32 PM Kevin A. McGrail <km...@apache.org>
> wrote:
> > Bertrand, wasn't this issue discussed recently?...
>
> There was this "Discussions in pull requests vs. dev list" thread on
> comdev, which might help.
>
>
> https://lists.apache.org/thread.html/a90d871d7e8637b7ed566bcc5f06a9920b480097647d1b70424fce1e@%3Cdev.community.apache.org%3E
>
> -Bertrand
>
Re: Using mail list or Issues management (e.g., Github, or JIRA) for
source code discussion?
Posted by Xiangdong Huang <sa...@gmail.com>.
Hi,
Thanks for the information.
I think the two suggestions are good:
1. Move discussions about big PR or design details to the dev list:
> If a PR is a big change, or if discussion veers into into design details
rather than just code, we expect our committers to say "let's move this to
the dev list".
2. a weekly or monthly report for reporting how many PR or issues are
resolved is useful.
I think we can try like this for a while to see whether it is useful :D
Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Bertrand Delacretaz <bd...@apache.org> 于2018年12月3日周一 下午5:45写道：
> Hi Kevin,
>
> On Sat, Dec 1, 2018 at 6:32 PM Kevin A. McGrail <km...@apache.org>
> wrote:
> > Bertrand, wasn't this issue discussed recently?...
>
> There was this "Discussions in pull requests vs. dev list" thread on
> comdev, which might help.
>
>
> https://lists.apache.org/thread.html/a90d871d7e8637b7ed566bcc5f06a9920b480097647d1b70424fce1e@%3Cdev.community.apache.org%3E
>
> -Bertrand
>
Re: Using mail list or Issues management (e.g., Github, or JIRA) for
source code discussion?
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Kevin,
On Sat, Dec 1, 2018 at 6:32 PM Kevin A. McGrail <km...@apache.org> wrote:
> Bertrand, wasn't this issue discussed recently?...
There was this "Discussions in pull requests vs. dev list" thread on
comdev, which might help.
https://lists.apache.org/thread.html/a90d871d7e8637b7ed566bcc5f06a9920b480097647d1b70424fce1e@%3Cdev.community.apache.org%3E
-Bertrand
Re: Using mail list or Issues management (e.g., Github, or JIRA) for
source code discussion?
Posted by "Kevin A. McGrail" <km...@apache.org>.
Bertrand, wasn't this issue discussed recently? Do you remember and
where it might have been documented so IoTDB can look to mimic?
Regards,
KAM
On 12/1/2018 8:10 AM, Xiangdong Huang wrote:
> Hi,
>
> When we host our source codes on Github, we can use the `issues` pages to
> manage all the issues -- not only the bugs, but also new features that we
> want to implement. Then, when we submit a Pull Request, the PR can link a
> corresponding issue easily.
>
> But, as Apache says "if it didn't happen on-list, it didn't happen.", I
> would like to know which type of discussions should appear in the mail
> list, and when to use Github's issue management (or JIRA) is better?
>
> By the way, I don't find any tool which can sync github's issues with mail
> list automatically. :(
>
> Best,
> -----------------------------------
> Xiangdong Huang
> School of Software, Tsinghua University
>
> 黄向东
> 清华大学 软件学院
>
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171