Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Notifications
Mark all as read
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

60%
+1 −0
#1: Initial revision by user avatar sau226‭ · 2021-04-19T03:17:19Z (over 1 year ago)
Everything below is my opinion and not that of the Codidact project or any other user.

> We currently let users with the Curate ability promote posts across the Codidact network. Should we choose some subset of these for promotion?

We should allow some sort of process like the similar to occur:
* Someone with Curate ability promotes the post (this applies to the individual site/community)
* Some sort of extra social media promotion requirement is met (e.g. a fixed amount of people with the ability then try to promote it, some sort of vote score or other check is run and returns an "OK" result). 
One of the options (from my understanding) that I have considered for this check is to flag a mod only tag in each category as making this check pass (via a site setting maybe?), adding a flag (or history entry, similar to the post closed one) on the question if it has been promoted, and then posts tagged with that tag and without the history entry can be queued for the next stage.
* The Communities application (Qpixel) then pushes the post to social media via API. Depending on the desired social streams, I'm thinking an API integration with a social media manager tool (similar to Hootsuite/Buffer, but Buffer has no API support) or a direct API integration with a particular social media system (e.g. Twitter) will do the job. Alternately, a page that collects eligible posts in one place and allows Codidact community team members to copy and paste directly into social media or a social media manager tool in their browser (or a static share button that has a similar effect) could also work, assuming we have a Community Team member available to do this manually.

> Should we take submissions from moderators only or let anyone suggest a post to be shared?

We should allow anyone with access to nominate posts for promotion (people with Curate ability) to make the suggestion, however some sort of software enforced check (like that I outlined above) should have the final say on what submissions go out. If we do not want to allow the software to make these decisions or until we code the appropriate checks, making the submissions for social media promotion a moderator only thing may also work.

> Would it make sense for us to open a meta thread and let people nominate high-quality posts there?

In the short term and if we are unable/unwilling to build an integration with a social media platform or manager, this could be a suitable solution for nominations.

In the long term, if the amount of content increases or we are able/willing to build a semi-automated integration with a social media platform or manager, I would say that appropriate automation rules be introduced and adjusted as is necessary - the community should nominate privately, and the software should decide using the rules whether to queue or not queue.

> Are there any guidelines we should put in place around the content we share, e.g. avoiding controversial questions?

These discussions are best held on individual communities, due to the differing opinions and views held by each of them, and to allow them to self-regulate the use of the tool wherever possible.

A global policy may be created and enforced such the community policies need to be compliant with it, in which we can put in baseline requirements that are relatively uncontroversial. Discussion and creation of the global policy should happen on this Meta community/site.

> How should we enable community members (or anyone else) to object to a promotion or proposed promotion? We don’t want to create controversy; how do we avoid unintentionally doing so?

Create a meta post on the issue, or add a comment/answer to a meta post created for objecting to this. If there is community consensus or a legitimate requirement (e.g. for Twitter, the kind of account lock that requires you to delete content before the account can be used is applied to our account) to remove a piece of social media promoted content or remove it from the promotion queue, we should take the relevant action and notify the community where possible.

> How should we treat posts that are timely? (Promoting it now seems helpful; it might be less relevant by the time a meta discussion resolves.)

Some ideas for handling this are:
* Notify a Community Team member via the relevant channel on Discord who can manually post it
* Raise a flag for a moderator, who can nominate the post and then add the tag to trigger the promotion.
* Build some sort of tool to allow Community Team/Moderators to promote with a toggleable "override" setting that is logged in post history/maybe on a mod only page somewhere (in this case, the override setting would assume all checks passed and would place the post in the promotion queue directly).