summaryrefslogtreecommitdiff
path: root/blog/2019/02/26/planning_meeting_iteration_32.mdwn
blob: ac1ce606853e10394de1b21bada21ad1352d35d2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
[[!meta title="Planning meeting (iteration 32)"]]
[[!tag draft meeting]]
[[!meta date="2019-02-26 21:05"]]
[[!meta author="liw"]]

THIS IS A DRAFT

People
=============================================================================

* [[Lars|people/liw]]
* Ivan
* Pyry

Agenda
=============================================================================

* Discuss and decide goals for this iteration.

Notes
=============================================================================

* This iteration is about moving Ick forward to using Muck.

Tasks for this week
=============================================================================

Tasks may be part of a project or be random small ones (max an hour)
that just need doing.

[[!table data="""
what                                        | Who      | estimate(h)

Write trivial facade for ickui              | Ivan+Pyry | 1
Make Muck benchmark to simulate log storage | Lars      | 1

Total                                       | Ivan+Pyry | 1
Total                                       | Lars      | 1
"""]]

Task descriptions
------------------------------------------------------------------------------

* **Write trivial facade for ickui:** Write a facade that provides a
  trivial `/version` endpoint, which reports the facade's version,
  without requiring a login.

  _Acceptance criteria:_ Facade `/version` can be tested manually with
  curl. The output includes the git commit, if the facade is running
  from a git clone.

* **Make Muck benchmark to simulate log storage:** The design of how
  build logs should be stored in Muck was discussed on the Ick mailing
  list. The design that the discussion ended up with should be
  validated by having a benchmark show that it works acceptably fast
  with a 100,000 lines of build log.

  _Acceptance criteria:_ The benchmark simulates how the controller
  would store logs, and reports a speed for re-assembling the log from
  snippets. (It is not necessary to make it fast; that's out of scope
  for the task.)