List of all occupation email addresses has some individuals (not public/”point of contact”) in it? research, try to remove them before making large announcement
Need a tasking/web based project management system – needs to be researched
Private messages and new post notifications for subscribed topics both generate email alerts. These should include the full message (at least in PM case).
Need osoga.com link to public discussion forum
forum photo system or other online photo sharing
Roles that should be defined for communications members:
- twitter/fb/g+/(any other “network”) operators – they interact with some network/site on our behalf, e.g. send out tweets based on our calendar and pr goals, report interesting tweets back to oso, monitor various twitter trends for us
- volunteer coordinator – talk to new contacts/people who want to help – be familiar with available roles and help them find a niche (in com2 or any other committee)
- task tracker/manager – not quite a manager, makes sure that things that are marked done are really done, that the processes we set up are actually functioning right on a day to day basis.
- Data entry/transcription
- blogger/poster – a webmaster, working to maintain all or part of the site.
occupysalemoregon.com – new banner, no fist
should 12v dc be used for lighting in camp? ask maker commit
we need ups/backup power – try to find large ups charge system, even if we need new batts
we need an authentication server to be able to have smooth integration between forum/blog/all future apps (email, tickets, inventory, etc)
investigate possible new meeting format using simultaneous chatroom and face to face meetings
we need more computers on site. communications should work on this.
file server and router systems on site need to be configured
designate backup for dreamhost credentials
communications needs a private file server – quick and dirty solution, but will be secure enough for private data like contact lists
paper filing system in com2 tent, we will start having a lot more paper soon and more data entry going on
look into caching http proxy on site, save our bandwidth for what really matters
document volunteer roles, nice flowcharts to explain movement of different datatypes
general policy: keep our urls pretty, descriptive, and short (in that order). People often only see the URL somewhere and having the right words there matters.
possibly migrate to new vmachine on dreamhost
define the role of “credential backup”