Ubiquity commands should have ancestors and descendants

Since anyone can make their own Ubiquity commands and upload them to the Herd, and these different commands can do the same thing, possibly with the same name, there should be a way to specify which commands evolved out of which other commands. If you modify someone's command for your own use, you'd specify the previous author and previous URL in the meta-information, and when it uploads to the Herd, this relationship would be taken into account.

If you look on the Herd for a "Last.fm artist" command, for instance, and see three different variations, it should be obvious from the tree structure that the commands are listed in that one of the commands is a newer updated version that evolved out of another, which is no longer maintained, and that the third was written independently.

If the commands are copyrightable, specifying the previous authors and version history is actually a legal requirement for some open source licenses (incompletely solved by options.contributors). So this would kill two... uh... solve two problems at once.