[python-committers] Re: core-dev chat

[Ethan Furman]

On 5/14/21 3:28 AM, Victor Stinner wrote:

> I'm always connected to IRC #python-dev (Freenode) for 10 years, a few
> other core devs use it time to time. Come to say hello ;-)

I've tried the IRC channel -- way too much noise.  Talking to bots is not my 
idea of a python dev chat.

My impression from the few times I've been there is that Victor uses it, and a bunch of bots use it (or maybe it's just 
one very vocal bot).


--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/OVZ4DAN4TQLKTMCDCCAQWMJ2FSXNZ46L/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Dong-hee Na]

Believe it or not, there are people who are not familiar with the IRC
culture.
And those people are who enter the opensource culture after the 2010s.
That period coincides with the growth of GitHub.

So I'm also a supporter of new communication tools.
Here the list below is my consideration.

a) Are people familiar?
If the tools are widely used by the tech company, I'd like to give the
score.
Because if the people are not familiar, it loses accessibility and maybe
nobody use after some period.

b) Does it has a thread feature?
I believe that most of the core devs need this feature since I observe that
we discuss some topics intensively for long periods of time.

c) Does it has a secret channel?

d) Can we get a sponsor from the provider or PSF for using the tools.
Because most of the tools have a subscription system and without that, we
can not use the advanced features.
For example, with free tier Slack, we lose old historical data.

So here is final my preferred list of that consideration
>>>  ["Slack", "Discord", "Teams"]

But my personal recent experience with the Discord public server was not
that good.
Because I got a lot of personal talks invitation that is actually spam
or scam.
So I exit the channel after the sprint is ended even though I use Discord
personally.
If we choose Discord, I'd like to suggest creating a new server for PSF,
not the rendezvous with the existed server.
This is the same opinion with Slack if we have the possibility to meet with
the same issue.

Regards,
Dong-hee


2021년 5월 14일 (금) 오전 8:39, Senthil Kumaran 님이 작성:

> Hello Core Dev,
>
> I find a need for a core-dev chat service, wherein I could engage in
> some quick effervescent conversations.
>
> It is like a team chat, that is popular with remote work these days.
> We even seem to have used Zoom Chat yesterday!
>
> * I know #python-dev in IRC exists, but it is mostly a channel for
> bots to send notifications, and there are plenty.  I am not certain if
> any core dev is active there. There was a time when this was active.
> * We tried python discord last year, and were bit overwhelmed with the
> number of channels and inability to customize
> * There seems to be Slack called pyslackers too[1]. I am yet to try it.
>
> To have a proper team-chat, we need a service (a) as well as (b) team
> using that.
>
> Does anyone else feel the need? Should we explore any? My thoughts and
> options are
>
> a) Resurrect #python-dev - changing notifications to different group.
> b) Request for core-dev in pyslackers Slack
> c) Request for core-dev in Discord.
>
> Any other ideas are welcome.
>
> If you think that chatting is not a good idea, and a mailing list, and
> discourse(discuss.python.org) are the best option, please share your
> thoughts as well.
>
> If we feel a chat service will be a good idea for core-dev to
> hangaround, then we can go to stage 2 of choosing the service by votes
> in discourse (discuss.python.org).
>
>
> Thank you,
> Senthil
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/BVPITIYRECSGCX2JUTMT7F7CCCYQSK4K/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/KMPHL7FMPLADQ4CYLXO5DYAEYCXUIM6A/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Nick Coghlan]

On Sat, 15 May 2021, 6:35 am Paul Moore,  wrote:

> On Fri, 14 May 2021 at 21:18, Senthil Kumaran  wrote:
>
> > > In other words, this isn't a technology problem, it's a people
> > > problem.
> >
> > Both. I didn't suggest this is technology problem. We, have to
> > choose one as per majority convenience.
>
> Fair enough. That suggests that abstaining is the right answer for
> people without a preference, I guess.
>
> > > Do enough of the core devs actually *want* to hang out in a
> > > chat forum to achieve critical mass and make it worthwhile?
> >
> > Yes, that's why the choice exist that "We don't want any chat platform".
>
> OK, as long as you don't also assume that abstention means "not
> interested in chat".
>

I think the wording of the poll here will matter quite a bit, as what
really makes a chat channel work is having a regular core of people that
are on at the same time and actually use it to talk to each other.

When that core is there, it's possible for newcomers to join, either by
lurking and observing the interactions for a while, or by introducing
themselves or asking a question and getting a reply. Without that core,
newcomers will join, not see any traffic, not get any replies their
messages, assume the channel is dead, and move on.

Time zones make it harder to build that core community, but even a channel
that has a definite active time zone (e.g. US or European business hours)
can be viable - you just need to indicate to newcomers the times when the
channel is most active.

For myself, the only period where I was a regular in Python related IRC
channels (including python-dev) was when I was working for Red Hat - I
considered joining them part of my regular login process for a work day.

When I left RH, and with the notable exception of Steering Council
meetings, I mostly went back to treating core development as an async-only
activity (sometimes very async these days, as I'll now sometimes go for
several weeks at a time without checking for any Python related messages if
I'm not already involved in a specific discussion).

Since then, the only times I've joined IRC or Zulip have been for core dev
and post-conference sprints, where I really was spending several hours in a
block on Python in general and not already focused on a specific writing or
development task.

So right now, I'd want a poll option that let me say "Only for specific
events (e.g. sprints), and will use whatever is nominated for the event"

But to figure out if a new channel (or resuscitating Zulip!) would be
viable, the information needed would be whether or not folks are prepared
to *idle* in the channel (even if they went AFK), with a view to becoming
regular participants, and what times they would be prepared to do that.

If there aren't half a dozen or a dozen folks willing to at least try to be
regulars in the channel (I don't actually know the minimum viable seed
number, but I assume there is academic research somewhere estimating it),
and their expected availability times don't have at least some overlap,
then I wouldn't expect a new channel to be any more successful than the
previous attempts.

Cheers,
Nick.





>
>
>
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/UEKMXJQKNH7V36GECE4OLKKLRK7QT7TI/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Paul Moore]

On Fri, 14 May 2021 at 21:18, Senthil Kumaran  wrote:
>
> On Fri, May 14, 2021 at 08:53:13PM +0100, Paul Moore wrote:
> > The problem with this, I think, is that my choice would be
> >
> > * Whichever one people actually used
>
> That's self-referencing, and unsolvable.

It is, but it's true nevertheless. I suppose I'd have to abstain in
that case. Would an "I'd be happy to have a chat platform but don't
care which one" option defeat the purpose?

> > In other words, this isn't a technology problem, it's a people
> > problem.
>
> Both. I didn't suggest this is technology problem. We, have to
> choose one as per majority convenience.

Fair enough. That suggests that abstaining is the right answer for
people without a preference, I guess.

> > Do enough of the core devs actually *want* to hang out in a
> > chat forum to achieve critical mass and make it worthwhile?
>
> Yes, that's why the choice exist that "We don't want any chat platform".

OK, as long as you don't also assume that abstention means "not
interested in chat".

> > Also, what would we talk about?
>
> Just as #python-dev or #python, but more constrained to committer
> discussions.

Sorry, I don't use IRC so that doesn't help much (maybe that suggests
I should have said my preference is "anything except IRC" :-))
Although the reason I never really did much with IRC was that it
seemed a bit too focused on the drop-in "hey, can anyone help" type of
interaction. So if that's a fair assessment then I can go with that
(and in that case I'd revise my vote to "not interested", as I
probably wouldn't stay logged onto a chat system if it was limited to
that type of conversation).

Paul
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/KMN3UZ2EUW4QICU2REEQT3QMW5PHCK74/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Senthil Kumaran]

On Fri, May 14, 2021 at 08:53:13PM +0100, Paul Moore wrote:
> The problem with this, I think, is that my choice would be
> 
> * Whichever one people actually used

That's self-referencing, and unsolvable.

> In other words, this isn't a technology problem, it's a people
> problem. 

Both. I didn't suggest this is technology problem. We, have to
choose one as per majority convenience.

