@@ -25,7 +25,7 @@ the overall health and functioning of the team.
25
25
## Announcing the schedule
26
26
27
27
After each planning meeting, the topics for the next three weeks will
28
- be posted on the README.md of the main repository and also sent a
28
+ be posted on the README.md of the main repository and also sent to a
29
29
dedicated internals thread.
30
30
31
31
## Examples of good candidates for discussing at the steering meeting
@@ -56,10 +56,21 @@ time to talk out the plans in more detail.
56
56
When deciding the topics for upcoming meetings, we must balance a number of things:
57
57
58
58
- We don't want to spend time on design work unless there are known
59
- people who will implement it and support it.
59
+ people who will implement it and support it; this includes not only
60
+ the "main coder" but also a suitable reviewer.
60
61
- We don't want to take on "too many" tasks at once, even if there * are* people to
61
62
implement them.
62
- - We also don't want to have active projects that will be "stepping on each others' toes", changing the same set of code in deep ways.
63
+ - We also don't want to have active projects that will be "stepping on
64
+ each others' toes", changing the same set of code in deep ways.
65
+
66
+ ## Meetings are not mandatory
67
+
68
+ It is perfectly acceptable to choose * not* to schedule a particular
69
+ slot. This could happen if (e.g.) there are no proposals available or
70
+ if nothing seems important enough to discuss at this moment. Note
71
+ that, to keep the "time expectations" under control, we should
72
+ generally stick to the same 4-week cycle and simply opt to skip
73
+ meetings, rather than (e.g.) planning things at the last minute.
63
74
64
75
## Adding a proposal
65
76
@@ -95,3 +106,11 @@ detailed proposals as the work proceeds.
95
106
** The requirements for non-technical proposals are somewhat looser.** A
96
107
few sentences or paragraphs may well suffice, if it is sufficient to
97
108
understand the aims of the discussion.
109
+
110
+ ## Frequently asked questions
111
+
112
+ ** What happens if there are not enough proposals?** As noted above,
113
+ meetings are not mandatory. If there aren't enough proposals in some
114
+ particular iteration, then we can just opt to not discuss anything.
115
+
116
+
0 commit comments