On Wed, Dec 19, 2018 at 8:19 PM Justin Mclean <jus...@classsoftware.com> wrote:
> > Slide 4 > - While the chair is responsible for making sure teh report is submitted > to the board, it's the PMC who writes and contrite to it. "The report is > technically single-author written by the PMC chair.” is sometimes teh case > but in some project its more of a collaborative effort. > The phrasing at https://www.apache.org/foundation/board/reporting is "While in most cases the chair works with other PMC members to write the report, the report is ultimately the chair's responsibility to complete and submit." I've been coached that the report is, ultimately: - from: the chair - to: the Board - about: Beam In practice, it is collaboratively drafted on dev@beam. I think there's subtlety here that I probably don't understand fully. Sort of like how the PMC selects a chair but the board appoints the person. Can you help me understand this better? Kenn Slide 9 > - Voting on contentious issues can cause division and split the community, > so care needs to be taken to build consensus before a vote of this nature. > - Voting on releases is different, -1 is not a veto > > Slide 10 > - CTR is much more common on ASF projects > > Slide 12 > - The tick and crosses are misleading, committer can be involved in > everything but don’t have binding votes including on releases. > > Slide 15 > - Quick to review PRs need not apply with CTR and committer can mentor > contributors as well in fact they may do that more than PMC members. > > I;’ll give some more feedback when I get a chance. > > Thanks, > Justin > > 1. https://whimsy.apache.org/roster/ > 2. https://www.apache.org/foundation/policies/conduct.html > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
