Re: Refactoring Create Order process during OFBiz Developers Conference Sponsored by Hotwax Media

[David E. Jones]

-David


On Jan 25, 2007, at 12:05 PM, Chris Howe 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%.

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/
have a car (I'll try to arrange rides in advance for people that

need

them, so please ask EARLY and get a verification from me before you
depend on this!)
7. while I'm not sure how this will work out, if you need financial
assistance or have money you could contribute to getting developers
here, please let me know
8. any questions or concerns you have

Also think about the topics you'd like to cover, especially things
that will make your life easier and the lives of your employers/
clients too. I'll be contacting people just before the event to ask
for preference and ideas, and then I'll put together a real list

for

the conference.

I look forward to meeting everyone there! Given the topics and

people

I've heard from so far this should be a pretty incredible event.

I'm

predicting we'll have more OFBiz experience in one room than has

ever

been done before!

-David


============================================================
============================================================
Hello All,

During the Users Conference this past November the idea of a
developers conference came up, and being something I had discussed
with others before this seemed to be a great idea and something I'd
be happy to host here at the same place where we had the user
conference in Nov 2006 (ie the old hotel where my home and office

are

right now, in Ephraim, UT).

The general idea is to get together and basically just work on

stuff.

We'd like to get as many of the committers and regular contributors
here as possible, and maybe even pool some funds to help mitigate

the

expense for far away people like Jacopo, Jacques, Hans, and perhaps
various others.

We may have some presentations on general topics, but the main

point

will be to pick a few objectives for the project and push them
forward. We will definitely want feedback on the projects we want

to

attach, and I'm thinking we'll have one person champion each
objective, and then everyone can split into groups and rotate

around

and just work on stuff. We'll have a couple of projectors

available,

plenty of chairs and table space and facilities for everyone's
laptops, and then we'll get some snacks and a mountain of bottled
water and we should be good to go.

As we talked about this the hope is certainly to help move certain
part of the OFBiz project forward, but also to work on anything

that

at least a couple of people need for clients and hopefully have
funding for to help them be able to attend and collaborate.

Ephraim is a small town and rather conservative, but we managed to
find pretty good diversion in the evenings, including "imbibing"
mountains of pasta, or getting in some beer and bowling at the

local

alley (which surprisingly, even to me, was pretty decent). For

those

staying longer in the area there are some national parks within a

few

hours, and lots of mountain roads that are groomed and marked for
snowmobiling and back-country skiing and such (or other things

during

the summer). We also have games and stuff in the building, like

ping

pong, foosball, and air hockey types of things.

The 2 main things I think we need to discuss are:

1. when to do it
2. what objectives to pursue

For #1 we're thinking about doing this as a full week late February
or early March with 3 possibilities, including: Feb 19 - 23, Feb 26

-

=== message truncated ===

smime.p7s
Description: S/MIME cryptographic signature