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

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

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

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

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

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

+ * 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)

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

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

+ * Carl: provide link to ASF publicity policy/rules

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

+ * Carl: next iteration of versioning document

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

+ 

+ * KB: Lyon is sold out

+ * Karsten: what is happening with Denver?

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

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

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

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

+ * write up what a process might be ( Karsten )

+ * workout how budgets work and how we might do allocations

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

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

+ 

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

+ 

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

+ 

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

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

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

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

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

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