On Sat, 31 Mar 2018 at 12:51 Mariatta Wijaya <mariatta.wij...@gmail.com> wrote:
> Thanks for the writeup Craig! > My comments: > > >> - decide on the type of logins/auth that will be allowed for this service >> -> GitHub oauth? >> -> Google oauth? > > > I'll be happy as long as these two auths are supported. > > - should there be a DNS name for this for easy access: chat.python.org >> ? > > > Maybe in the second phase (after the trial phase) > > -> identify points of contact for Zulip, i.e. who gets contacted if >> something goes wrong? > > > I'd like at least several core devs to get involved as admins. > > -> should the existing Python Software Foundation infrastructure team be > involved in the admin of this system? > > I think they should be involved, with setting up zulip and as admins. > Since I assume we will be going with zulipchat.com hosting, there shouldn't be much set up beyond choosing initial settings, but someone from the infrastructure team should have admin rights to make sure there are enough people with admin access should something arise. > > -> does Code of Conduct apply to users of chat system? Should this be >> advertised somehow > > > The PSF's CoC will apply. If it's up to me, I'll have a bot set up that > greets every new members with explicit reminder that the CoC applies there. > Yep, the CoC will automatically apply as it does to all infrastructure involving Python. And I vaguely remember there being a setting to specify what shows up when people sign up so this should be doable. > > -> what types of channels/rooms should be created? who is responsible >> for creating these channels? > > To start just a python-dev room? admins can create new channels. > Using Zulip parlance, we would set up streams for what we have mailing lists for. To start, I would say we set up a stream for core-workflow and go from there as desired/requested. (And if this is successful we could potentially hand https://github.com/python/core-workflow/issues over to the actual tools for core development instead of being a catch-all place for ideas that others don't use heavily). > > - identify systems that can be integrated with Zulip: > > -> GitHub (out of the box integration is available) > > > That's perhaps the important one right now (IMO). > There's also a Travis integration. > The next I'll probably use myself is Zapier integration :) > Future integrations can be proposed at later time. > > Related question: > - can anyone add/enable their own integration between zulip and something > else? or only the admins? > You might be able to add your own. If you play with chat.zulip.org it seems to suggest you can set up your own bot if you want. Instructions on writing new integrations can be found at https://zulipchat.com/api/integration-guide > > - where on the Python.org website should information be made available >> for logging into the chat system? > > > Start with the devguide. We might want to update > https://www.python.org/community/irc/. It can be requested by opening an > issue at https://github.com/python/pythondotorg. But let's not do that > yet until after the trial phase. > Yes, we haven't even agreed to doing a trial phase, so worrying about full-fledge roll-out isn't quite necessary yet. :) At this point we just need to figure out if we want to do this, why we want to do this, then we can worry about the how of flipping this on to test it out (i.e. the proposal doc). -Brett > > > Mariatta > > ᐧ > _______________________________________________ > core-workflow mailing list -- core-workflow@python.org > To unsubscribe send an email to core-workflow-le...@python.org > https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct >
_______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-le...@python.org https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
