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

Transfer stduhpf/caritat into the nodejs org #805

Closed
aduh95 opened this issue Jun 14, 2023 · 6 comments
Closed

Transfer stduhpf/caritat into the nodejs org #805

aduh95 opened this issue Jun 14, 2023 · 6 comments

Comments

@aduh95
Copy link
Contributor

aduh95 commented Jun 14, 2023

I suggest to transfer https://github.com/stduhpf/caritat into the nodejs GitHub organisation, and to create the @nodejs/caritat team to maintain it.

The goal of Caritat is to propose a robust voting solution that's integrated with the tools Node.js devs use. The TSC is ready to use it as its de facto voting solution, other teams are of course welcome to use it as well.

@stduhpf can you please 👍 to confirm you're OK with that plan? If you are, please transfer the repo to my GitHub account so I can transfer it to the org.

Refs: nodejs/TSC#1165

/cc @nodejs/tsc

@aduh95
Copy link
Contributor Author

aduh95 commented Jun 18, 2023

No objections from TSC members and the issue has been open for more than 72 hours, so the transfer is accepted. I'm going to proceed with the plan.

@mhdawson IIRC you have access to the bot account, could you take care of the NPM token creation please?

  1. Go to https://www.npmjs.com/settings/nodejs-foundation/tokens/new
  2. Enter the nodejs-foundation account's password
  3. Name: NPM_TOKEN secret to publish Caritat ?
    Type: "Automation"
    Click "Generate Token"
  4. Copy the generated token (it starts with "npm_")
  5. Go to https://github.com/nodejs/caritat/settings/secrets/actions/new
  6. Name: NPM_TOKEN
    Value: the token you copied at 4.
    Click "Add secret"

@mhdawson
Copy link
Member

@aduh95 can you add some of the missing boilderplate files ? I think we need a contributing.md with the DCO, one for Code of conduct and the licence should likely update to say "and collaborators" as we have for other reapos.

I'll try to get to looking at the token in the early part of this week.

@aduh95
Copy link
Contributor Author

aduh95 commented Jun 19, 2023

Hum I followed the recommendation in

Ideally, it would not have the following documents to inherit them from
[nodejs/.github](https://github.com/nodejs/.github):
- `CODE_OF_CONDUCT.md`.
- `CONTRIBUTING.md`: if there is one already, consider including the Developer's
Certificate of Origin section in the document to avoid potential copyright
conflicts.
Note that if the above documents are not checked out on the repository, they
will appear on the GitHub web UI but not on local clones of the repository. The
upside is that if the upstream document updates, no action needs to be taken for
the downstream repository to stay up-to-date.

+1 for the license file, I'll send a PR.

@aduh95
Copy link
Contributor Author

aduh95 commented Jun 26, 2023

@mhdawson friendly ping, I would love to be able to finish the transfer of the npm package.

@mhdawson
Copy link
Member

@aduh95 token added.

@aduh95
Copy link
Contributor Author

aduh95 commented Jun 28, 2023

Thanks, I've confirmed it works. The transfer is complete now.

@aduh95 aduh95 closed this as completed Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants