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
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
|
[[!meta title="Planning meeting"]]
[[!tag meeting]]
[[!meta date="2017-10-15 10:51"]]
[[!meta author="Lars Wirzenius"]]
People
=============================================================================
* [[people/liw]]
Agenda
=============================================================================
* Discuss and decide goals for this iteration.
Notes
=============================================================================
* My aim for this iteration is to get the controller to manage project
information properly. This means reviewing the yarns and code
related to the `/projects` end point, and fixing anything that needs
fixing. This will be time-boxed, so that if I run out of time to
fix, I will at least make a list of things that need to be fixed.
* Additionally, I will start a new tool, `icktool`, which will
provider a command-line interface to accessing the Ick APIs. Thinks
curl, but with token generation added, and output formatting.
Current projects
-----------------------------------------------------------------------------
* [[projects/2017/projects-endpoint]]
* [[projects/2017/icktool]]
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 | project | Who | estimate(h)
Write icktool that can generate token | [[projects/2017/icktool]] | [[people/liw]] | 2h
Review yarns for /persons | [[projects/2017/projects-endpoint]] | [[people/liw]] | 2h
Reviaw code for /persons | [[projects/2017/projects-endpoint]] | [[people/liw]] | 2h
Clean up yarns, code for /persons | [[projects/2017/projects-endpoint]] | [[people/liw]] | 2h
Total | | [[people/liw]] |
"""]]
Task descriptions
------------------------------------------------------------------------------
* **Write icktool that can generate token:** Add to ick2.git a new
script, `icktool`, which can generate a token, and query `/version`.
It should read a configuration file to get the necessary information
so that the user doesn't need to repeat things every time.
**Acceptance criteria:** Assuming a correct configuration file, user
can run `icktool token` to generate a token, and `icktool version` to
get a nicely formatted vesion of the `/version` resource. A token is
generated automatically, as needed, or can be provided by the user via
a command line option, to avoid re-generating every time.
* **Review yarns for /persons:** Read the current yarns for `/projects`,
and make note of anything that seems it would be worth fixing.
**Acceptance criteria:** I'm happy that after fixing the things I
find, the yarns will be good, meaning they're understandable by
others, correctly specify the needed functionality, and completely
test all the relevant aspects of the controllers handling of project
information.
* **Reviaw code for /persons:**Read the current code implementing
`/projects`, and make note of anything that seems it would be worth
fixing.
**Acceptance criteria:** I'm happy that after fixing the things I
find, the code will be good, meaning it's clean, correct, has good
unit tests, and has no major architectural or other flaws.
* **Clean up yarns, code for /persons:** This is time-boxed: only spend
the allocated time this iteration, and if there's more to do, leave
that for a future iteration.
**Acceptance criteria:** I've fixed at least one thing off the list,
and it's committed, merged, and passes CI.
|
