-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How does it work (legally) for someone in the community to submit a patch? I've always viewed the process for someone to become a committer to be that they must first submit some code indirectly (meaning, an existing committer vets it and then checks it in to source control). After a few rounds of submitting code that way, the person can be approved by the community as a new committer (at which point they submit a CLA and gain write access to source control).
However, how do we know that the code they submit indirectly is clear of copyright and license restrictions? Is it up to the committer that actually checks it in to verify it is clear? If so, how do we go about verifying that? Thanks, Josh - -- - ------------------------------- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFLHnJ3V/LQcNdtPQMRArhLAJ9I9w3bNXzpp4ZZa9KmaaDyaU8kUQCbB5Fu wGRcJxiwEPYzAM+yFRxWFc4= =y+g1 -----END PGP SIGNATURE-----
