pleroma/pleroma-meta
1
0
Fork 0
Code Issues 55 Pull requests 2 Projects Releases Packages Wiki Activity

COMMUNITY_GUIDELINES.md: Create from Gentoo #120

Open
lanodan wants to merge 14 commits from gitlab-mr-iid-2 into master
pull from: gitlab-mr-iid-2
merge into: pleroma:master
Conversation 36 Commits 14 Files changed 1 +58
lanodan commented 2022-02-27 17:57:15 +00:00
Owner
Copy link

This is to discuss a bit on having community guidelines, as started into #pleroma-dev on 2022-02-27.

This is to discuss a bit on having community guidelines, as started into `#pleroma-dev` on 2022-02-27.
lanodan commented 2022-02-27 18:07:42 +00:00
Author
Owner
Copy link
This document describes Pleroma's Code of Conduct for public communication fora, as well as the action taken should it be broken.
```suggestion:-0+0 This document describes Pleroma's Code of Conduct for public communication fora, as well as the action taken should it be broken. ```
lanodan commented 2022-02-27 18:07:42 +00:00
Author
Owner
Copy link
Pleroma prides itself on being a community driven distribution that acts with the best interest of the community at heart. Rules and regulations that keep us all moving in a forward direction are a reality for a community of this size.
```suggestion:-0+0 Pleroma prides itself on being a community driven distribution that acts with the best interest of the community at heart. Rules and regulations that keep us all moving in a forward direction are a reality for a community of this size. ```
lanodan commented 2022-02-27 18:07:42 +00:00
Author
Owner
Copy link
This document describes Pleroma's Code of Conduct for public communication mediums, who shall enforce said Code of Conduct, the action taken should the Code of Conduct be broken, as well as the method for appeals. Questions about this document and its contents can be directed to/in [to be discussed]

I think it should be directed to a specific repo and/or something like #pleroma-staff on IRC.

```suggestion:-0+0 This document describes Pleroma's Code of Conduct for public communication mediums, who shall enforce said Code of Conduct, the action taken should the Code of Conduct be broken, as well as the method for appeals. Questions about this document and its contents can be directed to/in [to be discussed] ``` I think it should be directed to a specific repo and/or something like `#pleroma-staff` on IRC.
lanodan commented 2022-02-27 18:07:42 +00:00
Author
Owner
Copy link
> By joining and/or participating in the Pleroma community, you are stating that you accept and agree to adhere to the rules listed below, even if you do not explicitly state so.
```suggestion:-0+0 > By joining and/or participating in the Pleroma community, you are stating that you accept and agree to adhere to the rules listed below, even if you do not explicitly state so. ```
lanodan commented 2022-02-27 18:07:43 +00:00
Author
Owner
Copy link

This line will need to be reworked a lot, as we usually do have a bit of idle chatter and can accept bugs reports on pleroma-dev.

This line will need to be reworked a lot, as we usually do have a bit of idle chatter and can accept bugs reports on pleroma-dev.
lanodan commented 2022-02-27 18:07:43 +00:00
Author
Owner
Copy link
* **Use concise and clear language.** The Pleroma community includes people from all over the world, with varying English skills and available time.
```suggestion:-0+0 * **Use concise and clear language.** The Pleroma community includes people from all over the world, with varying English skills and available time. ```
lanodan commented 2022-02-27 18:07:43 +00:00
Author
Owner
Copy link
Pleroma developers have come together with a common purpose, to further the project. Conflicts will undoubtedly arise, and though you are encouraged to work through issues on your own, assistance is available as requested and as needed.
```suggestion:-0+0 Pleroma developers have come together with a common purpose, to further the project. Conflicts will undoubtedly arise, and though you are encouraged to work through issues on your own, assistance is available as requested and as needed. ```
lanodan commented 2022-02-27 18:07:43 +00:00
Author
Owner
Copy link
Maintainers/Staff/Moderators may attempt to resolve the problem by talking to involved parties, potentially issuing warnings if appropriate. If the problem repeats itself, there are various options open, including temporary access suspension to different Gentoo communication facilities (such as the Gitlab or IRC). Details on current guidelines can be found in pleroma-meta maintainers guidelines page.
```suggestion:-0+0 Maintainers/Staff/Moderators may attempt to resolve the problem by talking to involved parties, potentially issuing warnings if appropriate. If the problem repeats itself, there are various options open, including temporary access suspension to different Gentoo communication facilities (such as the Gitlab or IRC). Details on current guidelines can be found in pleroma-meta maintainers guidelines page. ```
lanodan commented 2022-02-27 18:07:44 +00:00
Author
Owner
Copy link

Same thing regarding how to direct reports/complains.

