Slashdot Mirror

I'm not sure I agree with you a hundred percent on your analysis, there, Flexible.

The point here is not that RSS should be used for sending and receiving email. Rather, the point is that email leads to lots of problems in office communications...too much valuable knowledge ends up scattered in various inboxes, unavailable to the organization as a whole. Or even worse than that, you end up with a bajillion revisions of miscellaneous documents flying around as attachments.

A much better idea would be to deprecate email as it is currently used, and actually capture intra-office communication in some issue-tracking system, wiki, or other appropriate system.

Where I work we started doing this with JIRA and Confluence, both of which offer RSS feeds so that you can stay up-to-date on the changes within those systems. The combination is powerful, and I recommend it without hesitation.

I'm not sure I agree with you a hundred percent on your analysis, there, Flexible.

The point here is not that RSS should be used for sending and receiving email. Rather, the point is that email leads to lots of problems in office communications...too much valuable knowledge ends up scattered in various inboxes, unavailable to the organization as a whole. Or even worse than that, you end up with a bajillion revisions of miscellaneous documents flying around as attachments.

A much better idea would be to deprecate email as it is currently used, and actually capture intra-office communication in some issue-tracking system, wiki, or other appropriate system.

Where I work we started doing this with JIRA and Confluence, both of which offer RSS feeds so that you can stay up-to-date on the changes within those systems. The combination is powerful, and I recommend it without hesitation.

Both suck. Use Jira.

We just went through this recently at my company.
Our first though was Bugzilla, of course. But after looking into actually deploying it we realized it wasn't going to be that easy. So before we buried ourselves, we looked around to make sure Bugzilla was actually the right choice for us.

Turns out it wasn't.

We found Atlassian's JIRA. Installs like a breeze, easy to manage, no headaches, even actively tied into Atlassian's JIRA bugtracking system for itself! (And it works, seen bugs that we have submitted fixed in short order!)

We're not a really big shop, so I can't speak too much from the large scale deployment end, but aside from that this was a fantastic choice for us and I highly recommend it. (I am in no way affiliated with Atlassian or JIRA)

You should take look at the new documentation that we have put together. http://kb.atlassian.com.

Indexed, searchable, cross-referenced & annotatable knowledge base for Orion information.

• Oscache is a must for any JSP / servlet development, and allows the caching of sections of pages.
  
• Sitemesh allows you to decorate HTML similar to the decorator pattern described by the Gang of Four.
  
• Transform tags allow you to do code highlighting and xml transformations in your pages.
  
• WebCompass allows you to create meta-models of your site (allowing for dynamic navigation).