|
| 1 | +# Title of RFC |
| 2 | + |
| 3 | +| Status | (Proposed / Accepted / Implemented / Obsolete) | |
| 4 | +:-------------- |:---------------------------------------------------- | |
| 5 | +| **ID** | <this will be allocated on approval> | |
| 6 | +| **Author(s) ** | My Name ( [email protected]), AN Other ( [email protected]) | |
| 7 | +| **Sponsor ** | A N Expert ( [email protected]) | |
| 8 | +| **Updated** | YYYY-MM-DD | |
| 9 | +| **Obsoletes** | TF-RFC it replaces, else remove this header | |
| 10 | + |
| 11 | +## Objective |
| 12 | + |
| 13 | +What are we doing and why? What problem will this solve? What are the goals and |
| 14 | +non-goals? This is your executive summary; keep it short, elaborate below. |
| 15 | + |
| 16 | +## Motivation |
| 17 | + |
| 18 | +Why this is a valuable problem to solve? What background information is needed |
| 19 | +to show how this design addresses the problem? |
| 20 | + |
| 21 | +Which users are affected by the problem? Why is it a problem? What data supports |
| 22 | +this? What related work exists? |
| 23 | + |
| 24 | +## Design Proposal |
| 25 | + |
| 26 | +This is the meat of the document, where you explain your proposal. If you have |
| 27 | +multiple alternatives, be sure to use sub-sections for better separation of the |
| 28 | +idea, and list pros/cons to each approach. If there are alternatives that you |
| 29 | +have eliminated, you should also list those here, and explain why you believe |
| 30 | +your chosen approach is superior. |
| 31 | + |
| 32 | +Factors to consider include: |
| 33 | + |
| 34 | +* performance implications |
| 35 | +* dependencies |
| 36 | +* maintenance |
| 37 | +* platforms and environments impacted (e.g. hardware, cloud, other software |
| 38 | + ecosystems) |
| 39 | +* [compatibility](https://www.tensorflow.org/programmers_guide/version_compat) |
| 40 | +* how will this change impact users, and how will that be managed? |
| 41 | + |
| 42 | +## Detailed Design |
| 43 | + |
| 44 | +This section is optional. Elaborate on details if they’re important to |
| 45 | +understanding the design, but would make it hard to read the proposal section |
| 46 | +above. |
| 47 | + |
| 48 | +## Questions and Discussion Topics |
| 49 | + |
| 50 | +Seed this with open questions you require feedback on from the RFC process. |
0 commit comments