debugger.html community team members help shepherd the community.They are here to help mentor newcomers, review pull requests, and facilitate issue discussions. They are a fantastic resource and genuinely friendly human beings.
- Responding to newcomer questions in Slack, and in Github.
- Helping select tasks for newcomers or other community members who are unsure of where to start.
- Reviewing Pull Requests, with a goal of 3 reviews per PR.
- Where possible, helping bring a PR to final acceptable state based on engineering review.
- Providing useful feedback in issues.
- Leading by example, Mozilla's Community Participation Guidelines ("CPG").
- Knowledge experts in how to take, and file report violations of the CPG. reports.
- Ensuring opportunity for all levels of contribution, confidence and background.
Active Community Members are visibly active in Slack and/or Github channels. We identify active members as being those who contributors and staff can most count on for a response within 2-3 days.
| (Ordered by first name) | |
|---|---|
 |
Anshul is an Applications Deveoper @ORacle, living in India. Ask Anshul about...
|
 |
Hubert is a software developer @ComparetheMarket, formerly @Oath living in the UK. Ask him about:
|
 |
Martin is a software developer @ComparetheMarket, formerly @Oath living in the UK. |
 |
Princiya is a software developer from Berlin. Ask her about:
|
 |
Tyler is a software developer @jobber living in Canada. Ask him about:
|
From time to time, and for many reasons that life gives us, one of our community team members may need reduce or pause their involvement for a while. We might still see them in Slack, or commenting in bugs, but we have no expectations of regular availability.
| (Ordered by first name) | |
|---|---|
 |
Wellington is a software developer from Salt Lake City. You can ask him about:
|
Emeritus status honors those who have dedicated time and talent to the Debugger project, but for many reasons have needed to step back. We want to make sure they remain as a visible part of Debugger's history and success.
- If you think we've missed someone, please ping someone on the staff team
| (Ordered by first name) | |
|---|---|
 |
Lukas led expertise in areas of:
|
 |
Irfan led expertise in areas of:
|
 |
Jaideep led expertise in areas of:
|
Anyone with interest, and personal goals for Debugger community, and with two months of active contribution is invited to join our team. Simply drop anyone on the staff or community team a message in Slack or email, and we'll get right back to you.
We embrace diversity and invite people from all backgrounds to get involved. We don't discriminate based on family status, gender, gender -identity, marital status, sexual orientation, sex, age, ability, race and/or ethnicity, national origin, socioeconomic status, religion, geographic location or any other dimension of diversity.
Once per year, we'll check in with our active, and members on break to ensure they are feeling supported, and activated for the coming months. If we do not hear back from members at this time, they will be transitioned to alumni role. The next review period, will be during the month of July 2019.