Contributors mailing list archives
Re: Discover the OCA priorities for 2021 proposed by the boardby
Juan Del Castillo Gómez
Ok, I'm agree with you too.
Now, I'm understanding that the documentation project take in account many things, besides Functional/Technical docs, like:
- Transversal topics ( queue, connector, connector-odoo2odoo ...) depending the Business Objectives and the Technical requirements, so it depends on the specific implementation. So, maybe some sections with recipes for different Business Cases should be appreciate.
- Versioning documentation is another gap, for example ReadTheDocs, like many others, manage versioning/branching/languages... and can be integrated with GitHub easily.
I appreciate your answers,
El lun, 24 may 2021 a las 11:42, Jairo Llopis (<firstname.lastname@example.org>) escribió:
I agree with Tom.Also, having that /docs folder would make migrations even harder. Would make it very hard to find docs of several modules. Would force us to maintain one docs version per module version.El sáb, 22 may 2021 a las 18:42, Tom (<email@example.com>) escribió:I am with you except for 1 thing: I think documentation is central and not tied to specific repositories. Because if you want to make a doc about one topic such as "syncing data" it will involve many repositories: queue, connector, connector-odoo2odoo, server-tools, bank-statement, edi....
The e-learning system is good but it is not so strong in wiki-like editing.
The "Migration" docs and "OCA guidelines" have become powerful docs that are much referred to; i think a central place such as that would be better for the docs, and then organized per each topic. Either on Github Wiki or on Github pages.
Coop IT Easy SCRL fs, Virginie Dewulf