get to v1.0 #555
Description
The immediate goal, post hand-off to clj-commons, is to get people feeling comfortable making contributions, work through the issue backlogs, and cut v1.0 releases for all the libraries, representing a stable version of the current feature sets.
Here's my rough sense for how we can get there:
- I will go through all the projects and make sure there are decent namespace-level comments in every file (there should already be high-quality function doc-strings throughout, though if I've missed anything people should point it out).
- All issues should be tagged with their level of difficulty (easy, moderate, hard), where "easy" issues are suitable for new contributors, "moderate" for people with a passing familiarity, and "hard" may need to be reserved for existing experts.
- People assign themselves issues as they see fit, and ask for help whenever they need it.
- If parts of the codebase are unexpectedly confusing, people can open a documentation bug and assign it to me.
If we have too many non-easy issues, we can try a hybrid approach where a more experienced contributor outlines a likely solution, and a less experienced contributor tries to put it into effect.
All PRs should be reviewed by either @kachayev or myself before merging. If someone else feels comfortable playing the role of reviewer, let me know, I'd be happy to have the help.
This can serve as a place for tracking overall progress on our work, and any meta-discussion of how we want to approach it.
cc @kachayev @KingMob @valerauko @tanzoniteblack @frap @abhishekamralkar @solatis @greglook @slipset @danielcompton @borkdude @lread