⭐ [CM TEAM] Meeting Outcome 09/09/2019
11 months 5 days ago #1161497
The CM Meeting was completed tonight by the following members of staff: Clarky, Chuteuk, TheXnator & .uzi. We have been discussing emails, unbans, updates and future plans for ZARP Gaming with our new CMs.
None this week!
Server Owners Meeting
Thank you to all the server owners this week: DEADMONSTOR
Contact Us Emails
All the emails have been handled this week. If your email didn't get answered, then for whatever reason we didn't get it. We DO look at all emails and reply to them all, even those people who are CM banned.
Warning: Spoiler![ Click to expand ][ Click to hide ]
Demotions of Super Admins & Head Admin staff can only be raised in the Head Administrator meeting. All other parts of this policy will apply to the demotion of Lead Team members.
When Community Team and Lead Team members are raised for a demotion, the option of an Official Warning does not apply. When raising a demotion of a Community Team or Lead Team member, the Official Warning option is replaced with the option of a sanction.
All eligible members in the meeting must vote on a specific sanction to apply to the staff member in question and a time period over which to review the staff member again.
The exact nature of a sanction is the discretion of the eligible staff members in the meeting; however, a list of acceptable sanctions is included in this policy which should be used. A staff member of any rank which is applicable to vote on the sanction must also be assigned to handle the sanction, encompassing letting the staff member know what is expected of them and producing a review of the staff member being punished and the quality of their work.
The sanction should be completed to a high standard to ensure that the staff member is showing to the team that they are able to perform their roles to the best of their ability. Should the staff member fail to do so, or fail to complete their assigned sanction at all without good reason, it is recommended that, as appropriate and at the discretion of the staff members voting, the demotion voting option should be utilised.
At the end of the time period, the eligible staff members must vote on the punishment again in the relevant meeting. The staff member assigned to the punishment must present their review and discuss whether they believe the staff member has learned from their mistakes or if further action is required.
Following discussion of the review, the eligible staff team must then vote on whether to take further action. The same voting options apply here.
The following sanctions can be used, with a time period of between 1 week and 1 month:
Primary focus on training newly accepted / promoted staff members
Requirement to attend all meetings and be vocal on discussions of voting items
Requirement to maintain 4 hours per week of consistent activity over the course of the time period, carrying out all other applicable roles / responsibilities
A report in any format desired by the staff member on a specific, relevant issue/concern on the server in question (or community in the case of the CM Team)
(Server Owners+) Producing an update for a specific server
(Server Owners+) Producing a test plan / performing tests of an update for a specific server
(Server Owners+) Producing a full review of the server(s) including current plans for betterment of the server(s)
On last week's meeting outcome, we mentioned our focus on the server events (both manual and automated). We have been overseeing the creation of several new arenas and even testing a new automated event! We are still keen to get some more ideas from the community, you can leave a reply here! >
We are currently reviewing our strategy of creating, managing and distributing Steam Workshop content. Currently, a lot of our content is shared across multiple content packs. Before we release our fixed models, we need to improve how we handle content and future-proof our process. We hope we can streamline this workflow in the near future.