OKH Adoption WG - 22.8.9

Open Know-How
,
1

Minutes of previous meeting: OKH Adoption WG - 22.7.14 - Open Know-How - Internet of Production Alliance Community
Minutes of next minutes: to be added.

Next worksession: Tuesday September 13th, 4pm UTC

Minutes - 9th of August

Agenda:

  1. Welcome
  2. Review of action points from July 14th
  3. AOB:
    Update on the OKH maintenance WG,
    Discussion: should we focus on use-case analysis?

Attendees:

Emilio Velis - @emilio
Andre M Chagas - @amchagas
Barbara Schack - @BarbaraSchack
Max Wardeh - @max_w
Antonio Anaya - @kny5

Recap of action items:

  • Emilio: speak with fabcity/Tomas Diez on pitch/workshop at Fab17 about mapping fabcity projects and possibly using OKH as a basis for a tool to compare specs.
  • Antonio: speak with fabacademy/Luciano on pitch/workshop at Fab17 about mapping fabacademy projects and possibly using OKH as a basis for a tool for searchability of projects.
  • Emilio & Barbara: explore the “ask a hardware librarian” idea.
  • Barbara: start topic on forum around a set of metrics to experiment with tracking OKH “adoption”
  • All: think about Max’s proposal to “to develop a “use-case analysis” working group to discuss different use case for OKH and “spawn”/assess project groups to work on them”
  • Unclear action item/food for thought: think about how we get more human-centred design into OKH: how do we spend more time and brain power on “how do people search for hardware designs & documentation?” to inform the OKH family of standards and tools.

Meeting notes:

  1. Welcome round + note on secretariat moving forward: minutes to be posted on Community Forum in the OKH category: Open Know-How - Internet of Production Alliance Community

  2. Review of action items and define next steps where relevant.

  • Start conversations (on forum and in a call) about the following ideas:
    Notes from the discussion: for each of the following topics, the discussion focussed on a go/no-go of exploring the ideas further, and agreeing to a lead for each who would explore the topic further outside of the Working Group meeting.
    ** Emilio: “thanks to OKH: take similar devices and compare their specs” post on forum the idea and start conversation
    → Done. Link here: OKH standard Applications
    → Next step: a workstream on mapping fabcity projects. Emilio: speak with Tomas Diez. Then conversation with Antonio on how to move it forward.
    → Resources: FabCare | Envision Workshop 1.1A - Google Slides discussion with fab city.
    **Emilio & Barbara - “ask a hardware librarian”
    → Action item for next meeting: meeting and pitch the idea on the forum
    **Antonio: fabacademy: search-ability of other student projects - port of OKH search
    → Done: post the idea: Propose the OKH standard for the FabAcademy program
    → Next step: Antonio: speak with Luciano and prepare for fab17. Then conversation with Emilio on how to move it forward.
    ** Barbara - Define 3-4 metrics to be discussed by this group.
    → Done - Proposal # of manifests - # design platforms “OKH compatible” whether natively or thanks to some sort of tooling - a community health metric? Like #individuals or groups/orgs participating. Need to define what participating means.
    → Action item: Barbara: post on forum and launch discussion
    ** WIP: Sarah & Max : Dissemination of research findings from DAPSI funded research.
    ** Using google ads to push to where the OKH search/repository. No further action item defined.

  • Previous agenda points we couldn’t cover
    ** Work stream 4. Creating adoption support documents - will be covered in next meeting. Possible update by then from @schutton on work with tools to onboard a makerspace.

  • AOB:
    ** Max: linking with outputs of Maintenance WG & continued discussion:
    → Conversation about the current use of OKH as a tool for discoverability: that it is used to create manifest repositories, rather than as a global “google friendly” search-ability. Or to have a common language (Appropedia).
    ** Lack of human centered design: we talk about discoverability, but where is the look at “how do people search?”. How do they pick between thousands of designs and how can OKH help?
    ** Conversation around use cases: replicability of designs, helpful engineering will work from specific use cases.
    → Paper by Appropedia (unpublished, please don’t share yet!): https://esenedusv-my.sharepoint.com/:w:/g/personal/emilio_velis_esen_edu_sv/Efa53yN_QdlJunCU2y3e6qQBdBHTPdmkTOmiaFFLLwl6vQ?rtime=P-NqvCl62kg
    → Action: Emilio to post on forum about quality and replicability, referencing the work of Appropedia
    → Suggestion to develop a “use-case analysis” working group to discuss different use case for OKH and “spawn”/assess project groups to work on them (this has been the main focus of the last couple of WG meetings). Do we morph this WG into being primarily focused on that, and keep the comms side of adoption also in this WG (e.g creating adoption support documents and guides)? Or do we separate these two streams?
    Action item: think about the above suggestion and discuss in the next meeting

Minutes of previous meeting: OKH Adoption WG - 22.7.14 - Open Know-How - Internet of Production Alliance Community
Minutes of next minutes: to be added.

1 Like