search

npm / www

community space for the npm website
https://npm.community
69 stars 48 forks source link

Please make the old issues available #9

Closed JesseWeinstein closed 8 years ago

JesseWeinstein commented 8 years ago

There were over 700 issues in the old repo, including various relevant historical information about the growth and decision-making of npm. It's a shame to have all that historical data made inaccessible. I strongly encourage you to export a copy of it (there are many scripts floating around, I can provide specifics if wanted), and make that available somewhere (either on the npm website, or simply upload it to the Internet Archive as an item).

jefflembeck commented 8 years ago

@JesseWeinstein This is a great idea, but is a low priority for us. We’re definitely not opposed, though. If somebody has a script that can help us grab all of the old issues and put them in a file (json works nicely), we’d be happy to put it in here for downloading.

JesseWeinstein commented 8 years ago

Great! I can certainly understand it being low priority, and I don't think it's particularly urgent, either -- but I would be glad for it to be done eventually.

Regarding scripts, my first thought is https://github.com/joeyh/github-backup . I haven't used it personally, though, so there may be a better alternative available. I'll ask around.

ben-eb commented 8 years ago

Please can you make these available? It's not exactly encouraging to see threads like these lose all context because the issue has been erased. Now, because I don't have a reference of anything in this thread I don't know if this was closed, what priority it had/has, any workarounds, or how many people experienced this issue. It also discourages me from creating a new issue because what's to stop you guys deleting this repository as well and starting over again?

For what it's worth, I'm experiencing this bug still. 😐

JesseWeinstein commented 8 years ago

That is a good example of why this is important. It would be most easily solved by just making the repo public again, and adding a prominent notice: "This is for HISTORICAL REFERENCE ONLY." But I suppose there are presumably some reasons why that wasn't considered an acceptable solution.

JesseWeinstein commented 8 years ago

Also, another possible solution would be to make the repo public again for a short, designated period, and asking the Internet Archive (or ArchiveTeam) to scrape a copy of the issues into the Wayback Machine. Then the repo could be made private again, but the material could still be found at least by those who know to look in the Wayback Machine.

JesseWeinstein commented 8 years ago

Could I get this re-opened, so it doesn't get lost? If I don't get a response in about a month, I'll open a new issue requesting that this one be re-opened...