This is the mail archive of the
mailing list for the GCC project.
Re: Why not contribute? (to GCC)
- From: rridge at csclub dot uwaterloo dot ca (Ross Ridge)
- To: gcc at gcc dot gnu dot org
- Date: Sat, 24 Apr 2010 08:12:23 -0400 (EDT)
- Subject: Re: Why not contribute? (to GCC)
Manuel López-Ibáñez writes:
>What reasons keep you from contributing to GCC?
The big reason the copyright assignment. I never even bothered to read
it, but as I don't get anything in return there's no point. Why should
put obligaitons on myself, open myself up to even unlikely liabilities,
just so my patches can merged into the official source distribution?
I work on software on my own time to solve my own problems. I'm happy
enough not "horde" it and give it away for "free", but it doesn't
make much difference to me if anyone else actually ends up using it.
I can have my own patched version of GCC that does what I want without
Another reason is the poor patch submission process. Why e-mail a patch
if I know, as a new contributor, there's a good chance it won't even be
looked at by anyone? Why would I want to go through I a process where I'm
expected to keep begging until my patch finally gets someone's attention?
I also just don't need the abuse. GCC, while not the most of hostile of
open source projects out there, it's up there. Manuel López-Ibáñez's
unjustified hostility towards Michael Witten in this thread is just a
Finally, it's also a lot of work. Just building GCC can be pain, having
to find upto date versions of a growing list of math libraries that
don't benefit me in the slightest way. Running the test suite takes a
long time, so even trivial patches require a non-trivial amount of work.
Anything more serious can take a huge ammount of time. I've abandonded
projects once I realized it would be lot quicker to find some other
solution like using assembly, rather than trying to get GCC to do what
I wanted it to do.
Now these are just the main reasons why I don't contribute to GCC.
I'm not arguing that any these issues need to be or can be fixed. If I
had what I thought where good solutions that would be better overall to
GCC then I'd have suggested them long ago.
I will add, that I don't think code quality is a problem with GCC. I hate
the GNU coding style as much as anyone, but it's used consistantly and
that's what matters. Compared other open and closed projects I've seen
it's as easy to understand and maintain as anything. GNU binutils is
a pile of poo, but I don't know of any codebase the size of GCC that's
as nice to work with.