Just wanted to thank you so much for your hard work. The documentation is really well written!
On Wednesday, May 11, 2016, at 1:29:34 PM UTC-5, Andrew Godwin wrote: > > > > On Wed, May 11, 2016 at 11:00 AM, Jacob Kaplan-Moss <ja...@jacobian.org> > wrote: > >> I like this, and +1 on your rough outline. >> >> There is one missing thing here though: I think we need to consider the >> process/policy for removing things if they're no longer maintained. Without >> clear maintainership forks happen, which is bad for pretty much everyone. >> So I think we should have a plan in place for what happens if the shepherd >> can no longer tend to their flock, and nobody else steps into the role. >> >> I'd suggest something like this: if a project goes stale, core calls for >> new maintainers. If none arrive within a reasonable period of time (3 >> months?) we deprecate and remove the package from our org. >> >> > That seems sensible to me; if the project is important enough to Django, > I'm sure people will step up to take over, and if not, dropping it is > probably the better option rather than letting it linger. > > I would be inclined to merely mark it as deprecated and not drop it from > e.g. the GitHub org, though, as where would we move it *to*? > > 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/msgid/django-developers/885bd485-341a-47ad-8766-7ef17df77ada%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
