Comments (6)
I agree that using Wiki rather than PR to readmes would remove a big barrier to functional contribution. Does the OCA Functional Workgroup has an opinion on this ? @TumbaoJu
from maintainer-tools.
Would be a great step to add images, videos, better and updated documentation.
Good suggestion! β€οΈ
from maintainer-tools.
I also find that contributions to READMEs are a little big barrier, even now that some are on markdown. In my team, functionals usually review the README, or even write it, but at the end a technician pushes it to OCA.
It is particularly frustrating in the sense that we have one code base per odoo version, which makes it hard for devs, but more even for functionals to know where to find instructions.
My suggestion would be:
- Enable public "wiki" feature in our github repos. It's the easiest way to get from zero to wiki.
- In the module templates, auto-add a badge that points to the correct place in the wiki. Of course, the badge will point to a non-existing page until somebody decides to create it. But at least, there'll be an official wiki gathering point.
- Discourage wiki-per-version. Just document the module itself. If something is only on some version, just indicate it with some kind of comment.
Possible problems: abuse. However people could abuse already through PR bombs or offensive comments and we don't have such a big problem on that. I guess we can handle it later if/when happens.
from maintainer-tools.
Discourage wiki-per-version. Just document the module itself. If something is only on some version, just indicate it with some kind of comment.
This is what we started to do in our doc, but it tends to hinder readability as the number of version grows, so we switched to one doc per version. It might be preferable, even if some versions are not up to date (in which case it should be indicated).
from maintainer-tools.
We must think that the module documentation also serves as in-odoo documentation.
Separating the files as the technical teams does, could help to split the work and will serve to avoid the headers (buttons) on the README file.
When PR [FIX][17.0] oca_module
is merged, ocabot will the contents of the code files into the repo/oca_module/17.0/xxx.file
files.
When repo/oca_module/17.0/xxx.file
is updated, after 1h (to avoid an avalanche of commits), ocabot will update the contents of the files as Weblate does.
from maintainer-tools.
Hello everybody!
Thank you for all your comments and suggestions. As you know, we have been working on OCA modules documentation and we are open to all ideas.
We explored different avenues for the module documentation such as :
- Github Wiki: https://docs.github.com/en/communities/documenting-your-project-with-wikis
- GitHub Pages : https://pages.github.com/
- https://squidfunk.github.io/mkdocs-material/
- https://js.wiki/ : integrated with GitHub
Wiki.js or external tool
- Would need more work to put in place
GitHub Pages
- Works with RST files, a lot like the Read Me on the modules, so less available / user friendly, difficult to upload images (complicated process)
- Works with PR and merge process, so need approval
Wiki GitHub : https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages
- Easy to use
- Written in Markdown with editor and preview
- Clean and unify page layout
- Easy to add images by drag & drop
- Already available on the repos GitHub
- We could add an automatic link to the wiki page on the read me (top bar) like the links to Runboat for example.
- Ready to use (except for the automatic link in the Read Me)
- No approval / PR process, everybody can contribute
-- Less of a risk because it is only documentation
So our first recommandation was to try and test the Wiki on the repositories.
We did a bit of tests on that but then the idea of having 2 different places for the documentation (The Read Me AND the Wiki) became a problem hence the idea of ββusing the Read Me but converting it into a more accessible format.
We are still working on "How can we make this more accessible to functionals".
So thank you for all your ideas. We will take it into consideration.
@manuelfcordoba @florenciafrigieri2 @lfreeke @francesco-ooops @vdewulf
from maintainer-tools.
Related Issues (20)
- Add a new CONTEXT section into README.rst HOT 6
- False warning C7902(missing-readme) on some repo HOT 3
- pre-commit crashes in CI HOT 1
- Documentation for the best way to manage a high number of OCA repositories HOT 11
- I faced with error while using this module in pre-commit. HOT 1
- About squashing translation commits HOT 2
- Update our tooling to support Odoo 17 HOT 20
- Mention `odoo-module-migrator` in migration procedure wiki page HOT 1
- Mention `oca-port` in migration procedure wiki page HOT 6
- oca-gen-addon-readme: exits with no error if `description.rst` is not present HOT 14
- Update migration v17 Wiki HOT 2
- Clarify CONTRIBUTOR.md formatting HOT 20
- Wiki migration 17.0: New Settings format HOT 1
- oca-gen-addon-readme: stop emitting an XML declaration HOT 1
- Fail to run pre-commit on OCA project: ERROR No matching distribution found for setuptools_scm HOT 2
- Update wiki "Migration to version 16.0" with `fields_view_get` becomes `get_view` HOT 2
- Mention data-hotkey in the 15.0 migration guide
- delete
- module 'github3' has no attribute 'authorize'
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from maintainer-tools.