Re: GitHub migration planning

2012-04-24 Thread Mohamad Efazati
if trac maintain is paiful maybe this link can be helpful CommercialServices – The Trac Project -> http://trac.edgewall.org/wiki/CommercialServices در ۲۴ آوریل ۲۰۱۲، ساعت ۲۰:۲۲، Aaron C. de Bruyn نوشته: > On Mon, Apr 23, 2012 at 22:30, Tai Lee

Re: GitHub migration planning

2012-04-24 Thread Aaron C. de Bruyn
On Mon, Apr 23, 2012 at 22:30, Tai Lee wrote: > This seems odd to me. Django is generally a very open and community oriented > project, which strives to consult with the community and achieve a > consensus, resorting to a BDFL decision when necessary, after all sides

Re: GitHub migration planning

2012-04-24 Thread Florian Apolloner
Hi, On Tuesday, April 24, 2012 7:30:05 AM UTC+2, Tai Lee wrote: > I just remember Adrian basically saying (and I'm paraphrasing here): "I've > been away too long, but I'm back now and I've decided that we're moving to > GitHub!" > I had that feeling a bit myself, but I think there have been

Re: GitHub migration planning

2012-04-24 Thread Danny Adair
On Tue, Apr 24, 2012 at 17:30, Tai Lee wrote: > This seems odd to me. [...] > I don't remember a thread started by Django core letting the community know > that a move was seriously on the cards, and giving the community a chance to > have some formal input before a

Re: GitHub migration planning

2012-04-23 Thread Tai Lee
This seems odd to me. Django is generally a very open and community oriented project, which strives to consult with the community and achieve a consensus, resorting to a BDFL decision when necessary, after all sides have put their case. Maybe I wasn't following closely enough (apologies if

Re: GitHub migration planning

2012-04-23 Thread Daniel Sokolowski
Thanks Luke for the clarification. -Original Message- From: Luke Plant Sent: Saturday, April 21, 2012 8:52 AM To: django-developers@googlegroups.com Subject: Re: GitHub migration planning On 20/04/12 19:58, Daniel Sokolowski wrote: Was BitBucket (mercurial system which is python

Re: GitHub migration planning

2012-04-21 Thread Luke Plant
On 20/04/12 19:58, Daniel Sokolowski wrote: > Was BitBucket (mercurial system which is python based) not considered? > And could someone point me to a url where I can read the discussion on > this migration; I am rather curious why it’s happening – the current > system works so I see no reason to

Re: GitHub migration planning

2012-04-21 Thread Luke Plant
On 20/04/12 18:26, Max Thayer wrote: > Luke, maybe I don't understand something about Trac, but some of the > issues raised by you or those you quoted seem easily fixed. Consider: > > "- there isn't a notion of "component", so there's no way to ask > "give me > the list of all

Re: GitHub migration planning

2012-04-20 Thread Daniel Sokolowski
Thank you Alex and Max for your responses. -Original Message- From: Alex Ogier Sent: Friday, April 20, 2012 3:15 PM To: django-developers@googlegroups.com Subject: Re: GitHub migration planning On Fri, Apr 20, 2012 at 2:58 PM, Daniel Sokolowski <daniel.sokolow...@klinsight.com>

Re: GitHub migration planning

2012-04-20 Thread Alex Ogier
On Fri, Apr 20, 2012 at 2:58 PM, Daniel Sokolowski wrote: > Was BitBucket (mercurial system which is python based) not considered? And > could someone point me to a url where I can read the discussion on this > migration; I am rather curious why it’s happening –

Re: GitHub migration planning

2012-04-20 Thread Max Thayer
Paul, I meant no offense. I should have been more clear that I meant my question to explore what makes Trac ideal for Django. My apologies for any misunderstandings. Daniel: Indeed, BitBucket was considered. There's a thread about it from pretty recently here:

Re: GitHub migration planning

2012-04-20 Thread Daniel Sokolowski
, 2012 1:26 PM To: django-developers@googlegroups.com Subject: Re: GitHub migration planning Luke, maybe I don't understand something about Trac, but some of the issues raised by you or those you quoted seem easily fixed. Consider: "- there isn't a notion of "component", so

Re: GitHub migration planning

2012-04-20 Thread Paul McMillan
Max, and others on this thread, Arguing about the specific mechanics of how github issues work isn't productive. Put very plainly: Django will not move to github issues because they cannot support our open community triage process. This is not negotiable. Regards, -Paul -- You received this

Re: GitHub migration planning

2012-04-20 Thread Max Thayer
Luke, maybe I don't understand something about Trac, but some of the issues raised by you or those you quoted seem easily fixed. Consider: "- there isn't a notion of "component", so there's no way to ask "give me > the list of all contrib.auth tickets, so I can find the duplicate > quickly";"

Re: GitHub migration planning

2012-04-20 Thread Luke Plant
On 18/04/12 22:44, philipn wrote: > 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

Re: GitHub migration planning

2012-04-19 Thread Alex Ogier
On Thu, Apr 19, 2012 at 1:15 PM, philipn wrote: > > > > On Wednesday, April 18, 2012 5:26:27 PM UTC-7, dstufft wrote: >> >> Github issues do not have the ability for anyone to close, tag, or create >> milestones. You have to be the creator of the ticket or someone with >>

Re: GitHub migration planning

2012-04-19 Thread philipn
On Wednesday, April 18, 2012 5:26:27 PM UTC-7, dstufft wrote: > > Github issues do not have the ability for anyone to close, tag, or create > milestones. You have to be the creator of the ticket or someone with > commit access. Django's track instance allows anyone to participate > in this way

Re: GitHub migration planning

2012-04-18 Thread Dalton Barreto
Em 18 de abril de 2012 21:13, Luke Granger-Brown escreveu: > > On Wed, Apr 18, 2012 at 11:55 PM, Dalton Barreto > wrote: >> >> Em 18 de abril de 2012 19:46, Dalton Barreto >> escreveu: >> > Em 18 de abril de 2012 18:44, philipn

Re: GitHub migration planning

2012-04-18 Thread Donald Stufft
Github issues do not have the ability for anyone to close, tag, or create milestones. You have to be the creator of the ticket or someone with commit access. Django's track instance allows anyone to participate in this way and is one of the major reasons to my knowledge that Django will keep it's

Re: GitHub migration planning

2012-04-18 Thread Luke Granger-Brown
On Wed, Apr 18, 2012 at 11:55 PM, Dalton Barreto wrote: > Em 18 de abril de 2012 19:46, Dalton Barreto > escreveu: > > Em 18 de abril de 2012 18:44, philipn escreveu: > > Hmm, this would probably disable pull requests too. Not a

Re: GitHub migration planning

2012-04-18 Thread Karen Tracey
On Wed, Apr 18, 2012 at 6:55 PM, Dalton Barreto wrote: >> 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. >> > > Hmm, this would probably disable pull

Re: GitHub migration planning

2012-04-18 Thread Łukasz Rekucki
On 19 April 2012 00:55, Donald Stufft wrote: > Github Issues are not flexible enough for Django. > That's rather a vague statement. Github issues are actually more *flexible* then Trac as you can define any set of tags for an issue. What Django could possibly want to

Re: GitHub migration planning

2012-04-18 Thread Dalton Barreto
Em 18 de abril de 2012 19:46, Dalton Barreto escreveu: > Em 18 de abril de 2012 18:44, philipn escreveu: >> Hey folks! >> >> I started a wiki page to help plan a migration to GitHub: >> >> https://code.djangoproject.com/wiki/GitHub%20Migration >> >> I

Re: GitHub migration planning

2012-04-18 Thread Donald Stufft
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 (mailto:daltonma...@gmail.com)> wrote: > > Em 18 de abril de 2012 18:44, philipn >

Re: GitHub migration planning

2012-04-18 Thread Alex Ogier
On Wed, Apr 18, 2012 at 6:46 PM, Dalton Barreto wrote: > Em 18 de abril de 2012 18:44, philipn escreveu: >> Hey folks! >> >> I started a wiki page to help plan a migration to GitHub: >> >> https://code.djangoproject.com/wiki/GitHub%20Migration >> >> I

Re: GitHub migration planning

2012-04-18 Thread Dalton Barreto
Em 18 de abril de 2012 18:44, philipn 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,

GitHub migration planning

2012-04-18 Thread philipn
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