+ # 2014-02-26 Board Meeting!

+ ## Attending

+ * Karanbir Singh

+ * Jim Perrin

+ * Fabian Arrotin

+ * Carl Trieloff

+ * Mike McLean

+ 

+ ## Agenda

+ * Trademark

+ * SIG-focused open meeting

+ * Document sent around

+ * CoreOS

+ 

+ ## Actions

+ * Trademark examples for FAQ.

+ 

+ 

+ 

+ ## Notes

+ ###Trademark

+ Some public discussion is covering our base for us, people are schooling other people on the subject by using the guidelines.

+ We still want to put up some examples and improve the FAQ.

+ Need a process for how to reach out to people in violation of the trademark.

+ Will let people use logo for t-shirts if they are given away.

+ ###Hardware

+ were getting 600gb disks in the new hs23’s ( to fill out existing chassis )

+ were also getting 600gb disks for ibm 2u storage box

+ ###SIG

+ google-hangout(?) please check kit

+ prop for

+ centos-virt

+ centos-cloud

+ another ( maybe voip sig )

+ Desktop ( jim  )

+ hosting sig - not moving too far / too fast.

+ storage sig: they need something to make it worthwhile, cloud sig might deliver something, not much interest from gluster - beyond the emails to centos-devel

+ packaging /extending stuff SIG:

+ ###CoreOS

+ minimal kernel

+ centos-7 derived

+ maybe into an existing SIG or bootstrap a new

+ ###What should be the SIG status be for ‘re-branding’ CentOS

+ 

+ 

+ 

+ # 12 March 2014 Board Meeting

+ 

+ ## Attendees

+ * Mike McLean

+ * Carl Trieloff

+ * Karsten Wade

+ * Johnny Hughes

+ * Karanbir Singh

+ * Fabian Arrotin

+ * Ralph Angenendt

+ 

+ ## Agenda

+ ## building rockets with centos

+ ## trademark

+ ## board meeting time and daylight savings

+ 

+ 

+ ## Actions

+ Work with Richard to fix issues with trademark guidelines

+ 

+ 

+ 

+ 

+ ## Notes

+ Richard: trademark guidelines, as written, are problematic

+ may be unenforceable

+  need fixing

+ how/when should we engage with the community about this?

+ general agreement to keep this quiet until we have an acceptable draft

+ [PRIVATE] atomic: new subscription plans

+ 

+ 

+ ## release naming

+ we don’t support older point releases

+ we shouldn’t use labels like 6.4, just 6 (?)

+ nothing decided

+ suggestion to keep 5 and 6 the way they are and try out the new way with 7 (which isn’t yet decided either)

+ 

+ 

+ # Board minutes 2014-03-26

+ 

+ ## Attendees

+ * Mike

+ * KB

+ * Carl

+ * Karsten

+ * Fabian

+ * Ralphp

+ * Tru

+ * Jim

+ * Johnny

+ 

+ 

+ ## Agenda

+ * Release naming

+ * Export regulations verbage

+ 

+ 

+ 

+ 

+ ## Actions

+ Jim to write up list of actions / content to address export control requirements

+ 

+ 

+ ## Notes

+ ### Naming

+ Jim: need to sell the sanity aspect in light of new sigs

+ Jim: not a fan of cute names

+ Karsten: names are memorable

+ Mike: the names don’t have to be cute

+ Ralph: don’t want the name to be too long. dates are good/practical

+ Carl: need to avoid fragmentation. no names per variants

+ KB: Year and month is enough. It takes days to get content on the mirrors

+ Mike: let’s enumerate the different classes of sigs/variants and think about how naming should work in each case

+ Mike: we want to avoid giving the appearance of EUS-type support

+ Fabian: consider chef/puppet variables

+ could break various puppet modules/etc

+ Karsten: can we provide major/minor number where necessary without using it at top level?

+ Jim/KB: vendor validation

+ Jim: too drastic a change too fast could cause a user revolt

+ KB: just drop the subrelease altogether. E.g. centos-6-atomic

+ Karsten: need to really think about how we will present this to the community

+ folks will point out holes in plan

+ we’ll have an iterative process

+ KB: let’s take the rest of this offline/email

+ ### A wild Johnny appears!

+ ### Export stuff

+ Karsten: the laws are complex, but we need a simple policy

+ Karsten: software contributions imply access to software, which may be prohibited

