Re: [AnyC-devel] copyright issues

[Daniel W. <dan...@ro...>]

> I can see your point with these issues.  I do not have any problem
> with them.  I'll go so far as to say that for any code I have
> committed, or will commit to the CVS, I assign copyright ownership to
> you.  Because of this, I may choose to leave what I consider to be
> interesting changes outside of the CVS.  They would be incorporated
> as patches or as a forked version, as allowed by the GPL.  That said,
> I'm not anticipating anything interesting very soon, so I imagine
> that won't even be an issue for now.  If I do make some sort of
> interesting change, perhaps we can work something out, where I
> receive recognition for it, and you get copyright ownership on it.
> Anyways, we'll have to jump over those hurdles when and if we come to
> them.  For now, it's all yours, and full speed ahead.

  Great!  Some people get pretty annoyed at anything that's not "pure" GP=
L. =20
I'm guessing you probably understand the intricacies of the license.  The=
=20
only difference this would make is that I could take the GPL version and =
make=20
an "extended" version that was not GPL, or even dual license the current=20
version.  Obviously anything released under the GPL can't be "taken back"=
=2E =20
  Realistically, the scenario I was thinking of was if a company wanted t=
o=20
incorporate this program into a commercial compiler.  As much as it is wr=
ong,=20
many buisiness people believe that proprietary and expensive code is alwa=
ys=20
higher quality. =20
  As you say, though, this is all in the future.  I just wanted to clear =
it=20
up now just in case. =20

> I haven't heard from you since this letter, so I assume you're not
> finished.  I had almost no time on my trip to do anything
> interesting, so I didn't have time to review the AnyC source as I had
> wanted.  Is some of the documentation you're writing an architectural
> overview of the project?  It would be rather helpful for me to see
> the big picture of what's going on in the compiler.

  I haven't worked on the docs since then, but I will soon.  I am trying =
to=20
write "big-picture" documentation first.  It is harder than I thought it=20
would be.  It will probably be much easier on you if you wait for at leas=
t=20
some of the new docs I am writing before you try to tackle the source.  I=
=20
think the methods I am using are logical, but they probably aren't just l=
ike=20
other compilers, since I have never worked on compilers before this, and =
I'm=20
not a computer science student.