practicalli / practicalli/clojure
Clojure code base analysis
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Clojure code base is very stable and takes a very thoughtful approach to design
One of the goals of Clojure is to provide backwards compatibility, which requires being methodical about adding features. The side-effect of that is very little code churn.
Data analysis of GitHub repository
https://twitter.com/thesephist/status/1472644432621150220?t=qrgUa7Qfllibj0XThbsMeA&s=19
Note: GitHub repository is not open to PRs. Changes are via ask.clojure.com and Jira tickets (so each and every change can be considered by the core team)
Other code analysis tools
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
No files, tests, or entry points are mentioned. First clarify whether a repository analysis is wanted and what artifact would count as done; the issue currently provides context and external links but no actionable change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100