Meta: Possible Ecosystem Work
This is a meta issue that allows us to track work that could fall within the ~"group::ecosystem" backlog. Because of the way scoped labels work, issues will tend to get labeled with the stage that they are most closely related to (and rightly so). Because ~"group::ecosystem" 's work falls across multiple stages, marking an issue as related to this one allows for the stage/group label to remain for the time being, while giving us a way to note that it's a possible candidate for the ~"group::ecosystem" team to work on.
What issues should the Stages work on themselves?
Individual stages should be focused on creating the best DevOps tools in the market, and thus the work done by the stages should be directly contributive to the GitLab Product Vision. A litmus test for this is: “If we were the only player in the market, would we want this feature in our product?”
What issues does Ecosystem work on?
As a part of Enablement, Ecosystem works on issues that are not directly contributive to the GitLab Product Vision, but do allow a larger audience of users to use it. The goal of Ecosystem is to expand the reach of our products by removing integration-based roadblocks to adoption, where customers are unable to use GitLab because of other 3rd party software dependencies they have.
What about grey areas?
If it’s hard to categorize whether work should fall in the Stage or in Ecosystem, it’s likely that the work needs to be chunked into smaller pieces that are easier to classify. However, in the case that it’s difficult to determine what category a particular issue or feature should fall in, that determination will be made by the Product Leadership team.