tallship/telodendria
1
0
Fork 0
forked from Telodendria/Telodendria
Code Issues Pull requests Projects Releases Packages Wiki Activity

Add a DCO

Browse source
This commit is contained in:
Jordan Bancino 2022-08-25 07:16:07 -04:00
parent d8a89c4750
commit 2b72dd0dba
2 changed files with 58 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

76
site/index.html
View file

@ -1029,30 +1029,62 @@ made, but the information there can be made more accurate by setting
<code>MXID</code> to your Matrix ID, and <code>DISPLAY_NAME</code> to <code>MXID</code> to your Matrix ID, and <code>DISPLAY_NAME</code> to
your real name in your environment, or the <code>.env</code> file. your real name in your environment, or the <code>.env</code> file.
The <code>Subject</code> should very briefly describe what the patch The <code>Subject</code> should very briefly describe what the patch
is about. Below these headers, write a more in-depth description of is about.
the patch.
</p> </p>
<p> <p>
Then, send the resulting patch file to You'll also notice these lines:
<code>#telodendria-patches:bancino.net</code>, so it can be </p>
discussed and reviewed by the community. If you don't have a Matrix <div class="code">
account, and you <i>really</i> don't want to create one&mdash;ignoring [ ] I have read the Telodendria Project developer certificiate of
how odd it is that you are trying to contribute to a <i>Matrix</i> origin, and certify that I have permission to submit this patch
homeserver project&mdash;you can email your patches to under the conditions specified in it.
<a href="mailto:jordan@bancino.net">jordan@bancino.net</a>. However, </div>
the preferred way of submitting patches is to the official Matrix room, <p>
so I will upload your patch there along with your email address. If you This is a checkbox that tells me whether or not you actually have
are going to send patches via email, <b>they must be plain text</b> emails, the rights to submit your patch, and that once you submit the patch,
and the patch must be in the main body of the email. No MIME, base64, or your code is bound by the Telodendria license. The full text of the
printed-quotable garbage. I will silently reject emails that are not developer certificate of origin is as follows:
purely plain text. I should be able to write a raw copy of your message to </p>
an <code>mbox</code> file, and then apply it onto my code right from <ol>
there, with no further processing. If you're going to be a regular contributor, <li>The contribution was created in whole or in part by me, and I have
it would just be easier to create a Matrix account. It doesn't have to be the right to submit it under the open source license of the Telodendria
on my public homeserver, but it certainly can be. Note that the discussion and project; or</li>
ultimately the decision on what to do with your patch will all happen in <li>The contribution is based upon a previous work that, to the best
the Matrix room, so if you submit patches using email, you'll miss out on of my knowledge, is covered under an appropriate open-source license
any feedback. and I have the right under that license to submit that work with
modifications, whether created in whole or in part by me, under the
Telodendria project license; or</li>
<li>The contribution was provided directly to me by some other person
who certified (1), (2), or (3), and I have not modified it.</li>
<li>I understand and agree that this project and the contribution are
public and that a record of the contribution&mdash;including all
personal information I submit with it&mdash;is maintained indefinitely
and may be redistributed consistent with this project or the open-source
licenses involved.</li>
</ol>
<p>
After the headers, but before the checkbox, write a more thorough
description of the patch and why it was created. Then, send the
resulting patch file to <code>#telodendria-patches:bancino.net</code>,
so it can be discussed and reviewed by the community. If you don't
have a Matrix account, and you <i>really</i> don't want to create
one&mdash;ignoring how odd it is that you are trying to contribute
to a <i>Matrix</i> homeserver project&mdash;you can email your
patches to <a href="mailto:jordan@bancino.net">jordan@bancino.net</a>.
However, the preferred way of submitting patches is to the official
Matrix room, so I will upload your patch there along with your email
address. If you are going to send patches via email, <b>they must
be plain text</b> emails, and the patch must be in the main body
of the email. No MIME, base64, or printed-quotable garbage. I will
silently reject emails that are not purely plain text. I should be
able to write a raw copy of your message to an <code>mbox</code>
file, and then apply it onto my code right from there, with no
further processing. If you're going to be a regular contributor,
it would just be easier to create a Matrix account. It doesn't have
to be on my public homeserver, but it certainly can be. Note that
the discussion and ultimately the decision on what to do with your
patch will all happen in the Matrix room, so if you submit patches
using email, you'll miss out on any feedback.
</p> </p>
<p> <p>
Try to keep your patches on topic&mdash;make one patch file per feature Try to keep your patches on topic&mdash;make one patch file per feature

4
tools/bin/td
View file

@ -234,6 +234,10 @@ recipe_patch() {
echo "Date: $(date)" echo "Date: $(date)"
echo "Subject: " echo "Subject: "
echo echo
echo "[ ] I have read the Telodendria Project developer certificate"
echo " of origin, and certify that I have permission to submit"
echo " this patch under the conditions specified in it."
echo
cvs -q diff -uNp $PATCHSET | grep -v '^\? ' cvs -q diff -uNp $PATCHSET | grep -v '^\? '
) > "$PATCH_FILE" ) > "$PATCH_FILE"