On Mon, Aug 25, 2014 at 09:47:29AM -0600, Sebastian Kuzminsky wrote: > > It somewhat raises the barrier-to-entry for casual contributors: they > now have to know to use the -s flag to git commit. I guess it's easy > enough for the reviewers to inform them about it, or to add the SOB > themselves, so not a huge deal.
I don't think it's a big barrier. It's especially important to make license explicit for one-off commits that come from people we may never hear from or be able to contact again. I agree it's a slight burden but I think it's a necessary one. > How are long branches handled? For example, only about half of the > commits in joints_axes5 have SOB tags. Would someone have to edit all > the commits the next time the branch is rebased? Or would it suffice to > have a SOB tag on the merge commit? I think having a cutoff date (which is already in the proposal) is the best way to deal with this. Commits after we decide to do this must have s-o-b. Commits from before are the same as they ever were. ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
