github/overleaf
1
0
Fork 0
mirror of https://github.com/overleaf/overleaf.git synced 2024-09-16 02:52:31 -04:00
Code Issues Projects Releases Packages Wiki Activity
overleaf/server-ce/CONTRIBUTING.md
James Allen 5db301bc31 Update CONTRIBUTING.md
2014-02-21 20:36:33 +00:00

2.8 KiB
Raw Blame History

Contributing to ShareLaTeX

Thank you for reading this! If you'd like to report a bug or join in the development of ShareLaTeX, then here are some notes on how to do that.

Note that ShareLaTeX is actually made up of many seperate repositories (a list is available here).

Reporting bugs and opening issues

If you'd like a report a bug or open an issue then please:

  1. Find the correct repository. ShareLaTeX is split across multiple different repositories, each containing a different service (you can find a list of all repositories here, and all issues here). If you know the bug only applies to one service, then please open an issue in that repository. For general bugs and issues that span more than one service, please open an issue in the sharelatex/sharelatex repository.
  2. Check if there is an existing issue. If there is then please add any more information that you have, or give it a "+1" in the comments.

When submitting an issue please describe the issue as clearly as possible, including how to reproduce the bug, which situations it appears in, what you expected to happen, and what actually happens. If you can include a screenshot for front end issues that is very helpful.

Pull Requests

See our wiki for information on how to modify the ShareLaTeX code and set up a good development environment.

We love pull requests, so be bold with them! Don't be afraid of going ahead and changing something, or adding a new feature. We're very happy to work with you to get your changes merged into ShareLaTeX.

If you've got an idea for a change then please discuss it in the open first, either by opening an issue, or by joining us in our development chat room.

Developer Chat Room

If you want to ask any questions in real-time, or get a feel for what's going on then please drop into our development chat room. If no one is online then you can still leave a message that will hopefully get a reply when we return.

Security

Please do not publish security vulnerabilities publicly until we've had a chance to address them. All security related issues/patches should be sent directly to security@sharelatex.com where we will attempt to address them quickly. If you're unsure whether something is a security issue or not, then please be cautious and contact us at security@sharelatex.com first.