iop-alliance / OpenKnowHow

A metadata specification to enable the collection of distributed, standardised metadata of open source hardware designs
GNU General Public License v3.0
2 stars 1 forks source link

[Feedback][Pre-Val-Workshop] Free Comments #52

Open moedn opened 3 years ago

moedn commented 3 years ago
moedn commented 3 years ago

[FLB-OTC]

Daniel: can i submit a project from my personal web site? (after creating a toml?)

moedn commented 3 years ago

[FLB-OTC]

Mario: other platforms may not bother to implement an API for LOSH

moedn commented 3 years ago

[FLB-OTC]

Daniel: (automatically) notify people when they missed essential fields to fill out (and when it's not open source)

nielek2 commented 3 years ago

is there versioning as fields?

moedn commented 3 years ago

@nielek2 yes there is. I take this as a request for clarification :)

When the version in the version field is changed, this triggers the crawler (it will recognise it as an actual new version of the hardware). Without getting into detail here (seems like I have to clarify it somewhere in written form anyway), there are 3 main reasons for it:

  1. less dependency on specific APIs (such as GitHub; WIF e.g. doesn't have any versioning yet; so does(n't) OSHWA)
  2. hardware developers using git rarely use version tags (#messy-documentation)
  3. we don't want to track 'work in progress' on Wikibase, but rather (stable) releases/versions/snapshots of OSH others can refer to
moedn commented 3 years ago

moedn commented 3 years ago

no extra comments from [Malte-Cluster]

moedn commented 3 years ago

moedn commented 3 years ago

see also feedback from mid-term workshop here

moedn commented 3 years ago

moedn commented 3 years ago

@case06

Entscheidungskriterien für OSH: