OK, another update on the update (sorry, I am using the last of my energy to arrange this handover, so I missed some things yesterday)
I'm going to hand over to a team of Carlton, Jamesie and Asif for now - I'll get the docs on the repo sorted out tonight and make write up a few more docs on how to run the release side of things. I'll give Carlton admin access to the repo if he doesn't have it already, and the two of you I'll grant commit access. Hopefully that should be enough to give this a solid go. I'll leave notifications for @andrewgodwin on, on github, for now, so if you really need me try that, but I may turn that off if it turns out to be too much. Thanks all who came forward. I'm hopeful that things can be kept going! Andrew On Wed, Jan 30, 2019 at 2:18 PM Andrew Godwin <[email protected]> wrote: > Just to update on this - nobody has individually come forward to help > full-time, though I have seen Carlton help out on a few issues (thanks for > that). > > I've added the PySlackers group into the support docs, as well - thanks > for that offer. > > I'm still planning to remove myself from watching all the repos come Feb > 1st, and barring positive confirmation someone else is going to actively > take over I'll put up notices on all the projects that they are actively > unmaintained apart from security issues. > > Andrew > > > On Thu, Jan 17, 2019 at 10:06 AM Andrew Godwin <[email protected]> > wrote: > >> Hi all, >> >> I'm writing to you all to update you on the current situation of Channels >> and related libraries (channels-redis and Daphne) and potentially ask for >> help. >> >> I've been the sole maintainer of these projects for quite a while and it >> has become unsustainable - all of my energy is taken up fielding issues and >> support requests and I haven't been able to even get myself to start >> looking at Django async stuff because of it. >> >> Given that, if nobody else can step forward to take over, I'll have to >> put those three projects (Channels, channels-redis, and Daphne) into an >> explicit maintenance mode where they only accept security requests via the >> normal security@ route, and start the process of retiring them as active >> Django projects, as I don't want to give the impression they're still >> maintained if they're not. >> >> (note: the asgiref project is still fine and should probably move out of >> Django to its own effort at some point giving the growing set of ASGI tools) >> >> If people are willing to take over maintenance, I'm happy to help explain >> some things but I don't have the bandwidth to bring someone completely up >> from scratch, so I can't help mentor someone who is totally new to >> maintaining open-source Python (sorry!). >> >> Once I recover a bit from the burnout I'll be able to come back and help >> with the really complex bugs; the main thing I need out of is the seemingly >> endless support requests and weird WebSocket client bugs. >> >> My personal deadline for this is two weeks, on February 1st. If you want >> to help out, please feel free to reply either here or get in touch with me >> personally to chat about what's involved. >> >> 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 [email protected]. To post to this group, send email to [email protected]. 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/CAFwN1uq3tsuWiW6AkBegMV8O2XiYxCvwimBFOg8KLj6MVDZweQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
