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

Support and ownership of apps runtime #759

Open
martinothamar opened this issue Sep 10, 2024 · 0 comments
Open

Support and ownership of apps runtime #759

martinothamar opened this issue Sep 10, 2024 · 0 comments
Labels
Epic status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@martinothamar
Copy link
Contributor

Description

This is an analysis issue regarding support of our users and our ownership of the apps runtime, and how we can improve these aspects from an operational/team perspective. There are a couple of pain points that are all at least a little related

  • Development process is slow at times when features require work across systems (e.g. apps & Storage). This also affects the quality of our work in other systems such as Storage, as we are not very familiar with standards, processes, etc
  • We are not proactive when it comes to bugs and other operational issues, which means there are latent and common bugs that cause friction between us and our users and other teams on the platform
  • We have no insight or access to instance data for debugging purposes, and often have to rely on service owners or team Core to provide additional information
  • Our team, due to us working in the center of a lot of things (the runtime tying a lot of things together), usually ends up being involved in a lot of different activities that span the entire platform. This effect is also seen in support, where a lot of the time we end up just being routers for support tickets

These pain points may seem loosely related, and perhaps this issue should be broken up, but I think they all factor into how we perform as a team and how well we serve our users and other teams on the platform

In scope

TBD

Out of scope

TBD

Additional Information

TBD

Analysis

TBD

Conclusion

TBD

@martinothamar martinothamar added Epic status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
Status: 📈 Todo
Development

No branches or pull requests

1 participant