Aspirational idea
Using OpenD is supposed to be easy - the opend accessible productivity portal can provide everything you need to do work. But hacking on opend might be a little more involved. This document should help you get started.
Maybe someday a opend please setup-developer command would be a good idea.
- Download git, make, etc., if you don't already have it
- Clone the repo you want to work on. Probably `dmd` to work on the language itself.
- If you've already done those steps, `git checkout master` then `git pull upstream master` to get caught up.
- `git branch -b some_name_you_make_up`
- Edit the things you want to edit
- Recompile with the makefiles
- Use `opend please vdev build ....` to build your test programs to experiment with it
- `git commit` to save your code. The commit message ought to explain what the change is about and why.
- `git push` to start the pull request process
When you open a pull request, be prepared to talk about what it does, why it does it, and how to use it. You might want to talk to us all about an idea before implementing it, but also sometimes an implementation is the quickest and easiest way to show something. Use your own judgement as to how much time you want to sink in, but if something isn't going to be pretty quick to code, you probably should talk about it first to make sure you aren't going to waste your time.
Notes
Language and runtime development work should be done on the `opend` repo. It combines dmd, ldc, and druntime into one for most ease of use.