Liebe Leute,
in der OSEG-Community wurde gestern eine Initiative gestartet, einen Code of Conduct und einen Code of Content festzuschreiben – das betrifft vornehmlich die Moderation unserer Telegram-Gruppen, ist aber nicht darauf beschränkt. Der eine regelt unseren zwischenmenschlichen Umgang, der andere unseren Umgang mit Inhalten. Nach vielerlei Eskalationen über die Jahre, besteht jetzt wieder ein aktueller Anlass, das abschließend zu klären. Die Möglichkeit würde ich gern wahrnehmen.

Wer sich daran beteiligen möchte &/ bereits Material dafür hat, ist herzlichst willkommen. Wer gerade nicht die Zeit dafür findet, kann sich selbstredend später (ggf. nach dem ersten Entwurf) mit Feedback einbringen. Kritische Verhandlungspunkte (sollte es welche geben) werden in einem Plenum entschieden – da gibt's dann auch nochmal 'ne Möglichkeit, mitzuwirken.

Ich habe zur Entwurfserstellung eine organisatorische Gruppe und einen Prozess erstellt. In der Gruppe wird NICHT diskutiert; sie dient allein organisatorischer Absprachen (sonst fliegt uns die Kiste ggf. ergebnislos direkt um die Ohren; Telegram ist auch herrlich unübersichtlich bei solchen Debatten)

Ohne Euren Hirnschmalz wird das nix: Seid herzlichst eingeladen, diese Regelwerke zu gestalten :)

To join, just follow the white rabbit 🐇 :)

https://t.me/joinchat/mvAkj0CqLS80YTk6

interessantes paper -> "Why makers make what they make: motivations to contribute to open source hardware development" -> https://onlinelibrary.wiley.com/doi/epdf/10.1111/radm.12348

Großartig, einmal Open-Source-Hardware auf dem c't-Cover und es hagelt Resonanz:
Doppelte Abrufzahlen des Wikipedia-Artikels und hier ein Blog-Beitrag der deutschen Commons-Community:
https://keimform.de/2021/open-source-hardware-update/

Die Erstellung guter offener Dokumentationen ist zwar arbeitsintensiv, jedoch essentiell für die Entwicklung eines Open-Source-Hardware-Projekts sowie den Aufbau einer Community. Der Community-Review-Prozess nach DIN Spec 3105 ist zwar aufwendig aber auch lohnenswert für OSH Projekte.

Wir haben großartige Neuigkeiten für die Open Source Hardware Community
https://blog.opensourceecology.de/de/2022/01/community-review-eine-neue-methode-fuer-zuverlaessig-dokumentierte-open-source-hardware/

Fallen euch Open-Source-Hardware-Projekte ein, die Interesse an einem Community Review hätten?

Kennt Ihr ein Projekt, das unbedingt mal nachgebaut werden soll?

Du willst selbst aktiv werden und Projekte dabei unterstützen, bessere Dokumentationen zu liefern? Dann melde dich als Reviewer*in!

#CommunityReview #CommunityReviewProcess #OSH #Documentation #OpenSourceHardware

https://blog.opensourceecology.de/de/2022/01/community-review-eine-neue-methode-fuer-zuverlaessig-dokumentierte-open-source-hardware/

Gerne über unsere Kanäle liken, teilen, verlinken:

Twitter https://twitter.com/OSEGermany
Mastodon https://mastodontech.de/@OSEGermany
LinkedIn https://www.linkedin.com/company/osegev
Instagram https://instagram.com/OSEGermany
Facebook https://fb.com/OSEGermany
Telegram https://t.me/OSEGermany

Die Grundlagen von Open-Source-Hardware für Universitäten und Bildungseinrichtungen in gut 5 Minuten!

Original-Titel: "Open Hardware für Technologietransfer und Impact", Lightning-Talk beim University Future Festival 2021 vom Hochschulforum Digitalisierung und der Stiftung Innovation in der Hochschullehre.

https://youtu.be/H-u1GcYhn2g

Prototype Fund Hardware: Jurymitglieder vorschlagen

Kam eben per Mail rein:

Liebe Runde,

ein wenig Zeit ist vergangen, seit dem wir uns zum Workshop im Dezember gesehen haben. Seit dem ist viel passiert. Wir haben das Rahmenkonzept des Funds entwickelt, Kriterien für die Auswahl der Projekte aufgestellt, eine Galerie von guten Beispielen gebaut und die Plattform veröffentlicht. Nun sind alle wesentlichen Fragen geklärt und wir können mit dem Aufbau der Jury beginnen.

