Orientation
Get involved with Tech Ops.
Join our mailing list:
Check out our orientation wiki page (http://wiki NULL.occupy NULL.net/wiki/TechOps_Orientation).
Get involved with Tech Ops.
Join our mailing list:
Check out our orientation wiki page (http://wiki NULL.occupy NULL.net/wiki/TechOps_Orientation).
Pea on NYCGA.net:
Pea on OWS.net development:
Shawn on OWS.net content:
Darrell on Tech Coop:
Email Address Policy
Financial Status / Budget
Terms of Use
Home Page
Lots of exciting horizons ahead of us.
Sunday February 5th Tech Ops open meeting – Full minutes here (http://www NULL.nycga NULL.net/groups/tech/docs/meeting-minutes-tech-ops-2012-02-05).
Report backs covered upcoming training, Newsletters, NYCGA.net analytics, server naming, the Bloomberg Bucks project, Office space, and more.
It turns out that the 855 NYCGA 411 number is NOT free from NYC pay phones due to Verizon being a lazy jerk. (edit: this statement has not been verified)
Consensus was reached to propose an update to the Principles of Solidarity (http://www NULL.nycga NULL.net/resources/principles-of-solidarity/) and enact Project Requirements (http://wiki NULL.occupy NULL.net/wiki/TechOps_Project_Requirements) for all current and future projects.
FGA sounding board meeting:
Thursday, February 9 from 6:30 – 9PM at the Rayogram offices.
79 Leonard Street, New York, NY 10013
Occupywallstreet.net open content meeting
Monday’s 6pm at 60 wall street
We had a good discussion with the Media working group about their website. They are considering creating their own web site at occupytvny.org (http://occupytvny NULL.org) which currently forwards to their YouTube Channel (http://www NULL.youtube NULL.com/user/OccupyTVNY). We suggested that they use media.nycga.net (http://media NULL.nycga NULL.net) for the time being. Their domain could be pointed to this sub domain in the future.
The group also discussed the up coming 10TB media server that we will be installing soon. The servers are built and configured and need to be plugged in. The way we intake media and how we protect/respect that media as it relates to arrests and the author’s ownership is still yet to be seen.
Tech has collected a bunch of hardware including four laptops. We are looking for a way to share them with the community.
The newsletter points to interchange.occupy.net (http://interchange NULL.occupy NULL.net), a new service from occupy.net which allows for project posting and people to sign up for said projects.
We discussed our progress on bringing equality to Tech Ops as a follow up to a past meeting on the subject.
There was also discussion around a need for more members to get involved in blogging (as I have been doing the lion’s share thus far). Analytics work session was also discussed, though no time was set. We also spoke of reaching out to Occupywallst.org and discussed the fact that the NYCGA is now handling ten thousand + e-mails sent to general and press@occupywallst.org
The group reached consensus on the re-wording of a line from the Principles of Solidarity (http://www NULL.nycga NULL.net/resources/principles-of-solidarity/) - the first “official” document from the Occupation of Liberty Plaza.
We will bring this as a proposal to the General Assembly.
The original line:
Endeavoring to practice and support wide application of open source.
Tech ops agreed upon edit:
Making technologies, knowledge, and culture open to everyone to freely access, create, modify, and distribute.
We hope that this will highlight the fact that our documents can be amended. We also agreed to ask for GA approval to host our official documents on GitHub (https://github NULL.com/occupywallstreet) so their versions can be tracked.
The group also came to consensus on using project requirements to on board new projects. More information can be found here: http://wiki.occupy.net/wiki/TechOps_Project_Requirements (http://wiki NULL.occupy NULL.net/wiki/TechOps_Project_Requirements)
Basically this means that all projects that are “officially” sponsored by Tech Ops will have to meet some basic requirements of documentation and responsibility. In return these projects will have access to our reputation, hardware, and network (among other things).
(http://upload NULL.wikimedia NULL.org/wikipedia/commons/d/dc/Alburnum_%28PSF%29 NULL.png)
I would like to suggest a report back format where everyone shares their thoughts on the meeting. Add to this post or comment please.
Drew – We spent the first part of our meeting discussing how we can deal with inequality in our group. The discussion brought us to three main points: Training, Mentor-ship, and Outreach.
I don’t want a group dominated by white males from privilege but I am also struggling to maintain what we have already built. These problems can be solved together. By training people how to use tools, mentor/skill share with those who want to build the tools, and though out reach to listen to feedback from the community one lowers the barrier of entry into Tech and allows for more people to be involved in building and maintaining our shared resource.
If highly skilled person with access to technology is the inner ring, then I need to focus on serving those in the outer most rings. I, though, must strike a balance. I don’t have the resources to connect with the outer most rings right now, but I (and Tech) should always strive to reach that goal.
The group agreed on a number of things to move us in the right direction.
I hope the training program I’m working on will help broaden our lovely group. I plan to share and gather feedback from my morning sessions and then take it down to Charlott’s Place in the afternoon. I will be looking for an after work space to run some training to allow our work bound brothers and sisters to join in the fun.
We then gave report backs. Agreed to implement Charles’s Terms of Use (http://www NULL.nycga NULL.net/groups/tech/docs/draft-policies-privacy-terms-of-use-dispute-resolution) statement on the web site and open it for general review by the community. The group also discussed Devin’s project proposal which he will show us on Wednesday.
The food from Kitchen was great tonight!
(http://i NULL.snag NULL.gy/oUs8N NULL.jpg)Tech Ops presented two parts of our four part budget proposal at – the amazing – Monday’s Spokes Council (preview our beta live tweets reader (http://livetweets NULL.occupy NULL.net/display/2012-01-09)). The proposal, presented by @jake (http://www NULL.nycga NULL.net/members/jakedeg/) and @matt (http://www NULL.nycga NULL.net/members/mattlepacek/), was very well received. The tone of our proposal was amazing and the visual presentation knocked the socks off those at Spokes.
The Spokes Council chose to accept both proposals. (Minutes (http://www NULL.nycga NULL.net/2012/01/09/nyc-operational-spokes-council-192012-summary/))
[Drew rightly pointed out that some kind of intro or summary is needed here. Anyone?]
Tech Ops had a rousing conversation in person last week about policies. We’ve got an urgent need to create some, not just for public consumption but as a real guide for some of the issues we face. Below is our current draft for three policies:
We invite all of OWS to review these policies and comment below. Continue reading
One thing that we spent a lot of time talking about at tonight’s meeting (though this is FAR from the first time we’ve had this discussion) is the fact that our efforts to connect with interested folks who want to help have been absolutely dismal thus far. One of the things I brought up at the meeting (sometimes with less of my signature tact and cheer than usual – sorry) was the fact that we have tried many ideas for outreach and on-boarding, but they have repeatedly fallen short of our aspirations, usually because no one steps up to really make them work. I tend to think it is not because we have been lacking the perfect piece of software, and not because we have been lacking the right imaging or branding or marketing, but rather because we have been lacking the individual human beings with enough time/motivation/interest to take it upon themselves to really push these efforts forward. I think that many of the things we have tried, and the things we have repeatedly discussed trying, could have worked great if only they had been actively followed-through on. To help contribute to this conversation, I figured it might be helpful to compile a list of some of the tactics we have tried thus far and a brief analysis of their success: Continue reading
NOTE: This proposal was submitted to the Facilitation Working Group on 1/5/11 in anticipation of a presentation at Spokes Council on Friday 1/6/11. It is also viewable on the main nycga.net site here (http://www NULL.nycga NULL.net/2012/01/06/tech-ops-working-group-budget-for-phone-services-hosting-reimbursement-infrastructure-operating-costs-and-livestreaming-in-hd/). For a more detailed cost breakdown of this proposal, check out the itemized post. Also, the whole thing is available as a PDF, here: Tech Ops Funding Proposal MERGED
The Technology Operations group of the New York City General Assembly strives to provide tools that enable our movement to connect and communicate with each other and the world through technology. We provide as many tools we can to support OWS and the broader Occupy Movement as we all transform the world. Some of our more notable projects include tools that many people in the movement use every day: Continue reading
To read the written proposal for Spokes Council, check out this post.
Total max one-time cost (if all items approved): $10,608.99
Total recurring monthly expense: $863.68