From 4a985b7cd28515a64724df53f8f13c395a1aa0ca Mon Sep 17 00:00:00 2001
From: Miquel Sabaté Solà <mssola@mssola.com>
Date: Tue, 21 Jul 2026 22:27:45 +0200
Subject: Add the catalan version of the contributing.html file
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This also includes a few fixes and touches on the english one.

Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com>
---
 src/public/en/contributing.html | 69 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 69 insertions(+)
 create mode 100644 src/public/en/contributing.html

(limited to 'src/public/en/contributing.html')

diff --git a/src/public/en/contributing.html b/src/public/en/contributing.html
new file mode 100644
index 0000000..9fb236e
--- /dev/null
+++ b/src/public/en/contributing.html
@@ -0,0 +1,69 @@
+<p>
+  Unless stated otherwise, the projects you can find on
+  my <a href="https://git.mssola.com">own Git instance</a> or on
+  my <a href="https://github.com/mssola">Github profile</a> are basically
+  personal ones. That is to say that I don't expect contributions, to be
+  honest. But regardless of that, patches are always welcome :-) If you want to
+  report something odd or suggest an improvement,
+  just <a href="mailto:mssola@mssola.com" title="mssola@mssola.com">send me an
+  email</a>. Otherwise, if you have some changes that you would want to
+  contribute in, you should know that my preferred way to accept patches is via
+  email. That is:
+<p>
+
+<ul>
+  <li>
+    Use git's native commands (e.g. <code>commit</code>, <code>rebase</code>, et
+    al) to build a list of commits you'd like me to review.
+  </li>
+
+  <li>
+    Write <a href="https://chris.beams.io/posts/git-commit/" title="Blog post on
+    how to write good commit messages">good commit messages</a>. Extra points if
+    they are in the style of
+    the <a href="https://docs.kernel.org/process/submitting-patches.html"
+    title="Linux kernel">Linux kernel</a>.
+  </li>
+
+  <li>
+    Use the <code>--cover-letter</code> option
+    in <a href="https://git-scm.com/docs/git-format-patch" title="git
+    format-patch">git format-patch</a> if you are sending multiple commits, and
+    explain to me why I should merge your changes there.
+  </li>
+
+  <li>
+    Send everything via <a href="https://git-scm.com/docs/git-send-email"
+    title="git send-email">git send-email</a> and expect some back and forth via
+    email.
+  </li>
+</ul>
+
+<p>
+If you are crazy enough to have a fork of some of my projects, then you can also
+consider using git's native <a href="https://git-scm.com/docs/git-request-pull"
+title="git-request-pull manual">request-pull</a> command, even if I still prefer
+the aforementioned <code>git-send-email</code> method.
+</p>
+
+<p>
+Otherwise, if all of this git native shenanigans is beyond your alley of
+expertise, then, and as a last resort, sending me
+a <a href="https://github.com/mssola" title="my Github profile">Github PR</a>
+might not be too bad of an idea. For each project listed on
+my <a href="https://git.mssola.com">own Git instance</a> I try to have a mirror
+on Github that is reasonably up to date (no promises). That being said, I would
+still merge everything manually and I'd still possibly change the commit message
+if I feel like it could be improved but I don't want to bother you with new
+versions just because of the git commit message.
+</p>
+
+<p>
+Last but not least, I adhere to
+the <a href="https://docs.kernel.org/process/submitting-patches.html#developer-s-certificate-of-origin-1-1"
+title="Description of the Developer's Certificate of Origin 1.1">Developer's
+Certificate of Origin 1.1</a>. Thus, you must sign off all your commits if you
+want me to pull any of your changes. If your contribution was in any way
+developed with the aid of an LLM, I'd also like to know it, as I'd appreciate
+the honesty and I would tacke the review process differently.
+</p>
-- 
cgit v1.2.3