Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Suggestion was that the most important thing for the project is driving adoption. If this is true then what are the key blockers that stop user adoption of OFBiz? (the UI!)

Organise / setup teams from the community that focus on specific areas (e.g. workgroups) - this could really help progress

 

Strategy Ideas

If the UI was the main focus - what could the strategy look like

User Interface - have 2 versions of the UI, one very clean and simple, the other more advanced. (Our current UI could be the advanced one....?

Separate the webpart from the widgets

We have too many fields on one screen (many of them are not mandatory and are just included as optional). What if we slimmed down all the screens to have a sensible default UI for users. The UI could also be modifiable by service providers. Simplify the screens with defaults

Use Bootstrap / CSS / Angular

Isolate web related

Define a graphics charter to be used for the screens

Have a CSS convention

Remove web from the framework - it shouldnt be there!

 

Role of PMC

Discussion - re misconception of the role of PMC. Many people talk about 'the PMC should do something about....' or ' why hasnt the PMC put together a roadmap etc..' but it is the community that controls the direction of the project. Main role of PMC is to manage the release process, vote for committers / pmc members, handle security issues and manage the project brand. All other areas are community driven. PMC can take a more active role in other areas - but the community need to agree that they want the PMC to do this.

...