<html><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:10pt"><div><span>Hi :)</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span>+1</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">We should NOT be editing "man" pages. They are primarily written by devs for devs and sometimes just about understandable for tier3, maybe tier2, IT Support. They are NOT for general consumption and definitely not for noobs! You probably understand most of them as you are all quite advanced users but even you will struggle with quite a bit of it. Well, i do. <br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif;
background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">When you install a program the "man" page usually gets copied onto your system as 1 tiny text file amongst many packages. The normal way to read it is to get to a command-line and type (for example)<br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">man firefox</div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px;
font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">which gives you a vi text-editor. They give a lot more detail than the quick-guide cheat-sheets. Compare that man with the <br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">firefox --help<br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">The advantage of this type of "manual" is that it is highly specific to the
particular version of the program that you have on your machine. The disadvantage is that it's almost pure geek and needs to remain that way so that other geeks understand it and can easily modify it when they update the package/program. <br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">There are other ways of reading the "man" pages that attempt to make it a bit easier to read. It is even possible to find man pages on the internet but then that breaks the number 1 best point about them which is how tightly specific it is for your particular version&build on your machine. </div><br>So i think we can make reference to the "man" pages, just as we can to the
quick-guide cheat-sheets, but in the same way i don't think we should be editing them and i think our wiki-pages should be more generic to cover a wider range of versions to avoid getting out-dated so quickly. It might be good to copy&paste chunks out of some and then re-write or edit to de-geekify but only for our own wiki or official docs. For example if you were editing the rsync page then it might be wise to have a look at the rsync man page to see if anything significant has changed (probably hasn't) and maybe re-word a few things. <br><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;">Regards from <br>Tom :) <br></div><div style="color: rgb(0, 0, 0); font-size:
13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span></span></div><div><br></div> <div style="font-family: verdana, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Elizabeth Krumbach Joseph <lyz@ubuntu.com><br> <b><span style="font-weight: bold;">To:</span></b> Ubuntu Doc <ubuntu-doc@lists.ubuntu.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Thursday, 19 September 2013, 17:45<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: man pages - was: wiki vs documentation<br> </font> </div> <div
class="y_msg_container"><br>On Thu, Sep 19, 2013 at 9:23 AM, Little Girl <<a ymailto="mailto:littlergirl@gmail.com" href="mailto:littlergirl@gmail.com">littlergirl@gmail.com</a>> wrote:<br>> Hey there,<br>><br>> Lars Noodén wrote:<br>><br>>> I would like to see the manual pages treated as official<br>>> documentation. At the very least, they should give a complete<br>>> summary of the function(s) and options without pointing to third<br>>> party materials. Some do, some don't. All should, because every<br>>> end user has these pages installed on their machine so it would<br>>> make sense to use them as the first line of support. There are<br>>> systems that take this approach and it works well for them so it<br>>> could work well for Ubuntu, especially if it is coordinated<br>>> upstream with Debian.<br>><br>> Where are the man pages kept?<br><br>They are
all published and searchable here: <a href="http://manpages.ubuntu.com/" target="_blank">http://manpages.ubuntu.com/</a><br><br>> Are they on Launchpad?<br>><br>> Are there guidelines for how they should be constructed?<br>><br>> Can any of us edit them? I wouldn't mind going to town on some of<br>> them. (:<br><br>Man pages are typically written by the upstream software project and<br>then just included in the packages we ship with Ubuntu. As such, any<br>edits of them should probably be done upstream rather than patching<br>the Ubuntu packages with our own additions, unless they are<br>Ubuntu-specific changes that we're looking to document.<br><br>-- <br>Elizabeth Krumbach Joseph || Lyz || pleia2<br><a href="http://www.princessleia.com/" target="_blank">http://www.princessleia.com</a><br><br>-- <br>ubuntu-doc mailing list<br><a ymailto="mailto:ubuntu-doc@lists.ubuntu.com"
href="mailto:ubuntu-doc@lists.ubuntu.com">ubuntu-doc@lists.ubuntu.com</a><br><a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc</a><br><br></div> </div> </div> </div></body></html>