GOSH 2022 SESSIONS Documentation - THURSDAY Block # 1 (Thursday / Jueves, 10:00 am)

Hello everyone!

I am pleased to share with you the Documentation Notes from the GOSH 2022 sessions which compilation would not have been possible without your contribution on the pads created for it: Thank you all very much!

A special Thanks!!! to each of the members of the Documentation Team who have contributed to make this possible: we have collected the documentation of 42 sessions!
If you have not yet uploaded the documentation of the session you facilitated or where you were the note taker, feel free to do so by replying to this thread!

*Note: As the body of each Forum Topic is limited to 32000 characters, the post of the sessions has been split in different Topics according to the Blocks originally defined in the program. This way it is better distributed and easier to manage.


Block # 1 (Thursday / Jueves, 10:00 am)


Software for Hardware

Date: 2022-10-27
Time: 10:00
Facilitator: Clint
Notetaker: Josh


  • Josh x2
  • Clint
  • Nicole
  • Andrew
  • Nicholas
  • Byron
  • Joaquin
  • Nat
  • Survey Stack is a good example of a software that can interact (in principle) with many types of hardware
  • different hardwares require different scripting resources, which is lacking maybe in documentation
  • do we have anything that can interact with ALL types of open hardware?
  • Code that interfaces with hardware (via APIs) versus code that runs on hardware
  • to what extent do we need to account for both when trying to build software platform/ecosystems that can handle any sort of hardware
  • β€œMachine Shops” β†’ if we think in terms of implementation interfaces, standards, and various levels (e.g. transport vs analysis), it might be natural to visualize it as a network
  • Open Manufacturing platform
  • there is a problem with trying to aggregate data (or other output artifacts) that can result from the SAME TYPE OF HARDWARE distributed in many places; but also different types of hardware in the same location
  • Vertically integrated stacks β€” proprietary hardware has traditionally been coupled with proprietary software.
  • it’s very important to be smart about making decisions about where interfaces exist, and not re-inventing the wheel
  • camera trap example: lots of devices distributed over geography, need to aggregate data and analyze in central platform
  • Closed System vs Open System (IoT) Hardware β†’ to what extent are β€œclosed systems” meaningful today (or in 5 years)? Even β€œclosed systems” like a roomba which don’t actively input or output data are still trained on data which has been taken from other environments.
  • even in cases where we want to deal with data ingress, but not necessarily sharing (e.g. a home thermometer that we don’t want to share for privacy reasons), layers of standards are helpful if we want to do comparative analysis (or apply machine learning)
  • What are the layers of interest?
  • Data collection
  • Data transport
  • Data analysis
  • User interface
  • Standards for these already exist, right?
  • We need to distinguish between standards as in β€œhigh standard / low standard” versus standards as in β€œeveryone is using a common format”
  • Exchange formats
  • …
  • Control and management of devices
  • Open data is hard enough to find in the first place, but then without a clear understand of HOW THE DATA WAS COLLECTED there is a much bigger challenge
  • Software Supply Chain (software provenance) e.g. OpenChain Project

OSI model - Wikipedia

Global Emergency Strategies - Lessons from COVID-19

Date: 2022-10-27
Time: 10:00
Place: Tucan room
Facilitator: Amanda Matthes
Notetaker: Amanda Matthes


  • Amanda Matthes (University of Oxford)
  • Gabriel Naor (International School of Panama)
  • Andres Colmenares (Open Climate)
  • Rajas Poorna (Georgia Tech)
  • Lenin Rueda Torres (occupational and environmental health)

Discussion notes: (grouped by topic not chronological)

  • Who are we?
    • Gabriel: Student in school, encouraged to come to GOSH by teacher
    • Amanda: PhD student working on open source hardware for biologists
    • Andres: Strategist
    • Lenin: Technology and medicine, works for the government on topics of occupational health
    • Rajas: PhD student working on diagnostics with Raman spectroscopy
  • How did COVID-19 impact our work?
  • Availability and efficiency testing was difficult in many countries
    • Lenin used open source hardware to test facemasks
    • Rajas: Built cheap PCR during the pandemic and a way for healthcare workers to take blood without air exposure (COVID Kiosk)
  • Geopolitics in an emergency
    • Andres: We need to be able to work across borders
  • Climate change
    • Andres: Climate change is a climate emergency. Not enough action is being taken.
  • Education
    • Andres: COVID-19 shutdowns gave me the opportunity to learn new skills and space to think and do lots of things. But I also know people whose education suffered.


Ensuring Open Hardware is captured in Open Science recommendations

Date: 2022-10-27
Time: 10:00
Place: Outdoors
Facilitator: Jenny
Notetaker: Greg


  • Jenny
  • Alison
  • Katie
  • Shannon
  • Dorn
  • Dario
  • Greg
  • Paula
  • Moritz
  • Gina Leite
  • Guillermina


