Bug 1054341 - Explicitely mentions the license restriction
Summary: Explicitely mentions the license restriction
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-16 16:31 UTC by Pierre-YvesChibon
Modified: 2014-02-06 08:32 UTC (History)
1 user (show)

Fixed In Version: copr-1.25-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-06 08:32:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Pierre-YvesChibon 2014-01-16 16:31:54 UTC
The point b and c of "What I can build in copr" in https://fedorahosted.org/copr/wiki/UserDocs#FAQ specifies which licenses/projects can be built in COPR.

It might be good to have a reminder of this in COPR itself, maybe the login page, maybe the copr/create page

Also, point e about guidelines should may be exclude the packaging guidelines as if my understanding is correct copr allows package that do not follow completely Fedora's packaging guidelines

Comment 1 Miroslav Suchý 2014-01-16 16:50:48 UTC
Link to this item of FAQ is in "New Build" tab in WebUI. Is it enough for you?

This document is what I got from fedora-legal. If you want to change this point, please read previous discussion on fedora-legal@ and discuss it there.

Comment 2 Pierre-YvesChibon 2014-01-16 17:07:26 UTC
Maybe mention b and c in the New build tab with add a link "more info on what you can build"?

Comment 3 Miroslav Suchý 2014-01-17 07:32:18 UTC
Fixed in commit 5d29791.

It now state:
You agree to build only <a href="https://fedorahosted.org/copr/wiki/UserDocs#WhatIcanbuildinCopr">allowed content</a> in Copr. Check if your <a href="https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#Good_Licenses">license</a> is allowed.

And the same text is in header of page, when you are creating new project.


Note You need to log in before you can comment on or make changes to this bug.