GOSH 2022 SESSIONS
*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 # 6 ( Saturday / Sábado, 9:30 am) )
Medical Logistics & Compliance Barriers
Date: 2022-10-29
Time: 09:30
Place: Toucan Room
Facilitator / Notetaker: Amanda Matthes
Participants
- Amanda Matthes
- Rachel Aronoff, Hackuarium
- Jason Whitson
- Martin
Notes:
Introduction Round
– Rachel
Works at Hackuarium, a P1 lab in Switzerland
Has built diagnostics tools including a COVID-19 detection tool (CoronaDetectiveOnePagerUpdate - Google Docs)
Trying to get clinical validation
– Amanda
Personal health enthusiast
Interested in making it easier for individuals to access healthcare quickly
– Jason
Spent 10 years as a medical assistant in the US
Also experience as a nurse
Experienced how difficult it can be for patients on the receiving end of the healthcare system
– Martin
Experienced how different medical systems in Argentina and Mexico
Works in open data/anti corruption
Calculated that massive amounts of money have been wasted on medical resources
Discussion notes
– Rachel: JOGL Fitz tries to help open source projects navigate health care regulations (JOGL Fitz | JOGL)
– Martin: How do we prevent patent trolls? We need patent reforms.
– Jason: The FDA has an enormous backlog. Going through official channels takes many years.
– Martin: Argentina passed a law that automatically approve medications that don’t get processed after a certain amount of time has passed. (https://www.pharmabiz.net/anmat-plazos-by-macri/ and CAFABO – CÁMARA DE FARMACIAS BONAERENSE)
– Jason: Things labelled as supplements can circumvent medication regulations which has resulted in some dangerous medications becoming widely available in the past.
– Amanda: It’s important that regulations exist for medical hardware that could be dangerous. But there are also many cases where making hardware widely available quickly has lots of benefit with very little risk (like diagnostics for common conditions)
– Jason: The biohacking community operates in this space of “do now, ask for forgiveness later”
– Martin: Different countries and communities place different amounts of value on human life. This partially explains why the quality of healthcare is so different in different places.
More links
Mexican procurement law weirdness…
SaDiCo English
SaDiCo Spanish PDF
Regulatory Compliance Requirements for an Open Source Electronic Image Trial Management System - PMC (nih.gov)
RADVAC initiative
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Illegal
Date: Saturday
Time: 9:30 am
Place: Outside
Facilitator / Notetaker: Juul
Participants
- juul
- Mihnea
- Andy
Sci-hub, libgen z-library
Hosting in Romania? Cheap internet
-
Can we make local copies of these? Legality of archiving?
-
Some journals are leaving sections out of their PDF journals to keep them out of sci-hub. E.g. Nature articles with no Methods section.
biomedical piracy -
Four thieves vinegar collective?
reverse engineering and cracking
-
Where is it more or less legal
-
Can we do clean room reverse engineering as a community?
-
Can we make sniffing of communication between computer and lab hardware easier?
** So we can make our own open source software to replace the proprietary software
** Idea: Maybe an embedded device that is plug and play that can log and share traces? -
Legality of cracking. Is it legal in some countries
-
Jailbreaking is illegal for most devices in the U.S. but not in the EU
** Distribution of jailbreaking tools also illegal
** Can we get more DMCA exceptions for e.g. scientific devices? -
Tools
** Ghidra for static analysis (made by NSA)
Censorship / collaboration barriers
- How can we keep collaborating on open projects through access and trade barriers
** E.g. how can we sure we don’t exclude folks behind firewalls / tradewalls
** Getting people funding is problematic (and sometimes illegal) - Censorship and financial/trade barriers:
** E.g. Russia, Ukraine, Iran, Myanmar, China
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Electronics design Workshop - Mario Seeed
Date: 2022-10-29
Time: 9:30
Place: Ñeque
Facilitator: Mario De Los Santos
Participants:
Notes
Designing electronics and good manufacturing practices for makers.
The workshop talked about Eagle Autodesk, an open source platform to design circuits. The workshop had 5 participants that interacted with the software.
Specific points:
- Smart farm monitoring.
- Open source project.
- SeeedStudio develop open-hardware with design availables in the website
- Documentation on electronics.
- How to clear your designs to be understandable for more people
- Clear schematic dividing the main parts of the design.
- Use of commands on the software can make the design easier.
- PCB quote on industrial environments for makers.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Feedback session: Unconference Retrospective
Date: 2022-10-29
Time: 9:30
Place: Outside
Facilitator & Notetaker: Maria Frangos
Participants
- Shannon Dosemagen
- Greg Austic
- Nat Irwin
(and later) - Karl
- Niko
Things we should continue doing…
Hosting social events
Scheduling time for workshops (but more)
Connecting culture with ecology
Providing good food that accommodates individual food tolerance and preference
Onboarding new community members
Supporting those who couldn’t otherwise attend through sponsored / subsidised attendance and travel
Focusing on diversity of participants
Creating programming for locally-focused initiatives and prioritisation
Planning activities to connect as many , as quickly as possible (pre- and during first day of gathering
Translating talks / hiring translating buddies
Prioritising regionally diverse gatherings
Facilitating whole group unconference planning activity to enable participatory topic selection
Providing training for how-to facilitate (but on Day 1 / earlier in the day)
Stakeholder/ organiser perspective:
Strong “system” sessions, e.g. policy, funding
GOSH History, Day 1
Things we should start doing…
Participant perspective :
Being more intentional about the spaces we provide / different rooms for different vibes - e.g. don’t place the rest area next to the beverage and snack area
Planning more workshops
Standard communications channel (half the group was on WhatsApp
Make better use of forum
We can create an Element integration for the forum (or use Signal)
Redesigning workshop sign up form so that participants know what “workshop” means
Proposing ways that session work can continue between global events
Bringing back pre- and post-residencies for global gatherings
Providing better participant bios - e.g. “talk to me about…”
Doing a call for presentations / workshop proposals ahead of time on the forum
Creating a team to put together unconference proceedings
Creating a call for posters
Making sessions longer - 90 minutes
Encouraging participants to capture actions for each session
Stakeholder perspective:
Finalising agenda weeks in advance
Holding a logistics meeting for organising team so we are on the same page about who does what and when
Focusing on the future
Creating plan for outreach (ESRI, UN)
Hosting the public demo in more public, or at least in a more publically accessible space
Using our natural talents more effectively - Match people’s talents to tasks e.g.:
Social Media & Outreach
Communication
Whole Group Facilitation
Holding roadmap session earlier, perhaps as a pre-cursor to unconference planning session
Reconsidering how Working Group for Global Gathering is seated
Engaging academic / research community (consider a different format)
Creating a conference paper track
“Commissions” for long-term, persistent topics
Things we should stop doing…
Stakeholder / organiser perspective
Disregarding what was done before / reinventing the wheel
Changing the agenda on the fly
Dedicated groups:
Social
Logistics
Programming
Block # 7 ( Saturday / Sábado, 11:00 am) )
Private Investment and Incubators
Date: 2022-10-29
Time: 11:00
Place: Coati room
Facilitator / Notetaker: Constantin
Participants
- Andrew Lamb
- Ryan George
- Jenny Molloy
- Number of participants: 4
When raising private investment for Open Source Hardware we encounter a series of challenges that are a bit different from closed source products: understanding the private investor of the Open Source movement and vision, the way how you can provide a Return of Investment if the point is not entirely humanitarian to name a few.
It’s important to understand the product fits with the investor and if necessary to compromise in the middle somehow to make it happen. A good idea is to pitch the product, not the action.
In our collective opinion, there is no open science hardware incubator at the moment although hardware accelerators or incubators exist, they are focused intensively on the protection of the tech stack and return on investment in terms of sales and the protection of the product in terms of competitivity thus making them not a good fit for Open Science hardware.
Such incubators would need both technical and entrepreneurial support from people with experience in these areas in the context of Open Science Hardware.
We foresee two focus points: Design to Product and Product to Scale.
Innovation funds need to be invested both in producing and distributing Open Science hardware locally and remotely if possible.
An interesting skill needed to be developed in this type of incubator would be how to pitch OscH to investors.
GOSH would be a good candidate to kickstart such an Incubator.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Distributed Manufacturing - Next Steps
Date: 2022-10-29
Time: 11:00
Place: Coati
Facilitator: Constantin
Notetaker: Obanda
Participants
- Andrew
- Greg
- Nat
- Ryan
- Amanda
- Number of participants: 7
Notes:
- What success looks like for distributed manufacturing
- Mapping the level of hardware: hard-medium-easy
- easy: soap, buckets: single material, local, no electronics: #groups who can make - high: Case studies - Richard and Julian: search + quality mark would make sense ------>(protolabs, geomake)
- medium: gps logger, stem kits: single pcb, no calibration, lowish skills, <4 materials, <10m assembly time: #groups who can make - some: Case studies: Amanda: Contractual agreement between many parties would make sense e.g uber eats —>( groupgets, seed, kespal, konopo, kitspace)
- hard: open flexure microscope, reflectometer: >30 mins assembly time, calibration required, higher skill, more parts, custom parts, single source components: #groups who can make -few: A cooperative would make sense -------> (coop)
- Mapping the level of hardware: hard-medium-easy
- The “medium” and “easy” levels are already being solved by many groups. We need a co-op.
- Open distribution system where there is a big collective people forwarding things globally
- The co-op would
- Take ideas from developers
- Evaluate the market
- Manage the marketing and business side
- Work with manufacturers to get the project done
- Provide supply chain support
- Issues with shipping:
- Customs
- Supply chain
- Text support
- Point of sale services
- competition
- Skillset and knowledge to solve the technical challenges is required.
- So we look at the manufacturing framework
- Contractual agreement
- Process:
- Developers <> the cooperative <> Support <> Manufacturers <> Market
- Supply chain tool support
- Discovery tool to help one find what they need and what they don’t.
- The MVP includes the core activities of the COOP, and the legal system, and the products.
- onboarding
- catalogue/website
- point of sale
- distribution process is legal
- manufacturing training/system
- Quality mark/QC/QA
- Really good marketing/sales
- Cool Name
- Would likely require $150k - $200k
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Mapping OSH - Lit Review
Date: 2022-10-29
Time: 11:00
Facilitator & Notetaker: Nico
Participants Mapping
- Darin
- George
- Moritz
- Honey Badger
- Juul
- Andy (briefly :P).
Notes:
UC session: OH literature review, projects directories and searchability
This session split into a project “Mapping” session and a “OH literature review” session.
Intros:
– Darin & Nico: same stuff, we have a lot of “modular” high level dependencies, and want to reuse stuff and not make everything from scratch.
– George: go to GitHub/GitLab for specific software. It is frustrating to not know if there is some free project.
– Moritz: personal growth.
– Honey badger: loves hardware.
– Juul:
Related forum posts:
Webpage that lists all GOSH projects - #12 by kaspar
Objectives:
OH search engines and repositories.
List projects: needs, work in progress, finished projects.
Proposals:
– George: Get someone to crawl all websites, and make a list.
We need tags.
– Honey badger: Get an identifier for projects.
– Juul: make a mediawiki, host it on MIRAHEZE perhaps.
Search engines
Broad spectrum:
GitLab/GitHub
YouTube
Reddit forums
Reddit subs
Instructables
Thingiverse/Printables/Yegg/…
Make forums
Closer to OH (no particular order):
OpenNeuroscience: open-neuroscience.com
Open Hardware Observatory (OHO): oho.wiki
Just One Giant Lab (JOGL): Search Projects | JOGL
Open Hardware Repository (OHR): ohwr.org 1
WikiData projects category/node.
Juli’s query: GitHub - thessaly/GOSHMap: A collaborative Open Science Hardware projects map | Un mapa colaborativo de proyectos de hardware científico abierto
Shortlink: https://w.wiki/5ttR
Appropedia: appropedia.org/Category:Projects
OpenKnowHow (OKH): search.openknowhow.org
Kaspar’s “GOSH projects” community members website: projects.openhardware.science 1
GOSH forum has few projects, and doesn’t have a nice enough layout to crawl it.
Hackaday / hackaday.io (blog/information, project)
WikiFactory (HackADay aluternative): wikifactory.com/community/projects
OSWHA certification program list: OSHWA Certified Projects List
OpenHardwareMakers list: openhardware.space/projects
WildLabs.Net (field science)
Hackster.io: hackster.io
WikiFab, Piblitz
Tindie (Etsy for hardware)
Is there a yelp for hardware? A “meta” search engine for hardware. Crowd-source stuff like reviews.
Closer to wetlab OH:
Mailing lists:
DIYbio
OpenWetWare: openwetware.org
Big mediawiki where many labs document their protocols.
Would be great to have something like this for OH.
Hackteria (blog/information): Projects « Hackteria
Metadata standards
What information must we include about a project in a repository.
OpenKnowHow: Open Know-How
Great stuff.
Forum: community.internetofproduction.org
The standard supports “SUB PARTS” but does not define the dependencies “functionally” (not yet, 2022) or interfaces, to support modularity. Would be nice.
Open hardware literature review.
People: Jenny, Shannon, Katie, Luis Felipe.
Objective: gather papers on open hardware and around open hardware.
Notes: next post! Thanks Katie.
Other related suff
allspice.io “A git platform for hardware”
Why not use git? High entry barrier.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
GOSH Community Building
Date: 2023-11-29
Time: 11:00
Place: Outside dining venue
Facilitator and Notetaker: Fernando Daguanno, @alquimetricos
Participants
- Karl Kaddu, Environment for Development
- Gina Leite, Wildlife Conservation Society
- Guillermina Actis, Centro de Investigaciones para la Transformación
- Linda Aidoo, Kumasi Hive
- 5 people
Notes:
Timeline: A brief recall on GOSH 2017-2022 events
GOSH Santiago 2017
TecnoX 2018
Africa OSH Ghana 2018
2019 GOSH Shenzhen
Africa OSH Tanzania 2019
CIACIAR - RICAP - ReGOSH 2021
ReGOSH Mendoza 2022
GOSH Panama 2022
GOSH Camerún 2022
Audience ecosystem: What do GOSH current and potential members clusters look like?
-NGO
-Academia
-Networks
-Highschools
-Government
-Supragovernment institutions
-Individuals
Assessment
-The SH ecosystem is diverse and complex
-To expand and improve the reach of the OH community we need to transmit OSH value proposal in a brief and effective way through by-audience-tailored messages
Solution proposed
-(a collection of) OSH Elevator pitch(s)
-We need an internal tool/procedure to train the GOSH community members to become effective and diverse spokesperson/ambassadors/representatives of the OSH
-Some call them “Message toolbox”
-It may look like a Double-entry table with “audience cluster” in one column and “benefits” in the second one.
Summary: “To develop a bried handbook that we can use to train and help ourselves to communicate what OSH is to different types of audiences. A toolbox to become better OSH ambassadors and infiltrate other events and communities.”
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
ACTIVISM IN OScH
Date: 2022-10-29
Time: 11:00 hs
Place: mesa
Facilitator: Isaac
Notetaker: Lara Jatar
Participants
- Byron
- Isaac
- Tamara
- Lara
Notamos que quienes participamos somos de Latinoamérica, nos preguntamos si tiene algo que ver o algo que nos reúna.
Comenzamos dibujando lo que significa/representa o lo que nos gustaría abordar en relación con el activismo del OScH. Algunas cuestiones que surgieron:
- espacios naturales: respeto
- recuperación de industrias: espacios donde participan grupos que han sido discriminados/segregados.
- cooperativas comunitarias que puedan hacer uso de herramientas
- desarrollo social cooperativo
- desigualdad de
- quien hace el hardware, qué grupo, cómo se conforma
- Visibilizar brechas de la desigualdad de acceso.
- la herramienta libre puede utilizarse para visibilizar los privilegios.
Preguntas que surgen:
- ¿Cómo definimos la calidad de los productos?
Conclusiones:
- hardware abierto ayuda a visibilizar problemáticas: sociales, ambientales!!!
- problema social: contar las voces, quienes hablan, cuanto. Hacer ruido.
- mayor participación de comunidades locales de donde se realizan los encuentros.
- a veces nos debemos incomodar o debemos incomodar.
Links:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Peer review publishing
Date: 2022-10-29
Time: 11:00
Place: Tucan Room
Facilitator: Rachel
Notetaker: Pablo
Participants
- Pablo
- Valeria
- Diego
Notes
Participants introduction:
– Pablo develops OSH for teaching and agroecology. Most of the developments are documented on gitlab. Not published in a paper because of lack of time and cost.
– Diego studies bio-engineering. He has some projects documented (not very well) on github, but most are not.
– Valeria is writing his thesis, and has no documented projects.
Suggestions:
Choose the journal
Read the author guidelines
The reviewer is always right
Negotiate price with the journal
Take a look at the open source compliance
You can put your data in a repo as well
Share pre-prints
Diego asks how to collaborate with other labs. Rachel says most of the time it depends on random chances.
If you finally publish, be carefull with spam inviting you to events to talk about your work.
Links
Journals:
HardwareX
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Communication
Date: 2022-10-29
Time: 11:15
Place: outside
Facilitator: Alison Parker
Notetaker:?
Participants
- Alison
- Marcela
Notes
Collection of post-its - what are our needs?
- OScH 101: for new people. Find their potential
- Definition of “ubiquitous”
- How to continue promoting GOSH to reach an even wider community
- Building bridges (e.g. between academia and the grand public)
- OSH in simple language
- Find a common simple language (words) to speak about OScH
- Comms: how to get some attention in this attention economy
- New metaphors
Storytelling session in Shenzen - collection of slogans
The description of GOSH is not about hardware - it’s about making things differently
the collaborative economy
collaborative economies
decentralized
commons
How is it different? different from the mainstream, capitalism, private property
what are we trying to dispute, push against