So many open source projects enforce the Signed-off-by line in commit messages without assigning any menaing to it. I am not a laywer, but I believe such line bares no meaning unless otherwise specified (and even then it is questionable, at least).

Requring a magical incantation in commit messages is an artificial obstacle for contributing, especially for beginners. If your project does that, try to figure out if you can drop the requrement. Thanks

@hroncok this is absolutely bad advice. instead, projects should explicitly adopt the DCO, so the sign-off has meaning.

git commit --signoff automatically adds the line anyway.

@ariadne @hroncok I'd argue that the line is stupid and needs to go away. What you need to have is an explicit statement of what policy was signed off by. Because people just add it all the time by default, and don't actually know what the policy is of projects they submit to.

Then you can argue that any surprising policy is void for German contributors since they can't be considered to read them (that's the rule for ToS, and arguably those are ToS).

Worst
Design
Ever.

@juliank @ariadne @hroncok aside the legalities, if A authored, B proposed on list, C picked into staging and sent the final merge request... Signed-off-by has a clear chain where otherwise that info would be lost
@dango_ @ariadne @hroncok That's true sure. Some chain needs to be there, but it's hard to argue that people actually read the policy they signed off by.