Meza/Short procedure on how to submit a PR to Meza

For Meza

 * 1) At github.com
 * 2) Log in to your an account at Github.com
 * 3) Visit the Meza project page at: https://github.com/enterprisemediawiki/meza
 * 4) Create a "Fork" of the official Meza project on your github account
 * 5) On your wiki server
 * 6) Edit the files you think are wrong or need improved
 * 7) Back at https://github.com/ /meza 
 * 8) Verify that the changes you made a reflected in your fork of the meza project
 * 9) (optional) - Make a pull request (PR) in github using github gui tools to invite primary extension owner to "pull" your changes into their master repo.
 * 1) Back at https://github.com/ /meza 
 * 2) Verify that the changes you made a reflected in your fork of the meza project
 * 3) (optional) - Make a pull request (PR) in github using github gui tools to invite primary extension owner to "pull" your changes into their master repo.

For a specific extension on github

 * 1) On your wiki server
 * 2) vi either   or   and identify the repo source and version of the extension you wish to develop
 * 3) At https://github.com
 * 4) Log in to your an account at Github.com
 * 5) Visit the extension project page at: https://github.com/ /
 * 6) Create a "Fork" of the official extension project on your github account
 * 7) On your wiki server
 * 8) cd to
 * 9) Edit the files you think are wrong or need improved
 * 10) Visit
 * 11) Verify that the changes you made a reflected in your fork of the extension
 * 12) (optional) - Make a pull request (PR) in github using github gui tools to invite primary extension owner to "pull" your changes into their master repo.
 * 1) Verify that the changes you made a reflected in your fork of the extension
 * 2) (optional) - Make a pull request (PR) in github using github gui tools to invite primary extension owner to "pull" your changes into their master repo.

tgr's notes
You might set it something other than origin, but that's more of a personal workflow choice. e.g.: ...would be more of a feature branch type workflow
 * git remote set-url fork ...;
 * git branch my-fix;
 * git commit;
 * git push fork;
 * git checkout master