[OpenJDK Rasterizer] Rasterizer replacement proposal
roman.kennke at aicas.com
Tue Jun 12 10:32:51 PDT 2007
> getting back on the list.
> >> 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
> > software after all. Are you not allowed to look at any code except Sun
> > copyrighted?
> Yes, our understanding is that we can not look at your code until
> you share the copyright (and we can be reasonably sure that you
> own that copyright) - both of these conditions are not yet
> satisfied here - the second one because you mentioned about
> the possibility of your employer's involvement, so we wanted
> to clarify that first.
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
review my code before I start the copyright grantback dance for that
code. I am currently discussing this issue with Tom Marble and Mark
> >> I hope we'll make it easier for you and others to work
> >> directly with our 2D workspace instead of waiting for
> >> the fix to propagate to the main j2se workspace.
> > Yeah, this seems like the biggest complaint right now. It is not
> > possible for the community (e.g. me) to help out with code like this
> > when development is basically done behind closed doors. I am quite
> > that I could help out with both the rasterizer as well as with the
> > fonts, but it doesn't make much sense (and isn't very motivating) to
> > develop against code that is a couple of days/weeks old.
> I agree that the current situation is totally unacceptable.
> 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).
That'd be great.
> We'll have to send you the actual diffs directly, though,
> as you won't be able to access the web interface.
I prefer that anyway, as this is how it works in other projects I'm
> > 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?).
> I'll see if we could arrange that. I believe that it is our
> intention anyway - once we move to Mercurial each "group" will have
> their read/write mercurial workspace and members of the group
> will have read and in some cases write access.
> But at this point even a read-only svn workspace would help.
Kind regards, Roman
Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org
aicas Allerton Interworks Computer Automated Systems GmbH
Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany
http://www.aicas.com * Tel: +49-721-663 968-0
USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe
Geschäftsführer: Dr. James J. Hunt
More information about the graphics-rasterizer-dev