Re: [matplotlib-devel] git migration this weekend

On Sun, Feb 27, 2011 at 9:45 AM, Darren Dale wrote: > On Sun, Feb 27, 2011 at 8:32 AM, Darren Dale wrote: >> If we are not convinced that github issues provides >> everything we need, I think we should provide feedback to the github >> devs and stick with sourceforge for the time being. > > Here

Re: [matplotlib-devel] git migration this weekend

On Sun, Feb 27, 2011 at 8:32 AM, Darren Dale wrote: > If we are not convinced that github issues provides > everything we need, I think we should provide feedback to the github > devs and stick with sourceforge for the time being. Having said that, depending on how the github devs respond, we mig

Re: [matplotlib-devel] git migration this weekend

On Sun, Feb 27, 2011 at 8:32 AM, Darren Dale wrote: > If we are not convinced that github issues provides > everything we need, I think we should provide feedback to the github > devs and stick with sourceforge for the time being. Here is a copy of a message I just sent to supp...@github.com. If

Re: [matplotlib-devel] git migration this weekend

On Sun, Feb 27, 2011 at 7:46 AM, Jouni K. Seppänen wrote: > Darren Dale writes: > >> On Sat, Feb 26, 2011 at 5:58 PM, Eric Firing wrote: >>> On 02/26/2011 10:54 AM, Darren Dale wrote: >>> >>> The submitter info is lost? >>> And when it was originally submitted? >> >> No, I can improve it so this

Re: [matplotlib-devel] git migration this weekend

Darren Dale writes: > On Sat, Feb 26, 2011 at 5:58 PM, Eric Firing wrote: >> On 02/26/2011 10:54 AM, Darren Dale wrote: >> >> The submitter info is lost? >> And when it was originally submitted? > > No, I can improve it so this information is included. That's clearly in the xml file, except tha

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 6:14 PM, Eric Firing wrote: > It is impressive, and improves some aspects, but I don't see that it > makes the github tracker usable for new tickets.  I don't see any > facility for attaching a file--is this correct?  We really want users > with problems and suggestions to

Re: [matplotlib-devel] git migration this weekend

On 02/26/2011 01:44 PM, Fernando Perez wrote: > On Sat, Feb 26, 2011 at 3:24 PM, Darren Dale wrote: >> >> I agree that the github interface is not great. The github devs seem >> to know that everybody complains about it. > > Yup. I hold on to the hope that, because it's so egregiously, > painfull

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 3:24 PM, Darren Dale wrote: > > I agree that the github interface is not great. The github devs seem > to know that everybody complains about it. Yup. I hold on to the hope that, because it's so egregiously, painfully broken and braindead and it stands out so badly in com

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 6:15 PM, Benjamin Root wrote: > Github has been a wonderful tool for *developers*, but for > users of projects, I haven't seen the amount of sophistication and polish > that sourceforge has. > > I am personally fine with continuing to use sourceforge for the tracker (I > kn

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 5:58 PM, Eric Firing wrote: > On 02/26/2011 10:54 AM, Darren Dale wrote: >> On Sat, Feb 26, 2011 at 3:52 PM, Darren Dale  wrote: >>> On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing  wrote: On 02/26/2011 09:26 AM, Darren Dale wrote: > On Wed, Feb 16, 2011 at 2:19 PM, E

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 4:58 PM, Eric Firing wrote: > On 02/26/2011 10:54 AM, Darren Dale wrote: > > On Sat, Feb 26, 2011 at 3:52 PM, Darren Dale wrote: > >> On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing > wrote: > >>> On 02/26/2011 09:26 AM, Darren Dale wrote: > On Wed, Feb 16, 2011 at 2:1

Re: [matplotlib-devel] git migration this weekend

On 02/26/2011 10:54 AM, Darren Dale wrote: > On Sat, Feb 26, 2011 at 3:52 PM, Darren Dale wrote: >> On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing wrote: >>> On 02/26/2011 09:26 AM, Darren Dale wrote: On Wed, Feb 16, 2011 at 2:19 PM, Eric Firingwrote: > On 02/16/2011 08:38 AM, Darren D

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 3:52 PM, Darren Dale wrote: > On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing wrote: >> On 02/26/2011 09:26 AM, Darren Dale wrote: >>> On Wed, Feb 16, 2011 at 2:19 PM, Eric Firing  wrote: On 02/16/2011 08:38 AM, Darren Dale wrote: > On Wed, Feb 16, 2011 at 12:39 PM,

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing wrote: > On 02/26/2011 09:26 AM, Darren Dale wrote: >> On Wed, Feb 16, 2011 at 2:19 PM, Eric Firing  wrote: >>> On 02/16/2011 08:38 AM, Darren Dale wrote: On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez     wrote: > are you guys planning

Re: [matplotlib-devel] git migration this weekend

On 02/26/2011 09:26 AM, Darren Dale wrote: > On Wed, Feb 16, 2011 at 2:19 PM, Eric Firing wrote: >> On 02/16/2011 08:38 AM, Darren Dale wrote: >>> On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez >>> wrote: are you guys planning on transfering the old bugs to github? >>> >>> Probably at s

