Versions Compared

Key

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

...

What can we do as a community to encourage people to participate more on the mailing lists and in the discussions.?

  • Perhaps people Make sure that the tone of the discussions is friendly, open and welcoming of other opinions.
  • Be more patient.
  • Take the time to explain things in a friendly way to others that don't understand.
  • Use social media more  (blogs, twitter) - some people prefer other communication methods to mailing lists.

 

OFBiz Meetups

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 - we tend to meetup at Apachecon and that's it. Could we look at organising some meetups, hackathons, traininng 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 info for existing community members.

Find out if there is community interest in doing a specific OFBiz related event in India and /or Europe.

 

Project Work

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 intemediate  / expert ratings. Might be good to use the JIRA labels to flag certain JIRA as newcomer / beginner. (NEed to make sure that the experienced developers dont pick these up so there is nothing left for a real newcomer....)

...

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.

...

Write specifications to get consensus