07.16.2020

Agenda

Activities

• Research:

  • Mies, et al. (2019) - good background info on OSH and but has more focus on how traditional for-profit companies can benefit from OSH. This makes me think about how much about IP and the traditional business model (e.g. manufacturing, operations, business, and consumption) are "disrupted" because of OSHI should be included in lit review.
  • did you know that Tesla stated that they would "not initiate patent lawsuits against anyone who, in good faith, wants to use our technology." (Musk, 2014)

• interesting related projects. Added to contacts

  • Prakash Lab, Stanford University makes OSH for frugal science and global health. Created reusable PPE mask out of scuba gear
  • Feed the Future: Innovation Lab for Horticulture at UC Davis. Technology projects centered around agricultural technologies that "overcome common limitations in land, labor, capital and infrastructure."
  • Similar to the Cuba idea:An Alternative to the American way of Innovation | Andrew 'bunnie' Huang | TEDxPickeringStreet (video) -- "can technology be shared as virally as media?" ; "it's better to produce a copy, than to never produce at all"
  • Shenzhen Innovation Tour 2017, a mini-docuseries about factory and electronic makers in Shenzhen, China
  • Bonvoison is pronouced as: Bo-n-vu-uh-son (lik song)

• to watch:

  • Open Source is Insufficient to Solve Trust Problems in Hardware
  • Shenzhen: The Silicon Valley of Hardware (Full Documentary)
  • Open Source is Insufficient to Solve Trust Problems in Hardware: How Betrusted Aims to Close the Hardware TOCTOU Gap

• to read:

  • Best practices of open source mechanical hardware - Bonvoisin, et al. (2017). Also available on github

• emailed N.Peek about OSHWA survey data access/comparison/collabo. Connected me to Michael Weinberg and Alicia Gibb. Next steps?

• Literature Review: Relevant or not?

  • the availability and impact of 3D dekstop printers (e.g. Lulzbot Taz, RepRap, and Ultimaker)
  • Thingiverse does offer documentation and licenses on their website. Where do we draw the line on what not to include?
  • its economic impact - it is the opposite from traditional business logice with IP protection and copyright. Integrating OSH development into business/company processes, and the differences between OSH and non-OSH relationships (e.g. customer, maker, consumer, contributor, etc.). In Mies (2019), they differentiate between co-designing vs. open source product development (OSPD).
  • drafting Background/Intro Lit review outline

• Research Q Ideas:

  • disincentive to make a project OSH, but actually "openwashing". Looking at the barriers to documentation, transparency, and accessibility. Bonvoisin (2017) notes that accessibility takes a lot of investment and documentation is time-consuming. Can we make a template/guide to streamline this process?
  • Compare documentation and community of OSH commercial companies to OSH projects (those without formal institutionalized formation). E.g. OpenSci R has budget dedicated to documentation. Creating roles specifically for technical writers, community builders, like Wikimedia, Mozilla, GitHub, GitLab, but what are the OSH companies/organizations?
  • Study on how communities become active and inactive. Looking at the failed attempts to community buildings vs. successful community building. Parallels to the community types, e.g. religion, dance, food, politics, etc. How have the OSH complex assets lead to the community thriving or dying?