Page History

...

1. Documentation Updates
2. Bug Fixes
3. Improvements
4. New Features
5. Testing a component and creating automated tests (JUnit, Selenium)

Documentation Updates

We have a lot work related to. We have done some work tidying up our Technical Documentation and next we would like to focus on the End User Documentation but help with any documentation is always welcome. We are consolidating all our documentation into the Wiki so will be moving documents from the End User Documetation workspace.Some of the key tasks we need help with are :

...

• Reviewing the list of open JIRA issues an assigning yourself to an open issue - (NOTE: Contributors can now assign themselves to JIra issues and this let's us know that you are working on them)
• Providing a patch for a JIRA issue (If you are not setup as a contributor you can still help us by providing a patch for a reported problem - just attach the patch to the issue and add a comment with the details)

Improvements

If you are working in a particular area and have ideas for improvements to existing functionality then please share your ideas and /or your patches.

• Create a JIRA for the improvement and make sure it is flagged as an 'Improvement'
• If you have a patch created that will implement the improvement then please attach it to the JIRA for testing and review

Testing:

• Review JIRA issues and confirm if the original reported issue still exists (we have a lot of issues that may now be out of date but havent been closed )
• Test patches that have been submitted by community members to fix issues (before we can commit these we need a thorough test that the patch works and doesnt break any existing functionality)

Bug Fixing

• Review JIRA an assign yourself to an open issue then look at providing a patch to fix the issue

Documentation

• Creating automated tests using JUnit or Selenium
  

New Features

If there are features that you want to include in OFBiz then please share your experience and ideas

• Create a JIRA for the new feature or wish and make sure it it flagged correctly
• If you have a patch or code that you would like to contribute then please attach it to the JIRA for testing and review

 Why not calling a day Community Day for OFBiz every quarter of the year?
Usually it can be in the 3rd week of the month, lets say Saturday.
This way we will be able to organize 4 big community day every year.
On this day every community member is invited to solely work on OFBiz bugs,
improvements, new features and testing for whole day together. It will be
completely optional to participate.
It should be possible to come together and work with all the available
tools around us for managing OFBiz i.e. mailing lists, JIRA, Confluence.
Just an idea I got, so thought to put it here as I read your email. How about these dates each quarter-
Q1 - Saturday March 21 2015
Q2 - Saturday June 20 2015
Q3 - Saturday September 19 2015
Q4 - Saturday December 19 2015
If community shows interest we can publish news on OFBiz site for the same.
On start of each quarter we can announce the dates and reminders for the
same in the beginning/middle every month. Reminders are needed so that
interested parties can plan their availability accordingly.
We can call vote for the same, this way we will be able to know if
community is interested in participating in such events.
There will be definitely time zone issue we will face but IMO we should
discuss possibilities. The date and the day is important irrespective of
the time zone. Different groups can be active on the same date and we'll
definitely achieve something.
As one community member dedicates a full day of work around 8 hours he may
work on-
1. Documentation Updates
2. Bug Fixes
3. Improvements
4. New Features
5. Testing a component and creating automated tests (JUnit, Selenium)
In general anything is done for the project on the dedicated day and we'll
be able take community
interaction and spirit to next level.