[sage-devel] Re: Indexing Sage external packages (was: Giving back to the community)

2016-12-13 Thread Paul Leopardi
On Tuesday, 29 November 2016 05:57:09 UTC+11, Samuel Lelievre wrote: > > Dear sage-devel, > > This is a follow-up to a discussion on sage-support [0] in which > the original poster asks a question which I will summarize as: > > Having written some amount of Sage code for a project, > how can I

Re: [sage-devel] Re: Indexing Sage external packages (was: Giving back to the community)

2016-12-08 Thread Erik Bray
On Wed, Dec 7, 2016 at 7:41 PM, William Stein wrote: > On Wed, Dec 7, 2016 at 7:41 AM, Jeroen Demeyer wrote: >> On 2016-12-07 14:52, Kwankyu Lee wrote: >>> >>> What do you think? >> >> >> Why do this? I guess this will mostly lead to bitrotting code that would >> better be merged into Sage. > > "

Re: [sage-devel] Re: Indexing Sage external packages (was: Giving back to the community)

2016-12-07 Thread William Stein
On Wed, Dec 7, 2016 at 1:42 PM, Travis Scrimshaw wrote: > > > On Wednesday, December 7, 2016 at 9:41:32 AM UTC-6, Jeroen Demeyer wrote: >> >> On 2016-12-07 14:52, Kwankyu Lee wrote: >> > What do you think? >> >> Why do this? I guess this will mostly lead to bitrotting code that would >> better be

Re: [sage-devel] Re: Indexing Sage external packages (was: Giving back to the community)

2016-12-07 Thread Travis Scrimshaw
On Wednesday, December 7, 2016 at 9:41:32 AM UTC-6, Jeroen Demeyer wrote: > > On 2016-12-07 14:52, Kwankyu Lee wrote: > > What do you think? > > Why do this? I guess this will mostly lead to bitrotting code that would > better be merged into Sage. > If it is an independent package, then ther

Re: [sage-devel] Re: Indexing Sage external packages (was: Giving back to the community)

2016-12-07 Thread William Stein
On Wed, Dec 7, 2016 at 1:14 PM, Kwankyu Lee wrote: > On Wednesday, December 7, 2016 at 4:41:32 PM UTC+1, Jeroen Demeyer wrote: >> >> >> Why do this? I guess this will mostly lead to bitrotting code that would >> better be merged into Sage. > > > It seems a nice way to share code that enhances Sage

Re: [sage-devel] Re: Indexing Sage external packages (was: Giving back to the community)

2016-12-07 Thread Kwankyu Lee
On Wednesday, December 7, 2016 at 4:41:32 PM UTC+1, Jeroen Demeyer wrote: > > > Why do this? I guess this will mostly lead to bitrotting code that would > better be merged into Sage. > It seems a nice way to share code that enhances Sage in special areas, with least "friction". Users (and devel

Re: [sage-devel] Re: Indexing Sage external packages (was: Giving back to the community)

2016-12-07 Thread William Stein
On Wed, Dec 7, 2016 at 7:41 AM, Jeroen Demeyer wrote: > On 2016-12-07 14:52, Kwankyu Lee wrote: >> >> What do you think? > > > Why do this? I guess this will mostly lead to bitrotting code that would > better be merged into Sage. "According to the CRAN website, Currently, the CRAN package reposit

Re: [sage-devel] Re: Indexing Sage external packages (was: Giving back to the community)

2016-12-07 Thread Jeroen Demeyer
On 2016-12-07 14:52, Kwankyu Lee wrote: What do you think? Why do this? I guess this will mostly lead to bitrotting code that would better be merged into Sage. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

[sage-devel] Re: Indexing Sage external packages (was: Giving back to the community)

2016-12-07 Thread Kwankyu Lee
Hi, I am thinking of developing an external package in the direction of "experimental feature branches" among the work flows described in https://wiki.sagemath.org/CodeSharingWorkflow. Examples for this work flow, I think, could be found in the numerous track tickets with milestone "sage