-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a link to DCO text or bot to comment the plain text of DCO #106
Comments
https://developercertificate.org/ works fine for me. PRs welcome to edit the text in the checks DCO creates. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
yup, for the sake of a better experience of newcomers/beginners vs skilled ones that want to enable DCO. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
Yes. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
yup yup |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
Yes. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
👍 💯 |
👍 Allow customization on the comment text would be awesome. Can we help with sending a PR? |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
hey I've started to help out maintaining DCO. Would you like to send a PR? I promise I won't let it get stale |
Hi @gr2m, Meanwhile, we have chosen another solution. 🙁 |
@gr2m just seen that notification. Cool. I may send some PR in the coming weeks. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
…have Fix: dcoapp#106 Signed-off-by: d3fault <[email protected]>
…have Fix: dcoapp#106 Signed-off-by: d3fault <[email protected]>
…have Fix: dcoapp#106 Signed-off-by: d3fault <[email protected]>
This is a much more important issue than you guys are giving it credit! Currently there's no legal binding between --signoff and the DCO!! Requiring people to pass that --signoff flag currently is about as productive as putting a single "1" or "true" variable into a database with absolutely no meaning given to it. I'm sure you put lots of effort into making this bot function........ but without that legal binding it's all for nothing. I submitted a PR #165 as an attempt to create that legal binding, but so far it's just getting ignored. What gives? Also: I Am Not Lawyer. The "legally binding" text should probably be reviewed by one. |
Because newcomers may not be so familiar with all the things. I can't find any way to find the DCO text. I know what DCO stands for and what is that bot, but someone may not know that, so... it makes friction.
Best would be the bot to comment on the text on failure. Or at least link to always available, for some reason currently I cannot load the https://developercertificate.org/ but it seems up.
The text was updated successfully, but these errors were encountered: