Next Version Notes

[DocCyblade]

Use this as our on going release discussions.

On with the next release!

[DocCyblade]

@l-arnold - Going to take a break here. I have learned so much and thank you for your help with testing. We are a good team, and I look forward to improving this as I will be converting my current system of 3-4 paid softwares for my side jobs to Odoo v8 so I will be invested in keeping this updated for sure

Work is cranking up so don't be surprised if I go dark and radio silence for a week or two don't be alarmed. Hopefully the TKL core devs will take a look and when they do the next batch of upgrade we can get Odoo in!

[l-arnold]

Sounds very good. I'm i the same place, needing to get some work done.

I do have a short set of modules I would love to take on... But right now some normal work.

Send or text me phone/ email some time. If all fails we may be able to PM through turnkeylinux.com

Thanks again!

[DocCyblade]

Sounds good.

[l-arnold]

I've been thinking a functional way to add and subtract external modules would be "bash scripts" ,or something similar, that can be run which emulate how our "external modules" system work in building the ISO.

My only concern about them is that they will tend to "separate" the "build generation" of the base Odoo from the "module" uptake... I ran several of the "external mods" on our master build yesterday and it works quite easily. Ideally there would be some "controller" for the "addons" line in openerp-server.conf.

Technically the dating" could simply be tied togethether with a "commit date" that is similar to the git time on Odoo Proper. All of this leads to a "Git Update" process which would be very nice to build, I would think, into Webmin.

If this is there there would need to be a "database update" process that can also be invoked.

Thinking out loud. Perhaps this should be in the other repository, but fundamentally this is the only real difference right now as it is.

I don't think we should have "every additional" module. We might have a few "packages" as some require several elements to work. Testing yesterday told me that we should not just "throw everything from OCA in there, at least until the "how and the why" for each one is understood, tested and documented.

I do have a good working set right now. Exploring a bit more. Not too much.

[DocCyblade]

@l-arnold - Did you see that the repo was forked?

https://github.com/DocCyblade/tkl-odoo/network

[l-arnold]

I had not seen, but great to see. (I hope I didn't create anything new in that I missed my click placement and may have created a fork as well).... doesn't seem like it though.

Very exciting! Project anyway. https://github.com/turnkeylinux-apps

[l-arnold]

On my side I want to "weave" the l-arnold-branches back together (maybe abandon some branches) then just have a series of branches that define some "extra addons".

Looks like I can pull this "into master". I can also Merge my "dev-wip1" and "dev". Ultimately though I just want the "extra addons" being the variance. Thoughts on that approach?

[DocCyblade]

I've been thinking a functional way to add and subtract external modules would be "bash scripts" ,or something similar, that can be run which emulate how our "external modules" system work in building the ISO.

I think I read somewhere that you can add add-ons right from within Odoo? I know I saw a bunch of add-ons. Can you actually install an add-on or is this just a list from Odoo's website?

[l-arnold]

There are a a bunch of Addons that come with the Odoo Git Pull. (the odoo/addons folder
Technically, in a way, everything about Odoo acts like an "Addon" in that Apps, Modules, Addons (whatever differentiates them) all get "added" via settings. Many of them do come along with others (normally listed in dependencies).

That said, I think Odoo sets it up that you need a "contract" to pull others directly into your build. The Connector, which I am focused upon, is all about doing a GitPull from the OCA folders and updating the Addon's line to include each specific module in the line.

Seems there are easier ways... That said you don't want to pull outside modules "willy nilly". Sometimes they have Python dependencies etc (were generally in my original build, but come to think of it I need to compare the "before and after"...as I know you were delving into the Python world quite a bit in the TKL branch.

work work.

[DocCyblade]

If we would want to create a configuration script that would get a list of add-ons and allow you to install it just with a section via console script I think we need to take this outside of Turnkey. This way every odoo user could benefit from it no matter how they have it installed. Then once that is working, we can include that project into turnkey!

I think we would have the app (installed via GIT clone) one of the subdirectory would be a git module that would hold the "database" this is a GIT repo so, git pull would update the "database" This would then allow dynamic selection of the version of Odoo, so you only get add-ons listed for your version. This list is updatable via GIT so it would be easy to add more modules down the line or remove them.

I like this idea so much I started two new GIT repos, one for the app/scrip ohFig and ohFig Dataset I named it ohFig (I did not want to include "Odoo" in the name but I hint at it "oh" the "O" in Odoo and Fig for conFIG so Odoo Config = ohFig

I'll dabble when I can, maybe get some other in the community to punch around a bit. I think I'll write it in Python, as Odoo is written in this, and I want to learn it anyway.

[l-arnold]

We might even make an Odoo Module that can do this really.

Good idea about making it universal. Technically a "Bash Script" is pretty universal but an Odoo Module or something else to do as you describe. would be very cool.

Lets remember the "inside" and "outside" dependencies that may be required...

[DocCyblade]

Lets remember the "inside" and "outside" dependencies that may be required.

What do you mean by that?

[l-arnold]

Just as Odoo requires certain "python" or "related" packages along with the Git Clone/Pull

some Modules require other "python" or "related" packages along with their Git Clone/Pulls.

Normally documented in the view of the Module/App in settings.
Sometimes, like the Connector, it is important to go to the Online Documentation just to be sure.

Spreadsheet time again. Glad I remembered this.
When I started this whole thing I spent a lot of time comparing note and notes again about which dependencies would be required. I was wanting to get the Magento-Connector to be part of the build from the start...

No big. We'll just look at the lists.

[DocCyblade]

OK I understand. That would be one of the things that the script would do is know what dependencies are needed for each module and what install those dependencies. The data set our database part would have that information. We would make it module or so it would read the date is set and would be able to load list of modules/add-ons and then know what dependencies wouldn't be needed. The app/script would handle the reading/updating of the data set which would be a GIT repo.

The goal of the project would be to make Odoo easy to configure with third-party modules/add-ons.

Just thinking out loud

[l-arnold]

I wonder if we could have "Sub" sets.
I very much like having the general set of OCA modules available. I configured this myself in the end, but It really gives all the tools to run a business effectively having these available and installable (which they are for me). Some "Git Pull" scripts might help in the Appliance for other people.

[BillDStrong]

You can install the modules from OCA using pip, thanks to odoo-autodiscover. The OCA repos are already set up for this system. Odoo 10 has this functionality built in. You can add the necessary boilerplate to work with any odoo module, however. Since this uses pip, it automatically installs required python packages.

autodiscover also allows you to install to certain databases. All OCA addons are available, as well as meta packages that allow to install, for example, all the pos modules at one time.

odoo-autodiscover is the user facing tool, while setuptools-odoo is the server component for maintainers.

Here are some links for more info.
https://odoo-community.org/blog/oca-news-1/post/installing-oca-addons-the-easy-way-32
https://pypi.python.org/pypi/odoo-autodiscover
https://pypi.python.org/pypi/setuptools-odoo
http://wheelhouse.odoo-community.org/

[l-arnold]

@BillDStrong is adding valuable comments. As I have stated in a few places today, I would like us to look at what versions of Odoo should be included in the TKL Odoo Ap? Personally I would like to see both 8.0 and 10.0. Ideally we could provide an upgrade mechanism as well.

Following up more on Bill's comment directly, I would very much like to have implementation of the OCA addons be either built in, or made easily accessible. I need to understand the "auto-discover" methods more. From my perspective we could script some of this, though personally I like the Git Pull methods pretty well myself. As Bill says PIP does also work well and at times it is the only functional way to install some additional packages.