Skip to content

[PROPOSAL] Remove Stage 4 from RFC process #1194

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
epixa merged 6 commits into from
Jan 25, 2021
Merged

[PROPOSAL] Remove Stage 4 from RFC process #1194

Changes from 3 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
6e619ec
[proposal] Remove Stage 4 from RFC process
epixa Dec 14, 2020
4083732
Fix draft -> candidate
epixa Dec 29, 2020
00533a7
Adjust stage 2 criteria
epixa Dec 29, 2020
5c18106
update RFC template comments
epixa Jan 20, 2021
35fc020
fix stage information in rfc readme
epixa Jan 20, 2021
2add702
Merge branch 'master' into proposal-remove-stage-4
epixa Jan 20, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 10 additions & 27 deletions stages.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ <h1>ECS Proposal Stages</h1>
</tr>
<tr>
<td>1
<td>Proposal
<td>Draft
<td>
<ul>
<li>Make the case for these changes
Expand All @@ -70,7 +70,7 @@ <h1>ECS Proposal Stages</h1>
<ul>
<li>Opened pull request for this proposal revising the existing strawperson
<li>Identified "sponsor" at Elastic who will participate in RFC process and take ownership of the change after the process completes
<li>Types of fields or changes outlined
<li>Outlined initial field definitions
<li>High-level description of examples of usage
<li>High-level description of example sources of data
<li>Identified potential concerns and implementation challenges/complexity
Expand All @@ -79,58 +79,41 @@ <h1>ECS Proposal Stages</h1>
</ul>
</td>
<td>ECS team accepts the premise of the addition and commits to considering this proposal as it advances.
<td>None
<td>Draft field definitions can be committed to the ECS schema as "experimental" fields
<td>Major
<td>Proof of concepts, demos
</tr>
<tr>
<td>2
<td>Draft
<td>Candidate
<td>Identify a comprehensive set of field definitions that could be appropriate for real-world usage
<td>
<ul>
<li>Opened pull request for this draft revising the existing proposal
<li>Outlined initial field definitions
<li>Completed field definitions
<li>Included a real world example source document
<li>Identifies scope of impact of changes to ingestion mechanisms (e.g. beats/logstash), usage mechanisms (e.g. Kibana applications, detections), and the ECS project (e.g. docs, tooling)
<li>Subject matter experts weighed in on technical utility of field definitions in the pull request
</ul>
</td>
<td>The initial field definitions are a comprehensive, though not necessarily complete, model of the addition to the schema. Fundamental questions and concerns are resolved, though some less significant questions remain open.
<td>Draft field definitions can be committed to the ECS schema as "experimental" fields
<td>The initial field definitions comprehensively model the addition to the schema. Fundamental questions and concerns are resolved, though some less significant questions remain open.
<td>Candidate field definitions can be committed to the ECS schema as "beta" fields
<td>Iterative
<td>Experimental and beta features
<td>Experimental features
</tr>
<tr>
<td>3
<td>Candidate
<td>Indicate that direct experience from implementations and users is necessary to validate the additions
<td>
<ul>
<li>Opened pull request for this candidate revising the existing draft
<li>Completed field definitions
<li>Included multiple real world example source documents
<li>Existing or newly raised questions and concerns are addressed
</ul>
</td>
<td>There are no further open questions or unaddressed concerns, and the field definitions are complete based on the information and usage experience we have.
<td>Candidate field definitions can be committed to the ECS schema as "beta" fields
<td>Minimal: only those determined to be critical based on usage experience
<td>GA features
</tr>
<tr>
<td>4
<td>Finished
<td>Indicate that the addition is ready for GA release in ECS
<td>
<ul>
<li>Opened pull request for this candidate revising the existing candidate
<li>At least one real-world, production-ready usage implementation exists for the field definitions
<li>Included multiple real world example source documents
<li>Existing or newly raised questions and concerns are addressed
<li>No objections from sponsor, ECS team, or subject matter experts
</ul>
</td>
<td>The field definitions are in use as defined in real-world, production-ready software without raising additional questions or concerns that need to be resolved. The changes are ready to be released as GA in ECS.
<td>There are no further open questions or unaddressed concerns, and the field definitions are complete based on the information and usage experience we have.
<td>Field definitions can be committed to the ECS schema as "GA" fields
<td>None outside major versions
<td>Any
Expand Down