Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 977347 - Review Request: jcr-api - Java Content Repository Technology (JSR-283) API
Summary: Review Request: jcr-api - Java Content Repository Technology (JSR-283) API
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: FE-Legal
TreeView+ depends on / blocked
 
Reported: 2013-06-24 11:11 UTC by gil cattaneo
Modified: 2013-06-25 13:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-25 13:42:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description gil cattaneo 2013-06-24 11:11:44 UTC
Spec URL: http://gil.fedorapeople.org/jcr-api.spec
SRPM URL: http://gil.fedorapeople.org/jcr-api-2.0-1.fc16.src.rpm
Description: The Content Repository API for JavaTM Technology Version 2.0
is specified by JSR-283. This module contains the complete API
as specified.
Fedora Account System Username: gil

I'm not sure whether license is OK for fedora

Comment 2 gil cattaneo 2013-06-24 12:00:22 UTC
Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=5535106

Comment 3 Tom "spot" Callaway 2013-06-24 22:40:03 UTC
I'm pretty sure that license is non-free, it has use restrictions and does not permit modification. I'll ask Red Hat Legal to be sure.

Comment 4 Tom "spot" Callaway 2013-06-25 12:27:58 UTC
Red Hat Legal confirms, the Day Specification License is non-free.

Comment 5 gil cattaneo 2013-06-25 13:42:20 UTC
Thanks for your assistance.


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