Brett Cannon wrote: > 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.
Yep, that's right. We use this on chat.zulip.org to link to our own Code of Conduct, so you can check out what this looks like there. > 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. That sounds like a good plan to me. Anyone in a Zulip org can create a stream; that's an option the org admins can change, but it's what I'd recommend for Python. So it's easy to let this evolve organically from there. For ideas on what a fully-fledged state might look like, there's some good discussion about streams here: https://zulipchat.com/help/getting-your-organization-started-with-zulip and in a couple of articles it links to. Craig Rodrigues wrote: > -> GitHub (out of the box integration is available) Mariatta Wijaya wrote: > The next I'll probably use myself is Zapier integration :) Brett Cannon wrote: > There's also a Travis integration. Yep! Brett Cannon wrote: > Instructions on writing new integrations can be found at > https://zulipchat.com/api/integration-guide Yep! I'd add that we've put a fair bit of work and thought into making a great API for writing new integrations. I think we've been pretty successful at making it easy to do so, and the 90+ integrations we have built-in demonstrate that. 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
