On Fri, Sep 9, 2016 at 5:07 PM, Tim Graham <timogra...@gmail.com> wrote:
> Yea, I don't know. I guess it's tough to get feedback when few people have > a deep understanding of the technical details. That's at least why I didn't > have any feedback to offer. Proposing it in the middle of the summer when > people are on generally on vacation might have contributed to the silence. > I agree - the summer was maybe the most compounding factor here, along with the fact that it's really hard to reason and talk about. > > Just wanted to give my perspective in case it helps improve the process > for next time. I'm interested to see how this experiment turns out. > Thanks, and I am as well - this is new ground for all of us, I think, and while I'd like it to end up working fantastically, we can also learn along the way and work out how to better have Django grow in the next new direction too. Andrew > On Friday, September 9, 2016 at 11:58:41 AM UTC-4, Andrew Godwin wrote: >> >> I agree some discussion would be nice, but I tried several times to start >> some and was met with silence each time. Given the generally positive >> reaction I've had from everyone I spoke to about the idea, I took it to the >> technical board, which seemed better than just sitting around with nothing >> happening. >> >> There was a lot of discussion of technical merit of Channels previously >> during the proposal to merge it in, so I guess everyone felt they had said >> their piece then? I don't really know, the perspective from where I'm >> sitting is skewed and people are talking to me about Channels and its >> merits and downsides constantly. >> >> I tried to build on the problems people had with my merge approach and do >> this slowly, define a process, and get people involved - I'm not sure what >> else I could have done? Waited another two months? >> >> Andrew >> >> On Fri, Sep 9, 2016 at 4:51 PM, Tim Graham <timog...@gmail.com> wrote: >> >>> Thanks, what is missing to me is the technical discussions. Now, I see >>> there is a draft DEP: https://github.com/django/deps >>> /blob/master/draft/0006-channels.rst. If that was shared to this list, >>> I missed it. Perhaps it would have inspired some discussion in your >>> proposal [0] which didn't get any feedback. That was the oddest part of the >>> process to me. When you asked for feedback about whether or not the project >>> should be adopted as an official project, no one said anything and the >>> default action was to continue the process. It would have been nice to see >>> some enthusiasm from others about the merits of adopting it as an official >>> project. >>> >>> [0] https://groups.google.com/d/topic/django-developers/24DGLVVR >>> V_s/discussion >>> >>> On Friday, September 9, 2016 at 11:14:25 AM UTC-4, Andrew Godwin wrote: >>>> >>>> Of course - here is the email I sent to the board: >>>> >>>> --- >>>> >>>> Hello everyone, >>>> >>>> As per DEP 7 (https://github.com/django/dep >>>> s/blob/master/final/0007-official-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 <timog...@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- >>>>>> django-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-develop...@googlegroups.com. >>>>> To post to this group, send email to django-d...@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/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-develop...@googlegroups.com. >>> To post to this group, send email to django-d...@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/b3f050fb-e5fc-4679-abea-58cf521caed3% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/django-developers/b3f050fb-e5fc-4679-abea-58cf521caed3%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/e88d6cfe-978e-4563-b8ef- > ad4127bec563%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/e88d6cfe-978e-4563-b8ef-ad4127bec563%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/CAFwN1up_Onq3%2BKS31pAcV0CrULxMY5J-wBrSCoKQcDUvxuO-pg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
