CommunicationSystems: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 14: | Line 14: | ||
'''Staff Communication:''' | '''Staff Communication:''' | ||
*Mailing list | *Mailing list (currently in use) | ||
*[http://twiki.org/ twiki] | |||
*[http://foswiki.org/ foswiki (fork of twiki)] | |||
*[http://trac.edgewall.org/ Trac] | *[http://trac.edgewall.org/ Trac] | ||
*[http://www.redmine.org/projects/redmine redmine] (a Trac fork using Ruby on Rails) | *[http://www.redmine.org/projects/redmine redmine] (a Trac fork using Ruby on Rails) |
Revision as of 01:23, 30 March 2014
Communication is essential to this project. Developing and implementing unique, modern methods will dramatically further our goals. Below are some ideas on this topic. Feel free to comment on the [discussion page].
Community Discussion:
- story submissions on main site inviting discussion on an issue
- Consider.it is a powerful system for discussion on specific issues examaming pros and cons (try a Demo) (drag and drop "pros" and "cons" into your "opinion")
- (uses JavaScript, but they are looking for organizations to pilot with)
Community Polling:
- proprietary email voting system: Audioguy's Notes on his system
- archived ideas: Communication:Voting
Staff Communication:
- Mailing list (currently in use)
- twiki
- foswiki (fork of twiki)
- Trac
- redmine (a Trac fork using Ruby on Rails)
- InterTwinkles
- Intertwinkles uses JavaScript but looks incredibly powerful
- Use slashcode
- See: AudioGuyWorkNotes