org.eclipse.dash.handbook issues
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues
2021-09-24T20:24:27Z
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/156
PMC Members must be elected
2021-09-24T20:24:27Z
Wayne Beaton
PMC Members must be elected
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.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 Beaton
Wayne Beaton
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/155
Describe the means by which a committer may request that a restructuring revi...
2021-07-05T19:06:02Z
Wayne Beaton
Describe the means by which a committer may request that a restructuring review be scheduled
TL;DR: contact the EMO.
TL;DR: contact the EMO.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/154
Describe the relationship between committer elections and committer agreements
2021-05-05T17:59:22Z
Wayne Beaton
Describe the relationship between committer elections and committer agreements
Following a successful election, we go into a state where we are waiting for the newly elected committer to engage with us to ensure that the necessary agreements are in place. It's not obvious to an outside observer that anything is hap...
Following a successful election, we go into a state where we are waiting for the newly elected committer to engage with us to ensure that the necessary agreements are in place. It's not obvious to an outside observer that anything is happening.
As a start, we should explain the steps that are happening in the background, and give folks some idea of how long they should wait before they contact us for more information.
Ideally, we should also mark up the election record in the PMI to have it indicate where in the provisioning process we are for the committer. I'll open a separate issue against PMI for that.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/153
Terminating and Archiving a Project
2021-04-26T18:32:25Z
Wayne Beaton
Terminating and Archiving a Project
Describe what we do when a project is terminated and archived, including how a project may be revived from that state.
Describe what we do when a project is terminated and archived, including how a project may be revived from that state.
Wayne Beaton
Wayne Beaton
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/152
Roll "The First 90 Days" into the Starting an Open Source Project section
2022-05-10T15:11:11Z
Wayne Beaton
Roll "The First 90 Days" into the Starting an Open Source Project section
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.
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/151
Role "Contributor Guide Recommendation" into the handbook
2021-03-24T13:30:38Z
Wayne Beaton
Role "Contributor Guide Recommendation" into the handbook
Much of the content from the [Contributor Guide Recommendation](https://wiki.eclipse.org/Architecture_Council/Contributor_Guide_Recommendation) is already in the handbook. Let's roll anything that's missing into the handbook and turn tha...
Much of the content from the [Contributor Guide Recommendation](https://wiki.eclipse.org/Architecture_Council/Contributor_Guide_Recommendation) is already in the handbook. Let's roll anything that's missing into the handbook and turn that wiki page into a pointer to the handbook.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/150
Add a requirement/recommendation to provide a SECURITY file with project docu...
2023-05-25T15:18:51Z
Wayne Beaton
Add a requirement/recommendation to provide a SECURITY file with project documentation
Consider requiring/recommending that projects include a SECURITY file in their repositories.
The file should include a pointer to the [Eclipse Foundation Vulnerability Reporting Policy](https://www.eclipse.org/security/policy.php) along...
Consider requiring/recommending that projects include a SECURITY file in their repositories.
The file should include a pointer to the [Eclipse Foundation Vulnerability Reporting Policy](https://www.eclipse.org/security/policy.php) along with implementation details that are specific to the project.
What implementation details should be included in the file?
* By what mechanism should vulnerabilities be reported
* How vulnerabilities are tracked by the project team
* By what criteria the project team will decide whether or not a CVE will be requested from the Eclipse Foundation
What else?
Wayne Beaton
Wayne Beaton
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/149
Include GitLab
2023-09-18T19:33:28Z
Wayne Beaton
Include GitLab
Pretty much everywhere we reference GitHub, we should probably also reference GitLab.
Pretty much everywhere we reference GitHub, we should probably also reference GitLab.
Wayne Beaton
Wayne Beaton
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/148
Describe the GitHub Teams that we create in the handbook
2023-09-18T19:33:37Z
Wayne Beaton
Describe the GitHub Teams that we create in the handbook
For those projects that host on GitHub, the EF maintains multiple teams:
* Project Leads get "Maintainer" access;
* Committers get "Write" Access; and
* Contributors get "Triage" access.
Project leads and committers are elected in the ...
For those projects that host on GitHub, the EF maintains multiple teams:
* Project Leads get "Maintainer" access;
* Committers get "Write" Access; and
* Contributors get "Triage" access.
Project leads and committers are elected in the usual manner.
Contributors can be added to the project by editing the project metadata in the PMI and entering their email addresses in the "Source Code and Issues/Bugzilla" section.
Related:
* [Sync script issue](https://github.com/EclipseFdn/eclipsefdn-github-sync/issues/41)
@cguindon, can you confirm that what I've captured above is accurate? e.g., do project leads automatically get maintainer access, or do they need to request it?
Do you have any existing documentation that I can leverage here?
Wayne Beaton
Wayne Beaton
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/147
Change the amount reimbursed for logo design to 500€
2020-12-01T21:58:25Z
Eclipse Webmaster
Change the amount reimbursed for logo design to 500€
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#568455)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=568455)**
## Description
We have a policy captured in the handbook regarding funding for project logos.
https:...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#568455)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=568455)**
## Description
We have a policy captured in the handbook regarding funding for project logos.
https://www.eclipse.org/projects/handbook/#trademarks-project-logo
We'll change the amount to 500€
> The Eclipse Foundation will help fund the creation of project logos. A project leader or committer will have to pay for the logo design in advance. Once the logo is created, the project can then send the invoice to the Eclipse Foundation marketing team. The Foundation will reimburse up to 500€ for the logo design. Please also feel free to contact the Foundation marketing team with any questions about the logo design.
Can I get confirmation from the Marketing team, please?
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/146
Describe the relationship between Eclipse projects and working groups
2021-01-21T11:04:44Z
Eclipse Webmaster
Describe the relationship between Eclipse projects and working groups
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#568453)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=568453)**
## Description
We need to describe the relationship between Eclipse projects and working groups in th...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#568453)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=568453)**
## Description
We need to describe the relationship between Eclipse projects and working groups in the handbook.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/145
Describe what happens to an archived projects resources
2020-11-25T19:37:46Z
Eclipse Webmaster
Describe what happens to an archived projects resources
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#568314)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=568314)**
## Description
* Single TAR containing Code repos, Web repos, Downloads/Archives
* Bugzilla records m...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#568314)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=568314)**
## Description
* Single TAR containing Code repos, Web repos, Downloads/Archives
* Bugzilla records moved to Community/z_archive
* Forums Closed, moved to “Archived” category, no new posts
* Builds just killed
* Wiki is just left; no archive
* Mailing list archives remain indefinitely; mailing list itself is deleted
### Depends on
* [Bug 516014](https://bugs.eclipse.org/bugs/show_bug.cgi?id=516014)
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/144
Add README files to the list of things that should include incubation branding
2020-11-25T19:37:44Z
Eclipse Webmaster
Add README files to the list of things that should include incubation branding
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#567767)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=567767)**
## Description
The list should include repositories. Many people in our community will never look at ...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#567767)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=567767)**
## Description
The list should include repositories. Many people in our community will never look at the project web pages, PMI, or anything other than the repository.
We should probably include a notice that describes what this means in the CONTRIBUTING file of projects in the incubation phase as well.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/143
Add content to help project teams to market themselves.
2020-11-25T19:37:43Z
Eclipse Webmaster
Add content to help project teams to market themselves.
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#567642)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=567642)**
## Description
Examples:
* Create a twitter handle (with a pointer to the social media policy)
* Tra...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#567642)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=567642)**
## Description
Examples:
* Create a twitter handle (with a pointer to the social media policy)
* Trademark management
* Leverage the Adopters Programme
* Announce releases via news@eclipse.org
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/142
Describe how projects can have their own GitHub organization
2020-11-25T19:37:42Z
Eclipse Webmaster
Describe how projects can have their own GitHub organization
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#567324)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=567324)**
## Description
Add content to the handbook to describe how we use multiple GitHub organizations. Ther...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#567324)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=567324)**
## Description
Add content to the handbook to describe how we use multiple GitHub organizations. There's some information that we can scavenge in [Bug 535944](https://bugs.eclipse.org/bugs/show_bug.cgi?id=535944).
### Depends on
* [Bug 535944](https://bugs.eclipse.org/bugs/show_bug.cgi?id=535944)
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/141
Describe the "Eclipse License Feature"
2020-11-25T19:37:40Z
Eclipse Webmaster
Describe the "Eclipse License Feature"
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#566576)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=566576)**
## Description
From cross-project-issues-dev
--
we use the eclipse license feature [1] e.g. here in ...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#566576)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=566576)**
## Description
From cross-project-issues-dev
--
we use the eclipse license feature [1] e.g. here in the egit feature [2].
The version of the license feature is defined in the target platform we use [3].
In feature.properties we use [4]. If there is a new version of the license we
update the version of the license feature we include in the target platform.
[1] https://git.eclipse.org/r/plugins/gitiles/cbi/org.eclipse.license/+/refs/heads/master
[2] https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.xml#8
[3] https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit.target/egit-4.16-staging.target#25
[4] https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.properties#22
--
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/140
The EFSL should not be modified
2020-11-25T19:37:38Z
Eclipse Webmaster
The EFSL should not be modified
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#565451)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=565451)**
## Description
As a general rule, license text should not be modified (the BSD is an obvious exceptio...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#565451)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=565451)**
## Description
As a general rule, license text should not be modified (the BSD is an obvious exception).
The EFSL contains two templates that developers are tempted to modify.
The text of the EFSL itself, when included with content should not be modified in any way. The templates should be copied out of the EFSL and pasted elsewhere in the document.
e.g.,
...
== Copyright
Copyright © 2020 Eclipse Foundation, Inc. https://www.eclipse.org/legal/efsl.php
== License
Eclipse Foundation Specification License – v1.0
...
We can provide more help in the handbook.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/139
Describe how to push "large" files to the downloads server.
2020-11-25T19:37:36Z
Eclipse Webmaster
Describe how to push "large" files to the downloads server.
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#563102)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=563102)**
## Description
This may be an FAQ entry. This is a placeholder for now, pending the outcome of [Bug 5...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#563102)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=563102)**
## Description
This may be an FAQ entry. This is a placeholder for now, pending the outcome of [Bug 563101](https://bugs.eclipse.org/bugs/show_bug.cgi?id=563101).
### Depends on
* [Bug 563101](https://bugs.eclipse.org/bugs/show_bug.cgi?id=563101)
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/138
Typo in handbook
2021-03-24T17:26:57Z
Eclipse Webmaster
Typo in handbook
## Submitted by Jonah Graham `@jograham`
**[Link to original bug (#561029)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=561029)**
## Description
There is a type in the handbook:
"The named used in the Author field"
### See als...
## Submitted by Jonah Graham `@jograham`
**[Link to original bug (#561029)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=561029)**
## Description
There is a type in the handbook:
"The named used in the Author field"
### See also
* https://git.eclipse.org/r/159195
* https://git.eclipse.org/c/dash/org.eclipse.dash.handbook.git/commit/?id=2b82592c3187a4aa812535c6f46c62b444f0086a
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/137
[BLACK_FRIDAY] Possible lost commit in the dash.handbook repo
2021-09-24T20:26:10Z
Eclipse 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.