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
-
Bye bye spree (@luisramos0) Done Done Done
In play
-
Mobile shopping improvements (@Erioldoesdesign + @maikel) - Final tweaks on shopfront being worked on by @apb ikel to continue with the upcoming epic.
-
Rails Upgrade 4.1 and Rails Upgrade 4.2 (@Matt-Yorkley)
Planned to be merged this week for inclusion in next weeks release. -
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.
-
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
-
Platform T&Cs for Shoppers - two tiny epics (@lin_d_hop + X?)
-
Refactoring Adjustments (@Matt-Yorkley + ??) Refactoring of adjustments now they don’t live in Spree #6402
In Inception
-
Consumer price comparison / Unit price (@Jana + @Erioldoesdesign + @sauloperez ) - final round of design feedback done, all design actions have been completed and update posted on discourse. Waiting for tech feedback / approval to enter the delivery pipe @sauloperez to have a look and help break down into tasks
-
Tax Reports (@lin_d_hop + @Rachel + @Matt-Yorkley) - Version 2 of the tax report is out for community review! Some input received which needs to be discussed further to understand if this is going through another round of inception or if the work is a significantly useful as is.
Ready for Inception
-
History of invoice changes (@Rachel + ?) - needs a tech lead and waiting for review and re-inception. Leave until tech lead is picking it up.
-
Invoice number system (@Rachel + ?) - waiting for re-inception.
-
Backoffice UI Uplift - Some bits In Review, others In Design. We’re waiting on @Kirsten’s return to drive this forward.
Backlog
-
Improved reporting (@lin_d_hop + @Rachel + @Matt-Yorkley) This is bigger piece of work of which we will be picking off areas of priority.
-
Networking pt 2 The continuation of this work will wait until @Mario returns
Discussion
-
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
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 