GitBook: [master] 39 pages and 2 assets modified

SUMMARY.md

@@ -0,0 +1,41 @@
+# Table of contents
+
+* [Initial page](README.md)
+* [README](operations/README.md)
+  * [Job Descriptions](operations/jobs/README.md)
+    * [cloud](operations/jobs/cloud/README.md)
+      * [Job Description](operations/jobs/cloud/software-engineer.md)
+      * [Job Description](operations/jobs/cloud/cloud-engineer.md)
+    * [hr](operations/jobs/hr/README.md)
+      * [Job Description](operations/jobs/hr/recruitment-analyst.md)
+    * [Job Description Security](operations/jobs/security/README.md)
+      * [Job Description Security](operations/jobs/security/leader.md)
+      * [Job Description Security](operations/jobs/security/engineer.md)
+    * [administration](operations/jobs/administration/README.md)
+      * [Job Description](operations/jobs/administration/administrative-assistant.md)
+    * [Front-end](operations/jobs/front-end/README.md)
+      * [Front-end technical leader - Job Description](operations/jobs/front-end/technical-leader.md)
+  * [Security Policy](operations/security-policy.md)
+  * [Travel Policy](operations/travel-policy.md)
+  * [Rocket.Chat Incentives Policy](operations/incentives.md)
+  * [Paid Time Off Policy](operations/paid-time-off-policy.md)
+* [Onboarding](onboarding.md)
+* [LICENSE](license.md)
+* [Support](support/README.md)
+  * [Team](support/team.md)
+  * [Processes](support/processes.md)
+  * [Systems](support/systems.md)
+  * [Reference](support/reference.md)
+  * [SLAs](support/slas.md)
+  * [Partner Guide](support/partner-guide.md)
+* [Design](design.md)
+* [Product](product/README.md)
+  * [Rocket.Chat Release Planning](product/release-cycle.md)
+  * [Places or pages to update](product/pages-to-update.md)
+* [Departments](departments/README.md)
+  * [Security](departments/security.md)
+  * [Mobile Department](departments/mobile.md)
+* [Marketing](marketing.md)
+* [Summit](summit.md)
+* [Contributor Covenant Code of Conduct](code_of_conduct.md)
+

code_of_conduct.md

@@ -0,0 +1,44 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, available at [http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4/)
+

departments/README.md

@@ -1,4 +1,5 @@
 # Departments
 
-- [Mobile](mobile/)
-- [Security](security/)
+* [Mobile](mobile.md)
+* [Security](security.md)
+

departments/mobile.md