> Do enough of the core devs actually *want* to hang out in a
> chat forum to achieve critical mass and make it worthwhile? 

Yes, that's why the choice exist that "We don't want any chat platform".

> Also, what would we talk about? 

Just as #python-dev or #python, but more constrained to committer 
discussions. 


-- 
Senthil
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/G66FXXRFE625NWZYVOAQNHLE7THRLMET/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Paul Moore]

On Fri, 14 May 2021 at 19:51, Senthil Kumaran  wrote:
>
> On Fri, May 14, 2021 at 11:07:12AM -0700, Brett Cannon wrote:
>
> > You could launch a poll on discuss.python.org and see if there's a clear
> > winner.
>
> Yes, after hearing some opinions, I plan to do that. Right now, I guess
> the choices I am thinking are
>
> - No, I am not interested in Chat.
> - Focus on #python-dev IRC
> - Focus on Zulip. Keep #python-dev for alerts.
> - Gitter
> - Discord
> - Slack
>
> Platform + Community (number of votes) might help us come to a
> consensus.

The problem with this, I think, is that my choice would be

* Whichever one people actually used

In other words, this isn't a technology problem, it's a people
problem. Do enough of the core devs actually *want* to hang out in a
chat forum to achieve critical mass and make it worthwhile? Also, what
would we talk about? Would it only be for things like "hey, does
anybody know how X works, because I'm looking at bpo-" or would
"social" conversations be acceptable? How far would that go? Funny cat
videos? I'm half joking, but the truth is that a community is more
than just technical questions, but I don't know how many of us would
like that sort of community. But conversely, a platform that people
simply "pop in to" when they have a question won't last very long.

Paul
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/M7EY5O7LKJR5TUQ2F5Z4G66GVB22QDSQ/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Antoine Pitrou]

Le 14/05/2021 à 21:40, Senthil Kumaran a écrit :

On Fri, May 14, 2021 at 09:21:14PM +0200, Marc-Andre Lemburg wrote:

Wouldn't it make more sense to run a matrix.org server which then
connects and bridges across all those channels ?

https://matrix.org/bridges/

People could then continue to use their preferred platform,
without losing touch.


I haven't used matrix at all, so I couldn't imagine this.  This is a
great idea.


I don't think this is a great idea at all. The level of integration and 
polishness will probably be rather low, and functionality (e.g. 
discussion threads) will inevitably be constrained by the lowest common 
denominator.


IOW, you're probably looking at a user experience as frustrating as 
Discourse's bidirectional e-mail bridge.


Regards

Antoine.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/QVQQ3CL65E6SAIVDGVMRWN7WWWQGCFJO/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Senthil Kumaran]

On Fri, May 14, 2021 at 09:21:14PM +0200, Marc-Andre Lemburg wrote:
> Wouldn't it make more sense to run a matrix.org server which then
> connects and bridges across all those channels ?
> 
> https://matrix.org/bridges/
> 
> People could then continue to use their preferred platform,
> without losing touch.

I haven't used matrix at all, so I couldn't imagine this.  This is a
great idea. If we don't have a clear consensus, but find many platforms
equally preferable, then matrix bridge the islands.

One downside is, self-hosting and administration aspects that Marriata
brought up. It will have to be resolved separately.

-- 
Senthil

___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/N4VTKMPSX4OOWFKWA7OUL2W6WUBGQ7ZJ/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Marc-Andre Lemburg]

On 14.05.2021 20:50, Senthil Kumaran wrote:
> On Fri, May 14, 2021 at 11:07:12AM -0700, Brett Cannon wrote:
> 
>> You could launch a poll on discuss.python.org and see if there's a clear
>> winner.
> 
> Yes, after hearing some opinions, I plan to do that. Right now, I guess
> the choices I am thinking are
> 
> - No, I am not interested in Chat.
> - Focus on #python-dev IRC
> - Focus on Zulip. Keep #python-dev for alerts.
> - Gitter
> - Discord
> - Slack
>
> Platform + Community (number of votes) might help us come to a
> consensus.
> 
> Note: This is for #python-committers. For #users, I think, discord,
> slack, IRC, are present at the moment.

