THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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 |
| 11. Establish a group of mini subject matter experts covering business and technical | Not Started | |
| 12. Work on q Strategy to encourage more business users | In Progress | Website re-design and business based demo |
| 13. Look qt 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 |
Conclusion:
- Although some progress has been made the general feeling was that things happen at a slower pace because of the commnunity interaction and discussion that needs to take place
...
- Some people are used to things being done quickly and may find this frustrating so we need to recognise this so that people do not become discouraged by the time it takes for things to get moving.
- We need to continue to follow up proposals regularly
Discussion Topic: Freemarker
Jacopo mentioned that Freemarker is now an incubating project at Apache. Their main committer is based in Budapest and he arranged to meet him informally. Jacopo mentioned that the Freemarker team are keen to build up a user community around their project and as OFBiz makes use of Freemarker, it ,might be interesting to subscribe to their mailing lists to understand what is happening. He also highlighted that the Freemarker team are very interested in getting feedback about their produt and are happy to get any suggestions for improvements or notifications of bugs that need to be fixed;
Conclusion:
- This could be a good opportunity to build closing links between our communities that be very beneficial to both.
Details of their mailing lists are as follow/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.)
...
After a brief disucussion this idea was very well supported. There was query as to whether the Framework + Data Model would (or could ) be a separate official release or whether it could be packaged as part of our existing release that could be easily separated.
Conclusion:
- 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.
Discussion Topic: Migrating Minilang to Groovy
...
Nicolas, Gil and Julien volunteered to do a Groovy Weekend where they would go through converting Minilang to Groovy.
Conclusion:
- The main conclusion was that Groovy is the preferred DSL but we
...
- will not reject contributions just because they include Minilang code
...
- We will start work on converting existing Minilang into Groovy
Discussion Topic: User Experience / Business User Demo
...
Discussion Topic: Automated TestsTest