Worst case scenario, we need to do what Pluto did and that is import the
API package as a binary and have the impl at Apache. What I will tell
you is that Oracle and the 301 Expert group is all over moving
everything (including the API) over to Apache, but the code was written
originally using the same model as the JSR-168 mechanism because the
primary developers on the project were from the portal space.
Therefore, they really didn't bother checking to see if something like
this is acceptable from the JCP. As I said, though, other projects like
JSF allow API's to be implemented as part of OpenSource projects so I
really don't forsee an issue.
Matthias Wessendorf wrote:
On 9/26/07, Scott O'Bryan <[EMAIL PROTECTED]> wrote:
As for issue #1, I think we've pretty much got all of the undated items
done, but we're waiting for approval from the Spec lead on an open issue
regarding the API of the bridge. Initially the Spec lead was following
the pattern of JSR-168 and he was including the API as part of the
spec. This meant that the API package would need to remain unchanged
and all copyrights would continue to be held by Oracle. This is why
Pluto, for instance, builds against the JSR-168 binary api package. The
Expert Group discussed this and seems to be on-board with only making
the Java docs part of the specification so we submitted an inquiry to
the JCP regarding this issue and are waiting to hear back. Once the
spec lead returns and gives his approval, I'll upload the re-licensed
files to JIRA and we can pretty much fill everything out.
what happens when there isn't an approval ?
As for issue #2, I'm not sure what we need to do with that. I think
incubator said this could be handled as a code donation and NOT go
though the formal incubator process, but I'm not sure if this
constitutes a "vote" or not. I'm pretty sure we have tentative approval
from us (MyFaces) to accept the code donation and the ip-clearance seems
to indicate that this would be good enough but we could have a more
formal vote if people want.
Scott
Matthias Wessendorf wrote:
Hi,
so, the page is online now ([1]).
All we need is:
-fill out the missing things
-have a vote on [EMAIL PROTECTED] (or was there already a vote, can't
remember....)
-Matthias
[1] http://incubator.apache.org/ip-clearance/jsr-301-ri.html
On 9/3/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
This is the form that needs to be prepared. Manfred, can you take over
filling it out? It has to be an official or a member who does this.
http://incubator.apache.org/ip-clearance/index.html
regards,
Martin
JSR 301 Reference Implementation Codebase Intellectual Property (IP)
Clearance Status
Description
Describe the incoming codebase, including whether it is a large set of
patches, new functional modules, etc.
----------------------------
The codebase is the JSR 301 reference implementation.
----------------------------
Project info
* Which PMC will be responsible for the code: Apache MyFaces
* Into which existing project/module: Apache MyFaces
* Officer or member managing donation: Manfred Geiler (?)
Completed tasks are shown by the completion date (YYYY-MM-dd).
Identify the codebase
date item
2007-09-03 If applicable, make sure that any associated name does not
already exist and is not already trademarked for an existing software
product.
MD5 or SHA1 sum for donated software: (Note versioned software used to
calculate sum in parentheses). - Scott, can you take this over?
Copyright
date item
....-..-.. Check and make sure that the papers that transfer rights
to the ASF have been received. It is only necessary to transfer rights
for the package, the core code, and any new code produced by the
project.
....-..-.. Check and make sure that the files that have been donated
have been updated to reflect the new ASF copyright.
Identify name recorded for software grant: the name of the grant as
record in the grants.txt document so that the grant can be easily
identified
Verify distribution rights
Corporations and individuals holding existing distribution rights:
* For individuals, use the name as recorded on the committers page
date item
....-..-.. Check that all active committers have a signed CLA on record.
....-..-.. Remind active committers that they are responsible for
ensuring that a Corporate CLA is recorded if such is required to
authorize their contributions under their individual CLA.
....-..-.. Check and make sure that for all items included with the
distribution that is not under the Apache license, we have the right
to combine with Apache-licensed code and redistribute.
....-..-.. Check and make sure that all items depended upon by the
project is covered by one or more of the following approved licenses:
Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with
essentially the same terms.
Generally, the result of checking off these items will be a Software
Grant, CLA, and Corporate CLA for ASF licensed code, which must have
no dependencies upon items whose licenses that are incompatible with
the Apache License.
Organizational acceptance of responsibility for the project
Related VOTEs:
* The VOTE thread accepting the donation may happen either before
or after IP clearance. Adoption by lazy concensus is acceptable but
not recommended.
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
