On 12/20/18 3:14 AM, Kenneth Knowles wrote:
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
The PMC doesn't select a chair (it doesn't have the authority), but it
motions the board to appoint a specific person as chair, sort of like
introducing legislation in a parliament but not being able to vote on
it. The board then votes and either ratifies that motion, or it says
"we're not going to do that and here's why". A chair is an officer of
the foundation, and as such, HAS to be appointed by the board of
directors in the case of top level projects.
The chair is basically a glorified secretary (with certain additional
day-to-day operational powers that I'll not go into detail about), and
while the report can be and often is made as a collaborative effort,
it's the chair responsibility to send that report - whether it be a team
effort or a single person writing it - to the board.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
