Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wiki Management #525

Closed
Trott opened this issue Apr 19, 2018 · 17 comments
Closed

Wiki Management #525

Trott opened this issue Apr 19, 2018 · 17 comments

Comments

@Trott
Copy link
Member

Trott commented Apr 19, 2018

The wiki has been locked so only Collaborators can edit it.

There seems to be significant support for taking each document there and doing one of the following depending on what's most appropriate for that particular document:

  • add its contents to the website
  • add its contents to the docs directory in the repo
  • delete it

We don't have any concrete rules around wiki governance so I wanted to run this past the TSC (putting it on the agenda), CommComm, and docs folks.

@nodejs/tsc @nodejs/community-committee @nodejs/documentation

@Trott
Copy link
Member Author

Trott commented Apr 19, 2018

@nodejs/moderation

@joyeecheung
Copy link
Member

We can move the documents related to core maintance into the doc directory and the rest into the website.

@joyeecheung
Copy link
Member

Or if they are not up to date anymore, just archive them in a repo?

@jasnell
Copy link
Member

jasnell commented Apr 20, 2018

I'm good with preserving the content in an archived repo and deleting the wiki

@joyeecheung
Copy link
Member

BTW the wiki can be cloned with https://github.com/nodejs/node.wiki.git

@vsemozhetbyt
Copy link

@joyeecheung Only not on Windows due to How to migrate from ev_io_* to uv_poll_* for IO polling:

error: unable to create file node-v0.x-archive/How-to-migrate-from-ev_io_*-to-uv_poll_*-for-IO-polling.md: Invalid argument
fatal: unable to checkout working tree

It seems we need to rename it first without * forbidden in Windows fs.

@Trott
Copy link
Member Author

Trott commented Apr 23, 2018

@vsemozhetbyt I don't think there's anything stopping any Collaborator from renaming it so go ahead and rename it to something that works for Windows!

@vsemozhetbyt
Copy link

I was in doubt as I do not know C++ conventions there. Would ev_io_... to uv_poll_... be OK?

@richardlau
Copy link
Member

Or maybe just Migrating IO polling from libev to libuv?

@vsemozhetbyt
Copy link

Done)

@bnb bnb added the cc-agenda label Apr 23, 2018
@bnb
Copy link
Contributor

bnb commented Apr 23, 2018

Added CC agenda, as this is likely something the CommComm would be interested in discussing.

@fhinkel
Copy link
Member

fhinkel commented Apr 23, 2018

@Trott Can we ping @nodejs/tsc and if there are no objections take it off the tsc agenda?

@Trott
Copy link
Member Author

Trott commented Apr 24, 2018

@nodejs/tsc Seems like the plan is to move the wiki to a repository for archiving and then remove the wiki from the nodejs/node repo. Any documents in the wiki that need to be restored or preserved can be moved to the docs directory in nodejs/node or the website or anywhere else appropriate. Please leave a comment here if you object to this plan. Otherwise, I'll assume consensus and move forward.

@mhdawson
Copy link
Member

mhdawson commented May 9, 2018

@Trott I think this can be closed now?

@Trott
Copy link
Member Author

Trott commented May 10, 2018

I'd prefer it stay open until we actually decommission the wiki, but I won't make a fuss if anyone feels strongly that it ought to be closed now.

@mhdawson
Copy link
Member

No rush from my perspective, I thought we were done, but if there are additional steps leaving it open makes sense to me.

@Trott
Copy link
Member Author

Trott commented May 11, 2018

Wiki has been archived at https://github.com/nodejs/wiki-archive and disabled on the main repo. Thanks everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants