1. Mailing Lists
  2. Contributors
  3. Re: Odoo Storage Repository

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

RE: Odoo Storage Repository

Re: Odoo Storage Repository

Avatar

Re: Odoo Storage Repository

by
dar
- 12/01/2019 01:14:48
Re: Pedro

Your suggestion reflects the thought tradition of paternalisc moderation.

What we need is pluralistic chaos. People are smart enough to judge by themselves, evolve, get inspired and converge.

It's just how all things are.

And if I might inspire you: If everything would be Odoo. This world would be a boring place. So there is no value in it.

Thankfully, there are tons of constantly morphing inspiring ecosystems out there. The question is: where are the smartest guys. Those will lead the way, in their way. Odoo?!? Wtf!?!?

;-)

El vie., 11 ene. 2019, 6:57 p.m., David Arnold <dar@xoe.solutions> escribió:
Simone,

Make it $2.00! ;-)

For a free (wo)man github.com/OCA has two attractions:

- Code sharing ( ..., including QA, licensing questions, etc. )
- Indexing

Like with any indexing function (eg google search) it drives best if it is content neutral (beyond enforcing legality and good manners).

Many people might feel: if something goes into OCA, it must be the canonical form (because of our we paternalistic responsabilizó es as a good librarian). However, this completely excludes the other attraction (code sharing / collaboration).

This is wrong.

OCA must become a place where both functions are disaggregated, that means where forms of code sharing can coexist with an evolutionary approach to canon.

I noticed that this is inherently reflected in the repo structure.

Topic repos, by nature have a double live:
- They index (in a non neutral way)
- They do code sharing

Ceterum censeo, a flat module-repo relationship would condensate the code sharing attraction around the pure and mature VCS functions.

Whereas the indexing function can have many distinct interfaces. And the value, it adds, can be preserved without the flaws.

Last, but not least: indexing is best achieved with multidimensional metadata. A good librarian would rather implement a selector function, than single dimension, flat, topic hierarchy.


That should solve all problems, past and future.

Best Regards,

David A.

El vie., 11 ene. 2019, 2:47 p.m., Enric Tobella <etobella@creublanca.es> escribió:
Pedro, you cannot exepct that the odoo environment is perfect for everything. Odoo is a great ERP, but it is not a file storage system. Also, right now you are unable to use two servers with odoo against the same DB because the file storage system is stored on a file repository(I know you can make shared folders, but do you think that is a good approach?).
 
IMO, we should keep Odoo as an ERP and use a good file storage system with odoo. A system cannot be perfect at all the options.
 
I will like to put a real history in order to show my point.
 
On Medical centers they usually have a PACS/RIS. That is a storage system for medical images (they are really big and have specific protocols). Fifteen years ago every expert was saying: "You must have a single server for all the RIS environment." They said that because that made a single truth and good for small centers. It was a good approach but had a lot of flaws, because a RIS system must store images and the user must view it. As you can imagine, good storage systems were bad viewers and great viewers were bad storage systems. Our IT department said that it was a terrible idea and created a Farm of servers in order to make an environment that was fast, reliable and also great for viewing. For years, everyone said that we were crazy. Why we had to do that? Easy, because that was the future. Right now, everyone is doing as our IT department said. We never publicized it, but in the end, the experts found the flaws that we found on the initial moment.
 
As I said, you cannot expect that Odoo is perfect for everything and it is a good approach to remove from odoo non critical systems. Attachments are important but it is not critical for Odoo and it will not be improved in order to be perfect. Currently there is a lot of systems specialized on file storage and we should use them when necessary.
 
Enric Tobella Alomar
 
Centros Médicos Creu Blanca
Tel: 902 202 230
 
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
 
From: "Pedro M. Baeza (Tecnativa)" <pedro.baeza@tecnativa.com>
To: "Contributors" <contributors@odoo-community.org>
Date: Fri, 11 Jan 2019 18:51:45 -0000
Subject: Re: Odoo Storage Repository
 
But this is where I want to go... You need this because you want to connect to other system. But why do you want to connect there? This is what we have to achieve, the missing pieces (ACLs, features, etc), that we want from the other system to be on Odoo itself.
 
Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe




Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Reference