Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • OSEGeV Conformity Assessment Body OSEGeV Conformity Assessment Body
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OSE Germany e.V.
  • Projekte
  • CAB
  • OSEGeV Conformity Assessment BodyOSEGeV Conformity Assessment Body
  • Issues
  • #70

Closed
Open
Created Jan 10, 2022 by Nils Weiher@nilesOwner

Assessment level (DIY/Industry)

Here is some valuable insight to the idea of diverging prerequisites regarding the documentation:

Hello Nils, Lukas, how are you?

I still have to work on some little missing items in my documentation. I´ll keep you updated on that.

Anyway, I wanted to share a thought that came to me following last week's online meeting. In reality, it's pretty much the same stuff I've been saying about my needs before, except better, I think.

At the meeting you commented on an idea regarding the specs to be specified in 2 different levels: "DIY" or "industry". And that is closely related to what I´ve been dealing with on my project since the beginning. In my case, I want my documentation to be used by the industry, but it is not as detailed as it should be. Because of my lack of some technical specific knowledge, it looks more like DIY...

So my thought is that it would be fantastic if manufacturers could take a DIY project documentation (not just my case, but any DIY level project) and upgrade it to industry standard. As a result, the company becomes a contributor/documenter/backer/co-author to that project. That option, I feel, might be a significant component of the OSH DIN standards program and should be actively pushed. Even as an invitation to the entire business to participate in and contribute to the Open Source Movement, not simply as users but as developers/contributors.

As a result, the documentation improves because it is redacted by people who are well-versed in the field particular for each project. Furthermore, Open Source initiatives would reach the industry and, eventually, more end users.

That's what I've been looking for with my project. I am certain that my innovations have the potential to benefit a large number of people and companies, but I have yet to reach them... And I'm guessing I'm not the only one in this situation.

I hope you get my point, and that you find it relevant. Thanks again for your support!

Happy New Year!

@isabbioni

We are definitely going to discuss this in the future!

Assignee
Assign to
Time tracking