On Sun, 1 Apr 2018 at 01:09 Greg Price <g...@zulipchat.com> wrote: > Hello! Speaking as another member of the Zulip core team, I can > answer right here some questions from this thread. > > First off, I'll say that I'm very happy to see this discussion, and > repeat that we would be very happy to provide hosting. :) > > > > PREDEPLOYMENT QUESTIONS AND RESEARCH > > ==================================== > > 1. SETUP > > ======== > > - talk to Tim Abbot <tabbott(a)zulipchat.com> and confirm the > details about > > what Zulip can offer the Python project in terms of a hosted Zulip > chat > > service > > The hosted service we'd offer out of the box is what we call Zulip > Cloud Premium, as described here (except we'd provide it for free): > https://zulipchat.com/plans/ > > For more about how Zulip works and why we like it, you can read these: > https://zulipchat.com/why-zulip/ > https://zulipchat.com/for/open-source/ > > To set up a Zulip community, someone can follow any of the "sign up" > buttons to go to > https://zulipchat.com/new/ > and create a Zulip organization at a URL like python.zulipchat.com. > Then let us know and we'll mark that organization to get Zulip Cloud > Premium for free permanently. (We can also give it a custom domain > like chat.python.org later.) >
To prevent anyone from squatting on the name I just tried to register for python.zulipchat.com but was told that subdomain is not available (although python.zulipchat.com says there's no organization). :( -Brett > > > > - decide on the type of logins/auth that will be allowed for this > service > > -> GitHub oauth? > > -> Google oauth? > > -> chat service specific account? > > -> other? > > Out of the box, we support all three of the ideas above on > zulipchat.com: GitHub OAuth, Google OAuth, and users can sign up with > an email and password. > > > > - should there be a DNS name for this for easy eaccess: > chat.python.org > > ? > > We're happy to do this while hosting on the zulipchat.com cloud > service; we've done it for others before. No rush; we can move it to > such a name later. > > > > > 2. ADMIN > > ======== > > -> identify points of contact for Zulip, i.e. who gets contacted if > > something goes wrong? > > The usual point of contact is supp...@zulipchat.com; several of us > monitor that and we're quite responsive there. For most things that's > best. > > Folks can also contact me personally or, as mentioned upthread, Tim > Abbott. We're in the Zulip organization for Zulip's own development > community, at https://chat.zulip.org/ (which is of course open for > anyone to join); once an open Zulip org for the Python project is > set up, I'll certainly be present there too. > > > > > 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 > > This part is easy :) -- whoever wants to do this can just go to > https://zulipchat.com/new and create a new org. It's self-serve. > > > > 3. Have a few people in the core-workflow team test drive the > > system for 1 week > > I'd suggest one addition to this: have at least one experienced Zulip > user (probably me and/or Tim) participate in this step as well. Like > many forms of online communication, there's a lot of habits and norms > of usage for making everything smooth that you pick up naturally when > you join an established community, but aren't as obvious when everyone > is new to the system at the same time. > > Happy to answer other questions! > > Greg > _______________________________________________ > 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
