PR#54: formatting - centos/board

centos / board

#54 formatting

Merged 3 years ago by rbowen. Opened 3 years ago by rbowen.

centos/ rbowen/board master into master

formatting

Rich Bowen • 3 years ago

f3eba8

meetings/2016/2016-05-18.md

file modified

+91 -87

		`@@ -11,106 +11,110 @@`

		`## Minutes`
		`### Should the Board have a Secretary who tracks minutes & does other related duties?`
		`- Duties might include:`
		`- Taking minutes.`
		`- Reporting minutes to the Board list.`
		`- Posting minutes to wiki.centos.org, when required.`
		`- Other potential duties to be proposed & assigned in the future.`
		`- Perhaps incoming Secretary organizes the next 3 meetings?`
		`- Rotation:`
		`- 3 meetings in a row, then rotate.`
		`- First volunteer:`
		`- Karsten.`
		`- Also willing to create first definition of the role for the Board to approve.`
		`- Proposal: Should the Board have a Secretary who tracks minutes & does other related duties?`
		`- Vote:`
		`- Not amending governance yet.`
		`- All present: Yes`
		`- Jim, Carl still need to vote to finalize.`
		`+ * Duties might include:`
		`+ * Taking minutes.`
		`+ * Reporting minutes to the Board list.`
		`+ * Posting minutes to wiki.centos.org, when required.`
		`+ * Other potential duties to be proposed & assigned in the future.`
		`+ * Perhaps incoming Secretary organizes the next 3 meetings?`
		`+ * Rotation:`
		`+ * 3 meetings in a row, then rotate.`
		`+ * First volunteer:`
		`+ * Karsten.`
		`+ * Also willing to create first definition of the role for the Board to approve.`
		`+ * Proposal: Should the Board have a Secretary who tracks minutes & does other related duties?`
		`+ * Vote:`
		`+ * Not amending governance yet.`
		`+ * All present: Yes`
		`+ * Jim, Carl still need to vote to finalize.`
		`+`
		`## PaaS SIG`
		`- Done a first release`
		`- First run of their CI is going`
		`+ * Done a first release`
		`+ * First run of their CI is going`
		`## CfgMgmt SIG`
		`- Volunteer help having time conflict to having a meeting.`
		`- Meeting time is not convenient for anyone.`
		`- Need a separate IRC channel? #centos-meeting`
		`- Recommendation is to go back to Julien and have him find a good-enough time using an alternative IRC channel if needed.`
		`- Julien is driving but is concerned about complexity.`
		`- Separate tag for each version of each tool …?`
		`+ * Volunteer help having time conflict to having a meeting.`
		`+ * Meeting time is not convenient for anyone.`
		`+ * Need a separate IRC channel? #centos-meeting`
		`+ * Recommendation is to go back to Julien and have him find a good-enough time using an alternative IRC channel if needed.`
		`+ * Julien is driving but is concerned about complexity.`
		`+ * Separate tag for each version of each tool …?`
		`### Audio SIG`
		`- One short voice meeting, distracted by 6.8 release :)`
		`- Around 4 people want to contribute.`
		`- One person would not mind being group lead.`
		`- Karsten offering to do a road show tour to CCRMA when SIG is ready`
		`+ * One short voice meeting, distracted by 6.8 release :)`
		`+ * Around 4 people want to contribute.`
		`+ * One person would not mind being group lead.`
		`+ * Karsten offering to do a road show tour to CCRMA when SIG is ready`
		`+`
		`### Virt SIG`
		`- Xen part going like clockwork.`
		`- oVirt is active`
		`- Word of mouth is they consider move to CentOS to have been very beneficial`
		`+ * Xen part going like clockwork.`
		`+ * oVirt is active`
		`+ * Word of mouth is they consider move to CentOS to have been very beneficial`
		`### Cloud SIG`
		`- Clocking along fine.`
		`+ * Clocking along fine.`
		`### Atomic SIG`
		`- Happening, going fine`
		`- Vagrant box downloads ~25K?`
		`+ * Happening, going fine`
		`+ * Vagrant box downloads ~25K?`
		`### OpTools / Infra Tools SIG`
		`- Tracking, monitoring, etc.`
		`- Matthias Runge proposing`
		`+ * Tracking, monitoring, etc.`
		`+ * Matthias Runge proposing`
		`### Centosproject.org`
		`- Email redirector for people with accounts on accounts.centos.org`
		`- Domain could have contributor-focused content v. the end-user focus of centos.org & wiki.`
		`- Process`
		`- Email comes automatically from FAS.`
		`- Special group to approve people?`
		`- Protect from spam/abuse.`
		`- Contributor agreement?`
		`- Sensitive, complex area`
		`- Cla_done is patched out of our FAS`
		`- Karsten suggested then withdrew`
		`- Can we do that with “any” SIG approval?`
		`- Concern is to make sure people are real contributors`
		`- It should mean something.`
		`- SIG chair response can be slow in ack’ing users.`
		`- Need to specify criteria before announcing …`
		`+ * Email redirector for people with accounts on accounts.centos.org`
		`+ * Domain could have contributor-focused content v. the end-user focus of centos.org & wiki.`
		`+ * Process`
		`+ * Email comes automatically from FAS.`
		`+ * Special group to approve people?`
		`+ * Protect from spam/abuse.`
		`+ * Contributor agreement?`
		`+ * Sensitive, complex area`
		`+ * Cla_done is patched out of our FAS`
		`+ * Karsten suggested then withdrew`
		`+ * Can we do that with “any” SIG approval?`
		`+ * Concern is to make sure people are real contributors`
		`+ * It should mean something.`
		`+ * SIG chair response can be slow in ack’ing users.`
		`+ * Need to specify criteria before announcing …`


		`- Proposal: Should we provide this as an email alias/redirector for all contributors?`
		`- Implementation plan not included here …`
		`- Vote:`
		`- All present: Yes`
		`- Jim, Carl still need to vote to finalize.`
		`- Implementation plan forthcoming`
		`+ * Proposal: Should we provide this as an email alias/redirector for all contributors?`
		`+ * Implementation plan not included here …`
		`+ * Vote:`
		`+ * All present: Yes`
		`+ * Jim, Carl still need to vote to finalize.`
		`+ * Implementation plan forthcoming`

		`### SIG merit rises …`
		`- Do we have a process to promote SIGs?`
		`- Scaffolding already in place.`
		`- Need more docs about how SIGs work.`
		`- Not much written down, very verbal`
		`- Keeping it sane, easy, process-lite.`
		`- New SIGs bring same questions each time.`
		`- Expectations on SIGs vary.`
		`- At what part do they sponsor own people, sign own packages.`
		`- Can we have a SIG how-to, what document discussion?`
		`- Karsten volunteering to pull that meeting/discussion together.`
		`- Look into SIG guide`
		`- https://wiki.centos.org/SIGGuide`
		`- Good to use for centering of the SIG lead discussion ^^^^^`
		`- What are merit levels?`
		`+ * Do we have a process to promote SIGs?`
		`+ * Scaffolding already in place.`
		`+ * Need more docs about how SIGs work.`
		`+ * Not much written down, very verbal`
		`+ * Keeping it sane, easy, process-lite.`
		`+ * New SIGs bring same questions each time.`
		`+ * Expectations on SIGs vary.`
		`+ * At what part do they sponsor own people, sign own packages.`
		`+ * Can we have a SIG how-to, what document discussion?`
		`+ * Karsten volunteering to pull that meeting/discussion together.`
		`+ * Look into SIG guide`
		`+ * https://wiki.centos.org/SIGGuide`
		`+ * Good to use for centering of the SIG lead discussion ^^^^^`
		`+`
		`+ * What are merit levels?`
		`0. SIG Chair(s) exist & have membership.`
		`1. SIG Chair(s) can sponsor members.`
		`2. SIG Chair(s) can sign content.`
		`- Maybe can delegate sponsorship?`
		`- Proposal -- Board sponsor suggest SIG is ready and asks for vote. (post-minutes comment from KW: Meaning, when the Board sponsor for a SIG thinks it is ready to move up the merit levels, that Board member asks the Board to vote on the rise. Presumably others can also suggest, but the sponsor really is the champion for a SIG on the Board, as per Governance.)`
		`- Vote:`
		`- All present: Yes`
		`- Jim, Carl still need to vote to finalize.`
		`- Are any SIGs ready?`
		`- Virt SIG …`
		`- Current Leader may be leaving soon`
		`- Cloud SIG`
		`- All friends and family …`
		`- Self referential …`
		`- Leadership is very responsive.`
		`- SCL`
		`- Somewhat responsive …`
		`- PaaS`
		`- Very new, but might progress quickly`
		`+`
		`+ * Maybe can delegate sponsorship?`
		`+ * Proposal -- Board sponsor suggest SIG is ready and asks for vote. (post-minutes comment from KW: Meaning, when the Board sponsor for a SIG thinks it is ready to move up the merit levels, that Board member asks the Board to vote on the rise. Presumably others can also suggest, but the sponsor really is the champion for a SIG on the Board, as per Governance.)`
		`+ * Vote:`
		`+ * All present: Yes`
		`+ * Jim, Carl still need to vote to finalize.`
		`+ * Are any SIGs ready?`
		`+ * Virt SIG …`
		`+ * Current Leader may be leaving soon`
		`+ * Cloud SIG`
		`+ * All friends and family …`
		`+ * Self referential …`
		`+ * Leadership is very responsive.`
		`+ * SCL`
		`+ * Somewhat responsive …`
		`+ * PaaS`
		`+ * Very new, but might progress quickly`

