Direction Guidelines - Revision history

DV vapetastic at 18:03, 9 October 2026

2026-10-09T18:03:13Z

← Older revision		Revision as of 14:03, 9 October 2026
Line 7:		Line 7:
	'''Interim CR Conduct Policy'''		'''Interim CR Conduct Policy'''

	This document outlines the responsibilities of members of the Interim Content Review Team (Interim CR) in terms of behavior while conducting Interim CR business or acting in a private or public-facing capacity for Interim CR-related subjects. The Interim CR Conduct Policy may be temporarily suspended or bypassed by a majority vote of High Command as specified in the High Command Voting Policy. '''Any staff member engaging in the content review process (A.K.A. Reviewers) is beholden to this policy, including but not limited to: Interim Reviewers, Heads of Staff, Project Managers, and Maintainers.'''		This document outlines the responsibilities of members of the Interim Content Review Team (Interim CR) in terms of behavior while conducting Interim CR business or acting in a private or public-facing capacity for Interim CR-related subjects. The Interim CR Conduct Policy may be temporarily suspended or bypassed by a majority vote of High Command as specified in the High Command Voting Policy. '''Any staff member engaging in the content review process (A.K.A. Reviewers) is beholden to this policy, including but not limited to: Interim Reviewers, Heads of Staff, Project Managers, and Maintainers. Any PR author is also subject to these policies when interacting with Reviewers. If this policy is broken by a PR author, this can result in a denial of the PR, a suspension of access, or removal from the codebase.'''

	==== '''Approach to Content Review''' ====		==== '''Approach to Content Review''' ====

DV vapetastic: /* Upstream Merges */

2026-10-09T16:14:05Z

Upstream Merges

← Older revision		Revision as of 12:14, 9 October 2026
Line 147:		Line 147:
	Upstream merges are an incredibly complex "update" that is brought into the server from Wizards Den (our upstream). This involves many "refactors" and changes to systems that make our codebase more stable, and able to run more efficiently.		Upstream merges are an incredibly complex "update" that is brought into the server from Wizards Den (our upstream). This involves many "refactors" and changes to systems that make our codebase more stable, and able to run more efficiently.

	After each upstream merge, if this contains more than 2 weeks of content, there is a '''Mandatory''' 3 day PR freeze. <small>This may be changed or removed at any time by any head of development</small>		After each upstream merge, if this contains more than 2 weeks of content, there is a '''Mandatory''' 3 day PR freeze. <small>This may be changed or removed at any time by any head of development (IE Head Mapper, Head Maintainer)</small>

DV vapetastic at 16:01, 9 October 2026

2026-10-09T16:01:45Z

