Nlnet responsiblities

1

Here are all the points from our nlnet MoU with responsiblity assignments :slight_smile: … either “responsible” or “supporting”, can have multiple people for each… please self assign yourself. It’s a “wiki post” so anyone can edit. MoU is NLnet funding application successful! - #3 by nicksellen

Some reflections on our interests/motivations are here → HedgeDoc - Collaborative markdown notes

1. Improve developer experience

item feel responsible feel supportive
Migrate frontend to Vue3 / Quasar2 @tiltec @nicksellen
Add frontend integration tests and aim for 75% test coverage @nicksellen @tiltec
Reduce abstraction level of frontend data management @nicksellen @tiltec
OPTIONAL Improve developer documentation @nicksellen @tiltec

2. Roles feature

item feel responsible feel supportive
Complete “trust for role” feature @nicksellen @nathalie @bruno @Vasilis_Ntouros
Complete participant types for activities feature @nicksellen @nathalie @bruno @Vasilis_Ntouros
OPTIONAL Writeup process and documentation for roles feature @nathalie @nicksellen

3. Design and develop feature toward ‘breaking the silo’ among groups on Karrot and the wider public outside Karrot

item feel responsible feel supportive
Conduct and publish writeup of design process @bruno @Vasilis_Ntouros
Implement first iteration of feature (to be detirmined in design process) @nicksellen @Vasilis_Ntouros @Vasilis_Ntouros

4. Agreements feature

item feel responsible feel supportive
Writeup process and documentation for agreements feature @nathalie @bruno
Implement MVP of agreements feature @nicksellen @bruno

5. Refining places and activities feature

item feel responsible feel supportive
Refine display of places @bruno @nicksellen @Vasilis_Ntouros @nathalie
Add UI for editing place types @nicksellen @tiltec @bruno
OPTIONAL Streamline UI for creating activities @nicksellen @bruno @Vasilis_Ntouros

6. Improvement of the existing conflict resolution feature

item feel responsible feel supportive
Conduct and publish writeup of design process @bruno @Vasilis_Ntouros @nathalie
Implementation next iteration of conflict resolution feature @nicksellen @tiltec

7. Connect and engage with the communities using Karrot

item feel responsible feel supportive
Conduct and publish writeup into how Karrot is being used @Vasilis_Ntouros @nicksellen @bruno
Document participatory processes (for other projects) @nicksellen @bruno
Guide for participants on how to contribute (for potential contributors) @Vasilis_Ntouros @nicksellen @bruno

8. Facilitate self-hosting of Karrot

item feel responsible feel supportive
Add Karrot to co-op cloud tool @nicksellen @tiltec
Add documentation for self-hosters @nicksellen
2

Based on discussions from our last meetings (full notes here and here) here’s our assessment on how we intend to progress on the tasks above and their feasibility.

  1. Improve developer experience

a) is merged, we can request the money
b) c) and Optional: Nick started looked at this, seems achievable, good idea to talk to Tilmann, support each other

  • we are holding on to this
  • optional ones depend on nlnet also, putting those lower priority
  • get on with one of it now, others can be ongoing, nice independent tasks
  1. Roles feature
  • almost done
    • Nathalie and Nick will have a chat on that topic
  1. Design Breaking the silo
  • design process under way, Bruno proposes that it will be finished by July-August
  • implementation until October seems achievable from Nick’s perspective
  1. Agreements feature
  • writeup will start in 1-2 months, Nathalie and Bruno motivated
  • implementation part? highest chance for outside devs as there already is the prototype
    • maybe break it down to smaller parts
      new devs would still need Nicks help (what he offers)
      → holding on to it, check-in in a few weeks
  1. Refining places and activities feature
  • come up with ideas for design part is doable, but low priority now
  • evaluate in a few months
  1. Improvement of the existing conflict resolution feature

a) is high priority
b) holding on, evaluate in a few months

  • depends on our flow of work, there is potential for a lot of productivity
  1. Connect and engage with the communities using Karrot
  • a and c have high priority and a is under way
  • b is a maybe, needs to be evaluated in a couple of months
  1. Facilitate self-hosting of Karrot
  • self contained tasks, feel good about those
  • we’re doing it!