title: Apache Mesos | Community breadcrumb: Community layout: community_section
<h3 name="meetup">Local User Groups</h3>
<p><a href="user-groups/">Mesos User Groups</a> organize local Mesos events in different cities. Join one in your city, or learn how to start your own.</p>
<h3>Contribute</h3>
<h3 name="reportbugs">Report or track a bug</h3>
<p>New bugs can be reported on our <a href="http://issues.apache.org/jira/browse/MESOS">issue tracker</a>. In order to create a new issue, you'll need to signup for an account. See the guidelines <a href="/documentation/latest/reporting-an-issue/">here</a>.</p>
<h3 name="contribute">Contribute a patch</h3>
<p>Mesos relies on its community to test releases, find bugs, contribute fixes and features, and provide feedback on existing APIs. Your contributions are greatly appreciated! Since the infrastructure that the Mesos community uses day-to-day (ReviewBoard and JIRA) is unfamiliar to some, we also provide a beginner contribution guide which will help you get started using only GitHub.</p>
<p>Is this your first time contributing? See our <a href="/documentation/latest/beginner-contribution">beginner contribution guide</a>. Thanks! We love patches. :)</p>
<p>Looking to go deeper? Find out how to make larger contributions in the <a href="/documentation/latest/advanced-contribution">advanced contribution guidelines</a>.</p>
<h3 name="slack">Slack</h3>
<p>Developers and users chat at <a href="https://mesos.slack.com">mesos.slack.com</a>.</p>
<p>To request an invite for slack please click <a href="https://mesos-slackin.herokuapp.com">here</a>.</p>
<p>Thank you <a href="https://www.criteo.com">Criteo</a> for sponsoring Slack standard plan.</p>
<h3 name="ircchannel">IRC </h3>
<p> If you want to connect to our slack team through an IRC client please click <a href="https://my.slack.com/gateways">here</a> after signing up.</p>
<p>The slack channel is currently also mirrored at #mesos channel on irc.freenode.net.</p>
<p>If you are new to IRC, you can use a <a href="http://webchat.freenode.net/?channels=#mesos">web-based client</a>.</p>
<h3 name="twitter">Follow us on Twitter</h3>
<a class="twitter-timeline" href="https://twitter.com/ApacheMesos" data-widget-id="426586952293289985">Tweets by @ApacheMesos</a>
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
<h3 name="workinggroups">Working Groups</h3>
<p>
As the community has scaled, we work on larger and more involved features and components in separate interest or working groups.
By joining working groups, you will be able to get in touch with the stakeholders, contributors and committers interested in certain features for Mesos.
</p>
<p>
A working group is a group of people who are interested in actively participating in specific area of the project. Below are some of the expectations from a working group:
<ul>
<li>
Should have at least one lead who is responsible for organizing and driving the work group meetings.
</li>
<li>
Should have regular (online) meetings that are open to public, recorded and archived.
</li>
<li>
Should maintain meeting notes that are shared with the dev@mesos.apache.org list regularly.
</li>
<li>
Should have a corresponding slack channel (also publicly archived) where synchronous discussions take place.
</li>
</ul>
<h4 name="wgyoutube">You Tube Channel</h4>
<p>
Past meetings should be posted to the <a href="https://www.youtube.com/channel/UC0wxLxgX8ilUn0m31lCpzAw">YouTube Channel</a>.
</p>
<h4 name="wgmailinglist">Working Group Mailing List</h4>
<p>
Please use the <code>dev@mesos.apache.org</code> list for discussions. We don’t use separate mailing lists for each working group. In order to distinguish emails for a specific working group, please tag the email subject with the working group name like the following:
<p>
<pre><code>
[XXX WG] YOUR SUBJECT HERE
</code></pre>
</p>
</p>
<h4 name="activewg">Active Working Groups</h4>
<p>
<table style="width:100%">
<tr>
<th>
Name
</th>
<th>
Leads
</th>
<th>
Slack Channel
</th>
<th>
Meetings
</th>
<tr/>
<tr>
<td>
Containerization
</td>
<td>
<a href="mailto:yujie.jay@gmail.com;gilbert@apache.org">Jie Yu, Gilbert Song</a>
</td>
<td>
#containerizer
</td>
<td>
<a href="https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=sharing">Monthly on the first Thursday at 9:00 AM PST</a>
</td>
</tr>
<tr>
<td>
Performance
</td>
<td>
<a href="mailto:bmahler@apache.org">Benjamin Mahler</a>
</td>
<td>
#performance
</td>
<td>
<a href="https://docs.google.com/document/d/12hWGuzbqyNWc2l1ysbPcXwc0pzHEy4bodagrlNGCuQU/edit?usp=sharing">Monthly on the third Wednesday at 10:00 AM PST</a>
</td>
</tr>
<tr>
<td>
Community
</td>
<td>
<a href="mailto:vinodkone@apache.org">Vinod Kone</a>
</td>
<td>
#community
</td>
<td>
<a href="https://docs.google.com/document/d/1vgi434dYkkZHs49EK4F4eMmM-3JG4f3qg-N5En-4ubg/edit?usp=sharing">Every other Monday at 10:30 AM PST</a>
</td>
</tr>
<tr>
<td>
API
</td>
<td>
<a href="mailto:grag@apache.org">Greg Mann</a>
</td>
<td>
#http-api
</td>
<td>
<a href="https://docs.google.com/document/d/1JrF7pA6gcBZ6iyeP5YgDG62ifn0cZIBWw1f_Ler6fLM/edit?usp=sharing">Every other Tuesday at 11:00 AM PST</a>
</td>
</tr>
</table>
</p>
<h3 name="calendar">Events Calendar</h3>
<iframe src="https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com" style="border: 0" width="100%" height="600" frameborder="0" scrolling="no"></iframe>