COllaborative DEcision MAking (codema.in)

Create an Inclusion Policy for FSCI

Pirate Bady Sat 30 May 2020 9:37PMPublicSeen by 160

I would like to suggest to create an Inclusion Policy so as to make our community more welcoming to everyone.

Pirate PraveenSat 13 Apr 2024 2:31PM

@fugata I believe constructive discussion is not possible when there is a fundamental disagreement on the axioms and we can only say we agree to disagree. When one side believes Free Software is not necessary for privacy and another believes Free Software is essential for privacy, any discussion will not change the other person's mind after the arguments are laid out once.

Pirate PraveenSat 13 Apr 2024 3:16PM

@bvul the point is not about silencing you, you made your point and we want to allow new people to make this point. But should we allow them to repeat this in every thread? Should we allow people to hijack every discussion to be a discussion about merits of WhatsApp? Should we be forced to respond to this topic every single day?

Snehal ShekatkarSat 13 Apr 2024 3:45PM

@bvul So you want us to react to you everyday in the group? If you believe that WA is better then it is enough to discuss it for a day or two and stop it. You can't keep talking against people who believe in Free software repeatedly in a group meant to promote Free software. Moreover, you seriously lack basic etiquette for a constructive discussion, and hence your other arguments are useless unless you improve upon this most important thing.

Ravi Dwivedi
Agree
Fri 12 Apr 2024 3:42PM

Some amount of challenging of our views is fine, but repeated claims of promotion of proprietary software is not good. This proposal also lets people to continue on codema.in so I don't see how it restricts (permissible) free speech.

Kannan V M
Block
Fri 12 Apr 2024 3:42PM

Isn't this a room moderation subject? Why this has to be in CoC?

Kannan V MTue 16 Apr 2024 6:45PM

I mean if someone want to boast about Watsapp, they can go the off topic groups or other group n boast about it. The function of FSCI main group is to discuss and give support for Free Software. I mean nobody is censoring anyone, its just one has to act according the purpose/description of a room. I mean thats the civil thing to do.

If someone spamming with off topic so it affects other on topic discussions, the person has to be removed from the room or may be temporarily ban them.

And its already mentioned in point 4 in https://fsci.in/code-of-conduct/#actions-to-increase-representation

Item removed

pirate kingFri 12 Apr 2024 7:34PM

This probably fits in a faq section rather than a coc.

Abhijith PASun 14 Apr 2024 9:39AM

The proposed addition to CoC is not saying we need to show zero tolerance to proprietary software discussions in FSCI rooms/groups but rather promoting/defending it. I believe this a basic understanding of any group that formed on a common interest. I don't think we need to be that explicit.

What sane person will join a chat room titled "Free Software" and then promote proprietary software in it multiple times. I think then that person's only interest it to troll or ridicule other group members.

The way this alleged person conducted in the chatroom, I don't think if it make any difference if they was promoting "WeeChat".

Item removed

Amending FSCI CoC, Section 6, subsection 4.

proposal by Kannan V M Closed Tue 23 Apr 2024 7:00PM

Outcome
by Pirate Praveen Fri 3 May 2024 5:29PM

This proposal passed and we need to update the website.

This poll is to include content moderation to CoC (https://fsci.in/code-of-conduct/) for off topic discussion in topic specific groups. Following line will be amended to Section 6, "Actions to Increase Representation", Subsection 4, "Try to be concise and on-topic", description.

Discussion on topic specific FSCI spaces are required to be on topic and should follow guidelines of respective spaces.

FSCI is a community focused solely on promotion and improvement to free software. Even thought at times discussions divert through diverse topics, discussions in FSCI groups or rooms are mostly about free software. Usually such diversions are taken lightly, but at times the focus shifts entirely to off topic discussions, affecting other discussions relevant to the group.

This amendment in CoC is required to manage/moderate such off topic discussions.

The amendment does not restrict speech, since FSCI has spaces that conduct off topic discussions.

Please do comment improvements to the amendment.

Remember to see the last part of CoC - https://fsci.in/code-of-conduct/,

"While this code of conduct should be adhered to by participants, we recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this code of conduct. When that happens, you may reply to them and point out this code of conduct. Such messages may be in public or in private, whatever is most appropriate. However, regardless of whether the message is public or not, it should still adhere to the relevant parts of this code of conduct; in particular, it should not be abusive or disrespectful. Assume good faith; it is more likely that participants are unaware of their bad behavior than that they intentionally try to degrade the quality of the discussion."

Results

Akshay
Abstain
Tue 16 Apr 2024 7:40PM

I see the point on being on-topic already covered. And also the enforcement related advise is at the last part (quoted). Don't see any particular need for this amendment.

Kannan V MWed 17 Apr 2024 6:26AM

@Akshay Looks like enforcement related part is not needed. I am removing that line. The idea of this amendment is to strengthen section 6.4, "Try to stay on topic, especially in discussions that are already fairly large.".

Pirate Bady
Agree
Tue 16 Apr 2024 7:40PM

since you're already proposing an amendment to this section, it'd be good to suggest to replace "email" with "message" in the existing text of that section. it's something we missed to notice during the adoption of CoC.

Pirate Praveen
Agree
Tue 16 Apr 2024 7:40PM

It improves the wording "try to be on topic" to "required to be on topic". May be adding an explicit consequence will be better. As each guideline in CoC is not of same severity, if being off topic can lead to a ban, I think it is better to be explicit. Or have an explicit listing of things that can lead to a ban.

Abhijith PA
Agree
Tue 16 Apr 2024 7:40PM

Now we are at it lets number our sections. I see only subsections are numbered.

Badri SunderarajanFri 28 Aug 2026 7:23AM

Our CoC mandates using inclusive language including,

  • Use “everybody” or “people” instead of “guys”.

We also informally refer people to heyguys.cc even though it is not explicitly mentioned in the CoC.

Unfortunately, using the particular word "guys" as an example keeps leading to a lot of debate every time someone joins the group, because "guys" is increasingly being used as a gender-neutral term. People also have differing opinions about this, leading to a more heated debate each time. (It's unfortunate that the primary example used is "guys" as that is relatively more controversial and leads people to object even if the context in which we are directing people to heyguys.cc or the CoC text is completely unrelated to the word "guys")

To avoid such repeated debates, while at the same time providing a clear explanation to newcomers while remaining welcoming and not making them feel silenced, I think it would be good to include a practical explanation of why we don't use even potentially gendered words like "guys" in our community (without going into philosophical and subjective debates). For example, this is what I wrote in the group chat recently:

[I]t's true that "guys" and "bro" can be used in a gender-neutral way and I don't see anything wrong with using it that way in groups where this is not a big issue. However, FSCI consists predominantly of people in tech circles, which have historically had low female participation. Further, it's a large public group where not everyone knows each other. That means there's a higher risk of women who joining ending up with the (not incorrect) impression that this is a male dominated group. Avoiding terms that could be misinterpreted as male-exclusive and preferring words that are more (perhaps even a bit performatively) gender-neutral is an easy way we can help these people feel more included, which is the first step to increasing women's participaton [sic] in tech (and especially Free Software) circles where they tend to feel excluded

I think heyguys.cc also addresses this in some way, but that explanation is more generic and furthermore we don't even link to it in the CoC.

Does anyone have objections to including a modified version of the above quote? We can either add a paragraph as part of the CoC as an addendum to it.