On Fri, Jun 27, 2014 at 6:12 AM, Niklas Lemcke - 林樂寬 <compul@xxxxxxxxxxxxxx> wrote: > Regarding the mumble meeting: > > It has been suggested that the PMC will not have a chair for a longer > period of time, but rather that the chair changes from meeting to > meeting. I second that thought. Bill earlier (on IRC) suggested that I > organize the first meeting, which I would GLaDly do. However, if anyone > else feels they or someone else should do it, that's just as good. > > I tried to summarize the points that will have to be discussed, so that > everyone can get informed before the meeting and have an opinion / some > information. I suppose the list is still not complete, so please add to > it. > > Here it is, in chronological order: > > ## precedure related topics ## > * method of voting > * have Jos explain the nature of his foundation, and the intended > nature of collaboration with the CipherShed Project > * appoint QA Team members > * define a protocol to be followed for merges to the codebase (PMC vs. > QA Team) > * decide how to accept new contributors > * warrant canary solution > * Voice chats vs. IRC / mailing list discussions > * contact address (listaddress vs. @ciphershed.org) > * hopefully give Jos the go-ahead for funneling all them people > towards the CipherShed Project, and simultaneously discuss whether he > should officially question the security of Protectorion on twitter > > > ## code progress related topics ## > * signing / tagging of commits (related to merge-protocol) > * who does binary creation signing? Multiple persons for comparison? > * estimate date for first rebranded release, as well as what is > supposed to be included > * decide what should be included in second 'bugfix-release', and try > to estimate a timeframe / workload I pretty much agree with everything here. I don't think we should have a "dedicated chair," but a revolving chair who runs meetings. As for the topics above, I think that's pretty much exactly what we need to address.