Commit graph

70 commits

Author SHA1 Message Date
oliverpool 9810d8469a Add crystal to the github owners (#199)
For https://next.forgejo.org github-login-flow.

Reviewed-on: https://codeberg.org/forgejo/meta/pulls/199
2023-03-23 10:14:04 +00:00
fr33domlover 7b1c171c47
Mention sustainability repo in README.md 2023-03-18 11:23:30 +02:00
Felipe Leopoldo Sologuren Gutiérrez 690e7bb5e6 [Governance][Agreement] Add Accessibility as Forgejo value (#179)
The Forgejo initiative has publicly declared interest in develops a software forge with accessibility concerns, among other features.

Under this premise I propose to add Accessibility as a core value of the initiative:

*All Forgejo developments will be made considering the ability
   to access of people with disabilities or functional impairment as a condition of
   equality of opportunities and inclusion, understanding Accessibility as the
   quality of being able to access with assistive technology.*

Please feel free to comment, improve, suggest, object or approve this proposal taking into account your own concerns or level of agreement.

Co-authored-by: fsologureng <sologuren@estudiohum.cl>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/179
Co-authored-by: Felipe Leopoldo Sologuren Gutiérrez <fsologureng@noreply.codeberg.org>
Co-committed-by: Felipe Leopoldo Sologuren Gutiérrez <fsologureng@noreply.codeberg.org>
2023-03-15 17:03:21 +00:00
Earl Warren cc15844ad5
ban from 10-03-2023 to 03-2024
Closes: https://codeberg.org/forgejo/meta/issues/194
Closes: https://codeberg.org/forgejo-contrib/governance/issues/8
2023-03-10 14:27:25 +01:00
André Jaenisch 4ac91a9998 Propose new member on accessibility team (#193)
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/193
2023-03-10 10:08:12 +00:00
André Jaenisch d2b40d8b8d Propose new member on accessibility team
https://codeberg.org/forgejo/meta/issues/181 received six upvotes, so I want to move along.

Closes #181

Signed-off-by: André Jaenisch <ryuno-ki@noreply.codeberg.org>
2023-03-07 13:08:14 +00:00
Arnold Schrijver 593a6fc97d Circlebuilder steps out of chatroom moderation (#189)
I requested an admin to demote me from Forgejo Development, as mods can't do that themself.

Co-authored-by: Arnold Schrijver <circlebuilder-codeberg@engagingspaces.io>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/189
Co-authored-by: Arnold Schrijver <circlebuilder@noreply.codeberg.org>
Co-committed-by: Arnold Schrijver <circlebuilder@noreply.codeberg.org>
2023-03-02 15:08:28 +00:00
fr33domlover 05dc4604c9 Document decision-making process (#148)
So far, the decision-making guide is a brief very simplified one.

This PR:

- Improves the simplified guide
- Adds a full detailed version of the decision-making process, to help everyone make non-trivial decisions together, and so that even if I disappear, the project has the tools to continue, learn, evolve, flourish
- Tweaks the table in AGREEMENTS.md based on earlier feedback

Clarification: This PR isn't making a new agreement/decision, it's mostly just expanding the decision-making guide, and we can continue to try the guide in Forgejo and see how it goes and improve it as needed. Or even throw it away entirely if it really doesn't work.

It's not a command forcing you to make decisions in a certain way. It's a helpful resources giving you a way to make decisions together. If you know what you're doing and you don't need a guide, that's fine.

# The Request

If you have **limited time to read** the guide:

Can you **skim** through it and see if there's anything that stands out, that **bothers/concerns** you or that you disagree with? And comment if yes. Otherwise, do you trust me and **willing that we try the guide in Forgejo** (despite not thoroughly reading it) and see how it goes, and let it improve via ongoing feedback, and make an official community approval at a later time? (Worst case, if it turns out to be garbage, we can delete it)

If you **don't have time to read** the guide:

Do you trust me and **willing that we try the guide in Forgejo** (despite not reading the very long detailed sections that this PR adds) and see how it goes, and let it improve via ongoing feedback, and make an official community approval at a later time? (Worst case, if it turns out to be garbage, we can delete it)

If you **have time to thoroughly read** the guide:

Can you go through it and review / give feedback? Including *questions* if there's anything there that's unclear or confusing.

If you don't have enough trust in me to answer yes to the questions above, that's fine and please don't hesitate to say so <3 I know it's hard to trust a stranger landing some huge document out of nowhere. We'll figure out a pathway to togetherness. Even if it means simply closing this PR without merging anything.

Co-authored-by: fr33domlover <fr33domlover@riseup.net>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/148
2023-03-02 15:04:53 +00:00
Felipe Leopoldo Sologuren Gutiérrez ec3142d692 [Governance][Agreement] Add Privacy as Forgejo value (#178)
The Forgejo initiative has publicly declared that it develops a software forge with a focus on privacy, among other features.

Under this premise I propose to add Privacy as a core value of the initiative:

*All Forgejo developments will be made considering data protection by default and by design for all its users, understanding Privacy as a condition of human autonomy and self-governance*.

Please feel free to comment, improve, suggest, object or approve this proposal taking into account your own concerns or level of agreement.

Co-authored-by: fsologureng <sologuren@estudiohum.cl>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/178
Co-authored-by: Felipe Leopoldo Sologuren Gutiérrez <fsologureng@noreply.codeberg.org>
Co-committed-by: Felipe Leopoldo Sologuren Gutiérrez <fsologureng@noreply.codeberg.org>
2023-03-02 14:19:49 +00:00
Arnold Schrijver f57256028a Circlebuilder resigns from Moderation team (#185)
See also: https://codeberg.org/forgejo/meta/issues/176#issuecomment-820257

Co-authored-by: Arnold Schrijver <circlebuilder-codeberg@engagingspaces.io>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/185
Co-authored-by: Arnold Schrijver <circlebuilder@noreply.codeberg.org>
Co-committed-by: Arnold Schrijver <circlebuilder@noreply.codeberg.org>
2023-03-01 20:41:37 +00:00
Loïc Dachary 5281c83e89 [AGREEMENT] security team Gusted & dachary & fnetX (#174)
In accordance to the decision making process each applicant posted an
issue and actively reach out to the Forgejo community to get
feedback. During a period of four weeks no reservation or concerns
were expressed regarding their application and they can now become
legitimate member of the security team.

Closes: https://codeberg.org/forgejo/meta/issues/140

Co-authored-by: Loïc Dachary <loic@dachary.org>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/174
Co-authored-by: Loïc Dachary <dachary@noreply.codeberg.org>
Co-committed-by: Loïc Dachary <dachary@noreply.codeberg.org>
2023-02-27 15:08:23 +00:00
Loïc Dachary 078d706dda Becoming a legitimate member of Forgejo teams (#173)
Now that a decision making process is in place, as pledged at the
begining of Forgejo, I step down from all teams I belong to. I will
apply to become a member of the team in a way that meets the agreement
of the Forgejo community. This is an important step towards a
democratic governance and I'm happy this is happening.

I am not stepping down from the security team because:

* It is critical to keep the Forgejo user safe
* I have already applied to become a member

Co-authored-by: Loïc Dachary <loic@dachary.org>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/173
Co-authored-by: Loïc Dachary <dachary@noreply.codeberg.org>
Co-committed-by: Loïc Dachary <dachary@noreply.codeberg.org>
2023-02-27 15:05:53 +00:00
fr33domlover 6ebf771cf6
Add Feb 20 governance meeting notes 2023-02-22 22:03:32 +02:00
Loïc Dachary cfd37a557e FreeBSD team member & repository (#159)
Co-authored-by: Loïc Dachary <loic@dachary.org>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/159
2023-02-22 16:45:56 +00:00
Felipe Leopoldo Sologuren Gutiérrez b467378ed9 [AGREEMENT] Added first version agreement for PR moderation (#129)
First version of agreement for PR moderation according to discussed in #124

Co-authored-by: fsologureng <sologuren@estudiohum.cl>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/129
Co-authored-by: Felipe Leopoldo Sologuren Gutiérrez <fsologureng@noreply.codeberg.org>
Co-committed-by: Felipe Leopoldo Sologuren Gutiérrez <fsologureng@noreply.codeberg.org>
2023-02-22 14:39:16 +00:00
fr33domlover c8a5512b95
Turn VALUES.md into a full "commmnity contract" MISSION.md 2023-02-21 08:41:47 +02:00
fr33domlover c98adec122
Move decision-making agreements to AGREEMENTS.md & add decision making table 2023-02-21 08:19:41 +02:00
Loïc Dachary 6bfa3e560f Ryuno-Ki is no longer part of the security team (#161)
Co-authored-by: Loïc Dachary <loic@dachary.org>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/161
2023-02-20 21:03:38 +00:00
Loïc Dachary d258207ccf
unify the name of the recording 2023-02-20 19:01:31 +01:00
Loïc Dachary dbc9a64b24
governance meeting recording 2023-02-20 18:58:59 +01:00
Loïc Dachary 70c41d6d40 Add the team taking care of chatrooms (#158)
Co-authored-by: Loïc Dachary <loic@dachary.org>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/158
2023-02-17 23:46:14 +00:00
Loïc Dachary 8a735f7d23 add crystal to social account & release team (#157)
Co-authored-by: Loïc Dachary <loic@dachary.org>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/157
2023-02-17 23:44:44 +00:00
Loïc Dachary d822fc3b90
Resigning from the Well-Being team
My role only works of there is a consensus of all Forgejo community
members. There are concerns that I'm unfit for this role, reason why I
step down.

https://codeberg.org/forgejo/meta/issues/152#issuecomment-791859
2023-02-05 01:19:53 +01:00
Loïc Dachary 49ca881564
update the contributor list to match the corresponding team 2023-02-02 10:09:03 +01:00
crystal c0baa6851e
added crystal to contributors list 2023-02-01 13:05:35 -07:00
fr33domlover 586d0dc13a
Add agreement about asking well-being team for help with conflicts 2023-01-31 18:58:09 +02:00
Loïc Dachary 65df5701dc
fix logo links 2023-01-28 23:46:13 +01:00
Loïc Dachary 6d24420c40
Cherry-picking a PR with emacs and magit 2023-01-28 22:46:56 +01:00
fr33domlover 24b3530016
Place teams' files in teams/ subdir 2023-01-27 19:01:21 +02:00
fr33domlover 6b306e06d8
Add 2023-01-27 meeting notes 2023-01-27 17:42:19 +02:00
Loïc Dachary 3b0b9e3e15
2023-01-27 governance meeting 2023-01-27 14:51:20 +01:00
Sam Whited af398ba196
Add FreeBSD team
Fixes #121

Signed-off-by: Sam Whited <sam@samwhited.com>
2023-01-20 17:27:59 -05:00
Loïc Dachary a64c015f92
Social media agreement and team
Signed-off-by: Loïc Dachary <loic@dachary.org>
2023-01-20 18:01:49 +01:00
Caesar Schinas 3429cca195
add a monochrome version of the logo 2023-01-18 22:55:24 -10:00
gapodo e4aff30671 Add Gapodo to the list of Github organisation owners (#100)
Closes #100

As mentioned by @fsologureng I was added to the org by @caesar this should also clean up the missing documentation in the TEAMS.md
2023-01-09 23:17:33 +00:00
Loïc Dachary 8ecb1bbd1d remove the sentence related to who maintains what 2023-01-08 00:19:06 +00:00
Loïc Dachary 8e0d88d51c fix typo 2023-01-08 00:19:06 +00:00
Loïc Dachary 5a4f792b7b explain forgejo-contrib and the rules of engagement 2023-01-08 00:19:06 +00:00
Caesar Schinas e34fea4b78
add logo license 2023-01-07 02:00:01 -10:00
Loïc Dachary d55dc57c6a
document the teams 2023-01-05 21:12:08 +01:00
Loïc Dachary 38114413f3 document the primary color of the logo 2023-01-02 19:37:05 +00:00
oliverpool 08d3799b4e Document github organisation owners 2023-01-02 19:20:53 +00:00
fr33domlover b472fcf27c
Tweak team reference wording in DECISION-MAKING.md 2022-12-29 13:12:55 +02:00
fr33domlover c4377da62a
Add list of support resources to DECISION-MAKING.md 2022-12-29 10:55:42 +02:00
Caesar Schinas 5c1d732f4d
add current logo files and reorganise branding info 2022-12-25 22:44:35 -10:00
Loïc Dachary 3276b38b1d propose that transparency is a core value 2022-12-25 07:58:16 +00:00
Loïc Dachary 381a47aee8
make the readme a TOC to other documents 2022-12-24 12:20:59 +01:00
Loïc Dachary b14c84f331 Agreement about the Forgejo name, tagline, logo and mascot
Move from README.md to the newly created AGREEMENT.md and BRANDING.md
for details.
2022-12-24 11:12:52 +00:00
Loïc Dachary b47f07e030
governance meeting 2022-12-23 13:45:01 +01:00
Loïc Dachary 2be475ec3a
the accessibility team was created 2022-12-21 22:52:58 +01:00