Development Team - Policies & Procedures
  • Development Team
    • Development Team Info
      • Team Leadership
      • Project Scopes
      • Task Processing
      • Git Procedures
      • Server Versioning
    • Non-Disclosure Agreement
    • Beta Team Info
    • Apply For Dev Team
    • Changelog
  • Special Updates
    • 3.5.0 Update
  • Developer Wiki
    • Local Dev Server
Powered by GitBook
On this page
  • Creating a New Task
  • Developers
  • Liaisons
  • Beta Team
  • Required Approval/Testing
  • Assignments
  • Implementation
  1. Development Team
  2. Development Team Info

Task Processing

Last updated 4 months ago

Creating a New Task

Recently, the Development Team has begun using Discord Forums to track tasks. Below are the details on how the #dev-tasks discord forum channel works:

Developers

If you wish to work on a bug posted in the main discord, create a thread and give it the Bug/Issue Fix tag. No initial approval is needed.

If you wish to work on a new resource or feature, create a thread with the tags Needs Review and the relevant scope: Graphics, Software, etc. This is for new items or significant rewrites to fix bugs. Ping Project Lead for review and initial approval

Liaisons

If you have a request for development, create a thread with the tags: Needs Review and Liaison Request. Ping the Project Lead for review and initial approval.

If a Liaison requests a change to the server, Job Liaisons and Project Leads will discuss what is needed and, , will file a joint AI with HA outlining how the job will use what is changing and how the development team plans to execute the item, this includes specifics on what is requested so that scope or additional changes do not creep in.

Beta Team

Please filter your viewing of the threads to show Beta Testing only. You will be pinged when / if Beta Team action is needed.

Anything that is not marked "Beta Testing" or is marked "NDA" should be considered NDA until told otherwise.

Required Approval/Testing

This section outlines when third parties must be involved in originating suggestions, project approvals, or beta testing. Project Leads may adjust these based on priority and severity or require HA AI approval for any request, regardless of the outlined below.

  • Does not need beta testing: vector location adjustments, spelling mistakes, civilian owned job changes and additions, etc....

  • Needs beta testing: Changes to functions and logic include adding or majorly editing job checks and vehicle category checks, adding new features to a script that also required editing a secondary script (briefcases, for example), moderate and large script updates, and anything new.

  • What needs Liaison approval? These items need to come from within the jobs through their proper development liaison procedures, not from developers.

    • Job Liaisons approve location changes for vehicles, armories, lockers, impound, on-duty locations, vehicle extras, and anything else that only affects that job.

  • Civilian and Development Joint Ventures These items will be worked on and adjusted in conjunction with Civilian Liaisons. These items DO NOT require HA approval, but a simple ping is needed for HA to be aware of the change.

    • Economic changes include price and availability adjustments for items, vehicles, pawn payouts, criminal payouts, crafting requirements, etc.

    • Civilian Liaisons will be the point of contact for creating new civilian-owned businesses. Project Leads will collaborate on any script adjustments to accommodate real estate allocation and sale and any needed database updates. Once approved, Development will facilitate these changes. HA will be notified of new jobs that the Civilian has approved and that the Development has begun working on implementation.

  • What needs HOD approval?

    • Significant changes would affect the economy (new weapons, large-scale criminal payouts, etc.)

  • What needs HA approval? Project Lead's will obtain HA approval for the following:

    • New scripts

      • Temporary or seasonal resources do not need action items; only a quick notification to HA in a Discord channel is necessary.

    • New vehicles and vehicle packs

    • New liveries

    • New Interiors and Maps

    • New Clothing Models and Large texture redesigns/recoloring

    • Changes to public safety paycheck amounts and frequency

    • Anything else deems needed by Project Leads

Assignments

A Project Lead will assign projects to the developer they feel best suits the project. However, developers may request a task at any time if their current tasks progress. Upon project assignment, the developer(s) is responsible for giving regular status updates and overseeing that task from the start, through beta, if required, and the final Merge Request. Project branches should be created in compliance with Git Procedures

Implementation

Once developers complete an assignment, they must create a Merge Request on GitLab. Project Leads will review these requests, give feedback as needed, approve and merge them, and stage them for release.

Any change affecting all LEO jobs (armories & trunk contents) will require agreement by at least one liaison for each job. Use in the development server for those discussions. This also includes proposed changes to default extras for shared vehicles (unmarked, civ vehicles). Notify HA of said changes via ping in Discord.

if applicable
#liasions-general