Re: [pypy-dev] Sun's Open JDK Challenge http://openjdk.java.net/challenge/
In a message of Mon, 18 Feb 2008 21:13:28 +0100, holger krekel writes: <lots of good stuff> <what looks to me like a completely workable plan>
However, IMO the main current issue is to come up with possible goals and technical promises. Any comments and ideas about possible PyPy/JVM Da-Vinci technical goals?
yes, we need to hear from Samuele who is on John Rose's lead team for making adaptation to the JVM as suits dynamic languages. How this and the Da Vinci Machine hang together is not clear to me -- at least the last time I thought I understood it, Samuele made it clear to me that my model of what was going on was a grossly oversimplified model of what really was.
Otherwise i guess we may need to wait for Anto and Niko getting back.
Maybe, but maybe we ought to get started ahead of time. I happen to know Samuele's workload for 2 weeks from now -- we have an in house design sprint. If we could get some things settled ahead of time, this week, then this might be easier for him. Also, one reason I posted this here was that I was interested in hearing from people who are on this list, but so far not large contributors to the PyPy code base. Interested Lurkers, as it were. Are there any of you out there? Does this sound like something any of you are interested in? Laura
best & cheers,
holger
Laura Creighton wrote:
Interested Lurkers, as it were. Are there any of you out there? Does this sound like something any of you are interested in?
It sounds very interesting, but it seems that projects must be contributed under Sun's "Contributor Agreement", which doesn't sound particularly awesome IMHO. Regards, -- Chris Lamb, UK chris@chris-lamb.co.uk GPG: 0x634F9A20
onsdagen den 20 februari 2008 skrev Chris Lamb:
Laura Creighton wrote:
Interested Lurkers, as it were. Are there any of you out there? Does this sound like something any of you are interested in?
It sounds very interesting, but it seems that projects must be contributed under Sun's "Contributor Agreement", which doesn't sound particularly awesome IMHO.
Regards,
I can't really see what is wrong with it. They pay you to produce code. They can do anything they like with it, including selling it or giving it away for free. You can do anything you like with it, including selling it, or giving it away for free. Sounds reasonable to me. Jacob Hallén
Jacob Hallén wrote:
onsdagen den 20 februari 2008 skrev Chris Lamb:
Laura Creighton wrote:
Interested Lurkers, as it were. Are there any of you out there? Does this sound like something any of you are interested in? It sounds very interesting, but it seems that projects must be contributed under Sun's "Contributor Agreement", which doesn't sound particularly awesome IMHO.
Regards,
I can't really see what is wrong with it. They pay you to produce code. They can do anything they like with it, including selling it or giving it away for free. You can do anything you like with it, including selling it, or giving it away for free.
Sounds reasonable to me.
I am not sure it is practical to put parts of PyPy under this agreement. Which parts would that be? All of it (which would be hard, since we need to find all contributors and have them sign it)? Only the new bits which are rather useless by themselves? Cheers, Carl Friedrich
Carl Friedrich Bolz wrote:
Jacob Hallén wrote:
onsdagen den 20 februari 2008 skrev Chris Lamb:
Laura Creighton wrote:
Interested Lurkers, as it were. Are there any of you out there? Does this sound like something any of you are interested in?
It sounds very interesting, but it seems that projects must be contributed under Sun's "Contributor Agreement", which doesn't sound particularly awesome IMHO.
Regards,
I can't really see what is wrong with it. They pay you to produce code. They can do anything they like with it, including selling it or giving it away for free. You can do anything you like with it, including selling it, or giving it away for free.
Sounds reasonable to me.
I am not sure it is practical to put parts of PyPy under this agreement. Which parts would that be? All of it (which would be hard, since we need to find all contributors and have them sign it)? Only the new bits which are rather useless by themselves?
the rule as such makes most sense if the code is going into the Open JDK itself, I'm not sure how it would apply to stuff in another codebase that uses the Open JDK.
Samuele Pedroni wrote:
Carl Friedrich Bolz wrote:
I am not sure it is practical to put parts of PyPy under this agreement. Which parts would that be? All of it (which would be hard, since we need to find all contributors and have them sign it)? Only the new bits which are rather useless by themselves?
the rule as such makes most sense if the code is going into the Open JDK itself, I'm not sure how it would apply to stuff in another codebase that uses the Open JDK.
The problem is that all entries into the open JDK challenge have to be put under the contributor agreement. I agree that it might not make sense for PyPy since it is not going into the JDK. But that is what the rules are. Maybe we should send a mail asking whether other models might be possible. Cheers, Carl Friedrich
onsdagen den 20 februari 2008 skrev Carl Friedrich Bolz:
Samuele Pedroni wrote:
Carl Friedrich Bolz wrote:
I am not sure it is practical to put parts of PyPy under this agreement. Which parts would that be? All of it (which would be hard, since we need to find all contributors and have them sign it)? Only the new bits which are rather useless by themselves?
the rule as such makes most sense if the code is going into the Open JDK itself, I'm not sure how it would apply to stuff in another codebase that uses the Open JDK.
The problem is that all entries into the open JDK challenge have to be put under the contributor agreement. I agree that it might not make sense for PyPy since it is not going into the JDK. But that is what the rules are. Maybe we should send a mail asking whether other models might be possible.
Cheers,
Carl Friedrich
No, this is not quite true. You need to sign the contributor agreement, but that agreement only covers what goes into the Sun codebase. Wether they want to support something that goes into another codebase is an open question. Jacob
Jacob Hallén wrote:
onsdagen den 20 februari 2008 skrev Carl Friedrich Bolz:
I am not sure it is practical to put parts of PyPy under this agreement. Which parts would that be? All of it (which would be hard, since we need to find all contributors and have them sign it)? Only the new bits which are rather useless by themselves?
Carl Friedrich Bolz wrote: the rule as such makes most sense if the code is going into the Open JDK itself, I'm not sure how it would apply to stuff in another codebase that uses the Open JDK. The problem is that all entries into the open JDK challenge have to be
Samuele Pedroni wrote: put under the contributor agreement. I agree that it might not make sense for PyPy since it is not going into the JDK. But that is what the rules are. Maybe we should send a mail asking whether other models might be possible.
Cheers,
Carl Friedrich
No, this is not quite true. You need to sign the contributor agreement, but that agreement only covers what goes into the Sun codebase. Wether they want to support something that goes into another codebase is an open question.
Please read the challenge rules at: http://openjdk.java.net/challenge/rules/ Section 3 states: B. The Entry, in its entirety, must be contributed under the terms of the SCA. Cheers, Carl Friedrich
onsdagen den 20 februari 2008 skrev Carl Friedrich Bolz:
Jacob Hallén wrote:
onsdagen den 20 februari 2008 skrev Carl Friedrich Bolz:
Samuele Pedroni wrote:
Carl Friedrich Bolz wrote:
I am not sure it is practical to put parts of PyPy under this agreement. Which parts would that be? All of it (which would be hard, since we need to find all contributors and have them sign it)? Only the new bits which are rather useless by themselves?
the rule as such makes most sense if the code is going into the Open JDK itself, I'm not sure how it would apply to stuff in another codebase that uses the Open JDK.
The problem is that all entries into the open JDK challenge have to be put under the contributor agreement. I agree that it might not make sense for PyPy since it is not going into the JDK. But that is what the rules are. Maybe we should send a mail asking whether other models might be possible.
Cheers,
Carl Friedrich
No, this is not quite true. You need to sign the contributor agreement, but that agreement only covers what goes into the Sun codebase. Wether they want to support something that goes into another codebase is an open question.
Please read the challenge rules at: http://openjdk.java.net/challenge/rules/
Section 3 states:
B. The Entry, in its entirety, must be contributed under the terms of the SCA.
Cheers,
Carl Friedrich
Ok, I stand corrected. I just read what was said in conjunction with the SCA. Then it seems to make no sense to submit. Jacob
"Carl Friedrich Bolz" <cfbolz@gmx.de> wrote in message news:47BC9965.3020002@gmx.de... |B. The Entry, in its entirety, must be contributed under the terms of the SCA. As I read the rules, the proposal is intended to be a new (original) idea, to be implemented by writing *new* code. The new code constitutes the entry. The prize consitutes payment for the new code. It appears to me that the entry may depend on open source code that is not part of the entry itself. "Each Project must use only open source and free software tools and libraries with the exception of any non-free, encumbered binaries that are a part of the OpenJDK code base." They clearly cannot expect entrants to submit already licensed code to their SCA. I would simply be clear in the proposal what new work would constitute the 'entry' and what old work not a part of the 'entry' it might draw upon.
From the previous characterization of the SCA given in this thread, I would expect the the entry author(s) could also contribute it to the PyPy project if appropriate (ie, dual licence it).
tjr
participants (6)
-
Carl Friedrich Bolz -
Chris Lamb -
Jacob Hallén -
Laura Creighton -
Samuele Pedroni -
Terry Reedy