Product curation meeting #27 notes - 30 November 2020

Processes Update

Product Curation Meetings use the Inception Pipe board to discuss and (re)prioritise tasks of inception work

How the pipe is related:

The “Ready for Inception” column reflects the “Next Up Section” in the Product Curation Discourse Post
→ Tasks copied, prioritized from top to bottom. This also helps so see better which of those topics are already in progress and how far

“Needs Inception” column: here things are parked that are not yet prioritized and need inception work
→ Those things (identified problems/feature candidates) can come from discussions in Product Circle, Product Curation, Instance Managers, Research Insights, Papercuts, “All the things”, Wishlist Items, Feature Requests…

→ Regular grooming of this column in Product Curation Meetings, to feed the Ready for Inception column and prioritize inception work

Documentation for community:
We keep Discourse Posts, and break down the "Next Up"Section in

  • "In Inception
  • “Ready for Inception”

Current view of roadmap

Finished since last meeting

  1. Bye bye spree (@luisramos0) Done Done Done :tada:

In play

  1. Mobile shopping improvements (@Erioldoesdesign + @maikel) - Final tweaks on shopfront being worked on by @apb ikel to continue with the upcoming epic.

  2. Rails Upgrade 4.1 and Rails Upgrade 4.2 (@Matt-Yorkley)
    Planned to be merged this week for inclusion in next weeks release.

  3. KPIs & Metabase (@Jana + @sauloperez) - This work is now separate from the global metrics tasks. There is an open question around how queries are picked up by dev team or if this should be done within a tech support and sysadmin pipe. Action for @sauloperez @lin_d_hop @Jana and @Rachel to think about a next steps here.

  4. Stripe SCA compliance - Subscriptions (@lin_d_hop + @apb ) - Lynne and Andy to have a conversation to understand about what parts can be deployed independently.

Next Up

Ready To Go

In Inception

Ready for Inception



  • Governance - Product Curation is the process in which we combine our priorities around tech debt, features, and processes. Right now its difficult to combine all the things and include the community. There was a good discussion about the complications and raising the point that it is a significant governance issue that instances often do not feel heard. @konrad @Jana @Rachel @Erioldoesdesign to continue this discussion.

  • Security discussions: Some of this work has been deployed. Blocked by monitoring on smaller instances to see what kind of impact it has. Proposal to include CA and US in current monitoring

  • Sysadmin discussions: Who is in and who is out on global sysadmin became a follow on conversation to this. This relates to this conversation here.

  • Sysadmin and tech support workstream: Action for @sauloperez @lin_d_hop @Jana and @Rachel to think about a next steps here.

  • Automated testing: @filipefurtado has been working on this in the background removing release testing manual tasks and replacing them with automated tasks. An epic is being populated within #4333. @filipefurtado is leading on this but will require developers as well.

  • User balance calculations - #6366 . We’re going to take the task of unifying balances across the system for consistency.

  • Matt to increase his hours and take on the adjustments work :tada: He wan’t to test out 30hrs for 1-2 months and see how this goes. Maybe he’ll continue at this amount of contribution :pray: