# Discuss our Community Participation Guidelines **URL:** \ **Category:** Outreach square 🫂\ **Created:** [September 23, 2022, 6:21am UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138 "2022-09-23T06:21:24Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [September 23, 2022, 6:21am UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/1 "2022-09-23T06:21:24Z")
This is the companion discussion topic to our [Social Coding Community Participation Guidelines](https://discuss.coding.social/t/social-coding-community-participation-guidelines-wiki-post/137) wiki post. When these guidelines have been created in any location where they are used (e.g. in a `CODE-OF-CONDUCT.md` in a code repository) it is sufficient to refer to them in a similar way Mozilla does: > # Community Participation Guidelines > > This repository is governed by Mozilla’s code of conduct and etiquette guidelines. > For more details, please read the > [Mozilla Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/). > > ## How to Report > > For more information on how to report violations of the Community Participation Guidelines, please read our ‘[How to Report](https://www.mozilla.org/about/governance/policies/participation/reporting/)’ page. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [September 23, 2022, 11:02am UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/2 "2022-09-23T11:02:01Z")
I have updated the wiki post so that the guidelines relate to Social Coding Movement. I am very happy with the contents of the document. The Mozilla CoC lends itself very well for a Movement like ours, in their breadth and scope and the thoughtful formulations it uses. I have added the guidelines to a community repository on Codeberg, from where it can be referenced from other locations, in similar way as shown above. > **[socialcoding-practice](https://codeberg.org/socialcoding/socialcoding-practice)** > > Social coding practical guidance and guidelines. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [October 15, 2022, 7:31am UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/3 "2022-10-15T07:31:53Z")
I just found this [post](https://sunbeam.city/@mayel/108472355626370222) by @mayel containing reference to a paper [Designing Care and Commoning into a Code of Conduct](https://dl.designresearchsociety.org/cgi/viewcontent.cgi?article=1537&context=nordes) (PDF) by Cindy Kohtala of the Aalto University, Finland. It may have some nice further insights to improve our participation guidelines. > Despite claims to being counterculture and a better alternative, grassroots activist design groups and free culture movements may replicate the marginalizing behaviours of dominant society, also in their governance and designs of their interaction platforms. We developed a code-of-conduct, or Community Guidelines, for our online commons- oriented group to nurture a sense of a caring and mutually responsible community. The guidelines aim to bring into online interaction the living person-to-person dialogic relationality we exhibit in collaborative work offline. Our social learning process could have implications for designing healthier online community protocols and platforms and be able to better tackle the challenges of intersectionality. (Also [cross-referencing to Architecture of Participation](https://discuss.coding.social/t/workflow-for-social-coding-movement/78/3)) ---
**Author:** ![mayel](https://discuss.coding.social/letter_avatar_proxy/v4/letter/m/65b543/32.png) [@mayel](https://discuss.coding.social/u/mayel)\ **Post date:** [October 15, 2022, 8:07am UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/4 "2022-10-15T08:07:52Z")
Our code of conduct is largely inspired by that paper and adapted from the guidelines they wrote: [Bonfire](https://bonfirenetworks.org/conduct/) ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [January 2, 2023, 8:20pm UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/5 "2023-01-02T20:20:45Z")
## CoC Enforcement There’s still a couple of small things to do on the Social Coding Community Participation Guidelines, like hosting at [conduct.coding.social](http://conduct.coding.social) But the guidelines describing the actual Code of Conduct is only part of the Well-being process of a community or project. Actually enforcing the CoC in an inclusive, fair, and transparent manner is most important. And the way that is done needs to be well thought out and documented. There’s a free e-book on the subject written by Valerie Aurora and Marie Gardiner: > ### [How to respond to Code of Conduct Reports](https://frameshiftconsulting.com/resources/code-of-conduct-book/#book) > > - What to include in a code of conduct (and what to leave out) > - How to prepare to enforce a code of conduct > - Step-by-step instructions on how to respond to a report > - In-depth discussion of relevant topics > - Dozens of real-world examples of responding to reports * * * **Update** : [Forgejo project](https://forgejo.org) is figuring out Moderation procedures: [#138 - Channel moderation approaches - forgejo/meta - Codeberg.org](https://codeberg.org/forgejo/meta/issues/138) and best-practices can be formulated in conjunction to that. Also there’s a great guide on how to deal with Trolls (and not become one yourself while doing so). There’s 2 versions: - Long, but abandoned: [Avoiding Trolls (Long)](https://github.com/prettydiff/wisdom/blob/56cf98c2b7bbccc402164a3d6d06b08579c7216d/Avoiding_Trolls.md) - Current version, too brief: [Avoiding Trolls](https://github.com/prettydiff/wisdom/blob/troll/Avoiding_Trolls.md) ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [April 22, 2024, 10:54am UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/6 "2024-04-22T10:54:59Z")
### Input for further improvements .. In follow-up to mention of these guidelines (as published in [participate.coding.social](http://participate.coding.social)) on the Fediverse [@msavoritias posted](https://tilde.zone/@msavoritias/112314158652662374) a follow-up on providing examples of a good CoC (in my mind) and also good rules for community governance. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [November 26, 2024, 12:11pm UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/7 "2024-11-26T12:11:06Z")
## Enhancement: Grassroots SOS peer production principles The text at [https://participate.coding.social](https://participate.coding.social) is no longer accurate and must be updated: - Social coding is an “umbrelly movement” and not a “community”. - Convey the difference clearly, explain the philosophy of movement in context of social coding. - Replace references to “community” with proper “hedonic peer production”-related terms. - Explain the public umbrella services that are on offer (forum space, other channels). - Explain the themes and scope of social coding movement and expected mindset. - Mutual expectations aren’t properly managed yet, unbalanced, leading to confusion. - Explain the concept of Sustainable open software and relationship to FOSS - Note: Should split up into separate task to add terms to the Glossary (smallcircle project artifact) > **TODO** : Improve the texts collectively and update channels to latest version of the guidelines. ---
**Author:** ![wojciechxtx](https://discuss.coding.social/user_avatar/discuss.coding.social/wojciechxtx/32/681_2.png) [@wojciechxtx](https://discuss.coding.social/u/wojciechxtx)\ **Post date:** [December 18, 2024, 10:26pm UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/8 "2024-12-18T22:26:50Z")
> [#138 - Channel moderation approaches - meta - Codeberg.org](https://codeberg.org/forgejo/meta/issues/138) @aschrijver discussion there had not been updated in almost 2 years. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [January 19, 2025, 4:09am UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/9 "2025-01-19T04:09:58Z")
@erlend in the Muni Town general chatroom mentioned the following resource as a good basis for a Code of Conduct, and it may hold interesting information to improve the Participation Guidelines artifact as well and/or for further well-being procedures to be based on that. > **[How we'll do discussions here](https://www.wrecka.ge/how-we-do-it-here/)** > > Discussions on wreckage/salvage will take place in a semi-sheltered space to encourage generative and generous conversations. Note that the Social Coding Participation Guidelines are a reusable, independent and crowdsourced artifact, that is not tied to Social coding movement, but can be adopted by anyone, by referring to the guidelines in a `CODE_OF_CONDUCT.md` and in project communication channels. > **[Social Coding Community Participation Guidelines](https://participate.coding.social)** > > We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [February 4, 2025, 8:34am UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/10 "2025-02-04T08:34:03Z")
# Policy Cards [![image](https://discuss.coding.social/uploads/default/original/1X/741402411ceed7f55ae5111d3f5e9ebf213fa9fe.jpeg)](https://web.archive.org/web/20210318045401/https://www.privacylabel.org/learn/) _[Tijmen Schep](https://www.tijmenschep.com/privacy-label/) launched the site [privacylabel.org](http://privacylabel.org) (cert-expired, see [archive.org](https://web.archive.org/web/20210318045401/https://www.privacylabel.org/learn/))._ _Idea: Policy cards + pledge framework e.g. [responsibletech.work](http://responsibletech.work) to make Participation a living concept._ This was discussed on the Social experience design chatroom in relationship to: - **Pledgewashing** : _Pledges and manifesto’s not backed by compliance policies become mere PR pamphlets._ Because pledges today aren’t very useful. The Opportunity is to make pledges more valuable: monitorable and reinforcable. And potentially fully intrinsic to our open social stack over time. I know the folks behind [Responsible Tech Work](https://responsibletech.work/) and expect them to join social coding in due time. Here you have an example of a budding pledge framework. Alja, one of the co-creators of this initiative is also involved in [Tethix](https://tethix.co/) as co-founder together with Mat. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [April 20, 2025, 2:57pm UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/11 "2025-04-20T14:57:08Z")
@silverpill in the FEP issue tracker on codeberg, made the following comments wrt adopting of the participation guidelines: > The text is quite long and covers offline activities too, but parts that might apply to FEP repository are similar to what already exists in Codeberg Terms Of Service, [§ 2 Allowed Content & Usage](https://codeberg.org/Codeberg/org/src/branch/main/TermsOfUse.md#2-allowed-content-usage): > > ```auto > You must not share any content that's expressing hate or encouraging violence towards a person or group for any reason. We also explicitly do not tolerate: > > Discriminatory behaviour towards and promoting oppression, especially of marginalized groups on grounds of ethnicity, gender, disability, nationality, education, age, and religion. > Violent nationalist propaganda, Nazi symbolism or promoting the ideology of National Socialism. > Mobbing, stalking, doxxing (exposing someone's personal information), brigading (inciting a group to spam a specific place for any reason), threatening and harassment, as well as encouraging others to do those things. > Insults, discriminatory jokes, sexualized comments and other unwanted sexual attention. > Sexually obscene content, including content involving the exploitation or sexualization of minors. > Content that's glorifying violence; that includes any violent material without a proper content warning. > Content that harms the reputation of Codeberg. > > ``` > > All discussions that happen here are subject to those rules. They are more concise than Social Coding Guidelines, and easier to understand, so I think we don’t need to adopt Social Coding Guidelines, unless there is an evidence of a disruptive behavior that is not covered by Codeberg ToS but covered by Social Coding Guidelines. See for more information: > **[You must not share any content that's expressing hate or encouraging violence......](https://codeberg.org/fediverse/fep/issues/252#issuecomment-3863769)** > > The Code of Conduct of the FEP is currently implicit (I guess that means right now - being facilitated by SocialHub - the SocialHub Policy applies). As mentioned by @hrefna and my reply may tick many boxes to back up process governance, if tailored... ---
**Author:** ![d3v0](https://discuss.coding.social/user_avatar/discuss.coding.social/d3v0/32/936_2.png) [@d3v0](https://discuss.coding.social/u/d3v0)\ **Post date:** [May 2, 2025, 1:13pm UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/12 "2025-05-02T13:13:56Z")
There may be adaptations that are concise and easier to understand, such as this concept of an interactive guide: > **[Penpot | Full-stack design](https://design.penpot.app/#/view/02968425-bc48-80f1-8005-ae20bfa7c8a0?page-id=02968425-bc48-80f1-8005-ae20bfa7c8a1§ion=interactions&index=0&share-id=37d6e7bf-72f9-806c-8005-b0ac8f2cf749)** > > Penpot is the open-source design platform for teams that build digital products at scale. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [May 2, 2025, 2:45pm UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/13 "2025-05-02T14:45:28Z")
Yes, indeed. I also like the ‘nutrition label’ idea of policy cards above, and in light of the [coding.social](http://coding.social) site redesign [this simple layout](https://whynoipv6.com/faq) is fitting to split the larger chunks of text into separate ‘tabs’. Btw, part of the redesign/repositioning the new name should be ‘commons participation guidelines’, and this forum will have a ‘commons participation’ dedicated subcategory to discuss improvements. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [May 2, 2025, 4:02pm UTC](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138/14 "2025-05-02T16:02:10Z")
> [@aschrijver](#): > > this forum will have a ‘commons participation’ dedicated subcategory to discuss improvements. In fact.. we’re in it now: #fellowships:commons-participation