[seqfan] Re: something went wrong with new oeis this afternoon

Alexander P-sky apovolot at gmail.com
Sun Nov 14 01:06:09 CET 2010


>(it is possible a few edits may be lost, but hopefully not many)

Above supports my suggestion to implement emails sent from OEIS to
authors/editors, reflecting change of status and containing changes
made.

ARP
==============================================================
---------- Forwarded message ----------
From: Alexander P-sky <apovolot at gmail.com>
Date: Fri, 12 Nov 2010 15:31:50 -0500
Subject: Re: [seqfan] Re: Broken links
To: njas at research.att.com
Cc: rsc at swtch.com, david at research.att.com

>I don't think we want to send out email for each new sequence.
> That just makes things more complicated.
Complicated in what sense and for whom ?
For the implementers/maintainers of the OEIS or for the participants/users ?

Besides for asking for bringing back that feature for the backwards
compatibility reason alone, those confirmation emails also in the
previous OEIS format served authors to retain on their end as some
way of the history record keeping, which I am hoping many other
submitters besides me would appreciate ?
Typically in general practice of developing software applications, -
the factor of the convenience for users trumps inconvenience of
implementers ...
Also besides initial "submitting" event I was hoping that email
notifications of the "change of state", such  as "being edited",
"rejected" or "approved" will be issued ?
How else the submitter will know what is happening with his submission ?

ARP
========================================================
On 11/12/10, N. J. A. Sloane <njas at research.att.com> wrote:
>>Date: Fri, 12 Nov 2010 10:15:16 -0500
>>Subject: Re: [seqfan] Re: Broken links
>>From: Russ Cox <rsc at swtch.com>
>>To: Alexander P-sky <apovolot at gmail.com>
>>Cc: "N. J. A. Sloane" <njas at research.att.com>
>>On Fri, Nov 12, 2010 at 10:07 AM, Alexander P-sky <apovolot at gmail.com>
>> wrote:
>>> Looks like the event of the initial creation of the draft for the new
>>> sequence is not confirmed by sending the email to the author ?
>>I understood the purpose of the email as being
>>a copy for the author in case the entry was lost
>>or needed further editing or the like, because there
>>was no other immediate feedback.  In the new
>>OEIS, the immediate feedback is that you can
>>view the draft as soon as you click "Save Changes."
>
>>We could add an auto-email, of course, but
>>it seemed less important in this new immediate
>>gratification world.
>
>>Russ
>
> I don't think we want to send out email for each new sequence.
> That just makes things more complicated.
> When you submit a sequence, it goes straight into the OEIS now.
>
> Neil
On 11/13/10, N. J. A. Sloane <njas at research.att.com> wrote:
>
> It looks like at some time this afternoon, the OEIS
> changed back to a version from some hours earlier.
>
> We are working on the problem, but it
> may not be resolved until tomorrow (it is possible
> a few edits may be lost, but hopefully not many)
>
> Until it is resolved, maybe it would
> be better not to send in any new edits or sequences
>
>  Best regards
>  			 Neil
>
>
> _______________________________________________
>
> Seqfan Mailing list - http://list.seqfan.eu/
>




More information about the SeqFan mailing list