diff --git a/source/.gitignore b/source/.gitignore new file mode 100644 index 0000000000000000000000000000000000000000..20c08c56ebedab81b0dddeeff1b40898d22ccb73 --- /dev/null +++ b/source/.gitignore @@ -0,0 +1,2 @@ +/projects_and_specs.svg +/wg_and_specs.svg diff --git a/source/config.adoc b/source/config.adoc index de22cac6ab46f3ea9571b4719d084e94ade00c07..7b3a98931aa98410d52ea78090591514498cba0a 100644 --- a/source/config.adoc +++ b/source/config.adoc @@ -19,4 +19,5 @@ :handbookUrl: https://www.eclipse.org/projects/handbook :handbookReleaseUrl: {handbookUrl}#release :handbookReleaseAndProgressReviewsUrl: {handbookUrl}#release-review -:handbookProjectPage: {handbookUrl}#pmi-project-page \ No newline at end of file +:handbookProjectPage: {handbookUrl}#pmi-project-page +:handbookCommitterElections: {handbookUrl}#elections-committer \ No newline at end of file diff --git a/source/operations.adoc b/source/operations.adoc index d4c5804149e67b30baaa6da47205ad475d0e9cbb..fc321ffba603c2f5b81b09d53274a34ac373ee40 100644 --- a/source/operations.adoc +++ b/source/operations.adoc @@ -146,7 +146,7 @@ A specification project has one or more project leads. Project leads are the mai [#efspo-roles-rep] === Participant Representative -The EFSP states that a _member participant_ may appoint a _participant representative_ committer. A member participant is defined as a solutions, enterprise, or strategic member of the Eclipse Foundation. The intention of a participant representative is to ensure continuity of a member participant's interest. +The EFSP states that a _member participant_ may appoint a _participant representative_ committer. A member participant is defined as a strategic member or contributing member of the Eclipse Foundation that is a participant in the working group (i.e., has signed the corresponding working group participation agreement). The intention of a participant representative is to ensure continuity of a member participant's interest. Specifically, appointment of a participant representative: @@ -266,7 +266,6 @@ Per the process, this will be a `<duration>` day ballot, ending on `<date>` that Specification committee representatives, your vote is hereby requested. Please respond with pass:[+1] (positive), pass:[+0] (abstain), or pass:[-1] (reject). Any feedback that you can provide to support your vote will be appreciated. ____ - [#efspo-ballot-restructure] === Restructuring Review Ballot Template @@ -285,6 +284,9 @@ Per the process, this will be a `<duration>` day ballot, ending on `<date>` that Specification committee representatives, your vote is hereby requested. Please respond with pass:[+1] (positive), pass:[+0] (abstain), or pass:[-1] (reject). Any feedback that you can provide to support your vote will be appreciated. ____ +[#efspo-ballot-details] +=== Details + The `<details>` should concisely describe the changes that are proposed. This could be as simple as a statement stating that "The Eclipse Foo project will be converted into a specification project.", but other changes may be included. For example: @@ -397,7 +399,7 @@ Meritocracy is very relevant. However, the rules of engagement with specificatio Can a member participant (i.e., a particiant representing a company) appoint as many _participant representative_ committers as they'd like? :: -No. A participating company can appoint a single participant representative committer on a specification project, and only if they do not already have a committer representing their interests on that project. +No. A member participant (i.e., a company that is a participant in the working group) can appoint a single participant representative committer on a specification project, and only if they do not already have a committer representing their interests on that project. Additional committers representing the interests of a member participant must demonstrate merit through contribution and be elected to the project using the standard mechanism for {handbookCommitterElections}[electing committers]. Is a participant representative a special kind of committer? ::