Eclipse Dash issueshttps://gitlab.eclipse.org/groups/eclipse/technology/dash/-/issues2023-11-21T17:07:00Zhttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/179Add Committer Badge programme information to the handbook2023-11-21T17:07:00ZWayne BeatonAdd Committer Badge programme information to the handbookWe've captured the information in a [Google Doc](https://docs.google.com/document/d/1yZw9nCfvadWUrYo8kLDGxHXMW2mZPSrY6Fzjzw8drbU/edit?usp=sharing). Let's move that to the handbook.We've captured the information in a [Google Doc](https://docs.google.com/document/d/1yZw9nCfvadWUrYo8kLDGxHXMW2mZPSrY6Fzjzw8drbU/edit?usp=sharing). Let's move that to the handbook.2023-10-27https://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/171Add documention about OtterDog2023-05-30T19:09:18ZMikaël BarberoAdd documention about OtterDogGood start at what it provides https://www.eclipse.org/lists/tractusx-dev/msg00134.htmlGood start at what it provides https://www.eclipse.org/lists/tractusx-dev/msg00134.htmlMarta RybczynskaThomas NeidhartMarta Rybczynskahttps://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/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/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/147Change the amount reimbursed for logo design to 500€2020-12-01T21:58:25ZEclipse WebmasterChange 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/148Describe the GitHub Teams that we create in the handbook2023-09-18T19:33:37ZWayne BeatonDescribe the GitHub Teams that we create in the handbookFor 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 BeatonWayne Beatonhttps://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/181Enforcing 2FA on Gitlab Accounts2023-11-28T19:23:29ZTiago LucasEnforcing 2FA on Gitlab AccountsDear project committers, \
I would like to bring to your attention that the security team at the Eclipse Foundation will soon be requiring that accounts with committer privileges on gitlab.eclipse.org activate 2FA access control. \
The p...Dear project committers, \
I would like to bring to your attention that the security team at the Eclipse Foundation will soon be requiring that accounts with committer privileges on gitlab.eclipse.org activate 2FA access control. \
The plans, along with details on the importance of this change, have been [shared on the committers mailing list](https://www.eclipse.org/lists/eclipse.org-committers/msg01397.html). \
As included in the announcement, we are opening this ticket to inform you and track the activation of 2FA on accounts belonging to this projects’ members. \
To keep in mind, starting on on the **30th of October** you’ll likely see a banner each time you access GitLab reminding you to activate 2FA in your account. \
The deadline is **December the 4th**, by which access to your account will be limited until you activate 2FA. It is highly recommended that you enroll in this process before the deadline.
GitLab offers [instructions](https://gitlab.eclipse.org/help/user/profile/account/two_factor_authentication.md) on every step of the process and we’re happy to answer any question you might have. \
Thank you!
/cc @mbarbero
## FAQ
### How can I activate 2FA for my [gitlab.eclipse.org](https://gitlab.eclipse.org) account?
Detailed [instructions](https://gitlab.eclipse.org/help/user/profile/account/two_factor_authentication.md) are available. In a nutshell, visit [gitlab.eclipse.org/-/profile/two_factor_auth](https://gitlab.eclipse.org/-/profile/two_factor_auth) and follow the on-screen instructions.
If the form asks you for a password in order to set up 2FA on your account, this is not your Eclipse account’s password. It is a known bug on Gitlab that some accounts are requested a “local” password despite having one in the Active Directory. \
You should request a [password reset](https://gitlab.eclipse.org/-/profile/password/edit) and use that same password for this form. This process *does not* change your Eclipse account password.
### Do I need to purchase a hardware token for account access?
No. GitLab supports two 2FA methods:
_Time-based One Time Password_ (TOTP) compatible with mobile apps like Google Authenticator or Authy, and several password managers such as Bitwarden or 1Password.
_WebAuthN_, which necessitates a hardware token, typically a USB key (examples include [Solo 2 key](https://solokeys.com/) or [Yubikey](https://www.yubico.com/la-cle-yubikey/yubikey-5-series/)). These tokens are sometimes referred to as FIDO2 keys.
### How will this affect my [gitlab.eclipse.org](https://gitlab.eclipse.org) accounts?
In the near future, 2FA will become mandatory for authentication on your accounts. Should you not have enrolled by the deadline we communicated to you, access to the platform will be restricted.
### I already have 2FA enabled on [gitlab.eclipse.org](https://gitlab.eclipse.org), do I need to do anything?
No, you’re all good.
### What do I do if I lose my 2FA device?
We highly recommend the utilization of diverse secondary authentication methods. In the event that you misplace all your secondary authentication elements, recovery codes will be the only way to restore account access. By securely storing your recovery codes, you'll ensure the ability to regain access.
Note that the Eclipse IT team may be able to recover access to accounts with 2FA enabled if both the 2FA credentials and account recovery methods are lost. This will require extra identity verification and direct contact with [security@eclipse-foundation.org](mailto:security@eclipse-foundation.org) or [webmaster@eclipse-foundation.org](mailto:webmaster@eclipse-foundation.org).https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/46Expand the section on creating/managing a project website2021-08-19T20:02:58ZEclipse WebmasterExpand the section on creating/managing a project website## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#508465)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=508465)**
## Description
We should include some discussion of the URL, the relationship between the Git reposit...## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#508465)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=508465)**
## Description
We should include some discussion of the URL, the relationship between the Git repository and the website (e.g. how frequently one is pushed to the other), services provided, etc.
Random thoughts:
* The default implementation redirects to the project's PMI page.
* You need to be a committer to edit website content.
* Consider asking the webmaster to add your website Git repository to Gerrit.
* Contributions to the website can be considered as part of the merit for becoming a committer (it's really up to the project team).https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/55[faq] Project websites and IP Due Diligence2021-08-19T20:04:01ZEclipse Webmaster[faq] Project websites and IP Due Diligence## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#510376)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=510376)**
## Description
We need to provide some guidance regarding intellectual property due diligence and pro...## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#510376)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=510376)**
## Description
We need to provide some guidance regarding intellectual property due diligence and project websites.
From the POV of our due diligence process, website content is separate from project code. We expect project teams to respect licenses for all web site content, but do not require (or desire) that they submit website content (including third party libraries) for review by the IP Team.
This is true regardless of where the website content is stored.
If website content is included in project code builds, then it is considered project code and so is subject to the due diligence process.
### Blocking
* [Bug 499707](https://bugs.eclipse.org/bugs/show_bug.cgi?id=499707)https://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/90Include CONTRIBUTING and README to legal documents2024-01-15T20:44:46ZEclipse WebmasterInclude CONTRIBUTING and README to legal documents## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#527361)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=527361)**
## Description
This is not legal documentation per se, but the legal documentation section is probabl...## Submitted by Wayne Beaton `@wbeaton`
**[Link to original bug (#527361)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=527361)**
## Description
This is not legal documentation per se, but the legal documentation section is probably the best fit.
Rough thoughts:
```
The documentation described here includes files that describe licenses and notices, as well as general information about a project and instructions for those who might choose to contribute to the project. Strictly speaking, only the files containing licenses and notices files are legal documentation; the others files are included here for completeness.
A LICENSE, NOTICE, README, and CONTRIBUTING file, as described below, must be included in the root of every source code repository.
git.eclipse.org/project.git
├── CONTRIBUTING
├── LICENSE
├── NOTICE
├── README
└── ...
[[h.ozpt2xwxudvl]]
== Contributing File
Having concise and clear information how to get involved in a project is very important for building the community around a project. Therefore, to simplify adoption and encourage contributions all project repositories must contain a contribution guide.
The contribution guide must make it very clear what are the steps a contributor needs to follow so that their contribution reaches the project and may be accepted.
* Describe the legal part of the process for accepting contributions, including a direct link to the Eclipse Contributor Agreement (ECA) and Developer Certificate of Origin (DCO);
* Provide pointers to the source code, issue trackers, communication channels, etc.
* If the project accept contributions via Gerrit, describe the mechanics of using Gerrit for the contribution;
* If the project repository is hosted on GitHub, indicate whether or not the project will accept pull requests and describe the necessary steps to have the project honor those requests; and
* Describe any further project specific rules, which the contributors should know, including preferences on code quality, code formatting, and processes for code review
Keep the guide as concise as possible - it should contain a few words and a link to the website/wiki for details and more information.
Like a license file, the contribution guide must be expressed in a human readable (plaintext) form; human readable markup languages may be used. The file is conventionally named CONTRIBUTING and may include a suffix (e.g. CONTRIBUTING.md).
[[h.2ps8v8v7gcjl]]
== “Read me” File
Adopters of the project code (e.g. those individuals and organizations who are either using the software or are incorporating it into their own products) are the target audience for a readme file.
* Landing page of the project
* Description of the project
* Pointers to the other documents (LICENSE, CONTRIBUTING, NOTICE)
* License information
* Trademark (Eclipse Foundation and project-specific trademark statements)
The file is conventionally called README and may include a suffix. The contents can either be plaintext or a markup format.
```https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/149Include GitLab2023-09-18T19:33:28ZWayne BeatonInclude GitLabPretty much everywhere we reference GitHub, we should probably also reference GitLab.Pretty much everywhere we reference GitHub, we should probably also reference GitLab.Wayne BeatonWayne Beatonhttps://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/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/84Replace EPL-1.0 by EPL-2.0 in "Example Copyright and License Header for Dual-...2021-06-01T15:36:35ZEclipse WebmasterReplace EPL-1.0 by EPL-2.0 in "Example Copyright and License Header for Dual-licensed Content"## Submitted by Oliver Kopp
**[Link to original bug (#526164)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=526164)**
## Description
At https://www.eclipse.org/projects/handbook/#ip-copyright-headers, the "Example Copyright and Lic...## Submitted by Oliver Kopp
**[Link to original bug (#526164)](https://bugs.eclipse.org/bugs/show_bug.cgi?id=526164)**
## Description
At https://www.eclipse.org/projects/handbook/#ip-copyright-headers, the "Example Copyright and License Header for Dual-licensed Content" contains
SPDX-License-Identifier: EPL-1.0 OR Apache-2.0
but it should be
SPDX-License-Identifier: EPL-2.0 OR Apache-2.0
(note EPL-1.0 vs. EPL-2.0)
Because
* This program and the accompanying materials are made available under the
* terms of the Eclipse Public License 2.0 which is available at
* http://www.eclipse.org/legal/epl-2.0, or the Apache Software License
* 2.0 which is available at https://www.apache.org/licenses/LICENSE-2.0.
### Blocking
* [Bug 519789](https://bugs.eclipse.org/bugs/show_bug.cgi?id=519789)https://gitlab.eclipse.org/eclipse/technology/dash/org.eclipse.dash.handbook/-/issues/138Typo in handbook2021-03-24T17:26:57ZEclipse WebmasterTypo 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