Precisions in okh-manifest.yml model needed + Fr template/translation proposal

[Villafruela]

Hi,

In the template of okh-manifest.yml file described in the standard, i think some items should be explained in more details. For instance :

• affiliation should be defined more clearly. What does it represent ? Is it the name of the group, company, non profit group you may be part of or something else ?
• Also the difference between derivative, variant and sub should be defined more clearly to help users dissociate the different cases (if you've made a slight change on a project is it a derivative or a variant ?).
• At the begenning of the file, a comment explaining that if you have several items to specify, you can multiply the entries. For instance if you have several design files, you can add :
• path: [value]
  title: [value] several times, one for each file.

Maybe :

• a difficulty level could be added in the standard parameters in order to know if building the project is easy, medium, hard or very hard
• a skill list required to build the hardware could also help (like 3D printing, soldering, electronics, laser cutting etc.). This would help identify the kind of knowledge needed to build the hardware and what you need to learn to fulffill the construction if you lack one or several skills.

We've translated okh-manifest.yml template in french here We've also made a tutorial in french to explain how to use the OKH standard here. We're also willing to translate the OKH standard in french if you need. Just let us know...

Nemo

[amchagas]

Hi @Villafruela

Thanks for your input, translating the manifest, and creating a post in French to explain it!

Maybe it would be good to plug these translations into the main OpenKnowHow page as well as the form we have for creating manifests? what do others think? @kasbah @dubsnipe @julianstirling @rafaellaantoniou?

[julianstirling]

It is worth asking @pciavald if the manifest creator will generate an updated form based on this file. If I remember correctly it uses the comments to generate the form.

I think the right place for the translations would actually be with the spec, so that it can be kept in sync. We can then serve copies from the web-page. Something that we cannot do while it is in StandardsRepo...

[rafaellaantoniou]

Hi all,

I’m not sure what to add to this. I’ve brought this to the attention of Jérémy so he can add his thoughts.

Kind regards, Rafaella

[pciavald]

Hi,

@Villafruela unfortunately the standard that you've translated is not the latest version, it has been adjusted since the one you've taken as a base. Here's the latest version.

The manifest form is based on this file and we could imagine that the syntax is modified to something like this:

  *title <en:Name of the hardware; fr:Nom du matériel>: string;

[Villafruela]

I've made the modifications (not yet on our site) and proposed them on the repository. I can translate the rest of the assets files if you like, or anything else if you need, let me know. Once the files will be available i'll change our tutorial to match the last version.