[OpenJDK Rasterizer] Rasterizer replacement proposal
mark at klomp.org
Tue Jun 12 11:23:10 PDT 2007
Dmitri Trembovetski <Dmitri.Trembovetski at ...> writes:
> Roman Kennke wrote:
> However, in this case it will be useful for everybody
> else to understand the restrictions under which we currently
Thanks, that is useful.
> 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 question in this case since it all comes from
GNU Classpath. It is exactly the same as OpenJDK is already using (GPL +
classpath) and you can be sure that the FSF made sure sure all that code is as
clean as can be. They are kind of pedantic about that :)
> > 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.
After having played with mercurial a bit I am really looking forward to the full
rollout. It seems a very good pick for the way openjdk is setup.
More information about the graphics-rasterizer-dev