You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by Hezheng Yin <yi...@gmail.com> on 2022/05/25 04:26:33 UTC

When to use dev@ mailing list vs GitHub Issues

Dear Mentors and Community Members,

I'd like to seek your guidance regarding the usage of dev@ mailing list and
GitHub Issues. As the famous motto goes, "If it didn't happen on a mailing
list, it didn't happen." The ASF requires all communications related to
code and decision-making to happen on the project's mailing lists.

While we're steering our committers to use dev@ mailing list more often,
most users will continue to file issues on GitHub to report bugs or
request features. And follow-up discussions with those users will happen
naturally on GitHub.

Would this violate the Apache way of communicating via mailing lists? Are
there any best practices for balancing the usage of dev@ mailing list and
GitHub Issues? Your advice would be greatly appreciated.

Best,
Hezheng

Re: When to use dev@ mailing list vs GitHub Issues

Posted by Willem Jiang <wi...@gmail.com>.
When we work in public, we need to make sure we keep all the
information in public.
Using a mailing list or Github issue gives us a chance to speak in
public and the audience can follow us up by diving into the discussion
thread at any time and from anywhere.
Currently we are encouraging our developer to use the dev mailing list
and we can reference the discussion with the url of the mailing list
in the github issue.
At the same time, the dev mailing list can reference the github issue link.

Just my 2 cents.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 25, 2022 at 12:27 PM Hezheng Yin <yi...@gmail.com> wrote:
>
> Dear Mentors and Community Members,
>
> I'd like to seek your guidance regarding the usage of dev@ mailing list and
> GitHub Issues. As the famous motto goes, "If it didn't happen on a mailing
> list, it didn't happen." The ASF requires all communications related to
> code and decision-making to happen on the project's mailing lists.
>
> While we're steering our committers to use dev@ mailing list more often,
> most users will continue to file issues on GitHub to report bugs or
> request features. And follow-up discussions with those users will happen
> naturally on GitHub.
>
> Would this violate the Apache way of communicating via mailing lists? Are
> there any best practices for balancing the usage of dev@ mailing list and
> GitHub Issues? Your advice would be greatly appreciated.
>
> Best,
> Hezheng

Re: When to use dev@ mailing list vs GitHub Issues

