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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
54 messages Options
123
Reply | Threaded
Open this post in threaded view
|

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

Anil Patel
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 <[hidden email]> 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 ([hidden email]) 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 -
> Mar 2, or Mar 5 - 9.
>
> These are all about 2 months away and should hopefully give everyone
> time to get organized and make arrangements.
>
> Before getting into topics to cover, here are a few details about
> arrangements:
>
> 1. this will be sponsored and organized by the new and improved
> Hotwax Media, and the cost will be minimal and intended to just cover
> expenses (including meeting room facilities, food/snacks/drinks, and
> in some cases even lodging); the conference alone (without lodging or
> meals included) will probably run around $150 per person and as
> mentioned lodging in the building can be added on very affordably,
> and the meals dining in the area should be around $20-30 per day
> depending on how crazy you want to get ;)
>
> 2. the location will be old Ephraim Hotel at 24 West Center, Ephraim,
> UT 84627; we'll have meeting/working space for a maximum of around 25
> people and we might be able to arrange for another adjacent room to
> handle a few more; there will be around 10 very affordable (~$25-30
> per night) lodging rooms available in the building, and beyond that
> we have other rooms that aren't fixed up yet but there are other
> lodging options in town including a pretty nice mid-range hotel that
> costs around $80 per night
>
> 3. for travel: Ephraim is about a 2 hour drive from the Salt Lake
> City airport (code: SLC); alternatively, it is about a 4.5 to 5 hour
> (340 miles) drive from Las Vegas, NV; for real flexibility renting a
> car is a good idea, but we plan to arrange for rides with various
> local people or perhaps even a rented van or something for a ride
> share; we will need feedback on what people need or want in this area
> too
>
> So, for anyone interested in coming, please contact me (directly, off
> the list) with your preferences on the following:
>
> 1. when to have the conference: Feb 19 - 23, Feb 26 - Mar 2, or Mar 5
> - 9
>
> 2. your travel and accommodation preferences: need a ride from the
> SLC airport? prefer to stay at the building or in a nearby hotel?
>
> 3. would you be interested and able to contribute to help core people
> from farther away make it to the conference? if so how much?
>
> 4. would you be interested in intermediate level training before the
> conference (we are considering this, but haven't decided yet), or
> perhaps even more mentoring oriented sessions during the conference?
>
> 5. which objectives most interest you (select from below, and include
> your own too):
>
> a. testing infrastructure (finishing this up)
>
> b. kick-start a body of automated tests based on (a)
>
> c. project management build out so many of us as services companies
> can use it to run our businesses, and so that once it matures we can
> run/manage OFBiz on it too (this would be an alternative to things
> like Jira, XPlanner, gForge, etc); this could include a number of sub-
> objectives, even things like ical, etc features to integrate with
> desktop calendar and contact and such software; should also include
> reports, handy UIs for common tasks, short process docs for how we
> recommend the various tools be used together, etc
>
> d. content solutions: this could/would include stuff built on the
> current OFBiz content management data model and services, and/or the
> really cool Webslinger stuff from Brainfood (beyond whatever happens
> before the conference!)
>
> e. begin development on the human resources application
>
> f. refactor and clean up really old and messy code, like: the
> storeOrder service, the order manager checkout process, etc.
>
> g. visually appealing face lift for ecommerce, and based on that the
> back end apps too; this should include CSS oriented refactoring to be
> more Zen Garden like and easier to maintain and customize
>
> h. usability enhancements for certainly frequently used screens (like
> party search, order search, etc) based on AJAX and DHTML
>
> i. generic setup wizard, and perhaps one or two extension wizard
> examples for specific industries; this would go along with setup data
> files specific to these as well
>
> j. reporting tool refinements (probably form widget based) and a
> wider variety of OOTB reports, including some examples of how to do
> funky and cool print and web reports with these tools
>
> k. working through bugs to stabilize a release branch (which should
> be started a few weeks before the conference)
>
> l. review, organize, and expand the documentation (mostly now on
> docs.ofbiz.org, with most stuff moving there)
>
> m. ...
>
> Okay, there is a LOT we could cover and depending on how many people
> show up we'll want a list of probably 5-10 objectives to pursue,
> making sure we get at least a few things of interest to everyone.
>
> ==========================
>
> In general this is a chance for all of us to learn tons of stuff and
> collaborate in a way that is sometimes difficult remotely. The main
> goal is to take care of things that have been moving slow for a long
> time, or to jump start things that would be great but just haven't
> been able to get off the ground yet.
>
> I should also note that we would like to start doing this more
> regularly, perhaps even quarterly if there is enough interest. We can
> keep costs fairly low by doing it here in Ephraim or in other places
> like this, and by doing it regularly we can build the community and
> move forward long term objectives in a way that has been very
> difficult so far.
>
> I look forward to seeing as many of us there (here!) as possible!
>
> -David
>
>
>
>
>
Reply | Threaded
Open this post in threaded view
|

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

cjhowe
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 <[hidden email]> 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 <[hidden email]> 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 ([hidden email]) 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 ===

Reply | Threaded
Open this post in threaded view
|

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

David E Jones

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 <[hidden email]> 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 <[hidden email]> 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 ([hidden email]) 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 (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

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

David E Jones
In reply to this post by Anil Patel

Just some quick thoughts...

Following the pattern of the anonymous and other checkout processes  
in the ecommerce app would be a great way to go.

In the order manager there are various paths through the checkout  
process so we might have, for example, 2 different sets of request-
map definitions and two different "progress bars", one for sales  
orders and one for purchase orders. These two different sets of high-
level artifacts can point to the same views, services/events,  
screens, data prep scripts, etc wherever the two processes overlap.

-David


On Jan 25, 2007, at 11:34 AM, Anil Patel 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 <[hidden email]> 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 ([hidden email]) 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 -
>> Mar 2, or Mar 5 - 9.
>>
>> These are all about 2 months away and should hopefully give everyone
>> time to get organized and make arrangements.
>>
>> Before getting into topics to cover, here are a few details about
>> arrangements:
>>
>> 1. this will be sponsored and organized by the new and improved
>> Hotwax Media, and the cost will be minimal and intended to just cover
>> expenses (including meeting room facilities, food/snacks/drinks, and
>> in some cases even lodging); the conference alone (without lodging or
>> meals included) will probably run around $150 per person and as
>> mentioned lodging in the building can be added on very affordably,
>> and the meals dining in the area should be around $20-30 per day
>> depending on how crazy you want to get ;)
>>
>> 2. the location will be old Ephraim Hotel at 24 West Center, Ephraim,
>> UT 84627; we'll have meeting/working space for a maximum of around 25
>> people and we might be able to arrange for another adjacent room to
>> handle a few more; there will be around 10 very affordable (~$25-30
>> per night) lodging rooms available in the building, and beyond that
>> we have other rooms that aren't fixed up yet but there are other
>> lodging options in town including a pretty nice mid-range hotel that
>> costs around $80 per night
>>
>> 3. for travel: Ephraim is about a 2 hour drive from the Salt Lake
>> City airport (code: SLC); alternatively, it is about a 4.5 to 5 hour
>> (340 miles) drive from Las Vegas, NV; for real flexibility renting a
>> car is a good idea, but we plan to arrange for rides with various
>> local people or perhaps even a rented van or something for a ride
>> share; we will need feedback on what people need or want in this area
>> too
>>
>> So, for anyone interested in coming, please contact me (directly, off
>> the list) with your preferences on the following:
>>
>> 1. when to have the conference: Feb 19 - 23, Feb 26 - Mar 2, or Mar 5
>> - 9
>>
>> 2. your travel and accommodation preferences: need a ride from the
>> SLC airport? prefer to stay at the building or in a nearby hotel?
>>
>> 3. would you be interested and able to contribute to help core people
>> from farther away make it to the conference? if so how much?
>>
>> 4. would you be interested in intermediate level training before the
>> conference (we are considering this, but haven't decided yet), or
>> perhaps even more mentoring oriented sessions during the conference?
>>
>> 5. which objectives most interest you (select from below, and include
>> your own too):
>>
>> a. testing infrastructure (finishing this up)
>>
>> b. kick-start a body of automated tests based on (a)
>>
>> c. project management build out so many of us as services companies
>> can use it to run our businesses, and so that once it matures we can
>> run/manage OFBiz on it too (this would be an alternative to things
>> like Jira, XPlanner, gForge, etc); this could include a number of  
>> sub-
>> objectives, even things like ical, etc features to integrate with
>> desktop calendar and contact and such software; should also include
>> reports, handy UIs for common tasks, short process docs for how we
>> recommend the various tools be used together, etc
>>
>> d. content solutions: this could/would include stuff built on the
>> current OFBiz content management data model and services, and/or the
>> really cool Webslinger stuff from Brainfood (beyond whatever happens
>> before the conference!)
>>
>> e. begin development on the human resources application
>>
>> f. refactor and clean up really old and messy code, like: the
>> storeOrder service, the order manager checkout process, etc.
>>
>> g. visually appealing face lift for ecommerce, and based on that the
>> back end apps too; this should include CSS oriented refactoring to be
>> more Zen Garden like and easier to maintain and customize
>>
>> h. usability enhancements for certainly frequently used screens (like
>> party search, order search, etc) based on AJAX and DHTML
>>
>> i. generic setup wizard, and perhaps one or two extension wizard
>> examples for specific industries; this would go along with setup data
>> files specific to these as well
>>
>> j. reporting tool refinements (probably form widget based) and a
>> wider variety of OOTB reports, including some examples of how to do
>> funky and cool print and web reports with these tools
>>
>> k. working through bugs to stabilize a release branch (which should
>> be started a few weeks before the conference)
>>
>> l. review, organize, and expand the documentation (mostly now on
>> docs.ofbiz.org, with most stuff moving there)
>>
>> m. ...
>>
>> Okay, there is a LOT we could cover and depending on how many people
>> show up we'll want a list of probably 5-10 objectives to pursue,
>> making sure we get at least a few things of interest to everyone.
>>
>> ==========================
>>
>> In general this is a chance for all of us to learn tons of stuff and
>> collaborate in a way that is sometimes difficult remotely. The main
>> goal is to take care of things that have been moving slow for a long
>> time, or to jump start things that would be great but just haven't
>> been able to get off the ground yet.
>>
>> I should also note that we would like to start doing this more
>> regularly, perhaps even quarterly if there is enough interest. We can
>> keep costs fairly low by doing it here in Ephraim or in other places
>> like this, and by doing it regularly we can build the community and
>> move forward long term objectives in a way that has been very
>> difficult so far.
>>
>> I look forward to seeing as many of us there (here!) as possible!
>>
>> -David
>>
>>
>>
>>
>>


smime.p7s (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

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

cjhowe
In reply to this post by David E Jones
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" <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 ([hidden email]) 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 ===

Reply | Threaded
Open this post in threaded view
|

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

Daniel Kunkel
David

Can you explain your reticence to adding an Apache OFBiz sandbox where
more members of the community could share their work?

I can see this section possibly getting a disorganized over time with
*junk*... but it can be deleted easily enough. As a top level project
would it possible and better to organize a sub project for this?

Thanks

Daniel



On Thu, 2007-01-25 at 12:41 -0800, Chris Howe wrote:

> 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" <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 ([hidden email]) 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 ===
>
--
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 
*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-

Reply | Threaded
Open this post in threaded view
|

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

David E Jones

Okay, I just wrote a huge thing and deleted it. There might have been  
good stuff in there, but I am really frustrated because I've said it  
all before and based on the comments from Chris it doesn't seem like  
anything it making it out there.

If you're not a lawyer, then reference documents and processes  
already established.

I'm not even going to bother going into detail unless people are  
willing to:

1. describe their understanding of how what they want to do would be  
done under current policy
2. describe why that doesn't work for what you want to do
3. describe how the existing processes need to changed in order to  
accommodate it

A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it  
would create a huge mess. I'm afraid one of two things would happen:

1. nothing
2. a lot

In the case of number 1 it's not worth the effort to set it up. In  
the case of #2 it would required more effort to administer and  
monitor than we have resources for in OFBiz. There is no way I'd even  
think about doing this under the ASF umbrella because I am not  
willing to take on the responsibility of vetting a large number of  
committers and recommending them as committers in the ASF, which is  
BIG DEAL, and a responsibility and some people seem to be forgetting  
that.

If you want to be a committer you have to help with the project. You  
have to take ownership of it, defend it, be committed to it, and so  
on. Okay, now I'm doing what I was in the 2 page email I just deleted  
and I'm stopping.

If you want to know more about becoming and being a committer and  
about contributing to OFBiz, READ THE DARN DOCUMENTS!

I don't know WHY these questions are coming up here. Stop asking  
them. Read the documents. I won't be baited into this any more. It's  
a waste of time, and all based on supposition and not any real  
problems or issues as far as I can see.

If you develop something outside of OFBiz and want to contribute it,  
here is the page describing how it works:

http://incubator.apache.org/ip-clearance/index.html

This is basically a streamlined incubation process for code going  
into existing projects.

If you really want to help and be involved in the project it means  
working on OTHER PEOPLE'S STUFF, NOT YOUR OWN! Yes, it makes it  
easier to get your own stuff in but if that is all you're about  
related to the project, then being a committer isn't for you.

If you want to know more about contributing and being a committer,  
read the docs:

http://docs.ofbiz.org/x/mQ
http://docs.ofbiz.org/x/r

If you want to know more about licensing and legal issues, read the  
docs:

http://incubator.apache.org/incubation/Incubation_Policy.html
http://incubator.apache.org/ip-clearance/index.html
http://www.apache.org/foundation/how-it-works.html
http://www.apache.org/foundation/licence-FAQ.html
http://www.apache.org/legal/src-headers.html

For a lot of good information, broaden the scope and study under:

http://www.apache.org/dev/

These were not written because someone was looking for some  
entertainment. They were written so things wouldn't have to be  
explained over and over.

I'm calling it a day now, as soon as I take care of some real issues,  
and as long as my son with the flu doesn't throw up again. Sorry,  
this is really frustrating, and really silly. Reality sucks, but we  
all have to live with it.

If people want to help, then help. Don't just ask for help. Start by  
being a giver, not a taker.

If this sounds a bit harsh, great! Go for a walk and think about how  
things work in real life, then read it again. If you're still upset,  
read it again. Then go read all of the documents referenced. Then if  
you still have a question, send it on in, but PLEASE try to look at  
it from the point of a MEMBER of the OFBiz community, and not a user  
of OFBiz who really doesn't want to get involved.

If you're asking "how are you going to solve this problem" then  
you're asking the wrong question. If you want to participate as "how  
can I solve this problem", if "I" can't, then do with "how can we  
solve this problem". I don't mean that is what should be in your  
email, I mean that is what should be in your head. If you can't find  
an answer yourself that is 100% okay, just start a discussion and  
accept what you asked for.

If you don't like the answer explain why it doesn't work for you,  
which brings us back to the beginning of this email...

-David


On Jan 25, 2007, at 6:10 PM, Daniel Kunkel wrote:

> David
>
> Can you explain your reticence to adding an Apache OFBiz sandbox where
> more members of the community could share their work?
>
> I can see this section possibly getting a disorganized over time with
> *junk*... but it can be deleted easily enough. As a top level project
> would it possible and better to organize a sub project for this?
>
> Thanks
>
> Daniel
>
>
>
> On Thu, 2007-01-25 at 12:41 -0800, Chris Howe wrote:
>> 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" <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 ([hidden email]) 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 ===
>>
> --
> 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
> *-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-
>


smime.p7s (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

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

Daniel Kunkel
Hi

First, please understand I hold you in incredibly high regard, and
apologize for causing any frustration...  You and Andy have created an
amazing software tool that I'm basing my business on, and you've given
it away. I love that! As you can see, your efforts are now multiplying
in to a system that has a life of its own, which will eventually change
the face of many businesses throughout the world.

During this process, you've needed to exercise great control in choosing
what to allow into the project, and what to reject. Since I often update
my production system to the svn head, I'm very glad someone is there
watching, and if you think about it, it makes sense that access has been
very limited to just the professionals that have devoted themselves to
the project.

However, as it grows, there are more and more newbies that want to help
in their little way. Many *non-committers* who have wanted to give back
to the project have been stifled and frustrated, often because their
contributions were not appropriate, but sometimes simply because the
committers are too busy to review/test/correct their contributions. In
other cases, the resultant solutions are too specific to just their
business, or as a employee, the business although willing to donate the
code back, was not willing to devote the time needed to make the
consumable by the project at large.

So, what can we do to create a space where non-committers can share
their bits with the community? Please understand, we are agreed that
neither of us would want their contributions running on a system.

- The source forge sandbox isn't really a good fit, because, as Chris
has researched, the legal ramifications of donating it back to the
project outweigh the benefits begotten from the group effort.

- Forcing developers to work alone isn't working very well.

- A sandbox with lots of committers isn't going to work. Thanks for
explaining that in your e-mail, I didn't realize this wasn't workable
till now.

- Jira isn't working.

- The wiki could possibly work, but it doesn't go through the legal
process with each submission, and I cringe even thinking of trying to
work with code in wiki. Eek.

- Even using the wiki, to catalog which jira issues are "in play" is
unwieldy. Patch nightmare actually.

David, can you think of way to make a space in this community where the
new/non-polished committers can easily share and play together with
their ideas where they won't hurt the bigger project until the
components are well proven?

Would it work to have a sandbox that is managed by the existing
committers, or perhaps a few new committers? As a committer, you
wouldn't need to give nearly the same amount of time and attention to
trying to make sure the commitment met best practices, free of bugs,
etc. Any developer could share their stuff that they've implemented for
their business, or other neat components. And, since the commitments
would be in svn on the other side of the "Donate to the Apache
Foundation legal radio button, it'd be easy for these developers to
collaborate and slowly bring unworkable buggy messes into gold. Finally,
users could easily find and try the components without mucking with
patch files, etc.

Thanks

Daniel

On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:

> Okay, I just wrote a huge thing and deleted it. There might have been  
> good stuff in there, but I am really frustrated because I've said it  
> all before and based on the comments from Chris it doesn't seem like  
> anything it making it out there.
>
> If you're not a lawyer, then reference documents and processes  
> already established.
>
> I'm not even going to bother going into detail unless people are  
> willing to:
>
> 1. describe their understanding of how what they want to do would be  
> done under current policy
> 2. describe why that doesn't work for what you want to do
> 3. describe how the existing processes need to changed in order to  
> accommodate it
>
> A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it  
> would create a huge mess. I'm afraid one of two things would happen:
>
> 1. nothing
> 2. a lot
>
> In the case of number 1 it's not worth the effort to set it up. In  
> the case of #2 it would required more effort to administer and  
> monitor than we have resources for in OFBiz. There is no way I'd even  
> think about doing this under the ASF umbrella because I am not  
> willing to take on the responsibility of vetting a large number of  
> committers and recommending them as committers in the ASF, which is  
> BIG DEAL, and a responsibility and some people seem to be forgetting  
> that.
>
> If you want to be a committer you have to help with the project. You  
> have to take ownership of it, defend it, be committed to it, and so  
> on. Okay, now I'm doing what I was in the 2 page email I just deleted  
> and I'm stopping.
>
> If you want to know more about becoming and being a committer and  
> about contributing to OFBiz, READ THE DARN DOCUMENTS!
>
> I don't know WHY these questions are coming up here. Stop asking  
> them. Read the documents. I won't be baited into this any more. It's  
> a waste of time, and all based on supposition and not any real  
> problems or issues as far as I can see.
>
> If you develop something outside of OFBiz and want to contribute it,  
> here is the page describing how it works:
>
> http://incubator.apache.org/ip-clearance/index.html
>
> This is basically a streamlined incubation process for code going  
> into existing projects.
>
> If you really want to help and be involved in the project it means  
> working on OTHER PEOPLE'S STUFF, NOT YOUR OWN! Yes, it makes it  
> easier to get your own stuff in but if that is all you're about  
> related to the project, then being a committer isn't for you.
>
> If you want to know more about contributing and being a committer,  
> read the docs:
>
> http://docs.ofbiz.org/x/mQ
> http://docs.ofbiz.org/x/r
>
> If you want to know more about licensing and legal issues, read the  
> docs:
>
> http://incubator.apache.org/incubation/Incubation_Policy.html
> http://incubator.apache.org/ip-clearance/index.html
> http://www.apache.org/foundation/how-it-works.html
> http://www.apache.org/foundation/licence-FAQ.html
> http://www.apache.org/legal/src-headers.html
>
> For a lot of good information, broaden the scope and study under:
>
> http://www.apache.org/dev/
>
> These were not written because someone was looking for some  
> entertainment. They were written so things wouldn't have to be  
> explained over and over.
>
> I'm calling it a day now, as soon as I take care of some real issues,  
> and as long as my son with the flu doesn't throw up again. Sorry,  
> this is really frustrating, and really silly. Reality sucks, but we  
> all have to live with it.
>
> If people want to help, then help. Don't just ask for help. Start by  
> being a giver, not a taker.
>
> If this sounds a bit harsh, great! Go for a walk and think about how  
> things work in real life, then read it again. If you're still upset,  
> read it again. Then go read all of the documents referenced. Then if  
> you still have a question, send it on in, but PLEASE try to look at  
> it from the point of a MEMBER of the OFBiz community, and not a user  
> of OFBiz who really doesn't want to get involved.
>
> If you're asking "how are you going to solve this problem" then  
> you're asking the wrong question. If you want to participate as "how  
> can I solve this problem", if "I" can't, then do with "how can we  
> solve this problem". I don't mean that is what should be in your  
> email, I mean that is what should be in your head. If you can't find  
> an answer yourself that is 100% okay, just start a discussion and  
> accept what you asked for.
>
> If you don't like the answer explain why it doesn't work for you,  
> which brings us back to the beginning of this email...
>
> -David
>
>
> On Jan 25, 2007, at 6:10 PM, Daniel Kunkel wrote:
>
> > David
> >
> > Can you explain your reticence to adding an Apache OFBiz sandbox where
> > more members of the community could share their work?
> >
> > I can see this section possibly getting a disorganized over time with
> > *junk*... but it can be deleted easily enough. As a top level project
> > would it possible and better to organize a sub project for this?
> >
> > Thanks
> >
> > Daniel
> >
> >
> >
> > On Thu, 2007-01-25 at 12:41 -0800, Chris Howe wrote:
> >> 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" <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 ([hidden email]) 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 ===
> >>
> > --
> > 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
> > *-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-
> >
>

Reply | Threaded
Open this post in threaded view
|

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

jonwimp
David,

Just a brief response here.

Sandbox can be created outside of the OFBiz SVN. Even your personal branch (assuming you do an
"SVN copy/branch" from the OFBiz SVN trunk, not your read-only workspace containing the downloaded
OFBiz) is a sandbox.

 > - A sandbox with lots of committers isn't going to work. Thanks for
 > explaining that in your e-mail, I didn't realize this wasn't
 > workable till now.

David's right. If an OFBiz SVN trunk isn't working as well as we'd all like it (given limited
committers' resources to audit and/or to commit patches), then a sandbox given a disorganized
ragtag (at least I consider myself ragtag) team of committers won't work either (too many cooks).

 > Would it work to have a sandbox that is managed by the existing
 > committers, or perhaps a few new committers? As a committer, you
 > wouldn't need to give nearly the same amount of time and attention to
 > trying to make sure the commitment met best practices, free of bugs,
 > etc. Any developer could share their stuff that they've implemented for
 > their business, or other neat components. And, since the commitments
 > would be in svn on the other side of the "Donate to the Apache
 > Foundation legal radio button, it'd be easy for these developers to
 > collaborate and slowly bring unworkable buggy messes into gold. Finally,
 > users could easily find and try the components without mucking with
 > patch files, etc.

I (and some others) are currently looking to "round off loose ends" in OFBiz (for easy successful
demonstration to business clients, not IT folks). We're doing it in our own sandbox. If you'd like
to join us, let me know.

Our sandbox will contain many patches that won't be in OFBiz SVN. We (the ragtag team) will be
responsible for crash-testing those patches to death before we submit them to OFBiz. I believe
this is an excellent way to free up the OFBiz committers. We really test and audit our patches
first before even posting to OFBiz committers, in the proper formats (see
http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices) no less.

We're trying to take the heat off of the committers, allowing for a playground without messing up
the official OFBiz trunk for you/me/everybody, and create a structured way to submit patches to
OFBiz for review.

Well, at least that's my direction. The ragtag team isn't headed by me (I'm not paying).

Jonathon

Daniel Kunkel wrote:

> Hi
>
> First, please understand I hold you in incredibly high regard, and
> apologize for causing any frustration...  You and Andy have created an
> amazing software tool that I'm basing my business on, and you've given
> it away. I love that! As you can see, your efforts are now multiplying
> in to a system that has a life of its own, which will eventually change
> the face of many businesses throughout the world.
>
> During this process, you've needed to exercise great control in choosing
> what to allow into the project, and what to reject. Since I often update
> my production system to the svn head, I'm very glad someone is there
> watching, and if you think about it, it makes sense that access has been
> very limited to just the professionals that have devoted themselves to
> the project.
>
> However, as it grows, there are more and more newbies that want to help
> in their little way. Many *non-committers* who have wanted to give back
> to the project have been stifled and frustrated, often because their
> contributions were not appropriate, but sometimes simply because the
> committers are too busy to review/test/correct their contributions. In
> other cases, the resultant solutions are too specific to just their
> business, or as a employee, the business although willing to donate the
> code back, was not willing to devote the time needed to make the
> consumable by the project at large.
>
> So, what can we do to create a space where non-committers can share
> their bits with the community? Please understand, we are agreed that
> neither of us would want their contributions running on a system.
>
> - The source forge sandbox isn't really a good fit, because, as Chris
> has researched, the legal ramifications of donating it back to the
> project outweigh the benefits begotten from the group effort.
>
> - Forcing developers to work alone isn't working very well.
>
> - A sandbox with lots of committers isn't going to work. Thanks for
> explaining that in your e-mail, I didn't realize this wasn't workable
> till now.
>
> - Jira isn't working.
>
> - The wiki could possibly work, but it doesn't go through the legal
> process with each submission, and I cringe even thinking of trying to
> work with code in wiki. Eek.
>
> - Even using the wiki, to catalog which jira issues are "in play" is
> unwieldy. Patch nightmare actually.
>
> David, can you think of way to make a space in this community where the
> new/non-polished committers can easily share and play together with
> their ideas where they won't hurt the bigger project until the
> components are well proven?
>
> Would it work to have a sandbox that is managed by the existing
> committers, or perhaps a few new committers? As a committer, you
> wouldn't need to give nearly the same amount of time and attention to
> trying to make sure the commitment met best practices, free of bugs,
> etc. Any developer could share their stuff that they've implemented for
> their business, or other neat components. And, since the commitments
> would be in svn on the other side of the "Donate to the Apache
> Foundation legal radio button, it'd be easy for these developers to
> collaborate and slowly bring unworkable buggy messes into gold. Finally,
> users could easily find and try the components without mucking with
> patch files, etc.
>
> Thanks
>
> Daniel
>
> On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:
>> Okay, I just wrote a huge thing and deleted it. There might have been  
>> good stuff in there, but I am really frustrated because I've said it  
>> all before and based on the comments from Chris it doesn't seem like  
>> anything it making it out there.
>>
>> If you're not a lawyer, then reference documents and processes  
>> already established.
>>
>> I'm not even going to bother going into detail unless people are  
>> willing to:
>>
>> 1. describe their understanding of how what they want to do would be  
>> done under current policy
>> 2. describe why that doesn't work for what you want to do
>> 3. describe how the existing processes need to changed in order to  
>> accommodate it
>>
>> A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it  
>> would create a huge mess. I'm afraid one of two things would happen:
>>
>> 1. nothing
>> 2. a lot
>>
>> In the case of number 1 it's not worth the effort to set it up. In  
>> the case of #2 it would required more effort to administer and  
>> monitor than we have resources for in OFBiz. There is no way I'd even  
>> think about doing this under the ASF umbrella because I am not  
>> willing to take on the responsibility of vetting a large number of  
>> committers and recommending them as committers in the ASF, which is  
>> BIG DEAL, and a responsibility and some people seem to be forgetting  
>> that.
>>
>> If you want to be a committer you have to help with the project. You  
>> have to take ownership of it, defend it, be committed to it, and so  
>> on. Okay, now I'm doing what I was in the 2 page email I just deleted  
>> and I'm stopping.
>>
>> If you want to know more about becoming and being a committer and  
>> about contributing to OFBiz, READ THE DARN DOCUMENTS!
>>
>> I don't know WHY these questions are coming up here. Stop asking  
>> them. Read the documents. I won't be baited into this any more. It's  
>> a waste of time, and all based on supposition and not any real  
>> problems or issues as far as I can see.
>>
>> If you develop something outside of OFBiz and want to contribute it,  
>> here is the page describing how it works:
>>
>> http://incubator.apache.org/ip-clearance/index.html
>>
>> This is basically a streamlined incubation process for code going  
>> into existing projects.
>>
>> If you really want to help and be involved in the project it means  
>> working on OTHER PEOPLE'S STUFF, NOT YOUR OWN! Yes, it makes it  
>> easier to get your own stuff in but if that is all you're about  
>> related to the project, then being a committer isn't for you.
>>
>> If you want to know more about contributing and being a committer,  
>> read the docs:
>>
>> http://docs.ofbiz.org/x/mQ
>> http://docs.ofbiz.org/x/r
>>
>> If you want to know more about licensing and legal issues, read the  
>> docs:
>>
>> http://incubator.apache.org/incubation/Incubation_Policy.html
>> http://incubator.apache.org/ip-clearance/index.html
>> http://www.apache.org/foundation/how-it-works.html
>> http://www.apache.org/foundation/licence-FAQ.html
>> http://www.apache.org/legal/src-headers.html
>>
>> For a lot of good information, broaden the scope and study under:
>>
>> http://www.apache.org/dev/
>>
>> These were not written because someone was looking for some  
>> entertainment. They were written so things wouldn't have to be  
>> explained over and over.
>>
>> I'm calling it a day now, as soon as I take care of some real issues,  
>> and as long as my son with the flu doesn't throw up again. Sorry,  
>> this is really frustrating, and really silly. Reality sucks, but we  
>> all have to live with it.
>>
>> If people want to help, then help. Don't just ask for help. Start by  
>> being a giver, not a taker.
>>
>> If this sounds a bit harsh, great! Go for a walk and think about how  
>> things work in real life, then read it again. If you're still upset,  
>> read it again. Then go read all of the documents referenced. Then if  
>> you still have a question, send it on in, but PLEASE try to look at  
>> it from the point of a MEMBER of the OFBiz community, and not a user  
>> of OFBiz who really doesn't want to get involved.
>>
>> If you're asking "how are you going to solve this problem" then  
>> you're asking the wrong question. If you want to participate as "how  
>> can I solve this problem", if "I" can't, then do with "how can we  
>> solve this problem". I don't mean that is what should be in your  
>> email, I mean that is what should be in your head. If you can't find  
>> an answer yourself that is 100% okay, just start a discussion and  
>> accept what you asked for.
>>
>> If you don't like the answer explain why it doesn't work for you,  
>> which brings us back to the beginning of this email...
>>
>> -David
>>
>>
>> On Jan 25, 2007, at 6:10 PM, Daniel Kunkel wrote:
>>
>>> David
>>>
>>> Can you explain your reticence to adding an Apache OFBiz sandbox where
>>> more members of the community could share their work?
>>>
>>> I can see this section possibly getting a disorganized over time with
>>> *junk*... but it can be deleted easily enough. As a top level project
>>> would it possible and better to organize a sub project for this?
>>>
>>> Thanks
>>>
>>> Daniel
>>>
>>>
>>>
>>> On Thu, 2007-01-25 at 12:41 -0800, Chris Howe wrote:
>>>> 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" <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 ([hidden email]) 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 ===
>>>>
>>> --
>>> 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
>>> *-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-
>>>
>
>

Reply | Threaded
Open this post in threaded view
|

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

Jacques Le Roux
Administrator
In reply to this post by Daniel Kunkel
Daniel,

Just one very quick point : I do not totally agree about "Jira isn't working.". What is making you think that ? Please can you
elaborate ? From your comment we may find solutions...

Jacques

From: "Daniel Kunkel" <[hidden email]>
To: <[hidden email]>
Sent: Friday, January 26, 2007 11:04 AM
Subject: Re: Refactoring Create Order process during OFBiz DevelopersConference Sponsored by Hotwax Media


> Hi
>
> First, please understand I hold you in incredibly high regard, and
> apologize for causing any frustration...  You and Andy have created an
> amazing software tool that I'm basing my business on, and you've given
> it away. I love that! As you can see, your efforts are now multiplying
> in to a system that has a life of its own, which will eventually change
> the face of many businesses throughout the world.
>
> During this process, you've needed to exercise great control in choosing
> what to allow into the project, and what to reject. Since I often update
> my production system to the svn head, I'm very glad someone is there
> watching, and if you think about it, it makes sense that access has been
> very limited to just the professionals that have devoted themselves to
> the project.
>
> However, as it grows, there are more and more newbies that want to help
> in their little way. Many *non-committers* who have wanted to give back
> to the project have been stifled and frustrated, often because their
> contributions were not appropriate, but sometimes simply because the
> committers are too busy to review/test/correct their contributions. In
> other cases, the resultant solutions are too specific to just their
> business, or as a employee, the business although willing to donate the
> code back, was not willing to devote the time needed to make the
> consumable by the project at large.
>
> So, what can we do to create a space where non-committers can share
> their bits with the community? Please understand, we are agreed that
> neither of us would want their contributions running on a system.
>
> - The source forge sandbox isn't really a good fit, because, as Chris
> has researched, the legal ramifications of donating it back to the
> project outweigh the benefits begotten from the group effort.
>
> - Forcing developers to work alone isn't working very well.
>
> - A sandbox with lots of committers isn't going to work. Thanks for
> explaining that in your e-mail, I didn't realize this wasn't workable
> till now.
>
> - Jira isn't working.
>
> - The wiki could possibly work, but it doesn't go through the legal
> process with each submission, and I cringe even thinking of trying to
> work with code in wiki. Eek.
>
> - Even using the wiki, to catalog which jira issues are "in play" is
> unwieldy. Patch nightmare actually.
>
> David, can you think of way to make a space in this community where the
> new/non-polished committers can easily share and play together with
> their ideas where they won't hurt the bigger project until the
> components are well proven?
>
> Would it work to have a sandbox that is managed by the existing
> committers, or perhaps a few new committers? As a committer, you
> wouldn't need to give nearly the same amount of time and attention to
> trying to make sure the commitment met best practices, free of bugs,
> etc. Any developer could share their stuff that they've implemented for
> their business, or other neat components. And, since the commitments
> would be in svn on the other side of the "Donate to the Apache
> Foundation legal radio button, it'd be easy for these developers to
> collaborate and slowly bring unworkable buggy messes into gold. Finally,
> users could easily find and try the components without mucking with
> patch files, etc.
>
> Thanks
>
> Daniel
>
> On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:
> > Okay, I just wrote a huge thing and deleted it. There might have been
> > good stuff in there, but I am really frustrated because I've said it
> > all before and based on the comments from Chris it doesn't seem like
> > anything it making it out there.
> >
> > If you're not a lawyer, then reference documents and processes
> > already established.
> >
> > I'm not even going to bother going into detail unless people are
> > willing to:
> >
> > 1. describe their understanding of how what they want to do would be
> > done under current policy
> > 2. describe why that doesn't work for what you want to do
> > 3. describe how the existing processes need to changed in order to
> > accommodate it
> >
> > A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it
> > would create a huge mess. I'm afraid one of two things would happen:
> >
> > 1. nothing
> > 2. a lot
> >
> > In the case of number 1 it's not worth the effort to set it up. In
> > the case of #2 it would required more effort to administer and
> > monitor than we have resources for in OFBiz. There is no way I'd even
> > think about doing this under the ASF umbrella because I am not
> > willing to take on the responsibility of vetting a large number of
> > committers and recommending them as committers in the ASF, which is
> > BIG DEAL, and a responsibility and some people seem to be forgetting
> > that.
> >
> > If you want to be a committer you have to help with the project. You
> > have to take ownership of it, defend it, be committed to it, and so
> > on. Okay, now I'm doing what I was in the 2 page email I just deleted
> > and I'm stopping.
> >
> > If you want to know more about becoming and being a committer and
> > about contributing to OFBiz, READ THE DARN DOCUMENTS!
> >
> > I don't know WHY these questions are coming up here. Stop asking
> > them. Read the documents. I won't be baited into this any more. It's
> > a waste of time, and all based on supposition and not any real
> > problems or issues as far as I can see.
> >
> > If you develop something outside of OFBiz and want to contribute it,
> > here is the page describing how it works:
> >
> > http://incubator.apache.org/ip-clearance/index.html
> >
> > This is basically a streamlined incubation process for code going
> > into existing projects.
> >
> > If you really want to help and be involved in the project it means
> > working on OTHER PEOPLE'S STUFF, NOT YOUR OWN! Yes, it makes it
> > easier to get your own stuff in but if that is all you're about
> > related to the project, then being a committer isn't for you.
> >
> > If you want to know more about contributing and being a committer,
> > read the docs:
> >
> > http://docs.ofbiz.org/x/mQ
> > http://docs.ofbiz.org/x/r
> >
> > If you want to know more about licensing and legal issues, read the
> > docs:
> >
> > http://incubator.apache.org/incubation/Incubation_Policy.html
> > http://incubator.apache.org/ip-clearance/index.html
> > http://www.apache.org/foundation/how-it-works.html
> > http://www.apache.org/foundation/licence-FAQ.html
> > http://www.apache.org/legal/src-headers.html
> >
> > For a lot of good information, broaden the scope and study under:
> >
> > http://www.apache.org/dev/
> >
> > These were not written because someone was looking for some
> > entertainment. They were written so things wouldn't have to be
> > explained over and over.
> >
> > I'm calling it a day now, as soon as I take care of some real issues,
> > and as long as my son with the flu doesn't throw up again. Sorry,
> > this is really frustrating, and really silly. Reality sucks, but we
> > all have to live with it.
> >
> > If people want to help, then help. Don't just ask for help. Start by
> > being a giver, not a taker.
> >
> > If this sounds a bit harsh, great! Go for a walk and think about how
> > things work in real life, then read it again. If you're still upset,
> > read it again. Then go read all of the documents referenced. Then if
> > you still have a question, send it on in, but PLEASE try to look at
> > it from the point of a MEMBER of the OFBiz community, and not a user
> > of OFBiz who really doesn't want to get involved.
> >
> > If you're asking "how are you going to solve this problem" then
> > you're asking the wrong question. If you want to participate as "how
> > can I solve this problem", if "I" can't, then do with "how can we
> > solve this problem". I don't mean that is what should be in your
> > email, I mean that is what should be in your head. If you can't find
> > an answer yourself that is 100% okay, just start a discussion and
> > accept what you asked for.
> >
> > If you don't like the answer explain why it doesn't work for you,
> > which brings us back to the beginning of this email...
> >
> > -David
> >
> >
> > On Jan 25, 2007, at 6:10 PM, Daniel Kunkel wrote:
> >
> > > David
> > >
> > > Can you explain your reticence to adding an Apache OFBiz sandbox where
> > > more members of the community could share their work?
> > >
> > > I can see this section possibly getting a disorganized over time with
> > > *junk*... but it can be deleted easily enough. As a top level project
> > > would it possible and better to organize a sub project for this?
> > >
> > > Thanks
> > >
> > > Daniel
> > >
> > >
> > >
> > > On Thu, 2007-01-25 at 12:41 -0800, Chris Howe wrote:
> > >> 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" <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 ([hidden email]) 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 ===
> > >>
> > > --
> > > 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
> > > *-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-
> > >
> >

Reply | Threaded
Open this post in threaded view
|

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

jonwimp
In reply to this post by jonwimp
Oh dear, I meant to write to Daniel Kunkel, not David Kunkel.

Jonathon

Jonathon -- Improov wrote:

> David,
>
> Just a brief response here.
>
> Sandbox can be created outside of the OFBiz SVN. Even your personal
> branch (assuming you do an "SVN copy/branch" from the OFBiz SVN trunk,
> not your read-only workspace containing the downloaded OFBiz) is a sandbox.
>
>  > - A sandbox with lots of committers isn't going to work. Thanks for
>  > explaining that in your e-mail, I didn't realize this wasn't
>  > workable till now.
>
> David's right. If an OFBiz SVN trunk isn't working as well as we'd all
> like it (given limited committers' resources to audit and/or to commit
> patches), then a sandbox given a disorganized ragtag (at least I
> consider myself ragtag) team of committers won't work either (too many
> cooks).
>
>  > Would it work to have a sandbox that is managed by the existing
>  > committers, or perhaps a few new committers? As a committer, you
>  > wouldn't need to give nearly the same amount of time and attention to
>  > trying to make sure the commitment met best practices, free of bugs,
>  > etc. Any developer could share their stuff that they've implemented for
>  > their business, or other neat components. And, since the commitments
>  > would be in svn on the other side of the "Donate to the Apache
>  > Foundation legal radio button, it'd be easy for these developers to
>  > collaborate and slowly bring unworkable buggy messes into gold. Finally,
>  > users could easily find and try the components without mucking with
>  > patch files, etc.
>
> I (and some others) are currently looking to "round off loose ends" in
> OFBiz (for easy successful demonstration to business clients, not IT
> folks). We're doing it in our own sandbox. If you'd like to join us, let
> me know.
>
> Our sandbox will contain many patches that won't be in OFBiz SVN. We
> (the ragtag team) will be responsible for crash-testing those patches to
> death before we submit them to OFBiz. I believe this is an excellent way
> to free up the OFBiz committers. We really test and audit our patches
> first before even posting to OFBiz committers, in the proper formats
> (see
> http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices)
> no less.
>
> We're trying to take the heat off of the committers, allowing for a
> playground without messing up the official OFBiz trunk for
> you/me/everybody, and create a structured way to submit patches to OFBiz
> for review.
>
> Well, at least that's my direction. The ragtag team isn't headed by me
> (I'm not paying).
>
> Jonathon
>
> Daniel Kunkel wrote:
>> Hi
>>
>> First, please understand I hold you in incredibly high regard, and
>> apologize for causing any frustration...  You and Andy have created an
>> amazing software tool that I'm basing my business on, and you've given
>> it away. I love that! As you can see, your efforts are now multiplying
>> in to a system that has a life of its own, which will eventually change
>> the face of many businesses throughout the world.
>> During this process, you've needed to exercise great control in choosing
>> what to allow into the project, and what to reject. Since I often update
>> my production system to the svn head, I'm very glad someone is there
>> watching, and if you think about it, it makes sense that access has been
>> very limited to just the professionals that have devoted themselves to
>> the project.
>>
>> However, as it grows, there are more and more newbies that want to help
>> in their little way. Many *non-committers* who have wanted to give back
>> to the project have been stifled and frustrated, often because their
>> contributions were not appropriate, but sometimes simply because the
>> committers are too busy to review/test/correct their contributions. In
>> other cases, the resultant solutions are too specific to just their
>> business, or as a employee, the business although willing to donate the
>> code back, was not willing to devote the time needed to make the
>> consumable by the project at large.
>> So, what can we do to create a space where non-committers can share
>> their bits with the community? Please understand, we are agreed that
>> neither of us would want their contributions running on a system.
>>
>> - The source forge sandbox isn't really a good fit, because, as Chris
>> has researched, the legal ramifications of donating it back to the
>> project outweigh the benefits begotten from the group effort.
>>
>> - Forcing developers to work alone isn't working very well.
>>
>> - A sandbox with lots of committers isn't going to work. Thanks for
>> explaining that in your e-mail, I didn't realize this wasn't workable
>> till now.
>>
>> - Jira isn't working.
>> - The wiki could possibly work, but it doesn't go through the legal
>> process with each submission, and I cringe even thinking of trying to
>> work with code in wiki. Eek.
>>
>> - Even using the wiki, to catalog which jira issues are "in play" is
>> unwieldy. Patch nightmare actually.
>>
>> David, can you think of way to make a space in this community where the
>> new/non-polished committers can easily share and play together with
>> their ideas where they won't hurt the bigger project until the
>> components are well proven?
>>
>> Would it work to have a sandbox that is managed by the existing
>> committers, or perhaps a few new committers? As a committer, you
>> wouldn't need to give nearly the same amount of time and attention to
>> trying to make sure the commitment met best practices, free of bugs,
>> etc. Any developer could share their stuff that they've implemented for
>> their business, or other neat components. And, since the commitments
>> would be in svn on the other side of the "Donate to the Apache
>> Foundation legal radio button, it'd be easy for these developers to
>> collaborate and slowly bring unworkable buggy messes into gold. Finally,
>> users could easily find and try the components without mucking with
>> patch files, etc.
>>
>> Thanks
>>
>> Daniel
>>
>> On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:
>>> Okay, I just wrote a huge thing and deleted it. There might have
>>> been  good stuff in there, but I am really frustrated because I've
>>> said it  all before and based on the comments from Chris it doesn't
>>> seem like  anything it making it out there.
>>>
>>> If you're not a lawyer, then reference documents and processes  
>>> already established.
>>>
>>> I'm not even going to bother going into detail unless people are  
>>> willing to:
>>>
>>> 1. describe their understanding of how what they want to do would be  
>>> done under current policy
>>> 2. describe why that doesn't work for what you want to do
>>> 3. describe how the existing processes need to changed in order to  
>>> accommodate it
>>>
>>> A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it  
>>> would create a huge mess. I'm afraid one of two things would happen:
>>>
>>> 1. nothing
>>> 2. a lot
>>>
>>> In the case of number 1 it's not worth the effort to set it up. In  
>>> the case of #2 it would required more effort to administer and  
>>> monitor than we have resources for in OFBiz. There is no way I'd
>>> even  think about doing this under the ASF umbrella because I am not  
>>> willing to take on the responsibility of vetting a large number of  
>>> committers and recommending them as committers in the ASF, which is  
>>> BIG DEAL, and a responsibility and some people seem to be forgetting  
>>> that.
>>>
>>> If you want to be a committer you have to help with the project. You  
>>> have to take ownership of it, defend it, be committed to it, and so  
>>> on. Okay, now I'm doing what I was in the 2 page email I just
>>> deleted  and I'm stopping.
>>>
>>> If you want to know more about becoming and being a committer and  
>>> about contributing to OFBiz, READ THE DARN DOCUMENTS!
>>>
>>> I don't know WHY these questions are coming up here. Stop asking  
>>> them. Read the documents. I won't be baited into this any more. It's  
>>> a waste of time, and all based on supposition and not any real  
>>> problems or issues as far as I can see.
>>>
>>> If you develop something outside of OFBiz and want to contribute it,  
>>> here is the page describing how it works:
>>>
>>> http://incubator.apache.org/ip-clearance/index.html
>>>
>>> This is basically a streamlined incubation process for code going  
>>> into existing projects.
>>>
>>> If you really want to help and be involved in the project it means  
>>> working on OTHER PEOPLE'S STUFF, NOT YOUR OWN! Yes, it makes it  
>>> easier to get your own stuff in but if that is all you're about  
>>> related to the project, then being a committer isn't for you.
>>>
>>> If you want to know more about contributing and being a committer,  
>>> read the docs:
>>>
>>> http://docs.ofbiz.org/x/mQ
>>> http://docs.ofbiz.org/x/r
>>>
>>> If you want to know more about licensing and legal issues, read the  
>>> docs:
>>>
>>> http://incubator.apache.org/incubation/Incubation_Policy.html
>>> http://incubator.apache.org/ip-clearance/index.html
>>> http://www.apache.org/foundation/how-it-works.html
>>> http://www.apache.org/foundation/licence-FAQ.html
>>> http://www.apache.org/legal/src-headers.html
>>>
>>> For a lot of good information, broaden the scope and study under:
>>>
>>> http://www.apache.org/dev/
>>>
>>> These were not written because someone was looking for some  
>>> entertainment. They were written so things wouldn't have to be  
>>> explained over and over.
>>>
>>> I'm calling it a day now, as soon as I take care of some real
>>> issues,  and as long as my son with the flu doesn't throw up again.
>>> Sorry,  this is really frustrating, and really silly. Reality sucks,
>>> but we  all have to live with it.
>>>
>>> If people want to help, then help. Don't just ask for help. Start by  
>>> being a giver, not a taker.
>>>
>>> If this sounds a bit harsh, great! Go for a walk and think about how  
>>> things work in real life, then read it again. If you're still upset,  
>>> read it again. Then go read all of the documents referenced. Then if  
>>> you still have a question, send it on in, but PLEASE try to look at  
>>> it from the point of a MEMBER of the OFBiz community, and not a user  
>>> of OFBiz who really doesn't want to get involved.
>>>
>>> If you're asking "how are you going to solve this problem" then  
>>> you're asking the wrong question. If you want to participate as "how  
>>> can I solve this problem", if "I" can't, then do with "how can we  
>>> solve this problem". I don't mean that is what should be in your  
>>> email, I mean that is what should be in your head. If you can't find  
>>> an answer yourself that is 100% okay, just start a discussion and  
>>> accept what you asked for.
>>>
>>> If you don't like the answer explain why it doesn't work for you,  
>>> which brings us back to the beginning of this email...
>>>
>>> -David
>>>
>>>
>>> On Jan 25, 2007, at 6:10 PM, Daniel Kunkel wrote:
>>>
>>>> David
>>>>
>>>> Can you explain your reticence to adding an Apache OFBiz sandbox where
>>>> more members of the community could share their work?
>>>>
>>>> I can see this section possibly getting a disorganized over time with
>>>> *junk*... but it can be deleted easily enough. As a top level project
>>>> would it possible and better to organize a sub project for this?
>>>>
>>>> Thanks
>>>>
>>>> Daniel
>>>>
>>>>
>>>>
>>>> On Thu, 2007-01-25 at 12:41 -0800, Chris Howe wrote:
>>>>> 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" <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 ([hidden email]) 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 ===
>>>>>
>>>> --
>>>> 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
>>>> *-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-
>>>>
>>
>>
>
>

Reply | Threaded
Open this post in threaded view
|

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

cjhowe
In reply to this post by jonwimp
Jonathon,

You are missing the whole legal obstacle.  

Given the IP clearances necessary in all of those wonderful legal links
that David provided, your rag tag team's collaborative contributions
cannot be submitted to Apache OFBiz and be accepted into the project in
the form that they're likely to be offered.

Any collaborative efforts on the ofbiz-sandbox project on
Sourceforge.net do not clear the IP hurdles.  As far as the discussion
surrounding the anon checkout process, that did not clear the IP
hurdles.  The manner in which the Developer's conference has been
proposed, does not clear the IP hurdles.  OFBiz itself did not clear
the IP hurdle.  

David,

IP law in America is insufficient to provide documented references so
everything regarding it has to do with the concepts that surround it
instead of actual legislation or clear case law.  Do a google search
for Intellectual Property Bankruptcy Case Law and you will see some
staggering rulings.

A few legal concepts, IANAL

See Joint authorship and Ownership
http://library.findlaw.com/1999/Jan/1/241478.html

Every person who writes code (not under contract) owns the copyright of
what they write, this is because each individual is a sole-proprietor.

When you collaborate with someone, you own the copyright for the
portion you write, and the other person owns the copyright for the
portion they write.  The problem occurs that the partnership between
the two of you owns the copyright for the work as a whole.  

Now, what's the big deal?

The findlaw link only refers to the assets, not the liabilities.
Say one of these partners goes to a client and says "So and So and me
worked on this part of the code and I guarantee that it works."  The
source code says plain as day "No guarantees".  However, because one of
the partners guaranteed it, the partnership has guaranteed it.  The
members of the partnership are now jointly and SEVERELY liable for the
fulfillment of that guarantee.  The person spouting out guarantees has
overstepped his authority in making the guarantee, but that only makes
him liable to his partners as it's not fraudulent.   The partnership is
still liable to the bad partner's client.    Again, both jointly and
SEVERELY.

How does this likely affect Apache?  Likely only distribution will be
affected, not financial.  If it's found that the code is owned by the
partnership and there is some IP problem arising in that partnership,
Apache can be served a cease and desist order and will need to pull
that contribution out by it's root as well as any derivative of that
contribution.  No big deal, we can code around contributions. However,
Apache then cannot make previous revisions available through SVN
either. With jars this isn't a big problem, however the manner in which
OFBiz is written with it's components and services, and the largest
likely contribution not being in jar format, it is a HUGE problem.

If this is simply not a problem that can be solved in Apache, fine, I
accept that and we'll just have to live with either keeping our
collaborative contributions out of Apache OFBiz source, live with
limits of JIRA and the time and expertise (though limited :-)
)constraints of the committers or continue to accept the risk of
including these contributions in OFBiz source.

There are at least five separate groups of community members (including
one that you're involved with) vocally trying to collaborate on
solutions that are beneficial to the OFBiz community at large that if
allowed to their own devices will create great contributions that no
one can benefit from without obtaining the source from disparate
locations, unless they choose to ignore the possible repercussions.  I
think this constitutes a need in the community.  

I am shocked that no one who can post to the legal-discuss list will.
The easier to beg forgiveness than to ask for permission has the
potential of large repercussions especially when we're talking about
software that is attempting to be the backbone of businesses.



--- Jonathon -- Improov <[hidden email]> wrote:

> David,
>
> Just a brief response here.
>
> Sandbox can be created outside of the OFBiz SVN. Even your personal
> branch (assuming you do an
> "SVN copy/branch" from the OFBiz SVN trunk, not your read-only
> workspace containing the downloaded
> OFBiz) is a sandbox.
>
>  > - A sandbox with lots of committers isn't going to work. Thanks
> for
>  > explaining that in your e-mail, I didn't realize this wasn't
>  > workable till now.
>
> David's right. If an OFBiz SVN trunk isn't working as well as we'd
> all like it (given limited
> committers' resources to audit and/or to commit patches), then a
> sandbox given a disorganized
> ragtag (at least I consider myself ragtag) team of committers won't
> work either (too many cooks).
>
>  > Would it work to have a sandbox that is managed by the existing
>  > committers, or perhaps a few new committers? As a committer, you
>  > wouldn't need to give nearly the same amount of time and attention
> to
>  > trying to make sure the commitment met best practices, free of
> bugs,
>  > etc. Any developer could share their stuff that they've
> implemented for
>  > their business, or other neat components. And, since the
> commitments
>  > would be in svn on the other side of the "Donate to the Apache
>  > Foundation legal radio button, it'd be easy for these developers
> to
>  > collaborate and slowly bring unworkable buggy messes into gold.
> Finally,
>  > users could easily find and try the components without mucking
> with
>  > patch files, etc.
>
> I (and some others) are currently looking to "round off loose ends"
> in OFBiz (for easy successful
> demonstration to business clients, not IT folks). We're doing it in
> our own sandbox. If you'd like
> to join us, let me know.
>
> Our sandbox will contain many patches that won't be in OFBiz SVN. We
> (the ragtag team) will be
> responsible for crash-testing those patches to death before we submit
> them to OFBiz. I believe
> this is an excellent way to free up the OFBiz committers. We really
> test and audit our patches
> first before even posting to OFBiz committers, in the proper formats
> (see
>
http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices)

> no less.
>
> We're trying to take the heat off of the committers, allowing for a
> playground without messing up
> the official OFBiz trunk for you/me/everybody, and create a
> structured way to submit patches to
> OFBiz for review.
>
> Well, at least that's my direction. The ragtag team isn't headed by
> me (I'm not paying).
>
> Jonathon
>
> Daniel Kunkel wrote:
> > Hi
> >
> > First, please understand I hold you in incredibly high regard, and
> > apologize for causing any frustration...  You and Andy have created
> an
> > amazing software tool that I'm basing my business on, and you've
> given
> > it away. I love that! As you can see, your efforts are now
> multiplying
> > in to a system that has a life of its own, which will eventually
> change
> > the face of many businesses throughout the world.
> >
> > During this process, you've needed to exercise great control in
> choosing
> > what to allow into the project, and what to reject. Since I often
> update
> > my production system to the svn head, I'm very glad someone is
> there
> > watching, and if you think about it, it makes sense that access has
> been
> > very limited to just the professionals that have devoted themselves
> to
> > the project.
> >
> > However, as it grows, there are more and more newbies that want to
> help
> > in their little way. Many *non-committers* who have wanted to give
> back
> > to the project have been stifled and frustrated, often because
> their
> > contributions were not appropriate, but sometimes simply because
> the
> > committers are too busy to review/test/correct their contributions.
> In
> > other cases, the resultant solutions are too specific to just their
> > business, or as a employee, the business although willing to donate
> the
> > code back, was not willing to devote the time needed to make the
> > consumable by the project at large.
> >
> > So, what can we do to create a space where non-committers can share
> > their bits with the community? Please understand, we are agreed
> that
> > neither of us would want their contributions running on a system.
> >
> > - The source forge sandbox isn't really a good fit, because, as
> Chris
> > has researched, the legal ramifications of donating it back to the
> > project outweigh the benefits begotten from the group effort.
> >
> > - Forcing developers to work alone isn't working very well.
> >
> > - A sandbox with lots of committers isn't going to work. Thanks for
> > explaining that in your e-mail, I didn't realize this wasn't
> workable
> > till now.
> >
> > - Jira isn't working.
> >
> > - The wiki could possibly work, but it doesn't go through the legal
> > process with each submission, and I cringe even thinking of trying
> to
> > work with code in wiki. Eek.
> >
> > - Even using the wiki, to catalog which jira issues are "in play"
> is
> > unwieldy. Patch nightmare actually.
> >
> > David, can you think of way to make a space in this community where
> the
> > new/non-polished committers can easily share and play together with
> > their ideas where they won't hurt the bigger project until the
> > components are well proven?
> >
> > Would it work to have a sandbox that is managed by the existing
> > committers, or perhaps a few new committers? As a committer, you
> > wouldn't need to give nearly the same amount of time and attention
> to
> > trying to make sure the commitment met best practices, free of
> bugs,
> > etc. Any developer could share their stuff that they've implemented
> for
> > their business, or other neat components. And, since the
> commitments
> > would be in svn on the other side of the "Donate to the Apache
> > Foundation legal radio button, it'd be easy for these developers to
> > collaborate and slowly bring unworkable buggy messes into gold.
> Finally,
> > users could easily find and try the components without mucking with
> > patch files, etc.
> >
> > Thanks
> >
> > Daniel
> >
> > On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:
> >> Okay, I just wrote a huge thing and deleted it. There might have
> been  
> >> good stuff in there, but I am really frustrated because I've said
> it  
> >> all before and based on the comments from Chris it doesn't seem
> like  
> >> anything it making it out there.
> >>
> >> If you're not a lawyer, then reference documents and processes  
> >> already established.
> >>
> >> I'm not even going to bother going into detail unless people are  
> >> willing to:
> >>
> >> 1. describe their understanding of how what they want to do would
> be  
> >> done under current policy
> >> 2. describe why that doesn't work for what you want to do
> >> 3. describe how the existing processes need to changed in order to
>  
> >> accommodate it
> >>
> >> A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it
>
> >> would create a huge mess. I'm afraid one of two things would
> happen:
> >>
> >> 1. nothing
> >> 2. a lot
> >>
> >> In the case of number 1 it's not worth the effort to set it up. In
>  
> >> the case of #2 it would required more effort to administer and  
> >> monitor than we have resources for in OFBiz. There is no way I'd
> even
=== message truncated ===

Reply | Threaded
Open this post in threaded view
|

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

jonwimp
David (Jones),

This sounds serious. But I can't understand some (or most) of it. All I know is this sounds like I
need to get every contributor to give some kind of "explicit consent" for us to keep the source
"clean", so that we can pump their contributions back to OFBiz tree.

David, er, help?

Chris,

 > There are at least five separate groups of community members (including one
 > that you're involved with) vocally trying to collaborate on solutions that
 > are beneficial to the OFBiz community at large that if allowed to their own
 > devices will create great contributions that no one can benefit from without
 > obtaining the source from disparate locations, unless they choose to ignore
 > the possible repercussions.  I think this constitutes a need in the
 > community.

That sentence is long. I'm lost. Which 5 groups? What need?

 > I am shocked that no one who can post to the legal-discuss list will. The
 > easier to beg forgiveness than to ask for permission has the potential of
 > large repercussions especially when we're talking about software that is
 > attempting to be the backbone of businesses.

Where's the legal-discuss list? How does forgiveness and permission weight against each other?
What repercussions?

Jonathon

Chris Howe wrote:

> Jonathon,
>
> You are missing the whole legal obstacle.  
>
> Given the IP clearances necessary in all of those wonderful legal links
> that David provided, your rag tag team's collaborative contributions
> cannot be submitted to Apache OFBiz and be accepted into the project in
> the form that they're likely to be offered.
>
> Any collaborative efforts on the ofbiz-sandbox project on
> Sourceforge.net do not clear the IP hurdles.  As far as the discussion
> surrounding the anon checkout process, that did not clear the IP
> hurdles.  The manner in which the Developer's conference has been
> proposed, does not clear the IP hurdles.  OFBiz itself did not clear
> the IP hurdle.  
>
> David,
>
> IP law in America is insufficient to provide documented references so
> everything regarding it has to do with the concepts that surround it
> instead of actual legislation or clear case law.  Do a google search
> for Intellectual Property Bankruptcy Case Law and you will see some
> staggering rulings.
>
> A few legal concepts, IANAL
>
> See Joint authorship and Ownership
> http://library.findlaw.com/1999/Jan/1/241478.html
>
> Every person who writes code (not under contract) owns the copyright of
> what they write, this is because each individual is a sole-proprietor.
>
> When you collaborate with someone, you own the copyright for the
> portion you write, and the other person owns the copyright for the
> portion they write.  The problem occurs that the partnership between
> the two of you owns the copyright for the work as a whole.  
>
> Now, what's the big deal?
>
> The findlaw link only refers to the assets, not the liabilities.
> Say one of these partners goes to a client and says "So and So and me
> worked on this part of the code and I guarantee that it works."  The
> source code says plain as day "No guarantees".  However, because one of
> the partners guaranteed it, the partnership has guaranteed it.  The
> members of the partnership are now jointly and SEVERELY liable for the
> fulfillment of that guarantee.  The person spouting out guarantees has
> overstepped his authority in making the guarantee, but that only makes
> him liable to his partners as it's not fraudulent.   The partnership is
> still liable to the bad partner's client.    Again, both jointly and
> SEVERELY.
>
> How does this likely affect Apache?  Likely only distribution will be
> affected, not financial.  If it's found that the code is owned by the
> partnership and there is some IP problem arising in that partnership,
> Apache can be served a cease and desist order and will need to pull
> that contribution out by it's root as well as any derivative of that
> contribution.  No big deal, we can code around contributions. However,
> Apache then cannot make previous revisions available through SVN
> either. With jars this isn't a big problem, however the manner in which
> OFBiz is written with it's components and services, and the largest
> likely contribution not being in jar format, it is a HUGE problem.
>
> If this is simply not a problem that can be solved in Apache, fine, I
> accept that and we'll just have to live with either keeping our
> collaborative contributions out of Apache OFBiz source, live with
> limits of JIRA and the time and expertise (though limited :-)
> )constraints of the committers or continue to accept the risk of
> including these contributions in OFBiz source.
>
> There are at least five separate groups of community members (including
> one that you're involved with) vocally trying to collaborate on
> solutions that are beneficial to the OFBiz community at large that if
> allowed to their own devices will create great contributions that no
> one can benefit from without obtaining the source from disparate
> locations, unless they choose to ignore the possible repercussions.  I
> think this constitutes a need in the community.  
>
> I am shocked that no one who can post to the legal-discuss list will.
> The easier to beg forgiveness than to ask for permission has the
> potential of large repercussions especially when we're talking about
> software that is attempting to be the backbone of businesses.
>
>
>
> --- Jonathon -- Improov <[hidden email]> wrote:
>
>> David,
>>
>> Just a brief response here.
>>
>> Sandbox can be created outside of the OFBiz SVN. Even your personal
>> branch (assuming you do an
>> "SVN copy/branch" from the OFBiz SVN trunk, not your read-only
>> workspace containing the downloaded
>> OFBiz) is a sandbox.
>>
>>  > - A sandbox with lots of committers isn't going to work. Thanks
>> for
>>  > explaining that in your e-mail, I didn't realize this wasn't
>>  > workable till now.
>>
>> David's right. If an OFBiz SVN trunk isn't working as well as we'd
>> all like it (given limited
>> committers' resources to audit and/or to commit patches), then a
>> sandbox given a disorganized
>> ragtag (at least I consider myself ragtag) team of committers won't
>> work either (too many cooks).
>>
>>  > Would it work to have a sandbox that is managed by the existing
>>  > committers, or perhaps a few new committers? As a committer, you
>>  > wouldn't need to give nearly the same amount of time and attention
>> to
>>  > trying to make sure the commitment met best practices, free of
>> bugs,
>>  > etc. Any developer could share their stuff that they've
>> implemented for
>>  > their business, or other neat components. And, since the
>> commitments
>>  > would be in svn on the other side of the "Donate to the Apache
>>  > Foundation legal radio button, it'd be easy for these developers
>> to
>>  > collaborate and slowly bring unworkable buggy messes into gold.
>> Finally,
>>  > users could easily find and try the components without mucking
>> with
>>  > patch files, etc.
>>
>> I (and some others) are currently looking to "round off loose ends"
>> in OFBiz (for easy successful
>> demonstration to business clients, not IT folks). We're doing it in
>> our own sandbox. If you'd like
>> to join us, let me know.
>>
>> Our sandbox will contain many patches that won't be in OFBiz SVN. We
>> (the ragtag team) will be
>> responsible for crash-testing those patches to death before we submit
>> them to OFBiz. I believe
>> this is an excellent way to free up the OFBiz committers. We really
>> test and audit our patches
>> first before even posting to OFBiz committers, in the proper formats
>> (see
>>
> http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices)
>> no less.
>>
>> We're trying to take the heat off of the committers, allowing for a
>> playground without messing up
>> the official OFBiz trunk for you/me/everybody, and create a
>> structured way to submit patches to
>> OFBiz for review.
>>
>> Well, at least that's my direction. The ragtag team isn't headed by
>> me (I'm not paying).
>>
>> Jonathon
>>
>> Daniel Kunkel wrote:
>>> Hi
>>>
>>> First, please understand I hold you in incredibly high regard, and
>>> apologize for causing any frustration...  You and Andy have created
>> an
>>> amazing software tool that I'm basing my business on, and you've
>> given
>>> it away. I love that! As you can see, your efforts are now
>> multiplying
>>> in to a system that has a life of its own, which will eventually
>> change
>>> the face of many businesses throughout the world.
>>>
>>> During this process, you've needed to exercise great control in
>> choosing
>>> what to allow into the project, and what to reject. Since I often
>> update
>>> my production system to the svn head, I'm very glad someone is
>> there
>>> watching, and if you think about it, it makes sense that access has
>> been
>>> very limited to just the professionals that have devoted themselves
>> to
>>> the project.
>>>
>>> However, as it grows, there are more and more newbies that want to
>> help
>>> in their little way. Many *non-committers* who have wanted to give
>> back
>>> to the project have been stifled and frustrated, often because
>> their
>>> contributions were not appropriate, but sometimes simply because
>> the
>>> committers are too busy to review/test/correct their contributions.
>> In
>>> other cases, the resultant solutions are too specific to just their
>>> business, or as a employee, the business although willing to donate
>> the
>>> code back, was not willing to devote the time needed to make the
>>> consumable by the project at large.
>>>
>>> So, what can we do to create a space where non-committers can share
>>> their bits with the community? Please understand, we are agreed
>> that
>>> neither of us would want their contributions running on a system.
>>>
>>> - The source forge sandbox isn't really a good fit, because, as
>> Chris
>>> has researched, the legal ramifications of donating it back to the
>>> project outweigh the benefits begotten from the group effort.
>>>
>>> - Forcing developers to work alone isn't working very well.
>>>
>>> - A sandbox with lots of committers isn't going to work. Thanks for
>>> explaining that in your e-mail, I didn't realize this wasn't
>> workable
>>> till now.
>>>
>>> - Jira isn't working.
>>>
>>> - The wiki could possibly work, but it doesn't go through the legal
>>> process with each submission, and I cringe even thinking of trying
>> to
>>> work with code in wiki. Eek.
>>>
>>> - Even using the wiki, to catalog which jira issues are "in play"
>> is
>>> unwieldy. Patch nightmare actually.
>>>
>>> David, can you think of way to make a space in this community where
>> the
>>> new/non-polished committers can easily share and play together with
>>> their ideas where they won't hurt the bigger project until the
>>> components are well proven?
>>>
>>> Would it work to have a sandbox that is managed by the existing
>>> committers, or perhaps a few new committers? As a committer, you
>>> wouldn't need to give nearly the same amount of time and attention
>> to
>>> trying to make sure the commitment met best practices, free of
>> bugs,
>>> etc. Any developer could share their stuff that they've implemented
>> for
>>> their business, or other neat components. And, since the
>> commitments
>>> would be in svn on the other side of the "Donate to the Apache
>>> Foundation legal radio button, it'd be easy for these developers to
>>> collaborate and slowly bring unworkable buggy messes into gold.
>> Finally,
>>> users could easily find and try the components without mucking with
>>> patch files, etc.
>>>
>>> Thanks
>>>
>>> Daniel
>>>
>>> On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:
>>>> Okay, I just wrote a huge thing and deleted it. There might have
>> been  
>>>> good stuff in there, but I am really frustrated because I've said
>> it  
>>>> all before and based on the comments from Chris it doesn't seem
>> like  
>>>> anything it making it out there.
>>>>
>>>> If you're not a lawyer, then reference documents and processes  
>>>> already established.
>>>>
>>>> I'm not even going to bother going into detail unless people are  
>>>> willing to:
>>>>
>>>> 1. describe their understanding of how what they want to do would
>> be  
>>>> done under current policy
>>>> 2. describe why that doesn't work for what you want to do
>>>> 3. describe how the existing processes need to changed in order to
>>  
>>>> accommodate it
>>>>
>>>> A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it
>>>> would create a huge mess. I'm afraid one of two things would
>> happen:
>>>> 1. nothing
>>>> 2. a lot
>>>>
>>>> In the case of number 1 it's not worth the effort to set it up. In
>>  
>>>> the case of #2 it would required more effort to administer and  
>>>> monitor than we have resources for in OFBiz. There is no way I'd
>> even
> === message truncated ===
>
>

Reply | Threaded
Open this post in threaded view
|

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

Tim Ruppert
In reply to this post by Daniel Kunkel
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

o:801.649.6594
f:801.649.6595

On Jan 26, 2007, at 3:04 AM, Daniel Kunkel wrote:

Hi

First, please understand I hold you in incredibly high regard, and
apologize for causing any frustration...  You and Andy have created an
amazing software tool that I'm basing my business on, and you've given
it away. I love that! As you can see, your efforts are now multiplying
in to a system that has a life of its own, which will eventually change
the face of many businesses throughout the world. 

During this process, you've needed to exercise great control in choosing
what to allow into the project, and what to reject. Since I often update
my production system to the svn head, I'm very glad someone is there
watching, and if you think about it, it makes sense that access has been
very limited to just the professionals that have devoted themselves to
the project.

However, as it grows, there are more and more newbies that want to help
in their little way. Many *non-committers* who have wanted to give back
to the project have been stifled and frustrated, often because their
contributions were not appropriate, but sometimes simply because the
committers are too busy to review/test/correct their contributions. In
other cases, the resultant solutions are too specific to just their
business, or as a employee, the business although willing to donate the
code back, was not willing to devote the time needed to make the
consumable by the project at large. 

So, what can we do to create a space where non-committers can share
their bits with the community? Please understand, we are agreed that
neither of us would want their contributions running on a system.

- The source forge sandbox isn't really a good fit, because, as Chris
has researched, the legal ramifications of donating it back to the
project outweigh the benefits begotten from the group effort.

- Forcing developers to work alone isn't working very well.

- A sandbox with lots of committers isn't going to work. Thanks for
explaining that in your e-mail, I didn't realize this wasn't workable
till now.

- Jira isn't working. 

- The wiki could possibly work, but it doesn't go through the legal
process with each submission, and I cringe even thinking of trying to
work with code in wiki. Eek.

- Even using the wiki, to catalog which jira issues are "in play" is
unwieldy. Patch nightmare actually.

David, can you think of way to make a space in this community where the
new/non-polished committers can easily share and play together with
their ideas where they won't hurt the bigger project until the
components are well proven?

Would it work to have a sandbox that is managed by the existing
committers, or perhaps a few new committers? As a committer, you
wouldn't need to give nearly the same amount of time and attention to
trying to make sure the commitment met best practices, free of bugs,
etc. Any developer could share their stuff that they've implemented for
their business, or other neat components. And, since the commitments
would be in svn on the other side of the "Donate to the Apache
Foundation legal radio button, it'd be easy for these developers to
collaborate and slowly bring unworkable buggy messes into gold. Finally,
users could easily find and try the components without mucking with
patch files, etc.

Thanks

Daniel

On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:
Okay, I just wrote a huge thing and deleted it. There might have been  
good stuff in there, but I am really frustrated because I've said it  
all before and based on the comments from Chris it doesn't seem like  
anything it making it out there.

If you're not a lawyer, then reference documents and processes  
already established.

I'm not even going to bother going into detail unless people are  
willing to:

1. describe their understanding of how what they want to do would be  
done under current policy
2. describe why that doesn't work for what you want to do
3. describe how the existing processes need to changed in order to  
accommodate it

A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it  
would create a huge mess. I'm afraid one of two things would happen:

1. nothing
2. a lot

In the case of number 1 it's not worth the effort to set it up. In  
the case of #2 it would required more effort to administer and  
monitor than we have resources for in OFBiz. There is no way I'd even  
think about doing this under the ASF umbrella because I am not  
willing to take on the responsibility of vetting a large number of  
committers and recommending them as committers in the ASF, which is  
BIG DEAL, and a responsibility and some people seem to be forgetting  
that.

If you want to be a committer you have to help with the project. You  
have to take ownership of it, defend it, be committed to it, and so  
on. Okay, now I'm doing what I was in the 2 page email I just deleted  
and I'm stopping.

If you want to know more about becoming and being a committer and  
about contributing to OFBiz, READ THE DARN DOCUMENTS!

I don't know WHY these questions are coming up here. Stop asking  
them. Read the documents. I won't be baited into this any more. It's  
a waste of time, and all based on supposition and not any real  
problems or issues as far as I can see.

If you develop something outside of OFBiz and want to contribute it,  
here is the page describing how it works:


This is basically a streamlined incubation process for code going  
into existing projects.

If you really want to help and be involved in the project it means  
working on OTHER PEOPLE'S STUFF, NOT YOUR OWN! Yes, it makes it  
easier to get your own stuff in but if that is all you're about  
related to the project, then being a committer isn't for you.

If you want to know more about contributing and being a committer,  
read the docs:


If you want to know more about licensing and legal issues, read the  
docs:


For a lot of good information, broaden the scope and study under:


These were not written because someone was looking for some  
entertainment. They were written so things wouldn't have to be  
explained over and over.

I'm calling it a day now, as soon as I take care of some real issues,  
and as long as my son with the flu doesn't throw up again. Sorry,  
this is really frustrating, and really silly. Reality sucks, but we  
all have to live with it.

If people want to help, then help. Don't just ask for help. Start by  
being a giver, not a taker.

If this sounds a bit harsh, great! Go for a walk and think about how  
things work in real life, then read it again. If you're still upset,  
read it again. Then go read all of the documents referenced. Then if  
you still have a question, send it on in, but PLEASE try to look at  
it from the point of a MEMBER of the OFBiz community, and not a user  
of OFBiz who really doesn't want to get involved.

If you're asking "how are you going to solve this problem" then  
you're asking the wrong question. If you want to participate as "how  
can I solve this problem", if "I" can't, then do with "how can we  
solve this problem". I don't mean that is what should be in your  
email, I mean that is what should be in your head. If you can't find  
an answer yourself that is 100% okay, just start a discussion and  
accept what you asked for.

If you don't like the answer explain why it doesn't work for you,  
which brings us back to the beginning of this email...

-David


On Jan 25, 2007, at 6:10 PM, Daniel Kunkel wrote:

David

Can you explain your reticence to adding an Apache OFBiz sandbox where
more members of the community could share their work?

I can see this section possibly getting a disorganized over time with
*junk*... but it can be deleted easily enough. As a top level project
would it possible and better to organize a sub project for this?

Thanks

Reply | Threaded
Open this post in threaded view
|

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

Adrian Crum
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
Reply | Threaded
Open this post in threaded view
|

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

jonwimp
In reply to this post by Tim Ruppert
Tim,

For some reason I can't quite put my finger on, I am confident that I can process patches to my
own sandbox faster than the OFBiz committers can process patches to OFBiz.

Maybe it's because I am becoming an OFBiz addict that I work on it tirelessly and relentlessly? I
don't know.

And also, for some reason that escapes me, my commits seem to be more tested and less unsettling
than some of OFBiz's.

Maybe it's because I don't have 10 paying clients to serve at once.

Or maybe I do understand the OFBiz framework enough to be able to do a "OFBiz-wide grep or other
scan" in order to check whether my patches break stuff. Sort of like what a good IDE will do,
probably. But I'm always stone-age, stick to simple tools (with good mind map).

There's still this need to put together stable audited releases. I'm sort of doing that with my
personal "sandbox" on my harddisk.

I can't guarantee I can do the same if I'm a committer in OFBiz myself.

Jonathon

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
>
> On Jan 26, 2007, at 3:04 AM, Daniel Kunkel wrote:
>
>> Hi
>>
>> First, please understand I hold you in incredibly high regard, and
>> apologize for causing any frustration...  You and Andy have created an
>> amazing software tool that I'm basing my business on, and you've given
>> it away. I love that! As you can see, your efforts are now multiplying
>> in to a system that has a life of its own, which will eventually change
>> the face of many businesses throughout the world.
>>
>> During this process, you've needed to exercise great control in choosing
>> what to allow into the project, and what to reject. Since I often update
>> my production system to the svn head, I'm very glad someone is there
>> watching, and if you think about it, it makes sense that access has been
>> very limited to just the professionals that have devoted themselves to
>> the project.
>>
>> However, as it grows, there are more and more newbies that want to help
>> in their little way. Many *non-committers* who have wanted to give back
>> to the project have been stifled and frustrated, often because their
>> contributions were not appropriate, but sometimes simply because the
>> committers are too busy to review/test/correct their contributions. In
>> other cases, the resultant solutions are too specific to just their
>> business, or as a employee, the business although willing to donate the
>> code back, was not willing to devote the time needed to make the
>> consumable by the project at large.
>>
>> So, what can we do to create a space where non-committers can share
>> their bits with the community? Please understand, we are agreed that
>> neither of us would want their contributions running on a system.
>>
>> - The source forge sandbox isn't really a good fit, because, as Chris
>> has researched, the legal ramifications of donating it back to the
>> project outweigh the benefits begotten from the group effort.
>>
>> - Forcing developers to work alone isn't working very well.
>>
>> - A sandbox with lots of committers isn't going to work. Thanks for
>> explaining that in your e-mail, I didn't realize this wasn't workable
>> till now.
>>
>> - Jira isn't working.
>>
>> - The wiki could possibly work, but it doesn't go through the legal
>> process with each submission, and I cringe even thinking of trying to
>> work with code in wiki. Eek.
>>
>> - Even using the wiki, to catalog which jira issues are "in play" is
>> unwieldy. Patch nightmare actually.
>>
>> David, can you think of way to make a space in this community where the
>> new/non-polished committers can easily share and play together with
>> their ideas where they won't hurt the bigger project until the
>> components are well proven?
>>
>> Would it work to have a sandbox that is managed by the existing
>> committers, or perhaps a few new committers? As a committer, you
>> wouldn't need to give nearly the same amount of time and attention to
>> trying to make sure the commitment met best practices, free of bugs,
>> etc. Any developer could share their stuff that they've implemented for
>> their business, or other neat components. And, since the commitments
>> would be in svn on the other side of the "Donate to the Apache
>> Foundation legal radio button, it'd be easy for these developers to
>> collaborate and slowly bring unworkable buggy messes into gold. Finally,
>> users could easily find and try the components without mucking with
>> patch files, etc.
>>
>> Thanks
>>
>> Daniel
>>
>> On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:
>>> Okay, I just wrote a huge thing and deleted it. There might have been  
>>> good stuff in there, but I am really frustrated because I've said it  
>>> all before and based on the comments from Chris it doesn't seem like  
>>> anything it making it out there.
>>>
>>> If you're not a lawyer, then reference documents and processes  
>>> already established.
>>>
>>> I'm not even going to bother going into detail unless people are  
>>> willing to:
>>>
>>> 1. describe their understanding of how what they want to do would be  
>>> done under current policy
>>> 2. describe why that doesn't work for what you want to do
>>> 3. describe how the existing processes need to changed in order to  
>>> accommodate it
>>>
>>> A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it  
>>> would create a huge mess. I'm afraid one of two things would happen:
>>>
>>> 1. nothing
>>> 2. a lot
>>>
>>> In the case of number 1 it's not worth the effort to set it up. In  
>>> the case of #2 it would required more effort to administer and  
>>> monitor than we have resources for in OFBiz. There is no way I'd even  
>>> think about doing this under the ASF umbrella because I am not  
>>> willing to take on the responsibility of vetting a large number of  
>>> committers and recommending them as committers in the ASF, which is  
>>> BIG DEAL, and a responsibility and some people seem to be forgetting  
>>> that.
>>>
>>> If you want to be a committer you have to help with the project. You  
>>> have to take ownership of it, defend it, be committed to it, and so  
>>> on. Okay, now I'm doing what I was in the 2 page email I just deleted  
>>> and I'm stopping.
>>>
>>> If you want to know more about becoming and being a committer and  
>>> about contributing to OFBiz, READ THE DARN DOCUMENTS!
>>>
>>> I don't know WHY these questions are coming up here. Stop asking  
>>> them. Read the documents. I won't be baited into this any more. It's  
>>> a waste of time, and all based on supposition and not any real  
>>> problems or issues as far as I can see.
>>>
>>> If you develop something outside of OFBiz and want to contribute it,  
>>> here is the page describing how it works:
>>>
>>> http://incubator.apache.org/ip-clearance/index.html
>>>
>>> This is basically a streamlined incubation process for code going  
>>> into existing projects.
>>>
>>> If you really want to help and be involved in the project it means  
>>> working on OTHER PEOPLE'S STUFF, NOT YOUR OWN! Yes, it makes it  
>>> easier to get your own stuff in but if that is all you're about  
>>> related to the project, then being a committer isn't for you.
>>>
>>> If you want to know more about contributing and being a committer,  
>>> read the docs:
>>>
>>> http://docs.ofbiz.org/x/mQ
>>> http://docs.ofbiz.org/x/r
>>>
>>> If you want to know more about licensing and legal issues, read the  
>>> docs:
>>>
>>> http://incubator.apache.org/incubation/Incubation_Policy.html
>>> http://incubator.apache.org/ip-clearance/index.html
>>> http://www.apache.org/foundation/how-it-works.html
>>> http://www.apache.org/foundation/licence-FAQ.html
>>> http://www.apache.org/legal/src-headers.html
>>>
>>> For a lot of good information, broaden the scope and study under:
>>>
>>> http://www.apache.org/dev/
>>>
>>> These were not written because someone was looking for some  
>>> entertainment. They were written so things wouldn't have to be  
>>> explained over and over.
>>>
>>> I'm calling it a day now, as soon as I take care of some real issues,  
>>> and as long as my son with the flu doesn't throw up again. Sorry,  
>>> this is really frustrating, and really silly. Reality sucks, but we  
>>> all have to live with it.
>>>
>>> If people want to help, then help. Don't just ask for help. Start by  
>>> being a giver, not a taker.
>>>
>>> If this sounds a bit harsh, great! Go for a walk and think about how  
>>> things work in real life, then read it again. If you're still upset,  
>>> read it again. Then go read all of the documents referenced. Then if  
>>> you still have a question, send it on in, but PLEASE try to look at  
>>> it from the point of a MEMBER of the OFBiz community, and not a user  
>>> of OFBiz who really doesn't want to get involved.
>>>
>>> If you're asking "how are you going to solve this problem" then  
>>> you're asking the wrong question. If you want to participate as "how  
>>> can I solve this problem", if "I" can't, then do with "how can we  
>>> solve this problem". I don't mean that is what should be in your  
>>> email, I mean that is what should be in your head. If you can't find  
>>> an answer yourself that is 100% okay, just start a discussion and  
>>> accept what you asked for.
>>>
>>> If you don't like the answer explain why it doesn't work for you,  
>>> which brings us back to the beginning of this email...
>>>
>>> -David
>>>
>>>
>>> On Jan 25, 2007, at 6:10 PM, Daniel Kunkel wrote:
>>>
>>>> David
>>>>
>>>> Can you explain your reticence to adding an Apache OFBiz sandbox where
>>>> more members of the community could share their work?
>>>>
>>>> I can see this section possibly getting a disorganized over time with
>>>> *junk*... but it can be deleted easily enough. As a top level project
>>>> would it possible and better to organize a sub project for this?
>>>>
>>>> Thanks
>>>>
>>>> Daniel
>>>>
>>>>
>>>>
>>>> On Thu, 2007-01-25 at 12:41 -0800, Chris Howe wrote:
>>>>> 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" <[hidden email]
>>>>> <mailto:[hidden email]>> 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 <[hidden email]
>>>>>>> <mailto:[hidden email]>> 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 <[hidden email]
>>>>>>>> <mailto:[hidden email]>> 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 ([hidden email]
>>>>>>>>> <mailto:[hidden email]>) 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 ===
>>>>>
>>>> --
>>>> Daniel
>>>>
>>>> *-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-
>>>> Have a GREAT Day!
>>>>
>>>> Daniel Kunkel           [hidden email]
>>>> <mailto:[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
>>>> *-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-
>>>>
>>>
>>
>

Reply | Threaded
Open this post in threaded view
|

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

cjhowe
In reply to this post by Tim Ruppert
Tim,

If Anil and Ashish wrote anything in OFBIZ-510, then that's not
_exactly how anon checkout was created.  By quick glance, of the 61
messages containing the words OFBIZ-510 in them, you were the only one
who attached a patch, Anil and Ashish did not.  You three may have
passed patches amongst yourselves outside of the JIRA issue.  My
understanding is this constitutes collaboration and therefore the asset
you created is owned by the informal partnership between you three, not
one individual and not the ASF.

In regards to the patches vs SVN argument, I am not following your
logic at all.  SVN is a tool to manage patches.  That's what it is,
that's what it does.  How could individual patches be easier to
maintain than the tool that is designed to do that maintenance? Are you
talking about the collaboration part or just the part to merge back
into OFBiz?

A liberal sub-project SVN does not require patches be attached to a
JIRA issue until it's at a point to be contributed back into the major
work.  The collaborator simply commits his change.  That's what a
sandbox is for, to play in.  Unlike OFBiz itself, no one should expect
that the sandbox work.  At the time when it does work and it is
necessary to merge those changes back into the parent project, it will
require a single patch. Which because of the way OFBiz is set up, is
fairly small work.  That patch should have most bugs worked out and
testing is small work.

--- Tim Ruppert <[hidden email]> 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
>
> On Jan 26, 2007, at 3:04 AM, Daniel Kunkel wrote:
>
> > Hi
> >
> > First, please understand I hold you in incredibly high regard, and
> > apologize for causing any frustration...  You and Andy have created
> an
> > amazing software tool that I'm basing my business on, and you've
> given
> > it away. I love that! As you can see, your efforts are now
> multiplying
> > in to a system that has a life of its own, which will eventually  
> > change
> > the face of many businesses throughout the world.
> >
> > During this process, you've needed to exercise great control in  
> > choosing
> > what to allow into the project, and what to reject. Since I often  
> > update
> > my production system to the svn head, I'm very glad someone is
> there
> > watching, and if you think about it, it makes sense that access has
>  
> > been
> > very limited to just the professionals that have devoted themselves
> to
> > the project.
> >
> > However, as it grows, there are more and more newbies that want to
>
> > help
> > in their little way. Many *non-committers* who have wanted to give
>
> > back
> > to the project have been stifled and frustrated, often because
> their
> > contributions were not appropriate, but sometimes simply because
> the
> > committers are too busy to review/test/correct their contributions.
> In
> > other cases, the resultant solutions are too specific to just their
> > business, or as a employee, the business although willing to donate
>  
> > the
> > code back, was not willing to devote the time needed to make the
> > consumable by the project at large.
> >
> > So, what can we do to create a space where non-committers can share
> > their bits with the community? Please understand, we are agreed
> that
> > neither of us would want their contributions running on a system.
> >
> > - The source forge sandbox isn't really a good fit, because, as
> Chris
> > has researched, the legal ramifications of donating it back to the
> > project outweigh the benefits begotten from the group effort.
> >
> > - Forcing developers to work alone isn't working very well.
> >
> > - A sandbox with lots of committers isn't going to work. Thanks for
> > explaining that in your e-mail, I didn't realize this wasn't
> workable
> > till now.
> >
> > - Jira isn't working.
> >
> > - The wiki could possibly work, but it doesn't go through the legal
> > process with each submission, and I cringe even thinking of trying
> to
> > work with code in wiki. Eek.
> >
> > - Even using the wiki, to catalog which jira issues are "in play"
> is
> > unwieldy. Patch nightmare actually.
> >
> > David, can you think of way to make a space in this community where
>  
> > the
> > new/non-polished committers can easily share and play together with
> > their ideas where they won't hurt the bigger project until the
> > components are well proven?
> >
> > Would it work to have a sandbox that is managed by the existing
> > committers, or perhaps a few new committers? As a committer, you
> > wouldn't need to give nearly the same amount of time and attention
> to
> > trying to make sure the commitment met best practices, free of
> bugs,
> > etc. Any developer could share their stuff that they've implemented
>  
> > for
> > their business, or other neat components. And, since the
> commitments
> > would be in svn on the other side of the "Donate to the Apache
> > Foundation legal radio button, it'd be easy for these developers to
> > collaborate and slowly bring unworkable buggy messes into gold.  
> > Finally,
> > users could easily find and try the components without mucking with
> > patch files, etc.
> >
> > Thanks
> >
> > Daniel
> >
> > On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:
> >> Okay, I just wrote a huge thing and deleted it. There might have
> been
> >> good stuff in there, but I am really frustrated because I've said
> it
> >> all before and based on the comments from Chris it doesn't seem
> like
> >> anything it making it out there.
> >>
> >> If you're not a lawyer, then reference documents and processes
> >> already established.
> >>
> >> I'm not even going to bother going into detail unless people are
> >> willing to:
> >>
> >> 1. describe their understanding of how what they want to do would
> be
> >> done under current policy
> >> 2. describe why that doesn't work for what you want to do
> >> 3. describe how the existing processes need to changed in order to
> >> accommodate it
> >>
> >> A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it
> >> would create a huge mess. I'm afraid one of two things would
> happen:
> >>
> >> 1. nothing
> >> 2. a lot
> >>
> >> In the case of number 1 it's not worth the effort to set it up. In
> >> the case of #2 it would required more effort to administer and
> >> monitor than we have resources for in OFBiz. There is no way I'd
> even
> >> think about doing this under the ASF umbrella because I am not
> >> willing to take on the responsibility of vetting a large number of
> >> committers and recommending them as committers in the ASF, which
> is
> >> BIG DEAL, and a responsibility and some people seem to be
> forgetting
> >> that.
> >>
> >> If you want to be a committer you have to help with the project.
> You
> >> have to take ownership of it, defend it, be committed to it, and
> so
> >> on. Okay, now I'm doing what I was in the 2 page email I just
> deleted
> >> and I'm stopping.
> >>
> >> If you want to know more about becoming and being a committer and
> >> about contributing to OFBiz, READ THE DARN DOCUMENTS!
> >>
>
=== message truncated ===

Reply | Threaded
Open this post in threaded view
|

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

Daniel Kunkel
In reply to this post by Adrian Crum
I think I pretty much covered this in my other post, but I'll share the
few things I think could be done better.

1.) The original effort was submitted and not "lost" in the anals of
history even though it wasn't ready for prime time.

2.) You example worked because there were a small number of people
actively pushing something that happened rather fast, so the code did
not get too far out of date.

3.) You apparently worked on the code one at a time, and/or worked
together er separately to avoid any patching nightmares.

I'm not saying this the jira patch system doesn't work...  I'm saying I
think we could all benefit by creating a space for people to contribute
developments that aren't ready where it would be easy for others to work
on them piecemeal.

I think back and wonder how many of the developers out there worked on
projects specific to one business or another that DID not share it back
to the community because their efforts were not in a shape that could be
committed.

Thanks

Daniel



On Fri, 2007-01-26 at 08:11 -0800, Adrian Crum wrote:

> 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
--
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 
*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-

Reply | Threaded
Open this post in threaded view
|

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

Tim Ruppert
In reply to this post by jonwimp
Jonathon - I'm sure that you may be able to process patches VERY quickly - and that my friend, is a totally invaluable resource to have going on.  I mean please do more of them and report your findings, so that the project can move forward even more quickly.  It doesn't take a committer role to be actively involved in this. 

You may in fact grow into a role of a committer if you continue with the project and are able to help push the project forward as much as you appear to be motivated to do.  Thanks for being here - and keep up the JIRA testing - it means A LOT to all of us.

Cheers,
Tim
--
Tim Ruppert
HotWax Media

o:801.649.6594
f:801.649.6595

On Jan 26, 2007, at 10:00 AM, Jonathon -- Improov wrote:

Tim,

For some reason I can't quite put my finger on, I am confident that I can process patches to my own sandbox faster than the OFBiz committers can process patches to OFBiz.

Maybe it's because I am becoming an OFBiz addict that I work on it tirelessly and relentlessly? I don't know.

And also, for some reason that escapes me, my commits seem to be more tested and less unsettling than some of OFBiz's.

Maybe it's because I don't have 10 paying clients to serve at once.

Or maybe I do understand the OFBiz framework enough to be able to do a "OFBiz-wide grep or other scan" in order to check whether my patches break stuff. Sort of like what a good IDE will do, probably. But I'm always stone-age, stick to simple tools (with good mind map).

There's still this need to put together stable audited releases. I'm sort of doing that with my personal "sandbox" on my harddisk.

I can't guarantee I can do the same if I'm a committer in OFBiz myself.

Jonathon

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
o:801.649.6594
f:801.649.6595
On Jan 26, 2007, at 3:04 AM, Daniel Kunkel wrote:
Hi

First, please understand I hold you in incredibly high regard, and
apologize for causing any frustration...  You and Andy have created an
amazing software tool that I'm basing my business on, and you've given
it away. I love that! As you can see, your efforts are now multiplying
in to a system that has a life of its own, which will eventually change
the face of many businesses throughout the world. 
During this process, you've needed to exercise great control in choosing
what to allow into the project, and what to reject. Since I often update
my production system to the svn head, I'm very glad someone is there
watching, and if you think about it, it makes sense that access has been
very limited to just the professionals that have devoted themselves to
the project.

However, as it grows, there are more and more newbies that want to help
in their little way. Many *non-committers* who have wanted to give back
to the project have been stifled and frustrated, often because their
contributions were not appropriate, but sometimes simply because the
committers are too busy to review/test/correct their contributions. In
other cases, the resultant solutions are too specific to just their
business, or as a employee, the business although willing to donate the
code back, was not willing to devote the time needed to make the
consumable by the project at large. 
So, what can we do to create a space where non-committers can share
their bits with the community? Please understand, we are agreed that
neither of us would want their contributions running on a system.

- The source forge sandbox isn't really a good fit, because, as Chris
has researched, the legal ramifications of donating it back to the
project outweigh the benefits begotten from the group effort.

- Forcing developers to work alone isn't working very well.

- A sandbox with lots of committers isn't going to work. Thanks for
explaining that in your e-mail, I didn't realize this wasn't workable
till now.

- Jira isn't working. 
- The wiki could possibly work, but it doesn't go through the legal
process with each submission, and I cringe even thinking of trying to
work with code in wiki. Eek.

- Even using the wiki, to catalog which jira issues are "in play" is
unwieldy. Patch nightmare actually.

David, can you think of way to make a space in this community where the
new/non-polished committers can easily share and play together with
their ideas where they won't hurt the bigger project until the
components are well proven?

Would it work to have a sandbox that is managed by the existing
committers, or perhaps a few new committers? As a committer, you
wouldn't need to give nearly the same amount of time and attention to
trying to make sure the commitment met best practices, free of bugs,
etc. Any developer could share their stuff that they've implemented for
their business, or other neat components. And, since the commitments
would be in svn on the other side of the "Donate to the Apache
Foundation legal radio button, it'd be easy for these developers to
collaborate and slowly bring unworkable buggy messes into gold. Finally,
users could easily find and try the components without mucking with
patch files, etc.

Thanks

Daniel

On Fri, 2007-01-26 at 00:45 -0700, David E. Jones wrote:
Okay, I just wrote a huge thing and deleted it. There might have been  good stuff in there, but I am really frustrated because I've said it  all before and based on the comments from Chris it doesn't seem like  anything it making it out there.

If you're not a lawyer, then reference documents and processes  already established.

I'm not even going to bother going into detail unless people are  willing to:

1. describe their understanding of how what they want to do would be  done under current policy
2. describe why that doesn't work for what you want to do
3. describe how the existing processes need to changed in order to  accommodate it

A sandbox is a BAD BAD BAD BAD IDEA. Like you mentioned Daniel it  would create a huge mess. I'm afraid one of two things would happen:

1. nothing
2. a lot

In the case of number 1 it's not worth the effort to set it up. In  the case of #2 it would required more effort to administer and  monitor than we have resources for in OFBiz. There is no way I'd even  think about doing this under the ASF umbrella because I am not  willing to take on the responsibility of vetting a large number of  committers and recommending them as committers in the ASF, which is  BIG DEAL, and a responsibility and some people seem to be forgetting  that.

If you want to be a committer you have to help with the project. You  have to take ownership of it, defend it, be committed to it, and so  on. Okay, now I'm doing what I was in the 2 page email I just deleted  and I'm stopping.

If you want to know more about becoming and being a committer and  about contributing to OFBiz, READ THE DARN DOCUMENTS!

I don't know WHY these questions are coming up here. Stop asking  them. Read the documents. I won't be baited into this any more. It's  a waste of time, and all based on supposition and not any real  problems or issues as far as I can see.

If you develop something outside of OFBiz and want to contribute it,  here is the page describing how it works:


This is basically a streamlined incubation process for code going  into existing projects.

If you really want to help and be involved in the project it means  working on OTHER PEOPLE'S STUFF, NOT YOUR OWN! Yes, it makes it  easier to get your own stuff in but if that is all you're about  related to the project, then being a committer isn't for you.

If you want to know more about contributing and being a committer,  read the docs:


If you want to know more about licensing and legal issues, read the  docs:


For a lot of good information, broaden the scope and study under:


These were not written because someone was looking for some  entertainment. They were written so things wouldn't have to be  explained over and over.

I'm calling it a day now, as soon as I take care of some real issues,  and as long as my son with the flu doesn't throw up again. Sorry,  this is really frustrating, and really silly. Reality sucks, but we  all have to live with it.

If people want to help, then help. Don't just ask for help. Start by  being a giver, not a taker.
Reply | Threaded
Open this post in threaded view
|

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

Tim Ruppert
In reply to this post by Daniel Kunkel
Comments inline

On Jan 26, 2007, at 10:16 AM, Daniel Kunkel wrote:

I think I pretty much covered this in my other post, but I'll share the
few things I think could be done better.

1.) The original effort was submitted and not "lost" in the anals of
history even though it wasn't ready for prime time.

2.) You example worked because there were a small number of people
actively pushing something that happened rather fast, so the code did
not get too far out of date.


We also ensured that it didn't get out of date by updating our patches as things around them changed.  And yes, it was a smaller group of people, so it was easier to manage.

3.) You apparently worked on the code one at a time, and/or worked
together er separately to avoid any patching nightmares.

I'm not saying this the jira patch system doesn't work...  I'm saying I
think we could all benefit by creating a space for people to contribute
developments that aren't ready where it would be easy for others to work
on them piecemeal.

I definitely understand your pain here Daniel.  I would just ask the people who have these aspirations to try the existing system and first see how many people you actually get on board before building infrastructure to manage additional TEAMS of developers.


I think back and wonder how many of the developers out there worked on
projects specific to one business or another that DID not share it back
to the community because their efforts were not in a shape that could be
committed.


Having your code not be in shape enough to be committed probably never stopped anyone who really wanted their stuff to make it into the project :)  Open source is great and it does often bring out the best and works in people - I've always just taken the constructive criticism of people who have a bit more experience in the project - and that's always worked for me.

Cheers,
Tim

Thanks

Daniel



On Fri, 2007-01-26 at 08:11 -0800, Adrian Crum wrote:
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

o:801.649.6594
f:801.649.6595
-- 
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
*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-.,,.-*"*-



smime.p7s (3K) Download Attachment
123