Archived
15
23
Fork
You've already forked meta
6

[AGREEMENT] dachary application to the Well-Being team #152

Closed
opened 2023年02月04日 09:01:04 +01:00 by Ghost · 2 comments

Application

I propose to be accountable for the Forgejo Well-Being and become part of the the Well-Being team.

  1. If you agree, please simply add a 👍 to this issue.
  2. If you disagree or have reservations, please write them down here, in a comment.

This application follows the Forgejo decision making process. It is still new: do not hesitate to voice any concern you may have.

Pledge

I will proactively read all messages in all Forgejo spaces and react as soon as possible to defuse tension.

I acknowledge that I have no authority to redact messages or exclude people.

Background

I have been involved in the Well-Being team since the inception of Forgejo. There has been a few cases where tension began to show and I did my best to help defuse the tension.

I have been able to read all messages in all Forgejo spaces.

On one occasion I observed a behavior that went against the code of conduct and deferred to the moderation team.

In 2020 I began an experimentation of a similar Well-Being team in the context of the CHATONS collective. The experiment was successful (see the conclusion report) and became a permanent team, with a rolling team of applications (see the 2023 application for an example)).

### Application I propose to be accountable for the Forgejo Well-Being and become part of the [the Well-Being team](https://codeberg.org/forgejo/meta/src/branch/readme/TEAMS.md#well-being). 1. If you agree, please simply add a 👍 to this issue. 2. If you disagree or have reservations, please write them down here, in a comment. This application follows the Forgejo [decision making process](https://codeberg.org/forgejo/meta/src/branch/readme/DECISION-MAKING.md). It is still new: do not hesitate to voice any concern you may have. ### Pledge I will proactively read all messages in all Forgejo spaces and react as soon as possible to defuse tension. I acknowledge that I have no authority to redact messages or exclude people. ### Background I have been involved in the Well-Being team since the inception of Forgejo. There has been a few cases where tension began to show and I did my best to help defuse the tension. I have been able to read all messages in all Forgejo spaces. On one occasion I observed a behavior that went against the code of conduct and deferred to the moderation team. In 2020 I began an [experimentation of a similar Well-Being team](https://forum.chatons.org/t/proposition-dexperimentation-une-equipe-de-mediation/1571) in the context of the [CHATONS](https://chatons.org) collective. The experiment was successful (see the [conclusion report](https://forum.chatons.org/t/bilan-et-dissolution-de-lequipe-de-mediation-experimentale/2228)) and became a permanent team, with a rolling team of applications (see the [2023 application](https://forum.chatons.org/t/2023-candidature-pour-rejoindre-l-equipe-de-mediation-vincent-peugnet/4538) for an example)).
Contributor
Copy link

I regret of my afirmation made yesterday with respect to Löic ability to be a good integrant of the Well-Being team.

My reasons:

  1. There was an incident not well managed by both the Well-being team and the Moderation team. This is a fact.

  2. I expected consecuences about that fact furthermore a couple of days of silence. After that expectation my direct interpretation about the action of dissolve the W-B team was as a measure oriented to repair the fault. Until here, there is no other actions proposed to improve the procedure applied in the questioned event more than invite to talk, which is good, but not enough. There are improvements to the platform which are urgent to do. There are changes in the procedure and delimitation of roles, because, as @tallship remembered, in the mentioned incident the roles was interchanged between teams.

  3. If the reasons for dissolve the W-B team are not the above stated, then my concern addressed in the issue of dissolution about the legitimacy of the team, at least should be addressed following our recent Decision making agreement which states: When people are against a proposal, try to guess and look for what's important to them, which need/concern/value they're defending. Löic defends his point applying the status quo order and addressing my concern as off-topic; The team exists and there is a promise to the community in order to a dissolution, with higher priority than the dissolution of the Contribution team, with higher priority than to do a good delimitation of teams.

  4. So, Loïc doesn't whilling to pospone the dissolution of the Well-Being team, call by itself the dissolution of the team as a member of the Well-Being team, addressed a legitim concern about legitimacy of the team in question as off-topic and defends his position against other member of the community calling them a blocker.

  5. The first, if not the only one, rule of mediation is that one must never can be part in dispute of the mediated situation.

I regret of my [afirmation made yesterday with respect to Löic ability to be a good integrant of the Well-Being team](https://codeberg.org/forgejo/meta/issues/146#issuecomment-791447). My reasons: 1) There was an incident not well managed by both the Well-being team and the Moderation team. This is a fact. 2) I expected consecuences about that fact furthermore a couple of days of silence. After that expectation my direct interpretation about the action of dissolve the W-B team was as a measure oriented to repair the fault. Until here, there is no other actions proposed to improve the procedure applied in the questioned event more than invite to talk, which is good, but not enough. There are improvements to the platform which are urgent to do. There are changes in the procedure and delimitation of roles, because, as @tallship [remembered](https://codeberg.org/forgejo/meta/issues/146#issuecomment-790828), in the mentioned incident the roles was interchanged between teams. 3) If the reasons for dissolve the W-B team are not the above stated, then my concern addressed in the issue of dissolution about the legitimacy of the team, at least should be addressed following [our recent Decision making agreement](https://codeberg.org/forgejo/meta/src/branch/readme/DECISION-MAKING.md) which states: *When people are against a proposal, try to guess and look for what's important to them, which need/concern/value they're defending*. Löic defends his point applying the status quo order and addressing my concern as off-topic; The team exists and there is a promise to the community in order to a dissolution, with higher priority than the dissolution of the Contribution team, with higher priority than to do a good delimitation of teams. 4) So, Loïc doesn't whilling to pospone the dissolution of the Well-Being team, call by itself the dissolution of the team as a member of the Well-Being team, addressed a legitim concern about legitimacy of the team in question as off-topic and defends his position against other member of the community calling them a blocker. 5) The first, if not the only one, rule of **mediation** is that one must never can be part in dispute of the mediated situation.

I withdraw my application as a member of the Well-Being team. It can only work if there is a consensus and since you object @fsologureng, I respect your point of view.

I withdraw my application as a member of the Well-Being team. It can only work if there is a consensus and since you object @fsologureng, I respect your point of view.
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
2 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#152
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?