Posted by Willem Jiang <wi...@gmail.com>.
When ASF projects switch the github, the github issues are synced to
the ASF mailing list (notification@project.a.o) as a backup.
We use this link
(https://lists.apache.org/thread/ofsn31h187x8g2gxtv306wsjz7c6yd65) to
avoid duplicates of the information.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, May 26, 2022 at 4:51 AM Hezheng Yin <yi...@gmail.com> wrote:
>
> Hi Jinglei,
>
> For committers and contributors who are familiar with the Apache ecosystem,
> they would have no problem executing the workflow you proposed.
>
> This is more of a problem when users interact with DevLake by creating
> issues on GitHub. Some discussions between users and developers will happen
> in GitHub issues naturally. One way to ensure that the mailing list is our
> "single source of truth" is to duplicate any important information from
> those GitHub issues to dev@ mailing list afterward. Is this a common
> practice that other Apache projects adopt?
>
> Best,
> Hezheng
>
>
> On Tue, May 24, 2022 at 10:44 PM Jinglei Ren <ji...@merico.dev.invalid>
> wrote:
>
> > A sad fact is that many developers from certain areas of the world cannot
> > access the GitHub platform now (but cloning a public repo should be viable,
> > at least through VPNs). While mailing lists are old-school, I really
> > appreciate Apache’s wisdom – mailing lists are still the most widely
> > available and robust communication channel. We should welcome contributions
> > from developers who have only 10kbps network or experiene wars or disagree
> > with what their government is doing.
> >
> > So, I personally support having most technical discussions in this mailing
> > list (ML). Once any specific task is determined out of the discussion, it
> > could be converted to an issue or divided into issues on GitHub. Meanwhile,
> > I think we should keep the option for a developer to send a patch to this
> > mailing list as a way to submit code. Overall, the pipeline may go like
> > this:
> >
> > Critical discussions on ML ----> GitHub: Issues & issue-specific
> > discussions & the PR workflow
> >                              |
> >                             --> ML: Patches & patch-specific discussions &
> > the patching workflow
> >
> > The leftmost discussions on ML are general and most widely accessible.
> > Then the branch is a local choice of a small group of the (potential)
> > developers of a task. I think it is a good balance between most developers’
> > convenience and a baseline guarantee of everyone’s ability to participate.
> >
> > Thanks,
> > Jinglei
> >
> > From: Hezheng Yin <yi...@gmail.com>
> > Date: Wednesday, May 25, 2022 at 12:27 PM
> > To: dev@devlake.apache.org <de...@devlake.apache.org>
> > Subject: When to use dev@ mailing list vs GitHub Issues
> > Dear Mentors and Community Members,
> >
> > I'd like to seek your guidance regarding the usage of dev@ mailing list
> > and
> > GitHub Issues. As the famous motto goes, "If it didn't happen on a mailing
> > list, it didn't happen." The ASF requires all communications related to
> > code and decision-making to happen on the project's mailing lists.
> >
> > While we're steering our committers to use dev@ mailing list more often,
> > most users will continue to file issues on GitHub to report bugs or
> > request features. And follow-up discussions with those users will happen
> > naturally on GitHub.
> >
> > Would this violate the Apache way of communicating via mailing lists? Are
> > there any best practices for balancing the usage of dev@ mailing list and
> > GitHub Issues? Your advice would be greatly appreciated.
> >
> > Best,
> > Hezheng
> >

Re: When to use dev@ mailing list vs GitHub Issues

Posted by Hezheng Yin <yi...@gmail.com>.
Hi Jinglei,

For committers and contributors who are familiar with the Apache ecosystem,
they would have no problem executing the workflow you proposed.

This is more of a problem when users interact with DevLake by creating
issues on GitHub. Some discussions between users and developers will happen
in GitHub issues naturally. One way to ensure that the mailing list is our
"single source of truth" is to duplicate any important information from
those GitHub issues to dev@ mailing list afterward. Is this a common
practice that other Apache projects adopt?

Best,
Hezheng


On Tue, May 24, 2022 at 10:44 PM Jinglei Ren <ji...@merico.dev.invalid>
wrote:

> A sad fact is that many developers from certain areas of the world cannot
> access the GitHub platform now (but cloning a public repo should be viable,
> at least through VPNs). While mailing lists are old-school, I really
> appreciate Apache’s wisdom – mailing lists are still the most widely
> available and robust communication channel. We should welcome contributions
> from developers who have only 10kbps network or experiene wars or disagree
> with what their government is doing.
>
> So, I personally support having most technical discussions in this mailing
> list (ML). Once any specific task is determined out of the discussion, it
> could be converted to an issue or divided into issues on GitHub. Meanwhile,
> I think we should keep the option for a developer to send a patch to this
> mailing list as a way to submit code. Overall, the pipeline may go like
> this:
>
> Critical discussions on ML ----> GitHub: Issues & issue-specific
> discussions & the PR workflow
>                              |
>                             --> ML: Patches & patch-specific discussions &
> the patching workflow
>
> The leftmost discussions on ML are general and most widely accessible.
> Then the branch is a local choice of a small group of the (potential)
> developers of a task. I think it is a good balance between most developers’
> convenience and a baseline guarantee of everyone’s ability to participate.
>
> Thanks,
> Jinglei
>
> From: Hezheng Yin <yi...@gmail.com>
> Date: Wednesday, May 25, 2022 at 12:27 PM
> To: dev@devlake.apache.org <de...@devlake.apache.org>
> Subject: When to use dev@ mailing list vs GitHub Issues
> Dear Mentors and Community Members,
>
> I'd like to seek your guidance regarding the usage of dev@ mailing list
> and
> GitHub Issues. As the famous motto goes, "If it didn't happen on a mailing
> list, it didn't happen." The ASF requires all communications related to
> code and decision-making to happen on the project's mailing lists.
>
> While we're steering our committers to use dev@ mailing list more often,
> most users will continue to file issues on GitHub to report bugs or
> request features. And follow-up discussions with those users will happen
> naturally on GitHub.
>
> Would this violate the Apache way of communicating via mailing lists? Are
> there any best practices for balancing the usage of dev@ mailing list and
> GitHub Issues? Your advice would be greatly appreciated.
>
> Best,
> Hezheng
>

Re: When to use dev@ mailing list vs GitHub Issues

Posted by Jinglei Ren <ji...@merico.dev.INVALID>.
A sad fact is that many developers from certain areas of the world cannot access the GitHub platform now (but cloning a public repo should be viable, at least through VPNs). While mailing lists are old-school, I really appreciate Apache’s wisdom – mailing lists are still the most widely available and robust communication channel. We should welcome contributions from developers who have only 10kbps network or experiene wars or disagree with what their government is doing.

So, I personally support having most technical discussions in this mailing list (ML). Once any specific task is determined out of the discussion, it could be converted to an issue or divided into issues on GitHub. Meanwhile, I think we should keep the option for a developer to send a patch to this mailing list as a way to submit code. Overall, the pipeline may go like this:

Critical discussions on ML ----> GitHub: Issues & issue-specific discussions & the PR workflow
                             |
                            --> ML: Patches & patch-specific discussions & the patching workflow

The leftmost discussions on ML are general and most widely accessible. Then the branch is a local choice of a small group of the (potential) developers of a task. I think it is a good balance between most developers’ convenience and a baseline guarantee of everyone’s ability to participate.

Thanks,
Jinglei

From: Hezheng Yin <yi...@gmail.com>
Date: Wednesday, May 25, 2022 at 12:27 PM
To: dev@devlake.apache.org <de...@devlake.apache.org>
Subject: When to use dev@ mailing list vs GitHub Issues
Dear Mentors and Community Members,

I'd like to seek your guidance regarding the usage of dev@ mailing list and
GitHub Issues. As the famous motto goes, "If it didn't happen on a mailing
list, it didn't happen." The ASF requires all communications related to
code and decision-making to happen on the project's mailing lists.

While we're steering our committers to use dev@ mailing list more often,
most users will continue to file issues on GitHub to report bugs or
request features. And follow-up discussions with those users will happen
naturally on GitHub.

Would this violate the Apache way of communicating via mailing lists? Are
there any best practices for balancing the usage of dev@ mailing list and
GitHub Issues? Your advice would be greatly appreciated.

Best,
Hezheng