Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • EMO EMO
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 92
    • Issues 92
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse Foundation
  • EMO Team
  • EMOEMO
  • Issues
  • #225

Closed
Open
Created Nov 18, 2016 by Wayne Beaton@wbeatonOwner

[Bug 507786] Generalize about.html into a technology agnostic NOTICES file (leveraging SPDX)

Bugzilla Link 507786
Status NEW
Importance P3 normal
Reported Nov 18, 2016 14:15 EDT
Modified May 13, 2020 03:50 EDT
Depends on 429587
Blocks 508206, 498155

Description

My understanding is that "about" files are intended to provide licensing information (and other important related information) at the component level. The idea being that license information must be available to consumers should these components be distributed individually.

In OSGi terms, individual bundles are the component as it is possible, so it makes sense to include an "about" file in the bundle. For Eclipse Platform plug-ins, having the about file be in HTML format makes sense because this makes it really easy to display the "Legal Info" from the Installation Details dialog box.

I do not believe, however, that the specific file name (about.html) or format is significant outside of the scope of Eclipse Platform plug-ins. Indeed, we have already seen exceptions (Xtext uses different names for the files to avoid a technical limitation when deployed on Android).

It should be enough that the information be available in the most appropriate format. For Maven-based deployments, the information can be included in the pom.xml file [1]. Including license information in the POM is likely better than an about.html because services like Maven Central know how to use this information.

Other technologies may have more appropriate means of providing the information. At very least, it should be acceptable for the information to be provided in plain text.

So... I believe that the important bit is that the information be provided. How it is provided is a matter of convention or appropriateness for the specific technology. Does this make sense?

Assuming that I've not missed anything important, the About File Templates content [2] is still useful, but really only for Eclipse Platform plug-ins. We'll need to provide advice for the general case and perhaps include this existing content along with examples for other sorts of technology as examples.

[1] https://maven.apache.org/pom.html#More_Project_Information\ [2] https://www.eclipse.org/legal/epl/about.php

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent