Caviar's Department of Navy || Development Administration Protocol

[Jas_nRuski (Observer_99)]

SYSCOM Bulletin Board #0102
Written by: Jas_nRuski
Last Edited: 04/26/21

Introduction

This document shall outline and explain the protocols and precautions taken when dealing with specific scenarios.

Section A: Regular Protocols

All of the protocols that includes day-to-day operations are included here.

Recruitment Protocol

DEVELOPER RECRUITMENT PROTOCOL

Background Checks

• Gather all of the companies/teams/group owners a developer has worked for and interview as many of them as possible.

• Check if the developer is blacklisted from any development team/community.

• Check if the developer has any allegations attached to themselves.

• Check if the developer is an alt, view all/most of their groups/friends, account age, and see if they are registered on DevForum as a member.

• Visit all games/places the developer has.

• Check their inventory if necessary.

Interview/Qualification

1. Determine if their application is professional enough to be considered.

2. Determine if their work attached is good and not stolen/not ripped off.

3. If required:
   a. Set up a verbal interview of some sort.
   b. Ask the developer to accomplish a certain task.

Entry to Development Team

1. Have the intern developer complete at least two projects assigned.

2. Determine if their work ethics, quality of work, and work efficiency meet the standards of the development team.

3. If qualified, rank them in the main group.

4. If not qualified, keep them for more projects until they qualify or until after a whole month. If an intern is still not qualified after 30 days and 5 projects, they shall be terminated.

Administrative Strikes & Warnings

ADMINISTRATIVE STRIKES & FEEDBACKS

Feedback

• When a developer is not meeting the deadline required in which this incident happens/has happened once/twice occasionally.

• When a developer is breaking any minor articles of UCMJ and/or violates a part of their regulation in which the case is not severe and they are not a repeat offender.

• When a developer is unintentionally interfering with any internal matters such as regulations, events, and they are not a repeat offender.

Strikes(ST) and Suspension(SU)

A DEVELOPER WHO IS PLACED ON SUSPENSION MUST HAVE THEIR STUDIO ACCESS AND ADMIN ACCESS REVOKED IMMEDIATELY UNTIL THE END OF THEIR SUSPENSION OR BASED ON THE DISCRETION OF DEVELOPMENT ADMINISTRATION.

• When a developer is not meeting the deadline required for a project as a repeating offender (ST).

• When a developer is breaking any minor articles of UCMJ and/or violates a part of their regulation in which the case is semi-severe(ST) and/or they are a repeating offender (ST & SU).

• When a developer is unintentionally/intentionally interfering with any internal matters such as regulations, events, and they are/aren’t a repeating offender (ST and/or SU).

• When a developer is absent without leave (x1 ST per 3 days).

• When a developer is accused of any of the following cases (though not limited, ST and SU):

• • Asset Leaking
• • Threaten to remove asset
• • Harassment
• • Overreach of power (Admin Abuse)
• • Violation of UCMJ article 17 - 49, 52 - 76, and/or is on court for one of the violations as an accused.

Removal

• When a developer has more than 3 strikes and/or 2 suspensions.

• When a developer has:

• • Leaked assets
• • Removed/destroyed assets/equipment
• • Admin abused
• • Harassed
• • Acted extremely inappropriately

• Blacklisted from branch or service

• Violating any terms within section 2 and 3 of the development regulations.

• Intentionally and maliciously perform actions against a game/site/individual/group/organization.

Blacklist

A developer is qualified for a developmental blacklist if they are removed from the development team or plagiarizing information upon applying for a development position.

A developmental blacklist can elevate to a branch or even service blacklist if the case is severe enough.

Section B: Emergency Protocols

All of the protocols that includes day-to-day operations are included here.