Eclipse Dash issues
https://gitlab.eclipse.org/groups/eclipse/technology/dash/-/issues
2021-01-21T11:04:44Z
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/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.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/131
Consider moving Committer Due Diligence Guidelines into the handbook
2020-11-25T19:37:22Z
Eclipse Webmaster
Consider moving Committer Due Diligence Guidelines into the handbook
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#549686)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=549686)**
## Description
The Committer Due Diligence Guidelines content is likely a good fit for the handbook.
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#549686)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=549686)**
## Description
The Committer Due Diligence Guidelines content is likely a good fit for the handbook.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/130
Projects names may use a Working Group's brand
2020-11-25T19:37:21Z
Eclipse Webmaster
Projects names may use a Working Group's brand
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#549231)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=549231)**
## Description
The handbook states (in part):
--
The primary branding for any project name is fully-...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#549231)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=549231)**
## Description
The handbook states (in part):
--
The primary branding for any project name is fully-qualified formal name which includes the "Eclipse" prefix
--
The fully-qualified formal name may, with approval from a working group, use that working group's brand (e.g. "Jakarta Batch"). So... the formal name must have *an* Eclipse Foundation brand as a prefix.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/129
Describe the charts that we render for each project
2020-11-25T19:37:19Z
Eclipse Webmaster
Describe the charts that we render for each project
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#544357)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=544357)**
## Description
We should describe, for example, that only member companies are listed and that commit...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#544357)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=544357)**
## Description
We should describe, for example, that only member companies are listed and that committers who do not work for a member company are listed as "unaffiliated".
Q: what do I do if my contributions are not being properly attributed to my company?
A: Set your company affiliation in accounts.eclipse.org
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/128
Add advice regarding releasing parts of a project
2020-11-25T19:37:17Z
Eclipse Webmaster
Add advice regarding releasing parts of a project
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#544297)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=544297)**
## Description
It's relatively rare, but some projects need to release parts of their project. Projec...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#544297)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=544297)**
## Description
It's relatively rare, but some projects need to release parts of their project. Projects that make a habit of this sort of behaviour should probably consider refactoring (i.e. if you're releasing components on different schedules, should those components be separate projects?).
Here's part of an email that I sent to a committer.
--
To do a formal release, you need to first create a release record. You can put arbitrary text into the release name, so you could, for example, call a release "glassfish-doc-plugin 1.0" and then engage in the release process with that. The only real challenge in this is to ensure that it doesn't confuse the community or the development team.
Note that we made a change to the EDP in December that lets a project push out releases for a year after engaging in a successful Release or Progress Review. So you don't actually need to submit an IP Log for review or engage in a Release Review. Just create the release record and push out your bits. Any IP reviews associated with the content that you're pushing out need to be fully resolved before you push out anything that is considered an official release.
FWIW, you can also just build and push the new content to Maven labeled as a "milestone" build (or "alpha", "beta", "SNAPSHOT", whatever) of the forthcoming Eclipse GlassFish 5.2 release (e.g. set the version of the Maven record to "5.2M1" or something).
From a process point-of-view, you could also create an "Eclipse GlassFish 5.1.1" release that includes all of the exact same versions of software Eclipse GlassFish 5.1 has plus this plug-in. There's no rule that says that you have to rebuild everything, or that every software component share the same version as the associated Eclipse Project release (for example, the Eclipse IDE project only builds new versions of their plug-ins that actually change; "Eclipse IDE 4.10" includes plug-ins with a very wide range of version numbers). Again, it's really all about managing community confusion.
--
Eclipse MicroProfile also does this, so there might be an opportunity to scavenge some text from email exchanges with that team.
--
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/127
Add content describing how project team can receive (significant) code contri...
2020-11-25T19:37:16Z
Eclipse Webmaster
Add content describing how project team can receive (significant) code contributions
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#543503)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=543503)**
## Description
Starting point:
--
1) Contributors make some sort of public announcement that the con...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#543503)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=543503)**
## Description
Starting point:
--
1) Contributors make some sort of public announcement that the content will be delivered to the project
2) If the source code is not already in a public repository, it will have to be delivered to an existing project committer in some way
3) The source needs to be handed off to the IP Team for their review as a "project code" contribution to an existing project
4) Any developers who are coming to the project along with the code need to be voted in as committers
5) When the IP Team gives the go-ahead, either the existing public repository needs to be moved to the Eclipse Foundation, or a new repository can be created and used as a home for the code.
--
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/125
Migrate "Changing Leadership" content to the Handbook
2020-11-25T19:37:13Z
Eclipse Webmaster
Migrate "Changing Leadership" content to the Handbook
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#539976)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=539976)**
## Description
I'm not sure how much additional information is on this page, but we should move anyth...
## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#539976)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=539976)**
## Description
I'm not sure how much additional information is on this page, but we should move anything that is useful to the handbook.
https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/124
Cannot submit a CQ for WTP from the PMI (but I can submit for a subproject)
2020-11-25T19:37:11Z
Eclipse Webmaster
Cannot submit a CQ for WTP from the PMI (but I can submit for a subproject)
## Submitted by Nick Boldt
**[Link to original bug (#539759)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=539759)**
## Description
So, I read through the instructions here [1] and tried to find the "Committer Tools › Intellectual ...
## Submitted by Nick Boldt
**[Link to original bug (#539759)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=539759)**
## Description
So, I read through the instructions here [1] and tried to find the "Committer Tools › Intellectual Property" section on the WTP [2] site but despite being a committer on those projects I was unable to get a link to the CQ submission process.
[1] https://www.eclipse.org/projects/handbook/#pmi-commands-cq
[2] https://projects.eclipse.org/projects/webtools
Turns out the issue is that I'm not a committer for WTP, but for several of its subprojects, such as Dali [3].
[3] https://projects.eclipse.org/projects/webtools.dali
So perhaps it should be mentioned in the Projects Handbook that you might have to navigate down to a subproject before you can submit a CQ?