[Git][reproducible-builds/reproducible-website][master] 3 commits: Publish our new Code of Conduct
Mattia Rizzolo (@mattia)
gitlab at salsa.debian.org
Wed Sep 16 17:16:45 UTC 2026
Mattia Rizzolo pushed to branch master at Reproducible Builds / reproducible-website
Commits:
df0cb783 by Mattia Rizzolo at 2026-09-16T19:13:33+02:00
Publish our new Code of Conduct
Signed-off-by: Mattia Rizzolo <mattia at debian.org>
- - - - -
86434786 by Mattia Rizzolo at 2026-09-16T19:13:36+02:00
CoC typos
Signed-off-by: Mattia Rizzolo <mattia at debian.org>
- - - - -
ca36d617 by Mattia Rizzolo at 2026-09-16T19:16:18+02:00
Link the CoC in the footer
Signed-off-by: Mattia Rizzolo <mattia at debian.org>
- - - - -
13 changed files:
- + _conduct/committee.md
- + _conduct/conduct.md
- + _conduct/enforcement-manual.md
- + _conduct/faq.md
- + _conduct/reporting-guide.md
- _config.yml
- + _data/conduct.yml
- _events/gothenburg2026/index.html
- _includes/footer.html
- + _layouts/conduct.html
- contribute/index.md
- po/_pages.de.po
- po/_pages.pot
Changes:
=====================================
_conduct/committee.md
=====================================
@@ -0,0 +1,19 @@
+---
+layout: conduct
+title: Code of Conduct Committee
+short_title: Committee
+permalink: /conduct/committee/
+order: -1
+---
+
+# Code of Conduct Committee
+
+The current Code of Conduct Committee can be reached via email on
+`conduct at reproducible-builds.org`.
+
+The current members are:
+
+ * Chris Lamb <conduct.chris at reproducible-builds.org> (Chair)
+ * Holger Levsen <conduct.holger at reproducible-builds.org>
+ * Karen Sandler <conduct.karen at reproducible-builds.org>
+
=====================================
_conduct/conduct.md
=====================================
@@ -0,0 +1,90 @@
+---
+layout: conduct
+title: Reproducible Builds Code of Conduct
+permalink: /conduct/
+order: -1
+redirect_from: /conduct/.
+---
+
+# Reproducible Builds Code of Conduct
+
+Like the technical community as a whole, the team and community that comprises
+Reproducible Builds is made up of a mixture of volunteers and professionals
+from all over the world, working on every aspect of our mission.
+
+We have a few ground rules that we ask people to adhere to. This code applies
+equally to founders, mentors and those seeking help and guidance.
+
+This isn't an exhaustive list of things that you can't do. Rather, take it in
+the spirit in which it's intended - a guide to make it easier to enrich all of
+us and the technical communities in which we participate.
+
+This code of conduct applies to all spaces managed by Reproducible Builds. This
+includes IRC, the mailing lists, the issue tracker, Reproducible Builds events,
+and any other forums created by the project team which the community uses for
+communication. In addition, violations of this code outside these spaces may
+affect a person's ability to participate within them.
+
+If you believe someone is violating the code of conduct, we ask that you report
+it by emailing conduct at reproducible-builds.org. For more details please see our
+[Reporting Guidelines](reporting-guide/).
+
+* **Be friendly and patient.**
+
+* **Be welcoming.** We strive to be a community that welcomes and supports
+ people of all backgrounds and identities. This includes, but is not limited
+ to members of any race, ethnicity, culture, national origin, colour,
+ immigration status, social and economic class, educational level, sex, sexual
+ orientation, gender identity and expression, age, size, family status,
+ political belief, religion, and mental and physical ability.
+
+* **Be considerate.** Your work will be used by other people, and you in turn
+ will depend on the work of others. Any decision you take will affect users
+ and colleagues, and you should take those consequences into account when
+ making decisions. Remember that we're a world-wide community, so you might
+ not be communicating in someone else's primary language.
+
+* **Be respectful.** Not all of us will agree all the time, but disagreement is
+ no excuse for poor behavior and poor manners. We might all experience some
+ frustration now and then, but we cannot allow that frustration to turn into a
+ personal attack. It's important to remember that a community where people
+ feel uncomfortable or threatened is not a productive one. Members of the
+ Reproducible Builds community should be respectful when dealing with other
+ members as well as with people outside the Reproducible Builds community.
+
+* **Be careful in the words that you choose.** We are a community of
+ professionals, and we conduct ourselves professionally. Be kind to others. Do
+ not insult or put down other participants. Harassment and other exclusionary
+ behavior aren't acceptable. This includes, but is not limited to:
+
+ * Violent threats or language directed against another person.
+ * Discriminatory jokes and language.
+ * Posting sexually explicit or violent material.
+ * Posting (or threatening to post) other people's personally identifying
+ information ("doxing").
+ * Personal insults, especially those using racist or sexist terms.
+ * Unwelcome sexual attention.
+ * Advocating for, or encouraging, any of the above behavior.
+ * Repeated harassment of others. In general, if someone asks you to stop,
+ then stop.
+
+* **When we disagree, try to understand why.** Disagreements, both social and
+ technical, happen all the time and Reproducible Builds is no exception. It is
+ important that we resolve disagreements and differing views constructively.
+ Remember that we're different. The strength of our project comes from its
+ varied community, people from a wide range of backgrounds. Different people
+ have different perspectives on issues. Being unable to understand why someone
+ holds a viewpoint doesn't mean that they're wrong. Don't forget that it is
+ human to err and blaming each other doesn't get us anywhere. Instead, focus
+ on helping to resolve issues and learning from mistakes.
+
+Original text courtesy of the
+[Django Code of Conduct](https://web.archive.org/web/20240715222256/https://www.djangoproject.com/conduct/), which is itself
+based on material by the
+[Speak Up!](http://web.archive.org/web/20141109123859/http://speakup.io/coc.html)
+project.
+
+## Questions?
+
+If you have questions, please see [the FAQ](faq/)
+If that doesn't answer your questions, feel free to [contact us](mailto:conduct at reproducible-builds.org).
=====================================
_conduct/enforcement-manual.md
=====================================
@@ -0,0 +1,136 @@
+---
+layout: conduct
+title: Reproducible Builds Code of Conduct - Enforcement Manual
+short_title: Enforcement Manual
+permalink: /conduct/enforcement-manual/
+order: -1
+---
+
+# Reproducible Builds Code of Conduct - Enforcement Manual
+
+This is the enforcement manual followed by the Reproducible Builds Code of
+Conduct Committee. It's used when we respond to an issue to make sure we're
+consistent and fair. It should be considered an internal document, but we're
+publishing it publicly in the interests of transparency.
+
+## The Code of Conduct Committee
+
+All responses to reports of conduct violations will be managed by a
+[Code of Conduct Committee]({{ "/conduct/committee" | relative_url }}) ("the committee").
+
+The Reproducible Builds [core team]({{ "/who/people/#core-team" |relative_url }}) will establish this committee, comprised of
+at least three members. One member will be designated chair of the committee
+and will be responsible for all reports back to the core team. The core team
+will review membership on a regular basis.
+
+## How the committee will respond to reports
+
+When a report is sent to the committee they will immediately reply to the
+report to confirm receipt. This reply must be sent within 24 hours, and the
+committee should strive to respond much quicker than that.
+
+See the [reporting guidelines]({{ "/conduct/reporting-guide/" |relative_url }}) for details of what reports
+should contain. If a report doesn't contain enough information, the committee
+will obtain all relevant data before acting. The committee is empowered to act
+on Reproducible Builds behalf in contacting any individuals involved to get a
+more complete account of events.
+
+The committee will then review the incident and determine, to the best of their
+ability:
+
+* what happened
+
+* whether this event constitutes a code of conduct violation
+
+* who, if anyone, was the bad actor
+
+* whether this is an ongoing situation, and there is a threat to anyone's
+ physical safety
+
+This information will be collected, and whenever possible the committee's
+deliberations will be recorded and retained (i.e. IRC transcripts, email
+discussions, recorded voice conversations, etc).
+
+The committee should aim to have a resolution agreed upon within one week. In
+the event that a resolution can't be determined in that time, the committee
+will respond to the reporter(s) with an update and projected timeline for
+resolution.
+
+## Acting Unilaterally
+
+If the act is ongoing (such as someone engaging in harassment in
+`#reproducible-builds`), or involves a threat to anyone's safety (e.g. threats
+of violence), any committee member may act immediately (before reaching
+consensus) to end the situation. In ongoing situations, any member may at their
+discretion employ any of the tools available to the committee, including bans
+and blocks.
+
+If the incident involves physical danger, any member of the committee may — and
+should — act unilaterally to protect safety. This can include contacting law
+enforcement (or other local personnel) and speaking on behalf of the
+Reproducible Builds project.
+
+In situations where an individual committee member acts unilaterally, they must
+report their actions to the committee for review within 24 hours.
+
+## Resolutions
+
+The committee must agree on a resolution by consensus. If the committee cannot
+reach consensus and deadlocks for over a week, the committee will turn the
+matter over to the core team for resolution.
+
+Depending on the specific situation, the committee may then share their
+proposed response to the reporting person, and we'll check with them before
+going forward with any action.
+
+Possible responses may include:
+
+* Taking no further action (if we determine no violation occurred).
+
+* A private reprimand from the committee to the individual(s) involved. In this
+ case, a committee member will deliver that reprimand to the individual(s)
+ over email, cc'ing the committee.
+
+* A public reprimand. In this case, a committee member will deliver that
+ reprimand in the same venue that the violation occurred (i.e. in IRC for an
+ IRC violation; email for an email violation, etc.). The committee may choose
+ to publish this message elsewhere for posterity.
+
+* An imposed vacation (i.e. asking someone to "take a week off" from a mailing
+ list or IRC). A committee member will communicate this "vacation" to the
+ individual(s). They'll be asked to take this vacation voluntarily, but if
+ they don't agree then a temporary ban may be imposed to enforce this
+ vacation.
+
+* A permanent or temporary ban from some or all Reproducible Builds spaces
+ (mailing lists, IRC, etc.). The committee will maintain records of all such
+ bans so that they may be reviewed in the future, extended to new RB fora, or
+ otherwise maintained.
+
+* A request for a public or private apology. a committee member will deliver
+ this request. The committee may, if it chooses, attach "strings" to this
+ request: for example, the committee may ask a violator to apologize in order
+ to retain his or her membership on a mailing list.
+
+* Once a resolution is agreed upon, but before it is enacted, the committee
+ will contact the original reporter and any other affected parties and share
+ their proposed resolution. The committee will ask if this resolution is
+ acceptable, and must note feedback for the record. However, the committee is
+ not required to act on this feedback.
+
+Finally the committee will make a report for the Reproducible Builds core team.
+In case the incident or report involves a current member of the core team, the
+committee will provide the report only to the other core team members.
+
+The committee will never publicly discuss the issue; all public statements will
+be made by the Reproducible Builds core team.
+
+## Conflicts of Interest
+
+In the event of any conflict of interest a committee member must immediately
+notify the other members, and recuse themselves if necessary. If a report
+concerns a possible violation by a current committee member, this member should
+be excluded from the response process. For these cases, anyone can make a
+report directly to any of the committee chairs, as documented in the
+[reporting guidelines]({{ "/conduct/reporting-guide" | relative_url }}).
+
=====================================
_conduct/faq.md
=====================================
@@ -0,0 +1,91 @@
+---
+layout: conduct
+title: Reproducible Builds Code of Conduct - FAQ
+short_title: Frequently Asked Question
+permalink: /conduct/faq/
+order: -1
+---
+
+# Reproducible Builds Code of Conduct - FAQ
+
+This FAQ attempts to address common questions and concerns around the
+Reproducible Build community's Code of Conduct. If you still have questions
+after reading it, please feel free to contact us.
+
+## Why have you adopted a Code of Conduct?
+
+We think the Reproducible Builds community is awesome. If you're familiar with
+the RB community, you'll probably notice that the Code basically matches what
+we already do. Think of this as documentation: we're taking implicit
+expectations about behavior and making them explicit.
+
+We're doing this because the Reproducible Builds community has grown faster
+than any of us could have anticipated in 2014. This is on balance a very
+positive thing, but as we've grown past the point where it's possible to know
+the whole community we think it's very important to be clear about our values.
+
+We know that the Reproducible Builds community is open, friendly, and
+welcoming. We want to make sure everyone else knows it too.
+
+## What does it mean to "adopt" a Code of Conduct?"
+
+For the most part, we don't think it means large changes. We think that the
+text does a really good job describing the way the Reproducible Builds
+community already conducts itself. We expect that most people will simply
+continue to behave in the awesome way they have for years.
+
+However, we do expect that people will abide by the spirit and words of the CoC
+when in "official" Reproducible Builds spaces. This code has been adopted by
+both the RB core team and SFC. That means that it'll apply both in community
+spaces and at Reproducible Builds events.
+
+In practice, this means mailing lists (rb-general, etc.), the various
+Reproducible Builds IRC channels (`#reproducible-builds`, etc.), bug tracking
+and code review tools, and "official" Reproducible Builds events such as
+our summits. In addition, violations of this code outside these spaces may
+affect a person's ability to participate within them.
+
+This Code of Conduct is all about how we interact as a community. It's about
+saying that the Reproducible Builds community will be open, friendly, and
+welcoming. The core issue is about ensuring the conversations we have are
+productive and inviting for all.
+
+Real-life events, however, require a bit more care. Reproducible Builds wants
+to be sure that any events it funds have policies and procedures in place for
+handling harassment. It's especially important to us that real-life events take
+steps to protect the physical and mental security of their participants.
+
+So the Reproducible Builds project will require that any events it funds or
+hosts have some sort of anti-harassment policy in place. The Reproducible
+Builds project thinks the
+[Ada Initiative's template](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy)
+is pretty good, but we're open to alternatives.
+
+## What happens if someone violates the Code of Conduct?
+
+Our intent is that anyone in the community can stand up for this code, and
+direct people who're unaware to this document. If that doesn't work, or if you
+need more help, you can contact `conduct at reproducible-builds.org`. For more
+details please see our [Reporting Guidelines]({{ "/conduct/report-guide/" | relative_url }})
+
+## Why do we need a Code of Conduct? Everyone knows not to be a jerk.
+
+Sadly, not everyone knows this.
+
+However, even if everyone was kind, everyone was compassionate, and everyone
+was familiar with codes of conduct it would still be incumbent upon our
+community to publish our own. Maintaining a code of conduct forces us to
+consider and articulate what kind of community we want to be, and serves as a
+constant reminder to put our best foot forward. But most importantly, it serves
+as a signpost to people looking to join our community that we feel these values
+are important.
+
+## This is censorship! I have the right to say whatever I want!
+
+You do — in *your* space. If you'd like to hang out in our spaces (as clarified
+above), we have some simple guidelines to follow. If you want to, for example,
+form a group where reproducible builds is discussed using language
+inappropriate for general channels then nobody's stopping you. We respect your
+right to establish whatever codes of conduct you want in the spaces that belong
+to you. Please honor this Code of Conduct in our spaces.
+
=====================================
_conduct/reporting-guide.md
=====================================
@@ -0,0 +1,127 @@
+---
+layout: conduct
+title: Reproducible Builds Code of Conduct - Reporting Guide
+short_title: Reporting Guide
+permalink: /conduct/reporting-guide/
+order: -1
+---
+
+# Reproducible Builds Code of Conduct - Reporting Guide
+
+If you believe someone is violating the code of conduct we ask that you report
+it to the Reproducible Builds project by emailing
+`conduct at reproducible-builds.org`. **All reports will be kept confidential**.
+In some cases we may determine that a public statement will need to be made. If
+that's the case, the identities of all victims and reporters will remain
+confidential unless those individuals instruct us otherwise.
+
+**If you believe anyone is in physical danger, please notify appropriate law
+enforcement first.** If you are unsure what law enforcement agency is
+appropriate, please include this in your report and we will attempt to notify
+them.
+
+If you are unsure whether the incident is a violation, or whether the space
+where it happened is covered by this Code of Conduct, we encourage you to still
+report it. We would much rather have a few extra reports where we decide to
+take no action, rather than miss a report of an actual violation. We do not
+look negatively on you if we find the incident is not a violation. And knowing
+about incidents that are not violations, or happen outside our spaces, can also
+help us to improve the Code of Conduct or the processes surrounding it.
+
+In your report please include:
+
+* Your contact info (so we can get in touch with you if we need to follow up)
+
+* Names (real, nicknames, or pseudonyms) of any individuals involved. If there
+ were other witnesses besides you, please try to include them as well.
+
+* When and where the incident occurred. Please be as specific as possible.
+
+* Your account of what occurred. If there is a publicly available record (e.g.
+ a mailing list archive or a public IRC logger) please include a link.
+
+* Any extra context you believe existed for the incident.
+
+* If you believe this incident is ongoing.
+
+* Any other information you believe we should have.
+
+## What happens after you file a report?
+
+You will receive an email from the Reproducible Builds Code of Conduct Working
+Group acknowledging receipt immediately. We promise to acknowledge receipt
+within 24 hours (and will aim for much quicker than that).
+
+The working group will immediately meet to review the incident and determine:
+
+* What happened.
+
+* Whether this event constitutes a code of conduct violation.
+
+* Who, if anyone, was the bad actor.
+
+* Whether this is an ongoing situation, or if there is a threat to anyone's
+ safety.
+
+If this is determined to be an ongoing incident or a threat to physical safety,
+the working group's immediate priority will be to protect everyone involved.
+This means we may delay an "official" response until we believe that the
+situation has ended and that everyone is physically safe.
+
+Once the working group has a complete account of the events they will make a
+decision as to how to respond. Responses may include:
+
+* Doing nothing (if we determine no violation occurred).
+
+* A private reprimand from the working group to the individual(s) involved.
+
+* A public reprimand.
+
+* An imposed vacation (i.e. asking someone to "take a week off" from a mailing
+ list or IRC).
+
+* A permanent or temporary ban from some or all Reproducible Builds spaces
+ (mailing lists, IRC, etc.)
+
+* A request for a public or private apology.
+
+We'll respond within one week to the person who filed the report with either a
+resolution or an explanation of why the situation is not yet resolved.
+
+Once we've determined our final action, depending on the situation we may
+contact the original reporter to let them know what action (if any) we'll be
+taking. We'll take into account feedback from the reporter on the
+appropriateness of our response, but we don't guarantee we'll act on it.
+
+Finally, the Working Group will make a report on the situation to the
+Reproducible Builds core team. The core team may choose to publish a public
+report of the incident.
+
+## What if your report concerns a possible violation by a committee member?
+
+If your report concerns a current member of the Code of Conduct committee, you
+may not feel comfortable sending your report to the committee, as all members
+will see the report.
+
+In that case, you can make a report directly to any or all of the current
+(vice/co) chairs of the Code of Conduct committee. Their e-mail addresses are
+listed on the [Code of Conduct Committee]({{ "/conduct/committee/"|relative_url }})
+page. The chairs will follow the usual enforcement process with the other
+members, but will exclude the member(s) that the report concerns from any
+discussion or decision making.
+
+If your report concerns all current (vice/co) chairs of the committee, please
+send your report directly to the Reproducible Builds core team at
+`contact at reproducible-builds.org`.
+
+You can also reach out to [Software Freedom Conservancy](https://sfconservancy.org/)
+(SFC) at `info at sfconservancy.org`, or singularly [to their board](https://sfconservancy.org/about/board/)
+or [staff members](https://sfconservancy.org/about/staff/).
+
+## Reconsideration
+
+Any of the parties directly involved or affected can request reconsideration of
+the committee's decision. To make such a request, contact the CoC Committee at
+`conduct at reproducible-builds.org` with your request and motivation and they will
+review the case.
+
=====================================
_config.yml
=====================================
@@ -11,7 +11,7 @@ description: |
baseurl: ""
url: https://reproducible-builds.org
-include: ['_docs']
+include: ['_conduct', '_docs']
sass:
sass_dir: /assets/styles
@@ -23,6 +23,8 @@ sass:
collections:
blog:
output: true
+ conduct:
+ output: true
docs:
output: true
events:
=====================================
_data/conduct.yml
=====================================
@@ -0,0 +1,5 @@
+pages:
+ - committee
+ - faq
+ - reporting-guide
+ - enforcement-manual
=====================================
_events/gothenburg2026/index.html
=====================================
@@ -199,8 +199,7 @@ Requests for travel support are now not accepted anymore, check <a href="travels
<h2>Code of Conduct</h2>
<p>
-There will be a specific Code of Conduct governing the event, which will be published before the event starts.
-<!-- This event will be run under the guidance of the <a href="{{ "/codeofconduct" |relative_url }}">Reproducible Builds Code of Conduct</a>.-->
+This event will be run under the guidance of the <a href="{{ "/conduct" |relative_url }}">Reproducible Builds Code of Conduct</a>.
</p>
<p>
The organisers are committed to providing events where all participants feel safe. Attendees are expected to treat all people with respect and help create a welcoming environment. If you notice behaviour that fails to meet this standard, please speak up (aloud or in private to the organisers).
=====================================
_includes/footer.html
=====================================
@@ -32,6 +32,8 @@
Patches for this website welcome <a href="https://salsa.debian.org/reproducible-builds/reproducible-website">via our Git repository</a>
(<a href="{{ "/contribute/salsa/" | relative_url }}">instructions</a>) or via <a href="https://lists.reproducible-builds.org/listinfo/rb-general">our mailing list</a>.
•
+ <a href="{{ "/conduct/" | relative_usrl }}">Code of Conduct</a>
+ •
<a href="{{ "/who/" | relative_url }}">Full contact info</a>
</span>
</div>
=====================================
_layouts/conduct.html
=====================================
@@ -0,0 +1,33 @@
+---
+layout: no_sidebar
+---
+
+<div class="row justify-content-end">
+ <div class="col-md-12 col-lg-6">
+
+ {{ content }}
+
+ </div>
+
+ <div class="col-xl-2 col-lg-3 offset-lg-1 d-none d-lg-block">
+ <h5><a href="{{ "/conduct/" | relative_url }}">Reproducible Builds Code of Conduct</a></h5>
+
+ <ul class="list-unstyled">
+
+ {% for item in site.data.conduct.pages %}
+ {% assign item_url = item | prepend: "/conduct/" | append:"/" %}
+ {% for p in site.conduct %}
+ {% if p.url == item_url %}
+ <li>
+ {% if page.url == item_url %}
+ <strong>{{ p.short_title }}</strong>
+ {% else %}
+ <a href="{{ p.url | relative_url }}">{{ p.short_title }}</a>
+ {% endif %}
+ </li>
+ {% endif %}
+ {% endfor %}
+ {% endfor %}
+ </ul>
+ </div>
+</div>
=====================================
contribute/index.md
=====================================
@@ -65,6 +65,12 @@ If you want to contribute but not in the form of coding for the different projec
Lastly, you can support us through monetary donations or by providing resources. We have an [extensive guide on our donate page]({{ "/donate/" | relative_url }}) on how both companies and individuals can contribute to our cause. Every contribution makes a difference! To see the impact of your support, check out our [news]({{ "/news/" | relative_url }}) section, where we publish a monthly report on our progress.
+## Code of Conduct
+
+To ensure the safety of the people that make our community, and maintain a welcoming environment, we have a [Code of Conduct]({{ "/conduct/" |relative_url }}) in place.
+
+We expect every Reproducible Builds contributor to adhere by it.
+
## Get in touch
Our preferred way of contact is to post to our public mailing list, rb-general. To do so, please join the [`rb-general` mailing-list](https://lists.reproducible-builds.org/listinfo/rb-general). However, there are other ways you can contact us:
=====================================
po/_pages.de.po
=====================================
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2026-09-13 17:13+0200\n"
+"POT-Creation-Date: 2026-09-13 17:14+0200\n"
"PO-Revision-Date: 2020-04-24 11:25+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -3399,6 +3399,22 @@ msgstr ""
msgid "Lastly, you can support us through monetary donations or by providing resources. We have an [extensive guide on our donate page]({{ \"/donate/\" | relative_url }}) on how both companies and individuals can contribute to our cause. Every contribution makes a difference! To see the impact of your support, check out our [news]({{ \"/news/\" | relative_url }}) section, where we publish a monthly report on our progress."
msgstr ""
+#. type: Title ##
+#: contribute/index.md
+#, no-wrap
+msgid "Code of Conduct"
+msgstr ""
+
+#. type: Plain text
+#: contribute/index.md
+msgid "To ensure the safety of the people that make our community, and maintain a welcoming environment, we have a [Code of Conduct]({{ \"/conduct/\" |relative_url }}) in place."
+msgstr ""
+
+#. type: Plain text
+#: contribute/index.md
+msgid "We expect every Reproducible Builds contributor to adhere by it."
+msgstr ""
+
#. type: Title ##
#: contribute/index.md
#, no-wrap
=====================================
po/_pages.pot
=====================================
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2026-09-13 17:13+0200\n"
+"POT-Creation-Date: 2026-09-13 17:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
@@ -3677,6 +3677,24 @@ msgstr ""
msgid "Lastly, you can support us through monetary donations or by providing resources. We have an [extensive guide on our donate page]({{ \"/donate/\" | relative_url }}) on how both companies and individuals can contribute to our cause. Every contribution makes a difference! To see the impact of your support, check out our [news]({{ \"/news/\" | relative_url }}) section, where we publish a monthly report on our progress."
msgstr ""
+#. type: Title ##
+#: contribute/index.md
+#, markdown-text, no-wrap
+msgid "Code of Conduct"
+msgstr ""
+
+#. type: Plain text
+#: contribute/index.md
+#, markdown-text
+msgid "To ensure the safety of the people that make our community, and maintain a welcoming environment, we have a [Code of Conduct]({{ \"/conduct/\" |relative_url }}) in place."
+msgstr ""
+
+#. type: Plain text
+#: contribute/index.md
+#, markdown-text
+msgid "We expect every Reproducible Builds contributor to adhere by it."
+msgstr ""
+
#. type: Title ##
#: contribute/index.md
#, markdown-text, no-wrap
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/3755f3ddcd2f3c409a23138693c0d81178abc610...ca36d61753130b26fcae5cff97f4db2674adc534
--
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/3755f3ddcd2f3c409a23138693c0d81178abc610...ca36d61753130b26fcae5cff97f4db2674adc534
You're receiving this email because of your account on salsa.debian.org. Manage all notifications: https://salsa.debian.org/-/profile/notifications | Help: https://salsa.debian.org/help
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.reproducible-builds.org/pipermail/rb-commits/attachments/20260916/50b70537/attachment.htm>
More information about the rb-commits
mailing list