Archived
15
23
Fork
You've already forked meta
6

Code of Conduct & Well being team & contact #13

Closed
opened 2022年11月06日 15:27:18 +01:00 by Ghost · 5 comments

A temporary well being team and moderation team was appointed 10 November 2022.

The moderation team will rely on this Code of Conduct when diplomacy fails https://www.contributor-covenant.org/version/2/1/code_of_conduct/

Well being team

Moderation team

  • create a repository dedicated to the well being & moderation
  • add links to existing spaces so people can conveniently get in touch with the teams and read the CoC
  • add content to the future website regarding the teams and the CoC
A temporary well being team and moderation team was appointed 10 November 2022. The moderation team will rely on this Code of Conduct when diplomacy fails https://www.contributor-covenant.org/version/2/1/code_of_conduct/ ### Well being team * https://codeberg.org/dachary * https://codeberg.org/Gusted ### Moderation team * https://codeberg.org/circlebuilder * https://codeberg.org/onepict --- - [x] create a repository dedicated to the well being & moderation - [x] add links to existing spaces so people can conveniently get in touch with the teams and read the CoC - [x] add content to the future website regarding the teams and the CoC
Ghost added this to the Launch milestone 2022年11月06日 15:27:18 +01:00

Once finalized, the code of conduct should be added to the website : codename/website#2

Once finalized, the code of conduct should be added to the website : https://codeberg.org/codename/website/issues/2

Call for votes based on the following.

Code of Conduct & well being & moderation

In all "codename" spaces (issue trackers, chat room, etc.) we make an effort to create an inclusive environment for everyone. For that purpose, a "well being" team is trusted with defusing tensions before they escalate. And if that happens, the moderation team will have the difficult task to enforce a Code of Conduct.

In this very early stage of the "codename" project, we will appoint volunteers to be replaced when a proper process is in place. And vote on a Code of Conduct for them to use, when diplomacy failed.

Please cast your vote below by adding the URL of your codeberg account in the (votes: )

Votes will be counted and a resolution made on 10 November.

Temporary staff for the well being and moderation teams

