36c3-hacc
Haccers, Welcome to 36c3 !

Meeting notes day 2 @ boredeom: https://pad.pad.land/p/hacc-day2

Table of Contents
1 About HACC
2 Here...
2.1     Organizations (add yourself)
2.2     People (add yourself)
3 *** TODOS
3.1     * (DONE) ORGA -- change
3.1 about:future
3.2 entry to add HACC:
3.2.1     * (DOING) ORGA -- check 35c3 wiki to see HACC mentions
3.2.2     * (DOING) meet and connect HACC people
3.2.3     * (DONE) make HACC sub-assembly in wiki:
3.2.4     ______________ Next
3.2.5     * ADMIN -- fix hacc.wiki http redirect
3.2.6     ______________
3.2.7     * ORGA/ALL -- make 1-2 meetings a day to just coordinate?
3.2.8     * WORK -- translate pages of related projects (DE->ENG)
3.2.9     * WORK/CONTENT -- make a lot of HACC pages @ 36c3 wiki:
3.2.9.1         * individual 36c3 wiki "Project" type pages for HACC projects
3.2.10     * CONTENT -- make specific new HACC self-org sessions:
3.2.11     * CONTENT/WORK -- improve "Related events" page (Fahrplan) of "
3.3 about:future
3.4 " (36c3 wiki):
3.4.1     * ORGA -- coordinate a daily coordination meeting:
3.4.1.1             1B) work more on a realtime chat group:
3.4.2     * CONTENT/ORGA -- coordinate HACC specific self-organized sessions
4 *** Q FOR ALL
4.1 What do we want to do here?:
4.1.1     * revisit materials from 35c3
4.1.2     * meet the same people and new people
4.1.3     * hear optional updates from people:
4.1.4     * continue improving the workflow for:
4.1.4.1         a) AT events
4.1.4.2         b) NOT AT events:
4.1.5     * COLLECT SOURCES & PERSPECTIVES
4.2 * Q FOR ALL -- What do we want from 2020?
4.2.1     * [...] <------------- ADD NEW HERE 
5 *** (NOW)
6 *** DOING NOW !
6.1 START NEW WORKGROUPS:
6.1.1     * WG: Tools, Workflows, Processes
6.2 CHANNELS for ANNOUNCING a common activity protocol (for andreas)


About HACC

At 35c3, "Hackers Against Climate Change" (HAAC) was a series of self-organized sessions.
Hackers discussed "climate change", and tried to figure out how to organize around the issue.
    -> Wiki: hacc.wiki
    -> Pads Index: 🔗hacc-index


At 36c3, HACC seems to have consolidated around the about:future assembly. 
It is a general focal point to the various activities related to the topic that are announced to happen at 36c3 - talks, projects, self-organized sessions, etc.
    -> Congress 2019 Wiki: here
    -> Main Site: 🔗hacc-index



Here...

    Organizations (add yourself)
:
    * about:freedom = straight at entry to CCL
    * bits & baume = event
    * c3sus = "c3 sustainability"
    * [...]


    People (add yourself)
:
    * Raphael = @36c3 built a table for educational purposes & made a "hacc.wiki" sticker!
    * Blipp = about:future coordination
    * david/@dcht00 (wire, telegram, twitter)  = caretaker of pads 
    * moep = DECT @ congress
    * [...]





*** TODOS


LAST SIGNED OFF BY:
    david, moep ~ 20191227 0:30



    * (DONE) ORGA -- change about:future entry to add HACC:
        create link to this (overview) pad & link to hacc.wiki


    * (DOING) ORGA -- check 35c3 wiki to see HACC mentions

Keep checking and improving!


    * (DOING) meet and connect HACC people

meetup:
    andreas,david,raphael

todo?:
    seth,stephanie,...



    * (DONE) make HACC sub-assembly in wiki:


    ______________ Next

    * ADMIN -- fix hacc.wiki http redirect
    #SECURITY
    by 20191227 03:10
    http://hacc.wiki works
    https://hacc.wiki does not work

    who is the domain manager?

    ------------
    also:
        make a dedicated "security" council & action group



    ______________

    * ORGA/ALL -- make 1-2 meetings a day to just coordinate?
        * make sure we perform a protocol for what happens at this meeting
        ### TODO: 🔗hacc-protocols


    * WORK -- translate pages of related projects (DE->ENG)
        for example: https://events.ccc.de/congress/2019/wiki/index.php/Assembly:Bits_%26_B%C3%A4ume_(B%26B



    * WORK/CONTENT -- make a lot of HACC pages @ 36c3 wiki:


        * individual 36c3 wiki "Project" type pages for HACC projects

See Projects on hacc.wiki .
move and merge to "hacc-projects" !!!!


    * CONTENT -- make specific new HACC self-org sessions:
        * (david) protocols for hacc - see 🔗hacc-protocols (###TODO)
        * [...]


    * CONTENT/WORK -- improve "Related events" page (Fahrplan) of " about:future " (36c3 wiki):
        make easier to differentiate/connect/relate/consider DE and ENG
    
    * jointly overview and give mandate for the HACC Assembly wiki labels



    * ORGA -- coordinate a daily coordination meeting:
            1A) have a fixed time and place daily meeting:
                1PM?:
                    you can set activity for minimum of 4PM
                    know what has to be done so it is PROPERLY ANNOUNCED
            1B) work more on a realtime chat group:
                telegram? wire? only mailing list?


    * CONTENT/ORGA -- coordinate HACC specific self-organized sessions






