... is to make its patches unnecessary, by getting the changes needed for any program to compile on DragonFly built right into the program.  (Often called "pushing patches upstream")  That usually means creating a patch and then tracking down the program authors to get them to include those changes in the next release of a project.  That tracking down can be a majority of the work.  In that case: thanks, Rumko! Update: Also, thanks, Matthias Rampke!  He did the same thing for pcc.
Matthias Scheler is looking for Postfix testers.  If you run it, he has a patch to version 2.8.1 he'd like you to try. Also, the final list of GTK1-using packages that are not actively updated has been determined.  These packages are leaving pkgsrc next week unless there's any last-minute intercessions.
I've linked to it before, but it's expanded since: the Google Summer of Code projects page on dragonflybsd.org has a whole lot of ideas listed.  Please add to it, especially if there's a project you'd like to be doing.  (Here's more thoughts, for example.)
Sascha Wildner's removed the meteor(4) code because it apparently no longer builds, and it's unlikely anyone uses an actual video board that requires this driver, at this point.  If you do, speak up.
The pcc compiler is nearing 1.0. (via) This is seen as a gcc alternative, and it's present in NetBSD/OpenBSD. I recall it didn't work for DragonFly because of a lack of TLS support... Might be different now, if anyone wants to try.  (see prior mentions on the Digest)
Matthew Dillon has continued his bridge work, with another commit adding various features.  Go, read.
Venkatesh Srinivas did a comparison of the default scheduler in DragonFly with the "fairqueue" scheduler, using Interbench, the "interactivity benchmark".  The numbers don't show a deficit relative to either side, which is OK I guess?  I'm not sure how to analyze it.
I posted before about a move to use AT&T's U-Verse fiber/DSL product for dragonflybsd.org's connection.  It led Matt Dillon to try to add features to compensate for the service's shortcomings, but it's still problematic.  He's written up just how broken U-Verse is, calling it "almost a complete failure" as a business connection.  The bulk of the problems seem to come from the 2Wire DSL modem supplied by AT&T. Remember when the Internet used to be the place to find long technical writeups of a product directly from people who were using it?  Much of that has disappeared into comment forms and ephemeral Facebook posts.  That's too bad.
If you're like me, you've been using XMMS for music playback since just about forever.  It's ancient, though.  It uses GTK1, and since Thomas Klausner is trying to get GTK1 dependencies out of pkgsrc, he listed a roundup of alternatives on the pkgsrc-users mailing list, most/all of which are in pkgsrc.  Pouya Tafti added some more.
You can probably infer the new (to me) blog I found this week from some of the links...
  • Adding IPv6 to a FreeBSD Mail/Web Server - from Michael Lucas, repeat BSD author.  I link to this because we're all going to have to do something similar in the next year or so, I bet..
  • A visual guide to TMUX, part 1 and part 2.  tmux has usually been introduced to me as "It's BSD-licensed and not screen", which is good, but not compelling on its own.  The first of the articles linked here goes over the comparative differences in some detail.  (via)
  • Speaking of screen-ish things, do you leave an irssi session running in screen so that you can rejoin IRC conversations at any time?  I sure do.  Sometimes I even reconnect through ConnectBot on my Android phone.  There's now a Connectbot variation for irssi, just for people who do such a thing.  Don't forget: #dragonflybsd on EFNet.
  • Also still on the topic: forgetting to use screen and then being stuck with a long-running process is lousy.  There's ways to deal with it, though.  (via, from a blogroll link)
  • Hey, it's neat to see a new business built on BSD - OpenBSD, in this case: Tunnelr.  (via)
  • We're still doing great in terms of pkgsrc packages building successfully on DragonFly.
  • An hour+ recording of the recent NYCBUG meeting about BSD networking is online.  (Link is to a MP3 - via)
  • How not to comment code.
  • AT&T -> BSD -> AT&T.
Matthew Dillon has added transparent bridging, mostly to overcome issues with the AT&T DSL modem he's using.  With this non-default feature, IP packets retain the original MAC address when retransmitted through a new interface.
Thomas Klausner is planning to get rid of the last bits of GTK1 in pkgsrc, which means some old/non-updated software has to go too.   Speak up on the pkgsrc-users@netbsd.org mailing list if you need some of that listed software, or (better yet) provide patches to move it to GTK2.
For those of you thinking of IPv6 (and you should be), Matthias Rampke reported good luck with an IPv6 tunneling service.  He points out that the /48 address he now has at home is larger than the entire IPv4 network.
The virtio network drivers for DragonFly (mentioned previously here, here, and here) went away.  Apparently the original FreeBSD code was not supposed to be available publicly, under a BSD license, and it's having a knock-on effect for DragonFly and probably NetBSD. (virtio drivers, if this is an unfamiliar term, are for devices in virtual environments, as when DragonFly is running under VMWare or something similar.)
February's BSD Magazine is headlining "ZFS on FreeBSD", along with a bunch of other material, including an interview/example for the next BSDCan convention.  There's some BSD-project-specific news in there from this site about DragonFly, along with MirOS, MidnightBSD, and FreeBSD.