16:20:21 #startmeeting 16:20:21 Meeting started Thu Jan 23 16:20:21 2014 UTC. The chair is quaid. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:20:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:20:53 #info around Java jars, all that matters is redistributability -- if you want to maintain N jars for your users, that's up to you 16:21:45 #idea branding forum to discuss and resolve, cf. fedora-legal list 16:22:09 #action quaid to talk with fontana about branding forum 16:22:20 anyone else who wants to help keep notes from the meeting, go ahead 16:22:31 I'm not sure where the logs write to yet ... 16:23:00 You'll get a URL when you end the meeting. 16:23:17 Several of them, in fact. 16:23:27 quaid: you'll need to add whoever wants to add notes to #chair 16:23:50 right, the last one I saw from output didn't show the full URL just the local path, not sure what host it's on in other words 16:24:12 goozbach: I think anyone can do #idea and #info, only #agreed and #topic and a few others are saved to chair iirc 16:25:12 we ( Bahhumbug ) will be improving centbot in the coming days, so there should be some additional improvements 16:25:20 Someone needs to mute. 16:25:27 There definately is a call for something around rebrandability/interoperability SIG 16:26:02 Evolution: I've got a patch for meetbot which sends email to a list when finished 16:26:05 if you're interested 16:26:18 #info breaking out CLoud Infra and Instance as different SIGs 16:26:55 goozbach: that sounds great, my least favorite part of it is having to construct that email at the end :) 16:27:04 does the cloud instance sig exist yet? 16:27:12 mburned: yes 16:27:12 #info yes, oVirt is distributed via RPMs 16:27:13 Yes RDO uses either packstack or foreman as separate installers (puppet underneath) 16:27:14 * mburned probably needs to pay attention to that too 16:27:27 http://wiki.centos.org/SpecialInterestGroup/CloudInstance 16:27:38 kbsingh: thanks 16:27:40 #info ROD users either packstack or foreman as separate installers (puppet underneath) 16:28:45 ok, so then for the most part, people just want content installed and then configured later 16:29:28 that lends itself to these SIGs just being repos and no changes to anaconda or isos 16:29:46 hughesjr, I concur 16:30:21 that makes the delivery system much easier if we can get away with it 16:30:25 yea 16:30:36 i might argue that adding additional repos and/or pre-defined package sets might be useful 16:30:36 but that would need to fit into the overall scope 16:30:41 And then variants - liveCDs, perhaps - of preconfigured systems, like the RDO one. 16:30:42 goozbach: yes please, or send it off as a pull request on github 16:31:18 for the voip sig (at least for FreePBX) we want an easier way to rebrand/re-relase isos/anaconda 16:31:37 DrBacchus: right 16:32:09 I think the hardest part of getting a custom "installer" is the lack of documentation/tools on how to create a new spin 16:32:23 goozbach: i disagree 16:32:47 goozbach: Any information you can provide me regarding that patch would be welcome. 16:33:38 ke4qqq: another trick of having your bits in a central yum repo is that, if Foo is in git.centos.org, Foo can be called CentOS - this resolves the question that gregdek had earlier, right? 16:33:54 kbsingh: ok well the "how" isn't too bad it's the "what" needs to changed to comply with trademark issues 16:34:07 ke4qqq: we're looking at a future leg of the community build system that is Coprs-like - either user Coprs or build it in to Koji, for example 16:34:13 Bahhumbug, Evolution I'll have the patch up on github shortly 16:34:25 goozbach: Thank you. 16:34:47 goozbach: yes. thank you. the more work I can pile on Bahhumbug the better 16:34:48 :-P 16:34:59 * Bahhumbug hides 16:35:14 ke4qqq: meaning, we can lower the barrier to doing scratch builds from accepted source, making those repos available, etc. 16:39:46 yeah, folks are already doing all this ship and support bundled libs, not going to be any harder to do in CentOS 16:41:35 Bahhumbug: Evolution the code as-is is here: https://github.com/gooseproject/meetbot/blob/master/ircmeeting/meeting.py 16:41:50 don't have a good pull request as it's spread across three different commits 16:42:12 and I don't have time to re-do it as proper branch/and --squash 16:44:46 Koji supports building with Maven actually 16:44:57 though the feature is not used the the Fedora instance 16:45:47 goozbach: Thank you. 16:46:09 I missed that 16:46:12 what is the common thing therre? 16:46:23 #chair Evolution 16:46:23 Current chairs: Evolution quaid 16:47:00 what was the question KB just got +1 all around for? 16:47:02 we'd (FreePBX) like the that pushbutton iso dealio too 16:47:03 something about live CD? 16:47:06 ah 16:47:24 #agreed worth working on a pushbutton ISO tool as part of the CentOS Project 16:48:48 koji also supports building livecds and virt images 16:49:04 #idea have upstream merit be the basis for who gets commit access, rather than CentOS having to track it 16:49:13 mikem23: well then set it up :D 16:50:51 #idea within CentOS Project tools, have it be possible for someone in the SIG to get tired of greenlighting patches from a known good person, so proposes that person to the SIG for commit access directly -- this would happen outside of the upstream's own contributor growth pathway 16:50:59 jzb: is the above fair? 16:51:08 lets get some authentication in place, so that we can do much of this. 16:51:15 #chair jzb ke4qqq mikem23 samkottler 16:51:15 Current chairs: Evolution jzb ke4qqq mikem23 quaid samkottler 16:51:17 quite a bit of what we're dealing with depends on auth. 16:51:20 quaid: yes 16:51:24 #chair mburned 16:51:24 Current chairs: Evolution jzb ke4qqq mburned mikem23 quaid samkottler 16:51:44 the livecd and image from git stuff already works, so we dont need to block on other stuff. its a simple low hanging fruit thing that we can use to setup a relationship with 16:52:13 #info the livecd and image from git stuff already works, so we dont need to block on other stuff. its a simple low hanging fruit thing that we can use to setup a relationship with 16:53:08 ke4qqq: jzb I think we don't have consensus on how to handle merit and commit access to git.centos.org, I suspect it will be a blend of those two ideas; let's continue that discussion in The Usual Places 16:53:41 quaid: might be something to handle organically? 16:53:55 quaid: as it happens, rather than trying to put all the ideas in place day one? 16:53:58 (day one-ish) 16:54:05 #idea Seed a few committers to git.centos.org from each upstream, add new commiters as per $formula_to_be_determined but which could be a combination of merit-within-CentOS and merit-within-$upstream 16:54:24 jzb: +1 sure, i.e., no-new-thread-needed :) 16:54:41 #idea handle organically, don't sweat 16:54:55 #agreed CentOS is using the meritocracy spotlight, somehow :) 16:55:25 <-- doing anaconda "stuff" now 16:56:12 sounds like an episode of "Dirty Jobs" 16:56:55 :) 16:57:59 quaid, kbsingh is there any thought to creating SIG-specific mailing lists? 16:58:16 jzb: I think we were going to start on devel and split if needd 16:58:21 jzb: As I understood it, it'll be on centos-devel until it gets too noisy. 16:58:24 it's been a rather quiet list 16:58:33 kbsingh: can I help you with getting your notes in to this meetbot instance now? 16:58:36 quaid: it is a dirty job 16:59:02 DrBacchus: yeah, I refer to that as "standard operating procedure" - wait until it's annoying, then split :) 16:59:05 jzb: yes, once the SIG needs it and there is traffic that is SIG specific, lets mailing list it ( eg. CentOS-Virt is a list ) 17:00:43 kbsingh: gotcha 17:03:33 kbsingh: do you have any notes for the meeting before I close it? 17:03:49 quaid: just that i will write up notes from the call, and propose 17:10:54 kbsingh: OK 17:10:58 closing the meeting in a moment 17:13:15 quaid: ta 17:17:32 #endmeeting