mirror of
https://github.com/carbon-language/carbon-lang.git
synced 2026-10-05 19:31:08 +01:00
Jon Meow
574da45a6b
This sentence feels like a hold-over from the Google Doc, which still feels useful in that context. Especially because it's so easy to copy/share Docs outside the shared drive. However, for things going to GitHub, it seems like we should either have it everywhere or nowhere, and it doesn't feel helpful enough to have in every file. My feeling would be different about a notice on the website -- that could be done centrally for all pages, and may be more useful. However, I haven't bothered there because we restrict access to docs, and I think the login flow should make it clearer that a lack of re-sharing is the intent.
1.6 KiB
1.6 KiB
TODO
Table of contents
TODO: Initial proposal setup
- Create a GitHub pull request, to get a pull request number.
- Add the
proposalandWIPlabels to the pull request.
- Add the
- Name this file
/proposals/p####.md, where####should be the pull request number. - Update the title of the proposal (the
TODOon line 1). - Update the link to the pull request (the
####on line 11). - Delete this section.
TODOs indicate where content should be updated for a proposal. See Carbon Governance and Evolution for more details.
Problem
TODO: What problem are you trying to solve? How important is that problem? Who is impacted by it?
Background
TODO: Is there any background that readers should consider to fully understand this problem and your approach to solving it?
Proposal
TODO: Briefly and at a high level, how do you propose to solve the problem? Why will that in fact solve it?
Details
TODO: Fully explain the details of the proposed solution.
Alternatives considered
TODO: What alternative solutions have you considered?