On Fri, Mar 30, 2018 at 1:23 PM, Guido van Rossum <gu...@python.org> wrote:
> I've also got confirmation from Tim Abbott (ZulipChat cofounder) that
> they'd be happy to host us and would even prioritize features they want.
>
> Who's interested in making this happen?We should start with an experiment,
> and it would be good to create a plan for evaluating success. If you want
> to help out, please volunteer to write up such a plan -- implementation
> will be easy.
>
>
Here are some points I jotted down. If someone is interested in this,
maybe these points can be incorporated into
a full fledge plan:
PREDEPLOYMENT QUESTIONS AND RESEARCH
====================================
1. SETUP
========
- talk to Tim Abbot <tabb...@zulipchat.com> and confirm the details about
what Zulip can offer the Python project in terms of a hosted Zulip chat
service
- decide on the type of logins/auth that will be allowed for this service
-> GitHub oauth?
-> Google oauth?
-> chat service specific account?
-> other?
- should there be a DNS name for this for easy eaccess: chat.python.org
?
2. ADMIN
========
-> identify points of contact for Zulip, i.e. who gets contacted if
something goes wrong?
-> should the existing Python Software Foundation infrastructure team be
involved in the admin of this system?
-> does Code of Conduct apply to users of chat system? Should this be
advertised somehow
when users
-> what types of channels/rooms should be created? who is responsible
for creating these channels?
3. INTEGRATIONS
================
- read up on Zulip Integrations ( https://zulipchat.com/integrations/ )
and
Bots ( https://zulipchat.com/api/running-bots )
- identify systems that can be integrated with Zulip:
-> GitHub (out of the box integration is available)
-> Roundup (not available, needs to be written)
-> Buildbot (not available, needs to be written)
-> other ?
4. WEBSITE
==========
- where on the Python.org website should information be made available
for logging into the chat system?
DEPLOYMENT PLAN
===============
0. EVALUATION
=============
1. Have key stakeholders test drive https://chat.zulip.org , and make
sure they are OK with it, before proceeding to
rollout.
1. PHASE 1 - initial rollout
============================
1. Decide on the auth/login policy for the chat system
2. Get Zulip to set up the system and make it available
3. Have a few people in the core-workflow team test drive the
system for 1 week
4. If it is people in 3. are happy with it, proceed to next steps,
otherwise stop.
5. Write up some information on the website which points people to
the chat system.
6. Send out announcements (e-mail, website, blog, twitter, etc.)
about availability of chat site
2. PHASE 2 - post rollout
=========================
1. Look at what out of the box integrations can be set up quickly
(GitHub) and set them up
2. Write any additional integrations for things that are not
available (Roundup, Buildbot)
_______________________________________________
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
