Meetings

From HackerspaceWiki
Jump to: navigation, search
Meetings
Monthly Meeting
Type of Talk

Hackerspaces.org Meetings[edit]

Here you can find info on meetings on the topic of maintaining & improving this site.

Meetings happen in-person at worldwide hack events, and online regularly (every 8th of each month at 14.00 UTC on the #hackerspace channel on Freenode).


2018-12-27 @ 35c3[edit]


2019-04-20 @ Easterhegg 2019 Vienna[edit]

minutes from in-person meeting at Easterhegg 2019, Vienna


2019-08-24 @ cccamp2019[edit]


2019-09-08 @ (ONLINE) Regular #1[edit]

source notes pad

Topics/Agenda

content of the wiki, map, patterns how-to-conserve-this-meets, chatbot? organisational structure of hackerspaces, geekend?, domain?

Regular meetings on each 8th of the month

1. Wiki - non-space info content we should probably build three lists: keep improve and keep discard and discuss that on the next meeting.

Namespaces to use:

 * Hackerspaces
 * Events
 * HSo itself (meeting notes, who-is-who, )
 * hackerspace OS: Design Patterns and other patterns
 *  Affiliated Orgs (but never sponsors) [CCC, EFF?]

https://www.mediawiki.org/wiki/Help:Moving_a_page For information about mass moving pages (aka this is faster to move all the spaces in the hackerspaces namespace)


2. Domain: owned individually or transferred to an organization? Paul is currently in charge of the domain, could be transferred to e.g. CCC e.V. "he said he's gonna offer some kind of management interface so we can update records without having to mail him everytime"


3. Map improvements Waterppk has offered money(!!!) to have someone fix the map. They wish the map to show all hackerspaces in view. bronsen thinks this is indeed a technical issue and thus solvable.

Contact them under team@sector67.org

4. Design Patterns

Not all patterns seem applicable or at least miss some practical examples. Also a list of anti-patterns would be nice. Also more social conflict resolution patterns would be nice to have.


5. Should be done until next meeting (Tuesday 2019-10-08)

Self-proclaimed editors will have started categorizing and namespacing pages (see top 1) Editors: bronsen, g5pw, metalgamer [please add yourselves!] Concrete feedback from "The Map Team" regarding OSM & performance (see top 3)


2019-10-08 @ (ONLINE) Regular #2[edit]

[1]

Attendees: bronsen, g5pw, sva, aimeejulia, waterppk,

Topics/Agenda

  • content of the wiki
    • HSo census update
    • carry-overs:
      • editors have started checking pages
      • map team gives feedback
  • Meetbot
  • Hackerspaces.org Geekend
  • 36c3 meeting
  • next meeting


1 Content of the wiki

1.1 hackerspaces census update

(aimeejulia) - from my end I don't have many updates, only that I am receiving replies to my queries to the hackerspaces which I wasn't sure about and am updating them slowly, but the organic shop stuff got in the way and I am still reviewing the US listings

1.2 checking wiki pages (bronsen) - was not able to keep to my commitment from last time: I haven't checked any wiki pages :/ (bronsen) I shall try to review at least one page until #NextTime, to get going :)

1.3 map team feedback nothing has changed; offer still stands


2 Meetbot (sva) said that jomat: had installed a meetbot afaik - so thats a news to be reported ;)


3 Hackerspaces.org Geekend

  • what is it

a weekend to work on hackerspaces.org - we need more input from people interested in order to define goals for the event

  • who is it for

people who are interested / want to work actively on hackerspaces.org

  • what team will organize it

tbd perhaps sva, aimeejulia

  • when is a good time for it

aimeejulia to check with people who attended the camp if they would like to participate and when / which months / dates are desireable tbd

  • where? what about hosting (couchsurfing hotels etc)?

Kuckucksmuehle (https://wiki.ecohackerfarm.org/kuckucksmuehle) - can host currently up to 14 people (possible more after October) @ €25 per person per day (includes vegetarian food and accomodation) tbd

  • sponsors

CCC eV ? tbd

4. meeting at 36c3

would be good to organise a room for a meeting (2h) - aimeejulia to take care of this

5. next meeting

5.1 self-proclaimed editors report their progress in reviewing wiki pages 5.2 discuss hackerspaces.org geekend updates


  1. hackerspaces monthly meeting
    1. 8th December 2019 14:00 UTC on freenode #hackerspaces

attendees: <insert your name here>

   * Josh P, Melbourne Makerspace, FL, USA
   * rtn, ralptheninja
   * aimeejulia
   * bronsen
   * BuZz
   * myself
   * zeno4ever
    1. agenda points
      1. check-in
  • who is here and how are we all doing?
   * rtn - doing well, under the circumstances
   * aimeejulia - here but nursing a very sick Podha (the dog) so a little distracted
   * myself - awake now!
   * buZz
   * bronsen - very late, didn't do much
      1. advice for hackerspaces
  • How to advertise/marketing/etc to get new members.
   * have a nice name for the hackerspace is a good start (aimeejulia)
   * make sure the space is registered on https://wiki.hackerspaces.org (rtn)
   * we actually do not use paid for advertising, what we do is organising regular meetups and I give some talks at conferences that I go to (aimeejulia)
   * collaborate with other associations that have similar or related interests (aimeejulia & myself)
   * word of mouth (buZz, rtn)
   * twitter, faceboob not worth the effort
   * good blog content that people link to, project writeups and stuff, has given us nice high pagerank so we always come up first when people search for related terms in the area, but getting people to write documentation is a slippery problem (myself)
   * wear your merch (myself)
   * If you have a vinyl cutter, make it a stop on the tour and make sure every visitor has the chance to cut a bumper sticker that they can put on their own car before they leave. You'll be seeing 'em around town _everywhere_ after a few months.(myself)
   * Regular events (don't have to be frequent) allow the curious to "see some action" (bronsen)
   * Get a ML for the space to help with internal and external communication (rtn)
   * Reach out to other local communities to find unexpected overlap (rtn)
  • How to keep current members interested and coming in to work on their projects/group projects.
   * I think, is more like avoiding burnout. Interest generates itself unless something's deflating it. (myself)
   * engage in others and their projects, ask how the project is going and how they are doing (rtn)
   * we have a lot of people who'd rather fuss over administrivia, and "SHUT UP AND HACK" hasn't made it into our local lexicon as forcefully as I'd like. (myself)
   * I really want to make it clear that the rules-lawyers are simply not welcome if all they're going to do is nag people. Being excellent is more than just being compliant to every letter.(myself)
   * I think mentorship can help turning new members into active members(bronsen)
   * giving them root on everything also works :D (buZz)
   * never hack alone: hackerspaces, and thus hacking, are social (bronsen)
   * Mentorship works best when it's not helping someone do the task they're interested in (they have to do that on their own), but helping them navigate the group and space so they become independent sooner. (myself and buZz)
  • Residencies?
   * ecohackerfarm gives you a room and food for 25 hours a week of volunteering (https://wiki.ecohackerfarm.org/kuckucksmuehle:start)
   * most spaces don't offer anything similar
  • Ideas for public events?
   * Repair Cafes
   * Learn to use $tool (table saw, soldering iron, power drill)
   * hackevents
   * Retro gaming night
   * Take-it-apart events for kids
   * bring a friend evening
   * c3talks 
   * open day, waffles, cakes
   * Arduino workshops
   * go somewhere else as a group (myself, bronsen)
  • Turning event attendees into advocates, if not future members
   * Gotta differentiate this from "pay for an experience" outfits in town (myself)
   * I've always tried to take an "intermission" in the middle of an event, for someone other than the main presenter, to stand up and talk about the group a bit, what it means to be a community nonprofit, etc. (while the presenter can go get a drink or whatever). And I'll take questions from the attendees. (myself) 
  • Where to reach out to get help with e.g. funding or sponsoring to cover costs like rent etc? (rtn)
   * having several membership tiers with varying fees can perhaps help (bronsen)
   * companies will sponsor --as in donate their products--, but will want a tax-deductable receipt (bronsen)
   * organise a fundraiser (hello recursion ;P)
   * Add a donation page to your homepage; bitcoin, PayPal etc (rtn)
      1. general hackerspaces.org matters
  • shall we organise and meetup session at congress for hackerspaces.org? (aimeejulia)
   * yes (bronsen, rtn)
       * who will set up the meetup?
       * I can do it - aimeejulia
  • update on hackerspace census
   * https://wiki.hackerspaces.org/Hackerspace_Census_2019 - last update was in October... I am hoping to pick this up again soon (aimeejulia)
   * Could be something to discuss/bring up at 36c3 (rtn)


2019-12-30 @ 36c3[edit]

30/12/2019 12:00 - 13:00

Attending: tdor, aimeejulia, dagda, adam, warning, hsbe + others

__________________________

Agenda:

  • introduction
  • current status:
   - run by volunteers
   - handover of infrasturcture access from old people to new people
   - active community on irc freenode channel
   - census update
  • infrastructure distributed ideas:
   - zeronet, ipmf, - published on the networks, a test bed for decentralised network that looks like a normal nice looking website with a map right at the front
  • performance improvement:
   - it could be an idea to update the dependencies, topic linked with decentralised network 
  • hackerspaces set up tips:
   - new person setting up a hackerspace in poznan, workshop hack the hackerspace discuss how to structure a small to medium hackerspace managing people interfaces.
   - hackerspace.design - hackerspace blueprint
  • legacy... can we put it on the archive.org :
   - it currently bugs out because of the old wiki on them
  • making the wiki more user-friendly:
    - there is an offer from hsnl/hsbe to redesign the landing page
  • updating contact list on the wiki
  • enabling more hands-on help:
   - suggestion to use gitlab for tracking issues