Re: [matplotlib-devel] git migration this weekend

On Wed, Feb 16, 2011 at 2:19 PM, Eric Firing wrote: > On 02/16/2011 08:38 AM, Darren Dale wrote: >> On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez   >> wrote: >>> are you guys planning on transfering the old bugs to github? >> >> Probably at some point. >> >>> As I >>> mentioned, I have code lyi

Re: [matplotlib-devel] git migration this weekend

On Wed, Feb 16, 2011 at 7:57 PM, Michael Droettboom wrote: > On 02/16/2011 03:53 PM, John Hunter wrote: >> On Wed, Feb 16, 2011 at 2:47 PM, Michael Droettboom  wrote: >>> Not sure Sourceforge allows custom hooks in SVN. >> We have a couple in place already >> >> >> https://sourceforge.net/project/

Re: [matplotlib-devel] git migration this weekend

On 02/16/2011 03:53 PM, John Hunter wrote: > On Wed, Feb 16, 2011 at 2:47 PM, Michael Droettboom wrote: >> Not sure Sourceforge allows custom hooks in SVN. > We have a couple in place already > > > https://sourceforge.net/project/admin/svn.php?group_id=80706 Yes. But those aren't custom -- SF onl

Re: [matplotlib-devel] git migration this weekend

On Wed, Feb 16, 2011 at 2:47 PM, Michael Droettboom wrote: > Not sure Sourceforge allows custom hooks in SVN. We have a couple in place already https://sourceforge.net/project/admin/svn.php?group_id=80706 -- The ultima

Re: [matplotlib-devel] git migration this weekend

Not sure Sourceforge allows custom hooks in SVN. Mike On 02/16/2011 02:45 PM, Benjamin Root wrote: On Wed, Feb 16, 2011 at 1:30 PM, Sandro Tosi > wrote: On Wed, Feb 16, 2011 at 19:57, John Hunter mailto:jdh2...@gmail.com>> wrote: > On Wed, Feb 16, 2011 at 7:00

Re: [matplotlib-devel] git migration this weekend

On Wed, Feb 16, 2011 at 1:30 PM, Sandro Tosi wrote: > On Wed, Feb 16, 2011 at 19:57, John Hunter wrote: > > On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale wrote: > > > >> John, could you freeze the svn repo around noon on Friday? I'll > >> convert the repositories and push them up to github on Sa

Re: [matplotlib-devel] git migration this weekend

On Wed, Feb 16, 2011 at 19:57, John Hunter wrote: > On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale wrote: > >> John, could you freeze the svn repo around noon on Friday? I'll >> convert the repositories and push them up to github on Saturday. Is it >> possible to close the sourceforge bugtracker, f

Re: [matplotlib-devel] git migration this weekend

