sorrycc / sorrycc/awesome-javascript
Criteria
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 35k
- Forks
- 4.6k
- Avg merge
- 8h
- Merged PRs (30d)
- 1
Description
Hi Community,
I think it's time to start discussing what are criteria to describe a project as awesome. Top ones that I can think of are;
- At least 90% JavaScript/TypeScript/CoffeeScript
- At least couple of hundred/thousand stars, or any other metric to show its popularity
- Recent activity
- Good documentation/examples
After deciding some or all of these, I'm planning to put them in contribution docs and in pull request templates as pre-requisite, and hopefully prevent unpopular/inactive projects ending up here. After that, I'm also planning to cleanup the existing ones, if they're not matching with these criteria here.
Cheers,
G.
Contributor guide
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 reading the discussion on issue #731, then inspect the contribution docs and pull request templates mentioned in the proposal. Done means agreed criteria for “awesome” projects are reflected in both locations, with existing projects reviewed for compliance as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript, javascript, typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100