Github Issues are not flexible enough for Django.
On Wednesday, April 18, 2012 at 6:53 PM, Alex Ogier wrote: > On Wed, Apr 18, 2012 at 6:46 PM, Dalton Barreto <[email protected] > (mailto:[email protected])> wrote: > > Em 18 de abril de 2012 18:44, philipn <[email protected] > > (mailto:[email protected])> escreveu: > > > Hey folks! > > > > > > I started a wiki page to help plan a migration to GitHub: > > > > > > https://code.djangoproject.com/wiki/GitHub%20Migration > > > > > > I don't know what I'm doing, but I do know that the current Trac setup > > > (attaching patches, etc) is less accessible to non-core contributors than > > > GitHub and I'd love to do anything I can to help make this better. > > > > > > > > > Maybe the best way to avoid that people create issues on github is to > > disable it for the > > official repository. This is possible through the Github's Admin interface. > > > > > Err, I think the point was that Trac is less accessible than Github so > Django *should* be using Github Issues instead. > > Best, > Alex Ogier > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
