FM / source

/srv/osrm/osrm-backend/third_party/flatbuffers/docs/source/

/srv/osrm/osrm-backend/third_party/flatbuffers/docs/source

Name	Size	Mode	Actions
gRPC/	-	0755	rm
Benchmarks.md	4946	0644	edit dl rm
Building.md	4708	0644	edit dl rm
Compiler.md	8001	0644	edit dl rm
CONTRIBUTING.md	2242	0644	edit dl rm
CppUsage.md	27376	0644	edit dl rm
CUsage.md	8284	0644	edit dl rm
DartUsage.md	5153	0644	edit dl rm
doxyfile	102503	0644	edit dl rm
doxygen_layout.xml	8635	0644	edit dl rm
FlatBuffers.md	9219	0644	edit dl rm
FlexBuffers.md	7041	0644	edit dl rm
GoApi.md	1206	0644	edit dl rm
GoApi_generated.txt	4615	0644	edit dl rm
GoUsage.md	3782	0644	edit dl rm
Grammar.md	2267	0644	edit dl rm
groups	675	0644	edit dl rm
Internals.md	20064	0644	edit dl rm
JavaCsharpUsage.md	7055	0644	edit dl rm
JavaScriptUsage.md	4066	0644	edit dl rm
KotlinUsage.md	3774	0644	edit dl rm
LobsterUsage.md	3383	0644	edit dl rm
LuaUsage.md	3085	0644	edit dl rm
PHPUsage.md	3360	0644	edit dl rm
PythonUsage.md	3997	0644	edit dl rm
README_TO_GENERATE_DOCS.md	1078	0644	edit dl rm
RustUsage.md	7871	0644	edit dl rm
Schemas.md	27101	0644	edit dl rm
style.css	5507	0644	edit dl rm
Support.md	3425	0644	edit dl rm
Tutorial.md	104592	0644	edit dl rm
TypeScriptUsage.md	2431	0644	edit dl rm
WhitePaper.md	5744	0644	edit dl rm

Edit: /srv/osrm/osrm-backend/third_party/flatbuffers/CONTRIBUTING.md (2242B)

Contributing    {#contributing}
============

Want to contribute? Great! First, read this page (including the small print at
the end).

# Before you contribute
Before we can use your code, you must sign the
[Google Individual Contributor License Agreement](https://developers.google.com/open-source/cla/individual?csw=1)
(CLA), which you can do online. The CLA is necessary mainly because you own the
copyright to your changes, even after your contribution becomes part of our
codebase, so we need your permission to use and distribute your code. We also
need to be sure of various other things—for instance that you'll tell us if you
know that your code infringes on other people's patents. You don't have to sign
the CLA until after you've submitted your code for review and a member has
approved it, but you must do it before we can put your code into our codebase.
Before you start working on a larger contribution, you should get in touch with
us first through the issue tracker with your idea so that we can help out and
possibly guide you. Coordinating up front makes it much easier to avoid
frustration later on.

# Code reviews
All submissions, including submissions by project members, require review. We
use Github pull requests for this purpose.

Some tips for good pull requests:
* Use our code
  [style guide](https://google.github.io/styleguide/cppguide.html).
  When in doubt, try to stay true to the existing code of the project.
* Write a descriptive commit message. What problem are you solving and what
  are the consequences? Where and what did you test? Some good tips:
  [here](http://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message)
  and [here](https://www.kernel.org/doc/Documentation/SubmittingPatches).
* If your PR consists of multiple commits which are successive improvements /
  fixes to your first commit, consider squashing them into a single commit
  (`git rebase -i`) such that your PR is a single commit on top of the current
  HEAD. This make reviewing the code so much easier, and our history more
  readable.

# The small print
Contributions made by corporations are covered by a different agreement than
the one above, the Software Grant and Corporate Contributor License Agreement.

Contributing {#contributing} ============ Want to contribute? Great! First, read this page (including the small print at the end). # Before you contribute Before we can use your code, you must sign the [Google Individual Contributor License Agreement](https://developers.google.com/open-source/cla/individual?csw=1) (CLA), which you can do online. The CLA is necessary mainly because you own the copyright to your changes, even after your contribution becomes part of our codebase, so we need your permission to use and distribute your code. We also need to be sure of various other things—for instance that you'll tell us if you know that your code infringes on other people's patents. You don't have to sign the CLA until after you've submitted your code for review and a member has approved it, but you must do it before we can put your code into our codebase. Before you start working on a larger contribution, you should get in touch with us first through the issue tracker with your idea so that we can help out and possibly guide you. Coordinating up front makes it much easier to avoid frustration later on. # Code reviews All submissions, including submissions by project members, require review. We use Github pull requests for this purpose. Some tips for good pull requests: * Use our code [style guide](https://google.github.io/styleguide/cppguide.html). When in doubt, try to stay true to the existing code of the project. * Write a descriptive commit message. What problem are you solving and what are the consequences? Where and what did you test? Some good tips: [here](http://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message) and [here](https://www.kernel.org/doc/Documentation/SubmittingPatches). * If your PR consists of multiple commits which are successive improvements / fixes to your first commit, consider squashing them into a single commit (`git rebase -i`) such that your PR is a single commit on top of the current HEAD. This make reviewing the code so much easier, and our history more readable. # The small print Contributions made by corporations are covered by a different agreement than the one above, the Software Grant and Corporate Contributor License Agreement.