...
Proposal | Status | Comments |
---|---|---|
1.Tidy up OFBiz Technical Framework or Kernel | In Progress | Sharan created diagrams based this proposal; The idea to start working has been raised several times on the mailing list but no work has yet been done of the proposal; Unsure of what is stopping progress on this |
2.Define and implement a process to manage code that has been cleaned out | Not Started | |
3. Tidy or Clean Up OFBiz Business Framework | Not Started | |
4. Implement OFBiz Application Documentation | In Progress | Sharan has asked for technical reviews of the Webhelp addon to see how this can be integrated into the trunk Ron and Sharan are also currently doing a DITA proof of concept for some basic OFBiz application documentation to see how it could work; (if successful then proposals will be made to the community to look at introducing it) |
5. Externqal Dependencies Refactoring | ||
6. Build a Project Roadmap / High Level Plan | Sharan drafted some details LINK; | |
7. Ensure Business Success Stories are Documented | In Progress | Wiki and mailing lists are currently being used to capture details; The new OFBiz website will probably consolidate this information a bit more for display etc |
8. Marketing the OFBiz Demo to Business End Users | Not Started | There have been several discussions on the mailing lists about this but no actual progress has been made. Julien's presentation on UX Design has highlighted some of the problems with the current user interface |
9. Build a set of Common Core Marketing Material | In Progress | Progress on this has been slow but the French team have provided a template that could be used. |
10. Housekeeping qnd Ongoing Maintenance | In Progress | T to Sharan Foga from Jacques Le Roux (? |
11. Establish a group of mini subject matter experts covering business and technical | Not Started | |
12. Work on q a Strategy to encourage more business users | In Progress | Website re-design and business based demo |
13. Look qt at developing a full testing strategy | Not Started | |
14. Actively Manage OFBiz Branding and Trademarks | In Progress | Quite a bit of work has been done on this over the year. We have consolidated the OFBiz logo and removed 'the Open For Business Project' text. We are also in the process of registering Apache OFBiz and OFBiz as trademarks |
...
- This could be a good opportunity to build closing closer links between our communities that be very beneficial to both.
- The Freemarker project is small so looking to build their community so anyone from OFBiz that has an interest in Freemarker would be welcome
Details of their mailing lists are as follows:
Developer list: dev@freemarker.incubator.apache.org. Subscribe, Unsubscribe (After clicking on these links, send the appearing empty mail as is.)
Commit and Jira notifications: notifications@freemarker.incubator.apache.org. Subscribe, Unsubscribe (After clicking on these links, send the appearing empty mail as is.)
...
Discussion Topic: Framework
...
- A key point from the discussion was that some work needed to start on the framework however small as it has been the subject of so many discussions that people were getting frustrated that no visible progress had been made.
- Look at fixing the exisiting framework problems by internal re-factoring
- Work towards delivering the "3" OFBiz products - OFBiz, OFBiz Framework + Data Model, OFBiz Business User Component (Limited Scope)
Discussion Topic: Migrating Minilang to Groovy
...
The business demo would have a very limited scope e;g; simple shop; 2-3 users, 5 products (physical goods only), 1 currency, 1 company, 2 customers, 2 suppliers
Sharan mentioned EZBiz a project that David Jones looked at while ago around producing a simple version of OFBiz for small businesses. It was thought that this might push the scope to be more complex than we initially need for the Business Demo
Conclusion:
- Contact Stannah re their offer of their bootstrap theme
- Draft High Level Requirements for Business Demo Scope (maybe looking at if anything can be reused from EZBiz....)
Discussion Topic: Release Strategy
Pierre raised a topic regarding the release strategy and the visibility it would give the community. Over the last few years since we changed the release naming we know that we will release one new branch per year (e.g 09.04, 10.04,11.04, etc) and also update releases for all our active branches. This means that we could plan our releases. We could put together a high level plan with an estimated month for each proposed release and then have the visibility about what could be included or not. Pierre wanted to see if ze it could manage our releases more efficiently meaning they could be available faster. This could help contibutors contributors and committers provide patches etc for specific releases.
...
The topic around automated testing was discussed. Jacopo mentioned the idea of 'configuration by exception' which could be easier to implement and run. E.g the entitydef could be used for implicit naming.
Conclusion:
? to Sharan Foga, Jacopo Cappellato from Jacques Le Roux "convention over configuration" is the same than "'configuration by exception", right?
Jacques Le Roux: yes they are the same!