Some related posts from Technorati and Google.

[Lyrics Without Melody] Open Source Project Wiki: Each component should be given a wiki page (obviously a simple component template would be beneficial here), in which the following information could be defined: Component name, authors, current maintainer, who is working on it and what are they working on, status to next release, list of bugs associated with component, and documentation of that component. What makes the wiki great, is the simple fact that the text on it is written by a person, for people.

 [My Way] Human Interface Guidelines: HIG are nothing but documents which provide a set of recommendations which are to be followed while developing Graphical User Interface based Applications.They serve as a set of recommendations for the software developers while developing new software.These are not rules,just guidelines on how an application will "interface" on UI terms with the underlying Operating System.

[Ldodds.com] Lost Boy: Bootstrapping a Corporate Wiki: Using "inter wiki" linking features/macros I tied the Wiki into our Bugzilla installation, then into features on the test and public services. Our shared corporate drive had been descending into a mess for some time, and as it was available as HTTP over the internal network, I created an "Intranet" page on the Wiki and linked to every useful resource I could find on it.

 [Darcynorman.net] D’Arcy Norman Dot Net: For $30, you get a better-than-new iPod, while retaining the scratches and scuffs that you worked so hard to grind into your iPod…My battery was comped by the cool folks at FastMac, but if I’d have known about the cheap and fast shipping, I would have totally bought it myself!

[Docs.codehaus.org] Home - Confluence: We've also brought back the Groovy methods documentation up-to-date on the website, as well as the .Powered by Atlassian Confluence, the Enterprise Wiki.

Reflected tags on Technorati: Blog, Google Maps, GoogleMaps, Google_maps, Xml, Openpedia.org