Skip to content

WIP: Initial proposal for feature request #803

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

WIP: Initial proposal for feature request #803

wants to merge 1 commit into from

Conversation

antonkri
Copy link
Contributor

No description provided.

@github-actions GitHub Actions
Copy link

License Check Results

🚀 The license check preparation job ran successfully.

Status: ⚠️ Needs Review

Click to expand output 
2025/03/27 15:59:36 Downloading https://releases.bazel.build/7.4.0/release/bazel-7.4.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: docs
Loading: 0 packages loaded
    currently loading: docs
Loading: 0 packages loaded
    currently loading: docs
Analyzing: target //docs:license.check.python (1 packages loaded, 0 targets configured)
Analyzing: target //docs:license.check.python (1 packages loaded, 0 targets configured)

Analyzing: target //docs:license.check.python (90 packages loaded, 10 targets configured)

Analyzing: target //docs:license.check.python (94 packages loaded, 10 targets configured)

Analyzing: target //docs:license.check.python (99 packages loaded, 10 targets configured)

Analyzing: target //docs:license.check.python (130 packages loaded, 822 targets configured)

Analyzing: target //docs:license.check.python (135 packages loaded, 1747 targets configured)

Analyzing: target //docs:license.check.python (144 packages loaded, 2465 targets configured)

Analyzing: target //docs:license.check.python (144 packages loaded, 2465 targets configured)

Analyzing: target //docs:license.check.python (144 packages loaded, 2465 targets configured)

Analyzing: target //docs:license.check.python (148 packages loaded, 4611 targets configured)

INFO: Analyzed target //docs:license.check.python (149 packages loaded, 4736 targets configured).
[11 / 13] [Prepa] JavaToolchainCompileBootClasspath external/rules_java~/toolchains/platformclasspath.jar
[12 / 13] Building docs/license.check.python.jar (); 0s multiplex-worker
INFO: Found 1 target...
Target //docs:license.check.python up-to-date:
  bazel-bin/docs/license.check.python
  bazel-bin/docs/license.check.python.jar
INFO: Elapsed time: 21.785s, Critical Path: 2.46s
INFO: 13 processes: 9 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/docs/license.check.python docs/formatted.txt -review -project automotive.score -repo https://github.com/eclipse-score/score -token otyhZ4eaRYK1tKLNNF-Y
[main] INFO Querying Eclipse Foundation for license data for 69 items.
[main] INFO Found 45 items.
[main] INFO Querying ClearlyDefined for license data for 25 items.
[main] INFO Found 25 items.
[main] INFO License information could not be automatically verified for the following content:
[main] INFO 
[main] INFO pypi/pypi/-/docutils/0.21.2
[main] INFO 
[main] INFO This content is either not correctly mapped by the system, or requires review.
[main] INFO A review is required for pypi/pypi/-/docutils/0.21.2.
[main] INFO A review request already exists https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/19880 .

masc2023
masc2023 reviewed Mar 27, 2025
View reviewed changes
docs/contribute/contribution_request/feature_request.rst
Feature Request Guideline
##############################

.. gd_guidl:: Feature Request Guideline
Copy link
Contributor

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

masc2023
masc2023 reviewed Mar 27, 2025
View reviewed changes
docs/contribute/contribution_request/feature_request.rst
##############################

.. gd_guidl:: Feature Request Guideline
:id: gd_guidl__featr_request_guideline
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doc_

masc2023
masc2023 reviewed Mar 27, 2025
View reviewed changes
docs/contribute/contribution_request/feature_request.rst
.. gd_guidl:: Feature Request Guideline
:id: gd_guidl__featr_request_guideline
:status: valid
:tags: contribution_management
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove as not needed

@github-actions GitHub Actions
Copy link

The created documentation from the pull request is available at: docu-html

masc2023
masc2023 reviewed Mar 27, 2025
View reviewed changes
docs/contribute/contribution_request/feature_request.rst
* 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo founded

masc2023
masc2023 reviewed Mar 27, 2025
View reviewed changes
docs/contribute/contribution_request/feature_request.rst
* **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.
Copy link
Contributor

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

masc2023
masc2023 reviewed Mar 27, 2025
View reviewed changes
docs/contribute/contribution_request/feature_request.rst
* 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,
Copy link
Contributor

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)

masc2023
masc2023 requested changes Mar 27, 2025
View reviewed changes
Copy link
Contributor

@masc2023 masc2023 left a 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

4og
4og reviewed Mar 31, 2025
View reviewed changes
html.tar.gz
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@4og 4og 4og left review comments

@masc2023 masc2023 masc2023 requested changes

Requested changes must be addressed to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@antonkri @4og @masc2023