valueflows

valueflows docs
git clone https://s.sonu.ch/~srfsh/valueflows.git
Log | Files | Refs | README

2016-05-29-minutes.txt (2091B)


      1 *Agenda:
      2 
      3 * Workflow - elf Pavlik
      4  * actionable tasks vs. open discussions
      5  * milestones, monthly releases and versioning (v0.1, v0.2 ... v0.45)
      6  * bi-weekly meetings and agendas
      7 * Selfdogfood - elf Pavlik
      8  * VF ontology as knowledge resource
      9  * meetings as processes
     10  * iterations (between versioned releases) as processes
     11    * gh issues on release milestone as inputs
     12  * all contributions as received services
     13    * self-assigning to actionable task (gh issue) as commitment
     14 * Prototypes vs. Types — elf Pavlik
     15  * example: model descriptions on https://www.nitrokey.com/#block-block-6
     16  * example: https://shop.fairphone.com/fairphone/fairphone-2-tp.html#specifications
     17  * querying - we should create dataset from our snippets and query it with http://client.linkeddatafragments.org/
     18    * see also: http://ruben.verborgh.org/blog/2015/06/09/federated-sparql-queries-in-your-browser/
     19 
     20 
     21 elf
     22 Lynn
     23 Bob
     24 3 participants
     25 
     26 topics: 
     27 workflow
     28 closing issues
     29 bob will get more into the details of the current discussions this coming week
     30 .
     31 what to focus on next:
     32 process from recipe, then look for what needed to produce
     33 .
     34 entry points for focusing:
     35 1. planning the process
     36 2. isolate some issues
     37 (if we can)
     38 3. evolution of the intent
     39 (Pavlik needs inputs to his planned process)
     40 (this will include conversations for action but not in any detail)
     41 (but we can just note and park little issues there instead of getting distracted by them_)
     42 (black box for now)
     43 --path of just finding willing people to support wiht inputs
     44 .
     45 think about our workflow in light of vf
     46 as we work
     47 --lead to selfdogfood
     48 In other words, document our workflow using the VF vocab
     49 .
     50 our process: agreements documented by merging PRs
     51 .
     52 release cycle of monthly releases
     53 --will motivate to agree
     54 --publish to the w3c community group
     55 .
     56 .
     57 .
     58 Pavlik wants to explore prototypes
     59 Bob wants to contracts classes, type objects and prototypes as ways to model resource types and their relationships with resources.
     60 .
     61 .
     62 some time soon try to write some queries (when we have enough snippets to combine)
     63 Pavlik will take the lead on this.