I hope I am not too late to the party! Thanks for the ping @tschumilas and @Kirsten. My main question in this area is around stuff that most instances might not need/want but a potentially influential/large/well-funded user, possibly because of the way they are already doing business on another platform, wants to have (and is willing to fund the development of) as a prerequisite to coming on board with OFN. Examples would be the stupid non-metric weights and measures, which no one has asked for yet but may, and things like an item “countdown” which would be especially useful in bulk buying (like how many more kilos of bananas need to be bought before it makes up a case - we have a user who really really wants that to the point where they may go elsewhere if they don’t see that there is a plan for it).
For us in the US, who are still trying to lure folks over to OFN, the answer to many requests is either “it’s on the list but not yet scheduled” or something that translates as “we can put it on the list and it will get prioritized in some months but there are a lot of things ahead of it and likely it will stay on the list if it only matters to your business model or just to our instance so your choice is to adapt if you plan on using OFN the way it is even if you have $25k to pay for this functionality to be developed.”
I am mostly interested in the process for doing things that really only matter to one instance for now, like the changes that are legally required to invoices in France. I can see that some development is critical for one instance and irrelevant to everyone else - what is the process around this? How do we balance being a slow moving monolith on one extreme and utter chaos on the other?