About
OpenINF formed around a question. The tools to answer it did not exist, so building them became the work.
How can we help open source developers aggregate, curate, disseminate, and apply information more effectively?
In practice
Vision- The rules are written down
- How prose is styled, how a commit is worded, how a change gets reviewed. It lives in the handbook, not in the head of whoever reviews you.
- The community documents have one home
- The code of conduct, security policy, and the rest are written once, in OpenINF/.github, then mirrored into each repository as it builds. They cannot drift apart from one another.
- The portal is built in the open
- Its source, its issues, and the review behind every change are public. That includes how this page came to be.
Where it stands
In its infancy, and it shows: gaps, half-finished pages, rules with nothing written under them yet. What we know about is marked as such. Finding something we have missed is a good reason to open a pull request.