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

Adopt Backstage Community plugin standards #93

Open
t1agob opened this issue Apr 11, 2024 · 0 comments
Open

Adopt Backstage Community plugin standards #93

t1agob opened this issue Apr 11, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@t1agob
Copy link
Contributor

t1agob commented Apr 11, 2024

Is your feature request related to a problem? Please describe.
At this point we maintain separate packages in different repos which allows for additional flexibility but it requires a lot of effort in terms of maintenance due to release syncing and package dependencies.

Backstage recently announced their Community plugins repo which is going to host community plugins and also implements the standards and processes used in the main Backstage repo.

Describe the solution you'd like
I would like all the packages to be moved into a monorepo and follow the Backstage approach. This would still publish individual packages with their own version but would allow all contributors to the main Backstage repo to transparently contribute to our repo as it follows the same set of steps.

Describe alternatives you've considered
N/A

Additional context
This is not urgent but would reduce the amount of time it takes to do a release and ease the development process.

@t1agob t1agob added the enhancement New feature or request label Apr 11, 2024
@t1agob t1agob moved this to Under review in PagerDuty plugin for Backstage Apr 11, 2024
@t1agob t1agob moved this from Under review to Todo in PagerDuty plugin for Backstage Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant