|
|
ac2dcb |
# Board minutes 2016-11-11
|
|
|
ac2dcb |
|
|
|
ac2dcb |
## Attendees
|
|
|
ac2dcb |
* Jim Perrin
|
|
|
ac2dcb |
* Fabian Arrotin
|
|
|
ac2dcb |
* Johnny Hughes
|
|
|
ac2dcb |
* Mike McLean
|
|
|
ac2dcb |
* Ralph Angenendt
|
|
|
ac2dcb |
* Tru Huynh
|
|
|
ac2dcb |
* Karsten Wade
|
|
|
ac2dcb |
* Karanbir Singh
|
|
|
ac2dcb |
|
|
|
ac2dcb |
##Quorum achieved.
|
|
|
ac2dcb |
|
|
|
ac2dcb |
## Agenda & notes
|
|
|
ac2dcb |
|
|
|
ac2dcb |
### Budget
|
|
|
ac2dcb |
#### Do we want to have the Board manage part of the budget from OSAS/RH?
|
|
|
f3eba8 |
* Yes, on a year-over-year evolution of how things are managed.
|
|
|
f3eba8 |
* It’s RH money run on behalf of ...
|
|
|
ac2dcb |
#### What do we want to make public?
|
|
|
f3eba8 |
* Spending for community travel
|
|
|
f3eba8 |
* Swag & support provided out to community events directly
|
|
|
f3eba8 |
* Constraints on paying people back
|
|
|
f3eba8 |
* First year -- PayPal only, receipts require
|
|
|
f3eba8 |
* Budget limit per number of people, e.g. $150 for 50 people, etc.
|
|
|
f3eba8 |
* SIGs
|
|
|
f3eba8 |
* Community SIG leads …
|
|
|
f3eba8 |
* Cover up to $X of travel
|
|
|
f3eba8 |
* May cover some of RH expenses …
|
|
|
f3eba8 |
* Talk to management
|
|
|
f3eba8 |
* Cover up to $X of travel
|
|
|
f3eba8 |
* What is the definition of community in this context?
|
|
|
f3eba8 |
* Contributors from a vendor are still a community, but their employer should see the value of sending that person.
|
|
|
f3eba8 |
* Contributors from a project sponsored/run by a foundation should be able to find a way of sending a person.
|
|
|
f3eba8 |
* Contributors on own time & dime, should find a way to sponsor and support from project as much as possible.
|
|
|
f3eba8 |
|
|
|
ac2dcb |
#### Process
|
|
|
f3eba8 |
* Need a write-up.
|
|
|
f3eba8 |
* Three people with at least one Board member to oversee budget management, can do in Year One.
|
|
|
f3eba8 |
* Dollar amount to take to the Board for approval.
|
|
|
f3eba8 |
* Spending for all vendors coming in managed by the finance committee.
|
|
|
f3eba8 |
* Follows the same process.
|
|
|
f3eba8 |
* Year one - all run by Board for initial trial
|
|
|
f3eba8 |
* All should have a title in the project based on an existing chain of trust.
|
|
|
f3eba8 |
* Year two - look for people interested in helping
|
|
|
f3eba8 |
|
|
|
ac2dcb |
#### Getting outside funding
|
|
|
f3eba8 |
* Need a relationship with an open source program office.
|
|
|
f3eba8 |
* Run it on behalf of -- they spend at our direction.
|
|
|
f3eba8 |
* No pay to play … need to trust the community as to what we want to spend.
|
|
|
f3eba8 |
* Build trust in initial year …
|
|
|
f3eba8 |
* Community fund …
|
|
|
f3eba8 |
* E.g. CPanel wants to give $10K to sponsor people to their conference.
|
|
|
f3eba8 |
* Use the same process for decisions as for spending direct money.
|
|
|
f3eba8 |
* Transparency of multiple supporters shows diversity.
|
|
|
ac2dcb |
#### Equipment budget
|
|
|
f3eba8 |
* Solve problems the Board identifies
|
|
|
f3eba8 |
* E.g. signing for SIGs
|
|
|
f3eba8 |
* Strategic and tactical
|
|
|
f3eba8 |
* Oversight of the Infra Team …
|
|
|
ac2dcb |
|
|
|
ac2dcb |
|
|
|
f3eba8 |
* Putting an annual plan together
|
|
|
f3eba8 |
* Keep a 10% slush to cover all of above
|
|
|
ac2dcb |
|
|
|
ac2dcb |
|
|
|
ac2dcb |
#### Credit Suisse
|
|
|
f3eba8 |
* Sponsoring millions in EOL hardware for suitable charities and non-profits
|
|
|
f3eba8 |
* Sep 2017 is first set of kit coming available
|
|
|
f3eba8 |
* Get CentOS running on the laptops given away
|
|
|
f3eba8 |
* How should CentOS Project be involved?
|
|
|
f3eba8 |
* Can we use any of that hardware?
|
|
|
ac2dcb |
#### Actions
|
|
|
f3eba8 |
* Full process write-up.
|
|
|
f3eba8 |
* Define what community means in this context.
|
|
|
f3eba8 |
* Process to be public.
|
|
|
f3eba8 |
* By 1 March.
|
|
|
f3eba8 |
* Pick the finance committee.
|
|
|
f3eba8 |
|
|
|
ac2dcb |
### Advisory capacity (Board)
|
|
|
f3eba8 |
* Getting advice from:
|
|
|
f3eba8 |
* Representative of each Team about running the Project.
|
|
|
f3eba8 |
* From a specific user / audience?
|
|
|
f3eba8 |
* Who are using CentOS, maybe we can help make things better for them, then we get a voice into that community.
|
|
|
f3eba8 |
* Senior enough to have influence in that group and able to represent.
|
|
|
f3eba8 |
* What can they do?
|
|
|
f3eba8 |
* Come from existing contributors
|
|
|
f3eba8 |
* Provide wider perspective
|
|
|
f3eba8 |
* What does it mean to be on the Advisory Board?
|
|
|
f3eba8 |
* Provide advice to the executive leadership
|
|
|
f3eba8 |
* Examples
|
|
|
f3eba8 |
* Linux Foundation groups have an exec board, then a technical committee and community committee to advise.
|
|
|
f3eba8 |
* Proposal:
|
|
|
f3eba8 |
* Pick two areas, e.g.:
|
|
|
f3eba8 |
* VoIP
|
|
|
f3eba8 |
* High Energy Physics
|
|
|
f3eba8 |
* Identify four people in each area
|
|
|
f3eba8 |
* Arrange a monthly communication channel with those people and an identified CentOS person, with Board members involved.
|
|
|
f3eba8 |
* Ask Leslie Hawthorn to facilitate and manage the process.
|
|
|
f3eba8 |
* Each Board member identifies two areas of personal interest
|
|
|
f3eba8 |
* Two Board members research the areas to find people to be recommended
|
|
|
f3eba8 |
* Advisory Board is not a for-life thing, some privilege to be there
|
|
|
f3eba8 |
* Articulate the process publicly
|
|
|
f3eba8 |
|
|
|
ac2dcb |
### Metrics for SIGs
|
|
|
f3eba8 |
|
|
|
ac2dcb |
### Infra SIG & Fabian as Chair
|
|
|
ac2dcb |
|
|
|
ac2dcb |
|
|
|
ac2dcb |
|