Working with the Repository
You’ll need to install Mercurial first; check your OS’s package manager for a
You can check out a copy of the repository by cloning it:
$ hg clone http://bitbucket.org/zacharyvoase/markdoc $ cd markdoc/
There are several files and directories in the root of the repo:
markdoc/ |-- doc/ |-- src/ |-- test/ |-- UNLICENSE |-- MANIFEST.in |-- README |-- REQUIREMENTS |-- distribute_setup.py |-- nose.cfg `-- setup.py
- A Markdoc wiki containing Markdoc’s own documentation. How very meta.
- The home of all of Markdoc’s Python code.
- Markdoc’s tests (Python + Doctests) and nose configuration. Nose is a Python utility to automate and simplify running complex test suites.
- The text of the unlicense which designates Markdoc as public domain software.
- The necessary Python packaging machinery, so you can run
- Doesn’t need an explanation.
- A text file listing all of Markdoc’s requirements, suitable for use with
pip install -r REQUIREMENTS. pip is a next-generation
easy_installreplacement for Python.
Bug Reporting and Feature Requests
All bugs and feature requests are handled on the Bitbucket issues page.
If you’re interested in implementing a feature or extension for Markdoc, just fork the Bitbucket repository, work on the feature, commit your changes, then send me a pull request. If I like what you’ve done, I’ll pull your changes into the official Markdoc release and give you author credit.
Remember that you must be willing to release your changes to the public domain. If you are submitting a non-trivial patch, take a look at unlicense.org for detailed instructions; for now, you just need to agree to the following statement:
I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.