Wouldn't it make more sense to run a matrix.org server which then
connects and bridges across all those channels ?

https://matrix.org/bridges/

People could then continue to use their preferred platform,
without losing touch.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, May 14 2021)
>>> Python Projects, Coaching and Support ...https://www.egenix.com/
>>> Python Product Development ...https://consulting.egenix.com/


::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
   Registered at Amtsgericht Duesseldorf: HRB 46611
   https://www.egenix.com/company/contact/
 https://www.malemburg.com/

___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/RXNCZYEE2KHOJF5EXRAT62WCOQSSTXS4/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Senthil Kumaran]

On Fri, May 14, 2021 at 06:30:33PM +, Jason R. Coombs wrote:
> Would be delighted if there was a preferred platform for chat and that 
> platform
> be documented (and allowed to change as solutions and the community evolves).

This resonates well with me. Especially as I use _ these chat platforms_
with other communities.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/FLCYJHLJIMTKDW4X734ZOCL5UTVAMDEG/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Senthil Kumaran]

On Fri, May 14, 2021 at 11:28:48AM -0700, Mariatta wrote:

> I hope we can properly evaluate how the next chosen chatting platform
> can be used more effectively.

I agree. The proposal is like choice of Github. We don't self-host, but
if identify something that will work for us (provided there is a need).

___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/EVFUVUQMZUGJ3HAIHO2XKTEIEJ66A36J/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Senthil Kumaran]

On Fri, May 14, 2021 at 11:07:12AM -0700, Brett Cannon wrote:

> You could launch a poll on discuss.python.org and see if there's a clear
> winner.

Yes, after hearing some opinions, I plan to do that. Right now, I guess
the choices I am thinking are

- No, I am not interested in Chat.
- Focus on #python-dev IRC
- Focus on Zulip. Keep #python-dev for alerts.
- Gitter
- Discord
- Slack

Platform + Community (number of votes) might help us come to a
consensus.

Note: This is for #python-committers. For #users, I think, discord,
slack, IRC, are present at the moment.

-- 
Senthil
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/ZGVCFYCUPYBAXIGQC3VQRMD7I7XAMCEM/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Jason R. Coombs]

For CPython, I’ve been present on IRC and Zulip and Slack and Discord (and 
would prefer them in the reverse of that order).

I’ve used Gitter for CherryPy and Setuptools and Xonsh, but found the interface 
kinda meh compared to Slack and Discord.

Would be delighted if there was a preferred platform for chat and that platform 
be documented (and allowed to change as solutions and the community evolves).

On 14 May, 2021, at 14:07, Brett Cannon 
mailto:br...@python.org>> wrote:



On Fri, May 14, 2021 at 6:48 AM Senthil Kumaran 
mailto:sent...@python.org>> wrote:
On Fri, May 14, 2021 at 09:36:52AM +0200, Antoine Pitrou wrote:
> #python-dev on IRC has been wildly successful until perhaps 2015.
> Personally, I would have no problem using IRC if wanted to connect to a chat
> for CPython at all.

I know, it was useful, and #python is still. The bot, github, buildbot
made it more alerts only. Looks like Victor and few others still use it.


> Similarly, I would have no problem using Zulip.  I would even say that Zulip
> is by far the best chat system I've ever used, and the alternatives don't
> come near.  Its threading system is really superior to everything else.

With Zulip, I find it hard to understand, why I need two namespaces (for
lack of better term) before I start writing my text in Zulip chat.

#topic->subtopic [content]

I have not been a part of the community that uses Zulip effectively, so
I haven't learnt it well.

> The idea that if people don't use IRC and Zulip, then we should try another
> chat system, sounds like magical thought. What kind of properties do Slack,
> Gitter or Discord have that Zulip doesn't? They are actually quite annoying
> in my experience.

Some have community advantage. K8s, Golang people are on Slack. Multiple
Companies are on Slack, technical barrier is very low. Similar is the
case with Discord.

Yeah, I don't know if the Python community as a whole has totally settled on a 
platform.


Community usage, and usability _perhaps_ go hand in hand. General numbers
could support for this.

