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

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: [odoo-berlin-2018] Odoo Storage Repository

Re: Odoo Storage Repository

Avatar

Re: Odoo Storage Repository

by
dar
- 09/01/2019 02:37:36
Joergs, 

Looks like you're pointing out problems of over-coercion and lack of coexistence in the OCA.

That's something that dampens not only your mood. If true platform-coop is the goal, then the canonical form must _naturally_ evolve over a longer period of _friendly_ and _collaborative_ coexistence.

Needs reform.

Best Regards,

David A.

El mar., 8 ene. 2019, 7:17 p.m., Frederik Kramer <frederik.kramer@initos.com> escribió:
Hi Joe, hi Jordi, hi all, 

i personally think the richness of open communities (say open source) lies predominately in one of its fundamental freedoms, 
namely the freedom to inspect and change. I think neither Acsone nor anybody else in the Odoo Community would mind
if you lay your solution on the desk (i.e. publicly share it under an OSS compliant license) and either do 
the comparison (function-wise) yourself or let he "magical"
community decide what better fits their needs (on the basis of real code). 

We at initOS for instance still missed to contribute (ashes on my head)
our PoC on the Odoo / NextCloud implementation (though it worked quite well in the research project and we also 
decided to open it all up since long). 

For instance I personally don't like Java and maintaining Java Stacks (but that's just my vision on the IT-world and maintainability). 
I perfectly know for instance that Alfresco does a way more in traditional document management than Nextcloud, however i feel most companies don't need it.

Having said this. I am very happy the valued colleagues of Acsone contributed their solution and invited
others to inspect, improve, share and contribute. It is up to the others (meaning me, you and other companies) 
to contribute their work openly to let the majority decide what approach to value more or which approach to contribute to. 

The only thing that misses so far is a section / way / method in OCA that helps to people to share their alternative PoC stage projects if any (for instance
i would - and this is mostly the reason for not having contributed it so far- consider our integration PoC and not OCA quality for the time being). 

But even it we had this (i.e. a PoC section) already in place, open source is kind of "standing on the shoulder of giants". Were the giant is usually the one
that is being first on some distinct functional matter. 

All in all i would strongly recommend you to review your solution in light of the Acsone solution as we don't need 50 connectors between Odoo and Alfresco but 
one really reliable on and only if there is a fundamental quantum leap ahead or diversion in functionality propose an additional project. 

A far better way would be cherry pick things that may be relevant of your approach and are missing in Acsones approach and issue some proper pull 
requests with functional add-ons or improvements. I am sure if they really do make sense and meet the OCA quality standard they will also be merged ;-) 

Cheers and good night

Frederik


Am Dienstag, den 08.01.2019, 22:47 +0000 schrieb Joerg Lorenz:


> Jordi: 


> 


> thanks for pointing this out, I would not dare to question anybodies work, but I would like to shed some light on the comparison with two facts: 


> We have been doing the Alfresco intergration since 2014, two years early already. I think that this chalks one up for experience. 


> We think that the solution of ours is very rich and complete when it comes to the whole functionality, interface, user rights management and usabilty with Alfresco


> 


> I share your opinion on the matter with contribution, however. This is why we have withdrawn our Zugferd in the light of the better solution from OCA. 


> 


> have a nice evening.


> 


> Joe


> 


> Von: "Jordi Ballester Alomar" <jordi.ballester@eficent.com>


> An: "Contributors" <contributors@odoo-community.org>


> Gesendet: Dienstag, 8. Januar 2019 13:22:21


> Betreff: Re: Odoo Storage Repository


> 


> Joerg,


> 


> Relating to Alfresco integration, you might be interested in this excellent work from Acsone: http://alfodoo.org that is open source. It was presented at Odoo Experience 2016. 


> 


> IHMO It's better to contribute back and help make Alfodoo than making double efforts and dividing.


> 


> Regards,


> Jordi.


> 


> 


> 


> On Mon, Jan 7, 2019 at 10:12 PM Joerg Lorenz <jlorenz@itis.de> wrote:


> > Hi Enric: 


> > 


> > thanks for the contributions regarding odoo and the storage of it's attachement. We share the opinion that the odoo docs do not belong to the odoo system itself, as it is not suitable for


> > documents and it's management. 


> > I wanted to point you attention to the part that we have done regarding Alfresco. https://www.itis-odoo.de/en_US/page/it-is-odoo-alfresco-version-12. Please stay tuned for a english version or


> > study the version 10 (https://www.itis-odoo.de/en_US/page/odoo-alfresco10) or youtube videos (https://youtu.be/BGrop08ae0k)


> > 


> > In particular we think that an uniform rights management system for access and usage grant is fundamantally important to make the best use of any storage system provided. We have combined the


> > access rights on LDAP, and use a service acccount to handle the rights management that is coming through the user interaction to set the permissions accordingly.


> > 


> > We are intending to bring our whole Alfresco solution into the OCA open source stack and thus could imagine that it could server as a key component.


> > 


> > Also please stay tuned for the release of odoo enhanced community version 12 (see https://odoo-partner.org/de_DE/get-enhanced)


> >  that we will launch in a few days (middle of January is expected). We have mostly looked into migration and considered what was reported by failtoodoo. We are currently in small beta with this


> > release. See odoo-partner.org for details.


> > 


> > I am happy to get comments and would be keen sharing thoughts.


> >  


> > Thanks, Joe


> > (for those who do :)


> > 


> > Von: "Enric Tobella" <etobella@creublanca.es>


> > An: "Contributors" <contributors@odoo-community.org>


> > Gesendet: Montag, 7. Januar 2019 18:36:53


> > Betreff: Odoo Storage Repository


> > 


> > Dear contributors,


> >  


> > I have been working on a new set of addons in order to move the file repository to other options (Hadoop, Alfresco, SSH...). With these modules, you may consider two different storage options for


> > two modules (depending on the security required) or to use two different storage systems, one for old files and one for new ones (for example, a new file server).


> >  


> > It works also with the odoo standard system.


> >  


> > I made a Proof of concept with the SSH repository, but I would like to work in other options.


> >  


> > I think this a goot addition to the OCA environment and I would like to propose a new repo for this set of modules.


> >  


> > You can find my original repo in the following link:


> >  


> > https://github.com/etobella/odoo-storage


> >  


> > Kind regards,


> >  


> > Enric Tobella Alomar


> > etobella@creublanca.es


> >  


> > Centros Médicos Creu Blanca


> > Tel: 902 202 23

> >  

> > 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.

> > 

> > 

> > 

> > 

> > 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

> > 

> > _______________________________________________

> > Mailing-List: https://odoo-community.org/groups/contributors-15

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe: https://odoo-community.org/groups?unsubscribe

> 

> 

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

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

Reference