+ Karsten: we’re not here to take a political stance

+ let’s not let folks force us into taking one

+ people should not be using us to make a political statement

+ Jim: some details about Fedora’s approach

+ KB: a lot of people in Iran use Centos

+ users may be deliberately trying to push the boundaries

+ Carl: we don’t have to be police, just state the facts (in a nice way)

+ Jim: they can always get it from kernel.org

+ Fabian: what / how do we communicate mirror requests

+ needs wording up

+ ToDO: firewall off content from mirror-?.centos.org ( the ones hosted at redhat )

+ desireable to have elsewhere, but not essential 

+ ToDo: add notes to rsync header, mirrorlist node to say content is not acceptable for use in some areas

+ Jim to write up list of actions / content to address export control requirements

+ 

+ # Board minutes 2014-04-09

+ 

+ ## Attendees

+ * Mike

+ * Carl

+ * Karsten

+ * Jim

+ * Fabian

+ * Johnny

+ * Karanbir

+ 

+ 

+ ## Agenda

+ * Linux Foundation Press release

+ * Centos CN forum request

+ 

+ ## Actions

+ Carl: provide link to ASF publicity policy/rules

+ http://apache.org/press/#releases

+ Carl: next iteration of versioning document

+ 

+ ## Notes

+ ### Karsten brings up the Linux Foundation press release

+ KB: why is Stephanie involved?

+ Karsten: why is LF involved?

+ Karsten: Stephanie is simply a help resource we can use

+ KB: LF is not running the virt sig, rh is not running the virt sig

+ Carl: Press release needs to come to the board. Do we even want one?

+ Carl: notes how Apache Foundation handles such things

+ KB: Press release from their end vs. from our end

+ Karsten: none of us are pr experts. it’s good to have help.

+ Jim: just learned about this today. I want to see the release. Doesn’t matter that it’s for summit. Help from Stephanie is fine, but she is not a blocker.

+ Carl: If the release makes any representation about the project, then they need our approval

+ Carl: we should establish a press list and develop some expertise and rules

+ KB: haven’t had a chance to look. only had it for five minutes

+ KB: no need for this to block for weeks

+ Carl: need to formalize how we handle issuing our press releases.

+ through RH?

+ through another company that employs one of us?

+ Jim: can we view/crib the ASF policy?

+ Carl: yes

+ KB: let’s get this particular release handled in the next day for so and try to formalize the process later

+ Chinese language forum request

+ KB: relates previous attempt at a CN language forum

+ no activity

+ KB: Let’s do something more general, rather than specifically target one language

+ folks in Japan are interested, as well as...

+ indonesia

+ malaysia

+ brazil

+ every language group gets <langcode>.centos.org and a mailing list

+ set up a language moderators group

+ document how this process works

+ at least one member needs to: speak english, join moderators list

+ KB: this particular CN request comes from someone who might be problematic

+ may want too much autonomy

+ Mike: wonders if we should use hyperkitty

+ https://fedorahosted.org/hyperkitty/

+ demo: https://lists.stg.fedoraproject.org/archives/

+ KB: who is will to take ownership of delivering this?

+ KB: not it!

+ Perhaps someone in the community?

+ Johnny: I can create mailing lists and stand up forums pretty easily

+ Fabian: phpbb might not be that trivial

+ Fabian: no centralized auth

+ Fabian: we’ll have to retool heavily in the future

+ Carl: should we have a vote?

+ Statement : The board will allow the development of forums, lists, and content in other languages managed on CentOS infra and by the CentOS project open to contribution by all. The project will not delegate the running of CentOS branding infra, forums and such to 3rd parties.

+ ### Vote:

+ * yes: KB, Jim, Karsten,Carl, Fabian, Mike, Johnny

+ Carl review the versioning proposal

+ [see slide deck] -> where ? in google drive ?

+ (attached to “Numbering” thread on board mailing list)

+ (lots of discussion)

+ Johnny/Fabian are concerned that if we find it confusing, then the community will find it even more so and react negatively

+ Carl expresses willingness to spend more time to get it right

+ ### Dojos

+ KB: Lyon is sold out

+ Karsten: what is happening with Denver?

+ 

+ # Board minutes: 2014-05-21

+ 

+ ## Agenda:

+ 

+ c7 : Whats needed

+ numbering

+ problem statement ( Mike .. )

