[Twisted-Python] Enable and use GitHub Discussions for twisted/twisted

[Adi Roiban]

Hi,

Should I enable GitHub discussions for twisted/twisted repo?

Advantages:

* it's like email but I think that it's easier to include/exclude people
interested in the discussion
* If an external person / one time contributor wants to participate in a
discussion, subscribing to the whole maillinglist is no longer required
* Should be easier to find the "right answer" inside a discussion.
* You can search the twisted/twisted repo from one place (GitHub top left
search bar) and also find discussion for that topic.
* Might help with keeping the comments inside the PR focused on the code
review as it should be easier to start a discussion

Disadvantages

* Depend even more on GitHub / MS.. but I hope that even if
* Yet another communication channel for the Twisted community. We already
have
  * this mailinglist
  * the web mailinglist
  * IRC
  * stack overflow
  * GitHub PRs

We already depende a lot on Github for git hosting, code review, automated
tests, deployment, pypy publishing.
I don't know if the discussion feature will make much of a difference.

There is an API [0] that ctwisted-pythontwisted-pythonan be used to export
the data if needed or import mailman data.



What do you think?

Yes... no... maybe...stupid idea :)

Thanks
---

We have an archive for this  list [1]  but there is no search.

[0]
https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions
[1] https://twistedmatrix.com/pipermail/twisted-python/
-- 
Adi Roiban
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Enable and use GitHub Discussions for twisted/twisted

[Barry Scott]

On Monday, 29 March 2021 15:27:31 BST Adi Roiban wrote:
> Hi,
> 
> Should I enable GitHub discussions for twisted/twisted repo?

I can keep up with the email, but you will lose me if I have to
browse to github to see what is going on.

Barry


> 
> Advantages:
> 
> * it's like email but I think that it's easier to include/exclude people
> interested in the discussion
> * If an external person / one time contributor wants to participate in a
> discussion, subscribing to the whole maillinglist is no longer required
> * Should be easier to find the "right answer" inside a discussion.
> * You can search the twisted/twisted repo from one place (GitHub top left
> search bar) and also find discussion for that topic.
> * Might help with keeping the comments inside the PR focused on the code
> review as it should be easier to start a discussion
> 
> Disadvantages
> 
> * Depend even more on GitHub / MS.. but I hope that even if
> * Yet another communication channel for the Twisted community. We already
> have
>   * this mailinglist
>   * the web mailinglist
>   * IRC
>   * stack overflow
>   * GitHub PRs
> 
> We already depende a lot on Github for git hosting, code review, automated
> tests, deployment, pypy publishing.
> I don't know if the discussion feature will make much of a difference.
> 
> There is an API [0] that ctwisted-pythontwisted-pythonan be used to export
> the data if needed or import mailman data.
> 
> 
> 
> What do you think?
> 
> Yes... no... maybe...stupid idea :)
> 
> Thanks
> ---
> 
> We have an archive for this  list [1]  but there is no search.
> 
> [0]
> https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions
> [1] https://twistedmatrix.com/pipermail/twisted-python/
> 




___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Enable and use GitHub Discussions for twisted/twisted

[Glyph]

> On Mar 29, 2021, at 7:27 AM, Adi Roiban  wrote:
> 
> Hi,
> 
> Should I enable GitHub discussions for twisted/twisted repo?

Rather than phrasing this in terms of advantages & disadvantages, I think it 
might be more fruitful to talk about what problem we would ostensibly be trying 
to solve by using it.  Right now I don't think the list is high-traffic enough 
that the big advantage (you can have a discussion without blasting out a 
message to too many people) would really solve any issues we're currently 
having.

Personally I am -0 because I don't think that Github's structure for 
notifications are particularly conducive to an Inbox Zero style approach, i.e. 
one where everyone involved with he project knows where to go check for things 
that they might want to pay attention to.  The mailing list makes this very 
straightforward; you just check your email, which you're probably doing anyway.

Github does have some notion of "inboxes", i.e. 
https://github.com/twisted/twisted/pulls/review-requested/@me 
 could probably 
replace https://twisted.reviews , but even though I 
am a person who thinks way too much about inboxes 
, I find 
https://github.com/notifications  difficult 
to approach.  If we were going to turn it on we should probably have a 
recommended way to check in on messages for contributors.

-g

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python