org.eclipse.dash.handbook issueshttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues2021-09-24T20:24:27Zhttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/156PMC Members must be elected2021-09-24T20:24:27ZWayne BeatonPMC Members must be electedThe EDP states that:
> PMC leads are approved by the Board of Directors; PMC members are **elected** by the existing PMC leads and members, and approved by the EMO(ED).
In the handbook section on [PMC Member Elections](https://www.ecli...The EDP states that:
> PMC leads are approved by the Board of Directors; PMC members are **elected** by the existing PMC leads and members, and approved by the EMO(ED).
In the handbook section on [PMC Member Elections](https://www.eclipse.org/projects/handbook/#elections-pmc-member), we state:
> Some PMCs are set up to have a representative from each of the projects in the top-level project. Other PMCs are more exclusive and run an election similar to that of a project lead election.
The first sentence suggests that a project representatives can just be selected and we're done (that is, without an election). We need to make it clear that the manner by which members are selected must take the form of an election.
Further, we should describe the form of the election. We have no specific infrastructure configured for PMC Member elections, so they should be run in the PMC mailing list.Wayne BeatonWayne Beatonhttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/48Provide guidance for including vendor/company-specific links2021-09-24T20:25:42ZEclipse WebmasterProvide guidance for including vendor/company-specific links## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#508546)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=508546)**
## Description
Some project websites provide links to specific company websites (e.g. links to "profe...## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#508546)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=508546)**
## Description
Some project websites provide links to specific company websites (e.g. links to "professional services"). These websites need to follow rules regarding level playing fields and vendor neutrality. We should provide some advice for getting this right.https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/137[BLACK_FRIDAY] Possible lost commit in the dash.handbook repo2021-09-24T20:26:10ZEclipse Webmaster[BLACK_FRIDAY] Possible lost commit in the dash.handbook repo## Submitted by Denis Roy `@droy`
**[Link to original bug (#560106)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=560106)**
## Description
On Friday, Feb. 7, the file server hosting Eclipse Gerrit suffered a hardware failure. While...## Submitted by Denis Roy `@droy`
**[Link to original bug (#560106)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=560106)**
## Description
On Friday, Feb. 7, the file server hosting Eclipse Gerrit suffered a hardware failure. While we were able to resume service on a standby node, that node has a delayed sync.
We've identified some changes in your repository that may not be present in the current state. If the file names contain "refs/changes", this would indicate a Gerrit change was either posted, or merged prior to the failure, and that change may not have been replicated.
./dash/org.eclipse.dash.handbook.git/logs/refs/heads/master
./dash/org.eclipse.dash.handbook.git/objects/pack/pack-fbd2e7f71405d7d739dccc7eae4898a7888dc844.pack
./dash/org.eclipse.dash.handbook.git/objects/pack/pack-d3b4a3fd09e501e27791d982c5b0f9dc52d013a2.pack
./dash/org.eclipse.dash.handbook.git/objects/pack/pack-fbd2e7f71405d7d739dccc7eae4898a7888dc844.idx
./dash/org.eclipse.dash.handbook.git/objects/pack/pack-d3b4a3fd09e501e27791d982c5b0f9dc52d013a2.idx
./dash/org.eclipse.dash.handbook.git/refs/heads/master
As your repository may have changed since last Friday, we cannot automatically fix the issue. We recommend you re-sync your workspaces with your repo and make sure those changes are indeed there.https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/3All Eclipse project Git repositories must include a contribution guide2021-09-24T20:26:45ZEclipse WebmasterAll Eclipse project Git repositories must include a contribution guide## Submitted by Krum Tsvetkov
**[Link to original bug (#397644)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=397644)**
## Description
Created attachment 225328
draft proposal for the recommendation
There was a proposal on the cro...## Submitted by Krum Tsvetkov
**[Link to original bug (#397644)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=397644)**
## Description
Created attachment 225328
draft proposal for the recommendation
There was a proposal on the cross-project-issues list that projects should provide an explicit target definition:
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg08372.html
The proposal was discussed on the AC meeting on 13 Dec 2012:
http://wiki.eclipse.org/Architecture_Council/Meetings/December_13_2012#New_Topics
As not all projects are using Tycho as a build technology, the outcome of the discussion was to provide a more general recommendation that projects should provide a "how to contribute" page, and describe that using an explicit target definition is one good option for handling the dependencies.
We also discussed that it could be useful to give some concrete examples of contribution guides.
I tried to write up a draft for such a recommendation.
However, I'm not sure where to put it in Wiki, so for now I attach it as plain text here.
What could be a proper place in the Wiki for such a recommendation? I will format it then and put it there, instead of using a txt file :)
What do you think about the attached description?
I think it would be nice to have also other technical options described, but my own experience so far is with using Tycho and I couldn't write it.
What about the examples? I just picked a few, but haven't really looked into all projects.
~~**Attachment 225328**~~, "draft proposal for the recommendation":
[Recommendation_Target_Platform.txt](/uploads/09db0c90c6ad2aea2a1778cc0e55ed09/Recommendation_Target_Platform.txt)
### Blocking
* [Bug 404585](https://bugs.eclipse.org/bugs/show_bug.cgi?id=404585)https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/157Describe how to create a "help desk" repository2022-01-06T14:29:18ZWayne BeatonDescribe how to create a "help desk" repositoryOn https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/187#note_440915, we discuss the creation of Eclipse project-specific help desk repositories. We should capture the conventions and practices for these in the handbook.On https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/187#note_440915, we discuss the creation of Eclipse project-specific help desk repositories. We should capture the conventions and practices for these in the handbook.Wayne BeatonWayne Beatonhttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/158Describe the project termination process2022-02-08T22:05:28ZWayne BeatonDescribe the project termination processFrom [Bug 535766](https://bugs.eclipse.org/bugs/show_bug.cgi?id=535766)
> I searched the Eclipse Project Handbook (https://www.eclipse.org/projects/handbook/) for "Termination", because I wanted to provide a link to the process. I rememb...From [Bug 535766](https://bugs.eclipse.org/bugs/show_bug.cgi?id=535766)
> I searched the Eclipse Project Handbook (https://www.eclipse.org/projects/handbook/) for "Termination", because I wanted to provide a link to the process. I remember, somewhere, it was stated that the project is archived, but can be revived, if there is enough interest.
>
> However, I got two hits on "termination" only. And that was "termination reviews" only, without details. Do I mix things up with "Apache Attic" (http://attic.apache.org/)? - Especially "Process of leaving the Attic again)https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/159Inform new committers of the mailing lists to which they will automatically b...2022-02-14T21:15:35ZWayne BeatonInform new committers of the mailing lists to which they will automatically be subscribedWe have some scripts that automagically subscribe committers to various mailing lists.
@webmaster, can you please confirm that these are the lists (are there any more?):
* eclipse.org-members-committers@eclipse.org
* eclipse.org-commit...We have some scripts that automagically subscribe committers to various mailing lists.
@webmaster, can you please confirm that these are the lists (are there any more?):
* eclipse.org-members-committers@eclipse.org
* eclipse.org-committers@eclipse.org
We need to ensure that new committers are aware that they they will automatically be subscribed and must remain subscribed as part of the process of becoming a committer.
Do we automatically subscribe committers to their project's dev list? (per comments on Bug 437377, I think that this is a bootstrapping problem).
We should include pointers to other lists that may be useful (e.g. project dev list, cbi-dev, cross-project-issues-dev).https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/162Update the "Starting an Open Source Project at the Eclipse Foundation"2022-05-10T15:11:10ZWayne BeatonUpdate the "Starting an Open Source Project at the Eclipse Foundation"This section needs some work.
Here are some resources that might help:
* Add a Getting Started Checklist #54
* "The First 90 Days" #152
* Trademarks #118
* [Starting a Project at the Eclipse Foundation](https://www.eclipse.org/commun...This section needs some work.
Here are some resources that might help:
* Add a Getting Started Checklist #54
* "The First 90 Days" #152
* Trademarks #118
* [Starting a Project at the Eclipse Foundation](https://www.eclipse.org/community/eclipse_newsletter/2014/july/article2.php)Maria Teresa DelgadoMaria Teresa Delgadohttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/54Add a "Getting Started" checklist2022-05-10T15:11:11ZEclipse WebmasterAdd a "Getting Started" checklist## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#510310)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=510310)**
## Description
We have a bit of a start on this in the "Starting an Open Source Project at Eclipse" s...## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#510310)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=510310)**
## Description
We have a bit of a start on this in the "Starting an Open Source Project at Eclipse" section, but it's pretty high level and glosses over detail.
Further, having a more comprehensive check list gives us an opportunity to ensure that projects get off on the right foot.
Entries in the list should include:
* Ensure that all project committers have an Eclipse Foundation account;
After provisioning:
* Set up legal documentation (LICENSE.TXT) and about files;
* Add a CONTRIBUTING document;
* Upload your project logo
### Blocking
* [Bug 440244](https://bugs.eclipse.org/bugs/show_bug.cgi?id=440244)https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/152Roll "The First 90 Days" into the Starting an Open Source Project section2022-05-10T15:11:11ZWayne BeatonRoll "The First 90 Days" into the Starting an Open Source Project sectionThere's some useful content on this page [The First 90 Days](https://wiki.eclipse.org/Development_Resources/The_First_90_Days). Let's roll it into the handbook and redirect this page to the handbook.There's some useful content on this page [The First 90 Days](https://wiki.eclipse.org/Development_Resources/The_First_90_Days). Let's roll it into the handbook and redirect this page to the handbook.https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/163Ability to display a summary of clearlydefined findings2022-05-18T06:34:18ZBoris BaldassariAbility to display a summary of clearlydefined findingsAs discussed during our last call, it would be great to have an option for dash that displays a summary of all findings retrieved from clearlydefined. The idea is to use this summary to build ORT's curations file afterwards.
If we get t...As discussed during our last call, it would be great to have an option for dash that displays a summary of all findings retrieved from clearlydefined. The idea is to use this summary to build ORT's curations file afterwards.
If we get the "canonical path" (e.g. `npm/npmjs/@fluentui/react-text/9.0.0-alpha.13`) or whatever similar format that can be easily transformed that'd be enough for our purpose.https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/164Update contact information to point people to create "help desk" issues2022-06-13T18:14:58ZWayne BeatonUpdate contact information to point people to create "help desk" issuesSome of the handbook has been updated to refer to help desk, but not all.
We should review references to the webmaster email address and determine whether or not a pointer to help desk is a better fit.Some of the handbook has been updated to refer to help desk, but not all.
We should review references to the webmaster email address and determine whether or not a pointer to help desk is a better fit.Wayne BeatonWayne Beatonhttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/126Add content to help committers with hosted services/Google Analytics on a pro...2022-06-16T21:06:33ZEclipse WebmasterAdd content to help committers with hosted services/Google Analytics on a project website## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#542526)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=542526)**
## Description
We should include more information about hosted services in general and the use of Goo...## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#542526)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=542526)**
## Description
We should include more information about hosted services in general and the use of Google Analytics in particular to the Eclipse Project Handbook. This probably fits best in the "Resources" section.
Useful resources:
* Mike's statement on the topic [0]
* Chris' blog entry on the topic [1]
* Eclipse Foundation Hosted Services Privacy and Acceptable Usage Policy [2]
I'll take a pass at working Chris' blog post and Mike's statement into handbook content.
[0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=534384#c6
[1] https://blogs.eclipse.org/post/christopher-guindon/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy
[2] https://www.eclipse.org/org/documents/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy.pdfhttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/165Add recommendation about SECURITY.md in Eclipse Handbook2022-08-30T15:03:25ZMikaël BarberoAdd recommendation about SECURITY.md in Eclipse HandbookThere is no mention of a SECURITY.md file in the Handbook. I think we should promote it from the handbook.There is no mention of a SECURITY.md file in the Handbook. I think we should promote it from the handbook.https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/160Recommend to add a security.txt file to all repos (RFC 9116)2022-08-30T15:45:00ZFrederic Gurrfrederic.gurr@eclipse-foundation.orgRecommend to add a security.txt file to all repos (RFC 9116)Found here: https://twitter.com/GossiTheDog/status/1519502619034673154?t=qwW_gUGDzlvHai0QND9Yxw&s=09
`security.txt` has become an official standard defined in https://www.rfc-editor.org/rfc/rfc9116.
It lists contacts in case of securit...Found here: https://twitter.com/GossiTheDog/status/1519502619034673154?t=qwW_gUGDzlvHai0QND9Yxw&s=09
`security.txt` has become an official standard defined in https://www.rfc-editor.org/rfc/rfc9116.
It lists contacts in case of security vulnerabilities and gives credits to reporters + more.https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/30Include discussion of the Security Policy in the handbook2022-10-17T19:16:05ZEclipse WebmasterInclude discussion of the Security Policy in the handbook## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#496426)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=496426)**
## Description
We may only need a pointer. But we should have that pointer.
### Depends on
* [Bug ...## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#496426)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=496426)**
## Description
We may only need a pointer. But we should have that pointer.
### Depends on
* [Bug 496425](https://bugs.eclipse.org/bugs/show_bug.cgi?id=496425)
* [Bug 514571](https://bugs.eclipse.org/bugs/show_bug.cgi?id=514571)
### Blocking
* [Bug 510142](https://bugs.eclipse.org/bugs/show_bug.cgi?id=510142)
* [Bug 511789](https://bugs.eclipse.org/bugs/show_bug.cgi?id=511789)https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/167[Bug 415631] [EDP] EMO vs. EMO(ED)2022-11-08T16:01:55ZWayne Beaton[Bug 415631] [EDP] EMO vs. EMO(ED)| | |
| --- | --- |
| Bugzilla Link | [415631](https://bugs.eclipse.org/bugs/show_bug.cgi?id=415631) |
| Status | NEW |
| Importance | P3 normal |
| Reported | Aug 21, 2013 16:31 EDT |
| Modified | Oct 11, 2020 16:14 EDT |
## Descript...| | |
| --- | --- |
| Bugzilla Link | [415631](https://bugs.eclipse.org/bugs/show_bug.cgi?id=415631) |
| Status | NEW |
| Importance | P3 normal |
| Reported | Aug 21, 2013 16:31 EDT |
| Modified | Oct 11, 2020 16:14 EDT |
## Description
I believe that in some cases, the EDP uses the terms "EMO" and "EMO(ED)" inconsistently.
From section 4:
--\
As defined by the Eclipse Bylaws - Article VII, the Eclipse Management Organization (EMO) consists of the Foundation staff and the Councils. The term EMO(ED), when discussing an approval process, refers to the subset of the EMO consisting of the Executive Director and whomever he or she may delegate that specific approval authority to.\
--
We then have statements like this in section 4.5:
--\
The Scope of a Sub-Project is defined by the initial project proposal as reviewed and approved by the Project Management Committee (PMC) (as further defined below) of the Project's Project's top parent and by the EMO. \
--
In practice "EMO" means "Wayne and Mike". In this particular case, I'm all for course-correcting my process to more explicitly put project proposals in front of the councils and seek their approval. Is this desired, or does it add too much process? (making sure that the councils are aware of new projects seems like a good idea to me).
In section 6.2.1, "EMO" really means "Wayne": "The EMO will assist such groups in the preparation of a project Proposal." and "The Pre-proposal phase ends when the Proposal is published by EMO and announced to the membership by the EMO".
Section 6.3 mixes the roles up nicely...
"the EMO may initiate a Review on the Project's behalf" is--I think--wrong. I believe that it should be the PMC (see [Bug 344041 Comment 6](https://bugs.eclipse.org/bugs/show_bug.cgi?id=344041#c6)).
Also in that section: "A Review then continues with the Project's Leadership requesting that the EMO(ED) schedule the Review.", "Prior to the start of the review period, the Project leadership provides the EMO with review documentation.", and 'The EMO announces the Review schedule and makes the documentation available to the membership-at-large."
Further: "The Review begins with the EMO's posting of the review materials at the start of the Review period", and "The EMO(ED) approves or fails the Review based on the public comments, the scope of the Project, and the Purposes of the Eclipse Foundation as defined in the Bylaws." mix up the two terms.
In all these cases, "EMO" and "EMO(ED)" means "Wayne" (I am the EMO(ED) delegate in this case).
There are more examples.
Do we need to define a new role (e.g. Director of Open Source Projects)?
Or is it just the case that "Wayne" is the practical representative of the EMO and engages in all of these activities on behalf of the larger body, and we should change appropriate occurrences of "EMO(ED)" to "EMO"?
Or should we just update appropriate occurrences of "EMO" to "EMO(ED)" and Mike and I can hash out which parts he'll delegate to me?https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/166Revise the Initial Contribution Process2022-12-19T03:57:39ZWayne BeatonRevise the Initial Contribution ProcessIn the past, we required that project teams provide a ZIP file containing a snapshot of their repository to the IP Team for review via IPZilla. The team was then "on hold" until the IP Team granted their approval to "check-in"; with that...In the past, we required that project teams provide a ZIP file containing a snapshot of their repository to the IP Team for review via IPZilla. The team was then "on hold" until the IP Team granted their approval to "check-in"; with that approval, the project team could then work with the IT team to move/create repositories.
With the changes in the IP Policy, we have an opportunity to improve this experience.
The short version is this:
* Complete the proposal process and creation review;
* Project team and EMO works with IT Team to move existing repositories (or create new ones) in EF GitLab or EF-managed GitHub;
* EMO will initiate the intellectual property review of the default branch of all repositories;
* The EMO IP Team will inform the EMO when the reviews are complete.
Note that the overall process likely takes the same amount of time with these revisions as it did in the past. The perception and general experience should, however, be better for the committer teams involved.
We need to take special care to ensure that project teams understand that when we move repositories under management of the EFs, the repositories will become immediately subject to our system's management of project roles. Write access to repositories will, for example, be limited to committers who are listed on the project proposal and have signed the necessary agreements.
That is, some committers may lose access during the transition period, so care should be taken with regard to timing of the move. It is a best practice, therefore, to wait until a critical mass of committers have been onboarded before starting to move any repositories.
Note that the process is basically the same when a repository of existing code is added to a running project. We can likely do something similar with pull requests that require review (more investigation required).
/cc @mdelgado624 @skilpatrick2022-12-16https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/161Handbook website is not in sync with the latest content from the GitLab repo2023-02-03T11:03:30ZFrederic Gurrfrederic.gurr@eclipse-foundation.orgHandbook website is not in sync with the latest content from the GitLab repoExample:
https://www.eclipse.org/projects/handbook/#resources-github-access
> Project leads are granted admin level access to their project’s GitHub repositories.
vs
https://gitlab.eclipse.org/eclipse/dash/org.eclipse.dash.handbook/-/...Example:
https://www.eclipse.org/projects/handbook/#resources-github-access
> Project leads are granted admin level access to their project’s GitHub repositories.
vs
https://gitlab.eclipse.org/eclipse/dash/org.eclipse.dash.handbook/-/blob/master/source/chapters/resources.adoc#resources-github-access
> Project leads are granted `maintain` level access to their project’s GitHub repositories. \
> A project lead may request temporary `admin` level access to their project’s repositories by {helpdeskUrl}\[creating a Help Desk issue\]. The issue must describe what will be done using this new level of access and how long it will be needed.|
>
This caused confusion here: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1221#note_711665
Please update the handbook website with the latest content from the GitLab repo to avoid further confusion.Wayne BeatonWayne Beatonhttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/168Add information about resource packs to the handbook2023-02-03T11:41:15ZFrederic Gurrfrederic.gurr@eclipse-foundation.orgAdd information about resource packs to the handbookThis should include the content of the following sections:
* https://wiki.eclipse.org/CBI#What.27s_provided.3F
* https://wiki.eclipse.org/CBI#Additional_Resource_Packs
Content can also be used from
* https://wiki.eclipse.org/Jenkins#Abo...This should include the content of the following sections:
* https://wiki.eclipse.org/CBI#What.27s_provided.3F
* https://wiki.eclipse.org/CBI#Additional_Resource_Packs
Content can also be used from
* https://wiki.eclipse.org/Jenkins#About_resource_packs_and_quotas
More important than technical details (number of CPUs and RAM), is probably the process of how resource packs are assigned (https://wiki.eclipse.org/CBI#Assigning_Resource_Packs_to_a_Project) and how projects/orgs can check the status of resource pack allocation (https://wiki.eclipse.org/CBI#Sponsored_Projects).