Dudders spells "Dynamically Updating DNS Duly Embracing RSA SIG(0)" (with some poetic license). It points a domain name to a given IP address using the DNS UPDATE protocol and a SIG(0) signature. It is designed with embedded systems in mind and is especially useful as a dynamic DNS solution for a home modem/router with a dynamic IP.
Muxic is a minimal user interface to XMMS2. It is inspired by Winamp Classic's windowshade. It is only meant for controlling and monitoring playback, not for managing a media library or even a playlist. To actually play music, it relies on the XMMS2 (the X-platform Music Multiplexing System 2) daemon, and another XMMS2 client must be used to put some music in your playlist. Muxic's keybindings are based on a subset of Winamp Classic's keyboard shortcuts. Muxic announces track changes using Growl.
admittedly, i breezed through the essay, but:
what exactly is wrong with:
cvs co whatever
whatever they are, abolishing them will put port maintainers out of a job :p
"Why don't the tools that we use to develop software automatically capture the environment and software dependencies that are being used?"
Well I don't even use vim's autocompletion features, I sure wouldn't want it trying to calculate all dependencies :p. I'm quite happing writing that into configure.ac.
"... lack of modeling of the deployment environment..." Posix not good enough? That's why I write configure scripts (or rather have autoconf generate them for me). Why not let the host environment decide how IT wants things to be done, rather than doing this at the application level?
"Will it cause a software dependency conflict?" not under my gentoo system ;)
"developer/user collaboration" As a user, I'm quite happy to investigate how the developers want me to talk to them (whether it be mailing list, newsgroup, irc, bugzilla, forums). As a developer, I like the choice in choosing a communcation medium with users. If i'd rather help them interactively on irc, i'll do that. If I want bug-reports to be contributed via sourceforge style interface that sends an email somewhere I'll do that. This really doesn't have to be standardized IMHO.
Verifiability of software instantiation: I couldn't agree more, but it doesn't take much for the developer to work this out and add it to configure.
The essay resounds of what we're beginning to see and soon might have to suffer in the future M$ model (remote services, integrated automatic error reports, "registration of artifact use").