Software improvement

3-Pipe-ready The feature has been incepted, the story map is ready, the mockups are there, the community has reached to a consent on how it’s going to be done. Then an epic is created on Github (with all the stories attached) and put into the “feature backlog” in ZenHub, and the post is moved in Discourse to that “pipe-ready” category. It is ready to be put into the delivery pipe by the product curation team. 4-In delivery The feature has been put into the delivery pipeline by the curation team, devs are working on it RIGHT NOW ! 2-Inception The most voted feature are then properly incepted, which means there is a product owner and a tech owner assigned to the feature, they do the story map and mockups, so the feature is ready to be put into github with all the stories attached. 5-Done The feature has been released, let’s celebrate ! If it’s not fully satisfying the need, you can open a new proposal to go further (Archived) 0- Wishlist (curation) 1-Voting Candidates Here are all the ideas, things we want to change, make better, new features we want to develop, sharing problems our users encounter, etc. AFTER we checked they are small enough and clear enough to vote on and prioritize. We want to make sure we understand what we prioritize. If they are not they should go back to “wishlist (curation)” section.
Topic Replies Activity
About the Software improvement category 1 March 20, 2015
WIKI - ordered delivery backlog (pipe-ready and in delivery)

This is the single source of truth for the priority list of features ready to be put in the pipe AND already in the pipe. The idea is to reorder in real time things that are in the pipe. We might have started something, …

4 January 18, 2019
A new admin interface for OFN 13 December 4, 2019
[FEAT] Multilingual 1 September 4, 2017
Invoices 3 November 25, 2019
Link from Order Confirmation to enterprises' own website 4 November 19, 2019
Hubs can ask their customers to validate their own terms and conditions 8 November 19, 2019
Display price per single unit on variants 3 November 19, 2019
Customers Page 1 December 7, 2015
Hubs can block shoppers / decide who accesses their private shop 19 November 18, 2019
[FEAT] Product Import 9 November 13, 2019
OFN Lite 1 February 6, 2018
Enable shopfront ordering by producer 1 December 19, 2017
Strong Customer Authentication (SCA) compliance 1 September 19, 2019
[FEAT] Subscriptions (standing orders) 1 August 25, 2017
[FEAT] Spree Upgrade 1 August 25, 2017
Report that isolates various enterprise fees 41 November 5, 2019
Possible new category name option for enterprise fees 2 October 30, 2019
Bancontact payment method 29 October 17, 2019
1. Hub's suppliers can prepare the invidual orders for the hub's customers 41 October 17, 2019
Enable quick capture of payments for a batch of orders 15 October 17, 2019
Enable to identify customer on orders view 22 October 17, 2019
A shopper can add products to an existing order 2 October 9, 2019
Making OFN an open directory for all the local/sustainable food ecosystem 17 September 27, 2019
Posting Webhooks from OFN 2 September 21, 2019
Document our API 14 September 16, 2019
How to offer Mangopay as a payment method to hubs? [Split Payments] 63 September 6, 2019
An enterprise can offer different prices for different type of customers (ex: members, wholesalers, etc.) 17 August 31, 2019
Users can apply fees to specific products/variants 3 August 31, 2019
Spec for new reports to facilitate using a train line for distribution 1 October 18, 2016