Contributing to this repository

Coding guidelines

Please follow:

• Flutter-wide contributor guidelines.
• A2UI-specific guidelines.

Issue triage

Daily front-line triage

The function of the daily front-line triage is to determine if the issue is a critical issue that needs immediate response.

Until the genui package is marked as 1.0, an issue is critical if it blocks someone from compiling the package's code as part of their build process, or if previously advertised behavior breaks in surprising ways (a behavior change is not surprising if it was documented as part of the release of the package). We note that critical issues should be very rare.

We have a rotation which runs daily on business days. The responsibilities of the front-line triage include:

• Once a day, open the list of new issues which do not have front-line-handled label.
• Assess if this issue is critical (using the definition above). If so, assign P0 label and add the front-line-handled label. Then, ping the team chat, cc the Eng Manager, and share that a new P0 regression / issue has been identified. In addition, reply to the issue to acknowledge that we believe this is a P0 issue and thank the author for their time.
• If the issue is not critical and thus not a P0, then add the front-line-handled label to the issue. This signals that you have looked at the issue as part of front-line triage.
• If the issue looks legitimate, feel free to thank the author of the issue for their time. If a follow-up question is warranted, feel free to ask a follow-up question to help the second-line triage process.

Periodic second-line triage

Bi-weekly during the planning meeting

Check that existing issues are labeled and organized appropriately:

• Upgrade all assigned P2/P3 issues to P1, or unassign them.
• Set a milestone to all P0 and P1 issues.
• Add all projectless open issues to the "genui" project.

Weekly during the planning meeting

Triage issues ready for second-line review:

• Open the list of issues ready for second-line.
• For each issue in the list:
  • Do one of:
    • If we don't plan to fix the issue, close it with an explanation.
    • If we plan to fix the issue assign a priority label: P0, P1, P2, or P3. If you don't know which priority to assign, apply P2. If an issue is P0 or P1, add it to a milestone.
  • Add a label for second-line-triaged

At the end of a triage session, the untriaged issue list should be as close to empty as possible.

Internal information

For Google-internal information see go/a2ui-internal.