{"action":"opened","issue":{"url":"https://api.github.com/repos/django-nose/django-nose/issues/261","repository_url":"https://api.github.com/repos/django-nose/django-nose","labels_url":"https://api.github.com/repos/django-nose/django-nose/issues/261/labels{/name}","comments_url":"https://api.github.com/repos/django-nose/django-nose/issues/261/comments","events_url":"https://api.github.com/repos/django-nose/django-nose/issues/261/events","html_url":"https://github.com/django-nose/django-nose/issues/261","id":143247274,"number":261,"title":"Move project to jazzband","user":{"login":"jwhitlock","id":286017,"avatar_url":"https://avatars.githubusercontent.com/u/286017?v=3","gravatar_id":"","url":"https://api.github.com/users/jwhitlock","html_url":"https://github.com/jwhitlock","followers_url":"https://api.github.com/users/jwhitlock/followers","following_url":"https://api.github.com/users/jwhitlock/following{/other_user}","gists_url":"https://api.github.com/users/jwhitlock/gists{/gist_id}","starred_url":"https://api.github.com/users/jwhitlock/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jwhitlock/subscriptions","organizations_url":"https://api.github.com/users/jwhitlock/orgs","repos_url":"https://api.github.com/users/jwhitlock/repos","events_url":"https://api.github.com/users/jwhitlock/events{/privacy}","received_events_url":"https://api.github.com/users/jwhitlock/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-24T13:35:13Z","updated_at":"2016-03-24T13:35:13Z","closed_at":null,"body":"[Jazzband](https://jazzband.co) is a project to share responsibility for administration of open source projects. django-nose is a good candidate because:\r\n\r\n1. The project is mature and widely used. It is part of the workflow of mature projects, and is often picked because it is the \"boring\" choice.\r\n2. Community attention is on [py.test](http://pytest.org/latest/), which is gaining plugins and features. This is reflected in the bug-to-PR ratio in the issue tracker (many bug reports, fewer PRs).\r\n3. The project has been maintained by Mozilla developers. Out of the \"Maintainer\" list in AUTHORS.rst, only one (me) is actually active. Mozilla projects are moving away from django-nose, which means that work will have to move to nights and weekends, for even less attention and slower releases.\r\n4. Built-in features like ``REUSE_DB=1`` are [flaky](https://github.com/django-nose/django-nose/milestones/Fix%20REUSE_DB=1) and not used by everyone. This means that patches work for some people and not for others. These features require the collaboration of the users of the features, and rapid iteration through possible code changes to get to a shared solution.  Since I don't use these optional features, I can't really judge the PRs we do get.\r\n\r\nBy moving to jazzband, we'll make it easier for contributors to merge changes and make official releases. In the best case, this will spark some additional contribution to fix long broken features. In the worst case, the people that really need support for the latest Django will be able to publish a compatible version.\r\n\r\nTo move to jazzband, we'll have to follow the [guidelines](https://jazzband.co/about/guidelines). I think we're pretty close, but will need some changes, such as updating our ``CONTRIBUTING.rst``.\r\n\r\nI'm looking for feedback from existing maintainers ( @jbalogh , @erikrose, @jsocol, @robhudson ), as well as those who rely on django-nose. If you stay silent, I'm assuming you are OK with the changes needed."}}