Developing for the Server: Difference between revisions

From RetroMC
Jump to navigation Jump to search
(draft)
m (typo)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Developing for the server ==
[[Category:Server internals]] [[Category:Guides]]
Developing for the server is a great way to give back to the community if staffing isn't your thing. This page will go over the basics of developing of How to apply to develop, expectations, and progression.
Developing for [[RetroMC]] is a great way to give back to the community if staffing isn't your thing. This will be a basic overview of applying for the developer role, some expectations, and progression.
</br>
</br>
=== Applying to Develop ===
== Applying ==
Submit an Application: Apply through the server’s Discord by making a general ticket stating your intent to develop, any prior experience, and potential things you would like to work on. Barring any past major contributions to the projects used by the RetroMC on the RetroMC Github Org most applicants will be granted the role External Developer on discord. This grants access to the channels Technical-Announcements, Developers and Developer-Forum. Here you can discuss with other developers and staff about projects you would like to work on or get help with your current projects for the server.  
Send an application through the [[Discord server]] by making a [[Ticket system|general ticket]] and stating your intent to develop, any prior experience, and potential things you would like to work on. Barring any past major contributions to the projects used by RetroMC on the [https://github.com/retromcorg GitHub organisation], most applicants will be granted the [[Ranks#Staff-specific|External Developer]] role. This grants access to the channels <code>#technical-announcements</code>, <code>#developers</code> and <code>#developer-forum</code>, allowing you to discuss with other developers and staff about projects you would like to work on or get help with your current projects for the server.
</br>
</br><br>
External developers are only granted access to the basic projects used on the [https://github.com/retromcorg RetroMC Github Org] that are public, certain confidential repositories are not available to them until they have proved themselves with their contributions to be promoted to Developer.
External developers are only granted access to the basic projects on the [https://github.com/retromcorg GitHub organisation] that are public; certain confidential repositories are not available to them until they have proved themselves with their contributions to be promoted to [[Ranks#Developer|Developer]].
=== Development Process ===
 
In general all Developers can expect a standardized experience when submitting code to be used on the server that can be seen in the following flow chart.
== Development process ==
In general, all developers can expect a standardized experience when submitting code to be used on the server, as seen in the following flow chart:</br>
[[File:DevFlowChart.png|600x600px|frameless]]</br>
Current projects and wants can be found in the RetroMC Development <code>{{MCColor|&8|[}}{{MCColor|&4|Redacted!}}{{MCColor|&8|]}}</code>.</br>
== Expectations ==
All developers are expected to have some competency in a program language; whether it be [https://en.wikipedia.org/wiki/Java_(programming_language) Java] for server development, [https://en.wikipedia.org/wiki/HTML HTML] and [https://en.wikipedia.org/wiki/CSS CSS] for website development, [https://en.wikipedia.org/wiki/Lua_(programming_language) Lua] and [https://en.wikipedia.org/wiki/PHP PHP] for [https://en.wikipedia.org/wiki/MediaWiki MediaWiki] development, and whatnot.</br>
Developers (especially those who have been promoted to full-fledged Developer along with the in-game rank) are expected to conduct themselves as staff do, including (but not limited to):
* not using your staff powers (fly, vanish) to troll other players,
* not leaking confidential information, and
* generally follow all the [[server rules]].
For further reading, see the [[RSPM|staff policy]] and [[RCMP|change management]] manuals (and if you wish, the [[RPM]]).
 
{{MCColor|&4|<big><big><b>Failure to abide by said conduct may result in suspension or demotion.</b></big></big>}}

Latest revision as of 12:29, 25 February 2025

Developing for RetroMC is a great way to give back to the community if staffing isn't your thing. This will be a basic overview of applying for the developer role, some expectations, and progression.

Applying

Send an application through the Discord server by making a general ticket and stating your intent to develop, any prior experience, and potential things you would like to work on. Barring any past major contributions to the projects used by RetroMC on the GitHub organisation, most applicants will be granted the External Developer role. This grants access to the channels #technical-announcements, #developers and #developer-forum, allowing you to discuss with other developers and staff about projects you would like to work on or get help with your current projects for the server.

External developers are only granted access to the basic projects on the GitHub organisation that are public; certain confidential repositories are not available to them until they have proved themselves with their contributions to be promoted to Developer.

Development process

In general, all developers can expect a standardized experience when submitting code to be used on the server, as seen in the following flow chart:

Current projects and wants can be found in the RetroMC Development [Redacted!].

Expectations

All developers are expected to have some competency in a program language; whether it be Java for server development, HTML and CSS for website development, Lua and PHP for MediaWiki development, and whatnot.
Developers (especially those who have been promoted to full-fledged Developer along with the in-game rank) are expected to conduct themselves as staff do, including (but not limited to):

  • not using your staff powers (fly, vanish) to troll other players,
  • not leaking confidential information, and
  • generally follow all the server rules.

For further reading, see the staff policy and change management manuals (and if you wish, the RPM).

Failure to abide by said conduct may result in suspension or demotion.