meetings/2016/2016-06-15.md

file modified

+74 -67

		`@@ -16,75 +16,82 @@`
		`## Agenda & notes`

		`### Optools SIG`
		`- Lack of tools in CentOS (and Fedora) for operators of large infrastructure/installations`
		`- Doesn’t fit in e.g. Cloud SIG`
		`- Home for these tools + bits and pieces to install/config infrastructure`
		`- E.g. if logging, there are good & bad examples of what to log, how to log, etc.`
		`- So provide a guide of how-to install each specific tool, what to watch, etc.`
		`- E.g. OpenStack installations log way too much, including things that are not errors but look like errors, so need some filtering afterwards.`
		`- Useful outside of each specific SIG.`
		`- Relationship with Config Mgmt SIG`
		`- Would provide manifests/playbooks/recipes/etc. To get tools installed would first look to existing sources in CentOS & SIGs.`
		`- Configs ultimately belong to the Config Mgmt SIG.`
		`- Working against duplicated efforts in tools stacks`
		`- Diff stacks of software reimplement or bring in the same tools`
		`- Use case: correlate logs amongst all these things`
		`- E.g. openshift on top of openstack, want to be able to correlate the logged error into each part of the stack - storage, underlying OS, orchestration, etc.`
		`- Give operators tools to do deep-cause analysis`
		`- KB - having ELK, graphon, etc. in the project helps on community side as we have a very operator-heavy base, many potential consumers.`
		`- Proposal is on the wiki -- https://wiki.centos.org/SpecialInterestGroup/OpsTools`
		`- What about the lack of upstream connection? Are any SIG members from the relevant upstream projects.`
		`- Most things are not in our direct control, refer back up to EPEL.`
		`- Willing to build bridges into upstreams where there are no existing upstream developers here`
		`- Talking with actual upstream developers.`
		`- Elastic is changing to an ‘open core’/’commercial open source’ model`
		`- Have some contributions in`
		`- Paying attention to open source replacements for problematic source models.`
		`- Can start with current proposed package set, but can replace components one-at-a-time without disrupting user experience.`
		`- Provide modularity so we’re not locked in`
		`- “Log collector package” -- don’t need to know what is underneath, but can choose if you prefer.`
		`- Vote - Should the OpsTools SIG proposal be accepted and the SIG move forward?`
		`- +1 from all present`
		`- Tru vote, comments, questions requested`
		`+ * Lack of tools in CentOS (and Fedora) for operators of large infrastructure/installations`
		`+ * Doesn’t fit in e.g. Cloud SIG`
		`+ * Home for these tools + bits and pieces to install/config infrastructure`
		`+ * E.g. if logging, there are good & bad examples of what to log, how to log, etc.`
		`+ * So provide a guide of how-to install each specific tool, what to watch, etc.`
		`+ * E.g. OpenStack installations log way too much, including things that are not errors but look like errors, so need some filtering afterwards.`
		`+ * Useful outside of each specific SIG.`
		`+ * Relationship with Config Mgmt SIG`
		`+ * Would provide manifests/playbooks/recipes/etc. To get tools installed would first look to existing sources in CentOS & SIGs.`
		`+ * Configs ultimately belong to the Config Mgmt SIG.`
		`+ * Working against duplicated efforts in tools stacks`
		`+ * Diff stacks of software reimplement or bring in the same tools`
		`+ * Use case: correlate logs amongst all these things`
		`+ * E.g. openshift on top of openstack, want to be able to correlate the logged error into each part of the stack - storage, underlying OS, orchestration, etc.`
		`+ * Give operators tools to do deep-cause analysis`
		`+ * KB - having ELK, graphon, etc. in the project helps on community side as we have a very operator-heavy base, many potential consumers.`
		`+ * Proposal is on the wiki -- https://wiki.centos.org/SpecialInterestGroup/OpsTools`
		`+ * What about the lack of upstream connection? Are any SIG members from the relevant upstream projects.`
		`+ * Most things are not in our direct control, refer back up to EPEL.`
		`+ * Willing to build bridges into upstreams where there are no existing upstream developers here`
		`+ * Talking with actual upstream developers.`
		`+ * Elastic is changing to an ‘open core’/’commercial open source’ model`
		`+ * Have some contributions in`
		`+ * Paying attention to open source replacements for problematic source models.`
		`+ * Can start with current proposed package set, but can replace components one-at-a-time without disrupting user experience.`
		`+ * Provide modularity so we’re not locked in`
		`+ * “Log collector package” -- don’t need to know what is underneath, but can choose if you prefer.`
		`+ * Vote - Should the OpsTools SIG proposal be accepted and the SIG move forward?`
		`+ * +1 from all present`
		`+ * Tru vote, comments, questions requested`
		`+`
		`### ## SIGs ready for rise up?`
		`- Cloud SIG getting quite close`
		`- Work is having a lot of influence on downstream`
		`- Sorting out how that’s going to work`
		`- Maybe segregate RH parts?`
		`- Maturing very quickly`
		`- Expect to see them in self-admin mode soon-ish`
		`- PaaS SIG very organized`
		`- Closed group`
		`- Quite RH focused`
		`- Not ready yet, maybe next meeting or so?`
		`- Virt SIG`
		`- Established, self-organized`
		`- But … George Dunlap is moving from packaging to developing upstream`
		`- He’s actively looking for a takeover`
		`- Waiting for leadership shift`
		`+`
		`+ * Cloud SIG getting quite close`
		`+ * Work is having a lot of influence on downstream`
		`+ * Sorting out how that’s going to work`
		`+ * Maybe segregate RH parts?`
		`+ * Maturing very quickly`
		`+ * Expect to see them in self-admin mode soon-ish`
		`+`
		`+ * PaaS SIG very organized`
		`+ * Closed group`
		`+ * Quite RH focused`
		`+ * Not ready yet, maybe next meeting or so?`
		`+`
		`+ * Virt SIG`
		`+ * Established, self-organized`
		`+ * But … George Dunlap is moving from packaging to developing upstream`
		`+ * He’s actively looking for a takeover`
		`+ * Waiting for leadership shift`
		`+`
		`### Credit Suisse`
		`- SE Asia operations invests 5 to 7 mil in corporate social responsibility, including into technology`
		`- Hosting contests, giving away laptops, etc.`
		`- Want to spend on FLOSS projects`
		`- Moving dev environment from Debian to CentOS`
		`- Have 150 servers to contribute to FOSS projects`
		`- Spread across: Singapore, Hong Kong, Tokyo, Sydney`
		`- Need to handle hosting ourselves`
		`- Can we get that DC space?`
		`- Yes, via RH sponsorship, we can start this`
		`- Additional discussions`
		`- Host Dojos`
		`- Sponsor local community people in those specific countries`
		`- Reasonable interest in that piece`
		`- Sponsorship level?`
		`- Likely they host the details themselves`
		`- We may not need to create a ‘level’`
		`- Support might be 1 to 4 years through their contracts, depending on how much we have installed`
		`- Might be a foot in the door toward further contributions that are equally or more meaningful.`
		`- Value`
		`- What is the value of these machines v. cost to us to host v. canvassing for more hosting?`
		`- 7 July call to thrash out synergy`
		`- Figure out hosting costs`
		`+ * SE Asia operations invests 5 to 7 mil in corporate social responsibility, including into technology`
		`+ * Hosting contests, giving away laptops, etc.`
		`+ * Want to spend on FLOSS projects`
		`+ * Moving dev environment from Debian to CentOS`
		`+ * Have 150 servers to contribute to FOSS projects`
		`+ * Spread across: Singapore, Hong Kong, Tokyo, Sydney`
		`+ * Need to handle hosting ourselves`
		`+ * Can we get that DC space?`
		`+ * Yes, via RH sponsorship, we can start this`
		`+`
		`+ * Additional discussions`
		`+ * Host Dojos`
		`+ * Sponsor local community people in those specific countries`
		`+ * Reasonable interest in that piece`
		`+ * Sponsorship level?`
		`+ * Likely they host the details themselves`
		`+ * We may not need to create a ‘level’`
		`+ * Support might be 1 to 4 years through their contracts, depending on how much we have installed`
		`+ * Might be a foot in the door toward further contributions that are equally or more meaningful.`
		`+ * Value`
		`+ * What is the value of these machines v. cost to us to host v. canvassing for more hosting?`
		`+ * July call to thrash out synergy`
		`+`
		`+ * Figure out hosting costs`

