Re: [Gomp-discuss] Copyright Assignment

[Diego Novillo]

On Tue, 11 Feb 2003, Scott Robert Ladd wrote:

> > The code goes where-ever you please.  Starting a new GNU project is a
> > hassle, but aren't we just part of the GCC project?
> 
> I was under the impression that the gcc folk wanted us to be a separate
> project until they "approved" of us.
> 
Eh?  Where did you get that idea?  Working on a branch is exactly
what we need to do before being accepted.  This is how it
generally works (it's worked for me and tree-ssa, it's also
worked for the RA, for the CFG optimizer and the parser):

- Work starts on a branch.  Hardly anybody notices what you're
  doing.

- All the patches and design ideas are posted to the GCC lists.
  Usually, just the folks working on that branch will care to
  reply and emit opinions.  Although, you might get a few other
  comments.

- If what you're proposing is completely insane you will get more
  feedback, of course.

- Once the branch starts showing definite and measurable results,
  people will start paying attention.  That's when you start
  evaluating whether or not things might be ready to merge into
  mainline.  You then propose the merge, show what the
  improvements are.  
  
- Phasing in a mainline merge depends on many factors.  It's best
  if we can structure it so that patches are self-contained and
  easy to review.


> > (assuming you have a copyright assignment for GCC).
> 
> Well, I don't have one. I assume that's a problem?
> 
Definitely.  You cannot contribute code to GCC if you don't have
an copyright assignment with the FSF.


Diego.