MetaMeta: Usually RFCs start off as GDrive Docs and then become Markdown as they're completed. There is a handy GDrive Template too.
- RFC Name: [TBD: unique feature name]
- RFC ID: [TBD: pick the next id]
- Start Date: TBD: todays date, YYYY-MM-DD]
- Owner: [TBD: your name]
- Current Status: TBD: DRAFT -> REVIEW -> ACCEPTED]
[TBD: A short paragraph summary of the SDK-RFC. Something appropriate for putting in a status dashboard.]
[TBD: Why are we doing this? What use cases does it support? What is the expected outcome?]
[TBD: This part must cover the non-SDK specific API design. Concepts should be abstracted from an actual implementation, using some form of "pseudo" language that describes the concept rather than the actual language implementation. This part also covers the unified behavior that the user sees. What errors does the user see? If user does X, what happens on Y? What is the scope? What are the main components? How do they interact? What new interfaces are created? How are they presented in each of the platforms in scope? How will you know when you are done?]
[TBD: What new error handling needs to be considered]
[TBD: What documentation artifacts need to be created or changed in support of this RFC]
In this section, the abstract design parts need to be broken down on the SDK level by each maintainer and signed off eventually.
| Generic | .NET | Java | NodeJS | Go | C | PHP | Python | Ruby |
|---|---|---|---|---|---|---|---|---|
| foo() | foo | Foo | ...... | .. | . | ... | ...... | .... |
[TBD: A running log of larger questions, unresolved at first and later kept in place with their answers if the owner considers it useful to keep the background around.]
[TBD: YYYY-MM-DD Initial draft publication ]
If signed off, each representative agrees both the API and the behavior will be implemented as specified.
| Language | Representative | Date |
|---|---|---|
| Java | Michael N. | 01.01.1960 |