More actions
No edit summary |
→Delta-V Knowledgebase: clarify why in-game section may be out-of-date |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This document goes over most of the material of the 'Generalized' Onboarding. This does not go over specific details, and is only to be used as a resource. All staff members should have voice call or Discord discussion with a Senior / Head Of Staff 5 minutes or longer in duration prior to obtaining roles or accesses. | |||
This document goes over most of the material of the 'Generalized' Onboarding. This does not go over specific details, and only | |||
=== Staff Policy === | === Staff Policy === | ||
Below is the link | Below is the link to the staff policy. It applies to all staff, without exception. | ||
[[Staff Policy]] | [[Staff Policy]] | ||
== Staff HQ == | == Staff HQ == | ||
This is your "Quick Access" area to find exact details on policies regarding your position as a staff member | This is your "Quick Access" area to find exact details on policies regarding your position as a staff member. In each document you should find what you can, and cannot do, at a certain staff level. | ||
[[Staff HQ]] | [[Staff HQ]] | ||
== Delta-V Knowledgebase == | == Delta-V Knowledgebase == | ||
This is an in-house knowledgebase that categorizes '''ANYTHING''' you could possibly need information on. If | This is an in-house knowledgebase that categorizes '''ANYTHING''' you could possibly need information on. If something is missing from the in-game section, feel free to ping '''DisposableCrewmember42''' in the Discord. | ||
[https://knowledge.deltav.gay/ Delta-V Knowledgebase]: Contributor/Maintainer policy, List of Staff. Includes Adming Tips as an in-game section which may be out-of-date. Maintained by Toby222. | |||
[https://disposablecrewmember42.github.io/adming/ | [https://disposablecrewmember42.github.io/adming/ Adming Tips]: In-Game documentation only. Maintained by Disposable. | ||
== In-Game Staff == | == In-Game Staff == | ||
In-game staff such as Curators or Admins are required to have at least | In-game staff such as Curators or Admins are required to have voice call at least 10 minutes in duration with a Head of Staff or Senior prior to receiving any roles. This call has to cover what you '''can''' and '''cannot''' do as a staff member in your role. | ||
== | == GitHub == | ||
All bug reporting, as well as any codebase changes take place in the | All bug reporting, as well as any codebase changes take place in the GitHub repository. Content Reviewers are required to have a GitHub account, as well as basic knowledge on how to create a PR and how to create an issue report. | ||
[https://github.com/DeltaV-Station/Delta-v Delta-V Github] | [https://github.com/DeltaV-Station/Delta-v Delta-V Github] | ||
Latest revision as of 04:14, 15 March 2026
This document goes over most of the material of the 'Generalized' Onboarding. This does not go over specific details, and is only to be used as a resource. All staff members should have voice call or Discord discussion with a Senior / Head Of Staff 5 minutes or longer in duration prior to obtaining roles or accesses.
Staff Policy
Below is the link to the staff policy. It applies to all staff, without exception.
Staff HQ
This is your "Quick Access" area to find exact details on policies regarding your position as a staff member. In each document you should find what you can, and cannot do, at a certain staff level.
Delta-V Knowledgebase
This is an in-house knowledgebase that categorizes ANYTHING you could possibly need information on. If something is missing from the in-game section, feel free to ping DisposableCrewmember42 in the Discord.
Delta-V Knowledgebase: Contributor/Maintainer policy, List of Staff. Includes Adming Tips as an in-game section which may be out-of-date. Maintained by Toby222.
Adming Tips: In-Game documentation only. Maintained by Disposable.
In-Game Staff
In-game staff such as Curators or Admins are required to have voice call at least 10 minutes in duration with a Head of Staff or Senior prior to receiving any roles. This call has to cover what you can and cannot do as a staff member in your role.
GitHub
All bug reporting, as well as any codebase changes take place in the GitHub repository. Content Reviewers are required to have a GitHub account, as well as basic knowledge on how to create a PR and how to create an issue report.