That said. If we (a quorum) feel comfortable using anything like IRC,
Zulip, I agree, we don't need another one.

You could launch a poll on discuss.python.org and 
see if there's a clear winner.

-Brett


--
Senthil
___
python-committers mailing list -- 
python-committers@python.org
To unsubscribe send an email to 
python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/LYK567UL32MQS7IBRFADWM5WIN3AY57Q/
Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list -- 
python-committers@python.org
To unsubscribe send an email to 
python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/CG4MJEDHXTKT76DY5UARV4SSFZYX7VQ7/
Code of Conduct: https://www.python.org/psf/codeofconduct/

___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/BXKZI5Y2DJ3SHX2JZYLUCJHNERTNDTYK/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Mariatta]

I'm hesitant to start yet another communication channel without considering
all the maintenance work that it entails.
It's not just about "let's spin up the server" but we should think about
who will moderate and administer it.
Since we have tried various platforms in the past, and some just didn't
work for whatever reason, it would be good to analyze and find out why we
didn't like them, and how to ensure that the next platform will not end up
the same fate.
I hope we can properly evaluate how the next chosen chatting platform can
be used more effectively.


On Fri, May 14, 2021 at 11:07 AM Brett Cannon  wrote:

>
>
> On Fri, May 14, 2021 at 6:48 AM Senthil Kumaran 
> wrote:
>
>> On Fri, May 14, 2021 at 09:36:52AM +0200, Antoine Pitrou wrote:
>> > #python-dev on IRC has been wildly successful until perhaps 2015.
>> > Personally, I would have no problem using IRC if wanted to connect to a
>> chat
>> > for CPython at all.
>>
>> I know, it was useful, and #python is still. The bot, github, buildbot
>> made it more alerts only. Looks like Victor and few others still use it.
>>
>>
>> > Similarly, I would have no problem using Zulip.  I would even say that
>> Zulip
>> > is by far the best chat system I've ever used, and the alternatives
>> don't
>> > come near.  Its threading system is really superior to everything else.
>>
>> With Zulip, I find it hard to understand, why I need two namespaces (for
>> lack of better term) before I start writing my text in Zulip chat.
>>
>> #topic->subtopic [content]
>>
>> I have not been a part of the community that uses Zulip effectively, so
>> I haven't learnt it well.
>>
>> > The idea that if people don't use IRC and Zulip, then we should try
>> another
>> > chat system, sounds like magical thought. What kind of properties do
>> Slack,
>> > Gitter or Discord have that Zulip doesn't? They are actually quite
>> annoying
>> > in my experience.
>>
>> Some have community advantage. K8s, Golang people are on Slack. Multiple
>> Companies are on Slack, technical barrier is very low. Similar is the
>> case with Discord.
>>
>
> Yeah, I don't know if the Python community as a whole has totally settled
> on a platform.
>
>
>>
>> Community usage, and usability _perhaps_ go hand in hand. General numbers
>> could support for this.
>>
>> That said. If we (a quorum) feel comfortable using anything like IRC,
>> Zulip, I agree, we don't need another one.
>>
>
> You could launch a poll on discuss.python.org and see if there's a clear
> winner.
>
> -Brett
>
>
>>
>> --
>> Senthil
>> ___
>> python-committers mailing list -- python-committers@python.org
>> To unsubscribe send an email to python-committers-le...@python.org
>> https://mail.python.org/mailman3/lists/python-committers.python.org/
>> Message archived at
>> https://mail.python.org/archives/list/python-committers@python.org/message/LYK567UL32MQS7IBRFADWM5WIN3AY57Q/
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/CG4MJEDHXTKT76DY5UARV4SSFZYX7VQ7/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/FXIVKJ7JXGHFW7KWZTPIJHSDKJ25AYBR/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Brett Cannon]

On Fri, May 14, 2021 at 6:48 AM Senthil Kumaran  wrote:

