Manfred,
Cool thanks... R.I.
Manfred Geiler wrote:
Scott,
I nearly completed the form:
http://incubator.apache.org/ip-clearance/jsr-301-ri.html
(Might not yet have been mirrored, so alternatively check at
http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/jsr-301-ri.xml)
What I did not know is this: "Corporations and individuals holding
existing distribution rights"?
Are there any?
Oracle holds distribution rights to SOME of the code donated as part of
the code contribution, but they moved all this software to the Apache
Liscence and is letting Apache have it. So there is no control that
they would maintain over this code other then reserving the rights to
use it. I think the Apache Liscence correctly addresses this and the
process will be no different then Oracle's use of trinidad.
The only caviat that I see to this is the fact that Oracle intends to
use this as the R.I. for JSR-301 (and subsequent JSR's for this
bridge). As such, the JCP forces companies sponsoring the R.I. to take
responsibility for distribution of the "official" R.I. What this means
is that once the project is released, Oracle will need to check the R.I.
against the TCK and "bless" it as the official R.I. I suspect that this
will largely work like the Pluto project in practice. I don't know if
any of this constitutes "Corporations and individuals holding
existing distribution rights"? so let me know if you need more information..
Next step would be the official vote for "accepting the donation" on
the MyFaces dev list.
I think it's ready for a vote..
Then we must do the lazy consensus ack on the incubator list.
And last but not least we must agree on the svn folder name, where I
can drop the code. Suggestions?
Yes, let's keep JSR-301 out of the svn folder. I would "suggest"
putting it in a folder called "bridge-portlet" or "portlet-bridge".
JSR-301 is the initial release of this and will cover two specs. One
using Portlet 1.0 and JSF 1.2 and the second using Portlet 2.0 and JSF
1.2. My guess is there will need to be two different branches for this
as the code needs to be different on each drop. Going forward, though,
new JSR's will have to be filed to handle JSF 2.0 and we'd like this
project to continue to grow with these JSR's. So giving it a standard
name that would apply though the various releases would be advantageous.
Scott
--Manfred
On 10/11/07, Scott O'Bryan <[EMAIL PROTECTED]> wrote:
Hey Manfred,
I think I've *finally* got everything worked out for the copyright
sections of the ip-clearance for this contribution done and uploaded.
We ran into some last minute licensing issues that should be completely
resolved now.
As for the distribution rights section, I believe that all of those are
done as well since:
* All the initial committers for this project are currently active
in the Apache community and have signed the CLA
* I have signed the Oracle CLA as well and it's the same as what was
signed for my work on the MyFaces Trinidad project
* All items are under the Apache 2.0 liscence and are scheduled for
inclusion in the ASF
So my question is, do I make the updates to the ip-clearance form or do you?
Also, where do I list the initial committers to the project?
Thanks,
Scott O'Bryan
Lawrence Mandel wrote:
Manfred,
You need to build the site (run build.xml in the Site project) and then
run svn update on people.apache.org to pull the changes from SVN into the
public site.
Lawrence
"Manfred Geiler" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
09/07/2007 08:56 AM
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
"MyFaces Development" <[email protected]>
Subject
IP-Clearance for MyFaces / Portlet Bridge RI
I committed a new ip-clearance document a few days ago:
https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/jsr-301-ri.xml
Well, it does not show up yet on the
http://incubator.apache.org/ip-clearance/ page.
Is the incubator site automatically rebuilt periodically? If not, can
someone please do this manually?
Thanks.
--Manfred
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
