Archive the ECMAScript wiki

[littledan]

TC39 used a wiki for design docs and development through the ES6 era, before moving to GitHub. For a while, the ECMAScript wiki at http://wiki.ecmascript.org has been available just through Internet Archive. The wiki is very important for understanding the design decisions of the JavaScript language we have today. Is anyone interested in archiving it and placing it on GitHub?

[allenwb]

@dherman is probably the best source of info on prior work in this regard.

I've found that once I got into the habit of using it, the Internet Archive has proven to work really well for accessing wiki.ecmascript.org.

I'm actually more concern about preserving the content of bugs.ecmascript.org as that isn't replicated in the Internet Archive.

[allenwb]

@dherman is probably the best source of info on prior work in this regard.

I've found that once I got into the habit of using it, the Internet Archive has proven to work really well for accessing wiki.ecmascript.org.

I'm actually more concern about preserving the content of bugs.ecmascript.org as that isn't replicated in the Internet Archive.

[littledan]

My biggest complaint about using Internet Archive, apart from my fear about future unavailability, is that I don't know how to search it. Anyway, it sounds really urgent to archive bugs.ecmascript.org!

[littledan]

My biggest complaint about using Internet Archive, apart from my fear about future unavailability, is that I don't know how to search it. Anyway, it sounds really urgent to archive bugs.ecmascript.org!

[bterlson]

It should be archived. Why is this a 262 bug, though?

[bterlson]

It should be archived. Why is this a 262 bug, though?

[littledan]

@bterlson Where else should I file it? I don't want to put it in the Reflector, as this would be a good project for an external volunteer.

[littledan]

@bterlson Where else should I file it? I don't want to put it in the Reflector, as this would be a good project for an external volunteer.

[allenwb]

How about as an issue on the archives repository https://github.com/tc39/archives

So, it can be out of the way and ignored. 😜

[allenwb]

How about as an issue on the archives repository https://github.com/tc39/archives

So, it can be out of the way and ignored. 😜

[bterlson]

@allenwb seems good to me. Out of the way and ignored is bad but doesn't everyone subscribe to all notifications from the tc39 org?? :-P

I just don't want to use these issues for general discussion is why I asked. @littledan if you want it to remain open here, that's fine.

[bterlson]

@allenwb seems good to me. Out of the way and ignored is bad but doesn't everyone subscribe to all notifications from the tc39 org?? :-P

I just don't want to use these issues for general discussion is why I asked. @littledan if you want it to remain open here, that's fine.

[littledan]

@bterlson

Out of the way and ignored is bad but doesn't everyone subscribe to all notifications from the tc39 org?? :-P

Offtopic, but how do you do that? (Good thing to put in a how-we-work document...)

[littledan]

@bterlson

Out of the way and ignored is bad but doesn't everyone subscribe to all notifications from the tc39 org?? :-P

Offtopic, but how do you do that? (Good thing to put in a how-we-work document...)

[annevk]

You need to be a member of the org as far as I know. Non-members need to look if new repositories get added and then watch them. Looking for new public repositories can probably be automated in some fashion, but I don't think there's a service for it.

[annevk]

You need to be a member of the org as far as I know. Non-members need to look if new repositories get added and then watch them. Looking for new public repositories can probably be automated in some fashion, but I don't think there's a service for it.