Drop the "sign-off" from the requirements?
Background: back in the SMF-era, the "sign-off" was introduced in order to kind of replace the CLA. Obviously the two things are completely different.
So, the question is: after ne year and a half of development, do we still need that "tool"?
What do you think about dropping that requirement from the contributions?
Re: Drop the "sign-off" from the requirements?
Reply #3 –
Does it benefit tracking contributions, or do you have other methods to do that?
If the former, keep it. If the latter, toss it.
Re: Drop the "sign-off" from the requirements?
Reply #4 –
It's too make sure all contributions follow the BSD license right? So no one tries to claim you didn't have rights to their code later.
Re: Drop the "sign-off" from the requirements?
Reply #9 –
Sorry to be the basis of this, I had never heard of this sign off thing and github's pull request instructions didn't mention it.. I amended the commit with a signoff and pushed it to github.
Agree these don't seem to have much legal basis, but I'll also state here that my patch is made available under the same BSD license as the rest of Elkarte.