Contributing new support

1. Visit the motor record on GitHub: https://github.com/epics-modules/motor

2. Fork the master branch to your GitHub account (you'll need a GitHub account). Press the "Fork" widget in upper right of web screen.

3. git clone the fork from your account to your local workstation. You'll do the next steps within that clone.

... so far, real easy ...

4. hard part: develop the actual support

5. harder part: testing the support would be a big bonus

   Copy your support code into appropriate places, such as inside the motorApp directory, there are a variety of AaaaaaaSrc where Aaaaaaa is the name of the support directory. If you make a new AaaaaaaSrc directory, try to follow the patterns you see.

   Remember to copy in any databases, stream protocols, autosave request files, GUI screens, or other support into appropriate places.

... easy steps remain ...

6. Commit your changes to git and push your clone back back to your GitHub account.

7. On your GitHub, initiate a Pull Request (PR). That starts the discussion about how to finish this up before it gets merged into the motor record for general distribution.

---

One important aspect of this, especially if you think you lack caliber, is to get to that PR step so a discussion can start about your code. Changes, improvements, etc. can be committed throughout this discussion step. So, if you only have .c and .h files, commit them and start the PR, we can discuss what remains to be done.