I'm sorry, but certain things require special care. General organizing discussions can proceed on dev@, excluding this specific one.
On Sun, Jan 20, 2019 at 8:43 PM Gris Cuevas <g...@apache.org> wrote: > > > On 2019/01/19 16:58:52, Davor Bonaci <da...@apache.org> wrote: > > I'd say these matters are generally private between the organizer(s) and > > the PMC. This thread should continue on the PMC-private mailing list. > > Last time we checked (back in October), people who are not part of the PMC > couldn't send emails to the private mailing list nor read the responses. > The organization of the last London Summit occurred in the private list > with me and Matthias directly cc'ed in our individual emails. Additionally > a few of the other organizers didn't get visibility on how decisions were > formed and this obstructed the planning. > > I'd suggest we continue with the initial discussion here in order to offer > transparency, if a sensitive matter needs to be discussed, we can call it > out here and set context that a specific conversation will be moved to > private, bringing the decision made back to this thread. > > Also, I'd recommend we keep the discussion focused on the main matter: > Summit planning. If you have a proposal to revise what communications need > to be had in specific channels, you can start the conversation in a new > separate thread, I see a lot of value in having it. > > @PMC members, we'd love to get an outline of what needs to be done to > continue with the planning. We have a few people interested in helping out > and we'd love to keep the momentum going. > > > > > On Fri, Jan 18, 2019 at 4:06 PM Ahmet Altay <al...@google.com> wrote: > > > > > Thank you Joana. > > > > > > Kenn and PMC members could you comment on what needs to be done to move > > > this forward? > > > > > > On Thu, Jan 17, 2019 at 3:40 PM joanafil...@google.com < > > > joanafil...@google.com> wrote: > > > > > >> Dear Project Management Committee, > > >> > > >> > > >> The Beam Summits are community events funded by a Sponsoring Committee > > >> and organized by an Organizing Committee. I’d like to get the > following > > >> approvals: > > >> > > >> To organize and host the Summits under the name of Beam Summit > <region> > > >> <year>, i.e. Beam Summit North America 2019, Beam Summit Europe 2019 > and > > >> Beam Summit Asia 2019. > > >> > > >> To form organizing committees for each edition > > >> > > >> Approval to host each edition on the following dates and locations: > > >> > > >> - Beam Summit North America, on April 3rd, San Francisco, CA. (150 > > >> attendees) > > >> > > >> - Beam Summit Europe, on June 19th, Berlin, Germany. (150 attendees) > > >> > > >> - Beam Summit Asia, October (exact date tbc), Tokyo, Japan. (150 > > >> attendees) > > >> > > >> The events will provide educational content selected by the Organizing > > >> Committee, and will be a not-for-profit event, however, we might > charge a > > >> fee to support the organization and logistics costs. This matter will > be > > >> decided by the Organizing Committee and will be brought back to the > PMC if > > >> needed. The events will be advertised on various channels, including > the > > >> Apache Beam’s and Summit sponsor’s social media accounts. > > >> > > >> > > >> The Organizing Committee will acknowledge the Apache Software > > >> Foundation's ownership of the Apache Beam trademark and will add > > >> attribution required by the foundation’s policy on all marketing > channels. > > >> The Apache Beam branding will be used in accordance with the > foundation’s > > >> trademark and events policies specifically as outlined in Third Party > Event > > >> Branding Policy. The Organizing Committee does not request the ASF to > > >> become a Community Partner of the event. > > >> > > >> > > >> Please feel free to request further information if needed. > > >> > > >> > > >> Kind Regards, > > >> > > >> Joana Carrasqueira > > >> > > > > > >
