You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Yu <li...@apache.org> on 2022/04/21 09:00:32 UTC
Enable GitHub Discussions?
Hi Pulsarers,
Recently, we've found that many open source communities use GitHub
Discussions to facilitate effective communication, such as users can ask
questions, share ideas, and build connections with each other easily [1].
GitHub Discussions is designed to:
- Provide centralized community space for conversations and questions (and
make the lives of maintainers easier when it comes to issues and pull
requests).
- Create a place for newcomers and non-code collaborators to participate in
a larger community.
- Highlight project contributors to help develop the next generation of
maintainers.
And it is different from GitHub Issue by providing more functions for
conversations, questions, and community engagement. You can check all
details here [2].
~~~~~~~~~~~~~~~~
Do we want to enable the GitHub Discussions in Pulsar?
Feel free to comment, thank you!
[1]
https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
[2] https://resources.github.com/devops/process/planning/discussions/
Anonymitaet
Re: Enable GitHub Discussions?
Posted by tison <wa...@gmail.com>.
If we can bring GitHub Discussions threads to dev@ or users@ (by
categorized), it won't affect workflow based on mailing list.
Basically, you can discuss via GitHub Discussion by emails.
Best,
tison.
Dianjin Wang <dj...@streamnative.io.invalid> 于2022年4月21日周四 21:43写道：
> Agreed with @Enrico. If enabling the GitHub discussions, it's confusing for
> community members to recognize issues or discussions. If too many
> platforms, it's also hard for people to be focused.
>
> Best,
> Dianjin Wang
>
>
> On Thu, Apr 21, 2022 at 8:49 PM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > I believe that we should stick as much as possible to the mailing
> > list, this is the common way of running the community in the ASF.
> >
> > We already have a Slack space that is hard to follow.
> >
> > Enrico
> >
> > Il giorno gio 21 apr 2022 alle ore 14:47 tison <wa...@gmail.com>
> > ha scritto:
> > >
> > > You can ask for ASF INFRA to see whether there is a way to bring all
> > activities of GitHub Discussion to a mailing list. Just like development
> > activities to commits@.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
> > >>
> > >>
> > >> If/when GitHub disappears, will the community suffer from missing
> > >> information? If so, need to solve the "back to ASF"-path, so it isn't
> > >> lost.
> > >>
> > >> Niclas
> > >>
> > >> On 2022-04-21 11:00, Yu wrote:
> > >> > Hi Pulsarers,
> > >> >
> > >> > Recently, we've found that many open source communities use GitHub
> > >> > Discussions to facilitate effective communication, such as users can
> > >> > ask questions, share ideas, and build connections with each other
> > >> > easily [1].
> > >> >
> > >> > GitHub Discussions is designed to:
> > >> >
> > >> > - Provide centralized community space for conversations and
> questions
> > >> > (and make the lives of maintainers easier when it comes to issues
> and
> > >> > pull requests).
> > >> >
> > >> > - Create a place for newcomers and non-code collaborators to
> > >> > participate in a larger community.
> > >> >
> > >> > - Highlight project contributors to help develop the next generation
> > >> > of maintainers.
> > >> >
> > >> > And it is different from GitHub Issue by providing more functions
> for
> > >> > conversations, questions, and community engagement. You can check
> all
> > >> > details here [2].
> > >> >
> > >> > ~~~~~~~~~~~~~~~~
> > >> >
> > >> > Do we want to enable the GitHub Discussions in Pulsar?
> > >> >
> > >> > Feel free to comment, thank you!
> > >> >
> > >> > [1]
> > >> >
> >
> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
> > >> > [2]
> https://resources.github.com/devops/process/planning/discussions/
> > >> >
> > >> > Anonymitaet
> >
>
Re: Enable GitHub Discussions?
Posted by tison <wa...@gmail.com>.
If we can bring GitHub Discussions threads to dev@ or users@ (by
categorized), it won't affect workflow based on mailing list.
Basically, you can discuss via GitHub Discussion by emails.
Best,
tison.
Dianjin Wang <dj...@streamnative.io.invalid> 于2022年4月21日周四 21:43写道：
> Agreed with @Enrico. If enabling the GitHub discussions, it's confusing for
> community members to recognize issues or discussions. If too many
> platforms, it's also hard for people to be focused.
>
> Best,
> Dianjin Wang
>
>
> On Thu, Apr 21, 2022 at 8:49 PM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > I believe that we should stick as much as possible to the mailing
> > list, this is the common way of running the community in the ASF.
> >
> > We already have a Slack space that is hard to follow.
> >
> > Enrico
> >
> > Il giorno gio 21 apr 2022 alle ore 14:47 tison <wa...@gmail.com>
> > ha scritto:
> > >
> > > You can ask for ASF INFRA to see whether there is a way to bring all
> > activities of GitHub Discussion to a mailing list. Just like development
> > activities to commits@.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
> > >>
> > >>
> > >> If/when GitHub disappears, will the community suffer from missing
> > >> information? If so, need to solve the "back to ASF"-path, so it isn't
> > >> lost.
> > >>
> > >> Niclas
> > >>
> > >> On 2022-04-21 11:00, Yu wrote:
> > >> > Hi Pulsarers,
> > >> >
> > >> > Recently, we've found that many open source communities use GitHub
> > >> > Discussions to facilitate effective communication, such as users can
> > >> > ask questions, share ideas, and build connections with each other
> > >> > easily [1].
> > >> >
> > >> > GitHub Discussions is designed to:
> > >> >
> > >> > - Provide centralized community space for conversations and
> questions
> > >> > (and make the lives of maintainers easier when it comes to issues
> and
> > >> > pull requests).
> > >> >
> > >> > - Create a place for newcomers and non-code collaborators to
> > >> > participate in a larger community.
> > >> >
> > >> > - Highlight project contributors to help develop the next generation
> > >> > of maintainers.
> > >> >
> > >> > And it is different from GitHub Issue by providing more functions
> for
> > >> > conversations, questions, and community engagement. You can check
> all
> > >> > details here [2].
> > >> >
> > >> > ~~~~~~~~~~~~~~~~
> > >> >
> > >> > Do we want to enable the GitHub Discussions in Pulsar?
> > >> >
> > >> > Feel free to comment, thank you!
> > >> >
> > >> > [1]
> > >> >
> >
> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
> > >> > [2]
> https://resources.github.com/devops/process/planning/discussions/
> > >> >
> > >> > Anonymitaet
> >
>
Re: Enable GitHub Discussions?
Posted by Dianjin Wang <dj...@streamnative.io>.
Agreed with @Enrico. If enabling the GitHub discussions, it's confusing for
community members to recognize issues or discussions. If too many
platforms, it's also hard for people to be focused.
Best,
Dianjin Wang
On Thu, Apr 21, 2022 at 8:49 PM Enrico Olivelli <eo...@gmail.com> wrote:
> I believe that we should stick as much as possible to the mailing
> list, this is the common way of running the community in the ASF.
>
> We already have a Slack space that is hard to follow.
>
> Enrico
>
> Il giorno gio 21 apr 2022 alle ore 14:47 tison <wa...@gmail.com>
> ha scritto:
> >
> > You can ask for ASF INFRA to see whether there is a way to bring all
> activities of GitHub Discussion to a mailing list. Just like development
> activities to commits@.
> >
> > Best,
> > tison.
> >
> >
> > Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
> >>
> >>
> >> If/when GitHub disappears, will the community suffer from missing
> >> information? If so, need to solve the "back to ASF"-path, so it isn't
> >> lost.
> >>
> >> Niclas
> >>
> >> On 2022-04-21 11:00, Yu wrote:
> >> > Hi Pulsarers,
> >> >
> >> > Recently, we've found that many open source communities use GitHub
> >> > Discussions to facilitate effective communication, such as users can
> >> > ask questions, share ideas, and build connections with each other
> >> > easily [1].
> >> >
> >> > GitHub Discussions is designed to:
> >> >
> >> > - Provide centralized community space for conversations and questions
> >> > (and make the lives of maintainers easier when it comes to issues and
> >> > pull requests).
> >> >
> >> > - Create a place for newcomers and non-code collaborators to
> >> > participate in a larger community.
> >> >
> >> > - Highlight project contributors to help develop the next generation
> >> > of maintainers.
> >> >
> >> > And it is different from GitHub Issue by providing more functions for
> >> > conversations, questions, and community engagement. You can check all
> >> > details here [2].
> >> >
> >> > ~~~~~~~~~~~~~~~~
> >> >
> >> > Do we want to enable the GitHub Discussions in Pulsar?
> >> >
> >> > Feel free to comment, thank you!
> >> >
> >> > [1]
> >> >
> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
> >> > [2] https://resources.github.com/devops/process/planning/discussions/
> >> >
> >> > Anonymitaet
>
Re: Enable GitHub Discussions?
Posted by Dianjin Wang <dj...@streamnative.io.INVALID>.
Agreed with @Enrico. If enabling the GitHub discussions, it's confusing for
community members to recognize issues or discussions. If too many
platforms, it's also hard for people to be focused.
Best,
Dianjin Wang
On Thu, Apr 21, 2022 at 8:49 PM Enrico Olivelli <eo...@gmail.com> wrote:
> I believe that we should stick as much as possible to the mailing
> list, this is the common way of running the community in the ASF.
>
> We already have a Slack space that is hard to follow.
>
> Enrico
>
> Il giorno gio 21 apr 2022 alle ore 14:47 tison <wa...@gmail.com>
> ha scritto:
> >
> > You can ask for ASF INFRA to see whether there is a way to bring all
> activities of GitHub Discussion to a mailing list. Just like development
> activities to commits@.
> >
> > Best,
> > tison.
> >
> >
> > Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
> >>
> >>
> >> If/when GitHub disappears, will the community suffer from missing
> >> information? If so, need to solve the "back to ASF"-path, so it isn't
> >> lost.
> >>
> >> Niclas
> >>
> >> On 2022-04-21 11:00, Yu wrote:
> >> > Hi Pulsarers,
> >> >
> >> > Recently, we've found that many open source communities use GitHub
> >> > Discussions to facilitate effective communication, such as users can
> >> > ask questions, share ideas, and build connections with each other
> >> > easily [1].
> >> >
> >> > GitHub Discussions is designed to:
> >> >
> >> > - Provide centralized community space for conversations and questions
> >> > (and make the lives of maintainers easier when it comes to issues and
> >> > pull requests).
> >> >
> >> > - Create a place for newcomers and non-code collaborators to
> >> > participate in a larger community.
> >> >
> >> > - Highlight project contributors to help develop the next generation
> >> > of maintainers.
> >> >
> >> > And it is different from GitHub Issue by providing more functions for
> >> > conversations, questions, and community engagement. You can check all
> >> > details here [2].
> >> >
> >> > ~~~~~~~~~~~~~~~~
> >> >
> >> > Do we want to enable the GitHub Discussions in Pulsar?
> >> >
> >> > Feel free to comment, thank you!
> >> >
> >> > [1]
> >> >
> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
> >> > [2] https://resources.github.com/devops/process/planning/discussions/
> >> >
> >> > Anonymitaet
>
Re: Enable GitHub Discussions?
Posted by Enrico Olivelli <eo...@gmail.com>.
I believe that we should stick as much as possible to the mailing
list, this is the common way of running the community in the ASF.
We already have a Slack space that is hard to follow.
Enrico
Il giorno gio 21 apr 2022 alle ore 14:47 tison <wa...@gmail.com>
ha scritto:
>
> You can ask for ASF INFRA to see whether there is a way to bring all activities of GitHub Discussion to a mailing list. Just like development activities to commits@.
>
> Best,
> tison.
>
>
> Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
>>
>>
>> If/when GitHub disappears, will the community suffer from missing
>> information? If so, need to solve the "back to ASF"-path, so it isn't
>> lost.
>>
>> Niclas
>>
>> On 2022-04-21 11:00, Yu wrote:
>> > Hi Pulsarers,
>> >
>> > Recently, we've found that many open source communities use GitHub
>> > Discussions to facilitate effective communication, such as users can
>> > ask questions, share ideas, and build connections with each other
>> > easily [1].
>> >
>> > GitHub Discussions is designed to:
>> >
>> > - Provide centralized community space for conversations and questions
>> > (and make the lives of maintainers easier when it comes to issues and
>> > pull requests).
>> >
>> > - Create a place for newcomers and non-code collaborators to
>> > participate in a larger community.
>> >
>> > - Highlight project contributors to help develop the next generation
>> > of maintainers.
>> >
>> > And it is different from GitHub Issue by providing more functions for
>> > conversations, questions, and community engagement. You can check all
>> > details here [2].
>> >
>> > ~~~~~~~~~~~~~~~~
>> >
>> > Do we want to enable the GitHub Discussions in Pulsar?
>> >
>> > Feel free to comment, thank you!
>> >
>> > [1]
>> > https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
>> > [2] https://resources.github.com/devops/process/planning/discussions/
>> >
>> > Anonymitaet
Re: Enable GitHub Discussions?
Posted by Enrico Olivelli <eo...@gmail.com>.
I believe that we should stick as much as possible to the mailing
list, this is the common way of running the community in the ASF.
We already have a Slack space that is hard to follow.
Enrico
Il giorno gio 21 apr 2022 alle ore 14:47 tison <wa...@gmail.com>
ha scritto:
>
> You can ask for ASF INFRA to see whether there is a way to bring all activities of GitHub Discussion to a mailing list. Just like development activities to commits@.
>
> Best,
> tison.
>
>
> Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
>>
>>
>> If/when GitHub disappears, will the community suffer from missing
>> information? If so, need to solve the "back to ASF"-path, so it isn't
>> lost.
>>
>> Niclas
>>
>> On 2022-04-21 11:00, Yu wrote:
>> > Hi Pulsarers,
>> >
>> > Recently, we've found that many open source communities use GitHub
>> > Discussions to facilitate effective communication, such as users can
>> > ask questions, share ideas, and build connections with each other
>> > easily [1].
>> >
>> > GitHub Discussions is designed to:
>> >
>> > - Provide centralized community space for conversations and questions
>> > (and make the lives of maintainers easier when it comes to issues and
>> > pull requests).
>> >
>> > - Create a place for newcomers and non-code collaborators to
>> > participate in a larger community.
>> >
>> > - Highlight project contributors to help develop the next generation
>> > of maintainers.
>> >
>> > And it is different from GitHub Issue by providing more functions for
>> > conversations, questions, and community engagement. You can check all
>> > details here [2].
>> >
>> > ~~~~~~~~~~~~~~~~
>> >
>> > Do we want to enable the GitHub Discussions in Pulsar?
>> >
>> > Feel free to comment, thank you!
>> >
>> > [1]
>> > https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
>> > [2] https://resources.github.com/devops/process/planning/discussions/
>> >
>> > Anonymitaet
Re: Enable GitHub Discussions?
Posted by Niclas Hedhman <ni...@hedhman.org>.
On 2022-04-25 12:34, Yu wrote:
>> Another important part of The Apache Way is to make decisions by
>> reaching
> consensus (and avoiding votes).
>
> But the Apache Website says "one of the fundamental aspects of
> accomplishing things within the Apache framework is doing so by
> consensus,
> we need a way to tell whether we have reached consensus. We do this by
> voting." [1] — which means we make decisions by voting, correct?
>
> [1] https://www.apache.org/foundation/voting.html
Not necessarily... Many communities use "Lazy Consensus", meaning "I
will do this..." announcement (or even "I have done this...") and go
ahead with it UNLESS someone raises a concern. This typically works
well, if the community is reasonably well-aligned with the vision and
path forward.
Niclas
Re: Enable GitHub Discussions?
Posted by Yu <li...@apache.org>.
Hi Dave,
Thanks for your suggestions!
1. Using GitHub Discussions does not mean abandoning Google Docs, we can
use both and leverage both advantages.
2. One question on this:
> Another important part of The Apache Way is to make decisions by reaching
consensus (and avoiding votes).
But the Apache Website says "one of the fundamental aspects of
accomplishing things within the Apache framework is doing so by consensus,
we need a way to tell whether we have reached consensus. We do this by
voting." [1] — which means we make decisions by voting, correct?
[1] https://www.apache.org/foundation/voting.html
On Fri, Apr 22, 2022 at 11:00 PM Dave Fisher <wa...@apache.org> wrote:
> Hi Yu,
>
> > On Apr 21, 2022, at 11:46 PM, Yu <li...@apache.org> wrote:
> >
> > Thanks all!
> >
> > I understand that we need to follow the Apache way (If it didn’t happen
> on
> > the mailing list, it didn’t happen) to *make final decisions*, but we can
> > find a better place to *discuss issues and reuse information effectively*
> > [1].
>
> Another important part of The Apache Way is to make decisions by reaching
> consensus (and avoiding votes). [3]
>
> This discussion is not finished and this should not be a call to a vote.
> When a VOTE is called it must be clear and not buried at the bottom of a
> long email.
>
> The project has been using Google Docs for collaboration. Is the real
> motivation to use GitHub Discussions instead of Google Docs?
>
> >
> > ~~~~~~~~
> >
> > # Current issues
> >
> > We have a lot of work in various places, but the information is not
> > organized and reused effectively.
> >
> > ## Slack
> > - Information is not publicly accessible. You need to upgrade to paid
> plans
> > or else you can see just the 10,000 most recent messages.
> > - Information is scattered and not categorized.
>
> The Pulsar slack has existed since the beginning of the project. We have
> 6688 subscribers to the #general and that is great.
>
> >
> > # StackOveflow
> > - Inactive. Only 24 results after searching "apachepulsar".
>
> When I search “pulsar” I get over 500 results. This is an active channel.
> It’s a place where developers go.
>
> >
> > # Mailing List
> > - Information is scattered and not categorized.
> > - User experience is terrible. Plain text format decreases email
> > readability. Search function is hard to use.
>
> The search function at lists.apache.org is hard to use, but it is
> powerful. In other projects I’ve searched for and found email from 15 years
> ago. The new monthly calendar is very powerful.
>
> If we use GitHub Discussions then the discussion of the decision won’t be
> on the mailing list. People will write emails with links to the GitHub
> Discussions. These links will eventually get stale.
>
> If you want to improve lists.apache.org then you can influence that here:
> dev@ponymail.apache.org. Pony Mail is an Apache Incubator podling.
>
>
> >
> > ~~~~~~~~
> >
> > # Why try GitHub Discussions?
>
> >
> > Compared with the platforms above and GitHub Issue, GitHub Discussions
> make
> > collaboration more efficient by:
> >
> > # Making it easier to categorize, archive, and search information
> > - It has categories (Announcements, General, Ideas, Polls, Q&A, Show and
> > Tell, etc) and labels to categorize and filter information quickly.
> > - Information is permanently saved.
> > - Search is easy to use.
> >
> > # Providing a centralized community space for conversations and questions
> > - As instructed by GitHub, we can use GitHub Discussions to *discuss
> > things*, and use GitHub Issues to *catalog the work* we need to do after
> > we’ve reached a decision about how to move forward.
> >
> > # Boosting community engagement and encouraging people to make
> contributions
> > - It highlights project contributors and shows Most Helpful Ranking of
> > Contributors.
> > - It creates a place for newcomers and non-code collaborators to
> > participate in a larger community.
> >
> > # Calling users' attention to important issues or events
> > - Important discussions can be pinned to home pages for easy reference.
> >
> > ~~~~~~~~
> >
> > Feel free to share your thoughts. This vote will be open for 72 hrs.
>
> We are not ready to vote. While it might be good to do I cannot agree with
> all of your reasoning. If forced to vote then I am -1.
>
> I might agree to GitHub Discussions as a replacement for GoogleDocs.
>
> We have no power to move users away from StackOverflow. A huge number
> follow Pulsar on Slack. If it’s a matter of paying for a plan then perhaps
> there is a way. The PMC should discuss that.
>
> All The Best,
> Dave
>
> [3] http://theapacheway.com/consensus/
>
> >
> > Then we can ask Infra to do the needed GitHub Admin tasks if we reach a
> > consensus on enabling it, thank you!
> >
> > [1] http://theapacheway.com/on-list/
> >
> > Anonymitaet
> >
> > On Fri, Apr 22, 2022 at 2:34 AM Dave Fisher <wa...@apache.org> wrote:
> >
> >> I asked Infra. GitHub Discussions are not synchronized into ASF
> >> Infrastructure's GitBox. That means that there is not ability to change
> the
> >> notification scheme to send to a mailing list.
> >>
> >> Technically we can go down this path only if it is possible to set a
> >> notification within GitHub. You would need to look into that and if we
> >> decided to go forward we can ask Infra to do the needed GitHub Admin
> tasks.
> >>
> >> Community wise I agree with others that we are already splitting a lot
> of
> >> work into various places.
> >>
> >> Regards,
> >> Dave
> >>
> >> On Apr 21, 2022, at 5:47 AM, tison <wa...@gmail.com> wrote:
> >>
> >> You can ask for ASF INFRA to see whether there is a way to bring all
> >> activities of GitHub Discussion to a mailing list. Just like development
> >> activities to commits@.
> >>
> >> Best,
> >> tison.
> >>
> >>
> >> Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
> >>
> >>>
> >>> If/when GitHub disappears, will the community suffer from missing
> >>> information? If so, need to solve the "back to ASF"-path, so it isn't
> >>> lost.
> >>>
> >>> Niclas
> >>>
> >>> On 2022-04-21 11:00, Yu wrote:
> >>>> Hi Pulsarers,
> >>>>
> >>>> Recently, we've found that many open source communities use GitHub
> >>>> Discussions to facilitate effective communication, such as users can
> >>>> ask questions, share ideas, and build connections with each other
> >>>> easily [1].
> >>>>
> >>>> GitHub Discussions is designed to:
> >>>>
> >>>> - Provide centralized community space for conversations and questions
> >>>> (and make the lives of maintainers easier when it comes to issues and
> >>>> pull requests).
> >>>>
> >>>> - Create a place for newcomers and non-code collaborators to
> >>>> participate in a larger community.
> >>>>
> >>>> - Highlight project contributors to help develop the next generation
> >>>> of maintainers.
> >>>>
> >>>> And it is different from GitHub Issue by providing more functions for
> >>>> conversations, questions, and community engagement. You can check all
> >>>> details here [2].
> >>>>
> >>>> ~~~~~~~~~~~~~~~~
> >>>>
> >>>> Do we want to enable the GitHub Discussions in Pulsar?
> >>>>
> >>>> Feel free to comment, thank you!
> >>>>
> >>>> [1]
> >>>>
> >>>
> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
> >>>> [2] https://resources.github.com/devops/process/planning/discussions/
> >>>>
> >>>> Anonymitaet
> >>>
> >>
> >>
>
>
Re: Enable GitHub Discussions?
Posted by Yu <li...@apache.org>.
Hi Dave,
Thanks for your suggestions!
1. Using GitHub Discussions does not mean abandoning Google Docs, we can
use both and leverage both advantages.
2. One question on this:
> Another important part of The Apache Way is to make decisions by reaching
consensus (and avoiding votes).
But the Apache Website says "one of the fundamental aspects of
accomplishing things within the Apache framework is doing so by consensus,
we need a way to tell whether we have reached consensus. We do this by
voting." [1] — which means we make decisions by voting, correct?
[1] https://www.apache.org/foundation/voting.html
On Fri, Apr 22, 2022 at 11:00 PM Dave Fisher <wa...@apache.org> wrote:
> Hi Yu,
>
> > On Apr 21, 2022, at 11:46 PM, Yu <li...@apache.org> wrote:
> >
> > Thanks all!
> >
> > I understand that we need to follow the Apache way (If it didn’t happen
> on
> > the mailing list, it didn’t happen) to *make final decisions*, but we can
> > find a better place to *discuss issues and reuse information effectively*
> > [1].
>
> Another important part of The Apache Way is to make decisions by reaching
> consensus (and avoiding votes). [3]
>
> This discussion is not finished and this should not be a call to a vote.
> When a VOTE is called it must be clear and not buried at the bottom of a
> long email.
>
> The project has been using Google Docs for collaboration. Is the real
> motivation to use GitHub Discussions instead of Google Docs?
>
> >
> > ~~~~~~~~
> >
> > # Current issues
> >
> > We have a lot of work in various places, but the information is not
> > organized and reused effectively.
> >
> > ## Slack
> > - Information is not publicly accessible. You need to upgrade to paid
> plans
> > or else you can see just the 10,000 most recent messages.
> > - Information is scattered and not categorized.
>
> The Pulsar slack has existed since the beginning of the project. We have
> 6688 subscribers to the #general and that is great.
>
> >
> > # StackOveflow
> > - Inactive. Only 24 results after searching "apachepulsar".
>
> When I search “pulsar” I get over 500 results. This is an active channel.
> It’s a place where developers go.
>
> >
> > # Mailing List
> > - Information is scattered and not categorized.
> > - User experience is terrible. Plain text format decreases email
> > readability. Search function is hard to use.
>
> The search function at lists.apache.org is hard to use, but it is
> powerful. In other projects I’ve searched for and found email from 15 years
> ago. The new monthly calendar is very powerful.
>
> If we use GitHub Discussions then the discussion of the decision won’t be
> on the mailing list. People will write emails with links to the GitHub
> Discussions. These links will eventually get stale.
>
> If you want to improve lists.apache.org then you can influence that here:
> dev@ponymail.apache.org. Pony Mail is an Apache Incubator podling.
>
>
> >
> > ~~~~~~~~
> >
> > # Why try GitHub Discussions?
>
> >
> > Compared with the platforms above and GitHub Issue, GitHub Discussions
> make
> > collaboration more efficient by:
> >
> > # Making it easier to categorize, archive, and search information
> > - It has categories (Announcements, General, Ideas, Polls, Q&A, Show and
> > Tell, etc) and labels to categorize and filter information quickly.
> > - Information is permanently saved.
> > - Search is easy to use.
> >
> > # Providing a centralized community space for conversations and questions
> > - As instructed by GitHub, we can use GitHub Discussions to *discuss
> > things*, and use GitHub Issues to *catalog the work* we need to do after
> > we’ve reached a decision about how to move forward.
> >
> > # Boosting community engagement and encouraging people to make
> contributions
> > - It highlights project contributors and shows Most Helpful Ranking of
> > Contributors.
> > - It creates a place for newcomers and non-code collaborators to
> > participate in a larger community.
> >
> > # Calling users' attention to important issues or events
> > - Important discussions can be pinned to home pages for easy reference.
> >
> > ~~~~~~~~
> >
> > Feel free to share your thoughts. This vote will be open for 72 hrs.
>
> We are not ready to vote. While it might be good to do I cannot agree with
> all of your reasoning. If forced to vote then I am -1.
>
> I might agree to GitHub Discussions as a replacement for GoogleDocs.
>
> We have no power to move users away from StackOverflow. A huge number
> follow Pulsar on Slack. If it’s a matter of paying for a plan then perhaps
> there is a way. The PMC should discuss that.
>
> All The Best,
> Dave
>
> [3] http://theapacheway.com/consensus/
>
> >
> > Then we can ask Infra to do the needed GitHub Admin tasks if we reach a
> > consensus on enabling it, thank you!
> >
> > [1] http://theapacheway.com/on-list/
> >
> > Anonymitaet
> >
> > On Fri, Apr 22, 2022 at 2:34 AM Dave Fisher <wa...@apache.org> wrote:
> >
> >> I asked Infra. GitHub Discussions are not synchronized into ASF
> >> Infrastructure's GitBox. That means that there is not ability to change
> the
> >> notification scheme to send to a mailing list.
> >>
> >> Technically we can go down this path only if it is possible to set a
> >> notification within GitHub. You would need to look into that and if we
> >> decided to go forward we can ask Infra to do the needed GitHub Admin
> tasks.
> >>
> >> Community wise I agree with others that we are already splitting a lot
> of
> >> work into various places.
> >>
> >> Regards,
> >> Dave
> >>
> >> On Apr 21, 2022, at 5:47 AM, tison <wa...@gmail.com> wrote:
> >>
> >> You can ask for ASF INFRA to see whether there is a way to bring all
> >> activities of GitHub Discussion to a mailing list. Just like development
> >> activities to commits@.
> >>
> >> Best,
> >> tison.
> >>
> >>
> >> Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
> >>
> >>>
> >>> If/when GitHub disappears, will the community suffer from missing
> >>> information? If so, need to solve the "back to ASF"-path, so it isn't
> >>> lost.
> >>>
> >>> Niclas
> >>>
> >>> On 2022-04-21 11:00, Yu wrote:
> >>>> Hi Pulsarers,
> >>>>
> >>>> Recently, we've found that many open source communities use GitHub
> >>>> Discussions to facilitate effective communication, such as users can
> >>>> ask questions, share ideas, and build connections with each other
> >>>> easily [1].
> >>>>
> >>>> GitHub Discussions is designed to:
> >>>>
> >>>> - Provide centralized community space for conversations and questions
> >>>> (and make the lives of maintainers easier when it comes to issues and
> >>>> pull requests).
> >>>>
> >>>> - Create a place for newcomers and non-code collaborators to
> >>>> participate in a larger community.
> >>>>
> >>>> - Highlight project contributors to help develop the next generation
> >>>> of maintainers.
> >>>>
> >>>> And it is different from GitHub Issue by providing more functions for
> >>>> conversations, questions, and community engagement. You can check all
> >>>> details here [2].
> >>>>
> >>>> ~~~~~~~~~~~~~~~~
> >>>>
> >>>> Do we want to enable the GitHub Discussions in Pulsar?
> >>>>
> >>>> Feel free to comment, thank you!
> >>>>
> >>>> [1]
> >>>>
> >>>
> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
> >>>> [2] https://resources.github.com/devops/process/planning/discussions/
> >>>>
> >>>> Anonymitaet
> >>>
> >>
> >>
>
>
Re: Enable GitHub Discussions?
Posted by Dave Fisher <wa...@apache.org>.
Hi Yu,
> On Apr 21, 2022, at 11:46 PM, Yu <li...@apache.org> wrote:
>
> Thanks all!
>
> I understand that we need to follow the Apache way (If it didn’t happen on
> the mailing list, it didn’t happen) to *make final decisions*, but we can
> find a better place to *discuss issues and reuse information effectively*
> [1].
Another important part of The Apache Way is to make decisions by reaching consensus (and avoiding votes). [3]
This discussion is not finished and this should not be a call to a vote. When a VOTE is called it must be clear and not buried at the bottom of a long email.
The project has been using Google Docs for collaboration. Is the real motivation to use GitHub Discussions instead of Google Docs?
>
> ~~~~~~~~
>
> # Current issues
>
> We have a lot of work in various places, but the information is not
> organized and reused effectively.
>
> ## Slack
> - Information is not publicly accessible. You need to upgrade to paid plans
> or else you can see just the 10,000 most recent messages.
> - Information is scattered and not categorized.
The Pulsar slack has existed since the beginning of the project. We have 6688 subscribers to the #general and that is great.
>
> # StackOveflow
> - Inactive. Only 24 results after searching "apachepulsar".
When I search “pulsar” I get over 500 results. This is an active channel. It’s a place where developers go.
>
> # Mailing List
> - Information is scattered and not categorized.
> - User experience is terrible. Plain text format decreases email
> readability. Search function is hard to use.
The search function at lists.apache.org is hard to use, but it is powerful. In other projects I’ve searched for and found email from 15 years ago. The new monthly calendar is very powerful.
If we use GitHub Discussions then the discussion of the decision won’t be on the mailing list. People will write emails with links to the GitHub Discussions. These links will eventually get stale.
If you want to improve lists.apache.org then you can influence that here: dev@ponymail.apache.org. Pony Mail is an Apache Incubator podling.
>
> ~~~~~~~~
>
> # Why try GitHub Discussions?
>
> Compared with the platforms above and GitHub Issue, GitHub Discussions make
> collaboration more efficient by:
>
> # Making it easier to categorize, archive, and search information
> - It has categories (Announcements, General, Ideas, Polls, Q&A, Show and
> Tell, etc) and labels to categorize and filter information quickly.
> - Information is permanently saved.
> - Search is easy to use.
>
> # Providing a centralized community space for conversations and questions
> - As instructed by GitHub, we can use GitHub Discussions to *discuss
> things*, and use GitHub Issues to *catalog the work* we need to do after
> we’ve reached a decision about how to move forward.
>
> # Boosting community engagement and encouraging people to make contributions
> - It highlights project contributors and shows Most Helpful Ranking of
> Contributors.
> - It creates a place for newcomers and non-code collaborators to
> participate in a larger community.
>
> # Calling users' attention to important issues or events
> - Important discussions can be pinned to home pages for easy reference.
>
> ~~~~~~~~
>
> Feel free to share your thoughts. This vote will be open for 72 hrs.
We are not ready to vote. While it might be good to do I cannot agree with all of your reasoning. If forced to vote then I am -1.
I might agree to GitHub Discussions as a replacement for GoogleDocs.
We have no power to move users away from StackOverflow. A huge number follow Pulsar on Slack. If it’s a matter of paying for a plan then perhaps there is a way. The PMC should discuss that.
All The Best,
Dave
[3] http://theapacheway.com/consensus/
>
> Then we can ask Infra to do the needed GitHub Admin tasks if we reach a
> consensus on enabling it, thank you!
>
> [1] http://theapacheway.com/on-list/
>
> Anonymitaet
>
> On Fri, Apr 22, 2022 at 2:34 AM Dave Fisher <wa...@apache.org> wrote:
>
>> I asked Infra. GitHub Discussions are not synchronized into ASF
>> Infrastructure's GitBox. That means that there is not ability to change the
>> notification scheme to send to a mailing list.
>>
>> Technically we can go down this path only if it is possible to set a
>> notification within GitHub. You would need to look into that and if we
>> decided to go forward we can ask Infra to do the needed GitHub Admin tasks.
>>
>> Community wise I agree with others that we are already splitting a lot of
>> work into various places.
>>
>> Regards,
>> Dave
>>
>> On Apr 21, 2022, at 5:47 AM, tison <wa...@gmail.com> wrote:
>>
>> You can ask for ASF INFRA to see whether there is a way to bring all
>> activities of GitHub Discussion to a mailing list. Just like development
>> activities to commits@.
>>
>> Best,
>> tison.
>>
>>
>> Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
>>
>>>
>>> If/when GitHub disappears, will the community suffer from missing
>>> information? If so, need to solve the "back to ASF"-path, so it isn't
>>> lost.
>>>
>>> Niclas
>>>
>>> On 2022-04-21 11:00, Yu wrote:
>>>> Hi Pulsarers,
>>>>
>>>> Recently, we've found that many open source communities use GitHub
>>>> Discussions to facilitate effective communication, such as users can
>>>> ask questions, share ideas, and build connections with each other
>>>> easily [1].
>>>>
>>>> GitHub Discussions is designed to:
>>>>
>>>> - Provide centralized community space for conversations and questions
>>>> (and make the lives of maintainers easier when it comes to issues and
>>>> pull requests).
>>>>
>>>> - Create a place for newcomers and non-code collaborators to
>>>> participate in a larger community.
>>>>
>>>> - Highlight project contributors to help develop the next generation
>>>> of maintainers.
>>>>
>>>> And it is different from GitHub Issue by providing more functions for
>>>> conversations, questions, and community engagement. You can check all
>>>> details here [2].
>>>>
>>>> ~~~~~~~~~~~~~~~~
>>>>
>>>> Do we want to enable the GitHub Discussions in Pulsar?
>>>>
>>>> Feel free to comment, thank you!
>>>>
>>>> [1]
>>>>
>>> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
>>>> [2] https://resources.github.com/devops/process/planning/discussions/
>>>>
>>>> Anonymitaet
>>>
>>
>>
Re: Enable GitHub Discussions?
Posted by Dave Fisher <wa...@apache.org>.
Hi Yu,
> On Apr 21, 2022, at 11:46 PM, Yu <li...@apache.org> wrote:
>
> Thanks all!
>
> I understand that we need to follow the Apache way (If it didn’t happen on
> the mailing list, it didn’t happen) to *make final decisions*, but we can
> find a better place to *discuss issues and reuse information effectively*
> [1].
Another important part of The Apache Way is to make decisions by reaching consensus (and avoiding votes). [3]
This discussion is not finished and this should not be a call to a vote. When a VOTE is called it must be clear and not buried at the bottom of a long email.
The project has been using Google Docs for collaboration. Is the real motivation to use GitHub Discussions instead of Google Docs?
>
> ~~~~~~~~
>
> # Current issues
>
> We have a lot of work in various places, but the information is not
> organized and reused effectively.
>
> ## Slack
> - Information is not publicly accessible. You need to upgrade to paid plans
> or else you can see just the 10,000 most recent messages.
> - Information is scattered and not categorized.
The Pulsar slack has existed since the beginning of the project. We have 6688 subscribers to the #general and that is great.
>
> # StackOveflow
> - Inactive. Only 24 results after searching "apachepulsar".
When I search “pulsar” I get over 500 results. This is an active channel. It’s a place where developers go.
>
> # Mailing List
> - Information is scattered and not categorized.
> - User experience is terrible. Plain text format decreases email
> readability. Search function is hard to use.
The search function at lists.apache.org is hard to use, but it is powerful. In other projects I’ve searched for and found email from 15 years ago. The new monthly calendar is very powerful.
If we use GitHub Discussions then the discussion of the decision won’t be on the mailing list. People will write emails with links to the GitHub Discussions. These links will eventually get stale.
If you want to improve lists.apache.org then you can influence that here: dev@ponymail.apache.org. Pony Mail is an Apache Incubator podling.
>
> ~~~~~~~~
>
> # Why try GitHub Discussions?
>
> Compared with the platforms above and GitHub Issue, GitHub Discussions make
> collaboration more efficient by:
>
> # Making it easier to categorize, archive, and search information
> - It has categories (Announcements, General, Ideas, Polls, Q&A, Show and
> Tell, etc) and labels to categorize and filter information quickly.
> - Information is permanently saved.
> - Search is easy to use.
>
> # Providing a centralized community space for conversations and questions
> - As instructed by GitHub, we can use GitHub Discussions to *discuss
> things*, and use GitHub Issues to *catalog the work* we need to do after
> we’ve reached a decision about how to move forward.
>
> # Boosting community engagement and encouraging people to make contributions
> - It highlights project contributors and shows Most Helpful Ranking of
> Contributors.
> - It creates a place for newcomers and non-code collaborators to
> participate in a larger community.
>
> # Calling users' attention to important issues or events
> - Important discussions can be pinned to home pages for easy reference.
>
> ~~~~~~~~
>
> Feel free to share your thoughts. This vote will be open for 72 hrs.
We are not ready to vote. While it might be good to do I cannot agree with all of your reasoning. If forced to vote then I am -1.
I might agree to GitHub Discussions as a replacement for GoogleDocs.
We have no power to move users away from StackOverflow. A huge number follow Pulsar on Slack. If it’s a matter of paying for a plan then perhaps there is a way. The PMC should discuss that.
All The Best,
Dave
[3] http://theapacheway.com/consensus/
>
> Then we can ask Infra to do the needed GitHub Admin tasks if we reach a
> consensus on enabling it, thank you!
>
> [1] http://theapacheway.com/on-list/
>
> Anonymitaet
>
> On Fri, Apr 22, 2022 at 2:34 AM Dave Fisher <wa...@apache.org> wrote:
>
>> I asked Infra. GitHub Discussions are not synchronized into ASF
>> Infrastructure's GitBox. That means that there is not ability to change the
>> notification scheme to send to a mailing list.
>>
>> Technically we can go down this path only if it is possible to set a
>> notification within GitHub. You would need to look into that and if we
>> decided to go forward we can ask Infra to do the needed GitHub Admin tasks.
>>
>> Community wise I agree with others that we are already splitting a lot of
>> work into various places.
>>
>> Regards,
>> Dave
>>
>> On Apr 21, 2022, at 5:47 AM, tison <wa...@gmail.com> wrote:
>>
>> You can ask for ASF INFRA to see whether there is a way to bring all
>> activities of GitHub Discussion to a mailing list. Just like development
>> activities to commits@.
>>
>> Best,
>> tison.
>>
>>
>> Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
>>
>>>
>>> If/when GitHub disappears, will the community suffer from missing
>>> information? If so, need to solve the "back to ASF"-path, so it isn't
>>> lost.
>>>
>>> Niclas
>>>
>>> On 2022-04-21 11:00, Yu wrote:
>>>> Hi Pulsarers,
>>>>
>>>> Recently, we've found that many open source communities use GitHub
>>>> Discussions to facilitate effective communication, such as users can
>>>> ask questions, share ideas, and build connections with each other
>>>> easily [1].
>>>>
>>>> GitHub Discussions is designed to:
>>>>
>>>> - Provide centralized community space for conversations and questions
>>>> (and make the lives of maintainers easier when it comes to issues and
>>>> pull requests).
>>>>
>>>> - Create a place for newcomers and non-code collaborators to
>>>> participate in a larger community.
>>>>
>>>> - Highlight project contributors to help develop the next generation
>>>> of maintainers.
>>>>
>>>> And it is different from GitHub Issue by providing more functions for
>>>> conversations, questions, and community engagement. You can check all
>>>> details here [2].
>>>>
>>>> ~~~~~~~~~~~~~~~~
>>>>
>>>> Do we want to enable the GitHub Discussions in Pulsar?
>>>>
>>>> Feel free to comment, thank you!
>>>>
>>>> [1]
>>>>
>>> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
>>>> [2] https://resources.github.com/devops/process/planning/discussions/
>>>>
>>>> Anonymitaet
>>>
>>
>>
Re: Enable GitHub Discussions?
Posted by Yu <li...@apache.org>.
Thanks all!
I understand that we need to follow the Apache way (If it didn’t happen on
the mailing list, it didn’t happen) to *make final decisions*, but we can
find a better place to *discuss issues and reuse information effectively*
[1].
~~~~~~~~
# Current issues
We have a lot of work in various places, but the information is not
organized and reused effectively.
## Slack
- Information is not publicly accessible. You need to upgrade to paid plans
or else you can see just the 10,000 most recent messages.
- Information is scattered and not categorized.
# StackOveflow
- Inactive. Only 24 results after searching "apachepulsar".
# Mailing List
- Information is scattered and not categorized.
- User experience is terrible. Plain text format decreases email
readability. Search function is hard to use.
~~~~~~~~
# Why try GitHub Discussions?
Compared with the platforms above and GitHub Issue, GitHub Discussions make
collaboration more efficient by:
# Making it easier to categorize, archive, and search information
- It has categories (Announcements, General, Ideas, Polls, Q&A, Show and
Tell, etc) and labels to categorize and filter information quickly.
- Information is permanently saved.
- Search is easy to use.
# Providing a centralized community space for conversations and questions
- As instructed by GitHub, we can use GitHub Discussions to *discuss
things*, and use GitHub Issues to *catalog the work* we need to do after
we’ve reached a decision about how to move forward.
# Boosting community engagement and encouraging people to make contributions
- It highlights project contributors and shows Most Helpful Ranking of
Contributors.
- It creates a place for newcomers and non-code collaborators to
participate in a larger community.
# Calling users' attention to important issues or events
- Important discussions can be pinned to home pages for easy reference.
~~~~~~~~
Feel free to share your thoughts. This vote will be open for 72 hrs.
Then we can ask Infra to do the needed GitHub Admin tasks if we reach a
consensus on enabling it, thank you!
[1] http://theapacheway.com/on-list/
Anonymitaet
On Fri, Apr 22, 2022 at 2:34 AM Dave Fisher <wa...@apache.org> wrote:
> I asked Infra. GitHub Discussions are not synchronized into ASF
> Infrastructure's GitBox. That means that there is not ability to change the
> notification scheme to send to a mailing list.
>
> Technically we can go down this path only if it is possible to set a
> notification within GitHub. You would need to look into that and if we
> decided to go forward we can ask Infra to do the needed GitHub Admin tasks.
>
> Community wise I agree with others that we are already splitting a lot of
> work into various places.
>
> Regards,
> Dave
>
> On Apr 21, 2022, at 5:47 AM, tison <wa...@gmail.com> wrote:
>
> You can ask for ASF INFRA to see whether there is a way to bring all
> activities of GitHub Discussion to a mailing list. Just like development
> activities to commits@.
>
> Best,
> tison.
>
>
> Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
>
>>
>> If/when GitHub disappears, will the community suffer from missing
>> information? If so, need to solve the "back to ASF"-path, so it isn't
>> lost.
>>
>> Niclas
>>
>> On 2022-04-21 11:00, Yu wrote:
>> > Hi Pulsarers,
>> >
>> > Recently, we've found that many open source communities use GitHub
>> > Discussions to facilitate effective communication, such as users can
>> > ask questions, share ideas, and build connections with each other
>> > easily [1].
>> >
>> > GitHub Discussions is designed to:
>> >
>> > - Provide centralized community space for conversations and questions
>> > (and make the lives of maintainers easier when it comes to issues and
>> > pull requests).
>> >
>> > - Create a place for newcomers and non-code collaborators to
>> > participate in a larger community.
>> >
>> > - Highlight project contributors to help develop the next generation
>> > of maintainers.
>> >
>> > And it is different from GitHub Issue by providing more functions for
>> > conversations, questions, and community engagement. You can check all
>> > details here [2].
>> >
>> > ~~~~~~~~~~~~~~~~
>> >
>> > Do we want to enable the GitHub Discussions in Pulsar?
>> >
>> > Feel free to comment, thank you!
>> >
>> > [1]
>> >
>> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
>> > [2] https://resources.github.com/devops/process/planning/discussions/
>> >
>> > Anonymitaet
>>
>
>
Re: Enable GitHub Discussions?
Posted by Yu <li...@apache.org>.
Thanks all!
I understand that we need to follow the Apache way (If it didn’t happen on
the mailing list, it didn’t happen) to *make final decisions*, but we can
find a better place to *discuss issues and reuse information effectively*
[1].
~~~~~~~~
# Current issues
We have a lot of work in various places, but the information is not
organized and reused effectively.
## Slack
- Information is not publicly accessible. You need to upgrade to paid plans
or else you can see just the 10,000 most recent messages.
- Information is scattered and not categorized.
# StackOveflow
- Inactive. Only 24 results after searching "apachepulsar".
# Mailing List
- Information is scattered and not categorized.
- User experience is terrible. Plain text format decreases email
readability. Search function is hard to use.
~~~~~~~~
# Why try GitHub Discussions?
Compared with the platforms above and GitHub Issue, GitHub Discussions make
collaboration more efficient by:
# Making it easier to categorize, archive, and search information
- It has categories (Announcements, General, Ideas, Polls, Q&A, Show and
Tell, etc) and labels to categorize and filter information quickly.
- Information is permanently saved.
- Search is easy to use.
# Providing a centralized community space for conversations and questions
- As instructed by GitHub, we can use GitHub Discussions to *discuss
things*, and use GitHub Issues to *catalog the work* we need to do after
we’ve reached a decision about how to move forward.
# Boosting community engagement and encouraging people to make contributions
- It highlights project contributors and shows Most Helpful Ranking of
Contributors.
- It creates a place for newcomers and non-code collaborators to
participate in a larger community.
# Calling users' attention to important issues or events
- Important discussions can be pinned to home pages for easy reference.
~~~~~~~~
Feel free to share your thoughts. This vote will be open for 72 hrs.
Then we can ask Infra to do the needed GitHub Admin tasks if we reach a
consensus on enabling it, thank you!
[1] http://theapacheway.com/on-list/
Anonymitaet
On Fri, Apr 22, 2022 at 2:34 AM Dave Fisher <wa...@apache.org> wrote:
> I asked Infra. GitHub Discussions are not synchronized into ASF
> Infrastructure's GitBox. That means that there is not ability to change the
> notification scheme to send to a mailing list.
>
> Technically we can go down this path only if it is possible to set a
> notification within GitHub. You would need to look into that and if we
> decided to go forward we can ask Infra to do the needed GitHub Admin tasks.
>
> Community wise I agree with others that we are already splitting a lot of
> work into various places.
>
> Regards,
> Dave
>
> On Apr 21, 2022, at 5:47 AM, tison <wa...@gmail.com> wrote:
>
> You can ask for ASF INFRA to see whether there is a way to bring all
> activities of GitHub Discussion to a mailing list. Just like development
> activities to commits@.
>
> Best,
> tison.
>
>
> Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
>
>>
>> If/when GitHub disappears, will the community suffer from missing
>> information? If so, need to solve the "back to ASF"-path, so it isn't
>> lost.
>>
>> Niclas
>>
>> On 2022-04-21 11:00, Yu wrote:
>> > Hi Pulsarers,
>> >
>> > Recently, we've found that many open source communities use GitHub
>> > Discussions to facilitate effective communication, such as users can
>> > ask questions, share ideas, and build connections with each other
>> > easily [1].
>> >
>> > GitHub Discussions is designed to:
>> >
>> > - Provide centralized community space for conversations and questions
>> > (and make the lives of maintainers easier when it comes to issues and
>> > pull requests).
>> >
>> > - Create a place for newcomers and non-code collaborators to
>> > participate in a larger community.
>> >
>> > - Highlight project contributors to help develop the next generation
>> > of maintainers.
>> >
>> > And it is different from GitHub Issue by providing more functions for
>> > conversations, questions, and community engagement. You can check all
>> > details here [2].
>> >
>> > ~~~~~~~~~~~~~~~~
>> >
>> > Do we want to enable the GitHub Discussions in Pulsar?
>> >
>> > Feel free to comment, thank you!
>> >
>> > [1]
>> >
>> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
>> > [2] https://resources.github.com/devops/process/planning/discussions/
>> >
>> > Anonymitaet
>>
>
>
Re: Enable GitHub Discussions?
Posted by Dave Fisher <wa...@apache.org>.
I asked Infra. GitHub Discussions are not synchronized into ASF Infrastructure's GitBox. That means that there is not ability to change the notification scheme to send to a mailing list.
Technically we can go down this path only if it is possible to set a notification within GitHub. You would need to look into that and if we decided to go forward we can ask Infra to do the needed GitHub Admin tasks.
Community wise I agree with others that we are already splitting a lot of work into various places.
Regards,
Dave
> On Apr 21, 2022, at 5:47 AM, tison <wa...@gmail.com> wrote:
>
> You can ask for ASF INFRA to see whether there is a way to bring all activities of GitHub Discussion to a mailing list. Just like development activities to commits@.
>
> Best,
> tison.
>
>
> Niclas Hedhman <niclas@hedhman.org <ma...@hedhman.org>> 于2022年4月21日周四 20:16写道：
>
> If/when GitHub disappears, will the community suffer from missing
> information? If so, need to solve the "back to ASF"-path, so it isn't
> lost.
>
> Niclas
>
> On 2022-04-21 11:00, Yu wrote:
> > Hi Pulsarers,
> >
> > Recently, we've found that many open source communities use GitHub
> > Discussions to facilitate effective communication, such as users can
> > ask questions, share ideas, and build connections with each other
> > easily [1].
> >
> > GitHub Discussions is designed to:
> >
> > - Provide centralized community space for conversations and questions
> > (and make the lives of maintainers easier when it comes to issues and
> > pull requests).
> >
> > - Create a place for newcomers and non-code collaborators to
> > participate in a larger community.
> >
> > - Highlight project contributors to help develop the next generation
> > of maintainers.
> >
> > And it is different from GitHub Issue by providing more functions for
> > conversations, questions, and community engagement. You can check all
> > details here [2].
> >
> > ~~~~~~~~~~~~~~~~
> >
> > Do we want to enable the GitHub Discussions in Pulsar?
> >
> > Feel free to comment, thank you!
> >
> > [1]
> > https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/ <https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/>
> > [2] https://resources.github.com/devops/process/planning/discussions/ <https://resources.github.com/devops/process/planning/discussions/>
> >
> > Anonymitaet
Re: Enable GitHub Discussions?
Posted by Dave Fisher <wa...@apache.org>.
I asked Infra. GitHub Discussions are not synchronized into ASF Infrastructure's GitBox. That means that there is not ability to change the notification scheme to send to a mailing list.
Technically we can go down this path only if it is possible to set a notification within GitHub. You would need to look into that and if we decided to go forward we can ask Infra to do the needed GitHub Admin tasks.
Community wise I agree with others that we are already splitting a lot of work into various places.
Regards,
Dave
> On Apr 21, 2022, at 5:47 AM, tison <wa...@gmail.com> wrote:
>
> You can ask for ASF INFRA to see whether there is a way to bring all activities of GitHub Discussion to a mailing list. Just like development activities to commits@.
>
> Best,
> tison.
>
>
> Niclas Hedhman <niclas@hedhman.org <ma...@hedhman.org>> 于2022年4月21日周四 20:16写道：
>
> If/when GitHub disappears, will the community suffer from missing
> information? If so, need to solve the "back to ASF"-path, so it isn't
> lost.
>
> Niclas
>
> On 2022-04-21 11:00, Yu wrote:
> > Hi Pulsarers,
> >
> > Recently, we've found that many open source communities use GitHub
> > Discussions to facilitate effective communication, such as users can
> > ask questions, share ideas, and build connections with each other
> > easily [1].
> >
> > GitHub Discussions is designed to:
> >
> > - Provide centralized community space for conversations and questions
> > (and make the lives of maintainers easier when it comes to issues and
> > pull requests).
> >
> > - Create a place for newcomers and non-code collaborators to
> > participate in a larger community.
> >
> > - Highlight project contributors to help develop the next generation
> > of maintainers.
> >
> > And it is different from GitHub Issue by providing more functions for
> > conversations, questions, and community engagement. You can check all
> > details here [2].
> >
> > ~~~~~~~~~~~~~~~~
> >
> > Do we want to enable the GitHub Discussions in Pulsar?
> >
> > Feel free to comment, thank you!
> >
> > [1]
> > https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/ <https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/>
> > [2] https://resources.github.com/devops/process/planning/discussions/ <https://resources.github.com/devops/process/planning/discussions/>
> >
> > Anonymitaet
Re: Enable GitHub Discussions?
Posted by tison <wa...@gmail.com>.
You can ask for ASF INFRA to see whether there is a way to bring all
activities of GitHub Discussion to a mailing list. Just like development
activities to commits@.
Best,
tison.
Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
>
> If/when GitHub disappears, will the community suffer from missing
> information? If so, need to solve the "back to ASF"-path, so it isn't
> lost.
>
> Niclas
>
> On 2022-04-21 11:00, Yu wrote:
> > Hi Pulsarers,
> >
> > Recently, we've found that many open source communities use GitHub
> > Discussions to facilitate effective communication, such as users can
> > ask questions, share ideas, and build connections with each other
> > easily [1].
> >
> > GitHub Discussions is designed to:
> >
> > - Provide centralized community space for conversations and questions
> > (and make the lives of maintainers easier when it comes to issues and
> > pull requests).
> >
> > - Create a place for newcomers and non-code collaborators to
> > participate in a larger community.
> >
> > - Highlight project contributors to help develop the next generation
> > of maintainers.
> >
> > And it is different from GitHub Issue by providing more functions for
> > conversations, questions, and community engagement. You can check all
> > details here [2].
> >
> > ~~~~~~~~~~~~~~~~
> >
> > Do we want to enable the GitHub Discussions in Pulsar?
> >
> > Feel free to comment, thank you!
> >
> > [1]
> >
> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
> > [2] https://resources.github.com/devops/process/planning/discussions/
> >
> > Anonymitaet
>
Re: Enable GitHub Discussions?
Posted by tison <wa...@gmail.com>.
You can ask for ASF INFRA to see whether there is a way to bring all
activities of GitHub Discussion to a mailing list. Just like development
activities to commits@.
Best,
tison.
Niclas Hedhman <ni...@hedhman.org> 于2022年4月21日周四 20:16写道：
>
> If/when GitHub disappears, will the community suffer from missing
> information? If so, need to solve the "back to ASF"-path, so it isn't
> lost.
>
> Niclas
>
> On 2022-04-21 11:00, Yu wrote:
> > Hi Pulsarers,
> >
> > Recently, we've found that many open source communities use GitHub
> > Discussions to facilitate effective communication, such as users can
> > ask questions, share ideas, and build connections with each other
> > easily [1].
> >
> > GitHub Discussions is designed to:
> >
> > - Provide centralized community space for conversations and questions
> > (and make the lives of maintainers easier when it comes to issues and
> > pull requests).
> >
> > - Create a place for newcomers and non-code collaborators to
> > participate in a larger community.
> >
> > - Highlight project contributors to help develop the next generation
> > of maintainers.
> >
> > And it is different from GitHub Issue by providing more functions for
> > conversations, questions, and community engagement. You can check all
> > details here [2].
> >
> > ~~~~~~~~~~~~~~~~
> >
> > Do we want to enable the GitHub Discussions in Pulsar?
> >
> > Feel free to comment, thank you!
> >
> > [1]
> >
> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
> > [2] https://resources.github.com/devops/process/planning/discussions/
> >
> > Anonymitaet
>
Re: Enable GitHub Discussions?
Posted by Niclas Hedhman <ni...@hedhman.org>.
If/when GitHub disappears, will the community suffer from missing
information? If so, need to solve the "back to ASF"-path, so it isn't
lost.
Niclas
On 2022-04-21 11:00, Yu wrote:
> Hi Pulsarers,
>
> Recently, we've found that many open source communities use GitHub
> Discussions to facilitate effective communication, such as users can
> ask questions, share ideas, and build connections with each other
> easily [1].
>
> GitHub Discussions is designed to:
>
> - Provide centralized community space for conversations and questions
> (and make the lives of maintainers easier when it comes to issues and
> pull requests).
>
> - Create a place for newcomers and non-code collaborators to
> participate in a larger community.
>
> - Highlight project contributors to help develop the next generation
> of maintainers.
>
> And it is different from GitHub Issue by providing more functions for
> conversations, questions, and community engagement. You can check all
> details here [2].
>
> ~~~~~~~~~~~~~~~~
>
> Do we want to enable the GitHub Discussions in Pulsar?
>
> Feel free to comment, thank you!
>
> [1]
> https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/
> [2] https://resources.github.com/devops/process/planning/discussions/
>
> Anonymitaet