docs: make postject ready for transferring to the nodejs org

nodejs / postject

Easily inject arbitrary read-only resources into executable formats (Mach-O, PE, ELF) and use it at runtime.

Other

187 stars 14 forks source link

docs: make postject ready for transferring to the nodejs org #57

Closed RaisinTen closed 2 years ago

RaisinTen commented 2 years ago

This change adds a CODE_OF_CONDUCT.md file and a CONTRIBUTING.md file to the project. This is a requirement for transferring as documented in: https://github.com/nodejs/admin/blob/a99c444662467d596753affb2ce192250f4f4b6c/transfer-repo-into-the-org.md#step-1-get-the-repository-ready.

Refs: https://github.com/nodejs/admin/issues/739 Signed-off-by: Darshan Sen raisinten@gmail.com

RaisinTen commented 2 years ago

Merging this without reviews so that we can unblock https://github.com/nodejs/admin/issues/739 without waiting for a full day because we had consensus on doing this. Further improvements can be done in separate PRs.

jviotti commented 2 years ago

Sounds good!

jviotti commented 2 years ago

@RaisinTen Does this mean its 100% ready for transfer? Let me know once all its done so I can trigger the transfer conversation.

RaisinTen commented 2 years ago

@jviotti code wise, yes. Regarding acceptance in the nodejs org, we would need to wait for 72 hours after https://github.com/nodejs/admin/issues/739#issuecomment-1290170436 was posted. If there are no objections, then we would be 100% ready for the transfer.

RaisinTen commented 2 years ago

@jviotti 100% ready now. Could you help me transfer the repo? Seems like the "Transfer" option isn't showing up in the repo settings for some reason: