#67 Policy proposal: Community Publishing Platforms
Merged 6 days ago by bcotton. Opened 6 months ago by jflory7.
Fedora-Council/ jflory7/council-docs proposal/planet-policy  into  master

@@ -6,6 +6,7 @@ 

  ** xref:diversity-advisor.adoc[Fedora Diversity Advisor]

  * Council Policies

  ** xref:policy/coc-response-policy.adoc[Code of Conduct Response Policy]

+ ** xref:policy/community-publishing-platforms.adoc[Community Publishing Platforms]

  ** xref:policy/guiding-policy.adoc[Guiding Policy]

  ** xref:policy/policy-change-policy.adoc[Policy Change Policy]

  ** xref:policies.adoc[Additional Policies]

@@ -0,0 +1,65 @@ 

+ = Community Publishing Platforms

+ Justin W. Flory, Fedora Council, Fedora Community, and others <council-discuss@lists.fedoraproject.org>

+ v1.1.1, 2020-10-02

+ :toc:

+ 

+ [link=https://creativecommons.org/licenses/by/4.0/]

+ image:https://img.shields.io/badge/License-CC%20BY%204.0-lightgrey.svg[License: CC BY 4.0]

+ 

+ This policy page describes how Community Publishing Platforms are defined, reviewed, and moderated.

+ It provides a loose framework of how moderation is handled in cases that https://fedoraproject.org/wiki/Legal:Trademark_guidelines#Community_sites_and_accounts[involve the Fedora Trademark].

+ 

+ 

+ [[what]]

+ == What are Community Publishing Platforms (or, Platforms)?

+ 

+ *Community Publishing Platforms*, shortened as *Platforms*, are content-focused websites that publish Creative Works with the Fedora Trademark.

+ Platforms are places for expression of ideas and thoughts specifically related to or in the interest of the Fedora Project and its community.

+ 

+ [[examples]]

+ === Examples

+ 

+ Creative Works include, but are not limited to, the following examples:

+ 

+ * Blog posts

+ * Pictures or photographs

+ * Public social media posts

+ * Other written communications depending on context

+ 

+ The Fedora Council reserves the authority to modify or expand the definition of Creative Works, based on unique context of the Fedora Project and the Fedora Community..

+ 

+ Community Publishing Platforms include, but are not limited to, the following examples:

+ 

+ * https://communityblog.fedoraproject.org/[Community Blog]

+ * http://fedoraplanet.org/[Planet]

+ * Specific social media accounts

+ ** https://www.facebook.com/TheFedoraProject

+ ** https://twitter.com/fedora

+ ** https://twitter.com/fedoracommunity

+ ** https://twitter.com/fedora_planet

+ ** https://www.youtube.com/channel/UCnIfca4LPFVn8-FjpPVc1ow

+ ** https://www.reddit.com/r/Fedora/

+ ** https://discord.gg/fedora

+ ** https://telegram.me/fedoranews

+ ** https://www.instagram.com/thefedoraproject/

+ 

+ [[content]]

+ == What content is appropriate for Platforms?

+ 

+ Community Publishing Platforms feature Creative Works controlled by but not actively curated by the Fedora Community and Fedora Leadership.

+ Platforms may be provided on infrastructure or web services hosted and managed by the Fedora Project or its sponsors.

+ Community Publishing Platforms are not actively curated because they rely on decentralized community labor and contributions that are difficult to centrally control.

+ 

+ Creative Works on Platforms must comply with the xref:project:ROOT:code-of-conduct.adoc[Fedora Code of Conduct].

+ These Creative Works are not officially endorsed by the Fedora Project or Red Hat, but must comply with https://fedoraproject.org/wiki/Legal:Trademark_guidelines#Community_sites_and_accounts[existing trademark rules].

+ If the Fedora Trademark is used, it must comply to this policy.

+ 

+ 

+ [[report]]

+ == How to report a Creative Work

+ 

+ If you participate in an informally moderated Platform (e.g. Reddit, Telegram, Discord, etc.), work with Platform moderators first to report a Creative Work.

+ For the provided examples, this could be a Sub-Reddit moderator, a Telegram group admin, or a Discord server admin.

+ 

+ If you are unsuccessful in working with Platform moderators OR a Platform moderator encourages you to do so, follow the reporting guidelines in the xref:project:ROOT:code-of-conduct.adoc[Fedora Code of Conduct].

+ Specific outcomes will fall under the scope of the Fedora Code of Conduct.

Hi,

I am opening this pull request to suggest a new policy around content and moderation in Fedora. This policy defines Community Publishing Platforms such as the Fedora Planet and Community Blog, sets expectation for what content is allowed or not, and points to the Code of Conduct page for how to report Creative Works.

My motivation to propose this policy comes from recent discussions on the council-discuss list. I startedon this PR thinking, "What is the policy I would like as a member of the Fedora community and also someone who often writes, blogs, and talks about Fedora?" So I first looked at the Fedora Planet page. It was really out of date and included information that is no longer relevant or just plain wrong. But there were some good things there, so I used it as a base. I ended up with this first draft of a policy that gives me creative freedom as a member of the Fedora community while also providing clear boundaries of acceptable or unacceptable behavior.

This PR includes three commits to help for easier review:

  • 1st: Direct copy+paste from "Planet" Fedora Wiki page
  • 2nd: Convert MediaWiki syntax to AsciiDoc
  • 3rd: First draft of Community Publishing Platforms policy

Please let me know how to proceed with this policy change. Thanks!

Screenshot of local preview from generated site source

rebased onto 7871f10

6 months ago

This is a great start, @jflory7! A few thoughts/questions:

  • I know you say the examples are not exhaustive, but was leaving out Fedora Magazine deliberate or does it fall under the proposed policy?

  • By "social media platforms" do you mean Fedora's social media platforms or those belonging to contributors individually?

  • It's probably worth including Code of Conduct violations in the list of what's absolutely forbidden

  • I'm a little leery of specifying consequences in this policy, since that really belongs in the CoC. On the other hand, I'm not sure we'll get a new CoC any time soon so maybe this is the best we can.

Now that I think about it some more, I don't think either of Community Blog or Magazine belong, because the intent seems to be for this to apply to unmoderated venues. Both the Community Blog and Magazine are moderated, official project channels.

@bcotton:
I know you say the examples are not exhaustive, but was leaving out Fedora Magazine deliberate or does it fall under the proposed policy?

Now that I think about it some more, I don't think either of Community Blog or Magazine belong, because the intent seems to be for this to apply to unmoderated venues. Both the Community Blog and Magazine are moderated, official project channels.

I deliberately excluded the Fedora Magazine. Admittedly, the Community Blog probably falls under the same exclusion. It just so happens that both publications are managed by Red Hat employees, but that was not always the case. That was why I included the Community Blog as an example initially.

@bcotton:
By "social media platforms" do you mean Fedora's social media platforms or those belonging to contributors individually?

Originally I was thinking of community social media accounts. But I also don't want to overlap too much on the Community sites and accounts policy.

I'm on the fence. What do you think?

@bcotton:
It's probably worth including Code of Conduct violations in the list of what's absolutely forbidden

Please give me the exact wording to use for this.

I'm pushing back a bit on this one. What is forbidden? Not being considerate or respectful? That is a very broad stroke. :wink: But I know changing language for the CoC is out of scope for this PR, but our existing Code of Conduct isn't clear on that, so I don't know how to be clear on that in this document either.

@bcotton:
I'm a little leery of specifying consequences in this policy, since that really belongs in the CoC. On the other hand, I'm not sure we'll get a new CoC any time soon so maybe this is the best we can.

I intentionally left it open-ended. Removal of content is not much different from what is already written on the Planet wiki page:

"Material which is deemed inappropriate may be removed from the Planet without prior notice, although the Fedora Project's contributors do attempt to resolve every such situation constructively and amicably."

Possible suspension of an account is new language, but it is also vague language. I did this in the spirit of "re-establishing activity is a conversation, not an algorithm" since this was a precedent set by the Mindshare Committee.

I deliberately excluded the Fedora Magazine. Admittedly, the Community Blog probably falls under the same exclusion. It just so happens that both publications are managed by Red Hat employees, but that was not always the case. That was why I included the Community Blog as an example initially.

I don't think Red Hat employment is the deciding factor here. Just that it's moderated an an official platform of the project. The WordPress instances are hosted by Red Hat's Open Source Program Office regardless of who the fearless leader is at any moment.

Originally I was thinking of community social media accounts. But I also don't want to overlap too much on the Community sites and accounts policy.
I'm on the fence. What do you think?

I think we want to make it clear what is in scope. I'm not entirely sure I know what I think the scope should be. I think it's okay to overlap the Community sites and accounts policy, since this is basically a reinforcement of that.

@bcotton:
It's probably worth including Code of Conduct violations in the list of what's absolutely forbidden

Please give me the exact wording to use for this.

I'd go with "Content that violates the Code of Conduct"

I'm pushing back a bit on this one. What is forbidden? Not being considerate or respectful? That is a very broad stroke. 😉 But I know changing language for the CoC is out of scope for this PR, but our existing Code of Conduct isn't clear on that, so I don't know how to be clear on that in this document either.

Yeah, our Code of Conduct is suboptimal. My suggestion above just pushes the dust under the rug. I some sense it doesn't improve things any (because of the weaknesses in the CoC you point out), but it does make it explicit that we expect contributions here to abide by the CoC. Specifically I'm interested in making it clear that harassment, etc is not acceptable.

@bcotton:
I'm a little leery of specifying consequences in this policy, since that really belongs in the CoC. On the other hand, I'm not sure we'll get a new CoC any time soon so maybe this is the best we can.

I intentionally left it open-ended. Removal of content is not much different from what is already written on the Planet wiki page:

"Material which is deemed inappropriate may be removed from the Planet without prior notice, although the Fedora Project's contributors do attempt to resolve every such situation constructively and amicably."

Possible suspension of an account is new language, but it is also vague language. I did this in the spirit of "re-establishing activity is a conversation, not an algorithm" since this was a precedent set by the Mindshare Committee.

Yeah, I like the intent, I'm just not sure I like the implementation. But that's more on Legal than you. :smile: I think s/will result/may be subject to/ is an okay middle ground?

So, would that cover personal twitter account, or just the ones using the Fedora trademark ?

I do ask that, because if we cover personal twitter account of contributor, then posting a meme would result in suspension, as I think that most memes are copyright violation, especially since fair use do not exist everywhere in the world.

The part about posting nudity would also be problematic if applied to contributor personal account, I do know a few people in the free software community who do have private instagram account (or private mastodon one) to post nudes or near nudity.

The part about "adult content" is also something that rub me off in the wrong way. There is place where discussing LGBTQ topic would be seen as "adult content", even if there is nothing sexual involved. It do happen on a regular basis, see the recent cloudflare debacle ( https://www.theregister.co.uk/2020/04/01/cloudflare_familyfriendly_dns_service_flubs/ ).

And in fact, adult content is quite vague. I see why it cannot be precise, but if someone speak of how they are doing their own beer, that's obviously about alcohol, and could be understood as "adult content" based on drinking laws in the US. But in Germany, you can drink beer if you are 14 under some conditions (and 16 without those condition), so that would not be understood as "adult".

Or someone speaking about their love of manga (like Elfen Lied, Battle Royale, who are kinda violent and dark), or movies (Saw 3 is 18+ in France, Trainspotting is 18+ in Argentina, Kill Bill is 18+ in Japan, Reservoir Dogs is 18+ in Germany).

1 new commit added

  • Make edits to definitions of Platforms and permitted content per review
6 months ago

@bcotton:
I don't think Red Hat employment is the deciding factor here. Just that it's moderated an an official platform of the project.

I respectfully disagree. Infrastructure and services managed by Red Hat employees for the Fedora community play by a different set of rules than infrastructure and services managed by the community. I think this is reflected by the Community Platform Engineering team handing off multiple projects to the community, but not fully being able to do so (e.g. G.D.P.R. concerns with some data).

Red Hat employment is not a crime. I don't see it in a negative light. But internal policies and motivations at Red Hat do influence decision-making about allocation of specific categories of resources in Fedora (e.g. a person's time). Since Red Hat is Fedora's most significant sponsor, I feel like this is just being honest.

@bcotton:
I'd go with "Content that violates the Code of Conduct"

Yeah, I like the intent, I'm just not sure I like the implementation. But that's more on Legal than you. 😄 I think s/will result/may be subject to/ is an okay middle ground?

Edited in commit aa8109a.

@misc:
So, would that cover personal twitter account, or just the ones using the Fedora trademark ?

Just the Fedora Trademark. In commit aa8109a, I added more explicit language to connect this policy to use of the Fedora Trademark.

@misc:
I do ask that, because if we cover personal twitter account of contributor, then posting a meme would result in suspension, as I think that most memes are copyright violation, especially since fair use do not exist everywhere in the world.

You put your finger on a sore spot.

A short-term reply: Fedora should not consider the behavior or content shared on personal media and this policy proposal does not apply to personal social media (unless you are using the Fedora Trademark on it). This only applies to Community Publishing Platforms, which for now, basically means the Fedora Planet and some shared Fedora-branded social media accounts. Or a personal social media account that also uses the Fedora Trademark.

A long-term reply: Technically this allows for a neo-Nazi to publish an affirmation of the Holocaust on their personal blog with no consequence to their participation in Fedora. I don't think this is what we want either. But I am also confident that we can agree something like the neo-Nazi example does not, and will not ever, belong on a Community Publishing Platform. I think this is something for the Code of Conduct to address, not the Community Publishing Platform policy.

1 new commit added

  • metadata: Add author line, revision line, attributes, and license header
6 months ago

The creative commons link does not seem to define content or work here. Also, it leads to a German page for me, so it would be good to link to a page in English to ensure "content" and "work" can be found there.

I would prefer an explicit list instead of some vague examples. As far as I understand, Twitter is not a "Community Publishing Platform" but https://twitter.com/fedora is, isn't it?

This sounds like a promise that does not seem like it will be kept. For this, someone would need to actively monitor Fedora planet posts and remove the content.

All other platforms are moderated already, aren't they? So why would violating content be published in the first place?

A short-term reply: Fedora should not consider the behavior or content shared on personal media and this policy proposal does not apply to personal social media (unless you are using the Fedora Trademark on it). This only applies to Community Publishing Platforms, which for now, basically means the Fedora Planet and some shared Fedora-branded social media accounts. Or a personal social media account that also uses the Fedora Trademark.

What does using the Fedora Trademark for a personal social media account mean?

For example for Twitter, does it mean that the Fedora logo is used as part of the artwork for the account or does it mean the trademark is used in a tweet, a re-tweet or a tweet that is liked?

This seems to be the only place we document any result of a Code of Conduct violation. By writing that they might loose their publishing access, it seems like this is the hardest action that might result from a CoC violation but there are other outcomes such as disabling the FAS account or taking legal action, IMHO.

Metadata Update from @jflory7:
- Request assigned

3 months ago

rebased onto f2ce11d

3 months ago

I rebased the PR on latest master. Will try to pick this back up and address comments later in August.

rebased onto 59ef34f

3 months ago

1 new commit added

  • Maintain internal definition of Creative Works
2 months ago

1 new commit added

  • Change examples of Community Publishing Platform to explicit list
2 months ago

1 new commit added

  • Do not set false expectations of active curation
2 months ago

1 new commit added

  • Leave disciplinary action to Code of Conduct
2 months ago

Hi @till, I pushed four new commits that addressed your points. I split them out commit-by-commit to preserve my logic and process for thinking through the changes. See the commit messages for more details:

  1. d38ea39 Maintain internal definition of Creative Works
  2. b9417d4 Change examples of Community Publishing Platform to explicit list
  3. 5e8a209 Do not set false expectations of active curation
  4. a892825 Leave disciplinary action to Code of Conduct

Your feedback was excellent and I appreciate your eye for detail. I actually feel much better about this draft now. I am curious for you to take another look and share your thoughts.

@till:
What does using the Fedora Trademark for a personal social media account mean?

For example for Twitter, does it mean that the Fedora logo is used as part of the artwork for the account or does it mean the trademark is used in a tweet, a re-tweet or a tweet that is liked?

If you use the Fedora Trademark in your social media profile picture, and you also post anti-Semitic, racist, misogynist, homophobic, or any kind of discriminatory content, Fedora should protect its right to the Trademark, and thus the Fedora Council's right to work with a platform to remove the Fedora Trademark where the Fedora Council wishes.

So, the bottom line is, the Trademark Policy should protect Fedora's right to remove the Trademark where the owners of the Trademark wish. If you put the Fedora Trademark in your profile, avatar, or digital presence, and you behave in a way that reflects the values of the Fedora Project, no problem. If you use the Trademark and start to do things that are damaging to Fedora's Vision or Mission Statement, we might have a problem.

rebased onto 58f378d

2 months ago

1 new commit added

  • Increment to v1.1.0, update timestamp, add new author
2 months ago

rebased onto 58f378d

2 months ago

rebased onto f909999

a month ago

Rebased to latest master.

rebased onto e3e1463

a month ago

Hmm, why "Creative works"? This seems to conditionalize the policy on the "creative" part (and copyright laws). If I create an automatically generated blog (e.g. something that republishes the fedora-messaging stream with combined random quotes from another source), it will not be "creative work" since it'll be fully algorithmically generated. I think it would be more reasonable to use a more general phrase like "content (text, images, videos)".

I have a little discord-specific question. On a real time chat platform such as this, it wouldn't be of much benefit to go through a roundabout way outlined in the bottom of this PR and that is "follow the reporting guidelines in the Fedora Code of Conduct."

Instead, we have a way that allows our members to get in touch with the moderation team privately through PMing a bot which in turn sends a notification to all the moderators and further facilitates communication between the team and the member.

So I'm wondering whether this should be somehow documented either within the CoC or within this PR. Personally I'd like a sentence added to the CoC that reaching out to moderators of the platform in question should precede the report via pagure.io/CoC (unless the issue is with those moderators (?))


Where I'm coming from - creating a CoC ticket because someone posted or said something inappropriate on a real time (end-user oriented) chat platform, for it to be handled weeks later, isn't helpful. Such channels require response within hours in the worst case scenario - ideally minutes.

I feel like "CoC reporting" is for much larger issues than this, (especially contributor focused issues) and that this should be reflected in these documents. Somewhere...

@zbyszek wrote…
If I create an automatically generated blog (e.g. something that republishes the fedora-messaging stream with combined random quotes from another source), it will not be "creative work" since it'll be fully algorithmically generated.

Personally I disagree, I would consider this a creative work because it required a human's creativity to make the algorithm. Our algorithms are biased to their makers. Take a look at Facebook these days. :grinning:

But I appreciate your feedback. While I disagree personally, I'll see what others think during the two-week review period before proposing changes.

@rhea wrote…
So I'm wondering whether this should be somehow documented either within the CoC or within this PR. Personally I'd like a sentence added to the CoC that reaching out to moderators of the platform in question should precede the report via pagure.io/CoC (unless the issue is with those moderators (?))

This is a great question. I am with you on this too. Your Discord experience mirrors my experience with Telegram. I would even hypothesize ~75% of Fedora Community conflicts can be amicably resolved at a more "local" level without going down the CoC route.

I don't have a great answer. I want to say it is a Code of Conduct question, but I do deliberately mention Discord and Telegram communities in the policy. It is probably easier to add a note like this in this policy than it is to propose changes to the Code of Conduct.

I will try to revisit and propose a new edit this week. I am traveling starting tomorrow so I have limited bandwidth, but it is on my list. :grin:

But opening a CoC ticket is also used for more than reacting, as that's also for long term tracking.

If X do a CoC violation on platform A, B and C, who are handled by different mods, it can go under the radar if they are not talking together (especially if there is secret on decision, etc, etc). That's a issue recently highlighted on https://blog.mozilla.org/community/2020/09/10/weaving-safety-into-the-fabric-of-open-source/ , see "Centralized Data Tracking".

So the formulation should also be clear that while people should speak to moderators for a faster answer, I feel it should also be summarized in a ticket, for tracking purpose.

For tracking of moderation we have the tools necessary for the platforms in question. The problem with making this information "cross-platform" is that we would have to track our members to actually be able to figure out what's their account on which network and you can probably guess what kind of implications that would have, to not mention the need for a technical solution better than pagure tickets. (A database with unique user identifier, all of their connected network accounts, their infractions and moderation actions taken against them. All that with integration with whatever network we want this to run on. Think Valkyrja project with Telegram, Matrix, IRC, and "forum" modules.)

rebased onto 5731a21

18 days ago

2 new commits added

  • v1.1.1: Version increment and timestamp edit
  • Amend reporting guidelines for Platform moderators
18 days ago

See commit c1edc24:

Amend reporting guidelines for Platform moderators

This commit amends the reporting guidelines at the end of the proposal.
The edit is based on feedback from @rhea in Pull Request #67. It
encourages reporters to work first with Platform moderators as a first
response. It deliberately adds language to allow a Platform moderator to
defer an issue to the Fedora Code of Conduct process at their
discretion.

This is a work-around to NOT collect Personally-Identifiable Information
about day-to-day issues often resolved quickly by an informed Platform
moderator who may have additional context that is not obvious. This
work-around hopefully encourages Platform moderators to work with the
Fedora Council at their own discretion of whether a local issue needs
escalation. Because making a formal report in the CoC is an
escalation, from a psychological point-of-view.

However, it also leaves a pathway for a reporter who is unsatisfied with
the handling of an issue by a Platform moderator to escalate.

@rhea I am curious on your thoughts on the edit from a Discord admin point-of-view.

Sounds good, thank you!

Pull-Request has been merged by bcotton

6 days ago