Page History

...

• Future tasks or requests for improvements are also managed through JIRA

Marketing

No real marketing strategy in place

Need to aim to attract more business users 

External Dependencies

There was a brief discussion about external dependencies (i.e. on other projects or functionality) and how they have been implemented in OFBiz. The aim is to have a flexible framework that works with the Apache release process. Any external product needs to be maintained and when a release is made the project PMC are responsible for signing the release which ensures that any external dependencies willl be correctly integrated and maintained for the release.

We currently have cases where some external products should not have been implemented to form part of release but can be made available if users want to integrate them into an OFBiz release.

Technical vs. Business Knowledge

A key point was raised that some of the people classed as technical (i.e developers or integrators) in the project also have very solid business experience too. We need to capture information about who knows about which applications and business processes so that we can encourage them to become part of our team of 'mini subject matter experts'. 

Draft Proposals

These proposals are to be raised for on the mailing lists for community discussion and feedback. They will only be implemented if the community consensus is recevied/

1. Proposal: Tidy up OFBiz Technical Framework or "kernel"

   1. e.g identify what needs to be tidied up and assign the work out to be done
      
      

2. Proposal: Define and implement a process to manage the code that has been cleaned out

   1. eg to a sandbox location so could be used by users who want to pick it up and use
      
      

3. Proposal: Tidy or Clean up OFBiz Business Framework

   1.  (e.g. ensure business processes have a use case to describe the process and that can be used for validation)
      
      

4. Proposal: Implement OFBiz in Application Documentation

   1. We have been using docbook but two other proposals mentioned
   2. Idea 1: Use SVNPUB: This is committer controlled but may be able to switch to setup a business user expert with write access. This means that the "mini subject matter experts" could easier maintain their specific areas.
   3. Idea 2: Wikipedia style documentation where a page linked within the OFBiz application page (e.g. using the '?') will link to the wiki. This is more open and non committer controlled. Means more people can contribute
      
      

5. Proposal: External Dependencies Refactoring

   1. specific workstream on refactoring external dependencies

6. Proposal: Build a Project Roadmap / High level plan

   1. This will be used to show details of releases and how they are supported, details of work in development, updates planned.
   2. We need to look at tools available eg. JIRA has options to do planning and roadmap, also look for Roadmap and planning info on the Wiki as may be able to collate
      
      

7. Proposal: Ensure Business Success stories are documented

   1. This is valuable information for potential users. We could ask users  to add their stories and also get them to list the applications used / implemented.
   2. Existing policy is that there should be no direct links from OFBiz website main pages so need to use the wiki. Investigate whether integraters are willing to share their client links and stories.
      
      

8. Proposal: Marketing

   OFBiz - prepare

   the OFBiz Demo to Business End Users

   1. Prepare an end user demo that can be based on roles (e.g accountant, HR manager, Order Clerk, Warehouse Manager etc).
   2. Link to user stories that can have a script or supporting documentation (e.g currently on main page there are no instructions about how to login to the demo just in case you are thrown out.
   3. Also default user if flexadmin which doesnt have all the permissions for all applications).
      
      

9. Proposal: Build a set of Common Core OFBiz Marketing Material

   -

   1. Put together some standard OFBiz marketing information that all integrators / users have access to.
   2. Integrators can then adapt it to suit their needs if required. Information could be white papers around supported industries etc.

   Need

   2. Will need to define what tool could be used to prepare the material as it needs to be accessible to a common audience. This is important as everyone will need to be able to edit it!
      
      

10. Proposal: Housekeeping and Ongoing Maintenance

    1.  eg
    Maintenance - eg
    1. . Tomcat etc. Need to keep a watching brief on external products that are directly used by OFBiz and prepare a plan of when to integrate them
       
       

11. Proposal: Establish a group of  "mini subject matter experts"

    both

    covering business and technical

    (

    1. i.e. dont have to be both but can be

    )

    2. . Identify contributors and knowledge. Can refer to these people regarding their specific area
       
       

12. Proposal: Work on a strategy to encourage more business users

13. Proposal: Look at

    the

    developing a full testing strategy

    - unit

    1. Unit testing in isolation is not enough. We need to ensure there is an full end to end test flow
       
       

14. Proposal: Actively Managem OFBiz branding and trademarks

    - need

    1. Need to review the process and contact sites that may be infringing

    this

    1. on the OFBiz brand
       
       

Actions