Thanks Tim! I suggested the same method some time ago. Personally, I like the
idea of using existing resources.
Just set up a Jira issue and make it clear in the initial comment that it's a
"sandbox" - so everyone knows you're trying out ideas in that issue. Then follow
Tim's flow.
Simple.
-Adrian
Tim Ruppert wrote:
I know this sounds overly simplified, but someone please explain to me
why this doesn't work:
1. Someone - let's say Chris has a great idea for a new project
2. He creates a JIRA issue describing it
3. He attaches an initial patch
4. Someone else - let's say Daniel decides that he wants to contribute
to this effort and downloads the patch
5. He makes some improvements, so he updates the existing patch as well
as adds another patch containing additional data
6. Chris downloads it and makes some mods and reposts.
Now, to me this doesn't seem that crazy - and is totally legal. And . .
. just so you know - replace Chris with Tim and Daniel with either Anil
or Ashish and you have EXACTLY what happened with the anonymous checkout
process!
This shouldn't be this hard guys. My suggestion would be to TRY one of
these in this format and if you can't do it this way - THEN let's try
and address it. A separately maintained sandbox is absolutely no
different than managing patches - since both have to deal with
integration back into the OFBiz trunk in some form or fashion.
Personally, I think the patches will be EASIER to maintain because they
will allow you to make changes to existing code in an easier, more
trackable format. The alternative would be for you to maintain a
sandbox - AND patches for updates to the source - doesn't that sound
MORE tedious?
Anyways, thanks for listening to my ramble.
Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