*** Q FOR ALL



What do we want to do here?:


    * revisit materials from 35c3


    * meet the same people and new people


    * hear optional updates from people:
            a) people who were there before (at 35c3)
            b) new people


    * continue improving the workflow for:

        a) AT events

        b) NOT AT events:
                * have ways to overview materials
                * [...]




    * COLLECT SOURCES & PERSPECTIVES

* Create a possibility to face any composition of differing perspectives, informations, tactics, etc

* Make sources more plausable and, somehow, ranked ("generally effective", "recent", "controversial", ...)



* Q FOR ALL -- What do we want from 2020?

"meeting climate targets"?
consolidating?


    * [...] <------------- ADD NEW HERE 







*** (NOW)

* Meeting notes 191227


running some infrastructure
nobody wants to do wordpress
you are trying sulu CMS, because it has a tree like backend, so it makes it easy to understand
https://developersforfuture.org
https://econ4future.org/

scientists for future
people are everywhere

running:
    * mattermost to communicate
    * have a server running support:
        part of a big kubernetes cluster (in Berlin)
        can also offer infra (instances!)
        can also be used for experiments
        trying matrix (as a solution for "chat fights")
        trying mastodon server
        pad.developersforfuture.org
    * ...

involved in monthly meetup in berlin:
    "Adult organisation" (meeting of different "for future" groups)

https://forfuture-buendnis.de/

https://fridaysforfuture.org/statistics/map
they are simply in a facebook group
janine organizes the international stuff
she tries to manage the webpage, collect the page data, etc
the data is, so, centralized and summarized

there is so many maps
how to make them:
    discoverable ?
    decentralized ?
    allow for discovery ?
examples:
    https://fridaysforfuture.org/statistics/map
    https://map.preciousplastic.com/

CROSSLINKING as a part of CONSOLIDATION
max proposes a "crosslinking schema" myb with json-ld

-------------------------

what E2H is missing:
    1) search:
        WILL DO
    2) person profiles
    3) "it is more difficult to write in pads than in wiki":
        NO CONSENSUS

TRYING AGAIN:
    1) NO GROUP WILL GET A CONSENSUS ON A TOOL

exp 1: "70 perc will say lets use tool A, and then some of them will use it. the other 30 perc will come and troll the tool, so they arent productive."

    2) WE NEED A OVERVIEW OF DIFFERENT WAYS TO REACH AND REVISIT DECISIONS ABOUT TOOLS:
        2A) NARROW DECISION TO EXACTLY 2 ALTERNATIVES.:
            DECIDE ON 1 AND GIVE IT A TIME FRAME.
            DECIDE ON HOW TO EVALUATE WHETHER IF IT WAS SUCCESFUL AFTER T.
            IF NOT, HAVE A PRE-ESTABLISHED MIGRATION TO TOOL 2.
        2B) TOOLS NEED EDITORS:
            TAKE VOLOUNTEERS FOR EDITORS.
            EDITORS CHOOSE THE TOOL.
        2C) ...

"this is similar in companies. people sometimes sabotage tools they dont like."






*** DOING NOW !


https://events.ccc.de/congress/2018/wiki/index.php/Session:Hackers_Against_Climate_Change
1) Copy the same thing as last year (SESSION)
2) Set at date for Day 2 >andreas
3) Make a PROTOCOL for REVISITING (reprocessing/overviewing/...) PAST MATERIALS:
    >david
    "First year is easy - just try to do a massive brainstorming ... second year is hard"
    ------------------
    Parts / process / choreography:
        A) General introduction of who was here before
        B) New people
        C) Forming workgroups around existing things + trying to expand to new groups
        D) Inside the groups, revisiting (cleaned up) existing pads:
            We need group leaders, who are ready to tackle the past materials !
            Each group needs "one screen" action ?
        E) Merge session back



START NEW WORKGROUPS:

    * WG: Tools, Workflows, Processes
:
    * IS NOT: only a discussion about "which tool is better"
    * IS: an abstract discussion about how that would be evaluated !
    * IS: a discussion of who:
        * IS CURRENTLY using what
        * ... or has so in the past
        * ... or aspires to in the future
    * discuss abstract matters about workflows
        WRITE AN AGENDA !
    * [...]


CHANNELS for ANNOUNCING a common activity protocol (for andreas)
:
    * make a 36c3 wiki page
    * announce it on twitter (with tags)
    * ... mailing list
    * ... telegram group
    * ... about future daily 9pm meeting (IRL)
    * ... print posters ??? (at Digital Courage next to Food Hacking Base)
    * ... about:future channels:
        https://events.ccc.de/congress/2019/wiki/index.php/Assembly:About:future/Fahrplan
    * (...)



<---------------------------------------- (now)(new) above




(Site generated by E2H, an "Etherpad hypermedia" project by @dcht00). Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.


Edit Site

Edit CSS