-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
WIP: Initial proposal for feature request #803
base: main
Are you sure you want to change the base?
Conversation
License Check Results🚀 The license check preparation job ran successfully. Status: Click to expand output
|
Feature Request Guideline | ||
############################## | ||
|
||
.. gd_guidl:: Feature Request Guideline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be doc_, is not part of process model, it is a real document
############################## | ||
|
||
.. gd_guidl:: Feature Request Guideline | ||
:id: gd_guidl__featr_request_guideline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doc_
.. gd_guidl:: Feature Request Guideline | ||
:id: gd_guidl__featr_request_guideline | ||
:status: valid | ||
:tags: contribution_management |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove as not needed
The created documentation from the pull request is available at: docu-html |
* The outcome of the review could be like following: | ||
|
||
* **Accepted** - You feature request is accepted. The technical leads will create a GitHub issue of type 'Epic', where detailed information regarding your feature will be documented. | ||
Afterwards the epic will be assigned to the corresponding team (CFT/Community). If none of the CFTs/Communities match the new *feature request*, then a new CFT/Community will be founden. You will be invited to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo founded
* **Accepted** - You feature request is accepted. The technical leads will create a GitHub issue of type 'Epic', where detailed information regarding your feature will be documented. | ||
Afterwards the epic will be assigned to the corresponding team (CFT/Community). If none of the CFTs/Communities match the new *feature request*, then a new CFT/Community will be founden. You will be invited to | ||
the CFT/Community for break down of the *feature request* and planning. | ||
* **Rejected** - You *feature request* was rejected. It could be either because you description was not mature enough or because the proposal technically doesn't fit into S-CORE roadmap or architecture. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is rejected, as above is accepted
* Next step would be to start working on the *feature request*. First of all, set the corresponding GitHub issue into "in Progress" status. | ||
Issues, that stay in the status "Draft" for a loner period of time, will be deleted. Depending on the maturity of the *feature request*, following two options are possible: | ||
|
||
* If the Feature Request is "just an idea" and you do not have any concrete requirements, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This guideline does not macht the Change Management Process, which covers New Feature Request as modifications, a Feature Request is always a combination of an Issue and PR(s)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please align with Change Management
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this tarball added by mistake?
No description provided.