I know it's somewhat arrogant to call this the "@jcbhmr initiative", but I couldn't think of a more generalized name to describe the vastness of the stuff that this issue entails.
Proposition
Right now this repository appears to have a single "anchor" repository: the features repository. This is good, but I think this organization can be much more than just a features collection. I propose that we...
Expand to cover images, features, and templates
Add some target issues for what features/images/templates we want
Create web interfaces for browsing features/images/templates instead of README.mds in GitHub
Add more metadata and scope-defining goals and goalposts to this metadata repo
I know it's somewhat arrogant to call this the "@jcbhmr initiative", but I couldn't think of a more generalized name to describe the vastness of the stuff that this issue entails.
Proposition
Right now this repository appears to have a single "anchor" repository: the features repository. This is good, but I think this organization can be much more than just a features collection. I propose that we...
README.md
s in GitHubHere's a draft charter/objective document that I wrote down: jcbhmr/devcontainers-contrib#jcbhmr-initiative
Why we should expand the scope of this organization beyond just features
Tasks
Ideas
These are things that I thought about and dismissed, but wanted to record and share.
Rename this organization to something shorter than 21 characters (high friction, I know)
Ideas: