Rfc process in visuality
1 like•222 views
The document discusses introducing a Request for Comments (RFC) process at Visuality to improve how ideas are proposed and discussed. An RFC process would allow ideas to be presented to a wider audience, commented on by more experienced people, and keep ideas and best practices in one centralized place. RFCs should include sections like a header, abstract, motivation, proposal, instructions, benefits, possible challenges and links. RFCs would go through states like draft, feedback requested, accepted, and rejected. At Visuality, RFCs would be created and discussed in Notion, last typically two weeks, and be discussed in an RFC Slack channel with a bot.
Rfc process in visuality
- 2. Goals of this slideshow After this slideshow you will: ● Know what an RFC is ● Know why do we need an RFC alike process in Visuality ● Know the benefits of RFCs ● Know how and when to write an RFC
- 3. What actually is an RFC? RFCs, Request for Comments, are publications from the technology community
- 4. Why would we possibly need that in our company? What are the mechanisms used in the company now?
- 5. Why not 1 on 1? ● there appear a lot of questions, that would be answered by an RFC ● idea is not presented clearly ● discussed things may be forgotten ● nobody is aligned
- 6. What are the benefits of introducing RFC? ● save time that is usually spent on meetings ● present your idea to a wider audience ● allow others, maybe more experienced people, to comment on your idea ● allow the author to ask people that he/she may not know well (even from other cities/offices) ● lowers the importance of the factor of being shy, when you want to be a part of change ● everyone in a company is aligned with changes and ideas ● allow for an asynchronous flow of information (less meetings) ● everyone in a company has a right to give his/her opinion ● keep ideas and current best practices in one place
- 7. How an RFC should look like? It should contain at least those following sections: ● Header ● Abstract ● Motivation ● Proposal ● Instructions ● Benefits ● Possible challenges ● Links Short, informal, lightweight document.
- 8. RFC Structure - Header Title: enter title here Author: Adam Kowalski Start Date: DD-MM-YYYY To be reviewed by: DD-MM-YYYY State:
- 9. RFC Structure - Abstract One paragraph introducing the topic of the RFC. Answers the question WHAT?
- 10. RFC Structure - Motivation Why are we doing this? What use cases does it support? What is the expected outcome? Answers the question WHY?
- 11. RFC Structure - Proposal Here you can explain what you're suggesting/proposing. You can give an example of usage or describe how it can look like. Answers the question HOW?
- 12. RFC Structure - Instructions Answer some of possible questions that may appear. Describe confusing parts. Present best practices.
- 13. RFC Structure - Benefits Think about the big picture and impact on the whole company. What are the benefits of doing this? How to measure the impact of changes?
- 14. RFC Structure - Possible challenges What are the possible challenges that we will have to face? What are the suggestions for facing those challenges? Cost calculations of implementation may be done here.
- 15. RFC Structure - Links Links to useful sites or sites that you used researching for the RFC. Helpful for readers that would like to explore the topic deeper.
- 16. ● Draft - The author is working on the RFC. Good research is crucial here. ● Feedback Requested: The RFC has been sent and is waiting for feedback. ● Accepted: The deadline for comments has expired and the rfc was decided to be accepted. The idea is going to be implemented. ● Rejected: The deadline for comments has expired but no decision was taken or it was decided to be rejected. The idea is not going to be implemented but the idea can be redefined in other RFC to be resubmitted. RFC Lifecycle
- 17. RFC in Visuality ● Platform: Notion ● Lifetime duration: typically two weeks (may be shorter or longer depending on need) ● Editable RFCs in Draft and Feedback Requested state ● ‘RFC weekly’ Slack channel with RFC bot. ● Relationships: - Updates, Updated by - Obsoletes, Obsoleted by - Redefined by
- 19. Thank you for listening :) Q&A