Same thing regarding how to direct reports/complains.
lanodan commented 2022-02-27 18:07:44 +00:00
Author
Owner
Copy link
Remember, the moment you participate in a public discussion on Pleroma medium, you have made yourself a representative of the Pleroma community. We hope that you will not take this responsibility lightly, and will prove to be a positive force in it.
```suggestion:-0+0 Remember, the moment you participate in a public discussion on Pleroma medium, you have made yourself a representative of the Pleroma community. We hope that you will not take this responsibility lightly, and will prove to be a positive force in it. ```
tusooa commented 2022-02-27 18:31:49 +00:00
Owner
Copy link

do we have a mailing list?

do we have a mailing list?
hj commented 2022-02-27 18:31:58 +00:00
Owner
Copy link

I'd like to see CoC mention the scope where it applies, i.e. development discussion in MRs and IRC and such, public annoucments/speaking (publicly) from position of power.

Far too many community guidelines nowadays overextend to other social/private life, i.e. you supposed to follow Twitch's rules even when you're on Fedi/Twitter/Reddit/4chan/whatever, not following the rules CAN get you banned on Twitch and it's bullshit (IMO).

I'd like to see CoC mention the scope where it applies, i.e. development discussion in MRs and IRC and such, public annoucments/speaking (publicly) from position of power. Far too many community guidelines nowadays overextend to other social/private life, i.e. you supposed to follow Twitch's rules even when you're on Fedi/Twitter/Reddit/4chan/whatever, not following the rules CAN get you banned on Twitch and it's bullshit (IMO).
lanodan commented 2022-02-27 18:33:26 +00:00
Author
Owner
Copy link

Nah, it's just that gentoo does, among a bunch of other things.

Might be a good idea to have something like a mailing-list later on though so it's not just gitlab or IRC.

Nah, it's just that gentoo does, among a bunch of other things. Might be a good idea to have something like a mailing-list later on though so it's not just gitlab or IRC.
lanodan commented 2022-02-27 18:39:33 +00:00
Author
Owner
Copy link

"misinformation" should probably be re-worded because of current day meaning having changed a lot since 2013.

"misinformation" should probably be re-worded because of current day meaning having changed a lot since 2013.
hj commented 2022-02-27 18:44:02 +00:00
Owner
Copy link

As ademan mentioned in IRC it should also have "assumption of good faith" aka presumption of innocence https://en.wikipedia.org/wiki/Presumption_of_innocence

As ademan mentioned in IRC it should also have "assumption of good faith" aka presumption of innocence https://en.wikipedia.org/wiki/Presumption_of_innocence
lanodan commented 2022-07-26 05:41:19 +00:00
Author
Owner
Copy link
Remember, the moment you participate in a public discussion in the Pleroma Project Infrastructure, you have made yourself a representative of the Pleroma community. We hope that you will not take this responsibility lightly, and will prove to be a positive force in it.
```suggestion:-0+0 Remember, the moment you participate in a public discussion in the Pleroma Project Infrastructure, you have made yourself a representative of the Pleroma community. We hope that you will not take this responsibility lightly, and will prove to be a positive force in it. ```
lanodan commented 2022-07-26 05:45:11 +00:00
Author
Owner
Copy link
* **Constantly purveying slander/defamation** despite repeated warnings.

Alternatively from FreeBSD Community Code of Conduct, not sure what kind of license it's in, it's a FreeBSD original rule.
Parts from Django Code of Conduct and Speak Up! are under CC-BY-3.0.
Parts from LLVM Community Code of Conduct are also under an unknown license.

