Transfer the cookie-signature npm package to the organization

Open
#533 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
release

Research direction

Start with the linked discussion at tj/node-cookie-signature#36 and review the request to transfer the npm package to the organization. The issue says the repository transfer is blocked because TJ is hard to reach, and that transferring the npm package alone would be sufficient. Done means the package is under the organization; the issue names no code files or tests to run.

Written by the indexing model from the issue text.

Description

tc agenda top priority

I'm opening this because we discussed transferring the cookie-signature npm package to the organization a long time ago: https://github.com/tj/node-cookie-signature/issues/36

I'm happy to be the captain if you're looking for someone.

We haven't been able to transfer the repository because TJ is hard to reach, but if anyone can get in touch with him, that would be great. Having the npm package under the organization is more than enough, though.

Dominant language
No language data
Stars
74
Forks
27
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from expressjs/discussions

All issues in expressjs/discussions

Similar issues

More Release issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.