mozillians/README.md

[mozillians.org](https://mozillians.org)
========
![build status](https://travis-ci.org/mozilla/mozillians.svg?branch=master)

A community directory for **Mozillians** to connect with each other.

Table of Contents
=================

* [Instal, docs, API and more](#install-docs-api-and-more)
* [Contribute](#contribute)
* [File a Bug](#file-a-bug)
* [Writing code](#writing-code)
* [Chat With The Team](#chat-with-the-team)

## Install, docs, API and more
For documentation, see [mozillians.rtfd.org](https://mozillians.readthedocs.org/) or build the docs.

## Contribute

### File a Bug
[Create a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Participation%20Infrastructure&component=Phonebook) on bugzilla.mozilla.org in the `Participation Infrastructure > Phonebook` component. If you then want to submit a Pull Request, mention the bug number in the pull request to help with tracking. Here's an example commit message for a bug fix:
```
[fix bug 937104] Update to latest playdoh.
```

### Writing code
Get started with our [How to Contribute](https://mozillians.readthedocs.org/en/latest/contribute.html) documentation.

### Chat with the team
You can talk with the team in the `#commtools` IRC channel on [irc.mozilla.org](http://irc.mozilla.org/). We're a friendly group!
Remove `what's deployed` section. 2016-12-21 16:18:02 +03:00			`[mozillians.org](https://mozillians.org)`
Update README with more information and useful links 2013-11-16 02:15:29 +04:00			`========`
Add travis status image. 2014-10-27 12:39:35 +03:00			`![build status](https://travis-ci.org/mozilla/mozillians.svg?branch=master)`
Update README to specify bug tracking 2012-08-24 23:28:02 +04:00
Update README.md 2015-02-06 17:13:56 +03:00			`A community directory for Mozillians to connect with each other.`
Update README with more information and useful links 2013-11-16 02:15:29 +04:00
styling/docs (README.md file) - fixing typos; adding ToC this PR does basically aim at: - styling/docs (README.md file) - fixing typos; adding ToC --- the motivation for such does basically lie within: - improving accessibility of the file; - making the file easier to be read; --- with that i do basically aim at: - encouraging users to come back to the file and contributing to it 2017-10-12 16:42:04 +03:00			`Table of Contents`
			`=================`

			`* [Instal, docs, API and more](#install-docs-api-and-more)`
			`* [Contribute](#contribute)`
			`* [File a Bug](#file-a-bug)`
			`* [Writing code](#writing-code)`
			`* [Chat With The Team](#chat-with-the-team)`

Update README.md 2015-02-06 17:13:56 +03:00			`## Install, docs, API and more`
Fix typo in README. 2017-11-06 15:50:44 +03:00			`For documentation, see [mozillians.rtfd.org](https://mozillians.readthedocs.org/) or build the docs.`
Update README with more information and useful links 2013-11-16 02:15:29 +04:00
Update README.md 2015-02-06 17:13:56 +03:00			`## Contribute`
Update README with more information and useful links 2013-11-16 02:15:29 +04:00
styling/docs (README.md file) - fixing typos; adding ToC this PR does basically aim at: - styling/docs (README.md file) - fixing typos; adding ToC --- the motivation for such does basically lie within: - improving accessibility of the file; - making the file easier to be read; --- with that i do basically aim at: - encouraging users to come back to the file and contributing to it 2017-10-12 16:42:04 +03:00			`### File a Bug`
Fix wording in readme. 2017-03-03 16:29:47 +03:00			[Create a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Participation%20Infrastructure&component=Phonebook) on bugzilla.mozilla.org in the `Participation Infrastructure > Phonebook` component. If you then want to submit a Pull Request, mention the bug number in the pull request to help with tracking. Here's an example commit message for a bug fix:
Update README with more information and useful links 2013-11-16 02:15:29 +04:00			```
			`[fix bug 937104] Update to latest playdoh.`
			```

styling/docs (README.md file) - fixing typos; adding ToC this PR does basically aim at: - styling/docs (README.md file) - fixing typos; adding ToC --- the motivation for such does basically lie within: - improving accessibility of the file; - making the file easier to be read; --- with that i do basically aim at: - encouraging users to come back to the file and contributing to it 2017-10-12 16:42:04 +03:00			`### Writing code`
Use HTTPS protocol 2017-10-02 19:52:27 +03:00			`Get started with our [How to Contribute](https://mozillians.readthedocs.org/en/latest/contribute.html) documentation.`
Update README with more information and useful links 2013-11-16 02:15:29 +04:00
Update README.md 2015-02-06 17:13:56 +03:00			`### Chat with the team`
Minor changes to enhance readability. 2014-07-20 13:23:29 +04:00			You can talk with the team in the `#commtools` IRC channel on [irc.mozilla.org](http://irc.mozilla.org/). We're a friendly group!