← Older revision		Revision as of 12:01, 9 October 2026
Line 4:		Line 4:
	{{Important\|Title=Under Construction\|Note=This policy is currently under construction. All current documents are subject to change.\|Image=engineer.png\|Color=#c44f00}}		{{Important\|Title=Under Construction\|Note=This policy is currently under construction. All current documents are subject to change.\|Image=engineer.png\|Color=#c44f00}}

	~~=== Overview ===~~
	~~This page goes over Content Review, and How to perform these. This goes into detail about CR policy, Design Documents, Content removal, and more.~~

			'''Interim CR Conduct Policy'''

	~~== Content Review Policy ==~~		This document outlines the responsibilities of members of the Interim Content Review Team (Interim CR) in terms of behavior while conducting Interim CR business or acting in a private or public-facing capacity for Interim CR-related subjects. The Interim CR Conduct Policy may be temporarily suspended or bypassed by a majority vote of High Command as specified in the High Command Voting Policy. '''Any staff member engaging in the content review process (A.K.A. Reviewers) is beholden to this policy, including but not limited to: Interim Reviewers, Heads of Staff, Project Managers, and Maintainers.'''
	~~<small>Any portion~~ of the Content Review Policy ~~can~~ be suspended, or ~~overridden~~ by the ~~Content Director at any time~~.~~</small>~~

	~~1. The~~ '''Content Review ~~Team''' is expected to submit a roadmap to the '''Content Director''' and '''Project Management~~''' ~~for review when possible.~~		==== '''Approach to Content Review''' ====

	~~2. Content~~ Reviewers are expected to ~~fulfill their duties without bias~~. ~~Submission~~ of ~~PR’s that can~~ be ~~considered without merit~~ or ~~otherwise heavily biased~~, ~~should be considered for denial~~.		# Reviewers are expected to approach the process of content review with awareness of any personal biases regarding relevant subjects to the review, and should make those biases known to other Reviewers.
			# Reviewers should, even acknowledging biases, endeavor to approach the process of content review in an objective manner, and with the goal of achieving constructive dialogue and consensus (if possible) on the PR being reviewed.
			# Reviewers should utilize the Content Review bot (the "Raised Issue" system) and should have a generalized understanding of how the system functions and its appropriate use.
			# Reviewers should have a basic understanding of how PR submission works, including basic GitHub operations (pull requests, merges, etc), and should be reasonably up to date on the current state of Space Station 14 (the game, its mechanics, how systems function in play, etc).
			# Reviewers should focus on discrete issues when conducting content review, rather than making generalized statements ("I don't vibe with this," "This PR doesn't feel right," etc).
			# Reviewers should read the PR, ask questions of other reviewers or the PR author if necessary, and develop and articulate a stance on the PR.

	~~3. Content Reviewers are required to have a basic understanding~~ of ~~how PR Submission works, and how to use Github.~~		==== '''Behavior & Conflict of Interest''' ====

	4. ~~Using~~ the "~~Raised Issue~~" ~~system~~, ~~Content~~ Reviewers ~~must~~ have ~~a generalized understanding~~ of ~~how~~ to ~~use this system~~		# '''Staff ''cannot'' act as Reviewers for their own PRs.''' ''This includes but is not limited to: voting in favor of the PR, triaging the PR, or finalizing reviews of their own PR. Staff who are PR Authors are permitted to advocate, represent, clarify, and generally engage in conversation with Reviewers, as is normal for PR Authors; however, extended lawyering or attempts to use "soft power" (influence due to staff position, etc) can result in the Staff PR Author's access to the discussion being limited or denied, or the PR being denied by the Interm CR Team.''
			# '''Bullying, toxic statements, condescension, or "talking down" to others by Reviewers is not allowed.''' ''This applies to Community Members, PR Authors, or other Reviewers. If Reviewers engage in any of the above behavior, or violate the Staff Policy in the course of Interim CR work, they may have access to the discussion restricted or denied by the Interim CR Head or Moderation Staff. Repeated instances of the above behavior may lead to removal from the Interim CR Team at the discretion of High Command (as outlined in the Head Staff Voting Policy).''
			# '''Reviewers are encouraged to employ their expertise in discussion, but also to respect the expertise of other Reviewers in turn.''' ''Attempts to "correct" or otherwise dismiss the arguments of others in an offhand manner (i.e., one not backed by evidence/explanation) may be considered toxic behavior and may result in consequences as outlined above.''

	~~5. Content Reviewers cannot override issues on their own PR. The author is allowed to advocate, represent, clarify, and generally engage in conversation.~~

	~~6. Extended lawyering of PR Reviews is not allowed. Reviewers should focus on raising an issue, asking questions, and choosing a stance.~~

	~~7. Only Senior Content Reviewers may triage or finalize decisions regarding a PR with the standard review policy.~~

	~~8. No Content Reviewer may triage or end reviews for their own PR.~~

	~~9. Content Reviewers should be reasonably up to date and knowledgeable about the game and its intricacies.~~


Line 94:		Line 90:
	*Obvious small changes		*Obvious small changes

	*Additions or changes deemed by the ~~Content Director or Senior CR's~~ to be minor or essential (<small>this includes upstream merges</small>)		*Additions or changes deemed by the Interim Team lead to be minor or essential (<small>this includes upstream merges</small>)

	When in doubt, the team should be asked if a review is needed.		When in doubt, the team should be asked if a review is needed.

DV vapetastic: added under construction

2026-10-07T14:48:18Z

added under construction

← Older revision		Revision as of 10:48, 7 October 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:Content Review Guidelines}}		{{DISPLAYTITLE:Content Review Guidelines}}
	{{DISPLAYTITLE:Content Review Guidelines}}		{{DISPLAYTITLE:Content Review Guidelines}}

			{{Important\|Title=Under Construction\|Note=This policy is currently under construction. All current documents are subject to change.\|Image=engineer.png\|Color=#c44f00}}

	=== Overview ===		=== Overview ===

Vape: Review pol update

2026-07-15T19:27:40Z

Review pol update

← Older revision		Revision as of 15:27, 15 July 2026
Line 7:		Line 7:

	== Content Review Policy ==		== Content Review Policy ==
			<small>Any portion of the Content Review Policy can be suspended, or overridden by the Content Director at any time.</small>

	1. The '''Content Review Team''' is expected to submit a roadmap to the '''Content Director''' and '''Project Management''' for review when possible.		1. The '''Content Review Team''' is expected to submit a roadmap to the '''Content Director''' and '''Project Management''' for review when possible.

Line 13:		Line 15:
	3. Content Reviewers are required to have a basic understanding of how PR Submission works, and how to use Github.		3. Content Reviewers are required to have a basic understanding of how PR Submission works, and how to use Github.

	4. ~~In order~~ to ~~vote~~ on a PR, Content Reviewers ~~must present adequate reasoning and explanations behind~~ their ~~votes~~. ~~<small>We urge all reviewers~~ to ~~make use of~~ the ~~poll, as well as explain their reasoning~~.~~</small>~~		4. Using the "Raised Issue" system, Content Reviewers must have a generalized understanding of how to use this system

			5. Content Reviewers cannot override issues on their own PR. The author is allowed to advocate, represent, clarify, and generally engage in conversation.

			6. Extended lawyering of PR Reviews is not allowed. Reviewers should focus on raising an issue, asking questions, and choosing a stance.

			7. Only Senior Content Reviewers may triage or finalize decisions regarding a PR with the standard review policy.

			8. No Content Reviewer may triage or end reviews for their own PR.

			9. Content Reviewers should be reasonably up to date and knowledgeable about the game and its intricacies.

	~~5. Content Reviewers should be reasonably up to date and knowledgeable about the game and its intricacies.~~


Line 96:		Line 107:
	==How to conduct a review==		==How to conduct a review==

	Content Reviews should take place in the #content-review forum ~~channel~~. The CR who creates a Content Review post assumes responsibility for providing feedback to the author. This includes notifying the author that the content is under review, and summarizing feedback gathered in the review to provide the next steps to the author.		Content Reviews should take place in either the #public-content-review or the #private-content-review forum channels. The Senior Content Reviewer who creates a Content Review post assumes responsibility for providing feedback to the author. This includes notifying the author that the content is under review, and summarizing feedback gathered in the review to provide the next steps to the author.

			Content Review is not a vote. Content Review's take place with a raised issue system. If you have an issue with something in the PR, you should raise an issue using the Content Review bot using the small guide below:

			# Send a message outlining your issue with the PR.
			# Hover over the message.
			# Hover over <code>Apps</code>.
			# Hover over <code>Delta-V Bot</code>.
			# Click on <code>Raise Issue</code>. The message you send will be pinned and viewable by entering the command <code>/cr issue overview</code>. With every reminder message sent by the bot, the ratio of issues and overrules will be displayed. The same way is done to overrule issues.

	~~Content Review~~ is not a ~~true vote~~. ~~Members~~ of ~~CR are encouraged to vote in~~ the ~~poll~~, ~~give specific feedback on why they support or oppose this content~~, and ~~what should~~ be ~~changed, all with justification~~.		If an issue is not addressed, it must wait until the end of a review period. At the end of a review, the Senior Content Reviewer who initiated review, will tally both issues and overrides, and then determine whether the issues will prevent a PR from being merged. This includes requesting changes, applying a test merge, approving the PR as is, or denying the PR. <small>This can be overridden by the Content Director at any time.</small>

	Any final decisions must be communicated to the content author through appropriate channels. This will vary between PRs and DD. Design Document (DD) review takes place within Discord. Feedback should be provided within the original DD post in the forum.		Any final decisions must be communicated to the content author through appropriate channels. This will vary between PRs and DD. Design Document (DD) review takes place within Discord. Feedback should be provided within the original DD post in the forum.

Vape at 17:39, 7 February 2026

2026-02-07T17:39:51Z

← Older revision		Revision as of 13:39, 7 February 2026
Line 124:		Line 124:

	If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. <small>This only applies to PR's, and does not apply to design documents.</small>		If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. <small>This only applies to PR's, and does not apply to design documents.</small>


			== Upstream Merges ==

			Upstream merges are an incredibly complex "update" that is brought into the server from Wizards Den (our upstream). This involves many "refactors" and changes to systems that make our codebase more stable, and able to run more efficiently.

			After each upstream merge, if this contains more than 2 weeks of content, there is a '''Mandatory''' 3 day PR freeze. <small>This may be changed or removed at any time by any head of development</small>

Vape at 16:41, 7 February 2026

2026-02-07T16:41:34Z

← Older revision		Revision as of 12:41, 7 February 2026
Line 1:		Line 1:
			{{DISPLAYTITLE:Content Review Guidelines}}
	{{DISPLAYTITLE:Content Review Guidelines}}		{{DISPLAYTITLE:Content Review Guidelines}}

Vape at 16:41, 7 February 2026

2026-02-07T16:41:07Z

← Older revision		Revision as of 12:41, 7 February 2026
Line 1:		Line 1:
			{{DISPLAYTITLE:Content Review Guidelines}}

	=== Overview ===		=== Overview ===
	This page goes over Content Review, and How to perform these. This goes into detail about CR policy, Design Documents, Content removal, and more.		This page goes over Content Review, and How to perform these. This goes into detail about CR policy, Design Documents, Content removal, and more.

Vape at 16:35, 7 February 2026

2026-02-07T16:35:59Z

← Older revision		Revision as of 12:35, 7 February 2026
Line 109:		Line 109:

	== PR Deadlines ==		== PR Deadlines ==

			Deadlines are required when reviewing new content. Deadlines are relative to the size of the content. The standard method of tracking these deadlines is to create a poll with the appropriate duration in the review post.

			* Small changes are subject to 24 - 48 hours of consideration

			* Major changes are subject of up to 7 days of consideration. <small>this can be extended at any time with approval from a Senior CR or the Content Director</small>

			'''The minimum time for official review is 24 hours.''' <small>This can be shortened at any point with approval from a Senior CR or the Content Director</small>

			CR's should notify authors when the content is placed into official review, and give them an estimated wait time for feedback. If more time is required, the author should be notified.

			If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. <small>This only applies to PR's, and does not apply to design documents.</small>

Vape at 16:29, 7 February 2026

2026-02-07T16:29:40Z

@@ Line 71: / Line 71: @@
 ==== All content must pass the full review process before being approved ====
 with a few small exceptions. Proposed changes listed below do not require review:
 *Bug fixes
@@ Line 83: / Line 82: @@
 When in doubt, the team should be asked if a review is needed.
-====What to look for in a review====
 *Fits our MRP standard - Keeps the balance between action and roleplay, no overpowered things that break the fun. We want things to make sense in the setting.
 *Fits the Design Ethos - We are a server founded in analogue design. We want this to be displayed in all content that we merge, such that it fits the mechanical narrative of the game.