Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create an intake process and SLA #233

Closed
schuylermartin45 opened this issue May 11, 2023 · 1 comment
Closed

Create an intake process and SLA #233

schuylermartin45 opened this issue May 11, 2023 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@schuylermartin45
Copy link
Collaborator

I anticipate the linter will become a major component of future automated build pipelines. In anticipation of that day, I think we need to formalize communication and expectations with our stakeholders (for now, that would be the members of our team who build packages).

An intake process formalizes expectations with stakeholders. I anticipate a future in which the people responsible for the linter may not be as familiar with package building as other members of the team. Providing "rules of engagement" should mitigate confusion and set expectations. I believe this "we only build packages" mantra does not scale and needs to end in favor of a future with better specialization and greater lines of communication between expertise.

An SLA, coupled with increases to unit testing ( #230 ) ensures we have a process to reduce downtime in the event the linter starts operating in a unhealthy state.

@schuylermartin45 schuylermartin45 added the documentation Improvements or additions to documentation label May 11, 2023
@schuylermartin45
Copy link
Collaborator Author

Stakeholders should contact the Packaging Automation and Tooling Team for the time being. We will develop an SLA and rules of engagement as we scale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant