I don't agree that each patch needs to be a nearly complete solution. I have two
features I've been working on for a while now and I've broken them up into
smaller pieces - each one is its own Jira issue. Some of those patches have made
their way into the project, some have not.
Having it broken up that way allows others to work on bits of the project.
Committers have the option to commit the portions they feel are useful. The
remainder can be downloaded and applied to local copies.
Chris Howe wrote:
The only real *problem* with using jira for this is
that each patch needs to be a nearly complete solution
that is at that moment ready to be integrated into
OFBiz. There are many features/mini projects that
fall outside of that and are incrementally improved
upon (ie google checkout integration). Additionally,
it puts a bit of burden on those maintaining JIRA
(removing/renaming patches, etc). JIRA is probably
still an excellent location to discuss the
feature/mini project, it's just not as giving to
collaboratively create a feature.
--- Adrian Crum <[EMAIL PROTECTED]> wrote:
Why wouldn't you use Jira for this? I have found
Jira to be a useful tool to
gather comments and submit patches. Even if the
patches aren't put into the
project, they can still be downloaded and applied to
local copies.
Daniel Kunkel wrote:
Hi
I wonder how hard it would be to setup a svn
playground for non
*approved* ofbiz committers.
I've heard about more than one project that has
been started by an OFBiz
users
that never sees the lights of day, even though
there are probably others
that
would use it to jump start their efforts. In case
that didn't make
since,
consider the recent efforts to implement a google
shopping cart module.
In addition, a probably would be a great proving
ground to determine who
is appropriate to become a qualified OFBiz
committer.
The one challenge I have not worked out is how to
best structure the
playground
to support various projects and easily integrate
back into an OFBiz
instance.
Thanks