meetings/2016/2016-07-20.md

file modified

+59 -57

		`@@ -22,72 +22,74 @@`


		`## RH Summit report back`
		`- SIG potentials`
		`- Zimbra, Kollab, etc. with Docker help?`
		`- Karsten`
		`- Similar conversations as the past, just different ratios`
		`+ * SIG potentials`
		`+ * Zimbra, Kollab, etc. with Docker help?`
		`+ * Karsten`
		`+ * Similar conversations as the past, just different ratios`


		`- KB`
		`- Far fewer explaining, justifying`
		`- People interested in what we are doing, seen as part of the RH equation`
		`- Not much new engagement, certainly in the vendor space`
		`- Great to meet people, but existing relationships`
		`- Board openness`
		`- What does it matter? Cf. other strongly-led communities.`
		`- Publishing of non-private agenda`
		`- Report out to community (public-allowed minutes)`
		`- Public meetings on video (Hangout, Bluejeans published)`
		`- Public meetings on IRC (agenda + open floor)`
		`- Office hours`
		`- KB’s are vendor focused, not community-contributor focused`
		`- Desire for more documentation`
		`- “Why are not doing this? Why is this this way?”`
		`- Attracts people who won’t get on IRC/mail/forums`
		`- Uses direct calls as well`
		`- Current problem is contributor-based`
		`- People not getting there is more than just Linux`
		`- Berkus observation that there is an unactivated CentOS community at DockerCon`
		`- What are we doing that enables people to better understand what we’re doing, where we’re going?`
		`- Do people care?`
		`- People don’t want their bosses to know they are interested`
		`- The small people we’re trying to reach don’t attend MeetUps`
		`- People not at Red Hat are not announcing stuff from the project --`
		`- A small % of the potential audience might come along, increase engagement`
		`- Public input meetings v. having to meet people in person …`
		`+ * KB`
		`+ * Far fewer explaining, justifying`
		`+ * People interested in what we are doing, seen as part of the RH equation`
		`+ * Not much new engagement, certainly in the vendor space`
		`+ * Great to meet people, but existing relationships`
		`+ * Board openness`
		`+ * What does it matter? Cf. other strongly-led communities.`
		`+ * Publishing of non-private agenda`
		`+ * Report out to community (public-allowed minutes)`
		`+ * Public meetings on video (Hangout, Bluejeans published)`
		`+ * Public meetings on IRC (agenda + open floor)`
		`+`
		`+ # Office hours`
		`+ * KB’s are vendor focused, not community-contributor focused`
		`+ * Desire for more documentation`
		`+ * “Why are not doing this? Why is this this way?”`
		`+ * Attracts people who won’t get on IRC/mail/forums`
		`+ * Uses direct calls as well`
		`+ * Current problem is contributor-based`
		`+ * People not getting there is more than just Linux`
		`+ * Berkus observation that there is an unactivated CentOS community at DockerCon`
		`+ * What are we doing that enables people to better understand what we’re doing, where we’re going?`
		`+ * Do people care?`
		`+ * People don’t want their bosses to know they are interested`
		`+ * The small people we’re trying to reach don’t attend MeetUps`
		`+ * People not at Red Hat are not announcing stuff from the project --`
		`+ * A small % of the potential audience might come along, increase engagement`
		`+ * Public input meetings v. having to meet people in person …`


		`## Paris Nov`
		`- Have it as an interlock -- have people come talk to us, not a Dojo`
		`- Show the SIG process`
		`+ * Have it as an interlock -- have people come talk to us, not a Dojo`
		`+ * Show the SIG process`
		`+`
		`### Venues`
		`- Zeneca & Enovance office (no strings, middle of town, 40+ people)`
		`- Enovance booked for 9th, 10th Nov`
		`+ * Zeneca & Enovance office (no strings, middle of town, 40+ people)`
		`+ * Enovance booked for 9th, 10th Nov`
		`### Agenda`
		`- Two days of talks in the morning`
		`- Lunch - 12:00 - 13:30`
		`- Then special groups/focus areas within the larger room`
		`- HPC, Web hosting, etc. -- face to face discussions`
		`- Two sessions toward the end (after 3:30)`
		`- 15:30 - 16:30`
		`- 16:30 - 17:30`
		`- Focus areas`
		`- Where are we going to be in each of these focus areas in X years?`
		`- Contributor discussion`
		`- Have people walk away knowing how to participate`
		`- Get other interesting people doing stuff - Cern, etc.`
		`- Lightning sessions for an hour each day`
		`- Increase casualness over the two-days with small group`
		`- Having Leslie give a talk about ecosystem`
		`- Board members also have 15 min in there`
		`- Record everything`
		`- 11th morning for Board meeting`
		`+ * Two days of talks in the morning`
		`+ * Lunch - 12:00 - 13:30`
		`+ * Then special groups/focus areas within the larger room`
		`+ * HPC, Web hosting, etc. -- face to face discussions`
		`+ * Two sessions toward the end (after 3:30)`
		`+ * 15:30 - 16:30`
		`+ * 16:30 - 17:30`
		`+ * Focus areas`
		`+ * Where are we going to be in each of these focus areas in X years?`
		`+ * Contributor discussion`
		`+ * Have people walk away knowing how to participate`
		`+ * Get other interesting people doing stuff - Cern, etc.`
		`+ * Lightning sessions for an hour each day`
		`+ * Increase casualness over the two-days with small group`
		`+ * Having Leslie give a talk about ecosystem`
		`+ * Board members also have 15 min in there`
		`+ * Record everything`
		`+ * 11th morning for Board meeting`
		`### Organization`
		`Want to announce soon`
		`### Attendees`
		`- Will get some of the RH eng folks using the platform`
		`- Folks from the SIGs (Cloud, Storage, etc.)`
		`- People interested in relationship building`
		`- Walking away with content about what we do with CentOS Linux`
		`+ * Will get some of the RH eng folks using the platform`
		`+ * Folks from the SIGs (Cloud, Storage, etc.)`
		`+ * People interested in relationship building`
		`+ * Walking away with content about what we do with CentOS Linux`

