Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • O org.eclipse.dash.handbook
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 155
    • Issues 155
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Technology
  • Eclipse Dash
  • org.eclipse.dash.handbook
  • Issues
  • #55
Closed
Open
Issue created Jan 12, 2017 by Eclipse Webmaster@webmasterOwner

[faq] Project websites and IP Due Diligence

Submitted by Wayne Beaton @wbeaton

Link to original bug (#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
Assignee
Assign to
Time tracking

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