I think we're talking about two different things. You're talking about developing and I'm talking about legal issues. The manner of developing was already discussed in OFBIZ-499. The only legal way to use JIRA to collaborate this type of thing is to keep sending updated patches to JIRA or to have a committer review and add it to a specialized application. Neither one of these is speed of development friendly.
Legal concerns wouldn't have been one of the primary driving forces of moving to the ASF if it were true that "we've done fine for years". The project still has technical exposure to a C & D order as the CLA only covered works the copyright holder gave directly to the ASF not the works the copyright holder gave to the OFBIZ project prior to incubation. IANAL, and I don't think there is significant exposure, but it is still there. That opinion isn't based on the vehicle used to create Apache OFBiz, but on the impression of kindheartedness from the members of the community prior to incubation. I don't want to speculate on the legal relationship the group that worked on the anon checkout had, but I would suspect that it generated some negative legal exposure as well and that the proposed setup of Developers Conference will add to that. The only feedback that I've received from the general incubator list are speculations, all with the caveat that the poster is not a lawyer either and no one has been willing to post it to the legal-discuss list. This issue is one of the MAJOR reasons for the existence of non-profit entities like the ASF, FSF, and SPI. So again, I ask you to reconsider the need of a more public sandbox where this kind of community collaboration can be done without the complications of copyright infringement, or at the very least pose the question to legal-discuss for a formal opinion from those representing the ASF's interests. It is my understanding that when it's added to Apache owned SVN, ASF is the copyright holder of the collective work instead of an impromptu partnership where the individuals have no legal authority to offer a collective work. Regards, Chris --- "David E. Jones" <[EMAIL PROTECTED]> wrote: > > I REALLY don't think you need a sandbox for this. We've done fine for > > years without one, even with the recently re-done ecommerce anonymous > > checkout process and alternative checkout processes which were > developed entirely outside of OFBiz. > > Getting this stuff done is mostly a matter of knowing what you're > doing and having a clear goal to work towards, a design of sorts if > you will. A sandbox won't help that. > > Once you have a design you can start building it without touching the > > current stuff, just make it an alternate path and don't break > anything existing along the way. Once it is complete, then another > patch can go in to remove the old code. > > It's that simple. That process has been followed well over a hundred > > times over the life of OFBiz and even for those with commit access > it's the only way to go. If you don't have commit access, it's even > better because you can develop until you're stuck or out of time, > then throw in a patch and have it committed without breaking anything > > else, even if the new thing isn't working 100%. > > -David > > > On Jan 25, 2007, at 12:05 PM, Chris Howe wrote: > > > Hey Anil, > > > > I've begun some of this already. I'm taking the approach of > passing > > the cart to a simple method that first checks the order type and > then > > calls a method or service that is focused on that order type. Each > > order type service will call a multitude of methods/services that > > prepare the cart data to be entered into the datasource. > > > > I would love to collaborate on this, but because of the size, it's > > rather difficult to do by passing patches back and forth through > JIRA > > without having a reference point that SVN provides. This is one of > > those things that the ofbiz-sandbox project would be good for, but > it > > still has a legal issue that will prevent it from being entered > back > > into the project. I can as an individual grant Apache the license > it > > needs for the work I do, you as an individual can grant Apache the > > license it needs for the work you do, but without each of us > assuming > > the liability of a partnership we cannot grant a license for the > work > > as a whole. The only way around this is to use ofbiz-sandbox SVN > and > > make patches for each commit and each of us resubmit our own patch > to > > OFBiz JIRA with the order they need to be applied in. > > > > This would be sooooo much easier if the members of OFBiz PMC would > > respond on including a public sandbox in Apache OFBiz as each SVN > > commit will be licensed to Apache, and Apache will be the owner of > the > > work as a whole instead of an impromptu partnership being the > owner. > > > > > > --- Anil Patel <[EMAIL PROTECTED]> wrote: > > > >> I planning to participate in this developer conference. I am > >> interested in > >> contributing towards making Order Entry process more flexible. If > >> there are > >> Others who will be interested we can start some ground work. I > >> request one > >> of the commiters who has interest in this to Please lead this > effort. > >> > >> The anonymous checkout process in Ecommerce component provides > some > >> high > >> level guiding principals. Few things that I can think of are > >> 1) moving some code that's embedded in Java classes into small > simple > >> methods. > >> 2) Moving process control logic from event handlers to Controller > >> file. > >> > >> Any Ideas > >> > >> Regards > >> Anil Patel > >> > >> On 1/16/07, David E. Jones <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> NOTE: I'm just sending this to the dev list as this event is > meant > >>> mainly for those who want to be involved with development of > OFBiz > >>> itself. There will be a variety of projects going on and we hope > >>> everyone will be able to work on both paid and fun stuff, but the > >>> results will all be going right back into OFBiz. Still, everyone > is > >>> welcome to attend and join the "party" so if you know of someone > >> who > >>> might be interested but isn't subscribed to the dev mailing list, > >>> please forward it on to them. > >>> > >>> NOTE2: While most of this conference will be centered around > >>> development, if you aren't a developer it doesn't mean you can't > >>> come. It would be great to have, for example, people like > business > >>> analysts and technical writers to help with requirements, design, > >> and > >>> documentation and such would be great! > >>> > >>> Included below is the original email about this, and most of the > >>> information there is still applicable. Here are a few decisions, > >>> based on feedback: > >>> > >>> 1. the conference dates will be 5-9 March 2007 (Monday - Friday), > >> and > >>> may spill over into Sat the 10th > >>> > >>> 2. you don't have to come for the entire conference, but we > >> recommend > >>> coming for at least Mon-Wed or Wed-Fri as we'll schedule > big-group > >>> meetings and any presentations for Wednesday; if you can come for > >> the > >>> whole week, please do, it'll be great! > >>> > >>> 3. people are welcome to come and enjoy local attractions for the > >>> weekend before and/or after (it will still be cool in the area > >> here, > >>> snowy in the mountains for skiing/boarding/snowmobiling, and > >>> depending on weather it can be a great time for visiting the > >> deserts > >>> and canyons south of here) > >>> > >>> 4. the cost to cover the meeting rooms, snacks, infra stuff, etc > >> will > >>> be $175 for the week (or $35/day) per person; we will have > wireless > >>> internet access, and I have a bridge if anyone needs wired > access; > >> we > >>> will have at least 2 projectors and perhaps other large monitors > to > >>> facilitate group development and discussion > >>> > >>> 5. meals, lodging, etc are not included in the main price, but > >> we'll > >>> have 5-9 rooms available in the building (for $20-30 per night, > >> first > >>> come first serve); there is a decent hotel in town as well for > >> around > >>> $80 per night (contact me for details); for meals there are > various > >>> restaurants within walking distance > >>> > >>> 6. the attendance cap is initially 20 people; there seems to be a > >> lot > >>> of interest in this, so if we go over that we'll raise it by > >> perhaps > >>> 5-10 more people and convert some other adjacent rooms in the > >>> building to be for group meeting use as well (we're planning on 2 > >> big > >>> rooms, plus a fairly big room with a small kitchen in it) > >>> > >>> 7. the actual development goals are not finalized, but there is > >> quite > >>> a bit of interest in various things on the original list I > included > >>> (below), the big things seem to be testing infrastructure and > >> project > >>> management functionality > >>> > >>> To register (ASAP please, to make my job of planning easier!), > >> please > >>> contact me by email ([EMAIL PROTECTED]) with the following > >>> information: > >>> > >>> 1. your name, company name, contact info (phone, email if > different > >>> than from address) > >>> 2. how many in your group (if more than one, their names too) > >>> 3. plans (as much as known) for how many days and which days > >>> 4. lodging preference - in the building (private rooms, shared > >>> toilets/showers) how many rooms, or nearby hotel (I'll respond > with > >>> contact info for the nice place close by, or there is a "fleabag" > >>> motel place too though not sure if I'd recommend it) > >>> 5. snack/diet preferences > >>> 6. local travel plans: do you need a ride, or do you plan to > rent/ > === message truncated ===
