TOPIC: ⭐ [CM TEAM] Meeting Outcome 25/01/23 - NEW DEVS!

Community developers work closely together with the CM team and the server owners to consistently improve the community in various development areas. They oversee and assist in updates and bug fixes, and they are the first person the server owners should go to when encountering a problem with their server code. They are a skilled developer that oversee all Pointshop servers and ensure that every server has its bugs fixed and updates made.
They are required to think about future server options and assist in the creation of new servers. They have access to all server meetings and serve a prominent role in the weekly server owners meeting. They gain access to all the Pointshop server files and can code features and changes for DarkRP if accepted.

The community developers have the following rights and powers:

Can handle report abuses against all server ranks.
• Access to all server meetings.
• Access to the server owners meeting.
• Access to everything in game including rcon access and server options for all Pointshop servers.
• Access to all Pointshop server files and control panel.
• Access to Teamspeak Discord Admin powers.
• Access to Forum Administrator powers.
• Access to DarkRP Head Administrator powers.
• Can add new content to the servers with permission of the server owners.
• Can add or change content to DarkRP if accepted

---

The Community Developer role enables any member of the community to gain access to several different areas and codebases which will allow them to actively develop for the community without having to apply for a full Community Manager rank, especially if that person is not interested in the responsibilities that come with that role.

Community Developers can be given access to the following areas and codebases on a case-by-case basis. When they are applying or approached they should express what interest they have in being given access to each section:
• Access to Pointshop Servers and Head Admin ranks
• Access to SSRP Servers and Head Admin Ranks
• Access to Forum Administration
• Access to Forum Codebase
• Access to Discord Bot Codebase

All Community Developers who are accepted have the following rights and powers:

• Discord Head Admin
• Access to the Server Owners meeting and OneNote

Updates for any servers must be fully tested on a test server prior to release. This test server must be an exact copy of the live server that it is to be released on, and testing must be done on the same gamemode (where applicable).

In order for testing to be deemed complete, a full testing checklist must be created and followed with at least 3 people chosen at the Server Owners/Community Teams discretion.

2 members of the Community Team must approve any updates and the relevant checklists for it before it may be put onto the server. Initial testing should be carried out with all features completed at least 48 hours prior to the update.

Once an update has been tested and approved, an Announcement must be made on the forums, giving at least 24 hours of notice that the update is going to be released, including a list of relevant features / changes and the planned release date.

When this update is then put onto the server, which must be done by the main people behind the development, at least 2 people of Server Owner or above, including the main people who developed the update must remain on the server for a minimum of one hour to ensure that no other issues arise.

For something to be considered an “Update” under this policy, it must make significant change(s) to existing features or add new feature(s) to the server. This does not include basic configuration changes ie. Adding or removing levels / unlocks to a server.

When planning to implement major changes to or replacements for existing features, you need to discuss your changes with the Community Team in advance. Failing to do so might result in your changes not being released to the public.

Anything which is not deemed to be an update but still requires modification to the server’s codebase should not be done directly onto the live servers (excluding for rolling back changes or restoring backups). Though this does not require a full testing checklist and announcement, live editing should not occur.

If something has been fully tested on a test server with no issues or is only a minor configuration change (ie. Chat / voice tags), then this may be added to the live servers directly.