-
Notifications
You must be signed in to change notification settings - Fork 135
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
Transferring ownership of node-vscode-config #260
Comments
The repo is already moved under nodejs org, and I don't see an option to transfer it back to myself. |
can multiple editor configs be held in one repo? a repo just for vscode seems a bit extreme. |
The repo needs a LICENSE file and a Code of Conduct. |
@devsnek Yeah, we can rename the repo (to node-editor-config for example) and create a folder for each editor where configs can be stored? |
@Trott Is there a recommendation for adding LICENSE I've added link to admin CODE_OF_CONDUCT in PR nodejs/node-code-ide-configs#2 |
@trivikr Looks like the PR with that information has not yet landed. However, maybe https://github.com/nodejs/admin/pull/68/files will be helpful? It doesn't say what LICENSE is acceptable, but the main repo uses MIT license, so I imagine that would be an easy 👍. |
Added MIT License in nodejs/node-code-ide-configs#3 |
A tad bit of name bikeshedding: I suggest |
It seems like perhaps this should be closed. Feel free to re-open (or leave a comment requesting that it be re-opened) if you disagree. I'm just tidying up and not acting on a super-strong opinion or anything like that. |
The repo was renamed to |
Hi,
Earlier discussions in https://github.com/orgs/nodejs/teams/collaborators/discussions/58
The repo is already moved to nodejs as I followed the steps in documentation, and wasn't blocked. I wasn't aware of the policy which @Trott shared and following it now.
History:
Proposal:
Regards,
Trivikram
The text was updated successfully, but these errors were encountered: