|
 |
ac2dcb |
# Board minutes, 2014-08-27
|
|
|
ac2dcb |
|
|
|
ac2dcb |
## Attendees:
|
|
|
ac2dcb |
|
|
|
ac2dcb |
|
|
|
ac2dcb |
|
|
|
ac2dcb |
|
|
|
ac2dcb |
## Agenda:
|
|
|
ac2dcb |
|
|
|
ac2dcb |
|
|
|
ac2dcb |
|
|
|
ac2dcb |
## Actions/Decisions
|
|
|
ac2dcb |
Decision: Board is OK with giving out some accounts to get things started right away for the Cloud SIG.
|
|
|
ac2dcb |
Consensus is “sounds good” to do a CentOS partner-like summit.
|
|
|
ac2dcb |
Action: Board needs to generate list of 6 projects we want to work with by next meeting, so we can get this moving quickly.
|
|
|
ac2dcb |
|
|
|
ac2dcb |
## Notes:
|
|
|
ac2dcb |
### Statement around provenance of source
|
|
|
ac2dcb |
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.”
|
|
|
ac2dcb |
What is the problem we are trying to solve here? What audience do we want to address?
|
|
|
ac2dcb |
Seems to be a social issue rather than a technical one - technical interaction is going well.
|
|
|
ac2dcb |
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.
|
|
|
ac2dcb |
This could be something as straightforward as Karsten or Carl writing a wiki article (after we write it completely) as a statement ‘from RH’.
|
|
|
ac2dcb |
### Cloud SIG
|
|
|
ac2dcb |
Bootstrap with Euca & RDO, may not be clear if CloudStack has anything to do initially.
|
|
|
ac2dcb |
Draft proposal
|
|
|
ac2dcb |
https://docs.google.com/document/d/18qdScbax5wOdshePhMI0ZpO0JQvNJjMbZBRqWtXHwtA/edit
|
|
|
ac2dcb |
Decision: Board is OK with giving out some accounts to get things started right away for the Cloud SIG.
|
|
|
ac2dcb |
### CI/CD
|
|
|
ac2dcb |
Conversations with vendors, configs in mind, early next week target for decision and make orders.
|
|
|
ac2dcb |
Could borrow some blades until new hardware arrives.
|
|
|
ac2dcb |
Groups most likely to join: MariaDB, RDO, libvirt, qemu, ceph, gluster
|
|
|
ac2dcb |
About a month until this is ready to raise to the Board.
|
|
|
ac2dcb |
15 Sep is a bit tight to launch by.
|
|
|
ac2dcb |
HSS has two Java developers who are working on setting up Jenkins for internal.
|
|
|
ac2dcb |
KB to talk with them next week, see how we can work together.
|
|
|
ac2dcb |
Lower barrier to entry, more willing to run CI that doesn’t get fixed for a long time, not sending a community message.
|
|
|
ac2dcb |
Overlap in that they’ll do nightly, dailies, dev branches, where we might only pick up e.g. stable nightlies.
|
|
|
ac2dcb |
### CentOS (Friends) Summit
|
|
|
ac2dcb |
Around FOSDEM, Friday before.
|
|
|
ac2dcb |
Or if doing Dojo, do the Summit on Thursday or Monday after.
|
|
|
ac2dcb |
Can get a 30 - 45 person setup
|
|
|
ac2dcb |
f2f time, build relationships
|
|
|
ac2dcb |
Seek solutions together
|
|
|
ac2dcb |
Do hackathon work to get things working for people
|
|
|
ac2dcb |
Find 5 or 6 projects, could split the interaction in to 3 hour groups.
|
|
|
ac2dcb |
Need to generate this list soonest
|
|
|
ac2dcb |
Ceph, Gluster are in and good examples.
|
|
|
ac2dcb |
By 10 Sep create a list of who to work with.
|
|
|
ac2dcb |
LinuxCon NA or OSCON are good potential places to attach a next Summit.
|
|
|
ac2dcb |
Consensus is “sounds good” to do a CentOS partner-like summit.
|
|
|
ac2dcb |
Action: Board needs to generate list of 6 projects we want to work with by next meeting, so we can get this moving quickly.
|
|
|
ac2dcb |
### e
|
|
|
ac2dcb |
|