Wie versprochen kommen wir dazu noch mal auf euch zu. Wir würden uns sehr freuen, wenn wir unsere Expertise zusammennehmen, um geeignete Jurymitglieder zu finden. Das Ziel ist eine bunte Runde, mit Fachkenntnis und Wertekompass. Mehr dazu sowie ein Formular, über das ihr (anonym) Personen vorschlagen könnt, findet ihr in diesem Blogartikel: https://hardware.prototypefund.de/jurymitglieder-gesucht/

Wenn ihr Frage oder Anmerlkungen habt, dann meldet euch gerne. Ich hoffe, dass es bald wieder eine Gelegenheit gibt, sich zu sprechen!

Liebe Grüße /

🎉🎉 OSH Legal Issues Workhop 🎉🎉

Workshop Series Addressing Common Legal Pitfalls in Open Source Hardware

tl;dr: Bucerius Law School and FabCity Hamburg host a series of workshops for legal issues (and how to resolve or avoid them) for actors in the field of open source hardware, starting on March 25th; this is backed by the EU-H2020 project OPEN!NEXT so we can offer it for free & for anyone → to register, just let Sidsel (Danish Design Center) and me know via mail:

To: Sidsel Kjøller Damkjær <sidsel@maker-effekt.dk>
CC: Martin Häuer <martin.haeuer@ipk.fraunhofer.de>

We'll forward all further information to you. If you have concrete legal concerns already, please let us know, too :)

agenda for the 1st session: (Friday, March 25, 2022; 2 p.m. - 6 p.m.)

1. Free and open innovation: The idea behind OSH (short Introduction)
2. The legal material: What rights are we dealing with?
3. Rights management: Licensing of OSH
4. Defending OSH: Freedom to operate & avoiding infringement
5. Discussion on progress of the workshop

Each part (2-5) will be designed to take approximately 1 hour (short break and questions included).

long:

In early 2019 around 25 OSH-related organizations from around the globe sat together and collected pressing legal issues in the domain of open source hardware (OSH). Open Source Ecology Germany e.V. (OSEGeV) [1] founded a small working group which was eventually able to answer all (!) collected questions in collaboration with one of the largest legal firms worldwide. The results are being summarized in human-readable form in the "OSH Guideline | Legal Issues" [2] (the current release v0.3.1 mostly covers IPR; the liability chapter is yet to be written). That's also on which my tl;dr guide for licensing [3] some of you may know, is based on.
So instead of having hundreds of European OSH projects seeking legal advice on the same issues, they wanted to condense the current knowledge about common legal issues among OSH projects in one single document – one guide to support them all :)

Now, once the main authors of that guideline (Fabian & Felix) heard about OPEN!NEXT, we could convince them to hold a series of dedicated workshops for our practical issues 🎉🎉🎉
The sessions will be officially supported by Bucerius Law School [4] and FabCity Hamburg [5] ✨

We'll have a series of 3 workshops (half day each) starting at the end of March, each dedicated to practical cases from your side. After participating in that series, you may be able to legally support other OSH projects yourself :)

To take this awesome offer, the only thing you'll need to do is:

- accepting the calendar invite @Sidsel will send around\
(optional but highly recommended) state your questions or cases here: https://gitlab.com/OSEGermany/osh-guideline-legal-issues/-/issues/new
- you'll need a GitLab account; in case this option doesn't work for you, you can also send your questions &/ cases to me by mail and I'll add them to the repository
- please use the label "Question" and the Milestone "Workshops" when creating the issues
- being open, being active; the sessions are meant to be tailored to your specific needs → consequently, we rely on active participation (now already, when submitting the issues) from each of you in order to make it useful for you :)

Each session will be recorded and the recording shared for everyone. Your questions and practical cases will be clustered before a session in order to answer them efficiently. AND they will flow back into the guideline as (anonymized) practical cases in order to support other projects with similar questions and issues.

Ok then, let the games begin, looking forward to e-meet you in the workshops! :)

---
- [1] https://ose-germany.de/
- [2] https://gitlab.com/OSEGermany/osh-guideline-legal-issues
- [3] https://github.com/OPEN-NEXT/tldr-ipr/releases/download/v1.0.0/tldr-IPR.pdf
- [4] https://www.law-school.de/international/
- [5] https://www.fabcity.hamburg/en/

…muss leider verlegt werden, da die Workshopleiter heute erkrankt sind (COVID). Als Alternativ-Termin steht gerade der 22.4. im Raum, wird aber noch final bestätigt. Verzeiht die sehr kurzfristige Absage, aber das scheint gerade übrall so'n bisschen so zu sein

Schon ein paar Tage alt, gilt aber immer noch :) ↓

