Le 14/02/2020 à 16:46, Nicolas Malin a écrit :
Hi,
On 08/02/2020 14:25, Michael Brohl wrote:
Hi all,
[...]
A good roadmap would include a mix of core development tasks (making the framework better, new features in the applications and bugfixes). I can
image a roadmap with certain goals might also motivate more contributors to work together on announced features and finish a release. It could also
help to better organize community days and help organizing the development of long term changes (e.g. changes for a new deployment strategy, huge
refactorings etc.).
What do you think?
I'll always stay in favor of a fixed time release branchas rules like musical
paper who encourages us to move forward.
Perhaps we willincrease the space between each release to two years,which seems
to be more realistic.
On the roadmap concept, personally I don't believe in it, except forgiving us a good reason not to follow it. I'm being sarcastic but I will
explain. We mostly commit to OFBiz some problematic or improvement that we realized from production deployment after a process to ensure they will
be a real addedvalue for the community.
Set a roadmap to define the next OFBiz release implythat current projects(I talk about customer projectsfrom each society) follow or match the
roadmap and intrinsically we should achieve a goal to create an official release (that can be never done).
I more attachedto the principle concept (or golden rules, nameitas you wish) that will allowto see if a commit would not be in contradiction with
them. Some principles: need to be extensible by plugins, move old language code to up to date code, respect coding rules, make it simple, ...
This open more space for contributions while alsodefininga minima the way that
we wish to follow, timed by releases.
Just a last point, Sharan has been started a quality works on OFBiz roadmap [1] that we never continue. I talk about that not as reproach but more
as aninteresting try that unfortunately didn't match with how we works day-to-day
Nicolas
[1] https://cwiki.apache.org/confluence/display/OFBIZ/Draft+Framework+Roadmap
+1 here a list of attempts in the past:
https://cwiki.apache.org/confluence/display/OFBIZ/4.x+Proposed+Roadmap+Items
https://cwiki.apache.org/confluence/display/OFBIZ/Sharan+-+Documentation+WIP
(see children pages in the left panel)
https://cwiki.apache.org/confluence/display/OFBIZ/New+Features+Roadmap+-+Living+Document
If we would really want to do that I think the later is the simplest realistic one. But I believe, it would be wasted time again and I know what I'm
talking about.
We need to be realistic. It's impossible to "manage" an open source project, at
least one like OFBiz. I think Nicolas explained very well why...
Jacques