+ potential solution might be to use date stamp

+ 7.XXYY-<tag>

+ xx ⇒ year 2 bits

+ yy => month ( to match RHEL dates )

+ <tag> => potentially something that other variants can use

+ but we might need a default TAG ( Final ?  )

+ Would help if it the default started with an “A” so that it could be iterated after that easily

+ have a rough draft via Jason Brooks ( RH OSAS  Comms person ) by 23rd / 27th

+ altsrc

+ expectations internal to RH already point to people expecting git.centos.org being source upstream

+ feedback from HiPEx Spring was that people who care / are tracking conversations, already also expect git.c.o

+ Can we can push git as primary without breaking FTP per-se?

+ secureboot

+ Clarify the position on access for Red Hat owners / hosted

+ there might be exceptions in the future ( but those would be well defined ) 

+ default policy would be to allow community access as needed

+ Call for a mailing list vote on CERN people position ( if we want them in, and if we want them to run the koji )

+ we might need more board meetings in the coming weeks, make sure that we set expectations with everyone.

+ 

+ 

+ # Board minutes 2014-06-04

+ 

+ ## Agenda

+ 

+ * need to close to get versioning email out from board, assist from Jason

+ * invite for Jason to talk about ftp messaging coming from Red Hat

+ * basic update on where things stand, readiness. 

+ 

+ ## Actions

+ mikem needs access to git.centos.org for pushing altsrc content

+ team needs one-time-for-first-time access to source of 24 to 36 hours in advance of release for internal-only pre-staging.

+ mikem will bring this up in thu internal altsrc meeting

+ Setting up internal host on possibly OSAS lab machines as pre-staging git devel server in 10.x VPN space.

+ Can do a daily sync on #centos-devel when doing public prebuild dress rehearsal.

+ 

+ 

+ 

+ 

+ 

+ ## Notes

+ 

+ Packages that are from EL7 that need to go into EL6. (right?)

+ MikeM has list

+ prepupgrade-assistance, redhat-preupgrade-tool, preupgrade-*

+ These are going to be EL6 packages that only have source in git.centos.org and not in FTP - this means at least some EL6 source is moving to git from FTP.

+ When do we sync to RHN?

+ 

+ 

+ 

+ 

+ # Board minutes 2014-08-14

+ ## Attending:

+ * Ralph

+ * Carl

+ * Mike

+ * Johnny

+ * Jim

+ * KB

+ 

+ 

+ # Agenda:

+ ## SIG Overview and recap 

+ ### Virt SIG

+ * cbs access is now available to them

+ * qemu version convo 

+ * libivrt stable version

+ ### Cloud Instance SIG 

+ * AMI’s are with AWS, waiting QA signoff

+ * vagrant cloud setup

+ * GCE images ETA 10 - 12 days 

+ * docker images in prod

+ * consolidated builders in RDU

+ * Dir structure

+  * workout with tigert

+  * signed json api (?)

+ * ###Storage SIG

+ * glusterfs - test builds done

+ * working on docs

+ * ceph: might offload to gluster guy

+ ###Atomic SIG

+ * builds automation

+ * getting ready to release in a week or so

+ * handover to atomic sig folks longer term

+ * SME Server

+ * deadending, needs action

+ * Voip

+ * patrick working behind the scenes, will get proposal in - already has packages to go for asterisk

+ ### Cloud Infra

+ * kushan das, from EUCA came up today, unsure what he is able to do

+ 

+ ## CI SIG Conversation

+ naming QA SIg or CI SIG

+ jim / ralph /carl / kb / johnny  are ok with CI sIG

+ could it mean CI for the C project or CI oriented spin

+ SIG onboarding process

+ Board has decided that CI is an area of attention and focus, where we can build value for upstreams and users, and we should investigate options around that area for now.

+ ## dojo

+ write up what a process might be ( Karsten )

+ workout how budgets work and how we might do allocations

+ 

+ ## face2face at Dojo Barcelona

+ 

+ # Board minutes, 2014-08-27

+ 

+ ## Attendees:

+ 

+ 

+ 

+ 

+ ## Agenda:

+ 

+ 

+ 

+ ## Actions/Decisions

+ Decision: Board is OK with giving out some accounts to get things started right away for the Cloud SIG.

+ Consensus is “sounds good” to do a CentOS partner-like summit.

