Daniel, can I see if I'm understanding you correctly? you're saying that the way you want to see things run is that each year we pick a different people to form a team who are guiding the conference. They get to have creativity, and within oversight of the project, the DebConf community and the DCC this team gets to have wide latitude.
Year to year there are more or less members of this team who are at the host city. There probably do need to be members of this team in the host country. (It's possible to run conferences without people in the host country but those conferences cost at least an order of magnitude more than a DebConf to put on in my experience.) We've often been calling this the local team. The local team may be able to recruit volunteers from the broader DebConf community to do some tasks. Ultimately though, this yearly selected team is responsible for putting on the whole conference, either by doinga task themseles, finding volunteers to do that task, or not doing the task. The advantage you see in this system is that we get to try new things, it's not the same old DebConf. We get a different grou of people each year who can take ownership. We get rotation. The disadvantage is that this team may have more or less resources from the broader community. Timezone, communication skills, interpersonal factors, burnout, political situations (think choice of country), and phase of moon effect this. If I am understanding you correctly LOCAL TEAM IS A HORRIBLE NAME!!! You have new people coming into this team every year. With a name like local team they're going to assume that it's mostly the local people. Instead, as part of putting together a DebConf bid, you want this team to look to other parts of the world for some parts of the task. Perhaps as part of the team putting together Debconf 19, Antonio doesn't want to focus on content. It sounds like you're saying that since content is kind of essential to a Debconf, he (or the team putting together the bid) needs to have a plan for content. It can be to do it themselves. But it could also be to think about who did a great job of content in the past and see if they will join the "local team." to handle that. Except that with a name like local team, people aren't going to think that way, especially if this is their first DebConf bid. Again, this all assumes I am understanding you correctly. If I am, better names might include: * guiding team * The 2019 team (for the 2019 conference) * The bidding team But it also sounds like we want to emphasize the recruiting people from all around the wold as part of putting together the bid. It's possible this is all documented and that because I'm the kind of person who reads docs, if I were more involved in DebConf I'd just know it. And I'd find the name "local team" quaint kind of like how I find not a typewriter errors quaint. But for someone new, it's going to be confusing. And for this job, it's going to be inherently new, so I think that matters. I now leave you and Antonio to the interesting debate of whether this is the model we want.
