Emulator Issues #6126open
Write some "Guide to new Dolphin developers" wiki page
We're missing a lot of documentation that would help people know more about how to develop for Dolphin. We should create a wiki page explaining the global architecture of the project, how to use the infrastructure, who knows what in the development team, etc.
I'll most likely start working on it tomorrow, but if someone wants to start before that, go for it :P
My current TODO of things to explain:
Our dev workflow with Git: master is kind of stable, everything that is going to be worked on for more than 1-2 days goes to a separate branch. No rebase/merge --ff on branches pushed to the main repository.
Tools: Buildbot (+ WIP builders), irrawaddy, changes.dolphin-emu.org
Code architecture: what goes in Core/VideoCommon/AudioCommon/Common/Plugins/...
Global overview of the several components involved in emulation and how they communicate
Getting people to test your code: how to properly maintain a thread in the development forums to get as many people as possible to report issues before merging, who to ping on IRC, known useful testers, etc.
Who knows what in the team: who are the implicit maintainers of a subsystem (example: if I change GL stuff I probably want to ask degasus first, if someone changes DSP HLE stuff he should probably ask me, etc.)
Who maintains the wiki and how to contact them
Website/server infrastructure: where is the source code, where is it hosted, who has access to it, backups policy, how to edit the FAQ, etc.
Translation: who is admin on Transifex, how to merge the translations from Transifex to the Dolphin codebase, etc.
[Add your ideas here]