Add Community Guidelines – X

[ckatzenbach]

In the PGA meeting today (with @afisher3578 @pg-adrian @smmkolesnikov, we discussed how to handle Twitter Comm Guidelines (aka Twitter Rules) in the future. The issue is that the Twitter Rules are ver fragmented, much more than multi-page document by other platforms. Put concretely, we believe it would be important to start tracking pages such as:
– Crisis misinformation policy
Parody, commentary, and fan account policy
– Coordinated harmful activity

What's happening there is key rule-making on important aspects of digital communication on those platforms, so we should be tracking those. But how to categorise them?

(1) Most other platforms have those types of rules within the Community Guidelines, and also Twitter has listed and linked them in the context of their Twitter Rules. So probably that would be the best high-level category.
(2) But currently we have a finite set of sub document types for Comm Guidelines that don't encompass such policies.

--> What shall we do?
(A) Add specific subdocument types for each of those?
(B) Add a catch-all-remainder subdocument type/category for Comm Guidelines?
(C) Start tracking them separately in one way or the other?

[MattiSG]

Thanks @ckatzenbach for this question!

Regarding Community Guidelines, I believe the conclusion in the multi-page RFC was that there should be no named subtypes: to support exactly this case, as eloquently brought by @pg-adrian at the time, the Community Guidelines are just one terms, made of several documents that are combined. This is apparently how you are currently declaring these terms in PGA. I thus fail to understand your point (2) 🙂

If you consider that your point (1) warrants having an explicit dedicated type for some of these terms, we will welcome a new type proposal!

[ckatzenbach]

Alright, then that is good news. Our impression was that this definition of term types (including subtypes for Community Guidelines) means that there should be finite list. I believe if we can keep this flexibility, it makes sense to not structure this too much and just add them to the declaration file for Twitter.

[MattiSG]

Thanks @ckatzenbach for explaining the reasoning!
I am sorry for these subtypes, they definitely are misleading! They are a remnant from OpenTermsArchive/engine#780, and should have been cleaned in OpenTermsArchive/engine#891. We will do that when we can (contributions welcome!).