+ Action:  Board needs to generate list of 6 projects we want to work with by next meeting, so we can get this moving quickly.

+ 

+ ## Notes:

+ ### Statement around provenance of source

+ Some risk in how we state things, want to make sure we take the right angle so we are positioning the project correctly as “made of RHEL source but not closer to RHEL.”

+ What is the problem we are trying to solve here? What audience do we want to address?

+ Seems to be a social issue rather than a technical one - technical interaction is going well.

+ SL leadership want statements about the provenance of the source, which is something we want to be careful about so we don’t bring up the lack of SRPMs.

+ This could be something as straightforward as Karsten or Carl writing a wiki article (after we write it completely) as a statement ‘from RH’.

+ ### Cloud SIG

+ Bootstrap with Euca & RDO, may not be clear if CloudStack has anything to do initially.

+ Draft proposal

+ https://docs.google.com/document/d/18qdScbax5wOdshePhMI0ZpO0JQvNJjMbZBRqWtXHwtA/edit

+ Decision: Board is OK with giving out some accounts to get things started right away for the Cloud SIG.

+ ### CI/CD

+ Conversations with vendors, configs in mind, early next week target for decision and make orders.

+ Could borrow some blades until new hardware arrives.

+ Groups most likely to join:  MariaDB, RDO, libvirt, qemu, ceph, gluster

+ About a month until this is ready to raise to the Board.

+ 15 Sep is a bit tight to launch by.

+ HSS has two Java developers who are working on setting up Jenkins for internal.

+ KB to talk with them next week, see how we can work together.

+ Lower barrier to entry, more willing to run CI that doesn’t get fixed for a long time, not sending a community message.

+ Overlap in that they’ll do nightly, dailies, dev branches, where we might only pick up e.g. stable nightlies.

+ ### CentOS (Friends) Summit

+ Around FOSDEM, Friday before.

+ Or if doing Dojo, do the Summit on Thursday or Monday after.

+ Can get a 30 - 45 person setup 

+ f2f time, build relationships

+ Seek solutions together

+ Do hackathon work to get things working for people

+ Find 5 or 6 projects, could split the interaction in to 3 hour groups.

+ Need to generate this list soonest

+ Ceph, Gluster are in and good examples.

+ By 10 Sep create a list of who to work with.

+ LinuxCon NA or OSCON are good potential places to attach a next Summit.

+ Consensus is “sounds good” to do a CentOS partner-like summit.

+ Action:  Board needs to generate list of 6 projects we want to work with by next meeting, so we can get this moving quickly.

+ ### e

+ 

+ # Board minutes, 2014-10-28

+ 

+ ## Actions

+ Need to talk with Matt Domsch about MirrorManager 3 features and developments.

+ Work on bootstrapping Chinese community.

+ KB & Karsten still need to speak with Patrick McBride about Azure solution.

+ Board needs to help generate a list of who RH might want to hire.

+ 

+ 

+ 

+ ## Things on our mind:

+ 

+ ### Metrics & Bitergia - for example http://www.ovirt.org/stats/

+ ### Monthly builds - Q&A

+ Script in RDU2 that will build automatically on the 29th for Docker, cloud images, ISOs.

+ Generic cloud, raw cloud, Docker container, Vagrant image, and ISOs

+ Need to get these in the QA harness.

+ Currently need to be tested by hand.

+ ISO has all the updates smashed into base, latest versions of RPMs.

+ No ISO for 5 & 6.

+ Cloud images are yum updated.

+ Docker needs to build a new image, as it would otherwise overlay.

+ Expose tests so others can verify the images; we trust our own tests but you shouldn’t.

+ Reduce good enough to as many automated tests as possible.

+ Live CDs?

+ Heavily promote the idea that ‘yum update’ should be frequent, unless you have a specific reason not to. Run a cloud image that is a snapshot in time.

+ 

+ 

+ ### State of cloud

+ EC2 - Thor Nolen has sorted out a few things, figured out how to get us interfacing with the right set of people inside of Amazon. We are now a proper Amazon partner. CentOS governance is recognized as legal entity by Amazon Legal.

+ Bootstrapping AWS China with Windows & CentOS. How do we get a community in China?

+ Need to make sure EC2 images have Chinese language included.

+ http://gbraad.nl/

+ AliBaba?

+ Existing Chinese translator of CentOS wiki - Timothy Lee

+ CERN

+ Want Juno on EL6.

