Page History

...

• 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 web part 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 shouldn't 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 hasn't 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.

...

• move the theme material from framework to theme
• User new web technologies (AngularJS, etc)
• Additional note from Nicolas Malin

apachecon for the imperious to create a common theme that will be 
receive all standard technical rendering and common screen to offer more 
powerful on theme.

I started with success a POC on my github 
https://github.com/nmalin/ApacheOFBiz/tree/common-theme and we will open 
a issue about this.
The works isn't finish but I'm sure we are on a good way :)

Write specifications to get consensus

...