If you're new to Mesos
See the getting started page for more information about downloading, building, and deploying Mesos.
If you'd like to get involved or you're looking for support
See our community page for more details.
Mesos Documentation Guide
Documentation is an integral part of every good feature. It describes the intended usage and enables new users to start using and understanding the feature.
We have three different kinds of documentation:
User guides and non-code technical documentation are stored in markdown files in the docs/ folder. These files get rendered for the online documentation.
We will accept small documentation changes on Github via a pull request. Larger documentation changes should go through the reviewboard.
Doxygen API documentation needs only to be applied to source code parts that constitute an interface for which we want to generate Mesos API documentation files. Implementation code that does not participate in this should still be enhanced by source code comments as appropriate, but these comments should not follow the doxygen style.
Substantial libraries, components, and subcomponents of the Mesos system such as stout, libprocess, master, agent, containerizer, allocator, and others should have an overview page in markdown format that explains their purpose, overall structure, and general use. This can even be a complete developer guide.
- Regular source code documentation
All other source code comments must follow the Google Style Guide.
Conventions
We follow the IETF RFC 2119 on how to use words such as “must”, “should”, “can”, and other requirement-related notions.