Update legal documentation requirements for Eclipse Platform Features and Plug-ins
Submitted by Wayne Beaton
I've taken a first pass at documenting legal document requirements for Eclipse Plug-ins and Fragements , starting from the original documentation .
With the adoption of the EPL-2.0, we've decided to do away with the SUA. The actual license text can be used in its place for most content. In most cases, this is pretty straightforward and should require no more work than would be required to replace content with an updated SUA. It gets a little weird with Feature Update Licenses which require that the union of licenses in the corresponding plug-ins also be listed.
I've created this bug as a focal point for discussion regarding the content. The exist content is marked as a draft. I'll close this bug after we've decided to remove that mark.