Thanks @Rachel and @Mario for those explanations.
biggest frustration with OFN feature development
I share Bethan’s frustration regarding “minor” issues not being addressed. It’s hard to explain to users why new features are popping up while problems that annoy them on a daily basis remain unresolved. I’m jumping ahead to future discussions here, but I’d like to be able to keep using AI to handle these issues.
I also previously regretted that the work done on the order cycles admin was left hanging without any explanation (at least to me). I often find that timelines are too long across the different phases of our workflow. This also leads to wasted time and mental load from having to dive back into old topics.
Up until now, I haven’t felt like I’ve been part of the development choices, except for those recently funded by CoopCircuits.
How do I wish to be involved
I’m very interested in getting involved in OFN’s evolution, prioritization, and the choice of features to develop, but I also know that this requires time I don’t always have. I tend to trust those making proposals, but since we have to prioritize, it would be helpful to have a summary for each feature request explaining concretely what new things it will allow us to do and the dev effort required to get there.
As mentioned before, I’m interested in taking on certain S3/S5 issues like I did recently and maybe contributing to certain features with the help of AI.
I’d like to see the API improve, and I’m interested in developing features—connected to other open-source tools—that aren’t intended to be integrated directly into OFN.
That said, I’d also like to highlight the efforts made over the last few months to keep us updated and informed on the roadmap’s progress.