Initial round of discussion (who, what do they want to achieve)
– Jenny - open science has gotten into a lot of rooms that were inaccessible… and we need to piggyback on that success.
– Alison - is seeing changes in open science and wants hardware to be involved. Wants to do a policy series on this topic after this trip - that’d be an opportunity to implement those.
– Katie - seeing in funding spaces talk about open science (NSF as example). Same idea - how to capitalize for open hardware
– Shannon - +1 to above. Environmental space open hardware is the β€˜stepchild’ of the open science movement. Lots of misunderstandings and blank spots - OScH needs to be part of / central to / understood completely by. 2023 will be the year of Open Science… OScH HAS to have a place in that.
– Dorn - OpenTEAM + GOAT is ag related and should be focused on hardware and software. Wants to look at foundations, private, and others to better understand that full ecosystem. Need to think about the vertical structure, and how do we get it into contracts (hacking the system).
– Greg - +1 I want people to connect - there are experiences, strategies, and stuff we should share.
– Dario - with CZI on the funding side with Open Science program… currently lacks a portfolio focused on OScH. They’ve seen similar problems apply to parts of outputs which they see as critical. Preprints and open access publications… Despite the fact that their impact is massive, they are virtually absent from the standard recommendations. Open source research software is similar.

What strategies worked. What can be generalized to OScH.
– Paola - wants to include these ideas in her thesis work working in Fernan’s lab
– Diego - Works in different projects with universities, wants to ensure more people have access to open science
– Moritz - Wants to further OScH, Berlin University Alliance wants to push OS generally, and that may be an opportunity of OScH
– Gina - (with WCS host or for Cit Sci for Amazon Network) How to institutionalize OS culture within their Amazon Network, and create a culture for innovation?

What are the conversations we need to be in
Prompt: What are the words / arguments one could use to get OScH (Open Science Hardware) into OS (Open Science) conversations?
– (Alison) had a workshop around this a year ago. Here were the arguments that worked.
- DON’T FUND THINGS TWICE - this was an argument that seemed to connect
- NEW WAY OF COLLABORATIVE SCIENCE - this is one key element of a drastically collaborative approach.
– (Shannon) but the problem is we keep having a message that it’s education only… that really limits OScH applications… we need to get people to understand that it’s broader and applies to real actual infrastructure. Luis Fillipe - hardware is critical infrastructure!

– (Dario) (a) should we coordinate messages across a leader and let them run, or (b) should we create general principles that everyone can pick up.
– (Shannon) We need (a)… we need case studies!!! We need narratives and evidence
– (Jenny) We need evidence to point to… case studies also.
– (Moritz) We are assuming that people in power are acting in good faith… Some do, some do not. You can engage
– (Greg) We can’t generalize success because it’s so custom. We need to find those good faith actors (as Moritz said) to unlock how you actually β€˜do’ the process in any given situation
– (Dorn) Here’s a case example
- Inspire - you have to have successful examples (culture)
- Equip - here’s the toolkit you can use (contract language, tooling, design standards)
- Enforce - enforce bad actors or people who get off track (back to non-FOSS) (contractual enforcement)
– (Shannon) Similar examples in EPA and their experiences
- a main problem is the siloing of spaces… and they need a support group for those people who have β€˜drank the cool aid’… how do we get them together to recognize they are not alone.
– (Dorn) it’s important to help people find you, so they can start
– (Moritz) look to Research DAta Alliance
– (Alison) this is all about people! How do we broaden the community! Is there room for new professionals, professional development, fellowship?
– (Katie) can we also ensure that narrative includes not only how things are better/easier/etc. but also DEI.

What rooms are there and are we in it, or can we get in it?

  • US
    • UNESCO - we’re in the room!
    • RDA - we’re in the room!
    • NASA - they are interested
    • HDF (see next steps)
    • USDA -
    • Open Data Act created a cross agency act, and data interoperability is a key, so connecting with that.
    • Waldo - working on state level software contracting strategies.
    • Globe.gov project (NASA, State dept, NSF). Natural fit but definitely could be an ally.
  • Outside US
    • European Commission
    • (Guillermina) Horizon 2022 or other funding schemes. Lines of funding that recognizes bridging of OS projects. And european policy is very influential in South America as well, so there’s a broader impact there.
    • (Moritz) European Parliament (know an MEP)
    • (Guillermina) previous discussions with MEP weren’t very successful, but maybe through Horizon or other things.
    • (Dario) ED of creative commons was an MEP - may be a connection
    • Direct European Govts.
    • France, Netherlands,
    • La/referencia - engaged already in expanding OS, maybe a conversation with OScH could help
    • African Academy of Sciences, influential on the conference
    • Science Foundation of Africa (competing with AAS)…

