Agenda for the Midnight Doodle, 11pm GMT Fri 21st Oct

1. Whether to fork

2. What to call the fork (this may sound trivial but it's really important):
   • ExperimentalAngband
   • AngbandNG
   • Vangband
   • French Vanilla
   • Angband Sans Frontieres

3. Practicalities of the fork:
   • separate git repo
   • separate bug tracker
   • separate website, maybe?
   • same dev blog, maybe?
   • same team structure/leadership?
   • same autobuilder(s)

4. Defining the fork: who wants what in or out of the manifesto / announcement (see attachment):
   • important principles
     • based on V (same basic fantasy/mythical races/classes/monsters)
     • no other strictures (anything could go in, or out)
     • highly volatile (experimentation > balance - don't upgrade until current game finishes ...)
     • if your change breaks something, you should fix it or revert
     • implies no commitments to/for V (nothing is guaranteed to migrate to V)
   • putative roadmap
     • affixes
     • 1520-food
     • borg
     • reworked detection/ID (#298, #418, #509, #632, #1015, #1161, #1450, #1514 inc. rune-based ID)
     • crafting/forging (inc. new randarts, artifact devices etc.)
     • new combat (#534, #828, #1205, #1279, #1436, #1437, #1446)
     • tiered effects (#1041)
     • reworked magic (#1421 and implications for classes/skills)
     • more changes to dungeon generation
     • LOS/FOV (#757, #768)
     • monster flow/AI/detection (#78, #574, #591, #963, #1113, #1433)
     • ego monsters
     • new curses (any year now)

5. Any consequential issues for V (e.g. changes to commit access, roadmap, milestone dates)

6. AOB.