Re: Classpath future?

[John Keiser]

On 12 Jul 2001 18:37:29 -0400, Jeff Sturm wrote:
> 
> 
> On Thu, 12 Jul 2001, Mark Wielaard wrote:
> > 2b) Losing copyright/attribution when assigning
> 
> Are copyright and attribution really the same?  Would it be acceptable to
> all parties to have a "contributed by:" clause in a source file, but with
> FSF copyright?
> 
> Also, the www site could name significant contributors, much as GCC does
> now.
> 

Agreed.  At this point I think we have at least a partial solution to
the problem.

1. Patches: Savannah is pretty cool, I wasn't really aware of it, not
sure how I missed it.  I'll find that guy's patch and put it up there.
Etienne, please put yours up there if you could.  We'll wrangle this out
somehow :)

2. Assignment: I think people are worried about "who did it," and
rightly so.  Already we have the @author tag in JavaDoc, and I see no
reason we can't put something into the license (or on the site) stating
that all contributions will always maintain the name of the author.

3. Slowness of Contribution: Argh.  I was about to volunteer to write a
page with the agreement.  But *the FSF doesn't have it online anywhere*!
Argh argh argh.

Etienne, I'm not concerned with your forking (don't take that the wrong
way).  If you want to make patches on your own version, go ahead, but
try and stay in sync with the main tree.  The way I see it, by the time
you have enough code to matter, either these issues will be resolved or
forking will be fully justified.

I'm curious now.  Are there forking tools for CVS that let you monitor
for changes in the project you forked off of, and decide whether to
merge the changes in automatically?  (Or even automatically accept all
patches.)

--John