Re: [Twisted-Python] Migration to Git / GitHub

On Nov 17, 2015, at 12:52 PM, Donald Stufft wrote: > I don’t disagree with the decision to not move to GitHub issues, however > if you wanted to you could do what Golang did to minimize the data loss. > They emailed prior participants to their bug tracker to ask them to grant > their migration ap

Re: [Twisted-Python] Migration to Git / GitHub

> On Nov 17, 2015, at 11:57 AM, Adi Roiban wrote: > > All cloud based API don't allow us to impersonate users, so we will > lose the author information. > > This is one reason why I started this conversation. > > If you know how we can migrate to GitHub issues or GitLab or any other > bug trac

Re: [Twisted-Python] Migration to Git / GitHub

On 14 November 2015 at 11:39, Craig Rodrigues wrote: > On Fri, Nov 13, 2015 at 6:29 PM, Glyph Lefkowitz > wrote: >> >> >> >> We then asked people for money based on this document. So GitHub is more >> or less a done deal :-). >> > > If the plan is GitHub and the project is fine with that, then c

Re: [Twisted-Python] Migration to Git / GitHub

On Wed, 11 Nov 2015 at 22:41 Adi Roiban wrote: > Hi, > > So I am bringing this to the list for a greater audience and to reach > all borders and timezones :) > Thanks! > General rules by Glyph as they were sent to me :) > > Development can't stop, the website can't go down, and we can't lose >

Re: [Twisted-Python] Migration to Git / GitHub

On Fri, Nov 13, 2015 at 6:29 PM, Glyph Lefkowitz wrote: > > > We then asked people for money based on this document. So GitHub is more > or less a done deal :-). > > If the plan is GitHub and the project is fine with that, then cool. If there is time, I would recommend that the project take a qu

Re: [Twisted-Python] Migration to Git / GitHub

> On Nov 13, 2015, at 6:07 PM, Jonathan Vanasco wrote: > > Two notes: > > 1. Have you considered bitbucket? I personally prefer github, but I know > some python projects like it because of mercurial support. We wrote up a proposal for the fellowship at the beginning of this year,

Re: [Twisted-Python] Migration to Git / GitHub

Two notes: 1. Have you considered bitbucket? I personally prefer github, but I know some python projects like it because of mercurial support. 2. There are a lot of projects for transitioning trac tickets to github/bitbucket via their api. You can't transition some fields (reports, comments,

Re: [Twisted-Python] Migration to Git / GitHub

> On Nov 11, 2015, at 6:10 PM, Clayton Daley wrote: > > I'm not an SVN user (only Git) so I certainly don't care. I proposed it in > the other group to help facilitate a transitional period. That would give > users time to wrap up any work in SVN and transition to Git at their own > pace..

Re: [Twisted-Python] Migration to Git / GitHub

I'm not an SVN user (only Git) so I certainly don't care. I proposed it in the other group to help facilitate a transitional period. That would give users time to wrap up any work in SVN and transition to Git at their own pace... rather than on a specific drop dead date. Maybe that's not a probl

Re: [Twisted-Python] Migration to Git / GitHub

> On Nov 11, 2015, at 2:47 PM, Clayton Daley wrote: > > +1 > > Maybe this is old news, but I stumbled upon Subgit when poking around for > another open source project. It says you can commit to both for as long as > you like and... it's free to use for open source: > > http://www.subgit.com

Re: [Twisted-Python] Migration to Git / GitHub

+1 Maybe this is old news, but I stumbled upon Subgit when poking around for another open source project. It says you can commit to both for as long as you like and... it's free to use for open source: http://www.subgit.com/pricing.html Clayton Daley On Wed, Nov 11, 2015 at 4:40 PM, Adi Roiban

[Twisted-Python] Migration to Git / GitHub

Hi, So I am bringing this to the list for a greater audience and to reach all borders and timezones :) I think that most people agree that Twisted should get rid of SVN and move to Git. General rules by Glyph as they were sent to me :) Development can't stop, the website can't go down, and we