Meeting Minutes – TechOps GM – 2012/01/22

Posted by & filed under .

Report Backs
* Occupy Ecosystem
** Jason is not giving up Occupy.org legally but we have control of it.
** We’re going to point it to the CiviCRM
* Free Network
** Isaac is back from his two week roadtrip
** Developed a 18-month roadmap
** Wants to organize a global free network federation event this summer
* OccupyWallStreet.net
** First developer meeting took place on Thursday
** Tasks have been assigned and regular dev meetings are taking place thursdays at 4pmm
* OccupytheEarth.net
** Alive on our server
** Launch taking place at next Saturday’s eco-cluster – 2pm 56 Walketr St
** Wants to develop green knowledge trust, semantics wiki stuff, etc
** Revive the FLO Movement Group at the event
* NYCGA.net Administration
** Has seen lots of evidence of bullying, racism, etc
** Suggests requiring folks to accept a ‘policy’ when they register
* PermaBank
** We realized there’s a lot more work that needs to be done.
** Evan is searching for developers – won’t get to Beta without it.
** Georgiy made progress but needs follow up.
* Groups Proposal
** Group were supposed to be kicked off the website on the 20th
** Sometime tonight we’ll be receiving a list of groups to delete
** We’re ‘deactivating’, not ‘deleting’ groups.
** We may make a
* Training
** Newswire and maps training will take place tomorrow
** Design now has a group blog
** 30-40 people responded to a blog

Agenda Generation
* Terms of Use

**Charles: There’s a draft of 3 policies that have been circulated for a while.  One of them is terms of use, others are privacy and disciplenary action.  We have repeatedly asked people in Tech to voice feedback.  Most related to the privacy policy.  Patricia submitted two proposed changes.  One was accepted, on the other there is a disagreements.
** Charles: In the preamble there is a paragraph that addresses the responsibility of TechOps over technologies that we don’t support.  Charles proposes that those systems could be placed under the purview of TechOps policies – for example: if a real life person was harassing another real life person on Facebook then we could apply some disciplinary action.
** Patricia: We don’t need to include an invitation to use TechOps policies.
** Jake: Why do we need to collect info on admins, mailing lists, etc.
** Charles: We can help groups administer policies.
** Drew: Why do we want to apply our policies to other groups?
** Charles: This could be made available to people through GA announcement.
** Jake: We could just tell people this.
** Charles: We’re basically making a policy for our own stuff and not making it available for others.
** David: The only part of this policy is where administrators get involved is in the pre-amble.  We could put it later in the event.
** Ted: I don’t think we’re capable of trying to impose such broad rules and responsibilities.  I think we need a standard fair-use clause that makes it clear we’re a not-for-profit organization that isn’t making money.
** Facilitation: Any suggestions for Patricia’s modifications?
** Patricia: I changed the language to NYCGA over OccupyWallStreet because it applies specifically to the NYCGA, not the Bronx GA, etc.
** Charles: I will add a fair-use section.  This will all be sent to Legal.
** Drew: Are we consensing upon this, then moving it to legal, then the GA?
** Charles: Each policy once approved by us is more or less enforced – but we will take it to the lawyers, then the GA.  We are responsible for the digital properties so we must take responsibility before the GA authorizes an TOS.
** Jake: Safer spaces suggests we enforce our own policy on our own space.  I suggest adding
** Patricia: I think we agreed that we can’t unilaterally make policies without GA approval – we need to bring it to spokes or GA.
** Devin: I think we can apply policies unilaterally – especially when we don’t have one – but that this isn’t our space to keep safe.
** Charles: We need a policy  now.
** Drew: If we reach consensus this evening we apply the rules with the caveat that this is the ‘review period’ for these rules and now is the time for public criteque of this policies.  We can bring the modified version to the GA for consensus.
** Johnanna: What’s the time period.
** Charles: Earliest point to submit all three is 2-3 weeks.  At that point we should also have community feedback to apply.
** Patricia: Safer space is doing community agreements first then enforcement second.  Once we’ve reached consensus we can bring it to legal, spokes, etc.
** Jake: Users of the site are admins of groups so how can we apply this policy in that case.
** Charles: This policy gives us permission to figure this stuff out on a case by case basis – we’re flexible.
** Facilitation: Should we move to consensus?
** Casper: What do we do when we see a real and emminent threat?
** Charles: The ToC addresses this.
** Facilitation: Friendly Ammendments
*** Move to Patricia’s language in preamble
*** Change admin contact language
*** Fair use
*** Review period
** Facilitation: Passed!

** Drew: I need to collect content for the Eyebeam Event – I’ll bottom line.  I want to know who wants to come and what they want to present.
** Patricia: Can you recap what that is?
** Drew: They have people presenting activist technologies and then tabling.  Let’s discuss at Wednesday meeting.

* Project Requirements
* Next Saturday Eyebeam Event
* COD

Comments are closed.