Recommended issues/epics for co-create
Goal
Have 3-5 issues/epics from every product group (except for the Fulfillment and Growth sections) that respective PMs consider the best opportunities for co-create.
Context
Co-create is a company wide initiative to build stronger relationships with some of our biggest and most active customers through collaborative innovation. The program consists of a week-long onsite collaboration for a GitLab engineer that helps building empathy for our users. Moreover, we aim to train the customer in how to contribute to GitLab with the hopes that they will become long-term contributors.
Until now customers led what they would like to work on and this resulted in many failed initiatives as the issues customers picked did not fit the direction, the strategy, the size or were needed more discovery and validation before moving them to delivery. We would like to find a different balance where product groups identify non-trivial issues that could still be targets for community contribution when supported for a week by a GitLab engineer, and that could provide the co-create customer follow-up issues to contribute in the same area of the codebase.
Without your support, our best option is to point customer to this issue search. Until now no customer showed any interest in the issues on this list. Customers typically offered issues that were larger in size and more complex. Issues we might not consider for quick win and - in the case of epics - for community contributions. This is your opportunity to have sizable work shipped in your area with the support of our customers.
Request
Every PM is asked to label 3-5 issues or epics (preferably epics) with the ~co-create
label if they consider the specific issue to be a great candidate for co-create.
Good candidates are
- the epic includes 1-2 issues that can be finished in under a week
- the epic allows for continued work following the co-seated week
- the issues are refined, validated, and would be ready for development if scheduled internally (including designs, etc).
Not-in-scope
Discussing if you can let an engineer into the program for a week is outside the scope of this issue. Your recommendations might never be picked by customers, or engineers from other teams might support the effort, or your engineers might be asked to support work for another product group. This discussion will happen once there is customer interest in co-creating an epic/issue.
Todo
Please, apply the label before 2024-09-05 and check your name when done:
- Magdalena Frankiewicz ~group::import_and_integrate
- Jeff Tucker ~group::personal_productivity
- Jeff Tucker ~group::design_system
- Gabe Weaver ~group::project_management
- Amanda Rueda ~group::product_planning
- Matthew Macfarlane groupknowledge
- Haim Snir groupoptimize
- Marie-Christine Babin ~group::source_code
- Kai Armstrong ~group::code_review
- Michelle Chen ~group::remote_development
- Dasha Adushkina ~group::editor_extensions
- Derek Ferguson ~group::code_creation
- Jackie Porter ~group::ci_platform
- Rutvik Shah ~group::pipeline_execution
- Dov Hershkovitch ~group::pipeline_authoring
- Darren Eastman grouprunner
- Gabriel Engel ~group::hosted_runners
- Tim Rizzi ~group::package_registry
- Tim Rizzi ~group::container_registry
- Connor Gilbert ~group::static_analysis
- Sara Meadzinger ~group::secret_detection
- Sara Meadzinger ~group::dynamic_analysis
- John Crowley ~group::composition_analysis
- Sarah Waldner ~group::vulnerability_research
- Viktor Nagy groupenvironments
- Hannah Sutor groupauthentication
- Joe Randazzo groupauthorization
- Grant Hickman ~group::security_policies
- Alana Bellucci ~group::threat_insights
- Ian Khor groupcompliance
- Joe Randazzo groupanti-abuse
- Jocelyn Eillis ~group::pipeline_security
- Tanuja Jayarama Raju ~group::analytics_instrumentation
- Lindsy Farina ~group::product_analytics
- Sacha Guyon ~group::observability
- Roger Woo ~group::cloud_connector
- Dilan Orrino ~group::distribution_build
- Dilan Orrino ~group::distribution_deploy
- Mark Wood ~group::gitaly_cluster
- Mark Wood ~group::gitaly_git
- Sampath Ranasinghe groupgeo
- Ben Venker ~group::global_search
- Sampath Ranasinghe groupdatabase
- Christina Lohr ~group::tenant_scale
- Sam Wiskow groupdelivery
- Sam Wiskow groupscalability
- Chris Balane ~group::dedicated
- Loryn Bortins ~group::switchboard
- Chris Balane (Acting) ~group::pubsec_services
- Kevin Chu groupmlops
- Kevin Chu groupdataops
- Pini Wietchner groupai framework
- Torsten Linz groupduo chat
- Susie Bitters groupai model validation
- Susie Bitters groupcustom models