In both the Catalog SIG and Adoption SIG there have been discussions around the need for a more general Backstage framework SIG. To keep overhead in check we're proposing to close down the Catalog SIG and instead fold it into a new Framework SIG.
The description of the new SIG is a little bit more oriented towards what it really is - a place for discussion around the Backstage framework, rather than a group with direct ownership. That's instead handled through our governance and project areas.
An idea that I'm suggesting we try out is that in addition to keeping an open agenda for topics, we also spend any remaining meeting time towards pull request reviews. This could be reviews that are suggested by members of the community, but also PRs picked out during the meeting for discussion with the maintainers. I'm hoping that this can both help speed up pull request reviews, as well as give insight into the review process and open up for further discussion.
In both the Catalog SIG and Adoption SIG there have been discussions around the need for a more general Backstage framework SIG. To keep overhead in check we're proposing to close down the Catalog SIG and instead fold it into a new Framework SIG.
The description of the new SIG is a little bit more oriented towards what it really is - a place for discussion around the Backstage framework, rather than a group with direct ownership. That's instead handled through our governance and project areas.
An idea that I'm suggesting we try out is that in addition to keeping an open agenda for topics, we also spend any remaining meeting time towards pull request reviews. This could be reviews that are suggested by members of the community, but also PRs picked out during the meeting for discussion with the maintainers. I'm hoping that this can both help speed up pull request reviews, as well as give insight into the review process and open up for further discussion.