Dear all,
I sense we are reaching fatigue in the book project, and the situation is exacerbated
by the fact that we're communicating over the net, rather than in math common room.
We're losing the collaborative spirit!
I would like to propose a couple of steps which might help the situation.
1. Focus first on the technical issues that need to be done, such as organizing macros, the symbols index, filling in citations, etc. Keep controversial issue and the ones that require thought for later.
2. If you would like to make a change which requires a discussion, open a new issue. Do *not* wait for a concensus on every little detail. If it is clear that *some* sort of change will be accepted, then just make your change. We can then iteratively improve on it. There is no shame in redacting some commits if it turns out later that they were a bad idea.
I propose that the technical dictator divides issues into two milestones: "just-needs-to-be-done" and "will-generate-discussion". We should clean up just-needs-to-be-done before we work on "will-generate-discussion". I can do it as well, if the technical dictator feels I am trhustworthy.
At this point the book is already in a very good shape. So even if we don't make any will-generate-discsussion changes, the book is ok. But the book cannot be released when we still lack and index, and an index of symbol, and dozens of citations, and there are overful boxes, and missing references, etc.
Kindly,
Andrej