Re: [sage-devel] Re: What to do with research-y code.

2012-11-28 Thread David Kirkby
On 27 November 2012 15:12, kcrisman wrote: > How hard would it be to "import contrib.foo as modular.foo" > without causing problems? Because of course one wouldn't want one's > research stuff to have to live in a different namespace if it was for Sage > proper stuff. This reminds me of a situati

Re: [sage-devel] Re: What to do with research-y code.

2012-11-27 Thread William Stein
On Mon, Nov 26, 2012 at 11:48 PM, Burcin Erocal wrote: > On Tue, 27 Nov 2012 01:53:31 +0800 > P Purkayastha wrote: > > >> I think the Sage community could quickly expand and there could be >> tens, if not hundreds, of git development branches once the switch to >> git occurs. It would be quite h

Re: [sage-devel] Re: What to do with research-y code.

2012-11-27 Thread David Kirkby
On 27 November 2012 09:58, Simon King wrote: > Hi David, Hi Simon. > On 2012-11-27, David Kirkby wrote: >> I feel the way to solve this is to have community contributed >> packages, which don't form part of the core of Sage, but can be >> installed by anyone if they wish to. Projects like R, Pe

Re: [sage-devel] Re: What to do with research-y code.

2012-11-27 Thread Robert Bradshaw
On Mon, Nov 26, 2012 at 11:48 PM, Burcin Erocal wrote: > On Tue, 27 Nov 2012 01:53:31 +0800 > P Purkayastha wrote: > > >> I think the Sage community could quickly expand and there could be >> tens, if not hundreds, of git development branches once the switch to >> git occurs. It would be quite h

Re: [sage-devel] Re: What to do with research-y code.

2012-11-27 Thread Robert Bradshaw
On Mon, Nov 26, 2012 at 9:53 AM, P Purkayastha wrote: > On 11/27/2012 01:19 AM, Robert Bradshaw wrote: >> >> This is somewhat a continuation of the "permutations...again" thread, >> but I think the topic is much broader than that. Over time >> contributing Sage has become increasingly bureaucratic

Re: [sage-devel] Re: What to do with research-y code.

2012-11-27 Thread Robert Bradshaw
On Mon, Nov 26, 2012 at 9:46 AM, kcrisman wrote: > > Great thoughts, Robert; I don't know if it will go anywhere, but it's worth > revisiting every so often. > >> >> >> Raising the bar on Sage code quality creates this limbo area of code >> that's good enough to be shared/built upon, but not good

Re: [sage-devel] Re: What to do with research-y code.

2012-11-26 Thread Burcin Erocal
On Tue, 27 Nov 2012 01:53:31 +0800 P Purkayastha wrote: > I think the Sage community could quickly expand and there could be > tens, if not hundreds, of git development branches once the switch to > git occurs. It would be quite hard to keep track of all the different > branches and the individ