Group items tagged

One of the biggest problems of wikidom today is not WikiSpam but the tendency to redraw fundamental parts of communication from the main online community platform ("stage") to BackStage systems. The point of this page is to show why BackStageCommunication is used (it must offer advantages to individuals, otherwise they wouldn't do it) and how this may harm online-communities. But note that there is a difference between PrivateCommunication? and BackStageCommunication and that there may be situations where these are unavoidable.

syntax highlighting when editing code

Here are my thoughts on how to use a wiki page to collaborate on creating a non wiki page let say a powerpoint presentation. I am looking for feedback on this so feel free to add comments.

Many free RSS services let you subscribe to oodles of news sources that so you don't have to hopscotch from site to site to get the scoop. But the $29 FeedDemon 2 is the best RSS reader for steamrolling through thousands of feeds. Need headlines from the science section of the world's major newspapers? Check. Want the latest research from insider blogs about solar power? Check. FeedDemon is faster and more customizable than browser-based freebies, and it also lets you access feeds online.

2. Wikipedia You might shun this online, open-source encyclopedia if you've ever been burned by prank entries or fudged facts. But because anyone can edit Wikipedia, it's a richer resource than Britannica for subjects off the beaten path, such as the > 1960s underground press > or > rivethead subculture > . Though it's not the only source you should reference in term papers, at least Wikipedia gets you started. >

Corporate Wikis reviewed: Confluence, JotSpot, WetPaint, Socialtext by Troy Angrignon on Mon 10 Jul 2006 06:30 AM PDT  |  Permanent Link  |  Cosmos Wikis are on the rise in corporations. And it's about time. One of the principles of Web 2.0 is that your user community can generate content that is better, faster, and probably easier to read than you can as a vendor. One way to enable them to contribute would be to build a wiki and let them flesh it out. Some good examples are coming up in this article: "Corporate wikis breaking out all over: MSDN Wiki" by Dion Hinchcliffe. (He has another great post as well called "Exploiting the Power of Enterprise Wikis") Quote of the day: "Not leveraging the contributions of a company's most impassioned and enthusiastic customers is starting to be seen as a significand oversight in many business circles." It appears in the article that eBay is using Wikis to better communicate between their users, partners, and suppliers. Now MSDN (Microsoft Developer Network) is using their pages to improve the quality of their developer documentation with the MSDN Wiki. THAT is a great usage. Your users often know your product better than your engineers and product managers because they have to live with it day to day. And guess what? If they tell the truth about some part of your product being broken - that's a GOOD thing.

Atlassian's Confluence is the best of them so far. Pros: the overall design is clean, it has advanced management tools, good security, and simple attachments.Its email function has to pick mail up from a POP box which makes it a little bit less ad-hoc but still functional. And most importantly, it also has great tools for moving pages around. Cons: Text editing, like with most apps these days is a bit dodgy, and pasting in blocks of text from Word is likely to cause problems. The pricing model is reasonable but for some reason (possibly because they're from Australia), they still don't have a directly hosted option so you have to use somebody like Contegix or deploy it on your own box. This seems to be a big and obvious oversight on their part these days. Also, their pricing model doesn't encourage small deployments right off the bat. I think this is the one that we'll use more of internally at the company where I work. Summary: The best of the enterprise wikis today, and one of the best options for scalability.

WetPaint is a newcomer that is doing some interesting stuff and that might be a better bet than JotSpot. Pros: The design is beautiful, the tool is very easy to use, the text editor is one of the best I have seen. Cons: I'm not clear on their entierprise suitability and it's not really their target market. It didn't appear that they had much in the way of administration tools, granular security, or any way to integrate into a back-end authentication system. Summary: I met one of the WetPaint guys at Gnomedex but he didn't seem to know the product very well. Hopefully next time, they'll put somebody more knowledgeable at their booth who knows the product in more detail. I think they're worth watching to see what they do in the next few months.

The current release of Chandler builds upon the experimentally usable calendar for individuals and small workgroups. It is a test release for collecting feedback based on real usage. In addition to basic calendaring, advanced features include: recurring events; time-zones; overlayed, multiple calendars; and managing a single event across calendars. Chandler offers innovative capabilities in calendar sharing to support workgroup collaboration. Chandler sharing is server-based, works across platforms and supports multi-author editing. Our goal for our most recent release, 0.7alpha4, is to give a rough sketch of what Chandler will be by our first Preview release (Spring 2007). This release introduces the Dashboard, which gives users a runway view of all of their information. Users can try creating a simple task list, and can share that list with others just as they can share calendars. Users can also experiment with sending notes, tasks and invitations to others via email.