Any need for an svn playground?

[Daniel Kunkel]

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

--
Daniel

*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-
Have a GREAT Day!

Daniel Kunkel           [hidden email]
BioWaves, LLC           http://www.BioWaves.com
14150 NE 20th St. Suite F1
Bellevue, WA 98007
800-734-3588    425-895-0050
http://www.Apartment-Pets.com  http://www.Illusion-Optical.com
http://www.Card-Offer.com      http://www.RackWine.com
http://www.JokesBlonde.com     http://www.Brain-Fun.com 
*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-

[cjhowe]

I have a project pending for sourceforge.net for just
this purpose (it's taking a little bit of time because
of the holiday, I imagine).  I had asked a couple of
weeks ago if Apache Ofbiz would like this a similar
resource under their umbrella and really didn't get a
thumbs up/down from the committers.

If it does get approved, its Unix name will be
ofbiz-sandbox.  I'll post if/when it does get approved
unless Apache Ofbiz wants to maintain a similar
resource.

--- Daniel Kunkel <[hidden email]> 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
>
> --
> Daniel
>
>

*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-

> Have a GREAT Day!
>
> Daniel Kunkel           [hidden email]
> BioWaves, LLC           http://www.BioWaves.com
> 14150 NE 20th St. Suite F1
> Bellevue, WA 98007
> 800-734-3588    425-895-0050
> http://www.Apartment-Pets.com 
> http://www.Illusion-Optical.com
> http://www.Card-Offer.com     
> http://www.RackWine.com
> http://www.JokesBlonde.com   
> http://www.Brain-Fun.com 
>

*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-
>
>

[Adrian Crum]

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
>

[davidnwelton]

On 1/2/07, Chris Howe <[hidden email]> wrote:

> I have a project pending for sourceforge.net for just
> this purpose (it's taking a little bit of time because
> of the holiday, I imagine).  I had asked a couple of
> weeks ago if Apache Ofbiz would like this a similar
> resource under their umbrella and really didn't get a
> thumbs up/down from the committers.
>
> If it does get approved, its Unix name will be
> ofbiz-sandbox.  I'll post if/when it does get approved
> unless Apache Ofbiz wants to maintain a similar
> resource.

The ASF tends to be, in my experience, a little bit more beaurocratic
than might be desireable for purely blue-sky sandbox type things like
that, so I think that SF or google code or something else is probably
a better place for it until such time as it develops enough to be
something that the OFBiz PMC can look at integrating.

Just my opinion though, I'm not speaking for the ASF...

--
David N. Welton
 - http://www.dedasys.com/davidw/

Linux, Open Source Consulting
 - http://www.dedasys.com/

[cjhowe]

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 <[hidden email]> 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
> >
>

[Adrian Crum]

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 <[hidden email]> 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
>>>
>>
>
>

[cjhowe]

Adrian,
I think your OFBIZ-495 is a perfect example of an
issue that would benefit from something like this.
It's a fairly large task, and while there has
certainly been a lot of discussion on the mailing
list, you've essentially been left with the burden to
complete the task. However, if your patches were
applied to a sandbox, I think others would be more apt
(theoretically speaking) to take a look at it, and
instead of pointing out where there may be a flaw,
point out the flaw and provide a quick solution.  

How many comments in JIRA are: "there's xyz problem
with this patch, please resubmit".  This is the exact
response the reviewers should be giving because of the
amount of time it would take on their part to fix the
problem and create a more correct patch.  However, it
puts the burden back on the original submitter even
though he may be 30 days or more beyond that problem
in his own deployment.

In any event, I highly doubt there will be any arm
twisting for anyone to utilize a sandbox when
available.  But for those who want to collaborate a
little more closely with others, the option will
hopefully be beneficial for them.

--- Adrian Crum <[hidden email]> wrote:

> 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.
>
>

[Adrian Crum]

Actually, OFBIZ-495 is one of the small pieces I mentioned. I consider that
patch completed. The other enhancements I'm working on will require that patch.

So, (in my scenario) the "big project" Jira issue would contain a patch, along
with comments like "Requires framework_v2.patch in OFBIZ-495, aaabbbccc.patch in
OFBIZ-ZZZ" etc. Someone wanting to use the new feature would download and apply
the specified patches.

The "big project" might never make it into OFBiz initially. But maybe OFBIZ-495
would. If enough people apply the patch to their local copies and like it, then
maybe the committers will take a second look at including the feature in OFBiz.

I'm not arguing against what you've proposed. I'm just saying that I believe it
can be done with existing resources.


Chris Howe wrote:

> Adrian,
> I think your OFBIZ-495 is a perfect example of an
> issue that would benefit from something like this.
> It's a fairly large task, and while there has
> certainly been a lot of discussion on the mailing
> list, you've essentially been left with the burden to
> complete the task. However, if your patches were
> applied to a sandbox, I think others would be more apt
> (theoretically speaking) to take a look at it, and
> instead of pointing out where there may be a flaw,
> point out the flaw and provide a quick solution.  
>
> How many comments in JIRA are: "there's xyz problem
> with this patch, please resubmit".  This is the exact
> response the reviewers should be giving because of the
> amount of time it would take on their part to fix the
> problem and create a more correct patch.  However, it
> puts the burden back on the original submitter even
> though he may be 30 days or more beyond that problem
> in his own deployment.
>
> In any event, I highly doubt there will be any arm
> twisting for anyone to utilize a sandbox when
> available.  But for those who want to collaborate a
> little more closely with others, the option will
> hopefully be beneficial for them.
>
> --- Adrian Crum <[hidden email]> wrote:
>
>
>>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.
>>
>>
>
>