SQEK WORKFLOW

Last updated:
    2016-05-29 foundation (d)



Workflow Technologies (general)

Currently used:
    * website: (which tech???)
    * mailing list
    * twitter
    * Open Street Map maps (http://maps.squat.net)
    * ... ???

Future direction:
    * David pledges to setup a copy of the CHT workflow:
        * Basic parts: Etherpad + Syncthing
        * almost zero work to set up (for admin & users!) and can be done very soon.
        * what CHT uses is described roughly on http://totalism.org/workflow
    * goals:
        * support SQeK research work
        * think on how to support activists:
            * to use SQeK research + do own research
            * use SQeK tech infrastructure!
            * ... better: replicate and deploy own, self-hosted infrastructure !!!

Suggestion for new technologies:
    * Syncthing:
        * for internal documents / archive
        * open source, cross-platform, simple to use P2P file sharing app
    * Etherpad server (own or existing):
        * for group work, taking notes
        * always keep an index file! <-- temp: http://pad.totalism.org/p/sqek-index
        * stuff from mailing list is propagated there to be more easily reffered to and maintaned
    * real-time chat (little barrier to questions and talk):
        * irc room <-- temporarily #sqek on Freenode!
        * on conferences, using a Whatsapp/Telegram group or something very accessible could be better than nothing?



Workflow Technologies (at conferences / meetings)

So:
    * selfhosted local wifi Access Point
    * taking notes:
        * local, internal Etherpad
    * navigation (selfhosted, offline maps + markers):
        * Open Street Maps + OsmAnd mobile client 
    * recording audio <-- Alan did this mostly
    * [...]

Also:
    * get people online? (via ethernet + own AP)? >david
    * have printing solution available
    * make sure people are exchanging content (via Archive):
        * "e" zines, etc
        * photo
        * interesting data
        * slides
    * [...]




Taking notes

Use a localnet + local selfhosted Etherpad server.
IP and way to access is published + printed on wall. People are invited to use it!

Considerations:
    * when to take names (of people speaking) or not?
    * to project on board while writing, or not?
    * (several people on a common pad):
        * one person writing all
        * write materials separated + have "narrator" make live cuts?
        * Do we cut each-others materials, or "only touch yourself"?
    * [...]




Todos + Ideas

>edward
David possibly needs:
    * access to "a" records
    * access to documentation / experience with other people, of existing website project

Reorder older minutes
>david

Organize archive!
>david

Rethink scheduling of meetings
maybe some more self-org part would make sense (in tech world: "unconference")

...