Closed
Milestone Apr 4, 2018–Apr 13, 2018

Run an assessment

All of this should be done by clicking around. (No CLI)

  1. Creating an assessment in the mew-concept

  2. List past, current, future assessments

  • Past: completed
  • current: Where am i participating > notifications that assessments have progressed to the next stage
  • future: where am i called to act as assessor
  1. View assessment info (size, status, time, ...)

  2. Interact with assessment:

    • Stake, commit, reveal,...
    • create meeting point
  3. Interact with other participants

    • Proof of assessment role
    • act out an example assessment on gitlab
  4. Proof of credential

See this user-story for a complete list of requirements:

https://docs.google.com/document/d/1NpTvntxw7Mw_5R4geIgh0mgNcalKbE1d2XxGVuCdbSo/edit?ts=5ad9f6f5

(or check out the associated [user-story-issue](

RETRO (dju): I am closing this milestone as part of it has been factored out into https://gitlab.com/fathom/assess/milestones/8

  • what can we do better?

MS have low visibility in our current work flow, and this milestone lying around for two months without anythin happening on it is a testament to that. In the future, we could either link to them in issues more, or maybe have one person clearly assigned who will see a milestone thorugh or sunset it gracefully.

  • Work items 21
  • Merge requests 11
  • Participants 4
  • Labels 6
Loading
Loading
Loading
Loading
85% complete
85%
Start date
Apr 4, 2018
Apr 4
-
Apr 13 2018
Due date
Apr 13, 2018 (Past due)
21
Work items 21
Open: 3 Closed: 18
11
Merge requests 11
Open: 3 Closed: 0 Merged: 8
0
Releases
None
Reference: fathom%"Run an assessment"