Skip to content

Commit 3d89f76

Browse files
committed
doc: remove Go-proposal related blurb
1 parent 5e56c36 commit 3d89f76

File tree

1 file changed

+0
-18
lines changed

1 file changed

+0
-18
lines changed

README.md

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -89,24 +89,6 @@ For now, this should make do:
8989
- The author (and/or other contributors) do the work as described by the
9090
"Implementation" section of the proposal.
9191

92-
#### Quick start for committers
93-
94-
If you're already familiar with writing design docs for the Go project,
95-
the process has not changed much.
96-
The main thing that has changed is where the proposal is published.
97-
98-
In the situation where you'd write and circulate a design doc as a Google doc
99-
before, now you:
100-
101-
- Create a GitHub issue labeled Proposal, to get a number NNNN.
102-
- Check in the Markdown-formatted design doc to
103-
[the proposal repository](https://github.com/go-interpreter/proposal/)
104-
as `design/NNNN-shortname.md`.
105-
- Mail [go-interpreter](https://groups.google.com/group/go-interpreter/) as usual.
106-
107-
Worst case, by bypassing the initial discussion you've possibly written an
108-
unnecessary design doc. Not a big deal.
109-
11092
## Help
11193

11294
If you need help with this process, please contact the `go-interpreter` contributors by posting

0 commit comments

Comments
 (0)