-
Notifications
You must be signed in to change notification settings - Fork 134
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
Comments
@nodejs/moderation |
We can move the documents related to core maintance into the doc directory and the rest into the website. |
Or if they are not up to date anymore, just archive them in a repo? |
I'm good with preserving the content in an archived repo and deleting the wiki |
BTW the wiki can be cloned with https://github.com/nodejs/node.wiki.git |
@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 |
@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! |
I was in doubt as I do not know C++ conventions there. Would |
Or maybe just |
Done) |
Added CC agenda, as this is likely something the CommComm would be interested in discussing. |
@Trott Can we ping @nodejs/tsc and if there are no objections take it off the tsc agenda? |
@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. |
@Trott I think this can be closed now? |
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. |
No rush from my perspective, I thought we were done, but if there are additional steps leaving it open makes sense to me. |
Wiki has been archived at https://github.com/nodejs/wiki-archive and disabled on the main repo. Thanks everyone! |
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:
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
The text was updated successfully, but these errors were encountered: