Post by Pramire on Feb 6, 2018 23:59:04 GMT
Excerpt from the Developer policy:
4. Will Developers get promoted like other administrators?
Yes, they will have to climb the rank ladder. Developers will not outrank each other but work independently and collaboratively as needed. Developers will make any source readily available to other Developers for review and oversight. Administrators that become Developers will have the same permissions that they had before being appointed as a Developer. The Executive Lead Developer may be appointed for oversight and assistance to the owner but again, does not outrank the other developers, however, code will be revised by them and their assistants, in addition to other Developers.
5. Do server administrators outrank Developers or vice versa?
If they are a current administrator, the rank hierarchy still applies.
6. Can an administrator remove a Developer?
If necessary, a vote-off for a Developer can occur. The Developer is only then removed if the Lead Developer approves it. If a Developer is voted off and is removed from Developer status, their permissions gained as a Developer are removed. (This does not apply to Developers who applied for admin status and were promoted normally). In the event a Developer goes rogue or is breached, they can be removed. Likewise, a Developer could remove an Administrator if they went rogue or were breached if their admin permissions allows them to do so. Such an instance must be immediately reported to the Security Officer and Owner. Developers are still required to follow server conduct rules.
9. How can a Developer become an executive?
The Lead Developer and Webmaster with senior permissions are the only Developers in-line of becoming an Executive. If a Developer has admin permissions, they can become an Executive by being appointed by the Owner to another position, i.e. Security Officer.
11. How are changes made to the plugins?
If a current suggestion exists by an operator or administrator, the suggestion can be implemented if the suggestion is approved on the forum beforehand. If an issue is made on GitHub, making a suggestion, the same suggestion must also be made on the forum for members of the community to vote upon it. If a change is made, the Developer must notify the members on the forum. Commits must be made on (a) Owner and Lead Developer-approved GitHub organization(s). Changes to official organizations must be notified to the community.
A Lead Developer needs to be approved for the policy to operate effectively. Since there hasn't been any [public] headway made on the status of an appointment, I felt that a suggestion was necessary.
I'm suggesting Lemon to be selected as the Lead Developer to inherit permissions for Developer oversight, organization management and individual Developer management [among other permissions] as outlined by the policy here.
Yes, they will have to climb the rank ladder. Developers will not outrank each other but work independently and collaboratively as needed. Developers will make any source readily available to other Developers for review and oversight. Administrators that become Developers will have the same permissions that they had before being appointed as a Developer. The Executive Lead Developer may be appointed for oversight and assistance to the owner but again, does not outrank the other developers, however, code will be revised by them and their assistants, in addition to other Developers.
5. Do server administrators outrank Developers or vice versa?
If they are a current administrator, the rank hierarchy still applies.
6. Can an administrator remove a Developer?
If necessary, a vote-off for a Developer can occur. The Developer is only then removed if the Lead Developer approves it. If a Developer is voted off and is removed from Developer status, their permissions gained as a Developer are removed. (This does not apply to Developers who applied for admin status and were promoted normally). In the event a Developer goes rogue or is breached, they can be removed. Likewise, a Developer could remove an Administrator if they went rogue or were breached if their admin permissions allows them to do so. Such an instance must be immediately reported to the Security Officer and Owner. Developers are still required to follow server conduct rules.
9. How can a Developer become an executive?
The Lead Developer and Webmaster with senior permissions are the only Developers in-line of becoming an Executive. If a Developer has admin permissions, they can become an Executive by being appointed by the Owner to another position, i.e. Security Officer.
11. How are changes made to the plugins?
If a current suggestion exists by an operator or administrator, the suggestion can be implemented if the suggestion is approved on the forum beforehand. If an issue is made on GitHub, making a suggestion, the same suggestion must also be made on the forum for members of the community to vote upon it. If a change is made, the Developer must notify the members on the forum. Commits must be made on (a) Owner and Lead Developer-approved GitHub organization(s). Changes to official organizations must be notified to the community.
I'm suggesting Lemon to be selected as the Lead Developer to inherit permissions for Developer oversight, organization management and individual Developer management [among other permissions] as outlined by the policy here.
