node-unicode / node-unicode/node-unicode-data
What should I package in Debian?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 154
- Forks
- 18
- Avg merge
- 9h 48m
- Merged PRs (30d)
- 3
Description
I noticed this repo could have been updated when I saw other -- versioned -- packages get new releases.
Checking, I see that a release was tagged! Will it be the case in the future? If that is the case, I'll package released versions, and get auto-notified whenever you tag one.
If that is not the case, which commit should I package? I see there's been a lot of work these days, and I wouldn't like to package a random commit...
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue discussion and the repository's tagged releases. Determine whether Debian packages should follow tagged releases or a specific commit, then document that packaging policy and how packagers can be notified of future tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100