I can see the following options: 1. We store compo...
# sig-documentation
y
I can see the following options: 1. We store component’s docs in the component’s repo. That requires to make support branches it seems. If there is a typo in the doc, we either have to do a minor release or to use a docs version branch to fix it there (like we have in puppetdb/openvoxdb, see docs-x.y branches) 2. We store component’s docs in a separate repo (
*-docs
?). That decouples a component release and docs release. Though, one has to make changes in 2 repos (one is feature/fix in the component’s repo, one is to reflect it in docs repo). 3. We store all docs in a single repo (
openvox-docs
?). I guess we should discuss this during the next community call, if no opinions here. Meanwhile, feel free to inspire the choice here by pressing reactions below.
1️⃣ 1
2️⃣ 1
3️⃣ 5