Provide more help to select a project licence in the "Starting an Eclipse Open Source Project" section

Some thoughts

Must be one of EPL-2.0, EDL (BSD-3-Clause), Apache-2.0, MIT; exceptions are possible, but anything else requires board approval
The EPL-2.0 may be combined with a secondary license
Dual licensing scenario are supported
Specification projects must use EPL-2.0, EDL (BSD-3-Clause), Apache-2.0, or MIT; exceptions are possible, but there are some important constraints
Specification projects must not use the EFSL for source content (this is for Final Specifications only)
Exceptions require board approval (Must be an OSI-approved open source licence)
Even in exceptional cases, licence selection must be business-friendly.

Consider including a short description of secondary licensing. We may be able to paraphrase some bits from the EPL-2.0 FAQ.

The Eclipse Distribution License 1.0 (EDL) is a BSD-3-Clause licence. The BSD-3-Clause is a template licence that must specify a copyright holder and date. It would be inappropriate to list a specific vendor as the copyright holder on a vendor neutral open source project, so the EDL lists the Eclipse Foundation

Example and template code may use alternative licences per board directive. We do not generally include in this in the project licence declaration. Similar for documentation. See Approved Licenses for Non-Code, Example, and Other Content.

FYI @mdelgado624