Wrap up

  • (Katie) involved in climate action conversations
  • (Diego) fellowship programs are a good idea, young professional in latam
  • Meet people where they are… how to reach out?
  • (Moritz) Jobs… Workshops used to create tech in universities (in Germany)… how could we integrate makers into this and focus on Open Hardware. Lack of trust is a problem.
  • (dorn) 1) Hardware and climate is a huge opportunity. 2) Professional Development 3) FAIR and CARE.

ACTION: New Ideas

  • Could we propose training programs, fellowship, etc. (that big orgs like) specifically at the policy or large govt. level.
  • ?? - We need well evidenced case studies! Let’s create them to support additional change.
  • ACTION: Rooms we need to be in
  • Consider joining RDA, work to get FAIR implemented.
  • Pen - to think about how we can connect OScH in NASA…
    • Consider going through HDF Group University of Illinois, they are working with the software and data standards side… could we work with them to engage Open Science Hardware!
  • Dorn - connect with Waldo about how his contractual software success could be applied to the USDA case.
  • Jenny - connect with MEP, how do we get involved in that.
  • Dario - ED of creative commons was an MEP - may be a connection
  • Guillermina - La/Referencia connection
  • ?? - In Africa… what options are possible.
    • African Academy of Sciences, influential on the conference
    • Science Foundation of Africa (competing with AAS)…
  • Gina - Capes organization (brazil)

Talking more about it

  • (everyone interested) Professional Development concept… flesh it out!
    • feel free to make a session on this!
  • (Filipe, everyone) Strategies to reach out to new folks… talk and write up… there’s a session on that!
    • there’s a session, join!
  • (Moritz) Workshops used to create tech in universities (in Germany)… how could we integrate makers into this and focus on Open Hardware.
    • Talk with Josh - he’s creating systems to replace tech transfer, he’d have interesting ideas. Open Software Programs
    • There’s a session on this, people should join!


Collaborating with Small Communities

Date: 2022-10-27
Time: 10:15
Place: Outside the eating area
Facilitator: Marcelina
Notetaker: Johanssen Obanda


  • Brianna
  • Ian
  • Juan Pedro
  • 5 Participants

Collaboration is important in growing the impact and outreach of OSH work.
It is based on equal access, where all the community members who do not have OSH in their hands can access it and collaborate equally.
The community is made up of people with common interests, common challenges, self-organized groups, shared contexts (vulnerability, underserved, small, …)
Examples: JAY4T collaboration with local schools in Kisumu, Kenya Youth engagement: Experiencing fun science experiments with children. - YouTube
Collaboration is not about we vs them, but us together. Good collaboration means fixing things at a local level; community engineering and embracing/integrating traditional knowledge.
Indigous communities have for a long time contributed OSH knowledge throughout their communities. However, socio-cultural protection is needed to preserve local knowledge and OSH practices.
In community collaboration for osh, it is ideal to create an environment for active listening and self-directed science research (community science, and participatory approach).


So crazy it might work!

Date: 2022-10-27
Time: 10:15
Place: Neque room
Facilitator: Ryan
Notetaker: Ryan/Niko Obanda


  • Ryan
  • Niko
  • Ernesto
  • Constantin
  • Amanda
  • Bill Hatcher
  • Shannon Hicks
  • David
  • Jay
  • Genesis
  • Linda
  • Alexandra
  • Rachael

Some ideas were websites with more teardowns of scientific equipment, government sponsored open science hardware, assistive tech for scientist with handicaps, and an open microfluidic cloudlab and marketplace

Shake your body (you nerd)

Date: 2023-11-27
Time: 10:30
Duration: 20 minutes
Place: Outside park
Social media links and hashtags: @alquimetricos
Facilitator: Fernando Daguanno, @alquimetricos

Participants (15 to 17 participants)

  • Rachel Aronoff,
  • Goldjian
  • MartΓ­n Szyszlican,
  • Linda Aidoo,
  • Tiago Lubiana Alves,
  • Alexandra Covor,
  • Isaac NΓΊΓ±ez Quijada,
  • Tamara Matute Torres,
  • Rajas Poorna,
  • Elio Challita,
  • Carolina Borrero Arias,
  • and many more!

Outdoor playful activity. After some physical warm-up, we learned the basis of AlquimΓ©tricos hubs connections and started linking sticks and pentagonal hubs together. After breaking up into groups of 3 members, we built big equilateral triangles. After all of them were already verified we joined all triangles together into a big icosahedral structure, not without some puzzling here and there. All participants went through the collective experience of building a predetermined geodesic structure without knowing it, with bare instructions of the individual pieces’ link (but not the plans for the whole figure).
Then a brief introduction of the AlquimΓ©tricos project mission and vision was presented, and we all shared a photo or two and the joy of being collectively shaked nerds.