owned this note
owned this note
Linked with GitHub
# Where does ii come from ?
Mr. Rogers and the North American network of local Public Broadcast Stations is the inspiration for ii.nz and this presentation from eight years ago ties much of our NZ focus, but is really only a starting point for the conversation as we explore what this could look like in a Maori context.
- First, I trust that you will read this, it took me 20 years to find buried in the US Library of Congress, but it’ll should only take about ten minutes to read. It’s a philosophical statement from Fred Rogers and his thoughts on the continued funding of Public Television.
- **I hope to have a similar philisophical statement at some point**
- Second, I’d Iike you to watch the video and read the transcript of Fred Rogers as he spoke to Congress in the summer of 1969, trying to save funding meant for public television that was being redirected to the Vietnam War.
- **I hope we are having similar conversations with Parliament in the not-to-distant future to advocate for a Ministry of ii or something similar.**
- In this presentation from 8 years ago, I give away a laptop to anyone who will pay-it-forward, in a similar concept I like to call viral-generosity.
- **(The recipient was one of our speakers from IBM Friday)**
- After coming to NZ I worked with a Indigo Phillips, a local Maori web developer, in the past to explore some Maori concepts and how they might apply to technology.
- **Indie flew with me to China to give her pepeha and speak about whakapapa (and granted me permission to use the concept in tech)**
# Careers Expo
There’s much more, but I think those should cover most of the major concepts and ideas that ii is based on.
The site that was running on the screens (open on a computer): https://careers-expo.ii.nz/monitor.html
(Use a phone to open QR code to select presentations and drive the slides)
The source code for this is at https://github.com/ii/expo-prezzo
Here was our agenda for the two days: https://hackmd.io/BxgSYey_RE246yJC6GIPBQ
TODO: I think the Friday recordings are on a hard drive I’ll look into Tuesday…
# Friday First Session
## (None the people on this call are technical)
I help create and manage strategic initiatives for the CNCF.io, specifically I advise [@pritianka](https://twitter.com/pritianka) who is the GM of the CNCF. She happened to show up unexpected on the first call Friday morning just as a haka was playing and with a waharoa in the background. It was lovely to hear publicly from her all that ii does for the CNCF and how much we mean to her.
She then introduced [@breakawaybilly](https://twitter.com/breakawaybilly) (a CNCF employee focused on Students in Southern Hemisphere) who offered free training, certifications, and conference passes to NZ students.
Bill then introduced [@birthmarkbart](https://twitter.com/birthmarkbart) who learned Arabic in order to move to Spain to work with Refugees…. Bart writes rap songs as part of his contributions to the cloud.
# Friday Second Session
## (deeply technical, but still people focused)
[@jjasghar](https://twitter.com/jjasghar) is the audience member that took me up on the offer of the free MacBook Air on stage eight years ago, and later ended up as a Developer Advocate at IBM…
His email is email@example.com.
JJ also got to recount this memory of this talk and receiving that free laptop live during our talk Friday.
# Friday Third Session
[@eddiezane](https://twitter.com/eddiezane) came in from Amazon.
He’s very keen to see how he can help us with our initiatives.
He helps coordinate donations of infrastructure (AWS Cloud credits) from Amazon to the CNCF.
# Saturday First, Second, and Third Sessions
## It’s one big cloud party
Raw Zoom recording (it’s long):
- The woman with the inclusive beard is [@alisondowdney](https://twitter.com/alisondowdney) who is a Waikato CS Alum.
- [@spiffxp](https://twitter.com/spiffxp) is an old friend of mine who works at Google
- @mauilion created the Apple PIE (Platform Infrastructure Engineering)
- #SIG-Beard is a (Special Interest Group) focused on breaking the stereotypes of long bearded programmer types. When we meet in person, some of us hand out fake beards.
By far the highlight of this session was when Alison got to explain the first steps of contribution to a curious student…
Alison is the Co-Chair of the Contributor Experience for Kubernetes….
She’s responsible for what it looks like to start as a student, start contributing, and the upward ladder into leadership for the entire project... and she’s a local who now lives in London.
# Saturday Fourth Session
## encouraging neurodivergent nonbinary
Raw Zoom recording:
[@kiran_oliver](https://twitter.com/kiran_oliver) was super encouraging, lived in Auckland for a long time, got into the cloud while here and is now a Developer Advocate in the US.
They are so encouraging and I go into quite a bit of detail on how we plan for students to get an ii keyboard, and ii phone, and ideas on what to do with it in the longer term here in New Zealand and globally.
# beyond ii
## Tia STEM Wana (Feedback from Saturday's family day only)
### What worked
- Sofa seating area, allowed visitors to relax/chill while still visually connected with our stand
- We had the right amount of activities and hands on engagement (5-10 minutes in length)
- We had the right level of crew support (each activity required support)
- Giving away 'prizes' after visitors completed a task or challenge meant that it was engaging and memorable
- Brightly displayed and visually interesting stand attracted attention
- SV randomly driving the hexapod beyond our space was a great way to engage with people as they walked around and it brought smiles to people's faces
### What didn't work
- We didn't have a clear CTA (call to action)
- Our brand messaging was unclear (STEM Wana vs. STEMFest vs. Tinkd)
- No printed collateral with our details for people to take away
### What was surprising
- Visitors on saturday comprised families with younger children (our target audience). Not many teens
- Older visitors (grandparents) showed lots of interest in Tinkd (and asked about how we were funded)
- It was worth us attending and supporting the event, as a team building exercise and also as a public engagement exercise
- Based on the number of families who attended, it was a good indictation of interest we could expect for STEMFest
- We need to have our physical space allocation checked and confirmed earlier to better plan the space - better comms with the organisers
### Things that worked
- People seemed to understand what to do with the displays
- The presentation of the stand invited questions and invoked conversation
- The video calls with people in Open Source, creating conversation remotely and then locally
### Things that didn't work
- I find the event intense enough, so it's hard trying to bring up new things or change how things are
- The pipeline of getting connected and further steps should be clear. It seems as though we are there to connect them to an open path that they might be interested in and not for them to study at some institude. The path doesn't seem as obvious as something like studying at Toi or Waikato Uni(s)
- Break schedule / cycles; Rostering needed
- Standing for too long
### For next time
- Cards to hand out with more information (like business cards)
- Calls might be good in a booth or something
- Run infra for event in a more stable local environment
- Have shirts and stickers closer and more readily available
- Some kinda fun practical way to display open public collaboration
- Alternative way to control the slides / displays (not keyboard or mouse)
- Scan QR code from web browser. E.g go to c.ii.nz and point phone at display
- Less set up would for sure be better, so there less to move
- If a focus is the set up in front of them, display more about how it works to inspire
- Do something with the tab that they might leave in their browser after the event, like suggest a redirect to find out more after they walk away from the stand if they leave the tab open
- Some sort of interactive, probably not coding, way of showing pairing together
- Connect STEM Wana with the 3D printing and Open software
- Common knowlege share / responses
### Continous outreach
- Connect with our exhibitor neighbours
- Reach out to the tech teacher from Girls College, who was given an iikeyboard
- Reach out to my final tech teacher from Otumoetai College
- Plan and advertise the local meet ups for Thursday nights
- Ministry of Education ?
- ii.nz posts
- mailing list ?
What I hear everyone saying is that we need to
- slim down on the set
- enough to engage about concepts, and create shared understanding
- clarify the content for direction
- with shared understanding, content must direct to next steps (e.g meet ups, training, open days)
- connect better with individuals based on who they are
- that being for students, finding out the things they're interested as an entrypoint or gate
- that being for educators and institutes, equiping them with the free resource for preparing students for being the generation of cloud-natives in NZ
- shared ii explainations of concepts
- have an easy to grasp interactive local demonstration of cloud, the betterness of openess, pairing / open collaboration (rube-goldbergian)
### Objectives / Audience
- Primary goal was to expose late(?) teens to OpenSource technologies and careers
- Secondary goal was to expose educators and facilitators to same
- Audience was primarily senior high school students on Friday and families on Saturday
### Things that worked
- The more "accessible" systems drew people who asked questions
- the camera on the leftmost area and the games on the rightmost
- Chris' vid calls drew attention and interest
- Some questions were asked about the Raspberry Pis
- The stickers and the t-shirts were popular
- Trying to explain "low-level" technologies in relatable language to the target audience was very difficult
- Explaining the black-magic that went into setting up the QR code system and presentation control was very very hard
### For next time
- Demoing opensource tech based on a minimal understanding of what the audience already knows (web design in this case?)
- Have varying levels of *interactable* technology displayed in a consistent way - for example start with the gaming emulator on one end, move to a simple intranet messaging tool (Zach's idea?), and then have "lesser-known" technologies (Kubernetes?) at the other end.
- A poster etc of some of the career paths available as well as pay scales (audience is primarily students looking at career choices right?) and how to get there
- A display to demonstrate the massive importance that OSS has in driving most technologies we use today.
- Found the initial conversations hard to connect an individual with "open source" without understanding their interests/motivations/context first.
- Starting the conversation with "what's you're interest/passion/current career plans" gave me the context to decide what "open source technogoloy" would be the best for me to discuss with them.
### Better Messages
- Break down the needs of open source to highlight the needs outside of just the "code" bits, i.e. documentation, training, user support and project logistics. Lot of ideas from K8s community here to use as examples.
- Had a discussion with the CS student from Waikato University about a "collaboration project" that could link the CS students with students in the "Māori and Indigenous Studies".
- Find an open source project that has a direct benefits to the local communtity and work on enabling native Māori translation for the software.
- The outcome would help the CS students see how that they can have an impact on users and the Māori students would gain technology that helps them futher embrace their cultural needs and focus for the local iwis.
### Next Time
- Have a set of screens for taking some the software for a "Test Drive". Need to make sure the computer is suitiable for the demonstration.
- Locate more sucess stories of people using open source to create value for their clients and communities (local and/or online).
- There is an architectural firm in Brazil that's pushing their client work to GitHub which is mostly done with FreeCAD
- Create educational packs that help students/teachers know what "options" are available and where to get "started". Use infographics that create a clear story around a "real need" and what could/has been a possible "open solution" for the listed problem.
- cool discoveries:
- how much we wanna do broadcasting
- the skill at coordinating talks and people
- our live teamwork
- the joy of the random small project
- reception by the career expo folks (they liked us!)
- For our booth,ourselves: we always need to give more context
- Going from "what is open source" to "kubernetes" is a big leap
- Hard to cleanly say what it is we are there for, compared to other booths
- we aren't a school or a company or even an industry necessarily
- were almost anti-career path("there is no set path, just start contributing
- not against this point of view, tbh.
- with any work we do, we should define our key demographic and make sure to speak to them.
- Next booth should have more interactivity:
- this booth felt a bit hermetic, a wall between them and us
- open source is about exploration and modification, let's show that directly.
- encourage exploring and breaking things
- higher trust, less security
- focus on quick reaction, not continual preparation.
- a tangible cloud:
- a set of services that exist only on our wifi
- let them put their own websites up, put their chat up
- multiplayer programs hosted only on the pi's.
- celebrate the ephemeral nature of it all...graffiti walls, message boards,
- video streaming to other tvs
- a bit of intentional chaos
- saturday was my favourite day
- fuller conversations
- easier to engage and show
- I think we loved our presentation service more than the kids did.
- They did not think to scan, and when they did scan they wanted something
- could see the anti-climax when they realized it was just a different
- it was super fun to make, though. Like having these hackathons for services
we can then use...felt different than our standard work, and had some of the
most enriching/illuminating pairing while making this.
- I think ii hackathons over a limited set of days could be good.
- We would benefit from big-picture product/project planning
- to continually return to "who is this for, what are their needs, what are
- some of the biggest work we did was for things that never came up. It was
good to have, but interesting to think of how to be small and iterate
based on domain and target peeps.
- Definite desire/place for ii events.
- always asked "where are we based" or "where to find us" and they meant
- what would ii events look like? what would ii.nz look like if we are trying
to reach the career-expo audience?
- I am curious on our next step:
- continuation of the ii keyboard contest
- continuation of broadcasting/event. a fully online conference/programming could be good.
- more intro to open source, what does that look like?
- does it have to be kubernetes based? what does it look like to have
something that will _lead_ to kubernetes, but not _start_ with kubernetes?
- the students/teachers we connected to the best were learning HTML/CSS and
basic python. What does it look like to come to where they are, but bring ii
- kids were drawn to the broadcasting part, cos they all wanna be streamers.
What does an open source, cloud-native video game streaming look like?
- in general, i think biggest strength of open source infrastructure, and learning technical skills, is to be able to support your community's technical autonomy. That is the non-commercial aspect of this work that is important, and we could practice this/teach on this a lot more.
## Things that worked
- Zoom calls was a great way to get people out side NZ envolve
- Location of the Zoom camera was prefect.
## Things that did not work
- Dedicated host for Zoom host that lead and interview particiapants in converstion with a clear start and end times.
(Most callers was unsure of when it would be polite to leave)
- Being able to mute the on site mic. Was very difficult for speakers to talk over incoming local mic
- More stable, less vaunerable infra would reduce stress
- Let's cut the cutting edge stuff a little earlier into shape
## For next time
- Lots of short Zoom interviews.
- A Zoom camera looking towards the ii stand, so all the Zoomers can get a better feel for what is going inside our stand.
- A simple way to collect the contact information of the people of interist identieified by the ii staff at the show
- A community outreach person to help get in the other presentations form the community. (Teach then what is Git / a pull request / Reveal.JS etc. - It is not as obvious as it seem, and would be a barrier to entry for less tech people)
- Real running versions of day-to-day open software on "normal computers". (Blender, FreeCAD, Open Office etc.) - Show entry level end user use cases
- Plan swag and give-aways earlier for less delivery stress
- Student road map > "Start here, do this"
## Thoughts and suggestions
Make the HackMD document public.
I can't comment on what worked or the difficulties encountered at the expo but we can look at everything collectively and learn from there.
I am happy to help out where I can with any planning, executing or anything else for future events.
It might be an idea to share hippie's intro and content with Jay for the ii marketing and storytelling concept?
Reflections from an "non technical" participant observer YMMV
Person to Person interactions
* Watch for OVERLOAD "Linux is everything for Everyone at any time" is a bit overwhelming if someone doesnt have key concepts already
- Importance of questions to establish contacts knowledge base before going into any kind of explanation ( unless to a group)
- The questions to the new contact should also provide you with a unique map of what they might need/be able to contribute
Things To Develop
*Lots of practicing conversation Pathways
> Collective service to society?
>Meeting Sustainability Goals?
>Reducing Costs to Zero
>Shaping contributing to resiliance, self determination , rangatiratanga etc
> Privacy and Security
Bite size concepts and content and explanations
- Sticky Ideas - dont have to be entirely accurate statements " Kubernetes is Inception for your computer"
- Elevator/elevated pitches ( can you describe the concepts in a few sentences using no technical language)
- Be careful not to use these types of tools with experts as it obviously will be less effective (importance of establishing conversations)
Digital converstions with Maori and indigenous peoples
- There are many similar concepts in Te Ao Maori and Open Source , however they are also quite different systems of knowledge so they should not be conflated
- Future conversations with Tangata whenua about how Te Ao Maori concepts could be translated respectfully into the digital world - also who is leading and participating in that conversation is crucial- find a Tuakana ( mentor, big brother) from Mana Whenua to start this conversation
- Team knowledge and competence of Tikanga Maori learnt in a marae setting will be a gamechanger for the organisation as well as the relationship to Maori
- Relationships are key
- Questions to answer How does coding work within a Maori environment ? i.e. wananga,noho and marae spaces (experience needed as well as conceptual exchange).
- Future possibilities: high level conceptual frameworks of complex interelationships are available in Te Ao Maori, models of whanau, ecosystem, mauri , maramataka, cosmology, concepts of Mauri etc Tangata whenua, University of Waikato shared conversation to explore frameworks.
The screen presentation at event
- needed a bit more variety
- the game demos were a bit glitchy - if the playability was better could be more convincing advertisement ( up and running is not the same as good user experience)
possible things on screen in future events
-Interactive Distros: ubuntu Studio, pop OS, Garuda
-Demo of pine 64 screen casting and running distro an keyboard
-Demos of Dual booting multiple virtual machines running i.e a windows and MAC running within another OS ( visual)
- interactve terminals with worksheets with some basic commands ie pwd ls etc
- Explore Programming development on android/mobile devices
- dual boot mobiles?