* **In general, if someone asks you to stop, then stop.** Persisting in such behavior after being asked to stop is considered harassment.
```suggestion:-0+0 * **Constantly purveying slander/defamation** despite repeated warnings. ``` Alternatively from [FreeBSD Community Code of Conduct](https://www.freebsd.org/internal/code-of-conduct/), not sure what kind of license it's in, it's a FreeBSD original rule. Parts from [Django Code of Conduct](https://www.djangoproject.com/conduct/) and [Speak Up!](http://web.archive.org/web/20141109123859/http://speakup.io/coc.html) are under CC-BY-3.0. Parts from [LLVM Community Code of Conduct](https://llvm.org/docs/CodeOfConduct.html) are also under an unknown license. ```suggestion:-0+0 * **In general, if someone asks you to stop, then stop.** Persisting in such behavior after being asked to stop is considered harassment. ```
lanodan commented 2022-07-26 05:54:25 +00:00
Author
Owner
Copy link
* **Using the correct forum for your post. **Idle chatter does not belong in the Gitlab. Different fora will also have different standards of behaviour – a joke that is perfectly acceptable on IRC will be taken differently when made on a development forge or inside the source-code.

Mostly meh, I feel like the only one which fits there is the Gitlab part.

```suggestion:-0+0 * **Using the correct forum for your post. **Idle chatter does not belong in the Gitlab. Different fora will also have different standards of behaviour – a joke that is perfectly acceptable on IRC will be taken differently when made on a development forge or inside the source-code. ``` Mostly meh, I feel like the only one which fits there is the Gitlab part.
lanodan commented 2022-07-26 06:02:30 +00:00
Author
Owner
Copy link

Tried to add it, like via amending on "**Admit the possibility of fault and respect different point of views.**" or adding another point but I didn't find a way to make it work nicely, got some suggestions?

Tried to add it, like via amending on "`**Admit the possibility of fault and respect different point of views.**`" or adding another point but I didn't find a way to make it work nicely, got some suggestions?
lanodan commented 2022-07-26 06:08:24 +00:00
Author
Owner
Copy link

I put Maintainers for now but I think it would still be better to have a more or less different group of people so there is a way to get different people involved if needed.
Could be just a footnote/TODO as I think we might be too small in project members (~regular contributors).

I put Maintainers for now but I think it would still be better to have a more or less different group of people so there is a way to get different people involved if needed. Could be just a footnote/TODO as I think we might be too small in project members (~regular contributors).
lanodan commented 2022-07-26 06:09:27 +00:00
Author
Owner
Copy link

Related to #120/diffs

```suggestion:-0+0 ``` Related to https://git.pleroma.social/pleroma/pleroma-meta/pulls/120/diffs#note_92727
seanking commented 2022-08-26 21:55:48 +00:00
Member
Copy link

What means could we have to appeal for disciplinary measures? I guess we could have an email address like appeals@pleroma.social and then that could then forward the appeals to whoever handles that disciplinary action. But IDK. What do others think?

What means could we have to appeal for disciplinary measures? I guess we could have an email address like `appeals@pleroma.social` and then that could then forward the appeals to whoever handles that disciplinary action. But IDK. What do others think?
seanking commented 2022-08-26 22:01:32 +00:00
Member
Copy link

I concur.

I concur.
seanking commented 2022-08-26 22:03:34 +00:00
Member
Copy link

I feel like the best candidates for such a group would be folks who can objectively look at situations without a strong bias for or against certain developers, contributors, maintainers, etc.

I feel like the best candidates for such a group would be folks who can objectively look at situations without a strong bias for or against certain developers, contributors, maintainers, etc.
ilja commented 2022-09-12 16:45:48 +00:00
Member
Copy link

Seeing the nature of the software (a federated social network platform), not all communication happens on Pleroma Project Infrastructure. E.g. If I talk on fedi about some Pleroma feature/bug, or about some development work I'm doing, or talk to other devs (maybe from other AP-projects) about things, or..., then I'm as much a representative of the Pleroma community as I am on the GL issue tracker for example.

Also the "responsibility" part has a bit of a negative connotation.

Remember, the moment you participate in a public discussion within project spaces or in public spaces where you are representing the project, you have made yourself a representative of the Pleroma community. We hope that you will be a positive force in it.
Seeing the nature of the software (a federated social network platform), not all communication happens on Pleroma Project Infrastructure. E.g. If I talk on fedi about some Pleroma feature/bug, or about some development work I'm doing, or talk to other devs (maybe from other AP-projects) about things, or..., then I'm as much a representative of the Pleroma community as I am on the GL issue tracker for example. Also the "responsibility" part has a bit of a negative connotation. ```suggestion:-0+0 Remember, the moment you participate in a public discussion within project spaces or in public spaces where you are representing the project, you have made yourself a representative of the Pleroma community. We hope that you will be a positive force in it. ```
ilja commented 2022-09-12 18:00:36 +00:00
Member
Copy link

I added the 2.5.0 Milestone.

In chat it was decided that we want to have the guidelines agreed between us before, or at least not after, the release. The announcement should be done on the blog part so they're not lost into some release.

We may already do an announcement on donations and mention we're working on this, an extra blog post when we finished can be released in a subsequent announce to that one.

Adding the milestone may not be 100% technically correct since it's separate from the code, but it does show a commitment and makes it clear to us that this was decided.

I added the 2.5.0 Milestone. In chat it was decided that we want to have the guidelines agreed between us before, or at least not after, the release. The announcement should be done on the blog part so they're not lost into some release. We may already do an announcement on donations and mention we're working on this, an extra blog post when we finished can be released in a subsequent announce to that one. Adding the milestone may not be 100% technically correct since it's separate from the code, but it does show a commitment and makes it clear to us that this was decided.
lanodan commented 2022-09-12 18:07:20 +00:00
Author
Owner
Copy link

Yeah but that's pretty much a case-by-case basis kind of thing where I think the ones involved should point to one or more person that can act as an objective third-party.

Yeah but that's pretty much a case-by-case basis kind of thing where I think the ones involved should point to one or more person that can act as an objective third-party.
helene commented 2022-09-12 18:20:14 +00:00
Member
Copy link

I'm still not sure why this should be separated from the release announcement. I believe it is important enough that it should be included in the release announcement blogpost, particularly after previous events affecting Pleroma since the last major release.

I'm still not sure why this should be separated from the release announcement. I believe it is important enough that it should be included in the release announcement blogpost, particularly after previous events affecting Pleroma since the last major release.
ilja commented 2022-09-12 18:29:10 +00:00
Member
Copy link

So it wouldn't be lost in the other release announcements. As far as I'm concerned, it could still be mentioned in the release blog post as well (and link/reference to the other article).

So it wouldn't be lost in the other release announcements. As far as I'm concerned, it could still be mentioned in the release blog post as well (and link/reference to the other article).
hj commented 2022-11-21 20:32:30 +00:00
Owner
Copy link

also add a space in beginning .** -> . ** otherwise it breaks formatting

also add a space in beginning `.**` -> `. **` otherwise it breaks formatting
hj commented 2022-11-21 20:32:30 +00:00
Owner
Copy link

Looks good to me, although I think the whole Proctors thing should be pretty much just put onto maintainer's responsibility and/or community vote right now, as we really don't have nearly enough people to properly enforce things.

Looks good to me, although I think the whole Proctors thing should be pretty much just put onto maintainer's responsibility and/or community vote right now, as we really don't have nearly enough people to properly enforce things.
lanodan commented 2022-12-18 13:45:49 +00:00
Author
Owner
Copy link
This document describes Pleroma's Code of Conduct for public communication mediums, who shall enforce said Code of Conduct, the action taken should the Code of Conduct be broken, as well as the method for appeals.
```suggestion:-0+0 This document describes Pleroma's Code of Conduct for public communication mediums, who shall enforce said Code of Conduct, the action taken should the Code of Conduct be broken, as well as the method for appeals. ```
lanodan commented 2022-12-18 13:45:49 +00:00
Author
Owner
Copy link

The Proctors can be contacted by e-mail via proctors@gentoo.org.

Point of contact should be decided. I think it should be reasonably private but not via personal addresses / point of contact, for example via an issue on Pleroma's Gitlab.

> The Proctors can be contacted by e-mail via proctors@gentoo.org. Point of contact should be decided. I think it should be reasonably private but not via personal addresses / point of contact, for example via an issue on Pleroma's Gitlab.
hj commented 2022-12-21 23:45:29 +00:00
Owner
Copy link

issue in pleroma-meta should be fine, if not we can add another similar repo just for complaints about community

issue in pleroma-meta should be fine, if not we can add another similar repo just for complaints about community
lanodan commented 2022-12-22 00:24:54 +00:00
Author
Owner
Copy link
If you perceive a breach of the Code of Conduct guidelines, let the appropriate people know. Though they will also be watching many of the public mediums for any problems, they can not be expected to catch everything. Such reports can be made via [issues on pleroma-meta repository](https://git.pleroma.social/pleroma/pleroma-meta/-/issues).
```suggestion:-0+0 If you perceive a breach of the Code of Conduct guidelines, let the appropriate people know. Though they will also be watching many of the public mediums for any problems, they can not be expected to catch everything. Such reports can be made via [issues on pleroma-meta repository](https://git.pleroma.social/pleroma/pleroma-meta/-/issues). ```
hj commented 2023-11-22 14:56:35 +00:00
Owner
Copy link
* **Using the correct forum for your post.** Idle chatter does not belong in the Gitlab. Different fora will also have different standards of behaviour – a joke that is perfectly acceptable on IRC will be taken differently when made on a development forge or inside the source-code.
```suggestion:-0+0 * **Using the correct forum for your post.** Idle chatter does not belong in the Gitlab. Different fora will also have different standards of behaviour – a joke that is perfectly acceptable on IRC will be taken differently when made on a development forge or inside the source-code. ```
8ddb76cd88
Maybe should be contributor instead of development, at least it not about the Pleroma Social Network™
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin gitlab-mr-iid-2:gitlab-mr-iid-2
git switch gitlab-mr-iid-2

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff gitlab-mr-iid-2
git switch gitlab-mr-iid-2
git rebase master
git switch master
git merge --ff-only gitlab-mr-iid-2
git switch gitlab-mr-iid-2
git rebase master
git switch master
git merge --no-ff gitlab-mr-iid-2
git switch master
git merge --squash gitlab-mr-iid-2
git switch master
git merge --ff-only gitlab-mr-iid-2
git switch master
git merge gitlab-mr-iid-2
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
BE
No labels
BE
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
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
pleroma/pleroma-meta!120
No description provided.