Index: trunk/doc/devlog/20170213_edacore2.html =================================================================== --- trunk/doc/devlog/20170213_edacore2.html (revision 6900) +++ trunk/doc/devlog/20170213_edacore2.html (revision 6901) @@ -19,7 +19,7 @@ our formats and tools to let people easily set up their own services
  • such separately ran and maintained repositories would have different goals and policies; we shall accept that and be happy about that; we - should distribute file formats and tools, not policies and ideologoies. + should distribute file formats and tools, not policies and ideologies.

    How my favorite service would look like

    @@ -41,7 +41,7 @@
  • tags are free form key=value pairs, both key and value are simple strings
  • let tagging conventions emerge
  • let the these conventions be specified and maintained by the user community -
  • do not split the repositry on a per uploader basis - that's the least useful infromation for an end user +
  • do not split the repository on a per uploader basis - that's the least useful information for an end user
  • maybe implement a separate namespace for "signed" tags; e.g. some registered user would validate a few footprints and would tag them "went on copper and looked good"; if it's a signed tag, end users have the chance to validate the source of the tag and other contributors can not change or overwrite this tag
  • content licensing: @@ -51,7 +51,7 @@
  • optionally have a separate distribution and use license
  • first support footprints and symbols because we have converters for - those; gradually extend to 3d models, FEM, spice, schematics, pcbs + those; gradually extend to 3d models, FEM, spice, schematics, PCBs as common formats and/or converters emerge.