<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi all,</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Is there a way to keep documentation just for LTS versions? Documentation should contain not only theory or best practices, but reproducible topologies/examples which can be tested(scriptable) when an LTS version is released, so documentation doesn't break.<br><br>These examples should include bridges, vxlan, macvlan, network namespaces, device mapping, uid mapping/user_ns, logging, haddening, etc.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I know core devs have released blogs to help people understand LXD/LXC, but many of those articles asume or need some concepts beforehand to implement them correctly.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">There's also the *.md file in the github page which are pretty good explaining each component of LXD. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">For now we have discussions, Core dev blogs, github *md files, lxd wiki, etc. Shouldn't be useful to have an official documentation channel? </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Just some thoughts.<br><br>Luis Michael Ibarra</div><div><br>On Jan 12, 2017, at 17:13, Fajar A. Nugraha <<a href="mailto:list@fajar.net">list@fajar.net</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jan 13, 2017 at 12:05 AM, brian mullan <span dir="ltr"><<a href="mailto:bmullan.mail@gmail.com" target="_blank">bmullan.mail@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>I guess I'd like to hear from other LXD users out there that would be interested in more general "how-to" guides for LXD being available.<br></div><br></div></div></div></div></blockquote><div><br></div><div>A helpful documentation would always be useful</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div></div>Myself, I'm not a sw developer and not overly familiar with Github's utilization. I suspect there may be alot of LXD users that are more <i>"integrators"</i> of technologies into LXD and perhaps not dev's or Github users but I could certainly be wrong.<br><br></div></div></div></blockquote><div><br></div><div>There are lots of "users" which are just that: users. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div></div>In my mind I'd like to see something very easy to edit/submit/change/search <i>by the general LXD community of users</i>... much like a wiki is. <br><br></div></div></blockquote><div><br></div><div>From my experience in other open source projects, "EASY to edit" doesn't matter much in the end. What matters most, is for someone to volunteer maintaining it.</div><div><br></div><div>What usually happens:</div><div>- there are only minimal documentation available (the devs focus on the code), most info are available from users list</div><div>- someone would volunteer to maintain some sort of documentation, or the devs would eventually get to it.</div><div>- after some time, the docs might end up lagging due to real life problems</div><div>- some incorrect, or works-but-confusing info would end up in the "wiki"</div><div>- no one would step up to be the new doc maintaner</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Maybe github is all those things and its my lack of familiarity & daily use of it that makes me feel otherwise but I think the fact that on the LXD Github there are currently only 85 contributors <i>(nearly all are coder/devs) makes me think that many people may just not know "how" to add LXD related "user" generated content like this via gitub</i>?<br><br></div></div></blockquote><div><br></div><div>There's a learning curve, but not really that hard.</div><div><br></div><div>Github also has a wiki, but I suspect the devs team don't enable that feature to make sure all info on the github page are accurate.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>Anyway I'd like to see what others think.<br></div><div><br></div><div>I have found: <a href="https://meta.miraheze.org/wiki/Miraheze" target="_blank">https://meta.miraheze.org/<wbr>wiki/Miraheze</a> which is a highly rated, <i>widely used, open source, and <u>free</u> hosting </i>wiki site that supports a visual editor, subscribing & auto-notification to topics/subjects, etc. But that is just one possibility for consideration for <i>a user-friendly, easy-to-use</i> alternative?<br><br></div></div></blockquote><div><br></div><div>One option to move forward, is for you to create the docs on whatever platform you see fit. Then link to it anytime a relevant question pop up on this list.</div><div><br></div><div>-- </div><div>Fajar</div></div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>lxc-users mailing list</span><br><span><a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a></span><br><span><a href="http://lists.linuxcontainers.org/listinfo/lxc-users">http://lists.linuxcontainers.org/listinfo/lxc-users</a></span></div></blockquote></body></html>