Open push access to Alaska engineers

[blackfalcon]

The problem

It has been communicated that most engineers prefer to have push access versus having to fork a repo.

The proposal

While technical constraints keep us from adding all Alaska Github users to the open-source org, the proposal is similar to what we have proposed in the past with trusted contributors.

Within the AlaskaAirlines security group, we have implemented a parent container for users that are not part of the core Auro team and can have write access. Every child group (based on product group) placed within that parent will assume those same access rights. This non-core-Auro team member is assigned to all repos.

Users are not limited to that assigned role. Given the level of involvement and growing knowledge of the platform, users can be promoted to maintainer if not administrator of the project.

Currently, individuals who have identified themselves as interested in supporting the platform in the past have already been assigned write access to all the repos. For anyone else who is interested, simply reach out to anyone on the Auro core team and we will immediately grant you write access to all repos.

Expected outcomes

It has been communicated that having to fork a repo has dissuaded individuals from contributing to Auro and subsequently proposed that granting write access to more people would encourage more to contribute to the platform.

While we have no plans to evaluate an OKR on this work, we do hope and encourage those who do have write access to the platform to actively engage with the Auro team and support the efforts with contributions.

All contributors are encouraged to abide by Auro's contributing guidelines, security policy, and code of conduct.