ab heute können projekte beim prototype fund hardware eingereicht werden - schöne feiertag (: https://hardware.prototypefund.de/bewerbung/

🎉🎉 OSH Legal Issues Workhop | April 29th @14h CEST🎉🎉
(now for real)

Workshop Series Addressing Common Legal Pitfalls in Open Source Hardware

tl;dr: Bucerius Law School and FabCity Hamburg host a series of workshops for legal issues (and how to resolve or avoid them) for actors in the field of open source hardware, starting on April 29th; this is backed by the EU-H2020 project OPEN!NEXT so we can offer it for free & for anyone

Register HERE: https://mobilize.berlin/events/d60059e5-6020-4f16-be61-2d7ab578a18c

We'll forward all further information to you. If you have concrete legal concerns already, please let us know, too :)

agenda for the 1st session: (Friday, April 29, 2022; 2 p.m. - 6 p.m.)

1. Free and open innovation: The idea behind OSH (short Introduction)
2. The legal material: What rights are we dealing with?
3. Rights management: Licensing of OSH
4. Defending OSH: Freedom to operate & avoiding infringement
5. Discussion on progress of the workshop

Each part (2-5) will be designed to take approximately 1 hour (short break and questions included).

long:

In early 2019 around 25 OSH-related organizations from around the globe sat together and collected pressing legal issues in the domain of open source hardware (OSH). Open Source Ecology Germany e.V. (OSEGeV) [1] founded a small working group which was eventually able to answer all (!) collected questions in collaboration with one of the largest legal firms worldwide. The results are being summarized in human-readable form in the "OSH Guideline | Legal Issues" [2] (the current release v0.3.1 mostly covers IPR; the liability chapter is yet to be written). That's also on which my tl;dr guide for licensing [3] some of you may know, is based on.
So instead of having hundreds of European OSH projects seeking legal advice on the same issues, they wanted to condense the current knowledge about common legal issues among OSH projects in one single document – one guide to support them all :)

Now, once the main authors of that guideline (Fabian & Felix) heard about OPEN!NEXT, we could convince them to hold a series of dedicated workshops for our practical issues 🎉🎉🎉
The sessions will be officially supported by Bucerius Law School [4] and FabCity Hamburg [5] ✨

We'll have a series of 3 workshops (half day each) starting at the end of March, each dedicated to practical cases from your side. After participating in that series, you may be able to legally support other OSH projects yourself :)

Each session will be recorded and the recording shared for everyone. Your questions and practical cases will be clustered before a session in order to answer them efficiently. AND they will flow back into the guideline as (anonymized) practical cases in order to support other projects with similar questions and issues.

Ok then, let the games begin, looking forward to e-meet you in the workshops! :)

---
- [1] https://ose-germany.de/
- [2] https://gitlab.com/OSEGermany/osh-guideline-legal-issues
- [3] https://github.com/OPEN-NEXT/tldr-ipr/releases/download/v1.0.0/tldr-IPR.pdf
- [4] https://www.law-school.de/international/
- [5] https://www.fabcity.hamburg/en/

🧬 GOSH is "hiring" :) 🧬

↓

In order to learn about, support, and grow Open Science Hardware (OScH) and the OScH community, the Gathering for Open Science Hardware (GOSH) is providing support packages for up to four virtual OScH research and policy workshops. The support package we are providing includes:

Professional facilitation support
Note-taking and report drafting
Graphic design and layout for the final product.
Administrative and communications support
Small stipends of $100 for participants that require financial support.

This call supports meetings, writing workshops, or other collaborations to scope research topics, conduct literature reviews, and develop further policy advice aimed at defined audiences. The outcomes should advance recommendations made in a) the 2021 GOSH Policy Briefs aimed at funders, academic technology transfer offices, and international policymakers; or b) the Global Open Science Hardware Roadmap.

The deadline to apply for support is midnight US Eastern Time on 8 May 2022. Click here to find out more and apply!

We are also looking for reviewers for the GOSH Research and Policy Workshop Programme Working Group! We invite subject matter experts to join the working group to support us in reviewing proposals for this call. If you are interested in joining the working group, please send an email to board@openhardware.science.

Die neue Runde Open Hardware Makers startet 🎉
https://curriculum.openhardware.space/

✨✨✨ OSEG dreams now open ✨✨✨

OSEGeV steht kurz vor'm 6. Geburtstag und es wird Zeit, ein bisschen zu träumen und diese Träume wahr zu machen.
Wir haben Menschen, wir haben Geld und wir haben jede Menge Ideen → jetzt geht es darum, die 3 Komponenten zusammenzuführen :)

- Das Prozedere ist hier beschrieben: https://md.opensourceecology.de/s/68yJ2WMNX

- Telegram-Gruppe für's Voting und die Realisierung der Dreams: https://t.me/+xq0eWw8jlT03ZDcy

