Community mailing list archives
Re: Shipping Module for v7.0by
Easypost provides an API connection to a large number of carriers including DHL and they continue to add new ones. It's relatively easy to add any new carriers they support to the module because the underlying connection to Easypost is already done. It's easier than trying to connect to each carrier's API separately.
You create an account with them and load your UPS, DHL, etc credentials.
If the demand is there I can add the Easypost support for DHL, it shouldn't take very long to do.
In addition to Easypost we've also integrated with Stamps.com so the code will handle multiple shipping APIs.
3Dbinpacking is not required, it just helps automate the process of selecting which box size you want to use in the shipment, you can also manually select the box or use a simple rule to pick a box if you're shipping product by the case.
On 4 Apr 2015, at 15:53, Chris Jones wrote:
I put a feature list up in the Indiegogo page and in the perks I offer training, support and customization depending on the level.
There is a 25 minute video that walks through the features too.
Thanks for your reply, and the great video! :)
Couple of questions more..
Over here in Europe the concept of EasyPost doesn't exist. Most companies would be interested in connecting with national post carries like DHL / DeutschePost. Could you throw some light on swapping the EasyPost with other carriers
I doubt if any corporations here in Europe would be interested in using 3dbinpacking.com. Seems like 3dbin is a major dependency – how do we in Europe go about this part of the functionality?
Or was the module built only with US-landscape in mind?
maybe I missed it, but could you please share the specification (feature list) of the module? Any documentation (as also quality-report) would be a great help.
Also, what support would you be willing to offer for users (especially the financial contributors) of the module?
Ashant – euroblaze.de
On 4 Apr 2015, at 2:38, Chris Jones wrote:I just launched an Indiegogo campaign for the module. It's been through the ringers in a couple of live, production databases. One for a 3PL warehouse company and another for a Magento E-Commerce site. We recently moved to created labels in the background so we don't have timeout issues with Odoo. It allows us to handle a huge volume for shipments.
This is an all or nothing campaign. For $5k we release what I have immediately. For $7500 we port to Odoo 8 and if we raise more we'll add more features.
I hope you'll contribute. If you have suggestions for features you'd like to see, let me know.
On Thu, Feb 26, 2015 at 4:37 PM, Caudal Eric < firstname.lastname@example.org  > wrote:
Even in AGPL you can think of an Indiegogo campaign: this is not incompatible (eg: the effort made the OCA on the connector).
AGPL forces you to distribute the code to the users but never said that you can sell the code. AGPL by nature just limits the business model for resale (as any user provided the code can make it public any time).
Nevertheless, if you communicate properly you can get a first funding that would cover your RD effort and provide the code to those who contribute first.
Let's not forget that contributors need to make a leaving as well :)
2015-02-27 1:08 GMT+08:00 Dominique Chabord < email@example.com  > :
I think we can avoid another generic discussion on licensing. Chris
made no mistake in his statements so far.
He can open an indiegogo campaign to improve an AGPL module for
Openerp V7 or/and create an AGPL module with Odoo V8 or/and wait for
LGPL licensing and create a proprietary module for Odoo V8? or V9?
(depending on versioning at that time).
In any case, an AGPL module must be available to all kinds of users,
and to everybody if you use the CMS or Shop module of Version 8.
Chris probably understood, that any proprietary module on V8? or V9?
will prevent the use of any AGPL module from the community, in
particular many localisations and industry specifics.
2015-02-26 17:47 GMT+01:00 Nicholas Riegel < firstname.lastname@example.org  >:In general, I think there is alot of misunderstand about open source
licenses, and not just in this thread or with the Odoo/OpenERP community.
My understanding is source code released under the LGPL is similar to the
GPL and also requires source code to be made available to parties the
software is distributed (sold, given away for free, etc) to. The difference
with the LGPL vs GPL is that proprietary and other non LGPL licensed code
can be linked, depend, extend, etc on the LGPL code. LGPL is also know as
the "Library" GPL. The official name is Lesser General Public License. AGPL
requires the source be made available to all users of the software over a
network and not just parties the software is distributed to.
Odoo / OpenERP - AGPL
Module - must be AGPL, AGPL + Odoo Private Use License
Odoo - GPL (only provided as an example)
Module - must be GPL (only provided as an example)
Odoo - LGPL
Module - can be released under any licenses, including (but not limited
to): closed source, GPL. LGPL, Apache, BSD, MIT, Mozilla, etc
I don't think OpenERP v7 will be converted to LGPL, although I am not 100%
sure since I do not hold the copyright for that code nor work for the
company who owns the majority of the copyright for the code (Odoo SA).
This is a good site about open source licenses, including links to the full
I hope this helps.
MD/DC: 240-343-ITPS (4877)
Skype ID: itpedia
Google Hangout: itpedia.solutions.@gmail.com 
"Powering our customers into the future by leveraging the distinct
advantages of open source software."
<img src=" cid:email@example.com  " name="Image1"
align="left" border="0" height="66" width="386">
On 02/26/2015 02:02 AM, Chris Jones wrote:
cite=" mid:CAK1zTiYe5MAborZPDjrTB4txvQ8MK1Wkx5bv2eYmg6okxPxkKw@mail.gmail.com  "
AGPL requires that any code be made available to users of that system. It
does not require that the code be made available to the public Internet, but
does not stop that distribution if it happens.
If anyone sees merit in a robust shipping module for openerp and would be
open to an indiegogo campaign let me know otherwise I'll probably wait until
it can be released under LGPL as a paid module.
On Feb 25, 2015 9:43 PM, "cubells" < firstname.lastname@example.org  > wrote:El 26/02/15 a les 00:28, Chris Jones ha escrit:AGPL does not force sharing of code to the general public. By open
source I mean that i would make it publically available and continuing
to support it.
I think you understand incorrectly the AGPL license: