12 | Now you understand. Let's go to computer Brighton 13 |
14 | 15 |16 | You can read the overview of computer and the rules here. 17 |
18 |19 | Is anyone interested in a Computer meetup in Brighton? 20 |
21 | 22 |23 | If you have any suggestions for venues, or if you want to help organise Computer Brighton, get in touch with @badgermind or @computebrighton via Twitter 24 |
25 | 26 | 27 | -------------------------------------------------------------------------------- /us_newyork.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - New York 4 | --- 5 |Read the overview if you haven't already.
8 | 9 |//
10 | 11 |//
21 | 22 | 23 |The following are the previous organizers; feel free to let us know if you're interested in helping organize future meetings. For general questions, please read Running A Group.
26 | 27 |Read the overview if you haven't already / Lisez l'introduction s'il vous plaît si vous ne l'avez pas déjà fait.
7 |//
8 |First meeting / Premier rendez-vous:
10 |Location: Rockaberry on St. Denis. (They have good coffee, cakes and beer / Ils ont du bon café, du gâteau et de la bière)
11 |Time / Heure: 7pm Thursday Oct 24th / 7pm Jeudi le 24 Octobre
12 |All this is up for debate, so let's talk about it on Twitter or IRC! / Tout ceci est ouvert au débat, on peut discuter sur Twitter ou IRC!
13 |//
14 |Read The overview if you haven't already.
10 | 11 | 12 |We've just gotten started! Join us on IRC if you want in. :)
15 | 16 |We're still yet to settle a regular schedule, but let's get a calendar soon (!)
17 | 18 |We are currently planning our first meeting. Give scheduling input on doodle. 22 | 23 |
Talk to us if you want to attend, or just turn up!
26 | 27 |If you want to attend, say hello to someone, and they will drag you along.
37 | -------------------------------------------------------------------------------- /uk_birmingham.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Birmingham 4 | --- 5 |12 | Now you understand. Let's go to computer Birmingham 13 |
14 | 15 |16 | You can read the overview of computer and the rules here. 17 |
18 | 19 |20 | We're going to be quite flexible with the Computer meetup in Birmingham and see how it fits in with upcoming events for the next month with an aim to get our first one some time in November 2014. 21 |
22 | 23 |24 | We're currently trying to figure out what to do for the first meetup, but most likely it will be somewhere in Central Birmingham (possibly Urban or Yorks) and we will rotate locations to restaurants and bars if people wish. 25 |
26 | 27 |28 | If you have any suggestions, try getting in touch with @omarqureshi and they'll try and do their best to sort you out. 29 |
30 | 31 |32 | We don't have an IRC channel dedicated to computer yet, but, you can find quite a lot of us on Birmingham.io or talk to some of us in #wmrug. 33 |
34 | -------------------------------------------------------------------------------- /se_stockholm.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Stockholm 4 | --- 5 |7 | Read The Overview if you haven't already, especially the code of conduct. 8 |
9 |10 | So far, we are 3-4 people interested in starting a Stockholm group. Add questions and suggestions to this file. 11 |
12 | 13 |15 | No proper date suggestions yet, please provide your input. 16 | 17 | Preferrably a weekday, not too late? 18.00? Go on for a few hours or as long as we have fun. 18 |
19 | 20 |22 | Suggest locations here. Accessibility should be key. 23 |
24 |25 |
33 | Stockholm page originally created by @systerfrida and @ADropOfAwesome. Ping us if you're interested or want assistance in adding something. 34 |
35 | -------------------------------------------------------------------------------- /uk_central_london.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous Central London 4 | --- 5 |7 | Read The overview if you haven't already, especially the code of conduct. 8 |
9 | 10 |The Central London group is currently inactive — please see the 13 | London group for ongoing meetups.
14 | 15 |The nearest station is Holborn
22 | 23 |We're open to other venue suggestions in Zone 1, especially those that are accessible, well connected, and not necessarily in a pub, or loud
24 | 25 |Our first meeting will be Thursday the 21st of Novemeber, from 18.00, at The Holborn Whippet
28 | 29 |Talk to us if you want to attend, or just turn up!
32 | 33 |On twitter: @doismellburning, @alsothings
34 | 35 |If you want to attend, say hello to someone, and they will drag you along.
36 | -------------------------------------------------------------------------------- /uk_oxford.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Oxford 4 | --- 5 |12 | Now you understand. Let's go to computer oxford. 13 |
14 | 15 |16 | You can read the overview of computer and the rules here. 17 |
18 |19 | We're going to be quite flexible with the Computer meetup in Oxford and not stick to "every nth Monday at location." 20 |
21 |22 | The first Computer Oxford took place on 7th October 2013 and it went well, with 12 people attending. We'll be thinking about the next Computer Oxford shortly. 23 |
24 |25 | If you have any suggestions for venues, or if you want to organise the next Computer Oxford, get in touch with @omgmog or @lurst or @janepipistrelle via Twitter, or submit a GitHub issue to @omgmog's fork of computer. 26 |
27 |28 | Most of us idle in #oxford-geeks on irc.freenode.net if you want to chat, anybody is welcome. 29 |
30 | -------------------------------------------------------------------------------- /style.css: -------------------------------------------------------------------------------- 1 | body { 2 | font-size: 130%; 3 | font-family: monospace; 4 | } 5 | .accessibility-menu{ 6 | float:right; 7 | line-height:130%; 8 | } 9 | 10 | .accessibility-menu .bow{ 11 | display:none; 12 | color:black!important; 13 | background-color:white; 14 | padding:0.2em; 15 | } 16 | 17 | .accessibility-menu .wob{ 18 | color:white; 19 | background-color:black; 20 | padding:0.2em; 21 | } 22 | #accessibility:target, #accessibility.inverted { 23 | color:white; 24 | background-color:black; 25 | } 26 | #accessibility:target a, #accessibility.inverted a { 27 | color:white; 28 | } 29 | #accessibility:target .wob, #accessibility.inverted .wob { 30 | display:none; 31 | } 32 | #accessibility:target .bow, #accessibility.inverted .bow { 33 | display:inline; 34 | } 35 | section { 36 | max-width: 50em; 37 | margin: 2em auto; 38 | padding: 0 10px; 39 | } 40 | 41 | section#license { 42 | border-top: dashed 1px black; 43 | } 44 | 45 | h1, h2, h3, h4, h5, h6 { 46 | font-size: 100%; 47 | } 48 | 49 | h4 { 50 | margin-top: 2em; 51 | } 52 | 53 | ul { 54 | padding-left: 0; 55 | } 56 | 57 | li { 58 | list-style-type: none; 59 | line-height: 1.5; 60 | } 61 | 62 | ul.rules > li { 63 | line-height: 1.8; 64 | } 65 | 66 | ul.groups > li { 67 | font-weight: bold; 68 | margin-top: 1em; 69 | margin-bottom: 0.5em; 70 | } 71 | 72 | ul.groups li li { 73 | font-weight: normal; 74 | } 75 | 76 | ul li::before { 77 | content : '- '; 78 | } 79 | 80 | ul.groups li::before { 81 | content: ''; 82 | } 83 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## Computer Anonymous 2 | 3 | A meeting for people who don't know what they are doing on computer. The ideals and rules of the meetup are documented in index.html. 4 | 5 | We want to create a social group for people in and around tech, from all backgrounds, where they feel comfortable and welcome. 6 | 7 | We're not an outreach or an educational group, although both are important to us, we're primarily a technology related meetup, but with a code of conduct. 8 | 9 | If you want to start your own meetup, fork and open a pull request. We also love feedback and translations. 10 | 11 | Meeting pages and changes will almost always get merged straight away, but other changes take time. 12 | 13 | ## Writing Guidelines 14 | 15 | - We want to be explicit, not implicit, but we want to avoid special cases and lists where possible. 16 | - We want to avoid both slang and jargon, especially in the rules. We want to be conversational, not bureaucratic or formal in tone. 17 | - We have a complexity budget, we cannot make an exhaustive set of rules, and we have to translate things so the less words the better. 18 | - Smaller changes to the Rules have a higher chance of success, Larger changes take more discussion. Edit one line at a time. 19 | - The Code of Conduct is not a solution to people's behavior, but it's about admitting there is a problem. 20 | - Please avoid gendered language. This means don't use "guys", "guys and gals", "dude". We suggest "meatbags", "people", "peeps" or "folks". 21 | 22 | 23 | 24 | All content and contributions are licensed under CC0. 25 | -------------------------------------------------------------------------------- /ca_nl_stjohns.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous — St. John's, NL, Canada 4 | --- 5 |Read The overview if you haven't already.
8 | 9 |//
10 | 11 |All of this has just kind of been thrown together. If you have any alternate suggestions, speak up!
16 | 17 |Time: Tuesday, October 8, 2013 at 18:00
18 |Location: Atlantic Place, 215 Water St.
19 |//
26 | 27 |YellowBelly Brewery, 288 Water Street
30 |We need an option that's not in downtown...
37 | 38 |//
39 | 40 |Talk to us if you want to attend, or just turn up!
43 | 44 |Ping us! Er... me!
49 | -------------------------------------------------------------------------------- /uk_cardiff.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Cardiff 4 | --- 5 |7 | Read The Overview if you haven't already, especially the code of conduct. 8 |
9 | 10 |14 | At the moment we're investigating to see how much interest there is for a Meeting in Cardiff. Once we hit a critical mass (5 is good, right?) we'll start looking into dates that work for all. If you're interested in coming, either fork the repository, tweet me at @sgsabbage, email me at: my twitter handle AT gmail DOT com, or find me on the ##computer or ##computer.cardiff IRC channels on Freenode. 15 |
16 | 17 |20 | Urban Tap House - I've heard nothing but praise for this place, though I don't know what it's like for groups to meet up. 21 |
22 | 23 |24 | Milgi - It has a yurt! Also, a lovely environment, heated garden, hot drinks, vegetarian and vegan food. 25 |
26 | 27 |28 | A Shot In The Dark - Well-known independent coffee house on City Road. Again, very nice atmosphere, free wifi, large upstairs with comfortable sofas. 29 |
30 | 31 |32 | I've just added a few to get us started, but if you have any favoured venues that aren't on this list, let me know, or fork the repo and add them! 33 |
34 | -------------------------------------------------------------------------------- /de_berlin.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonym - Berlin 4 | --- 5 |If you don't understand where you are here, please read this introduction first
16 |Wenn du noch nicht verstehst wo du hier bist, bitte lies zuerst diese Einleitung.
17 | 18 |We're working out the first date.
22 |Wir gucken gerade, wo/wie/wann wir uns das erste Mal treffen werden.
23 | 24 | 25 |We might talk in English. We might talk in German. We might not talk. You're welcome if you can do any of these.
29 |Vielleicht reden wir Englisch. Vielleicht reden wir Deutsch. Vielleicht reden wir gar nicht. Wenn du eins davon kannst, dann bist du willkommen.
30 | 31 | 32 |On IRC: irc.libera.chat ##computer
36 |Auf IRC: irc.libera.chat ##computer
37 | 38 |@WhyComputer on twitter
39 |@WhyComputer auf Twitter
40 | -------------------------------------------------------------------------------- /_layouts/base.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 |
39 |
41 | 
42 |
43 |
44 | To the extent possible under law, the person who associated CC0 with this work has waived all copyright and related or neighboring rights to this work.
45 |
7 | Read The overview if you haven't already, especially the code of conduct. 8 |
9 | 10 |The North London group is currently inactive — please see the 13 | London group for ongoing meetups.
14 | 15 |The organisers are looking to create a non-drinking relaxed North London event as an alternative to the typical "meet in a pub, don't drink if you don't want to" event. We recommend people bring craft projects, instruments, or anything else people might enjoy.
18 | 19 |This is an experiment.
20 | 21 |Presently looking for meditation spaces to host a North London meetup. An ideal venue will have:
22 | 23 |Venue Suggestions:
33 | 34 |Talk to us if you want to attend, or just turn up!
47 | 48 |On twitter: @didlix
49 | 50 |If you want to attend, say hello to someone, and they will drag you along.
51 | -------------------------------------------------------------------------------- /uk_london.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - London 4 | --- 5 |Read The overview if you haven't already, especially the code of conduct.
8 | 9 |No future events are currently planned. If you’d like to organise one, please do so! See Issue #350 for some suggested venues.
12 | 13 |Date/time/venue: Wednesday June 3rd 2015, at St George's Tavern, 14 Belgrave Road, London, SW1V 1QD, from 6pm.
16 | 17 |Getting there and finding us: The closest station is Victoria. Once in the pub, look out for a "Computer Anonymous" sign.
18 | 19 |Accessibility: Step-free to enter, to the bar, to the seating, and to the RADAR-locked accessible toilet.
20 | 21 |Food and drink: Six real ales at £3.60–£4/pint. Lime and soda £1.20/pint. Main courses (including four vegetarian) £9–£12.25 (vegetarian main courses £9.50-£10.50).
22 | 23 | 24 | 25 |Once upon a time, there were four London Computer Anonymous groups, the most active of which was East London. 28 | West London also met on occasion, but rarely actually in the west. 29 | Central London met once, but sadly, North London still haven't.
30 | 31 |One day, these groups may become active again, but for now, the group formerly known as West London, is holding irregular meet ups, under the guise of Computer Anonymous - London.
32 | -------------------------------------------------------------------------------- /uk_manchester.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Manchester 4 | --- 5 |7 | Read The Overview if you haven't already, especially the code of conduct. 8 |
9 | 10 |14 | We haven't planned our first Meeting for Manchester yet, we're still working out where we want to hold it! If you have any ideas, fork the repository or send suggestions to me on 15 | twitter, @sjmarshy, whichever is easier. 16 |
17 | 18 |20 | The Font Bar is super cheap, however it's small and noisy and gets pretty full, so it might not be ideal for a large group 21 |
22 | 23 |24 | Footage is larger than Font, but it can still be a little loud 25 |
26 | 27 |28 | The Bay Horse is more central than the others, located in the northern quater. Nice atmosphere, too. 29 |
30 | 31 |32 | Brew Dog always looked pretty interesting, it's meant to be good for beers if you're into that sort of thing, and it's nice and central. 33 |
34 | 35 |36 | Lass O' Gowrie was a suggestion and it looks pretty good. Central location, and on their web page there's an image of transformers above the bar, which might be a good sign. 37 |
38 | 39 |40 | Sandbar looks like another possibility - close to the Lass O' Gowrie, so a possible back-up? 41 |
42 | 43 |44 | We need a few more suggestions for venues really! If you have any in mind, Let me know! 45 |
46 | -------------------------------------------------------------------------------- /au_ballarat.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Ballarat 4 | --- 5 |Computer.
8 | 9 |Computer ?
10 | 11 |Computer :-(
12 | 13 |Now you understand. Let's go to Computer Ballarat.
14 | 15 |Read the overview and the 16 | rules at Computer 17 | Anonymous if you haven't already.
18 | 19 |We've only just started! We haven't yet decided on long-term 22 | meeting plans.
23 | 24 |Time: Sunday 8th February 2015, 2pm-5pm AEST
27 | 28 |Location: The 29 | Mallow, 20 Skipton St, Ballarat VIC 3350
30 | 31 |(none yet)
34 | 35 |38 | Find us here: 39 |
40 | 41 |Some of the folks you might see at Computer Ballarat include:
47 | 48 |Talk to any of us if you want to attend, or just turn up!
56 | 57 |Got a suggestion, question, or issue? raise an 61 | issue on the 63 | computerballarat github repository
64 | 65 |Want to add your name, or any other information, to this 66 | page? Raise a pull request to the above repository! Need help? 67 | Github help is a good 68 | place to start. Or just raise an issue as above.
69 | 70 | -------------------------------------------------------------------------------- /us_denver.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Denver 4 | --- 5 |Read the overview if you haven't already.
8 | 9 |//
10 | 11 |Please place your name below if you are planning to attend.
27 | 28 |//
36 | 37 | 38 |Contact any of the following if you would like to attend, to help organize, or have any feedback!
41 | 42 |7 | Read The overview if you haven't already, especially the code of conduct. 8 |
9 | 10 |We're on haitus. Please see the London group for ongoing meetups.
13 |We meet on the first Thursday of the month, at The Pembury Tavern, 90 Amhurst Rd, E8 1JH.
Check out the @whycomputer twitter account for specific updates.
16 | 17 |See on Google Calendar, or load the iCal file into your own calendar.
The Pembury Tavern, 90 Amhurst Rd, E8 1JH
21 | 22 |The two nearest stations are Hackney Downs (National Rail), and Hackney Central (Overground)
23 | 24 |We're open to other venue suggestions, especially those that are accessible, well connected, and not necessarily in a pub, or loud
32 | 33 |Talk to us if you want to attend, or just turn up!
36 | 37 |On twitter: @ntlk @didlix @tomstuart @drmaciver @samphippen @mistertim @alsothings @hyper_linda
38 | 39 |If you want to attend, say hello to someone, and they will drag you along.
40 | -------------------------------------------------------------------------------- /us_austin.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Austin 4 | --- 5 |Read the overview if you haven't already.
8 | 9 |//
10 | 11 |//
20 | 21 |These things are all up for debate and discussion, use IRC and Twitter!
40 | 41 |//
42 | 43 |Vote on the next meeting at our Doodle page.
46 | 47 |//
48 | 49 |Talk to us if you want to attend or just turn up!
54 | 55 |Ping us!
62 | -------------------------------------------------------------------------------- /de_hamburg.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonym - Hamburg 4 | --- 5 |If you don't understand where you are here, please read this introduction first.
16 |Wenn du noch nicht verstehst wo du hier bist, bitte lies zuerst diese Einleitung.
17 | 18 |The group's ultimate, permanent Doodle for finding the next meeting time.
21 |Der ultimative, permanente Doodle um die passende Zeit zu finden.
22 | 23 | Link to the doodle poll. 24 | 25 |Time - Zeit:
26 |searching...suche...
27 | 28 |Location: searching....suche...
29 | 30 |We might talk in English. We might talk in German. We might not talk. You're welcome if you can do any of these.
34 |Vielleicht reden wir Englisch. Vielleicht reden wir Deutsch. Vielleicht reden wir gar nicht. Wenn du eins davon kannst, dann bist du willkommen.
35 | 36 |We have an kind-of official twitter account you can follow for local news and discussions @WhyComputer_HH.
40 |Wir haben ein quasi-offizielles Twitter Konto, das für Neuigkeiten und Diskussionen genutzt wird: @WhyComputer_HH.
41 | 42 |And here are some faces:
43 | 44 |@greelgorke on twitter
45 |@mparramon on twitter
46 | 47 |If you want to attend, say hello to someone, and they will drag you along.
48 |Wenn du kommen willst, sag "hallo" zu jemand, und sie/er wird dich einpacken und mitnehmen.
49 | 50 |On IRC: irc.libera.chat ##computer
51 |Auf IRC: irc.libera.chat ##computer
52 | 53 |@WhyComputer on twitter
54 |@WhyComputer auf Twitter
55 | 56 |Time - Zeit:
60 |6. November 2013
61 | 62 |Location: Cafe Absurd
63 | -------------------------------------------------------------------------------- /us_sanfrancisco.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - San Francisco 4 | --- 5 |Read The overview if you haven't already.
10 | 11 | 12 |Join us on IRC at ##computer on irc.libera.chat if you want in. :)
15 | 16 |Computer Anonymous SF has been on hiatus for a while but tends to meet on occasional Saturdays for brunch
17 | 18 |Time: Saturday, April 7th, 2018 at 11:00am PDT
21 |Location: Cosecha, 907 Washington St, Oakland, CA 94607
22 | 23 |Please sign up via the eventbrite page or ping Jay (@explain_analyze) or tdfischer (@tdfischer_ / irc) if you're attending, to make sure we confirm enough space / seats / stuff :)
24 | 25 |Time: Saturday, February 18th, 2017 at 11:00am PDT
28 |Location: Cosecha, 907 Washington St, Oakland, CA 94607
29 | 30 |Time: Saturday, December 3rd, 2016 at 11:00am PDT
31 |Location: Cosecha, 907 Washington St, Oakland, CA 94607
32 | 33 |Time: Saturday, July 9th, 2016 at 11:00am PDT
34 |Location: Cosecha, 907 Washington St, Oakland, CA 94607
35 | 36 |Time: Saturday, June 11th, 2016 at 11:00am PDT
37 |Location: Cosecha, 907 Washington St, Oakland, CA 94607
38 | 39 |Time: Saturday, April 9th, 2016 at 11:00am PDT
40 |Location: Cosecha, 907 Washington St, Oakland, CA 94607
41 | 42 |Time: Saturday, November 14th, 2015 at 11:30am PDT
43 |Location: Cosecha, 907 Washington St, Oakland, CA 94607
44 | 45 |Talk to us if you want to attend, or just turn up!
48 | 49 |If you want to attend, say hello to someone, and they will drag you along.
62 | -------------------------------------------------------------------------------- /uk_west_london.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - West London 4 | --- 5 |Read The overview if you haven't already, especially the code of conduct.
8 | 9 |The West London group is currently meeting under the guise of the 12 | Computer Anonymous — London group. See that page for meetup announcements.
13 | 14 |Suggestions in the west:
16 |Venue suggestions:
31 |The oddly named West London group met at: The Mad Hatter, 45 | 3-7 Stamford Street, London, SE1 9NY, on Wednesday 15th January, from about 18:30.
46 |Facebook event: Computer Anonymous: Mad Hatter, London
50 |----------------------------------------------------------------------------------
52 |The West London group met on 18th December 2013 at The Rylston in Fulham, from 18:30. 53 | 54 | The Rylston is a short walk from Fulham Broadway, West Brompton and West Kensington tube stations. 55 | 56 | The pub was quiet, despite a quiz happening. Pizzas were consumed, space invaders were cross-stitched, old computer magazines were read (including wonderful magazines from the 1980s! Thanks Tyrone!) and there were these stickers:
57 |
The oddly named West London group met at: The Mad Hatter, 61 | 3-7 Stamford Street, London, SE1 9NY, on Thursday 24th October 2013, from about 18:30. 62 |
Copies of Amiga Power were read, space invaders and Pac-Man ghosts were cross-stitched, people attempted regular expression crosswords, and read print-outs of esoteric languages such as the My Little Pony inspired FiM++. 63 | Cider, lemonade and lime, beer, and other such beverages were drunk, pies were eaten. Stickers were stuck. (Thanks Tef!) 64 | And also, most importantly, many wonderful conversations were had. 65 | 66 | This was the Facebook event: Computer Anonymous West London meet-up
67 |----------------------------------------------------------------------------------
68 | 69 |The West London group met at the Willow Walk near 70 | Victoria Station on Thursday 26th June 2014, from 6pm (see 71 | Facebook event).
72 | 73 |Venue suggestions in central London that might be convenient for people in west London:
81 |Read the overview if you haven't already.
7 |We meet on the last Wednesday of each month at 7pm, generally at pubs in the Camberville area.
8 |If you're new: usually, there will be some anons hanging out in front of the venue until 7:10 or so, waiting for others to show up, so look for them and say hi! You can also try tweeting some of the folks listed under "the people" -- @patcable makes it to most meetups. We haven't had a @WhyCompBos meetup in a while, and @kmbrlynn is trying to revive it! So you can reach out to her too.
9 |//
10 | 11 |When: Wednesday, March 29th, 2017, at 7pm
13 |Location: Aeronaut Brewing, 4 Tyler St, Somerville, MA 02143 [Google Maps]
14 | 15 |There are a few low-key events at Aeronaut that night - a story slam, food provided by a culinary startup, and jazz later on (here is their event calendar). If you have trouble finding us, try tweeting @patcable or @kmbrlynn
16 | 17 |(Meetup locations will be chosen from this list at semi-random, unless specific places are requested via pull request / tweets @WhyCompBos / etc, in which case we can totally go with popular requests :) )
19 |//
29 | 30 |@WhyCompBos on Twitter
32 |Talk to us if you want to attend or just turn up!
33 |Internet high-five/shoutouts/etc. to @flowerhack* 43 | for originally forking the whycomputer repo and getting the Boston party started.
44 | 45 |* moved away from Boston but we still love them <3
46 | 47 |Ping us!
48 | -------------------------------------------------------------------------------- /running_a_group.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Starting a Computer Anonymous 4 | --- 5 |If you aren't familiar with git and/or Github, contact the following people to do it for you:
8 | 9 | 13 | 14 |Starting local groups is excellent and highly encouraged, but in order to maintain the integrity of the groups, there are a few things you should keep in mind.
17 | 18 |Venues should be chosen with accessibility in mind - be it physical accessibility, financial accessibility, or generally safe places for all people.
20 |Many groups will likely be meeting in pubs and bars, but this certainly isn't mandatory and might not even be desired. It's worth exploring alternatives.
21 | 22 |Finding a good time for everyone is difficult, if not impossible, but you should make an attempt to use tools like doodle to find times that work best.
25 | 26 |GitHub has worked well for us in planning meetups and answering questions. We've avoided tradtional mailing lists, because of spam, and general lack of moderation. With GitHub, discussions tend to stay on topic, we can close, and reference issues. We've found that creating an account, setting up notices, is just as annoying as a traditional mailing list. We also don't get email on the first of the month.
29 | 30 |Git and IRC are great tools for collaboration, but not everyone is familiar with them. We want to include and encourage participation from people with all backgrounds, so knowledge of these systems shouldn't be a prerequisite.
Be available in other mediums so people can get help if they need it.
33 | 34 |Remember, everyones safety is a top priority. In order for these groups to survive, people need to be held accountable. Someone should be available to handle problems within the group.
36 | 37 |Try to have more than one point of contact, and if possible try to get people from different groups and backgrounds to volunteer. One person may burn out, and the more diverse the volunteers, the better.
40 | 41 |We should aim to handle all incidents in a consistent fashion. Let the person know in plain language what they did wrong and what action is being taken to deal with the situation. It is important to make this about the behaviour/words, not the person.
44 | 45 |After this point, if possible do not engage with the person who was causing the problem and give them time to cool off. If you do need to engage with them, offer them information without jokes or attacks, and disengage respectfully if it is a lost cause.
46 | 47 |Ask the person/s who suffered if they would like further support. Listen to what they say and make sure their needs are feedback to the group so we can all learn and improve. It is vital to let the person reporting know the methods of action you intend to take before taking them. Sometimes they have a different context with the person who has violated the code of conduct - they may worry about their physical/professional/personal safety with the person, so we want to make sure that we respond in a way that does the least harm to the reporter.
48 | 49 |If someone engages in behaviour that violates the code of conduct, organisers or designated volunteers may take action. Make sure that people attending the meeting are aware of who to contact (this should be on meeting pages; and made clear at the event).
52 | 53 |Our expectation is that if someone is asked to stop a harassing or otherwise inappropriate behaviour, they will do so immediately. If not the organisers may ask them to leave.
54 | 55 |We can expect to get some questions such as "can cis white straight guys come to this group without feeling uncomfortable?". Channel mods/tweeters should deal with these by referring to the 101 pages. It is understandable that people will get annoyed by such questions when they have to deal with them on a daily basis so please avoid tone policing people's responses and instead state that our purpose is not education on these issues and redirect to factual information.
58 | 59 |Similarly nobody should feel obligated to continually carry out 101-style education–such requests should be referred to our statement of purpose and the 101 links pages.
60 | 61 |If an incident occurs such that an individual is banned, this should be logged. If they tweet/email asking about this, reiterate what they did, post the logs and (briefly) why this was problematic.
62 | 63 | 64 | 65 | -------------------------------------------------------------------------------- /LICENSE.txt: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED HEREUNDER. 6 | Statement of Purpose 7 | 8 | The laws of most jurisdictions throughout the world automatically confer exclusive Copyright and Related Rights (defined below) upon the creator and subsequent owner(s) (each and all, an "owner") of an original work of authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the purpose of contributing to a commons of creative, cultural and scientific works ("Commons") that the public can reliably and without fear of later claims of infringement build upon, modify, incorporate in other works, reuse and redistribute as freely as possible in any form whatsoever and for any purposes, including without limitation commercial purposes. These owners may contribute to the Commons to promote the ideal of a free culture and the further production of creative, cultural and scientific works, or to gain reputation or greater distribution for their Work in part through the use and efforts of others. 11 | 12 | For these and/or other purposes and motivations, and without any expectation of additional consideration or compensation, the person associating CC0 with a Work (the "Affirmer"), to the extent that he or she is an owner of Copyright and Related Rights in the Work, voluntarily elects to apply CC0 to the Work and publicly distribute the Work under its terms, with knowledge of his or her Copyright and Related Rights in the Work and the meaning and intended legal effect of CC0 on those rights. 13 | 14 | 1. Copyright and Related Rights. A Work made available under CC0 may be protected by copyright and related or neighboring rights ("Copyright and Related Rights"). Copyright and Related Rights include, but are not limited to, the following: 15 | 16 | the right to reproduce, adapt, distribute, perform, display, communicate, and translate a Work; 17 | moral rights retained by the original author(s) and/or performer(s); 18 | publicity and privacy rights pertaining to a person's image or likeness depicted in a Work; 19 | rights protecting against unfair competition in regards to a Work, subject to the limitations in paragraph 4(a), below; 20 | rights protecting the extraction, dissemination, use and reuse of data in a Work; 21 | database rights (such as those arising under Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, and under any national implementation thereof, including any amended or successor version of such directive); and 22 | other similar, equivalent or corresponding rights throughout the world based on applicable law or treaty, and any national implementations thereof. 23 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and unconditionally waives, abandons, and surrenders all of Affirmer's Copyright and Related Rights and associated claims and causes of action, whether now known or unknown (including existing as well as future claims and causes of action), in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each member of the public at large and to the detriment of Affirmer's heirs and successors, fully intending that such Waiver shall not be subject to revocation, rescission, cancellation, termination, or any other legal or equitable action to disrupt the quiet enjoyment of the Work by the public as contemplated by Affirmer's express Statement of Purpose. 24 | 25 | 3. Public License Fallback. Should any part of the Waiver for any reason be judged legally invalid or ineffective under applicable law, then the Waiver shall be preserved to the maximum extent permitted taking into account Affirmer's express Statement of Purpose. In addition, to the extent the Waiver is so judged Affirmer hereby grants to each affected person a royalty-free, non transferable, non sublicensable, non exclusive, irrevocable and unconditional license to exercise Affirmer's Copyright and Related Rights in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the "License"). The License shall be deemed effective as of the date CC0 was applied by Affirmer to the Work. Should any part of the License for any reason be judged legally invalid or ineffective under applicable law, such partial invalidity or ineffectiveness shall not invalidate the remainder of the License, and in such case Affirmer hereby affirms that he or she will not (i) exercise any of his or her remaining Copyright and Related Rights in the Work or (ii) assert any associated claims and causes of action with respect to the Work, in either case contrary to Affirmer's express Statement of Purpose. 26 | 27 | 4. Limitations and Disclaimers. 28 | 29 | No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document. 30 | Affirmer offers the Work as-is and makes no representations or warranties of any kind concerning the Work, express, implied, statutory or otherwise, including without limitation warranties of title, merchantability, fitness for a particular purpose, non infringement, or the absence of latent or other defects, accuracy, or the present or absence of errors, whether or not discoverable, all to the greatest extent permissible under applicable law. 31 | Affirmer disclaims responsibility for clearing rights of other persons that may apply to the Work or any use thereof, including without limitation any person's Copyright and Related Rights in the Work. Further, Affirmer disclaims responsibility for obtaining any necessary consents, permissions or other rights required for any use of the Work. 32 | Affirmer understands and acknowledges that Creative Commons is not a party to this document and has no duty or obligation with respect to this CC0 or use of the Work. -------------------------------------------------------------------------------- /index.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous 4 | --- 5 |Now you understand. Let’s go to computer anonymous.
12 | 13 |This page is also available in the following languages:
14 |See if there’s one already where you live at the bottom of the page, or start one by forking the repository, making your changes, and submitting a pull request.
19 | 20 |This might be the group for you if you want to meet socially conscious nerds to talk about interesting things. This is not an entrepreneurial meetup, nor is it networking: It is a support group, a place to meet good people and talk about good and bad things.
29 | 30 |Although education and outreach are both important to us, the primary goal is to create a social group for people in and around tech, from all backgrounds, where they feel comfortable and welcome.
31 | 32 |There aren’t regularly organized talks, workshops, or otherwise. We don’t have tickets, we don’t have namebadges. We’re striving to be as disorganised and informal as possible. We will talk computer a lot but we’d also like to not talk computer too. At the end of the day we’re just wanting not to be alone when we find ourselves saying "computer".
33 | 34 |If you’re from a background which isn’t well-represented in most geeky meetups, come along – we want to make a difference.
37 |If you’re from a background which is well-represented in most geeky meetups, come along – we want your help making a difference.
38 |If you’re worried about not being computer enough, come.
39 |If you think you’re an imposter, come.
40 |If your day job isn’t code, come.
41 |This isn’t a group of experts, just people.
42 |We are interested in the social and technical problems.
43 |This is a support group. No-one knows what they are doing.
44 | 45 |48 | A code of conduct applies wherever we gather to talk computer. This is true both in person and online. 49 |
50 | 51 |It might be a good idea to read about being a good ally or some specific resources for various issues if you’re worried about offending people.
60 | 61 |On IRC: irc.libera.chat in the ##computer channel. IRC is logged by members, who are asked not to publicise their logs.
64 | 65 |@WhyComputer on twitter
66 | 67 |If you want to attend, say hello to someone, and they will drag you along.
68 | 69 |We are making plans on our GitHub repository, and if you have fixes or comments, open an issue!
70 | 71 |Currently inactive UK groups
85 |If you’d like to start a group nearer you, you can fork the GitHub repo and send us a pull request. We have some help and advice for those starting or running a group, which covers finding venues, handling problems, and people who can help with using GitHub.
119 | -------------------------------------------------------------------------------- /index.de.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous 4 | --- 5 |Jetzt verstehst du. Also lass mal zu Computer Anonym gehen.
12 | 13 |Diese Seite existiert auch in den folgenden Sprachen:
14 |Schau unten nach, ob es schon eine Gruppe in deiner Nähe gibt, oder starte selbst eine indem du das Repository forkst, deine Änderungen machst und ein Pull Request stellst.
19 | 20 |Dies könnte eine Gruppe für dich sein, wenn du mit sozial verantwortungsvollen Nerd*innen über interessante Dinge reden willst. Dies ist kein Stammtisch von Unternehmer*innen und kein Netzwerken: Es ist eine Selbsthilfegruppe, ein Platz um gute Leute zu treffen und um über gute und schlechte Dinge zu reden.
29 | 30 |Obwohl uns sowohl das Lernen wie auch freundlicher Kontakt gleich wichtig ist, ist unser Hauptziel eine soziale Gruppe zu erschaffen, in der alle Menschen in und um Technologie und mit allen Hintergründen sich wohl und willkommen fühlen.
31 | 32 |Es gibt keine regelmäßigen Vorträge, Workshops etc. Wir haben keine Tickets, wir haben keine Namensschilder. Wir streben es an möglichst unorganisiert und unformell zu sein. Wir werden viel über Computer reden, aber wir würden auch gerne nicht über Computer reden. Letztendlich wollen wir nur nicht allein sein, wenn wir "Computer" sagen.
33 | 34 |Wenn dein Hintergrund in den geekigsten Treffen nicht so vertreten ist, komm vorbei - wir wollen den Unterschied ausmachen.
37 |Wenn dein Hintergrund in den geekigsten Treffen stark vertreten ist, komm vorbei - wir wollen deine Hilfe um den Unterschied auszumachen.
38 |Wenn du Angst hast nicht Computer genug zu sein, komm vorbei.
39 |Wenn du glaubst ein Blender zu sein, komm vorbei.
40 |Wenn deine Arbeit nicht Code ist, komm vorbei.
41 |Dies ist keine Gruppe von Experten, nur von Menschen.
42 |Wir interessieren uns für soziale und technische Probleme.
43 |Dies ist eine Selbsthilfegruppe. Wir alle wissen nicht, was wir tun.
44 | 45 |48 | Ein Verhaltenskodex gilt, wo auch immer wir Computer reden. Es gilt sowohl online als auch offline wie auch von Angesicht zu Angesicht. 49 |
50 | 51 |Es könnte eine gute Idee sein zuerst darüber zu lesen wie du ein guter Verbündeter sein kannst (englisch), oder über ein paar konkrete Ratschläge (englisch), wenn du Angst hast andere Menschen unabsichtlich zu beleidigen.
60 | 61 |Im IRC Chat: irc.libera.chat 64 |
@WhyComputer Auf Twitter
71 | 72 |Wenn du dabeisein willst, sag einfach "Hallo" zu jemand und sie/er wird dich mitnehmen.
73 | 74 |Wir planen in unserem GitHub Repository, und wenn du Verbesserungen oder Kommentare hast eröffne dort einfach ein Issue!
75 | 76 |Wenn du selbst eine Gruppe in deiner Nähe initieren willst, dann forke das Github Repository, füge deine Gruppe ein und sende uns einen Pull Request. Wir haben etwas Hilfe und Ratschläge für die, die eine Gruppe starten oder betreuen. Themen, wie du Treffpunkte findest und Probleme handhabst, sowie Leute, die dir mit Github helfen können, findest du dort.
118 | -------------------------------------------------------------------------------- /uk_edinburgh.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Edinburgh 4 | --- 5 |Read the overview, if you haven't already.
8 | 9 |You can add your name by doing a fork and pull request on the github page, or by emailing computercomputercomputer at glastonbridge dot co dot uk. The latter method is somewhat unreliable and uses a high-latency meat interface, but it tries hard.
71 | 72 |There is also an edinburgh-specific IRC channel on freenode called ##computer.ed (web IRC interface)
73 | 74 |Computer Anonymous Edinburgh has a Twitter account: @whycomputered 77 | 78 |
We also have an announce mailing list. 79 | 80 |
The Southern was okay, but a bit noisy. I know some people struggled to hear conversations.
85 | 86 |The Royal Dick was found to be a little awkward for people to get to.
87 | 88 |Biblos has served us well for a few months, but it has been suggested that somewhere people feel less pressure to buy drinks might be a good idea.
89 | 90 |The usual suspects for a techy meetup are:
91 |But do we want to go back to the same old places? Perhaps there's somewhere nice down Leith, or in some other part of the town that would be more accessible to people who don't normally go to meet-ups?
104 | 105 |Other venues:
106 | 107 | 108 |Pros:
109 |Cons:
115 |Pros:
122 |Cons:
129 |Pros:
138 |Cons:
145 |Our second meeting at B+B Edinburgh saw the introduction of the formal informal discussion structure, whereby a number of pre-suggested topics were considered for structured discussion. In the end, we settled on bashing PHP for a bit. Cartharsis achieved, a disucssion on the nature of cloud services (defined as utility model pricing of online computing resources) and the popular conception there-of was led by John and all were enlightened.
155 | 156 |This was our first meeting at B+B Edinburgh and was pretty well attended. Everyone seemed pleased with the new venue, especially the view and the lack of noise. There was some discussion of a potential summer outing to somewhere near Edinburgh on the coast.
159 | 160 |These meetings were held at Biblos on 7th January, 10th February and 10th March respectively. 12 people attended in January (with comings and goings over the course of the evening) and 5 people were present in February.
163 | 164 |Due to organiser failure, we didn't meet on the 8th of November, but we will be meeting in November.
178 | 179 |The best date selected was Thursday the 14th. I've asked The Royal Dick to reserve us some space, but if they can't accommodate us we can fall back to the Southern again.
180 | 181 |I'd still like to explore non-traditional venues, but it seems like finding something suitable is nearly impossible. Am I wrong? Let me know!
182 | 183 |The first meeting was really informal and chatty, which is cool, but there's one specific thing I want to bring up to discuss for next time: what do we do in December, where the 8th is on a weekend? Also, I need assistance as I'm not reliable enough to organise things by myself. I'll be asking for a volunteer to help keep Computer Anonymous Edinburgh going.
184 | 185 |Our first meeting was at The Southern on Tuesday the 8th of October, from 7pm.
188 | 189 |19 people attended! It was great, and we had a big red button and some people ate burgers.
190 | 191 |Were you there? I thought it was great, but maybe I'm wrong. If you have any feedback, questions, or concerns at all, please contact me: @semanticist / john@semantici.st.
192 | 193 | -------------------------------------------------------------------------------- /us_seattle.html: -------------------------------------------------------------------------------- 1 | --- 2 | layout: base 3 | title: Computer Anonymous - Seattle 4 | --- 5 |Read the overview if you haven't already.
8 | 9 |//
10 | 11 |//
21 | 22 |Want to set up a computer anonymous event? Follow this handy-dandy guide. 25 | 26 |
//
27 | 28 |
//
163 | 164 |Contact any of the following if you would like to attend, to help organize, or have any feedback!
167 | 168 |