Hi Roman,
getting back on the list.
Roman Kennke wrote:
Hi Dmitri,
first of all, you should continue discussion on the mailing list IMO. It
doesn't leave a good impression against 'the community' when half of the
discussions are held privately. I won't CC the list now though, because
you
Dmitri Trembovetski wrote:
> It is also unfortunate that you do not have access to our
> code review system - although this is relatively easy
> to fix - we can include you as a reviewer in relevant
> code changes (the system is email and web-based).
>
> We'll have to send you the actual
Note that the webrev includes some of the closed sources too :
Javadocs Cdiffs Sdiffs Old New
src/closed/share/classes/sun/dc/pr/PathStroker.java
Javadocs Cdiffs Sdiffs Old New src/closed/share/native/sun/dc/pr/PathStroker.c
I am quite sure they would need to be [manually] elided.
-phil.
Tom
Hi Jim,
> The status on the pluggability API is that it is now completed and in
> our 2D integration workspaces waiting to go through the testing and
> promotion queues. The best current estimate as to when all of that
> process will be done is that it will probably appear on the OpenJDK
> pr
Roman Kennke wrote:
Hi,
I will send in my signed SCA the next couple of days, and at the same
time find out who is the actual copyright owner (me, or aicas - my
employer -, aicas already signed the SCA even). The remaining issue is
that the copyright is assigned to the FSF. I have hoped that y
Hi,
>getting back on the list.
Good!
> >>I think there are still legal issues preventing
> >>us looking at this code =(
> >
> > Unbelievable. But oh well... Why exactly can't you *look* at the code.
> > Because it's not submitted via the SCA? I mean, it's free, open source
> > softw
Hi,
> > I will send in my signed SCA the next couple of days, and at the same
> > time find out who is the actual copyright owner (me, or aicas - my
> > employer -, aicas already signed the SCA even). The remaining issue is
> > that the copyright is assigned to the FSF. I have hoped that you would
Roman Kennke wrote:
When I wrote this code for GNU Classpath, I assigned copyright to the
FSF, just like OpenJDK contributions are copyright-assigned to Sun. With
the difference that the SCA is automatically granting the contributor
all rights to the code, while with the FSF CA I need to go thr
Hi Phil,
> > When I wrote this code for GNU Classpath, I assigned copyright to the
> > FSF, just like OpenJDK contributions are copyright-assigned to Sun. With
> > the difference that the SCA is automatically granting the contributor
> > all rights to the code, while with the FSF CA I need to go t
Roman Kennke <[EMAIL PROTECTED]> writes:
> > > The remaining issue is
> > > that the copyright is assigned to the FSF. I have hoped that you would
> > > review my code before I start the copyright grantback dance for that
> > > code. I am currently discussing this issue with Tom Marble and Mark
> >
Dmitri Trembovetski <[EMAIL PROTECTED]> writes:
> Roman Kennke wrote:
>However, in this case it will be useful for everybody
>else to understand the restrictions under which we currently
>operate.
Thanks, that is useful.
>I don't think it's Sun only policy, pretty much any company
Hi Mark,
> >I don't think it's Sun only policy, pretty much any company has it.
> >It is easy to become tainted by looking at other's people code.
> >The fact that the code is open-source doesn't matter, since
> >it's a question of copyright.
>
> Note that the copyright isn't in q
> From: [EMAIL PROTECTED]
> Date: Tue, 12 Jun 2007 19:32:51 +0200
> ...
>>> I think it would make sense to at least provide read access to the real
>>> group workspace (if you're paranoid then maybe only to group members,
>>> but then comes the question, how can anybody become a group member?).
>>
13 matches
Mail list logo
