Add FEP Purpose and Guidelines #3

realloc · 2023-02-02T07:14:51Z

realloc commented

2023-02-02 07:14:51 +00:00

(Migrated from github.com)

First, we need to define what FEP is and how it works.

Fix CODEOWNERS to require corresponding Committee approval for FEP all types

First, we need to define what FEP is and how it works. - [x] Fix CODEOWNERS to require corresponding Committee approval for FEP all types

acid-ant (Migrated from github.com) reviewed 2023-02-02 14:03:29 +00:00

content/proposals/_index.en.md

acid-ant (Migrated from github.com) commented

2023-02-02 13:59:54 +00:00

PEP -> FEP?
An the same for bellow line:
- **Superseded** — Replaced by another succeeding PEP

PEP -> FEP? An the same for bellow line: `- **Superseded** — Replaced by another succeeding PEP`

anatoly-bogatyrev (Migrated from github.com) reviewed 2023-02-07 07:13:17 +00:00

fyrchik (Migrated from github.com) reviewed 2023-02-07 08:15:24 +00:00

content/proposals/_index.en.md

fyrchik (Migrated from github.com) commented

2023-02-07 07:40:58 +00:00

s/start reading at/read/ or refer to?

`s/start reading at/read/` or `refer to`?

content/proposals/proc/FEP-0001.md

					
				@ -0,0 +84,4 @@

				the right to reject FEP proposals if they appear too unfocused or too broad. If

				in doubt, split your FEP into several well-focused ones.

				Each FEP must have a champion -- someone who writes the FEP using the style and

fyrchik (Migrated from github.com) commented

2023-02-07 08:04:30 +00:00

If "champion" a common term?

content/proposals/proc/FEP-0001.md

					
				@ -0,0 +140,4 @@

				* In the "Type:" header field, enter "Standards Track",

				  "Informational", or "Process" as appropriate, and for the "Status:"

				  field enter "Draft". For full details, see [FEP Header Preamble]({{<ref

				  "#fep_header_preamble">}}).

fyrchik (Migrated from github.com) commented

2023-02-07 08:14:49 +00:00

The link is not rendered in GH web viewer.

realloc (Migrated from github.com) reviewed 2023-02-07 08:27:32 +00:00

content/proposals/proc/FEP-0001.md

					
				@ -0,0 +140,4 @@

				* In the "Type:" header field, enter "Standards Track",

				  "Informational", or "Process" as appropriate, and for the "Status:"

				  field enter "Draft". For full details, see [FEP Header Preamble]({{<ref

				  "#fep_header_preamble">}}).

realloc (Migrated from github.com) commented

2023-02-07 08:27:31 +00:00

It's not supposed to be. For nice view the one should make server and use local browser against provided URL.

Maybe later we could render site PRs to a separate URL to simplify process.

It's not supposed to be. For nice view the one should `make server` and use local browser against provided URL. Maybe later we could render site PRs to a separate URL to simplify process.

realloc (Migrated from github.com) reviewed 2023-02-07 08:28:09 +00:00

content/proposals/proc/FEP-0001.md

					
				@ -0,0 +84,4 @@

				the right to reject FEP proposals if they appear too unfocused or too broad. If

				in doubt, split your FEP into several well-focused ones.

				Each FEP must have a champion -- someone who writes the FEP using the style and

realloc (Migrated from github.com) commented

2023-02-07 08:28:09 +00:00

yes

fyrchik (Migrated from github.com) approved these changes 2023-02-07 12:50:44 +00:00

anatoly-bogatyrev (Migrated from github.com) approved these changes 2023-02-07 12:50:55 +00:00

alexvanin (Migrated from github.com) reviewed 2023-02-07 14:10:25 +00:00

content/proposals/proc/FEP-0001.md

					
				@ -0,0 +520,4 @@

				comment on the pull request. (If the original author's GitHub username is

				unknown, use email.) If the original author doesn't respond in a timely manner,

				the Committee will make a unilateral decision (it's not like such decisions

				can't be reversed :smile:.