This RFC outlines our goals and strategies when proposing ideas and asking for feedback
How it works
RFCs typically involve two things:
A proposal, like a new design pattern, a plan for technical changes, etc.
A way to submit feedback, through GitHub, Google Docs, etc.
IU staff, faculty, and students are encouraged to let us know what they think about our proposals. We’ll use that feedback to iterate and improve the final results. Rivet is a community effort, and we thank you in advance for your time reviewing, contributing, and helping us make it the best it can be.
Rivet RFCs will fall into two categories depending on the type of proposal.
Technical RFCs are available for review on GitHub. These can be accessed with your IU Login credentials. Within GitHub, you can leave comments, or propose revisions.
General RFCs will be available on this site, with an option to provide feedback via Google Docs (access with your IU Login account). Comments will be recorded and visible to others browsing the RFC in Google Docs.