> That's because you didn't look at non-open code. It's no better. Nobody said it was.
> This statement carries an implicit assumption that the only barrier > for contribution to GCC is the "high quality of code required". > This is not true. For one, copyright assignment requirement > is an untypical requirement for open-source world, > and may turn away some contributors. I said "A" large part. There is certainly a perception that the copyright assignment is an issue too. But, as was discussed here, there IDENTICAL liability with and without the assignment. So this is illusory. And if the reason for not wanting to assign the copyright is that they aren't comfortable with the code being part of the project, then there's a larger problem than the assignment itself.
