Interoccupy.net: InterOccupy on GIT (1 comment)
I've pushed the live code to the [[https://github.com/occupynet/InterOccupy occupynet github]].
There are a number of plugins, directoires, and themes that are being ignored.
To develop for interoccupy it will require running a local install of wordpress and using pulling in the repo to replace the wp-content folder.
OK, so we have been talking about helping with a variety of different major campaigns that are in the works for Occupy, but I think this should take precedence because it will be a very significant and definitive communication to people outside the Occupy movement and it's coming up very quickly. We can either work directly with someone/multiple people who are interested in creating the TV spots, or we can do research in general that may help and make it widely available.
If you are planning to create a spot or know someone who is, contact us please!
If you're interested in helping with research, come to today's meeting at 60 Wall Street Atrium at 7pm. See you there!
Federated General Assembly: Mapping the Movement slideshow (2 comments)
As part of the 2011 unconference, Thiago and Andrew presented on Dec 11 a second Mapping the Movement session. Attached is the slideshow we presented. It is a combination of drawings from our first session earlier in the week, and some renderings built upon these outcomes.
Federated General Assembly: blog: On broadcasting (2 comments)
When Thiago and I did our three-hour braindump last Sunday, one concept emerged with particular clarity: something we expect groups will be doing, over and over again, is taking content (posts, events, maybe minutes, maybe discussions) they've worked on within the group and promoting it out into a more visible space in the network. e.g., to:
- The homepage for their group
- The homepage for their whole site
- Some broader channels (details TBD) that propagate through the FGA network
The name we were using for that process is broadcasting. Not perfect, subject to change, and all that, but it kinda captures the idea.
What's most important is that the idea has a consistency all the way from the user's experience into the backend implementation. Any given broadcast process has three parts:
- The actual content to be shared around or promoted. An event, a post/statement of some kind, a document; something that's been worked on in a group.
- A process for approving the broadcast. Ideally, this could encompass a number of group decisionmaking processes (simple poll, some kinda consensus thing), but initially it could just be group admin (ugh) approval.
- A broadcast space or target - basically, that first list.
For users, we can make this regular and structured: a button & subsequent workflow around performing this basic action which, while the content, process and broadcast targets change, the overall experience stays the same. When it's time for the group to put something 'out there,' someone can hit the button to start the process of getting it published, and the whole process that makes that happen is transparent. We'll need some good visual language and patterns around that process so that even as the individual components change, the experience and intuition stays the same. In the backend, this sort of modular architecture is excellent: by subdividing the task of broadcasting into these three clear, distinct stages, we make it easy to add new broadcast targets, new processes, and new types of content later on.
One note - it's not that content can only propagate through the network by going through a broadcast process. I'm expecting that people will be able to join and follow groups, including on remote sites, and see a full activity stream of everything that's happening. The power of the broadcast lies in the ability to create separate, special communication channels which will, presumably, be less noisy and contain more high-priority information as they cannot be populated unless a group has gone through some process to approve the message. Even if they turn out to be just as noisy, though, broadcasted messages that have been through a process let us know the answer to that constant question - "is this message just your opinion? or has it been through a group - and which group?"
I have created a user ows with the password ows on my project management site.
You can find there structured information relating to CiviCRM in the Notebook section:
CiviCRM: Using CiviCRM e-book (1 comment)
I have posted a PDF e-book in the Document section: http://projects.occupytechnology.org/documents/24
which is like 100x better than the existing FLOSS manual for learning Civi.
Federated General Assembly: wiki re-organized (1 comment)
I retitled and reorganized the wiki a bit. Moved some sections around for clarity.
Things have fallen behind somewhat, so I thought I should at least try and clean up our public presence.
*Individuals with specifics to report:
Share what you've been working on
Share what you're doing
Mention any blockers you have
Recruit people for help on specific tasks
Schedule any follow-ups
- Lippe - Sam
- Chris - Julieanne
- Michael - Katie
- general coordinating - working group in NY, fielding volunteers
- identifying technologies & writing up divisions of labor for back-end folks so they can operate simultaneously while ux and front end execute other tasks
- better means - great system, been exploring
- finishing write up and starting discussion amongst back-end folks
- find front end coordinator
- find a way to partition conversations so we can clear up general list
- figure out way to make fewer lines of communication run through him
FOLLOW UP: talk with larger group re: move to better means
WORKING ON: writing letter to form component groups (UX code, concepts of communication, meetings and accountability), more layers of discussions that aren’t necessarily code related
- Feeling cautious about adding layers to an already complicated process
WORKING ON: catch up and digesting threads for potential organization, starting public facing documents for groups
WORKING ON: Coordinating interviews, reaching out to people
NEXT STEPS: will be in touch with Atlanta folks who used NYCGA as basis for their site
*wants to highlight focus on transparency and availability to occupiers
FOLLOW UP - work on a method of communication and pick someone responsible for interfacing with occupiers
WORKING ON - restructuring engagement model
Engagement Model - plan for all the steps we need to get through to build the site
Next Steps: Meet with Sam, share with a few others for feedback then share with larger group
WORKING ON - mobile applications for FGA, automated voice transcription - there are some that are useful for interviews possibly (will follow up with Katie)
FOLLOW UP - Michael & Katie follow up together on how this can be used for interviews
I created a new "FGA priorities" sort on the issues page, which groups things together a bit more sanely for where we are at.
- hosting infrastructure
- project management
- site building
Also available in: Atom