Re: Reviving watersprings.org.

[Warren Kumari <[e-mail]>]

On Wed, Jul 2, 2014 at 3:13 PM, Elwyn Davies <[e-mail]> wrote:
> Hi.
>
> I also quite liked the watersprings interface and was saddened by its
> demise.  However, Henrik's draft searching scheme does most of what I
> need and the interface at tools.ietf.org/html/draft... gives you the
> access to all the versions and output renderings.
>
> The only thing lacking is the ability to have a nicely formatted and
> resonably compact list of all the drafts ever made starting with a given
> letter.  Useful for idle browsing and finding drafts you can't quite
> remember the title or authors of.

Well, I finally had a chance to poke at this -- I moved everything
over to a new VM and fixed it there (instead of poking at the existing
one). I never really used the original one, so I'm not sure if I fixed
/ reimplemented all the features.

I also updated some things - the original one was doing some fancy FTP
parsing, which I couldn't really see the point of, so I replaced it
with rsync. Oh, this also didn't update since ~2011, will see if I can
backfill sometime...

Anyway, if folk would like to see the new version, it is at
http://watersprings.snozzages.com -- once if finished futzing with it
I'll change the DNS.


>
> Warren: If you have time and enthusiasm I'd be inclined to see if a
> couple of extra screens could be added to what we have already rather
> than reimplementating a separate Watersprings clone since the back end
> is already in place.

This was easier, although it did mean relearning Perl -- will look at
reimplementing on the IETF site sometime.


W
>
> I don't think that putting back what Watersprings had exactly would give
> you any more ancient history.  I seem to remember that it didn't have
> drafts earlier than about 1995, but it's a long time since I checked
> that ;-). I did when I was looking for Nimrod routing history and other
> stuff for the routing history RFC.
>
> The current tool has a smattering of moderately ancient history already:
>
> Some of the suggestions for IPng are there:
> http://tools.ietf.org/html/draft-crocker-ip-encaps-01
> http://tools.ietf.org/html/draft-deering-sip-00
> (The REAL SIP!)
>
> but I suspect the list is incomplete - however unless the file archives
> are lurking in some server, I don't know how we would know (did
> ietf-announce exist in those days and would it help?)
>
> Regards,
> Elwyn
>
>
>
> On Wed, 2014-07-02 at 19:15 +0100, Adrian Farrel wrote:
>> Interesting, Warren.
>>
>> I used to use waterspring and still have an annoying bookmark that autocompletes when I start to type www.wat...
>>
>> At the time that waterspring was set up we didn't archive old versions of I-Ds and once an I-D had expired it disappeared (related issues, but separately annoying). That is no longer the case, so the (UI aside) the main residual value would be retrieving the archive of old I-Ds and I am not so sure how useful that is, but archivists and IPR lawyers might comment).
>>
>> Adrian
>>
>> > -----Original Message-----
>> > From: ietf [mailto:[e-mail]] On Behalf Of Warren Kumari
>> > Sent: 02 July 2014 19:09
>> > To: [e-mail] Disgust
>> > Subject: Reviving watersprings.org.
>> >
>> > Hi there all,
>> >
>> > A number of years ago there was a site called watersprings.org which
>> > archived Internet Drafts and RFCs and provided some interesting
>> > linking between them.
>> > I never used it, but apparently a number of folk really liked the
>> > interface / etc.
>> >
>> > The site was hosted in Japan and the creator shut it down to conserve
>> > power after the 2011 tsunami. I provided him a VM (on a machine that
>> > nLayer / Richard Steenbergen hosts for me), and we started migrating
>> > over to it. Unfortunately, he no longer has the time / resources to
>> > run the site, and we never finished the migration / the scripts
>> > haven't run since then.
>> >
>> > Anyway, I've offered to take over maintaining the VM, try figure out
>> > how it all works, upgrade it, finish the migration, etc.
>> > Before spending the time on this though, I figured I should check if
>> > folk still want it / think that it will be a useful resource. The time
>> > investment will be fairly significnat, but happy to do it if folk will
>> > use it...
>>
>