meetings/2016/2016-11-11.md

file modified

+77 -72

		`@@ -16,90 +16,95 @@`

		`### Budget`
		`#### Do we want to have the Board manage part of the budget from OSAS/RH?`
		`- Yes, on a year-over-year evolution of how things are managed.`
		`- It’s RH money run on behalf of ...`
		`+ * Yes, on a year-over-year evolution of how things are managed.`
		`+ * It’s RH money run on behalf of ...`
		`#### What do we want to make public?`
		`- Spending for community travel`
		`- Swag & support provided out to community events directly`
		`- Constraints on paying people back`
		`- First year -- PayPal only, receipts require`
		`- Budget limit per number of people, e.g. $150 for 50 people, etc.`
		`- SIGs`
		`- Community SIG leads …`
		`- Cover up to $X of travel`
		`- May cover some of RH expenses …`
		`- Talk to management`
		`- Cover up to $X of travel`
		`- What is the definition of community in this context?`
		`- Contributors from a vendor are still a community, but their employer should see the value of sending that person.`
		`- Contributors from a project sponsored/run by a foundation should be able to find a way of sending a person.`
		`- Contributors on own time & dime, should find a way to sponsor and support from project as much as possible.`
		`+ * Spending for community travel`
		`+ * Swag & support provided out to community events directly`
		`+ * Constraints on paying people back`
		`+ * First year -- PayPal only, receipts require`
		`+ * Budget limit per number of people, e.g. $150 for 50 people, etc.`
		`+ * SIGs`
		`+ * Community SIG leads …`
		`+ * Cover up to $X of travel`
		`+ * May cover some of RH expenses …`
		`+ * Talk to management`
		`+ * Cover up to $X of travel`
		`+ * What is the definition of community in this context?`
		`+ * Contributors from a vendor are still a community, but their employer should see the value of sending that person.`
		`+ * Contributors from a project sponsored/run by a foundation should be able to find a way of sending a person.`
		`+ * Contributors on own time & dime, should find a way to sponsor and support from project as much as possible.`
		`+`
		`#### Process`
		`- Need a write-up.`
		`- Three people with at least one Board member to oversee budget management, can do in Year One.`
		`- Dollar amount to take to the Board for approval.`
		`- Spending for all vendors coming in managed by the finance committee.`
		`- Follows the same process.`
		`- Year one - all run by Board for initial trial`
		`- All should have a title in the project based on an existing chain of trust.`
		`- Year two - look for people interested in helping`
		`+ * Need a write-up.`
		`+ * Three people with at least one Board member to oversee budget management, can do in Year One.`
		`+ * Dollar amount to take to the Board for approval.`
		`+ * Spending for all vendors coming in managed by the finance committee.`
		`+ * Follows the same process.`
		`+ * Year one - all run by Board for initial trial`
		`+ * All should have a title in the project based on an existing chain of trust.`
		`+ * Year two - look for people interested in helping`
		`+`
		`#### Getting outside funding`
		`- Need a relationship with an open source program office.`
		`- Run it on behalf of -- they spend at our direction.`
		`- No pay to play … need to trust the community as to what we want to spend.`
		`- Build trust in initial year …`
		`- Community fund …`
		`- E.g. CPanel wants to give $10K to sponsor people to their conference.`
		`- Use the same process for decisions as for spending direct money.`
		`- Transparency of multiple supporters shows diversity.`
		`+ * Need a relationship with an open source program office.`
		`+ * Run it on behalf of -- they spend at our direction.`
		`+ * No pay to play … need to trust the community as to what we want to spend.`
		`+ * Build trust in initial year …`
		`+ * Community fund …`
		`+ * E.g. CPanel wants to give $10K to sponsor people to their conference.`
		`+ * Use the same process for decisions as for spending direct money.`
		`+ * Transparency of multiple supporters shows diversity.`
		`#### Equipment budget`
		`- Solve problems the Board identifies`
		`- E.g. signing for SIGs`
		`- Strategic and tactical`
		`- Oversight of the Infra Team …`
		`+ * Solve problems the Board identifies`
		`+ * E.g. signing for SIGs`
		`+ * Strategic and tactical`
		`+ * Oversight of the Infra Team …`


		`- Putting an annual plan together`
		`- Keep a 10% slush to cover all of above`
		`+ * Putting an annual plan together`
		`+ * Keep a 10% slush to cover all of above`


		`#### Credit Suisse`
		`- Sponsoring millions in EOL hardware for suitable charities and non-profits`
		`- Sep 2017 is first set of kit coming available`
		`- Get CentOS running on the laptops given away`
		`- How should CentOS Project be involved?`
		`- Can we use any of that hardware?`
		`+ * Sponsoring millions in EOL hardware for suitable charities and non-profits`
		`+ * Sep 2017 is first set of kit coming available`
		`+ * Get CentOS running on the laptops given away`
		`+ * How should CentOS Project be involved?`
		`+ * Can we use any of that hardware?`
		`#### Actions`
		`- Full process write-up.`
		`- Define what community means in this context.`
		`- Process to be public.`
		`- By 1 March.`
		`- Pick the finance committee.`
		`+ * Full process write-up.`
		`+ * Define what community means in this context.`
		`+ * Process to be public.`
		`+ * By 1 March.`
		`+ * Pick the finance committee.`
		`+`
		`### Advisory capacity (Board)`
		`- Getting advice from:`
		`- Representative of each Team about running the Project.`
		`- From a specific user / audience?`
		`- Who are using CentOS, maybe we can help make things better for them, then we get a voice into that community.`
		`- Senior enough to have influence in that group and able to represent.`
		`- What can they do?`
		`- Come from existing contributors`
		`- Provide wider perspective`
		`- What does it mean to be on the Advisory Board?`
		`- Provide advice to the executive leadership`
		`- Examples`
		`- Linux Foundation groups have an exec board, then a technical committee and community committee to advise.`
		`- Proposal:`
		`- Pick two areas, e.g.:`
		`- VoIP`
		`- High Energy Physics`
		`- Identify four people in each area`
		`- Arrange a monthly communication channel with those people and an identified CentOS person, with Board members involved.`
		`- Ask Leslie Hawthorn to facilitate and manage the process.`
		`- Each Board member identifies two areas of personal interest`
		`- Two Board members research the areas to find people to be recommended`
		`- Advisory Board is not a for-life thing, some privilege to be there`
		`- Articulate the process publicly`
		`+ * Getting advice from:`
		`+ * Representative of each Team about running the Project.`
		`+ * From a specific user / audience?`
		`+ * Who are using CentOS, maybe we can help make things better for them, then we get a voice into that community.`
		`+ * Senior enough to have influence in that group and able to represent.`
		`+ * What can they do?`
		`+ * Come from existing contributors`
		`+ * Provide wider perspective`
		`+ * What does it mean to be on the Advisory Board?`
		`+ * Provide advice to the executive leadership`
		`+ * Examples`
		`+ * Linux Foundation groups have an exec board, then a technical committee and community committee to advise.`
		`+ * Proposal:`
		`+ * Pick two areas, e.g.:`
		`+ * VoIP`
		`+ * High Energy Physics`
		`+ * Identify four people in each area`
		`+ * Arrange a monthly communication channel with those people and an identified CentOS person, with Board members involved.`
		`+ * Ask Leslie Hawthorn to facilitate and manage the process.`
		`+ * Each Board member identifies two areas of personal interest`
		`+ * Two Board members research the areas to find people to be recommended`
		`+ * Advisory Board is not a for-life thing, some privilege to be there`
		`+ * Articulate the process publicly`
		`+`
		`### Metrics for SIGs`
		`+`
		`### Infra SIG & Fabian as Chair`