> On Fri, May 14, 2021 at 09:36:52AM +0200, Antoine Pitrou wrote:
> > #python-dev on IRC has been wildly successful until perhaps 2015.
> > Personally, I would have no problem using IRC if wanted to connect to a
> chat
> > for CPython at all.
>
> I know, it was useful, and #python is still. The bot, github, buildbot
> made it more alerts only. Looks like Victor and few others still use it.
>
>
> > Similarly, I would have no problem using Zulip.  I would even say that
> Zulip
> > is by far the best chat system I've ever used, and the alternatives don't
> > come near.  Its threading system is really superior to everything else.
>
> With Zulip, I find it hard to understand, why I need two namespaces (for
> lack of better term) before I start writing my text in Zulip chat.
>
> #topic->subtopic [content]
>
> I have not been a part of the community that uses Zulip effectively, so
> I haven't learnt it well.
>
> > The idea that if people don't use IRC and Zulip, then we should try
> another
> > chat system, sounds like magical thought. What kind of properties do
> Slack,
> > Gitter or Discord have that Zulip doesn't? They are actually quite
> annoying
> > in my experience.
>
> Some have community advantage. K8s, Golang people are on Slack. Multiple
> Companies are on Slack, technical barrier is very low. Similar is the
> case with Discord.
>

Yeah, I don't know if the Python community as a whole has totally settled
on a platform.


>
> Community usage, and usability _perhaps_ go hand in hand. General numbers
> could support for this.
>
> That said. If we (a quorum) feel comfortable using anything like IRC,
> Zulip, I agree, we don't need another one.
>

You could launch a poll on discuss.python.org and see if there's a clear
winner.

-Brett


>
> --
> Senthil
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/LYK567UL32MQS7IBRFADWM5WIN3AY57Q/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/CG4MJEDHXTKT76DY5UARV4SSFZYX7VQ7/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Senthil Kumaran]

On Fri, May 14, 2021 at 12:28:00PM +0200, Victor Stinner wrote:
> 
> The bugs.python.org and buildbot notifications are useful to me and I
> don't feel annoyed by them. But GitHub review are hard to use: only
> the user name and the PR number are given: PR title and comment
> content are not provided, you have to click on each link to know more.
> Moreover, when a user leaves 10 comments, there are 10 IRC
> notifications!

That's my experience too. Should the bot alerts be sent different
channel, so that it has more people focus?

> Mailing lists, discuss.python.org, IRC, Zulipchat, Twitter, private
> messages, etc. Well, I have enough communication channels to talk with
> other core devs ;-)
> https://pythondev.readthedocs.io/communication.html

Certainly. If we introduce another, perhaps the kill one which which
didn't take off. I agree, not introducing another one to be mix is
desirable.

-- 
Senthil
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/X3DQAT3WLYIHA3UYZ4U5XY7LTNRUVOQK/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Senthil Kumaran]

On Fri, May 14, 2021 at 09:36:52AM +0200, Antoine Pitrou wrote:
> #python-dev on IRC has been wildly successful until perhaps 2015.
> Personally, I would have no problem using IRC if wanted to connect to a chat
> for CPython at all.

I know, it was useful, and #python is still. The bot, github, buildbot
made it more alerts only. Looks like Victor and few others still use it.


> Similarly, I would have no problem using Zulip.  I would even say that Zulip
> is by far the best chat system I've ever used, and the alternatives don't
> come near.  Its threading system is really superior to everything else.

With Zulip, I find it hard to understand, why I need two namespaces (for
lack of better term) before I start writing my text in Zulip chat. 

#topic->subtopic [content]

I have not been a part of the community that uses Zulip effectively, so
I haven't learnt it well. 

> The idea that if people don't use IRC and Zulip, then we should try another
> chat system, sounds like magical thought. What kind of properties do Slack,
> Gitter or Discord have that Zulip doesn't? They are actually quite annoying
> in my experience.

Some have community advantage. K8s, Golang people are on Slack. Multiple
Companies are on Slack, technical barrier is very low. Similar is the
case with Discord.

Community usage, and usability _perhaps_ go hand in hand. General numbers
could support for this.

That said. If we (a quorum) feel comfortable using anything like IRC,
Zulip, I agree, we don't need another one.

-- 
Senthil
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/LYK567UL32MQS7IBRFADWM5WIN3AY57Q/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Victor Stinner]

Hi,

