4 ms·
Anyone can contribute to Django right now; just like anyone can contribute to Rails. Only a group of core maintainers can merge those contributions into a core
by jnoller 16y ago
Anyone can contribute to Django right now; just like anyone can contribute to Rails.
Only a group of core maintainers can merge those contributions into a core, shipping release. So how does the DVCS make that core think, work or release any differently?
- varikin 16y agoI think the DVCS issue is not part of "what is wrong with Django." Like you said, anyone can contribute, and core developers will be responsible for reviewing and integrating those contributions, regardless of the VCS. There are even unofficial mirrors on Github and Bitbucket if someone wants to go that route. All that said, if Git or Hg (or other DVCS) would make some of the developers tasks easier, like reviewing patches (in the form of pull requests on Github), managing branches, tagging releases, etc, I think it is a worthwhile switch. Edit: Changed core developers to developers in the last paragraph/run-on sentence because it might benefit all contributors.
- jnoller 16y agoExcept that if the Django core developers thought that using Git, mercurial, or github would grossly improve their workflow, don't you think they'd use it? They may be perfectly comfortable with their current tools - we agree though, this is not a source control issue. It's is a personnel, and social issue. DVCSes are not magical, and github isn't a cure-all. If the problem is with the people; we have to fix the people, get new ones - not change the tools.