Abstract #
Allow org admins to export one Markdown document for every single RFC in their organization as part of a single click initiated batch job.
Background #
Currently RFC Hub is a monorepo with a single process handling both web rendering and API calls. Deployment kicks off via GitHub actions. Exporting RFC content would require a lot of manual copying and pasting.
Problem #
Users of RFC Hub expect the ability to export RFCs in an industry standard format to avoid vendor lockin. Supporting this will increase confidence and hopefully adoption. Since the underlying representation for RFCs is already Markdown this RFC proposes that the export process generates individual Markdown files for each RFC.
Proposal #
User Interface #
Definition of success #
Alternatives Considered #
Do Nothing #
Nobody likes a walled garden
Export HTML #
Export .doc / .docx #
Export to Google Drive #
Perform Export in Main Server Process #
History Log
Complete History Log| Operation | Instigator | Revision | When |
|---|---|---|---|
| Now being reviewed by Morticia Addams | Thomas Hunter II | r13 | |
| No longer being reviewed by Morticia Addams | Thomas Hunter II | r13 | |
| Linked as "relate" to RFC5 | Thomas Hunter II | r13 | |
| Morticia Addams had their approved review reverted | Thomas Hunter II | r13 | |
| New RFC revision created: 13 | Thomas Hunter II | r13 | |
| Linked as "relate" to RFC7 | Thomas Hunter II | r12 | |
| Active version of RFC changed from 9 to 12 | Thomas Hunter II | r12 | |
| Active version of RFC changed from 12 to 9 | Thomas Hunter II | r9 | |
| New RFC revision created: 12 | Thomas Hunter II | r12 | |
| File "fake-export-diagram-1BOQ27I0.png" added to RFC | Thomas Hunter II | r11 |
RFC Revision: