-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a project for which I'd like to use copyright assignment for all contributors. In thinking about it for a bit, I felt like Fossil might work well for this system. My thoughts were to make the contributor agreement a Wiki page, then have people's signatures take the form:
- -- Real Name (fossil username) Then their first commit could include their signature on this page. We'd have a real name to use for legal purposes should it prove necessary, a Fossil user ID to associate with commits. I had a couple questions about this scheme. I know that there's currently not a "fossil wiki annotate" command, but should push come to shove, is it possible to associate a given change on a page to a unique username, or at least to some sort of unique token so we could associate a string of commits and other changes to someone's addition of a signature to the agreement page? I know that Fossil is big on allowing anything to be edited and keeping audit trails. Is there any immediately apparent way that someone might break this scheme? To be clear, I'm sure it isn't foolproof. Putting aside whether or not people think copyright assignment is a good idea, I'm wondering if the idea of tracking it on an integrated Wiki page and tying that directly to new contributors' first commit might not be the neat use case it appears to be? Thanks. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzkJ8UACgkQIaMjFWMehWLbwACfd+fCdKnvVX1BO+4fgN5ON2TY Vo4An3q9WCE0GMxvEvnvDgU2QQ+Wy8d+ =9q/q -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
