I am not a Django contributor, just a user. Whether it's github or bitbucket or something else, the more important question is stick with the current system and workflow as well as policies or move the code and then of course also have a somewhat different workflow when you start using githubs/bitbuckets/etc ticket system.
Obviously the plan is to move the code to github but continue to use trac for issues. It's to time consuming and complicated (look at the current discussion among core devs on django-dev about how to better document policies for contributing because it's to confusing) already so this certainly would make it even worse. Maybe it's a naive view of things but in the end Django is a Python lib, there are many such on github/bitbucket using the well integrated features of the platform so folks can actually spend their time developing the software itself rather than spending time on figuring out policies and maintaining infrastructure which gets so time consuming that the number of people who actually do stuff is quite small in the end. I am not criticizing, it's just something that's a bit odd, I mean, what's so special about Django that it couldn't go with githubs/bitbuckets tickets as well? Current trac could be made read-only and tickets continued on gh/bb and simply link into trac for some time until all older tickets are resolved and trac can be shut down entirely. But then again, I am no core dev, not even a contributor, just a user. Maybe all the bureaucracy and policies around contributing is needed in case of Django. If so then sorry for the noise :) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/vCrLN_-EqhMJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
