org.eclipse.dash.handbook issues
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues
2024-01-15T20:55:45Z
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/113
Make it clear that the project website must be hosted on EF managed servers
2024-01-15T20:55:45Z
Eclipse Webmaster
Make it clear that the project website must be hosted on EF managed servers
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#535141)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=535141)**
## Description
The section that discusses the project website implies, but does not state that the pr...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#535141)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=535141)**
## Description
The section that discusses the project website implies, but does not state that the project website must be hosted on EF managed servers.
That is, the website that the user ends up on by navigating to http://www.eclipse.org/`<short-name\>` must be running on EF infrastructure. This could be (as is default) the "PMI" page that's generated from project metadata, or a custom site that hosted on our www servers.
This URL must not, for example, redirect to a community portal.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/120
Add the Eclipse Foundations project server policy to the handbook
2024-01-15T20:53:51Z
Eclipse Webmaster
Add the Eclipse Foundations project server policy to the handbook
## Submitted by Eclipse Webmaster `@webmaster`
**[Link to original bug (#538607)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=538607)**
## Description
We've created the following policy for virtual machines provided by the Eclipse...
## Submitted by Eclipse Webmaster `@webmaster`
**[Link to original bug (#538607)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=538607)**
## Description
We've created the following policy for virtual machines provided by the Eclipse Foundation.
`<----- Begin Policy ---->`
Project Server Policy
By operating a virtual server hosted either directly by the Eclipse Foundation or provided via the Eclipse Foundation’s funding in support of an Eclipse Foundation open source project to which you are a committer, you agree to the following:
1)To respond within 30 days to written requests eclipse.org-gdpr@eclipse.org to delete accounts or make user data available to the specific user in question. Server maintainers must subscribe to this list.
2)To collect only as much information is required to process the user’s request and to securely dispose of it when no longer required.
3)To make the contents of the server available for auditing should the need arise, and to provide support as required in order to carry out the audit process.
4)To take reasonable security precautions to prevent unauthorized access, and to notify the Eclipse Foundation (via privacy@eclipse.org) immediately if you suspect a security breach of any kind. Be sure to include the nature and scope of the suspected breach.
5)To ensure all web pages related to operation of the server use either the standard Eclipse.org footer template, or a footer that prominently contains a copyright notice, and the following set of links:
1) Main Eclipse Foundation website (http://www.eclipse.org)
2) Privacy policy (http://www.eclipse.org/legal/privacy.php)
3) Website terms of use (http://www.eclipse.org/legal/termsofuse.php)
4) Copyright agent (http://www.eclipse.org/legal/copyright.php)
5) Legal (http://www.eclipse.org/legal)
6)To ensure explicit consent has been given by the user before you can start using cookies. This requirement also includes cookies used by 3rd party services such as, but not limited to: Google Tag Manager, and social media widgets.
7)To ensure webpages related to the services being offered are fully compliant with the GDPR regulations
8)To not collect or track user activity on Eclipse Foundation-owned domains.
9)Google Analytics codes that do not belong the the Eclipse Foundation are prohibited
Failure to comply with this Policy may result in the server or funding in question being terminated without notice.
`<-------- End Policy ------>`
### Blocking
* [Bug 534384](https://bugs.eclipse.org/bugs/show_bug.cgi?id=534384)
### See also
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=552136
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/24
Add discussion of what to expect when transitioning an existing project
2024-01-15T20:35:32Z
Eclipse Webmaster
Add discussion of what to expect when transitioning an existing project
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#491835)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=491835)**
## Description
We need some discussion of what existing projects should expect when transitioning to ...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#491835)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=491835)**
## Description
We need some discussion of what existing projects should expect when transitioning to Eclipse/LocationTech/PolarSys. This belongs in the "Starting a New Open Source Project" section.
e.g.
Projects transitioning to Eclipse are required to:
* Transfer ownership any existing project name to the EF;
* Transfer existing domain names that use the project name trademark to the EF;
* Conform to the Eclipse Logo & Trademark usage guidelines on project websites and in communication with the community (e.g. in slide decks);
* Conform to the Eclipse Development Process;
* Conform to the Eclipse IP Policy and follow the Eclipse IP Due Diligence Process;
* Maintain metadata pertaining to the project using the EF-provided PMI;
* Use EF-provided VCS for all project source code;
* Host binary distributions from EF-provided downloads server; and
* Use EF-provided web hosting services for the project's primary website.
Note that other services can be used in addition to EF-provided ones, but the EF provided ones must be considered canonical.
Projects are expected spend effort engaging with their community, and court contributions and new developers. Projects are also encouraged to provide mature automated build solutions, maintain both user and contributor documentation, and otherwise engage in activities that encourage participation in the project.
New project sponsors must engage in the process of transitioning an existing project with the intent to continue development of the project code and growth of the community and ecosystem around the project.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/118
Add discussion regarding trademarks to the "Starting an Open Source Project a...
2024-01-15T20:35:32Z
Eclipse Webmaster
Add discussion regarding trademarks to the "Starting an Open Source Project at Eclipse Foundation" section
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#537997)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=537997)**
## Description
We do have some discussion regarding trademarks in the document (e.g. [1]) and the "St...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#537997)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=537997)**
## Description
We do have some discussion regarding trademarks in the document (e.g. [1]) and the "Starting an Open..." section [2] does touch on the subject, but more detail will be valuable.
We should, for example, describe the trademark review and transfer process, offer some specific guidance regarding how to select a name, and ensure that the reader is aware that they will need to sign related domain names to the Eclipse Foundation.
It might be valuable to talk about expectations regarding technical namespaces (e.g. that projects should use "org.eclipse.*" for their Java namespace when technically feasible).
[1] https://www.eclipse.org/projects/handbook/#trademarks
[2] https://www.eclipse.org/projects/handbook/#starting
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/30
Include discussion of the Security Policy in the handbook
2022-10-17T19:16:05Z
Eclipse Webmaster
Include 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/162
Update the "Starting an Open Source Project at the Eclipse Foundation"
2022-05-10T15:11:10Z
Wayne Beaton
Update 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 Delgado
Maria Teresa Delgado
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/136
Provide help to determine whether or not a CVE is warranted
2020-11-25T19:37:31Z
Eclipse Webmaster
Provide help to determine whether or not a CVE is warranted
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#558854)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=558854)**
## Description
A CVE is generally warranted when a vulnerability is identified in released code. The ...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#558854)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=558854)**
## Description
A CVE is generally warranted when a vulnerability is identified in released code. The converse is that a CVE is generally not warranted for a vulnerability detected in a random commit or milestone build; though, there is some grey area.
We need more here.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/135
Update content regarding the Eclipse DockerHub organization
2020-11-25T19:37:29Z
Eclipse Webmaster
Update content regarding the Eclipse DockerHub organization
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#558443)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=558443)**
## Description
Per [Bug 500937](https://bugs.eclipse.org/bugs/show_bug.cgi?id=500937) Comment 14, the...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#558443)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=558443)**
## Description
Per [Bug 500937](https://bugs.eclipse.org/bugs/show_bug.cgi?id=500937) Comment 14, the process by which we manage the Eclipse DockerHub organization has changed. We need to update the documentation accordingly. Setting this to major as the information in the handbook is currently incorrect.
### Depends on
* [Bug 500937](https://bugs.eclipse.org/bugs/show_bug.cgi?id=500937)
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/2
IP Log Contribution Doc is wrong (not updated for Git)
2020-11-25T19:37:28Z
Eclipse Webmaster
IP Log Contribution Doc is wrong (not updated for Git)
## Submitted by Dani Megert
**[Link to original bug (#387767)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=387767)**
## Description
http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log#Contributors
does not say anything...
## Submitted by Dani Megert
**[Link to original bug (#387767)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=387767)**
## Description
http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log#Contributors
does not say anything about Git (setting author).
### Blocking
* [Bug 435933](https://bugs.eclipse.org/bugs/show_bug.cgi?id=435933)
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/134
Update the IP Due Diligence Process documentation in light of October 2019 IP...
2020-11-25T19:37:27Z
Eclipse Webmaster
Update the IP Due Diligence Process documentation in light of October 2019 IP Policy updates
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#553649)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=553649)**
## Description
We need to update the documentation.
The gist is:
* Generate a dependency list
* Sca...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#553649)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=553649)**
## Description
We need to update the documentation.
The gist is:
* Generate a dependency list
* Scan the list to flag those entries that are "problematic"
* Engage with the IP Team to resolve those problematic entries
* Profit.
Obviously, more detail is required. I'll capture that detail here.
We intend to support the scanning part (bullet #2) by providing a tool. This is tracked in [Bug 553016](https://bugs.eclipse.org/bugs/show_bug.cgi?id=553016). I may make that bug a blocker (theoretically, we can do this without a tool, but a tool will certainly make it easier).
### Blocking
* [Bug 552967](https://bugs.eclipse.org/bugs/show_bug.cgi?id=552967)
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/133
Provide guidance regarding what constitutes "cryptography"
2020-11-25T19:37:26Z
Eclipse Webmaster
Provide guidance regarding what constitutes "cryptography"
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#552763)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=552763)**
## Description
We are required to report use of cryptography to the US government. In order to do thi...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#552763)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=552763)**
## Description
We are required to report use of cryptography to the US government. In order to do this, we must track the use of cryptography. Currently, we do this via IPzilla by marking project code and third party CQs with the cryptography keyword.
Use of cryptography takes two forms: either the project implements a cryptographic algorithm itself or it leverages third party content that does.
At this point, I'm not quite sure how to expand on that, but we need something better than "I'll know cryptography when I see it".
We need to add content to the handbook to discuss what constitutes cryptography and how to keep track of it (open a CQ).
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/132
Add content supporting specification projects to the handbook
2020-11-25T19:37:24Z
Eclipse Webmaster
Add content supporting specification projects to the handbook
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#552040)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=552040)**
## Description
For example...
For release reviews, specification projects require a ballot of the sp...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#552040)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=552040)**
## Description
For example...
For release reviews, specification projects require a ballot of the specification committee. My current thinking is that the EMO will request that the specification committee initiate the ballot.
Project teams should also anticipate the extra time required to complete the release review. Ballots require a minimum of two weeks and may be extended to 30 days.