Skip to content

Commit df9f042

Browse files
committed
incorporate some edits from mw
1 parent 75bb5b0 commit df9f042

File tree

1 file changed

+22
-3
lines changed

1 file changed

+22
-3
lines changed

procedures/steering-meeting.md

Lines changed: 22 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ the overall health and functioning of the team.
2525
## Announcing the schedule
2626

2727
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
2929
dedicated internals thread.
3030

3131
## Examples of good candidates for discussing at the steering meeting
@@ -56,10 +56,21 @@ time to talk out the plans in more detail.
5656
When deciding the topics for upcoming meetings, we must balance a number of things:
5757

5858
- 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.
6061
- We don't want to take on "too many" tasks at once, even if there *are* people to
6162
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.
6374

6475
## Adding a proposal
6576

@@ -95,3 +106,11 @@ detailed proposals as the work proceeds.
95106
**The requirements for non-technical proposals are somewhat looser.** A
96107
few sentences or paragraphs may well suffice, if it is sufficient to
97108
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

Comments
 (0)