--- /dev/null
+[[!meta title="Debbugs: Control at Submit time"]]
+
+One of the features that I have been asked for multiple times is the
+ability to use control@bugs.debian.org commands at
+submit@bugs.debian.org time. I have now implemented this with the
+following syntax:
+
+ Package: foo
+ Version: 1.0-3
+ Control: retitle -1 this is the title
+ Control: severity -1 bleargh
+ Control: summary -1 0
+ Control: forward -1 http://bugs.debian.org/nnn
+
+In short, you preface any control commands with Control:, -1 is the
+current bug, and the rest of each line is the control@ grammar you
+already know. This also now works for every kind of message to
+nnn@bugs.debian.org with the exception of messages received at
+nnn-done and nnn-forwarded. I don't know why you'd use it for anything
+else but submit@ messages, but hey, whatever works.
+
+
+[[!tag debian tech debbugs]]
--- /dev/null
+[[!meta title="Debbugs: outlook command"]]
+
+Neil McGovern asked me to add an additional feature to the BTS to
+support tracking the current status of attempts at fixing a bug. In
+past releases, we've used the nice commenting feature of
+bts.turmzimmer.net to keep track of what is going on in a particular
+nasty RC bug, who is working on it, and what needs to be done next (or
+if everyone can just ignore the bug).
+
+This feature should probably have already been in the BTS to start
+with, but now it is. In addition to the existing summary feature,
+where you can nominate a message or text to be the summary for a bug,
+there is an `outlook` command, which tracks the current status of the
+bug, and behaves in exactly the same way:
+
+ outlook 12345 not good
+ outlook 54321 0
+ thanks
+
+ I'm totally stymied by #54321.
+
+for example.
+
+I plan to include the outlook in the bugscan output in the future too,
+so it'll be easily accessible. (And possibly up-to-the-minute with
+some javascript-fu.)
+
+[[!tag debian tech debbugs]]
--- /dev/null
+[[!meta title="Wikipedia Deletion Reviews"]]
+
+Many community driven projects have a problem with overgrown
+bureaucratic processes reducing the desire and ability of casual
+contributors to contribute. Debian has struggled with this problem,
+with efforts like Debian Maintainers and sponsorship to address it,
+but it's insidious and difficult to completely overcome. I recently
+ran into this problem again with Wikipedia, where I'm a casual
+contributor (I probably average an edit a month).
+
+[[!agimg /2004/05_may/bot_garden_20040528/002_the_boojum_tree_20040528.jpg]] Sometime in 2006, I uploaded an image of a Boojum tree I took in 2004
+to Wikipedia to provide an image for the
+[Boojum tree](http://en.wikipedia.org/wiki/Boojum_tree) article. It
+wasn't a particularly awe inspiring image, as I took it while I was
+teaching second quarter freshmen biology on campus, and showing the
+students the awesome
+[Botanical Gardens at UCR](http://gardens.ucr.edu). In 2011, a
+Wikipedia user asked for deletion of the image because of some
+confusion about the copyright on the image, as
+[Apache::Gallery](http://apachegallery.dk/)'s default template footer
+contains Apache::Gallery's copyright. I didn't notice that during the
+7 day deletion review period because I rarely log into Wikipedia.
+
+A few days ago, I noticed the deletion and asked for a
+[Deletion Review](https://en.wikipedia.org/wiki/Wikipedia:Deletion_review).
+I assumed that my explanation that the copyright notice was for
+Apache::Gallery would be understood (or at least believed), and that
+at least the original reason for the deletion would be seen to be
+invalid. Instead, during
+[the process](https://en.wikipedia.org/wiki/Wikipedia:Deletion_review/Log/2012_June_26#File:Boojum_tree_ucr_botanical_garden.jpg)
+I was questioned as to whether I actually took the picture, why I used
+GPLv2+ for the pictures, whether I was claiming other people's images,
+and whether the image was actually good enough to be in Wikipedia in
+the first place. Hundreds of lines of text, an edit to the template in
+A::G, hours wasted, people still unsatisfied, and the potential
+contributor (myself) feeling so annoyed with the entire process that I
+bothered to write this blog entry.
+
+While I'm not sure what to do about Wikipedia, I've been forcibly
+reminded of how important enabling easy contributions are, and how
+alienated one can feel when one is stymied by them to the point that
+your (admittedly insignificant) contribution to a project no longer
+seems worth the effort.
+
+[[!tag debian tech wikipedia]]
---------------------
Like most computer languages, R uses variables as a means of storing
-information in memory and retrieving it later. A variable
+information in memory and retrieving it later. Variables can be
+assigned to using the `<-` or `=` operator. For example, to assign the
+number `5` to the variable `foo`, you would write
+
+[[!sweavealike echo=1 results="hide" code="""
+foo <- 5
+"""]]
+
+Variables can retrieved simply by referring to them by name. For
+example, to add `8` to the variable `foo` and store the result in
+`bar`, you would do the following:
+
+[[!sweavealike echo=1 results="hide" code="""
+bar <- foo + 8
+"""]]
+
In R, variables are more correctly called objects, because they have
-structure and do not directly refer to a memory.
+structure and do not directly refer to a specific memory location.
Basic Types
----------
--- /dev/null
+[[!meta title="pages tagged wikipedia"]]
+
+[[!inline pages="tagged(wikipedia)" actions="no" archive="yes"
+feedshow=10]]