Group items tagged

Being a CalDAV reference implementation is not a priority.

we will not be implementing CalDAV scheduling

misperception in the press

Wiki Etiquette

Build structure:

Take it personally: Yes, colleagues will edit your work and you might not agree with every change, but that's the nature of collaboration. It doesn't mean that your co-workers dislike you or think you're stupid. Ignore questions: Colleagues may disagree with your changes and ask why you made them. If so, be prepared to give concrete reasons for your edits. Delete useful content: Many times a posting can be improved by amending or editing it, but deleting content upsets people, and they may feel they've wasted their time. Be chatty: A wiki shouldn't be used as a chat room. Any discussions related to a wiki subject should take place on the discussion or talk page, not on the actual content page. Keep it secret: If you find valuable content on your company's wiki, tell others about it. Wikis benefit from a wide range of contributors.

Let's face it. Most of us out here in the open source community are getting a very good deal. We are fortunate to have bright people building software for us at little to no charge. If we begin to depend on these freely given gifts, we should never make the mistake of then assuming the one giving the gift is somehow accountable to us. Gifts given should be received with gratitude and an expectation of nothing further. Nothing. And, if we aren't able or willing to help, the least we can do is try not to ruin the fun!!! Thanks, Bèr! I appreciate your article very much.

Redshaw said that rather than an age bias, he noticed more of an executive level bias to collaborative efforts: the higher up in the company's hierarchy the less social networking technologies get used. "That's a good thing," he said. "The real work gets done not in the board room."