I'm always connected to IRC #python-dev (Freenode) for 10 years, a few
other core devs use it time to time. Come to say hello ;-)

The bugs.python.org and buildbot notifications are useful to me and I
don't feel annoyed by them. But GitHub review are hard to use: only
the user name and the PR number are given: PR title and comment
content are not provided, you have to click on each link to know more.
Moreover, when a user leaves 10 comments, there are 10 IRC
notifications!

Example:

11:17 < Not-4ecb> [cpython] shihai1991 reviewed pull request #26103
commit - https://git.io/JsOQn

I almost never go to Zulipchat. I was there one month ago, 6 months
since my previous visit. There were few messages.

Mailing lists, discuss.python.org, IRC, Zulipchat, Twitter, private
messages, etc. Well, I have enough communication channels to talk with
other core devs ;-)
https://pythondev.readthedocs.io/communication.html

Victor
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/U5NAQXJ2LXD2S4C5HTP3T6VBEWXEMISL/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Antoine Pitrou]

Le 14/05/2021 à 09:26, Senthil Kumaran a écrit :

On Fri, May 14, 2021 at 09:03:05AM +0200, Antoine Pitrou wrote:

Well, the more you create chat services for a single purpose, the less
you're likely to actually find a community there.  Why do you want to use
Gitter if Zulip and IRC already exist?


The goal is not the tool, but the community chat, specifically, core-dev
chat, and to find if most feel 'OK' to give a shot at chat again.

I notice, I use Slack and Discord for specific purposes, as there is
channel for the topic I am interested in, community presence, and
convenience.

The tool, could be determined based what many feel comfortable with.

- Zulip and IRC for core-dev, have been tried, and not been successful.
- Gitter, Slack, or Discord for Core-Development needs have not been
   tried yet.


#python-dev on IRC has been wildly successful until perhaps 2015. 
Personally, I would have no problem using IRC if wanted to connect to a 
chat for CPython at all.


Similarly, I would have no problem using Zulip.  I would even say that 
Zulip is by far the best chat system I've ever used, and the 
alternatives don't come near.  Its threading system is really superior 
to everything else.


The idea that if people don't use IRC and Zulip, then we should try 
another chat system, sounds like magical thought. What kind of 
properties do Slack, Gitter or Discord have that Zulip doesn't? They are 
actually quite annoying in my experience.


Regards

Antoine.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/R2FSGVOEF7UZBECMHIZARYY4MNGHUBPH/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Senthil Kumaran]

On Fri, May 14, 2021 at 09:03:05AM +0200, Antoine Pitrou wrote:
> Well, the more you create chat services for a single purpose, the less
> you're likely to actually find a community there.  Why do you want to use
> Gitter if Zulip and IRC already exist?

The goal is not the tool, but the community chat, specifically, core-dev
chat, and to find if most feel 'OK' to give a shot at chat again.

I notice, I use Slack and Discord for specific purposes, as there is
channel for the topic I am interested in, community presence, and
convenience.

The tool, could be determined based what many feel comfortable with. 

- Zulip and IRC for core-dev, have been tried, and not been successful.
- Gitter, Slack, or Discord for Core-Development needs have not been
  tried yet.

-- 
Senthil
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/LRL3GEUELUOOUBRHPEDEJFJLARCTJ4J6/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: core-dev chat

[Antoine Pitrou]

Le 14/05/2021 à 02:25, Senthil Kumaran a écrit :

On Thu, May 13, 2021 at 04:53:08PM -0700, Guido van Rossum wrote:

I’ve found Gitter works well. I’d use that, assuming it was only open to core
devs and invitees.


Thanks! I interpret this as

a) Yes to a need for chat-service for core-dev.
b) Add Gitter to the list of options to consider too.

I have used Gitter and I could use it too.

The important factor is the community and usage of chat.


Well, the more you create chat services for a single purpose, the less 
you're likely to actually find a community there.  Why do you want to 
use Gitter if Zulip and IRC already exist?


___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/PTJS3G54CRZOSTNL6HOBFPGWNDWKOLHR/
Code of Conduct: https://www.python.org/psf/codeofconduct/