Page History

...

Jacopo Capellato, Olivier Heintz, Nicolas Malin, Gil Portenseigne, Youssef Khaye, julien Julien Nicolas, Sharan Foga, Leila Mekika, Catherine Heintz, Bilgin Ibryam, Anahita Goljahani, Taher Alkhateeb,

...

Sometimes when a thread is posted or proposal made on the mailing list, there is no community feedback at all. Lack of feedback makes it very difficult for the person making the proposal or starting the discussion because they dont don't know whether the community are not interested, think it's a bad idea or silent because they agree. Over the last few months with all the work that has been done, lots of ideas and proposals have been made.

One response was that perhaps people are not responding because they dont don't think that they have the technical knowledge or expertise to respond or give an opinion.

...

Meeting at Apachecon is a great way to strengthen relationships and also collaborate. What about making use of meetups (real and virtual) to bring the community together. Many other ASF project have meetups but OFBiz doesnt doesn't - we tend to meetup at Apachecon and that's it. Could we look at organising some meetups, hackathons, traininng training etc. We have a lot of work so the meetups could be a way for a group of people to work together on a specific topic. Could also be used to do some outreach (recruit new members) as well as providing some valueable valuable info for existing community members.

...

There is a lot of work happening on the project at the moment and there is work at every level. You dont need to be an expert - there are tasks ranging from beginner / newcomer to experienced expert. If we could break down the tasks into the levels then it would be easier for people to pick. The original refactor list had easy / intemediate  intermediate  / expert ratings. Might be good to use the JIRA labels to flag certain JIRA as newcomer / beginner. (NEed Need to make sure that the experienced developers dont don't pick these up so there is nothing left for a real newcomer....)

...

• 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 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 shouldnt 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 hasnt 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 PMC members, handle security issues and manage the project brand. All other areas are community driven.

The community dont don't always realise or understand that PMC members mainly participate on the mailing lists as individuals and OFBiz contributors (and not as PMC members). The main area where being a PMC role is used or acknowledged is a formal vote. Individual PMC members (wearing the hat of an OFBiz contributor / committer and not as a PMC member) can and are encouraged to work / support other areas.

...

Multiple Projects

OFBiz could deliver more than one product. We could have more than one project active at the same time e.g

...

• move the theme material from framework to theme
• User new web technologies (angularjsAngularJS, etc)

Write specifications to get consensus

...