Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Poll: Making sage-mode a standard package
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ivan Andrus  
View profile   Translate to Translated (View Original)
 More options May 28 2012, 6:30 am
From: Ivan Andrus <darthand...@gmail.com>
Date: Mon, 28 May 2012 12:30:40 +0200
Local: Mon, May 28 2012 6:30 am
Subject: Re: [sage-devel] Re: Poll: Making sage-mode a standard package
On May 26, 2012, at 7:31 PM, Benjamin Jones wrote:

> On Sat, May 26, 2012 at 10:23 AM, Ivan Andrus <darthand...@gmail.com> wrote:
>> On May 26, 2012, at 7:09 PM, Benjamin Jones wrote:
>>> On Sat, May 26, 2012 at 6:55 AM, Ivan Andrus <darthand...@gmail.com> wrote:

>>>> No offense taken.  Who knows what's going to happen after I graduate for
>>>> example—maybe I'll get a full time job fixing bugs in Sage, or maybe I'll be
>>>> flipping burgers. :-)

>>>> It's important to remember that if it's standard someone _has_ to maintain
>>>> it.  Of course, it's also more likely that someone _will_ maintain it.

>>>> -Ivan

>>> From the point of view that making sage-mode a standard package would
>>> increase the likelihood that it is maintained, I would support it
>>> being included as a standard package.

>> Do you say that because you feel it hasn't been maintained well, or that it might not be in the future since the original author has moved on?

>> -Ivan

> I said that in the spirit that I think sage-mode is a useful package
> and any steps we can take to ensure that useful packages continue to
> be well maintained is a good thing. I haven't been using it for all
> that long, so I can't comment on if it has or hasn't been maintained
> well in the past. As for the future, who knows, but making it a
> standard package will increase its chances to thrive compared to
> making it an optional package.

> What is your opinion as the current maintainer?

Unless I'm mistaken, if it becomes standard then someone (probably me) has to volunteer to maintain it for at least 2 years.  I'm okay with that since I'll be maintaining the Mac and iPhone apps for probably that long.  Of course I would prefer to not commit in case things change in the future.  :-)  But I would be willing to do it.

If I doesn't go standard and things don't work out for me after graduation in a way that I can spend a "lot" of time on sage, then I probably won't maintain it other than perhaps helping track down issues (i.e. no new features, code cleanup etc.).  Usually emacs lisp code is pretty easy to debug so I don't think it would take too much time.  Of course even if it does go standard there is no guarantee of new features, but it would be slightly more likely.  So in the end it may not making too much difference.

Also, do there need to be automated tests to become standard?  If so then someone would have to write them.  I would _love_ to have some tests for sage-mode, especially since we will have to support fgallina's rewrite of python.el pretty soon [1].  I certainly couldn't write them really soon (I'm already way behind on the iPhone app), but it would be a good reason to keep the ticket open.

-Ivan

[1] https://bitbucket.org/gvol/sage-mode/issue/1/support-pythonel-by-fgal...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.