[Mesa-dev] [PATCH] docs: Document and *require* usage of Signed-off-by

Jordan Justen jordan.l.justen at intel.com
Thu Nov 29 00:33:01 UTC 2018


On 2018-11-28 13:43:29, Eric Anholt wrote:
> Jordan Justen <jordan.l.justen at intel.com> writes:
> 
> > This adds the "Developer's Certificate of Origin 1.1" from the Linux
> > kernel. It indicates that by using Signed-off-by you are certifying
> > that your patch meets the DCO 1.1 guidelines.
> >
> > It also changes Signed-off-by from being optional to being required.
> >
> > Signed-off-by: Jordan Justen <jordan.l.justen at intel.com>
> > Cc: Matt Turner <mattst88 at gmail.com>
> 
> What problem for our project is solved by signed-off-by?  Do you think
> that it has actually reduced the incidence of people submitting code
> they don't have permission to submit in the projects where it's been
> used?  I know the behavior in the kernel is that people submit a patch,
> it's missing s-o-b, so it gets bounced, then they maybe add s-o-b or
> just give up.  I don't think anyone stops and says "Wow, that's a good
> question.  Maybe I don't have permission to distribute this after all?"

Is it possible that some of the cases of "just give up" were "Oh I
didn't think about that. I guess I actually don't have permission to
contribute this under that license."?

It seems like contributors have to spend a little brain power once to
read and ponder the ~25 line document with regards to their
contributions, and then just add a -s to their commit command line.

-Jordan


More information about the mesa-dev mailing list