We are the A-Team, focused on enhancing productivity for OpenINF’s engineering teams. Our experts develop and support tools and automation to achieve this goal. We are constantly working to improve this repository, so please feel free to contribute if you notice any omissions or errors.
[!NOTE] As of 2023-02-14, the Engineering Productivity group, a.k.a. the A-Team, is no longer a discrete team. Its operations are split between the new Product Integrity WG meta-team and Engineering Operations. For now, many discussions around the test and automation work that was formerly under Engineering Productivity may continue in our Matrix channel.
\text{Productivity} \equiv \text{Output} : \text{Input}
Fig. 1 | Equation expressing the “productivity
ratio” as the output divided by the input denoted using a colon (:
) notation.
🧠 Learn more…
After baseline productivity is characterized, temporal analysis and comparison of this measure enables inference regarding productivity gains, losses, or stagnation. Information systems thus facilitate longitudinal tracking of productivity, providing insight into the impact of interventions and exogenous factors on operational efficiency.
Maximizing productivity is an essential goal across industries and disciplines. Elucidating the determinants of productivity through rigorous measurement and evidence-based investigation is critical for informing managerial strategy and resource allocation. The study of productivity therefore constitutes a vital research area with implications for technological progress, economic growth, and organizational success.
\text{Productivity (in percent)} \equiv \frac{\text{Output}}{\text{Input}} \times 100
Fig. 2 | Equation expressing the “productivity ratio” (in percent)
as the output divided by the input (in fractional form), multiplied by 100
.
Welcome to the homepage of the Engineering Productivity WG (called “the A-Team” for nostalgic reasons). Although previously formally known as the Automation and Tools team, we often still use the nickname “A-Team”, and you’ll see A-Team references scattered throughout our codebases. Although we are proud to now finally be recognized as an officially chartered WG (Working Group), we still prefer the “A-Team” nickname from our humble beginnings. Please preserve all instances of this esoteric usage you may find while spelunking in our codebases by leaving them as-is and untouched.
We’re a group of programmers who develop and support a wide range of services, tools, and automation that serve the engineering teams at OpenINF, with a specific focus on work that increases the productivity of those teams.
We are part of the Release & Productivity meta-team.
The Engineering Productivity WG is a diverse group of engineers passionate about improving engineering quality and productivity at OpenINF. We are experts in various coding languages and tools and are always looking for new ways to make engineering more efficient and effective. We work with others in a responsive and agile manner, striving to be a model of open development. We create, maintain, and extend a diverse array of sustainable tools and systems that derive and deliver information on the quality of OpenINF’s products and enhance the impact and effectiveness of the OpenINF community.
We’re a friendly bunch of people happy to help you; we want to hear about your ideas and problems. Please let us know what you think we can do to help you work more productively.
See our team rosters below for a list of folks on our “A-Team”…
Name | Organization(s) | Engineering Role | Status | GitHub Handle |
---|---|---|---|---|
Derek Lewis | OpenINF × FontVault & AMPHTML | Development | highly particip. | @DerekNonGeneric |
👻 | OpenINF × FontVault (opt., but pref.) | Development | fillable (you?) | @ghost |
Milena Mitrovic | OpenINF × FontVault | Design / UI / UX | ltd. avail. | @EmMitrovic |
👻 | OpenINF × FontVault (opt., but pref.) | Design / UI / UX | fillable (you?) | @ghost |
Jorge Bucaran | OpenINF × Hyperapp | Quality Assurance (QA) | highly particip. | @jorgebucaran |
Sora Morimoto | OpenINF × OCaml & TC39 | Prod. Mgmt. (PM) | min. avail. | @smorimoto |
👻 | OpenINF | Prod. Ownership (PO) | fillable (you?) | @ghost |
Name | Organization | Engineering Role | Updates URL |
---|---|---|---|
Bard | Google AI | Generative Model | https://bard.google.com/updates |
ChatGPT | OpenAI | Generative Model | https://help.openai.com/en/articles/6825453-chatgpt-release-notes |
Claude | Anthropic | Generative Model | https://www.anthropic.com/index?subjects=claude |
We work on various things that vary from quarter to quarter, but we encourage other teams to learn more by browsing the details below as we set up new systems. The information here represents the general scope and direction of our current and ongoing activities taking place between our developing camps.
🧠 Learn more…
This section is still in draft stage.
All information may be incomplete, inaccurate, outdated, or even completely wrong. Refer to #8 to track progress…
- Autoland
- Treeherder/Perfherder
- TestInformant
- web-platform-tests
- CI integration (openinfbot/Taskcluster),
- JS specification (TC39 AssertionError Proposal)
- new test harnesses as needed
- mach
- GitHub Actions
- code coverage
We set and deliver quarterly goals, which is usually an excellent place to see what we’re up to.
See the Project Central wiki page for a list of projects we own.
Every other Tuesday, we have a fortnightly meeting that lets out before noon U.S. Pacific Time. We typically discuss status, and new projects, have demonstrations of the latest tools & features, and sometimes even engage in bikeshedding.
[!NOTE] These regularly scheduled A-Team team meetings are not networking events; however, we will occasionally host invited experts from the community to make presentations relevant to our objectives and likely relevant to other community members as well.
All are welcome; please join us!
Tentative & Historical, 2023
Date | Day of Week | Time | Event Name |
---|---|---|---|
2023-02-14 | Tuesday | 12pm PST | The New Age of AI: A Convo with Google DeepMind (formerly Brain) |
2023-04-19 | Wednesday | 12pm PDT |
ICU4X Virtual Open House * |
2023-10-12 | Thursday | 1am PDT | |
2023-10-13 | Friday | 1am PDT | |
2023-10-17 | Tuesday |
11am–noon PDT ⏳⧉ |
|
noon–1pm PDT ⏳⧉ |
A-Team Working Session | ||
2023-10-24 | Tuesday |
9am–5pm PDT ⏳⧉ |
|
2023-10-25 | Wednesday | 3pm PDT | |
2023-10-26 | Thursday | 3pm PDT | |
2023-10-30 | Monday |
5am–6am PDT ⏳⧉ |
OCaml.org Community Meeting 🐫 |
2023-10-31 | Tuesday | TBD | Halloween 🎃 |
2023-11-07 | Tuesday | 12pm PST | |
2023-11-08 | Wednesday | 12pm PST | |
2023-11-13 | Monday |
10am–11am PST ⏳⧉ |
OCaml.org Community Meeting 🐫 |
2023-11-27 | Monday |
10am–11am PST ⏳⧉ |
OCaml.org Community Meeting 🐫 |
2023-11-21 | Tuesday | 5am PST |
A-Team Fortnightly Team Meeting # |
2023-12-05 | Tuesday | 5am PST |
A-Team Fortnightly Team Meeting # |
2023-12-19 | Tuesday | 5am PST |
A-Team Fortnightly Team Meeting # |
Table 3 | The OpenINF A-Team events — both hosted & unhosted — since being re-imagined for our New Age of AI (i.e., ever-benevolence).
We love contributors! We see community members as one of the keys to our success and actively encourage their contributions. Working on the tooling, automation, testing, and build systems at OpenINF is a fantastic introduction to OpenINF development. There are two great ways to help: joining an existing project or taking on one of our starter projects to help rev up to speed.
-
Longer-running, scoped contributing opportunities with definite goals, mentors, and timelines
-
Look over our list and see if there is anything that you’d like to help with
If you have questions or want to sign up, please find us on Matrix or X (formerly Twitter).
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. If for whatever reason you spot something to fix but cannot patch it yourself, please open an issue.
This project is licensed under either of
at your option.
The SPDX license identifier for this project is
MIT OR Apache-2.0
.
Portions of this document are reproduced from work created and shared by Mozilla and used according to terms described in CC BY-SA 3.0.
Except as otherwise noted, this content is published under CC BY 4.0.