Collaboration Stack

Registered by Dustin Kirkland 

SUPERSEDED BY:
 * https://blueprints.launchpad.net/ubuntu/+spec/server-karmic-virtual-appliance

Many businesses adopting 'agile' development methodologies could benefit from some open source collaboration tooling, such as:
 * wiki's (mediawiki?)
 * instant messaging (jabber?) and/or irc (unreal?)
 * collaborative document editing (gobby?)
 * pastebin
 * voip/teleconferencing
 * ...

I'm not yet singling out the particular implementation of any given technology (note the projects plus question mark in parentheses).

However, I am suggesting that many organizations could use internal implementations of one or more of these open collaboration tools. As such, this isn't about "replacing" an internal dns infrastructure. Rather, it's about rolling out a brand new, first-time pastebin server.

We could create a tasksel, or even virtual appliances in a ready-to-deploy mode for one or more of these tools. And in many cases, this might be the foot in the door for the "first" Ubuntu server in some organizations.

:-Dustin

Blueprint information

Status:
Complete
Approver:
Rick Clark
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Superseded
Series goal:
None
Implementation:
Needs Infrastructure
Milestone target:
None
Started by
Dustin Kirkland 
Completed by
Dustin Kirkland 

Related branches

Sprints

Whiteboard

Discussion Points:
 * Brainstorm an *extensive* list of collaboration technology packages
 * Separate these into tiers, (good, better, best)
 * Discuss different ways of presenting/installing these services
  * tasksel (not ideal, perhaps)
  * canned virtual appliances
  * vm-builder
 * Perhaps produce some documentation on how to make your business more "Agile" by using Ubuntu + X,Y,Z technologies
-- Dustin Kirkland

This is very similar to "Tightly Integrated Application stacks that we have discussed before. I think the key value would be integration between components.

dendrobates: Until we have a better way of displaying install tasks, I would prefer to limit the number of tasksel tasks. We can discuss this in the virtual appliance session at UDS.

It would be better to integrate these tools into some sort of package, or make their configuration centralized. If we talking about servers here, it means enterprise - and then we enter the whole new world of requirements, like REAL usability, time to learn, resources required, compatibility with other systems, etc. The more we could do with one installation the better - it would require less convincing to try it. -- Alex Lourie.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.