• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

SourcePackage licenses

Overview

• Launchpad entry: https://blueprints.edge.launchpad.net/soyuz/+spec/sourcepackage-licenses

• Created: 2008-12-01 by CelsoProvidelo

• Contributors: JulianEdwards

Overall Summary

Summary: This specification describes how sourcepackage licenses will be stored and tracked within Launchpad using the new debian copyright format. See http://wiki.debian.org/Proposals/CopyrightFormat for more information.

Goal/Deliverables: Extract and store as much information as possible from the new machine readable copyright format when it's used.

We will know we have finished when the license relationships expressed in the new copyright format are stored and acessible after a sourcepackage upload is processed.

Release Note

Not yet.

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the first part of our release change log.

It is mandatory.

Rationale

Not yet.

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

Use cases

• Richard is a strong GPL-v3 defensor, and to prove his point, he want to produce a report of all sources currently published in ubuntu/jaunty which contains GPL-v3 license code.
• John, a developer, has packaged a new upstream source and should be able to express all the licenses involved in his package for uploading it.
• Romeu, a release manager of a distribution hosted in Launchpad, wants to audit all the sources published in his release and decided, based on their licenses, which sources can be redistributed on their mirrors.
• Juliet, a package reviewer, should be able to inspect the licenses involved in a new source uploaded to ubuntu before accept it.
• Ruben, an user, wants to find a ERP application already packaged in ubuntu and licensed under a GPL-compatible license, so he can start to implement his free extensions to it.
• ...

Assumptions

1. The ubuntu and the debian community are happy with http://wiki.debian.org/Proposals/CopyrightFormat specification;

2. There is no major different (pattern-wise) between the debian format and the RPM proposal (see http://fedoraproject.org/wiki/Packaging/LicensingGuidelines);

3. This specification will focus in storing a comprehensive set of data that represents what is encoded in the debian/copyright file. No UI features have to be delivered yet.
4. ...

User Interface

None, see Assumptions

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. This could include subsections in addition to what is provided in this spec template.

Code Changes

Not yet.

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Schema Changes

Not yet.

What Database changes are you proposing? Do you need a new index created? Proposing a new table? If so, what does it look like?

Migration

Not yet.

Include:

• data migration, if any
• redirects from old URLs to new ones, if any

• how users will be pointed to the new way of doing things, if necessary. (If your change is big enough, consider using the rollout template.)

Unresolved issues

None, so far.

CategoryProposal