+ Use this as a reason to open source RDO tools so that CERN can repackage for EL7.

+ Make this a Cloud SIG code asset.

+ Then CERN can help with the code.

+ ### Azure

+ Gallery, cf. Amazon Marketplace.

+ OpenLogic in there

+ Condition of Gallery is that the OS is provided.

+ Updates need an SLA from Azure back to the originator vendror.

+ The Azure needs

+ Open Technology Group, related to Outercurve, has Linux support on Azure.

+ Publish images via an Azure account, can ask for the image to be public. So it’s searchable/findable.

+ Certain accounts can have the flag to publish to Gallery.

+ Support issues goes to a URL e.g. wiki.centos.org/Cloud/Azure. That page spells out how to get support. Need an Azure-specific mailing list.

+ more ref: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-endorsed-distributions/ and http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-create-upload-vhd/

+ Targeted for Nov monthly build.

+ 

+ 

+ 

+ # Board minutes 2014-11-19

+ ## Agenda

+ 

+ 

+ 

+ ## Notes

+ Open NFV - NFV SIG

+ http://wiki.centos.org/SpecialInterestGroup/NFV

+ http://opennfv.org

+ Interested parties for SIGs

+ Telcos

+ VoIP providers

+ Is OpenStack a necessary provider?

+ Current plan is to use OS but it’s possible to use others

+ May see CloudStack included

+ Reference platform discussion ongoing, adjusted according to testing.

+ Key is to use what exists from stable-enough upstream

+ OpenStack Juno, Helium, OpenDaylight, etc.

+ 

+ 

+ # Board minutes 2016-05-18

+ 

+ ## Agenda

+ * Board Secretary idea

+ * SIG reports

+ * centosproject.org

+ * SIG merit promotions

+  * Any ready?

+  * Process?

+ I.e. getting FAS sponsor/admin access for SIG Chairs.

+ 

+ ## 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.

+ ## PaaS SIG

+ 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 …?

+ ### 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

+ ### Virt SIG

+ 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.

+ ### Atomic SIG

+ Happening, going fine

+ Vagrant box downloads ~25K?

+ ### OpTools / Infra Tools SIG

+ 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 …

+ 

+ 

+ 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?

+ 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

+ 

+ # Board minutes 2016-06-15

+ 

+ ## Attendees

+ * Jim Perrin

+ * KB Singh (Chair)

+ * Fabian Arrotin

+ * Johnny Hughes

+ * Karsten Wade (Secretary, meeting #2)

+ * Michael McLean

+ * Ralph Angenendt

+ * Carl Trieloff

+ ## Guests

+ * Richard Megginson (OpsTools SIG)

+ * Matthias Runge (OpsTools SIG)

+ 

+ ## 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

+ ### ## 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

+ ### 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

+ 

+ 

+ 

+ 

+ # Board Minutes 2016-07-20

+ 

+ ## Attendees

+ * Karanbir Singh (chair)

+ * Jim Perrin

+ * Johnny Hughes

+ * Ralph Agnenendt

+ * Karsten Wade (sec’y)

+ * Mike McLean

+ * Tru Huynh

+ ## Regrets:

+ * Fabian Arrotin

+ * Carl Trieloff

+ ## Agenda & notes

+ * SIG proposals

+ * OSAS sysadmins to bring idea of curating Ansible content idea to Config Mgmt SIG

+ * SIG reports

+ * SIGs reporting frequently enough to the devel list, mostly business as usual

+ * SIG Guide

+ * Finish the guide, then go for more feedback

+ * JZB, Berkus, Bowen - have newer-eyes perspective

+ 

+ 

+ ## RH Summit report back

+ 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 …

+ 

+ 

+ ## Paris Nov

+ 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

+ ### 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

+ ### 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

+ 

+ 

+ # Board minutes 2016-11-11

+ 

+ ## Attendees

+ * Jim Perrin

+ * Fabian Arrotin

+ * Johnny Hughes

+ * Mike McLean

+ * Ralph Angenendt

+ * Tru Huynh

+ * Karsten Wade

+ * Karanbir Singh

+ 

+ ##Quorum achieved.

+ 

+ ## Agenda & notes

+ 

+ ### 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 ...

+ #### 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.

+ #### 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

+ #### 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.

+ #### Equipment budget

+ Solve problems the Board identifies

+ E.g. signing for SIGs