Confirm
2,177
edits
Changes
no edit summary
* Maintain the reporting tools
* When: Weekly on Wednesdays at 16:00 UTC (08:00 PST, 11:00 EST, 18:00 EET)
* Where: [https://mozilla.zoom.us/j/110819485 Zoom ID 110-819-485]
* Notes: [https://docs.google.com/document/d/1kHHimZH65Rg_Nzx_JfyPqeXL6ONTse0nG2t9Nkv4eOY/edit Google Docs]
=== Calendar =Onboarding ==There's a Performance [https://calendar.google.com/calendar/embed?src=mozilla.com_9bk5f2rqdeuip38jbeld84kpqc%40group.calendar.google.com shared calendar] ([https://calendar.google.com/calendar/ical/mozilla.com_9bk5f2rqdeuip38jbeld84kpqc%40group.calendar.google.com/public/basic.ics iCal]), which is primarily used for PTO. === PTO ===Add any PTO to the shared calendar (see above) so the team You are aware. === Groups ===Feel free to sign up encouraged to improve the following groups, and post to them when you have something to share or questions to ask.* [https://groups.google.com/a/mozilla.com/forum/#!forum/perftest perftest] is invite only, and used for team communications and setting up test accounts* [https://groups.google.com/a/mozilla.com/forum/#!forum/performance performance] is for general discussion and announcements* [https://groups.google.com/a/mozilla.com/forum/#!forum/perfteam perfteam groupOnboarding|onboarding page] is for the performance engineering team* [https://groups.google.com/a/mozilla.com/forum/#!forum/perf-sheriffs perf-sheriffs] is for discussions related to performance sheriffing* [https://groups.google.com/a/mozilla.com/forum/#!forum/perftest-alerts perftest-alerts] is for alerts related to performance tests* [https://groups.google.com/forum/#!forum/pi-monitoring pi-monitoring] is used to share regression summaries === Credentials ===There's a shared [https://1password.com/ 1Password] vault for credentials that If you may need to access. Please submit a request for 1Password from [https://mozilla.service-now.com/sp?id=sc_cat_item&sys_id=94530ae813805b007b5450782244b009&sysparm_category=018c96e84ff35200f004ef6d0210c7b4 The Hub]. Once you have an account and the software set up (available on iOSask questions that are not already covered, Android, Windows, macOS) you can be added you to please update the team vault. === Additional equipment ===You may need additional hardware such as mobile devices, laptops, etc. You can request this equipment from [https://mozilla.service-now.com/sp The Hub]. === GitHub ===We have a [https://github.com/orgs/mozilla/teams/fxperftest GitHub team] for simplifying access to repositories. All team members page so that belong to the [https://github.com/orgs/mozilla Mozilla organisation] should be added to this team as maintainers. Other team members will need to be manually granted access to individual repositories as needed. === Shared folder ===We have a [https://drive.google.com/drive/u/0/folders/1EyeiuJYmivvY83BCicqeR4-59HRTU-ll shared folder] in Google Drive. === Sheriffing ===Performance sheriffs will need to complete the following: * Request an LDAP account* Request commit access:** Level 1: {{bug|1398609}}** Level 3: {{bug|1509284}} * Request access to Treeherder sheriff group: {{bug|1506882}}* Training (ranked)* Join the [https://groups.google.com/next person has a/mozilla.com/forum/#!forum/perf-sheriffs perf-sheriffs] Google Group === Review policy ===When you push a commit up for review, you should use the following syntax to request review from the [https://phabricator.services.mozilla.com/tag/perftest-reviewers/ perftest review group]: <code>r=#perftest</code> A single r+ from one reviewer is required for the patch to be allowed to be sent off for integration. More reviewers can pitch in on the same review, and Lando will in this case automatically rewrite the commit message to show who was involved signing off the patch, for example: <code>Bug 1546611 - Fix "None" checks when validating test manifests; r=perftest,rwood</code> When you occasionally you have to single out individuals for specific topic expertise, you add an exclamation mark behind the nickname: <code>r=#perftest,rwood!</code> This will add the patch to the shared review queue, but also block the review from landing pending Rob's approval. Requested changes by other reviewers will also block the reviewbetter onboarding experience.
== Task Workflow ==
