* Quick review of DebConf16 organization. The goal is to be able to quickly
  identify
  - what went good/bad?
    - Bad
     - left things too late, even more than other years
      - blocked brochure on website/design (but no one was working actively on that yet)
     - orga turmoils affecting the local team
     - lacked final report from DC15
     - too much RT (items rotted there, hidden among spam); work on a sponsors list
       -> Drop RT, focus on Git (having RT behind debian.org antispam ?)
     - venue/food contracts came too late (though people were confident it would finally get worked out) -- until quite late the plan had been to bring in outside caterers
     - some things were delayed until Stefano was physically present
     - At some point we do have to address governance... although it is a contentious topic (to put it mildly)
    + Good
     + Allison stepped in to do necessary work within sponsorship team
     + Attitude of "just get things done"
  - what was a good/bad idea?
  - what could/should the DebConf17 team take from this?
   - Allison hopes we already have a good base/initial team to start on sponsorship work
   - especially for local sponsorship, we need more team members to pick up a couple of sponsor contacts
   - for DC17, Jimmy is already checking about legal issues (how to sign/pay)
   - sometimes items need to be discussed/agreed in team meetings; recommendation is to force making a decision rather than let things slip
   - do we need some group to work as tie-breakers? (waiting for consensus can be frustrating/inefficient)
   - make sure everyone agrees on what we are trying to achieve

	
	
		We can still be intentional about the culture we want to enable us to work effectively, regardless of local cultural defaults.
* How to help DebConf17 team to get started?
    - Preparing a bid for the previous year helped the team have a good basis now
    - Choice of venue (decision by a narrow vote) was a way of deciding the type of DebConf for DC17
  - What are the first steps?
    - Define wishes/ideas
    - Think about timeline/tracking of tasks
    - Recruit people for sponsorship work, and try to spread across team
  - Who's interested to help?
    - Speak to DC17 locals to get an account on dc17's kanboard
  
  "Hybrid mañana/not-mañana culture" needed (think about needs in advance, write them down when you think of them, and handle them early if possible. but some things need to be taken care of, or changed, closer to the conference.)
  - DC17-needed list compiled by locals during dc16 https://pad.riseup.net/p/dc17_needed
  
  - Continuity team?
   - Need some group to sign documents/approve budgets -- so need DPL delegation?
   - In the past we did have a few cases where the local team took decisions that were not ok -- need to have some way to address this
  
    - Of course, challenges for every conference are completely different... I would not expect the same strengths and shortcomings of _this_ experience to be applied to next. But having long-term accumulation of knowledge is *important*!
    - DPL thinks the delegation is necessary, but we should avoid putting too much pressure on them.