Discovery Gaming Community

Full Version: Development Team Structure
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
"Who does what around here?"

Discovery GC Development Team, Groups and Structuring

Disclaimer: This list may change frequently or slowly
Last Update: Wednesday, February 21st, 2018

Development Team
- Lead Developer:
- Assistant Lead Developer:
- Department Heads: , , , , ,
- Senior Developers: , , ,
- Junior Developers: , , ,
- Associates: , ,

- On Extended Leave: ,

Position Definitions
- Lead: Development Team oversight, organization, and management.
- Head: Coordinates, manages, and provides direction for the Department they are in charge of. They work alongside Junior and Senior members of their group, and report to the Lead Developer.
- Senior: Well-experienced and/or longstanding member of a Department. Those with expertise in multiple roles may be listed as this in their secondary positions.
- Junior: Usually a more recent addition to the Development Team. Those with multiple roles may be listed as this in their secondary positions. Some of their usernames might not appear in gold, a choice left to the part time assistants.
- Associate: As the title implies, these members are new and are undergoing instruction to perform their listed roles. As they are not yet full members, their usernames do not appear in gold.
- On Leave: Busy or away for the time being; expected to return at some point in time.

Department Definitions
- Storyline, Lore, & Infocard Developers: Directs roleplay progression
- System Modification Developers: Produces system and universe changes
- PvP Balance Developers: Manages combat aspects
- Art Developers: Models (including hitboxes, textures, hardpoints, and shield bubbles), effects (visual, sound), and iconography
- Website, FLHook, and Server Shenanigans: Code writing (for the game, forums, wiki, and more), server management, and update management
- Economy and Mining Developers: Works with commodity availability and pricing

Listed by Department

Storyline, Lore, Infocards, & Systems (SLIS) Planning Developers
- Head: (Story) (Infocards)
- Senior: ,
- Junior: , ,
- Associate:
- Current part time infocard writers: ,

Quality Assurance Developers
- Head:
- Developers:

System Modification and Bug Fixing Developers
- Head:
- Senior:
- Junior:
- Associate:

PvP Balance Developers
- Head:
- Senior: (Snubcraft),
- Junior: (Capital Ships and Snubcraft)
- Associate: (Capital Ships),

Art Developers
- Head: (Models & Visual Effects)
- Senior: (Models), (Visual Effects)
- Junior: (Models), (Icons & 2D Art), (Models)
- Associate: (Models)

Website, FLHook, and Utilities
- Head: (FLHook Code Writer, & DGC Wiki Administrator)
- Senior: , (DGC Wiki Administrator & Navmap Site Administrator)
- Junior:
- Associates: (DGC Wiki Administrator)

Economy and Mining Developers
- Head: (Economy)
- Senior:
- Junior:
- Associate:

Miscellaneous Developers
- Development Oversight (Lead Developer):
- Development Oversight (Assistant Lead Developer):
- Update Manager:
- Server Manager:
Development Workflow
- 1 - Development Team exits the bug fixing cycle from the previous update. Lead Developer initiates progress for the next update and sets an estimated preliminary deadline
- 2 - Story Planning Developers contact faction leaders, representatives, and/or lore knowledgeable players (where relevant) about planned updates. With their input and advice, these developers create, draft, revise, then finalize update packages
2 – 3 Lead Developer gives the System Modification Developers the go-ahead to start work for an update package, once completed by the story guys
- 3 - System Modification Developers work on their assigned packages (or chunks thereof) as time permits. They occasionally collaborate with or help out others on some portions, then they stitch it together and bug test when they've finished
3 – 4 Lead Developer gives the Economy Developers the go-ahead to start fixes and rebalances, once the packages are completed by the system modders
- 4 - Economy Developers correct trade route imbalances and errors, in addition to adjusting existing content plus creating new features as planned out
( - X [3, 4] - Meanwhile, Story Planning Developers, as managers of the Infocard Writers (and as writers themselves), produce the necessary infocards for the update. These are encoded into XML and inserted when complete)
( - Y [2, 3, 4] - Meanwhile, PvP Balance Developers work on balance solutions. Effects and Models Developers work with them, in addition to producing their own content. These three groups tend to have a mostly independent workflow from the rest, but the release schedule is the same as the team)

4 – 5 Lead Developer gives the Server Shenanigans Developers the go-ahead to prepare for a deploy of the update to the server, once workflow steps 4, X, and Y are complete
- 5 - Server Shenanigans Developers wrap everything up, and press the big red button. Relevant server utilities and features, such as the navmap, are also attended to
5 – 6 We all relax for a bit
- 6 - Development Team enters the bug fixing cycle for the just-released update. Developers work on problems relevant to their role
6 – 1 Wash, rinse, repeat

This is a basic gist of what goes on. There is some other background stuff, such as story/systems planning, economy planning, and the things those server guys do. Out of this main workflow, step 3 is definitely the longest part of that, which is why X and Y occur during it. Steps 4 and 5 are typically the most brief, yet also the most crucial phase.