howto post to this blog

firstly, please note that anything you submit to this blog is Public Domain and can be used and edited by anyone, even in a commercial project (but also in any free project.) this is easier than using for instance, the gnu fdl license, as not all the projects that benefit from this blog use that license. you can still use content from here, in gnu fdl content.

there are several ways you can post or contribute to this blog:

use the comment feature:

1. suggest a change- this is like a wiki, except you don't have to edit wiki code. all suggestions will be taken seriously, but not all suggestions will be followed. compare to wiki where no suggestions are taken seriously, and many changes are reverted. eh... wiki is good, no- great, but only if you're "in."

unless there is an important reason to remove them, suggestions will be left in place as comments even if they are not used, and they will be removed if they are incorporated into the main post.

2. comment with a url- please note that spam will be treated as spam, and (due to human imperfection and mistakes that are otherwise regretfully made) sometimes even a good url will be treated as spam :) but do feel Quite Free to post a url. if it is yours, say so and the contents will be added to the blog. otherwise, we will consider writing a blog entry ABOUT the url and its contents.

3. write a whole entry! we want to add entries to this blog. at this writing, it's unknown (by the author) how long a comment you can write. don't be bashful.

use murga's forum:

as of this writing, only one post on murga's puppylinux forum contains the string "**docme" - add this to the end of your post on the forum, and your post will be (manually) added here. it's that simple! also, if you add "**docme" to a comment on the forum, about a post you didn't write, it's just like "comment with a url" (above.) PLEASE DO NOT spam murga's forum with a post that says "docme" and contains nothing else, we're not advocating that sort of clutter.

two more things to consider:

1. (in theory) credits go to the contributers of each post- we will do our utmost (which may prove imperfect) to thank everyone involved in each post, at the bottom of each post. "thanks to:" also serves as an "i wrote this" signature:

thanks to: amish, everyone that participates *

*an example "thanks to" line.

2. ktwi: (known to work in...) if you know the version of puppy 1.07 / puppy 2.11 / grafpup 104 / muppy 006 etc, include it. many things here will work across many versions, but it's great to
note what version you are writing about :)

thanks to: amish, and You!