Difference between pages "Miniconf Info" and "Clsx takeaways"

From LCA2016 Delegate wiki
(Difference between pages)
Jump to: navigation, search
(Monday 1st Feburary)
 
(clsXlca 2015 Takeaways)
 
Line 1: Line 1:
== Miniconf CFPs ==
 
  
[https://linux.conf.au/programme/miniconfs Miniconf page on linux.conf.au]
 
  
Mini conferences will run on the Monday and Tuesday of LCA 2016. The call for papers for these are handled individually by the organisers of each conference.
+
= clsXlca 2015 Takeaways =
  
Here's a list of the open CFPs, with close dates and links. If you are attending LCA and have a ticket, why not throw in a proposal? [https://linux.conf.au/register/info You can also buy a single miniconf ticket].  
+
We summed up the day by sharing our take aways from the day. Turns out to be a nice summary of the day's discussions.
  
 +
* Post it Thank Yous. See http://instagram.com/p/xz1NAHFGt8/ [[File:B7Qr4w3CEAEBDhX.jpg|right|200px]]
 +
* Support - how do we support our communities?  Doing this stuff is hard. Supporting the work is key.
 +
* Communicate and Collaborate (this was echoed by others too) and soon, and often. Don't keep it to yourself. Share.
 +
* Burnout is  a thing.
 +
* Inspired to get my community going, and will write a blog article sparked by ideas today. Culture!
 +
* Recognition: working towards a recognition culture across, up, down and the tree.
 +
* Types of recognition.  Just ask.
 +
* Surprise! Pleased that these conversations are happening.
 +
* It's possible to generalise the issues.
 +
* Recognition is important. The non-code work is hard to measure.
 +
* We don't have to solve ALL the problems.  Sometimes they solve themselves, sometimes they just stop being problems.
  
=== Open Call for Proposals ===
+
'''Code of conducts are important. We need them now. Stop procrastinating.'''
  
Multimedia - Open - Closes January 18 [http://www.annodex.org/events/lca2016_mmm/index.php/Main/CallForPapers  Multimedia Call for Papers]
+
Understanding what other people are doing validates what we're doing too and shows how and where we can improve.
  
Documentation - Open - Closes ?? [http://lca2016docsminiconf-schwarzgeraet.rhcloud.com/ Documentation Call for Papers]
+
== NOTES ==
  
Kernel - Open - Closes January 20 [https://docs.google.com/forms/d/148SieC6vmAxJZ3R5Lz5e1Mb0IM06LNSCt6WNVEwYFcs/viewform Kernel Call for Papers]
 
  
 +
===Agenda===
  
=== Other Miniconfs ===
+
* Context Appropriate Tone
 +
* Protecting your community - umbrella'ing
 +
* funding, budgeting and fundraising
 +
* community manager therapy
 +
* docs process
 +
* hiring
 +
* metrics
 +
* one off advice
 +
* best and worst practices
 +
* marketing
 +
* breakouts
 +
* sustainable handover and pipeline
 +
* burnout, retention and recrutiment
 +
* diversity - correct vs importance
 +
* management
 +
* problement people and managing them
 +
* creating engagement leadership diversity
 +
* succession planning
 +
* managing conflict
 +
* governance and politics
 +
* lifecycle growth / wind down - detecting mission accomplished
 +
* inductions and introductions
 +
* how to recognise all contributions - how and feel part of the community
 +
* making people feel safe  - and flipside - people who make our communities feel unsafe
 +
* creating a truly *global* community
 +
* interdisciplinary skills - and working across domains
 +
* choosing not to be offended if you have the ability to
  
Open Cloud - Closed
 
  
Functional Programming - Closed
+
===Order of events===
  
SysAdmin - Closed
+
* Introductions
 +
* Agenda from the room
 +
* dot voting on topics
  
Open Radio - Closed
+
==Talks==
  
Open Source and Bio - Closed
+
* Clinton Roy - diversity- and how it affects people's lives, and the difference it can make
  
Open Knowledge - Closed
+
* SUz - diversity within the fab lab - think about poeple who have been excluded on the basis of difference - who have been excluded from the school system. Peopole who are unemployable - people need time and patience to help them become useful.
  
Open Hardware - No CFP
+
* Tridge - project leaders as umbrellas. Came about linuxcare auslabs joined IBM, Hugh Blemings was the manager withi the group - part of his job was to act as an umbrella - to protect the geeks. In some communities, discussing all this stuff up front is good, but in others this can be a barrier because they don't want to have to think about all the peripheral stuff - they just want to code and send packets. A lot of communities the project leader bears the brunt of this stuff - ie leader as an umbrella.
  
Community Leadership - No CFP
+
* Victoria - human being - until I was welcomed into the group I was an outsider, and Donna welcomed me. This is all about welcoming and introduction. How do you know what to do? Do people want to be welcomed? You have to ask your community. What is the right welcome for your commuity? They will know how to raise issues, they will feel safe, because it is part of the welcoming practice. You need to tell people how to get involved. Talk to your people - find a way to speak to them individually.
  
=== Miniconf Schedules ===
+
** Donna additional: code of conduct, this is where it is, EULA - this is where the rules of engagement are.
  
 +
* Darrell - changing funding paradigms. How groups maintain funding. In AU now, small groups are being defunded because they are seen as not effective. But the small groups are effective - but you're not seen as effective if you don't make a profit - so there is a pressure to make a profit. As one example Lifeline is now spending their time running a book fair, and selling solar energy and coffee so that they can be sustainable financially. The issue is though that the people who call Lifeline now are put on hold, because Lifeline cannot take all their calls - because they are busy selling books and coffee. Is this the right way for non-profits to work? We have non-profits because we've found that some services are best run by non-profits because those services are not seen as valuable by government, which is validated by conversations by politicians. Services are increasingly user-pays - particularly for social servies, and this is where AUstralia's social services are headed. This is a call to action to revers ethe trend.
  
==== Monday 1st Feburary ====
+
* Joshua Hesketh - succession planning is very important for the strength and helath of the organisation. Josh is tryin to encourage the pipline for Linux Aus council. If you'r einvolvedin the community, how do you want to be involved in the future of the community. Part of this picture ismentoring - ie having someone come in at a junior level and mentoring them up. If you're burning all your members out, maybe you *should* shut down.
  
 +
* Adam - learnings from dealing with problem behaviours at MakeHakeVoid. Paassive aggression was our first step, and it was a mistake. Then, engagement turned to the mailing list. Engagement with the problem behavoiur using the medium they were using for the problem behaiour didn't work either. Instead, a safe space was created for a converation, and a trusted friend was present, and the conversation directly addressed the problem behaivours. Unfortunately the mailing behaviours moved into the person to person space. His behavioru contributed to the burnout of others, so we tried to address it. We tried to established new rules and behaviours. We found we were stacking rules upon rules and it was unsustainable. We realised that the community that he wanted wasn't the comunity we wanted. The person needed structure and predictability, whereas the Hackerspace needed more flexibility. This was met with threatening behaviour from the person, and legal action. The next stage was a thrid party mediator. The parties wanted different things from the mediation process and was less than successful. Finally an email was sent where the person was excluded from attended. The lesson is that sometimes excluding someone *is* the right decision. Unfortunately the person is also on another local group in the area and I'm now in conversations with the leader of the other group about the person's behaviour.
  
{| class="wikitable"
+
** Mark: Are you aware of [http://www.plausiblydeniable.com/opinion/gsf.html geek social fallacies] document?
| align="center" style="background:#f0f0f0;"|''''''
+
| align="center" style="background:#f0f0f0;"|'''Costa Hall'''
+
| align="center" style="background:#f0f0f0;"|'''D2.211'''
+
| align="center" style="background:#f0f0f0;"|'''D2.193 Percy Baxter'''
+
| align="center" style="background:#f0f0f0;"|'''D2.212'''
+
| align="center" style="background:#f0f0f0;"|'''D4.303 Costa Theatre'''
+
| align="center" style="background:#f0f0f0;"|'''Wool Museum'''
+
|-
+
| ||[http://sites.rcbops.com/opencloud_symposium/ Open Cloud Symposium]||Open Hardware Miniconf||[http://www.annodex.org/events/lca2016_mmm/ Multimedia and Music Miniconf]||Documentation Miniconference||[http://afrubin.github.io/miniconf/ Open Source and Bioinformatics]||Linux Kernel
+
|-
+
| 9:00||Conference Opening||Conference Opening||Conference Opening||Conference Opening||Conference Opening||Conference Opening
+
|-
+
| 10:00||morning tea||||||||||
+
|-
+
| 10:40||Continuous Delivery using blue-green deployments and immutable infrastructure by Ruben Rubio Rey||||10:40 - An Open Approach to Whole-House Audio (Bdale Garbee)||||10:40 - Miniconf Welcome
+
 
+
10:50 - TBA (Bernie Pope)
+
 
+
11:20 - TBA (Harriet Dashnow)
+
 
+
11:50 - TBA (Adrian Hecker)
+
||
+
|-
+
| 11:35||Network Virtualization 101 by Sandro Mathys||||11:35 - GStreamer in the living room and in outer space (Sebastian Dröge)
+
 
+
11:55 - Free Software in the Audiokinetic Laboratory (Tobias Brodel)
+
||||||
+
|-
+
| 12:20||lunch||||||||||
+
|-
+
| 13:20||The Twelve-Factor Container by Casey West||||13:20 - Qtractor and Project Management (Klaatu)||||13:20 - Message from the ABACBS President (Tony Papenfuss)
+
 
+
13:30 - TBA (David Powell)
+
 
+
14:00 - Production Pathology: from spinning wheels to knitting mills (Ken Doig)
+
 
+
14:30 - R and Bioconductor: open source software for analysing genomic data (Belinda Phipson)
+
||
+
|-
+
| 14:15||Assorted Security Topics in Open Cloud by Jason Cohen||||14:15 - Real Time Tuning Analysis (Jan Schmidt)
+
 
+
14:40 - Why no FOSS on stage right? (Hugh Blemings)
+
||||||
+
|-
+
| 15:00||afternoon tea||||||||||
+
|-
+
| 15:40||TBA||||15:40 - Conference Recording 2.0: Building a Better System (Joel Addison)||||15:40 - Applied bioinformatics using open source software (Lavinia Gordon)
+
 
+
16:10 - TBA (Simon Gladman, Yousef Kowsar, and Andrew Isaac)
+
 
+
16:50 - TBA (Torsten Seemann)
+
||
+
|-
+
| 16:35||Live Migration of Linux Containers by Tycho Andersen||||16:35 - Informal jam/demo session
+
* ALDA: A Music Programming Language for Musicians (Jim Cheetham) [20 minutes]
+
* Others TBA
+
 
+
17:10 - Lightning talks
+
||||||
+
|-
+
| 17:20||||||||||||
+
|-
+
| 18:00||Linux Australia AGM||||||||||
+
|}
+
 
+
==== Tuesday 2nd Feburary ====
+
 
+
 
+
{|class="wikitable"
+
| align="center" style="background:#f0f0f0;"|''''''
+
| align="center" style="background:#f0f0f0;"|'''Costa Hall'''
+
| align="center" style="background:#f0f0f0;"|'''D4.303 Costa Theatre'''
+
| align="center" style="background:#f0f0f0;"|'''D2.193 Percy Baxter'''
+
| align="center" style="background:#f0f0f0;"|'''D2.211'''
+
| align="center" style="background:#f0f0f0;"|'''Wool Museum'''
+
|-
+
| ||[http://sysadmin.miniconf.org/programme16.html Systems Administration Miniconf]||OpenRadio Miniconf||Open Knowledge||Community Leadership Summit X at LCA||[http://bfpg.github.io/fp-miniconf/ Functional Programming Miniconf]
+
|-
+
| 9:00||KeyNote ||KeyNote||KeyNote||KeyNote||KeyNote
+
|-
+
| 10:00||morning tea|||||||||
+
|-
+
| 10:40|| 10:40 Is that a data-center in your pocket? by Steven Ellis
+
 
+
11:10 Samba Status update by Andrew Bartlett
+
 
+
11:25 5 Minute break
+
 
+
11:30 A Gentle Introduction to Ceph by Tim Serong
+
 
+
11:50 Keeping Pinterest Running by Joe Gordon
+
 
+
|
+
10:40 Miniconf Open
+
 
+
10:50 A live demo of the CubicSDR open source SDR software, Paul Warren
+
 
+
11:15 All Your Modem are Belong To Us, David Rowe
+
 
+
11:40 Project Horus - high altitude balloon payloads, Mark Jessop
+
 
+
12:00 Lightning talks
+
 
+
|| 
+
10:40 Miniconf open
+
 
+
11:05 OpenTechSchool - open learning in practice by Lillian Ryan
+
 
+
11:30 Open Data + Video Games = Win by Paris Buttfield-Addison
+
 
+
|| (CLSx runs no schedule) || 10:40 Miniconf open
+
11:00 The Essential Tools of Open-Source: Functional Programming, Parametricity, Types by Tony Morris
+
 
+
11:40 Functional programming in Python with Toolz and fn.py by Juan Nunez-Iglesias
+
|-
+
| 12:20||lunch|||||||| 
+
|-
+
| 13:30|| 
+
 
+
13:20 Site Reliability Engineering at Dropbox by Tammy Butow
+
 
+
13:45 'Can you hear me now?' Networking for containers by Jay Coles
+
 
+
14:05 5 Minute break
+
 
+
14:10 Network Performance Tuning by Jamie Bainbridge
+
 
+
14:30 Real hardware: you get to keep the pieces, but they're pretty awesome pieces by Rob N
+
 
+
14:45 Pingbeat: y'know, for pings! by Joshua Rich
+
 
+
|
+
13:30 Tutorial - Embedded sensor data with Lora radio modules, Andrew McDonnell
+
 
+
14:10 Using the OpenRadio as RF test equipment, Kim VK5FJ
+
 
+
14:40 Panel/Discussion
+
 
+
|| 13:20 Open information: Documenting data and methods by Rhydwyn
+
 
+
13:45 Prying Open Government - An Introduction to Freedom of Information by Dan Hawke
+
 
+
14:10 Internet Archive: Universal Access. Open APIs by VM Brasseur
+
||(CLSx runs no schedule)|| 13:20 Data made out of functions by Ken Scambler
+
13:55 The Emperor’s New Closure: FP in Javascript by Nick Moore
+
 
+
14:30 Practical Functional Architecture by Jed Wesley-Smith
+
|-
+
| 15:00||afternoon tea||||||||
+
|-
+
| 15:40||
+
15:40 The life of a sysadmin in a research environment by Eric Burgueo
+
 
+
16:00 TSAR (the TimeSeries AggregatoR) - How to Count Tens of Billions of Daily Events in Real Time Using Open Source Technologies by Anirudh Todi
+
 
+
16:20 5 Minute break
+
 
+
16:25 Creating bespoke logging systems and dashboards with Grafana, in fifteen minutes by Andrew McDonnell
+
 
+
16:35 Ergonomics of Automation by Jamie Wilkinson
+
 
+
16:50 Order in the chaos: or lessons learnt on planning in operations by Peter Hall
+
 
+
17:05 Sysadmins: present, past and future by  Javier Turegano
+
|
+
 
+
Mini field day; hands on demo, radio orienteering and more
+
 
+
|| 15:40 Prospects and pitfalls in open demography by Fred Michna
+
 
+
16:30 TBA
+
||(CLSx runs no schedule)|| 15:40 Swift Functional Programming by Paris Buttfield-Addison
+
16:15 Haskell is Not For Production and Other Tales by Katie Miller
+
 
+
17:05 LIGHTNING TALKS and miniconf close
+
|-
+
| 17:20||||||||||
+
|-
+
| 18:00||Professional Delegates Networking Session||||||||
+
|}
+
 
+
{{Template:Navigation}}
+

Revision as of 18:56, 23 January 2016


clsXlca 2015 Takeaways

We summed up the day by sharing our take aways from the day. Turns out to be a nice summary of the day's discussions.

  • Post it Thank Yous. See http://instagram.com/p/xz1NAHFGt8/
    B7Qr4w3CEAEBDhX.jpg
  • Support - how do we support our communities? Doing this stuff is hard. Supporting the work is key.
  • Communicate and Collaborate (this was echoed by others too) and soon, and often. Don't keep it to yourself. Share.
  • Burnout is a thing.
  • Inspired to get my community going, and will write a blog article sparked by ideas today. Culture!
  • Recognition: working towards a recognition culture across, up, down and the tree.
  • Types of recognition. Just ask.
  • Surprise! Pleased that these conversations are happening.
  • It's possible to generalise the issues.
  • Recognition is important. The non-code work is hard to measure.
  • We don't have to solve ALL the problems. Sometimes they solve themselves, sometimes they just stop being problems.

Code of conducts are important. We need them now. Stop procrastinating.

Understanding what other people are doing validates what we're doing too and shows how and where we can improve.

NOTES

Agenda

  • Context Appropriate Tone
  • Protecting your community - umbrella'ing
  • funding, budgeting and fundraising
  • community manager therapy
  • docs process
  • hiring
  • metrics
  • one off advice
  • best and worst practices
  • marketing
  • breakouts
  • sustainable handover and pipeline
  • burnout, retention and recrutiment
  • diversity - correct vs importance
  • management
  • problement people and managing them
  • creating engagement leadership diversity
  • succession planning
  • managing conflict
  • governance and politics
  • lifecycle growth / wind down - detecting mission accomplished
  • inductions and introductions
  • how to recognise all contributions - how and feel part of the community
  • making people feel safe - and flipside - people who make our communities feel unsafe
  • creating a truly *global* community
  • interdisciplinary skills - and working across domains
  • choosing not to be offended if you have the ability to


Order of events

  • Introductions
  • Agenda from the room
  • dot voting on topics

Talks

  • Clinton Roy - diversity- and how it affects people's lives, and the difference it can make
  • SUz - diversity within the fab lab - think about poeple who have been excluded on the basis of difference - who have been excluded from the school system. Peopole who are unemployable - people need time and patience to help them become useful.
  • Tridge - project leaders as umbrellas. Came about linuxcare auslabs joined IBM, Hugh Blemings was the manager withi the group - part of his job was to act as an umbrella - to protect the geeks. In some communities, discussing all this stuff up front is good, but in others this can be a barrier because they don't want to have to think about all the peripheral stuff - they just want to code and send packets. A lot of communities the project leader bears the brunt of this stuff - ie leader as an umbrella.
  • Victoria - human being - until I was welcomed into the group I was an outsider, and Donna welcomed me. This is all about welcoming and introduction. How do you know what to do? Do people want to be welcomed? You have to ask your community. What is the right welcome for your commuity? They will know how to raise issues, they will feel safe, because it is part of the welcoming practice. You need to tell people how to get involved. Talk to your people - find a way to speak to them individually.
    • Donna additional: code of conduct, this is where it is, EULA - this is where the rules of engagement are.
  • Darrell - changing funding paradigms. How groups maintain funding. In AU now, small groups are being defunded because they are seen as not effective. But the small groups are effective - but you're not seen as effective if you don't make a profit - so there is a pressure to make a profit. As one example Lifeline is now spending their time running a book fair, and selling solar energy and coffee so that they can be sustainable financially. The issue is though that the people who call Lifeline now are put on hold, because Lifeline cannot take all their calls - because they are busy selling books and coffee. Is this the right way for non-profits to work? We have non-profits because we've found that some services are best run by non-profits because those services are not seen as valuable by government, which is validated by conversations by politicians. Services are increasingly user-pays - particularly for social servies, and this is where AUstralia's social services are headed. This is a call to action to revers ethe trend.
  • Joshua Hesketh - succession planning is very important for the strength and helath of the organisation. Josh is tryin to encourage the pipline for Linux Aus council. If you'r einvolvedin the community, how do you want to be involved in the future of the community. Part of this picture ismentoring - ie having someone come in at a junior level and mentoring them up. If you're burning all your members out, maybe you *should* shut down.
  • Adam - learnings from dealing with problem behaviours at MakeHakeVoid. Paassive aggression was our first step, and it was a mistake. Then, engagement turned to the mailing list. Engagement with the problem behavoiur using the medium they were using for the problem behaiour didn't work either. Instead, a safe space was created for a converation, and a trusted friend was present, and the conversation directly addressed the problem behaivours. Unfortunately the mailing behaviours moved into the person to person space. His behavioru contributed to the burnout of others, so we tried to address it. We tried to established new rules and behaviours. We found we were stacking rules upon rules and it was unsustainable. We realised that the community that he wanted wasn't the comunity we wanted. The person needed structure and predictability, whereas the Hackerspace needed more flexibility. This was met with threatening behaviour from the person, and legal action. The next stage was a thrid party mediator. The parties wanted different things from the mediation process and was less than successful. Finally an email was sent where the person was excluded from attended. The lesson is that sometimes excluding someone *is* the right decision. Unfortunately the person is also on another local group in the area and I'm now in conversations with the leader of the other group about the person's behaviour.