You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
D. Joe 676266af38 Typo in unicode blog post 1 year ago
250bpm.com.md Link removed rather than changed to point to existing page for project. 1 year ago
README.md finally systematizing this, and also hey why not put my moldy and empty gitlab account to some use? 3 years ago
akura-typo.md * just another simple typo 2 years ago
creative-commons-terms.md duplicate text in CC wiki terms 2 years ago
dark-corners-of-unicode.md Typo in unicode blog post 1 year ago
docker-devicemapper-loop-lvm-doc.md docker doc loop-lvm doc word switch 2 years ago
dwheeler-evaluate-oss-fs.md dwheeler's busted link to IDA OS Migration docs with WBM version 2 years ago
firefox-bookmark-all-tabs-shortcut.md maybe the real bug is that none of the contextual menu items are meant to have hotkeys, or those hotkeys require a pointing device to reach them 2 years ago
flossmanuals-nl-xo.md this is the only one that's missing, and /sugar or /xo under nl.f.n do not work either 3 years ago
gitready-remote-tracking-cheatsheet-link.md from Nov 16 2 years ago
jkrieger-opensource.com-bio.md * simple editing mistake 2 years ago
libraryfreedomproject-mptk-cm.md * replace CM link with LineageOS link 2 years ago
libraryfreedomproject-mptk-oc-nc.md * replace CM link with LineageOS link 2 years ago
linode-api-v4-doc-old-end.md * I've got to get this stupid soft-wrap situation in hand 2 years ago
linode-custom-install.md * marking up device names to distinguish from surrounding text 2 years ago
manned.org.md Create entry for manned.org typo 1 year ago
monorepo-medium-oberlehner.md reading about monorepos 2 years ago
notes.md * converting notes file to .md format and brief ref to new file 3 years ago
org-mode-diary.md simple misspelling, but not 'du temps' 2 years ago
pygtk-main-sidebar.md markdownifying and slight edit for flow 2 years ago
pygtk-tutorial.md markdownifying and slight edit for flow 2 years ago
pythonspot-jinja2.md * Typo in pythonspot jinja2 tutorial 1 year ago
ralphbean-gitflow-nvie-pix.md * linkfication to presentation and author bio 2 years ago
rclone-manual-nextcloud.md * rclone manual misspells Nextloud 2 years ago
script-missing-dir.md The Ubuntu 16.04 implementation of the 4.4 BSD `script` program dumps core when trying to open a file in a non-existant directory. 1 year ago
snowdrift.md snowdrift 3 years ago
sugarlabs-wiki-on-fedora.md new links for Fedora sugar packages 2 years ago
threebean-gitflow-endofunctors.md 'homeomorphic endofunctors' comparison git tweet gone missing 2 years ago
tootstream-mastotech.md * oops. this is why I set my MIME types so that w3m can render Markdown: So I can proof .md files. 2 years ago
tor-googlecode-torsocks.md torsocks 3 years ago
whygitisbetter.md whygitisbetter, site abandonded, file still available 2 years ago
www.openinfra.org.md I seem to be encountering this routinely, wonder if there's some general amelioration of this being pursued. 3 years ago

README.md

random bug reports

In FOSS America, you don’t find bugs, bugs find you.

These are bugs that I stumble across, as one does, in the course of doing other things. As such, they are always a surprise and, usually, an annoyance. But, my stack can only get so deep, so to drop everything and try to document and report the bug to the right people in the right way is, to be honest, too much of a hassle for a lot of bugs that are more easily worked around or accomodated. Other times, there’s nothing I’d like better to do than to go haring off after the bug, but I don’t feel I can spend the time, because I already had a task I was supposed to be doing.

A lot of the bugs I meet which I feel I can address are pretty simple: Broken links or misspellings or grammar errors or other typos, or they’re wishlist items. So, in a lot of ways, these are harder bugs to deal with right off the bat because, unlike code, documentation and web sites often do not have source repositories or bug trackers set up, or, at least, that are as easy to find and navigate.

The first step of reporting a bug is to document it. Write down what happens. (Or, if this is how you work, or more appropriate to the task in some other way, to screenshot it, or to record video or whatever. Get a record, at any rate.)

So, my first impulse is to reach for my text editor. That’s where this repository comes in. I’m already used to checking in text changes and pushing them up to a public place, why not do this for my bug write ups?

This way, if the bug reporting mechanism is the “send an email” and I’ve already pushed a short write-up of the bug to this repository, I can just send a link!

If there is a more structured bug-reporting mechanism, at least I’ll have some of the details in hand wherever and whenever I am procrastinating hard enough that sending the report in seems to be an attractive way to spend the time.

So, we’ll see how this goes. Maybe if it works out, and I end up reporting these bugs and they get fixed, or they get fixed some other way, I’ll be able to git mv some-bug fixed/