Thanks for the summary, James. As one of the IRC group contacts, here's the proposal for what happens to the cloaks on Freenode:
- Right now there's a @django/committer/$name cloak. We'd abandon that cloak. - Instead, every DSF member can apply for a @django/member/$name cloak by getting in touch with one of the IRC group contacts (namely apollo13 and myself, MarkusH) and pointing them to their name on the DSF member list. I'm not entirely sure yet how we would do the verification. Maybe by asking for the IRC handle when people become IRC members? - To ensure we have moderators in place for every #django-* channel we'd also introduce the @django/moderator/$name cloak. Each DSF member can apply for that cloak. It will give cloak holders "voice" privileges in #django-* channels. One needs to show "regular activity" in at least one official channel to become a moderator. - Former @django/committer/$name holders will be migrated to @django/member/$name unless they reach out to an IRC group contact before (or after, but that's double the work 😉). With regards to the #django-core IRC channel, we'll figure out how to delete it. People in there, expect to be kicked out 🙂. Cheers, Markus On Tue, Apr 21, 2020, at 5:34 AM, James Bennett wrote: > Last month the process of adopting DEP 10 -- new governance for the > Django project -- was completed: > > https://www.djangoproject.com/weblog/2020/mar/12/governance/ > > As a result, we are now in the implementation stage. Although there > will almost certainly be other items that pop up on the to-do list, > here's a quick status update on what has been done so far, and what > still needs to be done. > > Some of these items require particular permissions; for example, I > believe I currently have the necessary permissions to handle the PyPI > configuration change, and I know I have the necessary permissions to > create a page on djangoproject.com for listing the recipients of the > initial grant of "Django Core Developer" status, but some others -- > particularly closing mailing lists, and IRC-channel bureaucracy -- I > don't have access for, so consider this message a call to anyone who > *does* have those permissions to get in touch and coordinate on > getting them done. > > > * DONE -- Create a Mergers group for the main Django repository > * DONE -- Remove commit access for the main Django repository from the > former "Django Core" team > > * IN PROGRESS -- DSF Board develops infrastructure for running a > Technical Board election > * IN PROGRESS -- Restrict PyPI package-upload access to Releasers > * IN PROGRESS -- Add page on djangoproject.com listing recipients of > "Django Core Developer" title > * IN PROGRESS -- Update Django documentation to describe DEP 10 governance > > * TODO -- Close django-core mailing list > * TODO -- Close django-technical-board mailing list > * TODO -- Close #django-core IRC channel > * TODO -- Remove or change Django "committer" cloak on Freenode IRC > * TODO -- DSF Board to create a process for granting "Django Core > Developer" title beyond initial DEP 10 grant > * TODO -- First DEP 10 election of Technical Board > > -- > You received this message because you are subscribed to the Google > Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAL13Cg9vj6qGbnR9Zj6inYNsRTv1Orbvn-CkWBmtCFRDoLTxGA%40mail.gmail.com. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0ddfcd81-7495-46c6-973b-47d8c5c3df4d%40www.fastmail.com.
