Thanks David! Those are great and can be adapted for use on our website. :)
On Nov 8, 2013 6:27 PM, David Gomes da...@elementaryos.org wrote:
https://hackpad.com/Reporting-elementary-OS-bugs-FUZeBaYBosQ Reporting
elementary OS bugs
Yeah, but I think UbuPhillip made a better one fro the IRC stuff here:
https://docs.google.com/a/elementaryos.org/document/d/1yyuYkKluaLJuUMpWGVkJpzWyBK8ZLIj4KhpwQz04giY/edit
On Mon, Nov 11, 2013 at 5:28 PM, Cassidy James cass...@elementaryos.orgwrote:
Thanks David! Those are great and can be
I know of one item I'd really like to see documented because I don't
understand it without docs. It's our CMake commands and config options. I
never knew some projects have make valadocs command and nobody seems to
know why it fails and what dependencies it's missing. It'd also be nice to
include
Yeah, even more customization guides are not worth the ink, but people
could collect the already existing ones together (so, posting them on
the gdoc and make sure that the author is using the CC-BY) and maybe
we can make one structured document out of it.
to the HIG: Maybe pics of good and bad
Hi,
*Under what license am I supposed to release my documentation?*
It is better to license them under
http://creativecommons.org/licenses/by/3.0/ instead of
http://creativecommons.org/licenses/by/2.0/.
So the note at the end of the document would be:
This work is licensed under a
Is there a doc about how to go about documenting code?
That will help us a lot.
On Nov 5, 2013 3:32 PM, David Gomes da...@elementaryos.org wrote:
Completely agreed Daniel, I guess teemperor listed my doc more as a doc
example rather than what we're gonna do.
However, thank you for reminding
I want to take the opportunity to remind everyone that we DO NOT need an
extended customization guide. There are plenty of great articles and websites
that cover these topics extensively.
When we're talking about user documentation, we want to show users how to do
things. Most of the time
7 matches
Mail list logo
