kottans / kottans/hacktoberfest
Open-for-Contribution register
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
- repo(s) link + contribution guidelines (
CONTRIBUTING.md| issue # | contribute page (example)) - tech stack (JS, JS/React, JS/Vue, Java..., MEAN....)
- label(s) for open contribution opportunities (
help wanted,up-for-grabs,good-first-issue) - label(s) for non-programming issues (
documentation,content,translation) - label(s) for complexity
- label(s) for hacktoberfest
- optional scoping labels (freecodecamp labels for e.g.)
- any swag?
- email to remind on updates (once/twice a year | before hacktoberfest | any date)
Labels suggestions (label, description, color)
Backlink
Restrictions (pure PRism is restricted)
Listing sortable by A-Z, Stars, Forks, Watched, Used by, language, last update time, open issues only
For maintainers:
Suggested bots:
- PR stall notifier
- linting
- https://allcontributors.org/
- labeller example
Suggest issue and PR templates.
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 with issue #11's requirements list and review the referenced CONTRIBUTING.md, contribute-page, labeller, and PR-template examples. Done requires an agreed scope for the register, labels, sorting, restrictions, maintainer bots and templates, and update reminders.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100