- Hier kommen alle Dreams rein: https://md.opensourceecology.de/jI9gVv6rSqaBTG3Bq7D9sA?both

📅 12.06. ist Dream Freeze! Ab da beginnt das Voting und die Abstimmung zur Realisierung. Wir haben also knapp 2 Wochen zum Träumen & Aufschreiben :)

Na denn 'nen schönen Montag Euch allen! Wir sehen uns im Pad 😘

Deutsch: (English version down below)

Im Rahmen meiner Masterarbeit entwickle ich eine Wissensdatenbank und Suchmaschine für Open Source Hardware (OSH) 📖🛠. Zur Einbeziehung der Community und Endbenutzer in die Entwicklung möchte ich mehrere Interviews/Befragungen durchführen. Die gewonnenen Erkenntnisse sollen bei der Ermittlung von Anforderungen und bei der späteren Validierung helfen. Daher suche ich Teilnehmer, die sich beruflich oder in ihrer Freizeit mit dem Thema Hardware beschäftigen. Wenn du interessiert bist, an einem solchen 📋🗣 Interview teilzunehmen, dann komme gerne auf mich zu 😃

✉️ Mail: andre.lehmann@posteo.de
💬 Telegram: @Aisbergg

Vielen Dank!


--------------------------------------------------------------------------------


English:

As part of my master thesis I am developing a knowledge base and search engine for Open Source Hardware (OSH) 📖🛠. To include the community and end users in the development process I like to run multiple interviews/surveys. The knowledge gained should help in the identification of requirements and in the later validation. Therefore, I am looking for participants that are working with hardware in some ways professionally or in their free time (Makers/Designers). If you are interested to partake in such an 📋🗣 interview, then please contact me 😃

✉️ Mail: andre.lehmann@posteo.de
💬 Telegram: @Aisbergg

Thank you very much!

Good afternoon open source hardware avant-garde!

tl;dr: OPEN_NEXT needs input to 1) validate released ICT tools and 2) scope further developments of the same (all tools are of course open source) by June 26

long ↓

In the past 2 years we've developed a a variety of IT tools in the EU-H2020-funded project OPEN!NEXT to support design reuse of already published OSH. After all it's now time to validate to what extent these tools are practically useful for actors in the field of OSH. The goal of this is to identify 1) the core value these tools have for you and 2) blind spots or features we still need to work on.
In other words: Your feedback will set the foundation for further development to be carried out and new projects proposals to be submitted.
Of course the source codes of all tools are published under a free/open license.

For the following tools we're currently looking for feedback:

- Wikifactory (the platform is not open source, but the tool below is)
Wikifactory is an online platform aiming to provide a dedicated development environment for open source product development.
The University of Bath created a tool that provides users with valuable metadata on OSH projects (e.g. file types in the repository or history of open/closed issues). This is now being implemented on the Wikifactory platform but is also applicable to other platforms such as GitHub.
Please respond to this short survey to help them help you! → https://ec.europa.eu/eusurvey/runner/WIF-improvements
- The Library of Open Source Hardware (LOSH)
LOSH is a distributed knowledge base for OSH designs and features a meta search engine for OSH. Concept and underlying metadata specification are based on efforts of the Open-KnowHow initiative. The mission: If there's an OSH design published on the internet, you should find it on LOSH.
find the survey here: https://ec.europa.eu/eusurvey/runner/LOSHval1
André from OSEGeV is dedicating his master thesis to LOSH and carrying out major development efforts. To include the community and end users in the development process he's currently running multiple interviews & surveys – and he's looking for participants that are working with hardware in some ways professionally or in their free time (Makers/Designers). If you are interested to take in such an interview, then please contact him :)
✉️ Mail: andre.lehmann@posteo.de
💬 Telegram: @Aisbergg
- OSH repository checker
This is a command-line tool to quickly run checks on OSH repositories (e.g. "is the project using an hardware-specific open source license?" or "does the project use open source file formats for electronic files?". Think of it as an OSH repository linting tool
find a full list of current checks here: https://gitlab.com/OSEGermany/osh-tool/-/tree/master/src/checks
There's no survey for this tool; if you find this useful, please go ahead, test it and file bug reports and feature requests on GitLab (using issues) → looking forward to follow up on them :)
https://gitlab.com/OSEGermany/osh-tool/

This is it; as said input from the OSH community would be super valuable, so we can make sure that the final releases are actually useful for many people.
Since we'd still need time to evaluate the results and wrap-up the final report, we'd need your input by June 26 🙏

Also, if you need more info or want to get in touch with the developers and researchers behind these tools directly → don't hesitate, I'll get you connected

THANKS; looking forward to your input :)
-Martin