Some case studiesEdit
- Hacking health
- Open Stack
What tools are we using?Edit
- Wordpress - easy to use, but hard to customize outside of its typical use case
- Drupal - harder to configure, but once set up, as easy as Wordpress
- Drupal commons: "A clone of meetup.com"
- OpenScholar / OpenOutreach - prepackaged drupal modules
- wickedsmart (on sourceforge)
- Big Blue button
- CRM (e.g. civic CRM)
- Canvas - many features limited to cloud environment
- Diaspora - peer-to-peer social network
- Avalon - curation of digital media
What are the challenges?Edit
- Access to data
- Privacy: how can you ensure it? Breaches of privacy can have very serious consequences
- How can you ensure that you'll have access to your data? There were lots of issues with getting data out of NING-based sites
- Free software developed on top of proprietary platforms
- e.g. built on google hangout
- Why does the whole stack need to be open source?
- There is a slippery slope from using non-free tools for collaboration, to losing freedom in the kernel and other parts of the stack
- After the success of free software in the kernel, the free software world has lagged behind in newer trends, like cloud platforms, collaboration software
- Challenges of communication:
- Multiple (human) languages used in a group
- Diverse skill levels: jargon e.g. "page" may not mean much to some
- "A dozen programs with a dozen micro sites"
- Compatibility amoung open source tools
What are some best practices?Edit
- Use purpose-specific icons to overcome barriers due to language or skill levels
- When selecting a tool, look at its community, and ask, "is this likely to be supported several years from now"?
- Use CRM to manage address books etc. in a platform-agnostic way
- Focus on group processes, not on tools.
What do we still need?Edit
- Tools for real-time communication
- Tech support for open tools drupal etc.
Community content is available under CC-BY-SA unless otherwise noted.