Add the catalan version of the contributing.html file

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

Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com>

2 files changed, 115 insertions, 42 deletions

diff --git a/src/public/contributing.html b/src/public/contributing.html
index 1cf7702..109659e 100644
--- a/src/public/contributing.html
+++ b/src/public/contributing.html
@@ -1,67 +1,71 @@
+
 <p>
-  Unless stated otherwise, the projects you can find on
-  my <a href="https://git.mssola.com">Git instance</a> or on
-  my <a href="https://github.com/mssola">Github profile</a> are basically
-  personal projects. 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:
+  En principi tots els projectes que veureu a la meva
+  <a href="https://git.mssola.com">instància de Git</a> o al
+  meu <a href="https://github.com/mssola">perfil de Github</a> són personals.
+  Amb això vull dir que honestament no espero cap contribució, però tot i així
+  sempre s'agraeix l'ajuda :-) Si voleu informar d'algun error o suggerir alguna
+  millora, <a href="mailto:mssola@mssola.com" title="mssola@mssola.com">em podeu
+  enviar un correu electrònic</a>. Sinó, si realment voleu contribuir amb
+  canvis, prefereixo que m'envieu pedaços per correu electrònic. És a dir:
 <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.
+    Utilitzeu les comandes natives de Git
+    (p.e. <code>commit</code>, <code>rebase</code>, et al) per tal d'obtenir un
+    llistat de commits que voldríeu que revisés.
   </li>
 
   <li>
-    Write <a href="https://chris.beams.io/posts/git-commit/" title="good commit
-    message">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>.
+    Escriviu <a href="https://chris.beams.io/posts/git-commit/" title="Entrada
+    sobre com escriure bons missatges de Git">bons missatges als
+    commits</a>. Encara millor si estan en l'estil
+    del <a href="https://docs.kernel.org/process/submitting-patches.html"
+    title="Linux kernel">nucli Linux</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.
+    Utilitzeu l'opció <code>--cover-letter</code>
+    de <a href="https://git-scm.com/docs/git-format-patch" title="git
+    format-patch">git format-patch</a> si esteu enviant diversos commits, i
+    expliqueu allà perquè hauria de revisar els vostres canvis.
   </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.
+    Envieu-ho tot amb <a href="https://git-scm.com/docs/git-send-email"
+    title="git send-email">git send-email</a> i miraré de respondre a les
+    propostes de canvi.
   </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.
-</p>
-
-<p>
-Otherwise, if all of this git native shenanigans is beyond your alley of
-expertise, then sending me a Github PR might not be too bad of an idea. 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.
+  Si sou suficientment <em>frikis</em> com per haver fet un fork d'algun
+  projecte meu, aleshores també podríeu utilitzar la comanda nativa de
+  git <a href="https://git-scm.com/docs/git-request-pull"
+  title="git-request-pull manual">request-pull</a>, encara que prefereixo el
+  mètode que suara he llistat amb <code>git-send-email</code>.
 </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.
+  Havent dit això, si tot plegat només us genera dubtes i creieu que va més
+  enllà de l'experiència que teniu amb el desenvolupament de programari, podeu
+  considerar com a últim recurs enviar-me un <a href="https://github.com/mssola"
+  title="El meu perfil de Github">PR a Github</a>. Per a tots els projectes que
+  tinc a la meva
+  <a href="https://git.mssola.com">instància de Git</a>, miro de tenir un mirror
+  a Github que estigui raonablement actualitzat (no prometo res). Igualment, no
+  fusionaria res per allà i ho faria a mà. Això inclou que potser faig canvis en
+  el missatge si s'escau.
 </p>
 
 <p>
-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.
+  Per acabar, m'afegeixo
+  al <a href="https://docs.kernel.org/process/submitting-patches.html#developer-s-certificate-of-origin-1-1"
+  title="Descripció del Certificat d'Origen del Desenvolupador 1.1">Certificat
+  d'Origen del Desenvolupador 1.1</a>. Per tant, per a cada commit necessito
+  el <code>Signed-off-by</code> si voleu que agafi els vostres canvis. A més,
+  si la vostra contribució ha estat feta en qualsevol part del procés amb
+  l'ajuda d'un model de llenguatge, també m'agradaria saber-ho. Agraeixo
+  l'honestedat i faria que el procés de revisió l'encarés d'una altra manera.
 </p>
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>