While family changes have limited my time quite a bit, another challenge is the number of projects I'm involved in. I am trying to identify pause points for those projects and work towards them.
committed: conventional 1.0 support before pausingtypos: benchmarks ran and formal announcementassert-rs: effectively at a pause pointcargo-release: reduce the number of commits and improve "is a release needed?" detectionstager/cargo-tarball: This is the area of most work needed
Whats not listed are some ideas I have around improving the licensing landscape. Those will also be a relatively big distraction if I move forward with them.
and I hope people are more excited by
typos than they were for committed
(
typos is a source code spell checker targeted at being run in CIs)
Funny enough,
typos was originally going to be my second Rust project for learning the language until Cobalt took over all my time
So that ideas has been sitting around for years
Especially when the goal it to automate Changelogs Oo
which is super duper great
Some people are against auto-generated changelogs. Sometimes it is because people are unfamiliar with how conventional helps. Other times, its because they aren't considering the size of the project, how thinly spread maintainers are, and that sometimes something is better than nothing (looking at you, all those Rust crates that broke compat without any changelog for me to reference to know how to update).
For the people anti-changelog generation, I'm tempted to add a feature to
committed that will error if a fix, feat, or BREAKING CHANGE commit does not include a change in the changelog.
apart from having a standardised format that ease the reading
To go back to cobalt, what do you think will happen to it? For a blog, shall I move to Zola as well?