See below for the list of candidates.

  • YES: I agree the candidates to the well being and moderation teams are appointed (votes: https://codeberg.org/dachary/)
  • NO: I do not agree, I want other people (votes: )

Code of Conduct

Well being

Its goal is to defuse tensions.

It has no power whatsover. The members are approved by the organization and trusted to:

Governance / Moderation

Its goal is to enforce the CoC.

It has the power to exclude people from a space.

Its decisions must be logical, fact based and transparent to the organization trusting them with the task.

Discussions

People explicitly agree to apply a CoC to a space (loic)

A code of conduct is only meaningful in a given space if it was explicitly decided by the people ultimately responsible for managing the space. For instance a chatroom, a given repository in a given organization, a forum.

For instance if https://codeberg.org/codename/ is managed by people who agree on https://www.contributor-covenant.org/version/2/1/code_of_conduct/ they are expected to act on it if something happens anywhere in the repositories below this point, for instance https://codeberg.org/codename/.

The people who enter this space must be able to clearly figure out if there is a code of conduct and who to turn to in case they need to.

With that in mind a CoC should not be included in a code repository because it will, very likely:

  • conflict with the CoC that is in place in another space after the repository is forked
  • not be explicitly agreed to by the people who are responsible for the space in which the repository is forked

For instance if https://codeberg.org/codename/codename/ is forked into https://codeberg.org/otherorg/codename/ and

Social Coding Community Participation Guidelines

  • This document was adapted from Mozilla who use it across their entire organization. They have integrated insights from their Internet Health programs in it regarding Inclusion and Diversity.
  • Social Coding's variant will be positioned to be applicabe to any project that considers itself a Social Coding practitioner. I.e. dedicates to its Principles and adopting Free Software Developer Lifecycle (FSDL) best-practices from the pattern library as it grows.
  • The guidelines will be published at conduct.coding.social
  • There's a discussion topic on Discuss Social Coding for feedback & questions.
  • Note: Social Coding Movement will be member of The Forgers Guild just like Codename may be.
Call for votes based on the following. --- Code of Conduct & well being & moderation === In all "codename" spaces (issue trackers, chat room, etc.) we make an effort to create an inclusive environment for everyone. For that purpose, a "well being" team is trusted with defusing tensions before they escalate. And if that happens, the moderation team will have the difficult task to enforce a Code of Conduct. In this very early stage of the "codename" project, we will appoint volunteers to be replaced when a proper process is in place. And vote on a Code of Conduct for them to use, when diplomacy failed. Please cast your vote below by adding the URL of your codeberg account in the (votes: ) Votes will be counted and a resolution made on 10 November. ### Temporary staff for the well being and moderation teams See below for the list of candidates. - YES: I agree the candidates to the well being and moderation teams are appointed (**votes:** https://codeberg.org/dachary/) - NO: I do **not** agree, I want other people (**votes:** ) ### Code of Conduct - 1 - https://www.contributor-covenant.org/version/2/1/code_of_conduct/ (**votes:** ) - 2 - https://codeberg.org/SocialCoding/community/src/branch/main/CODE_OF_CONDUCT.md (**votes:** https://codeberg.org/dachary/) - 3 - https://www.gnu.org/philosophy/kind-communication.html (**votes:** ) - 4 - Take inspiration from the [Core Nonviolence Commitments](https://thefearlessheart.org/resources/core-commitments/) (**votes:** ) ## Well being Its goal is to defuse tensions. It has no power whatsover. The members are approved by the organization and trusted to: - read all communications to detect tensions between people before they escalate - do their best to defuse the tension - Candidate for the team - https://codeberg.org/dachary - https://codeberg.org/Gusted ## Governance / Moderation Its goal is to enforce the CoC. It has the power to exclude people from a space. Its decisions must be logical, fact based and transparent to the organization trusting them with the task. - Candidate for the team - https://codeberg.org/circlebuilder - https://codeberg.org/onepict ### Discussions #### People explicitly agree to apply a CoC to a space (loic) A code of conduct is **only** meaningful in a given space if it was explicitly decided by the people ultimately responsible for managing the space. For instance a chatroom, a given repository in a given organization, a forum. For instance if https://codeberg.org/codename/ is managed by people who agree on https://www.contributor-covenant.org/version/2/1/code_of_conduct/ they are expected to act on it if something happens anywhere in the repositories below this point, for instance https://codeberg.org/codename/. The people who enter this space must be able to clearly figure out if there is a code of conduct and who to turn to in case they need to. With that in mind a CoC should not be included in a code repository because it will, very likely: - conflict with the CoC that is in place in another space after the repository is forked - not be explicitly agreed to by the people who are responsible for the space in which the repository is forked For instance if https://codeberg.org/codename/codename/ is forked into https://codeberg.org/otherorg/codename/ and - https://codeberg.org/otherorg has a different CoC, for instance https://codeberg.org/SocialCoding/community/src/branch/main/CODE_OF_CONDUCT.md, there is a conflict. - https://codeberg.org/otherorg has no CoC because the people who forked the repository do not care for CoC, a visitor will be mislead into thinking that a CoC is expected to be enforced although it won't #### Social Coding Community Participation Guidelines - This document was adapted from Mozilla who use it across their entire organization. They have integrated insights from their Internet Health programs in it regarding Inclusion and Diversity. - Social Coding's variant will be positioned to be applicabe to any project that considers itself a Social Coding _practitioner_. I.e. dedicates to its [Principles](https://coding.social/principles) and adopting Free Software Developer Lifecycle (FSDL) best-practices from the pattern library as it grows. - The guidelines will be published at `conduct.coding.social` - There's a [discussion topic](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138) on Discuss Social Coding for feedback & questions. - Note: [Social Coding Movement](https://coding.social) will be member of [The Forgers Guild](https://forg.es) just like Codename may be.
YES: I agree the candidates to the well being and moderation teams are appointed (votes: https://codeberg.org/onepict/)
Code of Conduct
 2 - https://codeberg.org/SocialCoding/community/src/branch/main/CODE_OF_CONDUCT.md (votes: https://codeberg.org/onepict/)
YES: I agree the candidates to the well being and moderation teams are appointed (votes: https://codeberg.org/onepict/) Code of Conduct 2 - https://codeberg.org/SocialCoding/community/src/branch/main/CODE_OF_CONDUCT.md (votes: https://codeberg.org/onepict/)

The votes are now closed and archived here for the record.

Code of Conduct & well being & moderation

In all "codename" spaces (issue trackers, chat room, etc.) we make an effort to create an inclusive environment for everyone. For that purpose, a "well being" team is trusted with defusing tensions before they escalate. And if that happens, the moderation team will have the difficult task to enforce a Code of Conduct.

In this very early stage of the "codename" project, we will appoint volunteers to be replaced when a proper process is in place. And vote on a Code of Conduct for them to use, when diplomacy failed.

Please cast your vote below by adding the URL of your codeberg account in the (votes: )

Votes will be counted and a resolution made on 10 November.

Temporary staff for the well being and moderation teams

See below for the list of candidates.

Code of Conduct

Well being

Its goal is to defuse tensions.

It has no power whatsover. The members are approved by the organization and trusted to:

Governance / Moderation

Its goal is to enforce the CoC.

It has the power to exclude people from a space.

Its decisions must be logical, fact based and transparent to the organization trusting them with the task.

Discussions

People explicitly agree to apply a CoC to a space (loic)

A code of conduct is only meaningful in a given space if it was explicitly decided by the people ultimately responsible for managing the space. For instance a chatroom, a given repository in a given organization, a forum.

For instance if https://codeberg.org/codename/ is managed by people who agree on https://www.contributor-covenant.org/version/2/1/code_of_conduct/ they are expected to act on it if something happens anywhere in the repositories below this point, for instance https://codeberg.org/codename/.

The people who enter this space must be able to clearly figure out if there is a code of conduct and who to turn to in case they need to.

With that in mind a CoC should not be included in a code repository because it will, very likely:

  • conflict with the CoC that is in place in another space after the repository is forked
  • not be explicitly agreed to by the people who are responsible for the space in which the repository is forked

For instance if https://codeberg.org/codename/codename/ is forked into https://codeberg.org/otherorg/codename/ and

Social Coding Community Participation Guidelines

  • This document was adapted from Mozilla who use it across their entire organization. They have integrated insights from their Internet Health programs in it regarding Inclusion and Diversity.
  • Social Coding's variant will be positioned to be applicabe to any project that considers itself a Social Coding practitioner. I.e. dedicates to its Principles and adopting Free Software Developer Lifecycle (FSDL) best-practices from the pattern library as it grows.
  • The guidelines will be published at conduct.coding.social
  • There's a discussion topic on Discuss Social Coding for feedback & questions.
  • Note: Social Coding Movement will be member of The Forgers Guild just like Codename may be.
The votes are now closed and archived here for the record. --- Code of Conduct & well being & moderation === In all "codename" spaces (issue trackers, chat room, etc.) we make an effort to create an inclusive environment for everyone. For that purpose, a "well being" team is trusted with defusing tensions before they escalate. And if that happens, the moderation team will have the difficult task to enforce a Code of Conduct. In this very early stage of the "codename" project, we will appoint volunteers to be replaced when a proper process is in place. And vote on a Code of Conduct for them to use, when diplomacy failed. Please cast your vote below by adding the URL of your codeberg account in the (votes: ) Votes will be counted and a resolution made on 10 November. ### Temporary staff for the well being and moderation teams See below for the list of candidates. - YES: I agree the candidates to the well being and moderation teams are appointed (**votes:** https://codeberg.org/dachary/, https://codeberg.org/gusted, https://codeberg.org/onepict, https://codeberg.org/caesar, https://codeberg.org/oliverpool https://codeberg.org/fnetx https://codeberg.org/tallship) - NO: I do **not** agree, I want other people (**votes:** ) ### Code of Conduct - 1 - https://www.contributor-covenant.org/version/2/1/code_of_conduct/ (**votes:** https://codeberg.org/caesar https://codeberg.org/hugopeixoto/ https://codeberg.org/dachary/) - 2 - https://codeberg.org/SocialCoding/community/src/branch/main/CODE_OF_CONDUCT.md (**votes:** https://codeberg.org/onepict, https://codeberg.org/circlebuilder) - 3 - https://www.gnu.org/philosophy/kind-communication.html (**votes:** https://codeberg.org/Gusted https://codeberg.org/tallship) - 4 - Take inspiration from the [Core Nonviolence Commitments](https://thefearlessheart.org/resources/core-commitments/) (**votes:** ) - I am fine with any of the aforementioned option (**votes:** https://codeberg.org/oliverpool) ## Well being Its goal is to defuse tensions. It has no power whatsover. The members are approved by the organization and trusted to: - Read all communications to detect tensions between people before they escalate. - do their best to defuse the tension/. - Candidate for the team - https://codeberg.org/dachary - https://codeberg.org/Gusted ## Governance / Moderation Its goal is to enforce the CoC. It has the power to exclude people from a space. Its decisions must be logical, fact based and transparent to the organization trusting them with the task. - Candidate for the team - https://codeberg.org/circlebuilder - https://codeberg.org/onepict ### Discussions #### People explicitly agree to apply a CoC to a space (loic) A code of conduct is **only** meaningful in a given space if it was explicitly decided by the people ultimately responsible for managing the space. For instance a chatroom, a given repository in a given organization, a forum. For instance if https://codeberg.org/codename/ is managed by people who agree on https://www.contributor-covenant.org/version/2/1/code_of_conduct/ they are expected to act on it if something happens anywhere in the repositories below this point, for instance https://codeberg.org/codename/. The people who enter this space must be able to clearly figure out if there is a code of conduct and who to turn to in case they need to. With that in mind a CoC should not be included in a code repository because it will, very likely: - conflict with the CoC that is in place in another space after the repository is forked - not be explicitly agreed to by the people who are responsible for the space in which the repository is forked For instance if https://codeberg.org/codename/codename/ is forked into https://codeberg.org/otherorg/codename/ and - https://codeberg.org/otherorg has a different CoC, for instance https://codeberg.org/SocialCoding/community/src/branch/main/CODE_OF_CONDUCT.md, there is a conflict. - https://codeberg.org/otherorg has no CoC because the people who forked the repository do not care for CoC, a visitor will be mislead into thinking that a CoC is expected to be enforced although it won't #### Social Coding Community Participation Guidelines - This document was adapted from Mozilla who use it across their entire organization. They have integrated insights from their Internet Health programs in it regarding Inclusion and Diversity. - Social Coding's variant will be positioned to be applicabe to any project that considers itself a Social Coding _practitioner_. I.e. dedicates to its [Principles](https://coding.social/principles) and adopting Free Software Developer Lifecycle (FSDL) best-practices from the pattern library as it grows. - The guidelines will be published at `conduct.coding.social` - There's a [discussion topic](https://discuss.coding.social/t/discuss-our-community-participation-guidelines/138) on Discuss Social Coding for feedback & questions. - Note: [Social Coding Movement](https://coding.social) will be member of [The Forgers Guild](https://forg.es) just like Codename may be.

The issue description was updated to reflect the vote results. The teams are temporarily appointed by an unanimous vote. The https://www.contributor-covenant.org/version/2/1/code_of_conduct/ code of conduct has most votes (3 votes).

This is temporary and will be submitted to a proper discussion and vote after the governance is established.

The [issue description was updated](https://codeberg.org/codename/meta/issues/13#issue-198983) to reflect the vote results. The teams are temporarily appointed by an unanimous vote. The https://www.contributor-covenant.org/version/2/1/code_of_conduct/ code of conduct has most votes (3 votes). This is temporary and will be submitted to a proper discussion and vote after [the governance is established](https://codeberg.org/codename/meta/issues/19).
Commenting is not possible because the repository is archived.
No Branch/Tag specified
readme
No results found.
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
Accessibility
Relates to Accessibility (a11y) of product, project and process.
Agreement proposal
Forgejo agreement proposal, following a discussion
Communication
Relates to all channels, social media, website, blog posts.
Election
Process of appointing a person into a role or team (if choosing people just for a specific one-time task, use the Entrustment label)
Entrustment
Process of choosing/approving specific people to do a critical/high-impact one-time task (if choosing people for an ongoing role/team, use the Election label)
Governance
Relates to processes, procedures and decision-making.
Meeting
An upcoming team meeting
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/meta#13
Reference in a new issue
forgejo/meta
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?