No description
Find a file
2019-01-22 05:56:17 -05:00
250bpm.com.md Link removed rather than changed to point to existing page for project. 2018-12-31 12:28:38 -05:00
akura-typo.md * just another simple typo 2018-03-21 14:58:28 -04:00
creative-commons-terms.md duplicate text in CC wiki terms 2017-11-13 19:22:23 -05:00
dark-corners-of-unicode.md Typo in unicode blog post 2019-01-22 05:56:17 -05:00
docker-devicemapper-loop-lvm-doc.md docker doc loop-lvm doc word switch 2017-11-16 10:14:20 -05:00
dwheeler-evaluate-oss-fs.md dwheeler's busted link to IDA OS Migration docs with WBM version 2017-12-18 11:30:20 -05:00
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 2017-12-11 19:01:05 -05:00
flossmanuals-nl-xo.md this is the only one that's missing, and /sugar or /xo under nl.f.n do not work either 2017-10-16 15:48:44 -04:00
gitready-remote-tracking-cheatsheet-link.md from Nov 16 2017-12-11 19:00:26 -05:00
jkrieger-opensource.com-bio.md * simple editing mistake 2018-01-15 09:52:03 -05:00
libraryfreedomproject-mptk-cm.md * replace CM link with LineageOS link 2018-03-06 08:35:03 -05:00
libraryfreedomproject-mptk-oc-nc.md * replace CM link with LineageOS link 2018-03-06 08:35:03 -05:00
linode-api-v4-doc-old-end.md * I've got to get this stupid soft-wrap situation in hand 2018-04-10 09:06:31 -04:00
linode-custom-install.md * marking up device names to distinguish from surrounding text 2018-03-06 08:20:39 -05:00
manned.org.md Create entry for manned.org typo 2019-01-04 07:56:26 -05:00
monorepo-medium-oberlehner.md reading about monorepos 2017-12-29 13:16:23 -05:00
notes.md * converting notes file to .md format and brief ref to new file 2017-10-03 10:15:03 -04:00
org-mode-diary.md simple misspelling, but not 'du temps' 2017-12-12 14:22:00 -05:00
pygtk-main-sidebar.md markdownifying and slight edit for flow 2017-12-18 11:35:19 -05:00
pygtk-tutorial.md markdownifying and slight edit for flow 2017-12-18 11:35:19 -05:00
pythonspot-jinja2.md * Typo in pythonspot jinja2 tutorial 2019-01-08 15:36:06 -05:00
ralphbean-gitflow-nvie-pix.md * linkfication to presentation and author bio 2018-03-06 09:21:37 -05:00
rclone-manual-nextcloud.md * rclone manual misspells Nextloud 2018-05-20 10:01:34 -04:00
README.md finally systematizing this, and also hey why not put my moldy and empty gitlab account to some use? 2017-03-23 13:55:05 -04:00
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. 2018-12-31 12:11:30 -05:00
snowdrift.md snowdrift 2017-10-13 12:31:54 -04:00
sugarlabs-wiki-on-fedora.md new links for Fedora sugar packages 2017-12-18 11:30:50 -05:00
threebean-gitflow-endofunctors.md 'homeomorphic endofunctors' comparison git tweet gone missing 2017-12-29 12:45:36 -05:00
tootstream-mastotech.md * oops. this is why I set my MIME types so that w3m can render Markdown: So I can proof .md files. 2018-03-15 10:10:31 -04:00
tor-googlecode-torsocks.md torsocks 2017-10-13 11:14:39 -04:00
whygitisbetter.md whygitisbetter, site abandonded, file still available 2017-11-13 20:14:02 -05:00
www.openinfra.org.md I seem to be encountering this routinely, wonder if there's some general amelioration of this being pursued. 2017-10-23 11:17:19 -04:00

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/