On 02/16/2011 08:38 AM, Darren Dale wrote: > On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez wrote: >> are you guys planning on transfering the old bugs to github? > > Probably at some point. > >> As I >> mentioned, I have code lying around for the upload (and to download >> from launchpad, but t

Re: [matplotlib-devel] git migration this weekend

On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale wrote: > John, could you freeze the svn repo around noon on Friday? I'll > convert the repositories and push them up to github on Saturday. Is it > possible to close the sourceforge bugtracker, feature requests, etc to > new issues as well? I did some

Re: [matplotlib-devel] git migration this weekend

On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez wrote: > are you guys planning on transfering the old bugs to github? Probably at some point. > As I > mentioned, I have code lying around for the upload (and to download > from launchpad, but that's irrelevant here).  I'm going to be mosly > offl

Re: [matplotlib-devel] git migration this weekend

Hey, On Wed, Feb 16, 2011 at 5:00 AM, Darren Dale wrote: > > John, could you freeze the svn repo around noon on Friday? I'll > convert the repositories and push them up to github on Saturday. Is it > possible to close the sourceforge bugtracker, feature requests, etc to > new issues as well? are

Re: [matplotlib-devel] git migration this weekend

On Sun, Jan 30, 2011 at 8:10 AM, Darren Dale wrote: > On Thu, Jan 27, 2011 at 9:34 PM, Darren Dale wrote: >> Hi Folks, >> >> I'm planning on freezing the sourceforge svn repository Friday evening >> at 8:00 (NY time), and moving the git repository to its new home on >> Saturday morning. >> >> If

Re: [matplotlib-devel] git migration

On Mon, Feb 7, 2011 at 5:41 PM, John Hunter wrote: > On Feb 7, 2011, at 3:17 PM, Andrew Straw wrote: > >> On 07-Feb-11 17:13, Darren Dale wrote: >>> The git migration is still on hold, pending the return of CVS service >>> at sourceforge. According to someone on the sourceforge IRC channel, >>> C

Re: [matplotlib-devel] git migration

On Feb 7, 2011, at 3:17 PM, Andrew Straw wrote: > On 07-Feb-11 17:13, Darren Dale wrote: >> The git migration is still on hold, pending the return of CVS service >> at sourceforge. According to someone on the sourceforge IRC channel, >> CVS is estimated to return this week, but it might slip

Re: [matplotlib-devel] git migration

On 07-Feb-11 17:13, Darren Dale wrote: > The git migration is still on hold, pending the return of CVS service > at sourceforge. According to someone on the sourceforge IRC channel, > CVS is estimated to return this week, but it might slip to next week. Thanks for the update. At some point, one c

Re: [matplotlib-devel] git migration this weekend

On Thu, Jan 27, 2011 at 9:34 PM, Darren Dale wrote: > Hi Folks, > > I'm planning on freezing the sourceforge svn repository Friday evening > at 8:00 (NY time), and moving the git repository to its new home on > Saturday morning. > > If you have concerns, please speak up. John discovered a problem

Re: [matplotlib-devel] git migration

On Wed, Mar 3, 2010 at 1:31 PM, Jonathan Taylor wrote: >> I am strongly in favor of keeping the entire commit history of >> trunk/matplotlib.  While the repo is large now, most of the size comes >> from data and regression test images, and the early history is largely >> code so will not add much

Re: [matplotlib-devel] git migration

> I am strongly in favor of keeping the entire commit history of > trunk/matplotlib.  While the repo is large now, most of the size comes > from data and regression test images, and the early history is largely > code so will not add much incremental size.  I suppose one of the > downsides of git i

Re: [matplotlib-devel] git migration

John Hunter wrote: > On Tue, Mar 2, 2010 at 11:41 PM, Eric Firing wrote: > >> Andrew Straw wrote: >> [...] >> >>> This is a good point. My preferred option is that we jettison all the >>> stuff that is not going to be shipped with MPL 1.0 from the git repo. >>> (More correctly - we build a

Re: [matplotlib-devel] git migration

On Wed, Mar 3, 2010 at 8:29 AM, william ratcliff wrote: > I don't want to get into a flame war over this, but if Sourceforge was > pressured into this and is having complaints and google has the same > problem, how does Github get around it?  Are they incorporated in the US or > outside?  If this

Re: [matplotlib-devel] git migration

I don't want to get into a flame war over this, but if Sourceforge was pressured into this and is having complaints and google has the same problem, how does Github get around it? Are they incorporated in the US or outside? If this is likely to become a problem, is there another service that can

Re: [matplotlib-devel] git migration

On Tue, Mar 2, 2010 at 11:41 PM, Eric Firing wrote: > Andrew Straw wrote: > [...] >> This is a good point. My preferred option is that we jettison all the >> stuff that is not going to be shipped with MPL 1.0 from the git repo. >> (More correctly - we build a git repo without that stuff ever going

Re: [matplotlib-devel] git migration

Hi, On Tue, Mar 2, 2010 at 10:17 PM, william ratcliff wrote: > I think there's a legal reason for the embargo--sourceforge apparently also > has such a policy: > http://sourceforge.net/blog/clarifying-sourceforgenets-denial-of-site-access-for-certain-persons-in-accordance-with-us-law/ > So, as a

Re: [matplotlib-devel] git migration

I think there's a legal reason for the embargo--sourceforge apparently also has such a policy: http://sourceforge.net/blog/clarifying-sourceforgenets-denial-of-site-access-for-certain-persons-in-accordance-with-us-law/

Re: [matplotlib-devel] git migration

Eric Firing wrote: > All, > > I think the git migration deserves its own thread on the devel list, so > here is a start. Explanation: the last bit of discussion was actually off-list, but because it was tacked onto a matplotlib-users list thread, and appeared there in my mailer, I failed to no

Re: [matplotlib-devel] git migration

Andrew Straw wrote: [...] > This is a good point. My preferred option is that we jettison all the > stuff that is not going to be shipped with MPL 1.0 from the git repo. > (More correctly - we build a git repo without that stuff ever going in.) > We can keep the old svn tree around and migrate the

Re: [matplotlib-devel] git migration

On Tue, Mar 2, 2010 at 11:03 PM, Matthew Brett wrote: > Hi, > > > Apart from being inflammatory, has anyone considered code.google.com(GC) as > > a solution? > > ;) - speaking as someone with no right to offer an opinion - please, > no. Google blocks Cuba from google code completely, for no obv

Re: [matplotlib-devel] git migration

Hi, > Apart from being inflammatory, has anyone considered code.google.com (GC) as > a solution? ;) - speaking as someone with no right to offer an opinion - please, no. Google blocks Cuba from google code completely, for no obvious reason, and a) that seems to me quite wrong and outside the s

Re: [matplotlib-devel] git migration

On Tue, Mar 2, 2010 at 9:17 PM, Andrew Straw wrote: > Eric Firing wrote: > > All, > > > > I think the git migration deserves its own thread on the devel list, so > > here is a start. > > > To the uninitiated - a decision is being made that MPL is moving to git > and github. We hope that this move

Re: [matplotlib-devel] git migration

Eric Firing wrote: > All, > > I think the git migration deserves its own thread on the devel list, so > here is a start. > To the uninitiated - a decision is being made that MPL is moving to git and github. We hope that this move will foster greater contributions from the community and a blurri