@@ -0,0 +1,98 @@
+# Mobile Department
+
+_Note: this document is still in progress, but everything that’s written here is valid starting 9th November, 2018_
+
+## Experts
+
+* [Filipe Brito](https://open.rocket.chat/direct/filipe.brito), Android Engineer
+* [Rafael Kellermann Streit](https://open.rocket.chat/direct/rafael.kellermann), iOS Engineer & Team Leader
+
+## Basics
+
+### Working Hours
+
+We expect you work from 9am to 6pm every day from your timezone. If you cannot make this hours, inform your team leader of the times you’ll work so everybody will know and we will avoid contact with you outside these hours. Since the mobile team is 100% remote, we need to make sure our times are synced so we don't bother other colleagues when they're not working.
+
+### Chat \(open.rocket.chat\)
+
+It’s not required to be connected to the chat all the time, but it’s expected that you check it at least twice in the morning and twice in the afternoon so you don’t miss important announcements or important questions.
+
+### Mobile Team Sync
+
+1. There will be a bot every Monday, Tuesday, Thursday and Friday that will ask you in the morning what’s your status \(working on, blocked issues, problems you are having, etc\). It’s expected that you reply to this bot as soon as you start working that day.
+2. We have calls every Wednesday with iOS and Android team. It’s expected that all of you participate of this meeting \(it’s only once a week!\) and the duration is between 30min and 45min.
+3. It’s expected that you keep your status in GitHub Projects updated. Every cycle has a project and there’s columns that specifics what should be done, what is in progress, what’s waiting for review and what’s done already.
+
+### Rocket.Chat Company Weekly Calls
+
+Every week the whole company joins a call via Jitsi \(link on the event\) at 1pm Brasilia Time \(duration is no longer than 1h\). It’s expected that you are present into this meeting and if not, you **must** inform your team leader why.
+
+### Calendar
+
+Mobile Team has a shared calendar where we put our deadlines and important events to the whole mobile team. Make sure you have it subscribed in your calendar application, you can copy [this url](https://calendar.google.com/calendar?cid=cm9ja2V0LmNoYXRfY3BqcGV2a3BvOXR1NmZxbWczdDNvM2tobjRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ).
+
+It's also expected that you reply to the invitations you are invited for with yes, no or maybe.
+
+### Emails
+
+There are three emails that we can use to communicate internally: `[email protected]`, `[email protected]` and `[email protected]`. If you want to communicate the whole team you can reach `[email protected]`.
+
+It’s expected that you check your email at least twice a day \(morning and afternoon\) for new invitations, annoucements, etc.
+
+### Forum
+
+There's an [internal category in our forums specific to the Mobile Team discussions](https://forums.rocket.chat/c/internal/mobile). It's encouraged that everyone share ideas and problems there in form of discussion. It's the preferable way to communicate long discussions with your team. All discussions on this category are private.
+
+### Office Vibe
+
+You will receive sometimes emails from Office Vibe questionnaires. It’s expected that you reply to all of them in order to help Rocket.Chat improve with your feedback. We encourage you to give us written feedback from there as much as possible, one of our core values is to be transparent and honest with each other. If you don't feel like giving feedback with your name on it, you can also choose to send the feedback anonymously.
+
+### Small Improvements
+
+Once a quarter you’ll be requested to make 360º reviews of some of your colleagues and to make your self-assessment. The 360º reviews are optional but we encourage you to give to at least 3 of your collegues once a quarter. The self-assessment review is strictly required as your team leader will also write a feedback for you and you'll only be able to do see it if your self-assessment was written.
+
+### PTO
+
+Please refer to the company guidelines about PTO in [company's handbook](https://rocket.chat/handbook/operations/paid-time-off-policy/).
+
+### Vacations
+
+We don’t contact you in your vacation time unless it’s super urgent. The contact will probably be over phone call or something, but we plan everything so we don’t have to contact you at anytime. We don’t expect you to read your emails, calendar changes, forums, chats, etc. This is the time for you to turn off and disconnect. Also refer to the [company handbook](https://rocket.chat/handbook/operations/paid-time-off-policy/) for more information about vacations.
+
+## GitHub
+
+### Pull Requests
+
+1. Prefer to use pull-requests to send changes to your repository always. It’s also very important that your pull-request have tags, milestone and the cycle.
+2. You can request your colleagues to review your PRs as much as you want. It’s expected that every colleague don’t take more than 24 hours to review a new pull-request. Taking more than 3 days to review a PR will sound us an alarm that something is not right. We believe that moving the project with small pull-requests is the way to go and reviewing them quickly will reduce the changes of causing conflicts and wasting time to fix it.
+
+### Issues
+
+1. It’s expected that you create issues for the bugs you found, improvements that you think are necessary \(or want to start a discussion about it\) or new features. It’s always preferable to discuss things on the issues or pull-requests than on the chat or video calls.
+2. Make sure you tag your issues and the issues from the community correctly and add the milestone if you think it makes sense.
+3. Bugs are prioritised over new features and improvements most of the time, if you have any question about the prioritisation, contact your team leader.
+
+### Planning
+
+You can refer to your platform planning document \([iOS](https://github.com/RocketChat/Rocket.Chat.iOS/blob/develop/PLANNING.md) and [Android](https://github.com/RocketChat/Rocket.Chat.Android/blob/develop/PLANNING.md)\) for questions related to the way we plan our cycles.
+
+### How to choose something to work on
+
+Prior starting your wokr on your `To-do` issues. They're sorted by priority.
+
+### Community
+
+Everyone on the team is responsible for taking care of the community issues and questions. Everyone has the same responsibility and we value very much being clear and responsible to them. Our community is super important to the company.
+
+## Meetings
+
+We avoid meetings trying to do every discussion async. Unless something really requires our presence in real time, we'll prefer to use our forums to long discussions. If the discussion is too much back and forth we can schedule a call \(30min is preferred, 1h maximum\) to resolve the situation with a very clear goal.
+
+## Stores \(App Store and Google Play\)
+
+Every member of the team has the capability to submit new builds to the store and is encouraged to do so.
+
+## How to work with the Design Team
+
+Design Team is a shared team with all other teams of Rocket.Chat and to contact them in order to request assets, new designs or share ideas we have a channel to each specific platform or feature being developed. For iOS, we have `ios-design` channel and for Android team we have `android-design`.
+