Of course - here is the email I sent to the board: ---
Hello everyone, As per DEP 7 (https://github.com/django/deps/blob/master/final/0007-offic ial-projects.rst), I would like to propose Channels as an official Django project. Specifically, I would like to have the following repos as official Django projects: andrewgodwin/channels andrewgodwin/daphne andrewgodwin/asgi_redis andrewgodwin/asgi_ipc andrewgodwin/asgiref I debated whether to not include asgiref and asgi_ipc, but I think it is in the project's best interest to have them both as they are both valuable and small in scope. The proposed shepherd is myself, and the proposed maintenance team is myself, Steven Davidson, and Jeremy Spencer. The other two maintainers are relatively new to contributing but I aim to mentor them up to full maintenance over the coming months; I will also continue to look for a more experienced Django community member to help me with this process. I will abstain from any vote, but my personal view is that this would benefit Django, and that it draws the right balance between not including it in core straight away but still having it under the official Django umbrella. If you have any questions or clarifications, please say and I'm happy to discuss. --- Andrew On Fri, Sep 9, 2016 at 4:08 PM, Tim Graham <timogra...@gmail.com> wrote: > Could you please share the information that you submitted to the technical > board as per the DEP: "The Shepherd will submit the project, the list of > people signed up for the Maintenance Team, and the collated arguments to > the Technical Board for decision." > > In hindsight, I expected that information to be shared on this mailing > list before project is submitted to the technical board. Would it make > sense to do that in the future? > > > On Friday, September 9, 2016 at 10:58:24 AM UTC-4, Andrew Godwin wrote: >> >> Hi everyone, >> >> The Technical Board approved Channels as an official Django project as >> per DEP 7, and so the repositories have been moved under the django/ >> project on GitHub, as well as a few other things the DEP requires, and >> improving the contribution guidelines and triaging tickets. >> >> You can read more in the announcement: https://www.djan >> goproject.com/weblog/2016/sep/09/channels-adopted-official-d >> jango-project/ >> >> If you have any questions about what this means, I'm happy to answer them >> here! I'm aiming for a 1.0 release reasonably soon, after one or two minor >> breaking changes that need to be done (there'll be deprecation warning code >> in there so things don't mysteriously break on upgrade). >> >> Andrew >> > -- > 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 post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ms > gid/django-developers/d8e29c3b-1cc4-4329-a3ec-968b73417b6f% > 40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/d8e29c3b-1cc4-4329-a3ec-968b73417b6f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFwN1urPt2mOgB%2B-6ODtihnNmaGxGcMWNcoL6ttJmKJmFvK%2BUw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
