justinmclean commented on code in PR #154: URL: https://github.com/apache/comdev-site/pull/154#discussion_r1483618591
########## source/board/overview.md: ########## @@ -0,0 +1,89 @@ +--- +title: An overview of board responsibilities +url: /board/overview.html +tags: ["board"] +--- + +What's involved in being a director? This document tries to give an +overview of the time commitment involved, and what the work looks like. + +The official duties of the Board are defined [on the Apache Governance +website](https://apache.org/foundation/governance/board.html). You +should read that doc, and those to which it links, first. + +This document tries to give a little more flavor, for the benefit of +someone who's considering running for their first term as a Director. + +# Work Load + +## Monthly meeting + +As with most things in open source, you can spend as much time on them +as you want, and pursue your indivual passions. However, being a +director does carry certain basic responsibilities. +You are expected to attend the board meeting, once a month. This meeting +can run from a half hour, on up, depending on the issues to be discussed +in that particular month. + +The shortest board meeting ran less than 15 minutes, while the longest +ones have been upwards of 2 hours. + +## Pre-meeting work + +Most of the work of a board meeting happens before the meeting starts, +as discussed in the [formal +documentation](https://apache.org/foundation/governance/board.html). + +The Incubator report, in particular, consists of the podling reports +for all active incubation efforts, and so is effectively a dozen reports +on its own. + +In a typical month, there will be between 70 and 90 individual board +reports. In addition to that, there are a dozen officers reports, +various special orders, and following up on action items. + +If you review each of your shepherd projects in depth, and attempt to read Review Comment: Mention, how many report a director is assigned to as a shepherd? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
