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. Jacob On Tue, May 10, 2016 at 10:58 PM, Andrew Godwin <and...@aeracode.org> wrote: > Hi everyone, > > Following my decision to move Channels away from a 1.10 merge and towards > an existence as a separate app for a bit while it matures, I would like to > write up a process DEP for how we achieve this - specifically, what it > takes to be adopted as a non-core app, what that means for the Django > organisation, and what its goals should be. > > Given recent events, I feel having a process that's agreed upon and > specified is a good move for this, especially if we do it with something > else again in future. > > My rough outline is as follows: > > - A non-core project can be moved under the governance of the Django > project if it is deemed an important feature that's in our interests to > maintain and grow > > - We should be relatively convinced that it represents the best > implementation of the feature that there is, that it is matured and has a > stable release, and that there aren't competing implementations at a > similar level > > - The decision-making structure is similar to that of a DEP, in that > there must be a core "shepherd" who is the go-to person for it and makes > sure it crosses the basic test, and a technical board vote on inclusion. > > - A project under Django governance will fall under the Django umbrella > for security-related reports and fixes, and will maintain the Django > security policy on the current major release only. > > - Release schedule will not be fixed to Django's and no LTS pattern will > be forced on it, and a limited backwards-compatibility policy of only "at > least one major version" will be maintained. > > I think it's worth working out how the whole thing is going to run if > we're going to do it properly, and the DEP system seems like the best place > for something like this. If we do go down the path of starting to split out > Django into more packages, as well, it could provide a useful base for that > to structure around (though we'd want to beef up security/backwards-compat > timelines). > > It's also probably sensible that whatever we come up with covers > localflavor, as well, since that's sort of in this state already. > > 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/CAFwN1ur%3D-RAxA72vTxT2bq5-QVDLcdnOiXK_HnvyjwZHpi_izw%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAFwN1ur%3D-RAxA72vTxT2bq5-QVDLcdnOiXK_HnvyjwZHpi_izw%40mail.gmail.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/CAK8PqJHTX2kYR8CpNGz_rOJGGaKf0Z3seXA_LTLHtbNnMyjh5w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
