17:01:55 #startmeeting Council (2015-06-15) 17:01:55 Meeting started Mon Jun 15 17:01:55 2015 UTC. The chair is mattdm. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:55 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:02:02 #meetingname council 17:02:02 The meeting name has been set to 'council' 17:02:04 #chair mattdm jreznik jwb cwickert rdieter langdon sgallagh decause 17:02:04 Current chairs: cwickert decause jreznik jwb langdon mattdm rdieter sgallagh 17:02:11 #topic Open Floor 17:02:19 mattdm, you said the meeting would be in #fedora-council in the email... 17:02:19 Today is an informal open floor meeting 17:02:26 urrghh. 17:02:32 hello 17:02:33 i didn't have enough coffee at that point 17:02:36 ha 17:02:42 .hello 17:02:42 langdon: (hello ) -- Alias for "hellomynameis $1". 17:02:49 .hello decause 17:02:50 .hello langdon 17:02:50 decause: decause 'None' 17:02:53 langdon: langdon 'Langdon White' 17:03:09 So, this is our agendaless town-hall week 17:03:12 .hello sgallagh 17:03:13 sgallagh: sgallagh 'Stephen Gallagher' 17:03:21 .hello ankursinha 17:03:22 FranciscoD: ankursinha 'Ankur Sinha' 17:03:26 just sitting in to see what's going on :) 17:03:52 hi 17:03:54 So, we can either all start talking (which is fine) or we can call for anything specific anyone wants to go through and cover it that way 17:04:11 Elections: we have one open seat and one nominee - makes no sense IMO to continue with the elections. 17:04:28 jkurik: --- and nomination period is closed, right? 17:04:34 yes 17:04:44 there used to be a minimum number of required candidates, but I think this was body specific? 17:05:07 and if there weren't enough candidates, the "charters" had clauses on how this was to be handled 17:05:12 We definitely don't have that in the council charter 17:05:31 A minimum number of candidates are necessary in order to hold an election. This will be the number of open seats + 25%. 17:05:34 https://fedoraproject.org/wiki/FESCo_election_policy 17:05:39 that's fesco, not council 17:05:42 yeah 17:05:43 fesco ^ 17:05:46 which means we really don't need to run an election 17:06:46 yeah, I'm good with that 17:07:00 congrats langdon 17:07:00 .hello bowlofeggs 17:07:01 bowlofeggs: Sorry, but you don't exist 17:07:02 than 17:07:03 * jkurik congratulates langdon to the chair in Council 17:07:05 oh man! 17:07:21 if we had _no_ candidates, then, fine. Let's just announce "number of candidates = number of seats, done" 17:07:41 LOL!! THANKS eveah so much! 17:07:48 langdon: nice campaign :P 17:07:51 #info langdon back on the council as his candidacy is unopposed 17:08:03 * langdon thinks that means he doesn't have to do the interview qs!! 17:08:04 * mattdm edits wiki 17:08:57 I was wondering if the council had any ideas on marketing the fedora products? 17:09:09 langdon: congratuations you're on the hook through f24 now :) 17:09:22 as in, the PRD refresh is somewhere around the corner - should the WGs also think a little about how they want to market their products? 17:09:47 at the moment, there's absolutely nothing - no flyers, no posters, to give out at events. 17:09:56 * langdon thought f23 was the last one, a la windows... 17:10:23 (especially product specific stuff) 17:10:28 FranciscoD: Yes. That should be part of the PRD to some degree, and then that should give guidance to marketing and ambassadors 17:10:42 That'd help, yes 17:11:02 At the moment, I was working on flyers, but without input from the WGs, it's a little difficult 17:11:02 Sounds like you're primarily concerned with what I guess is called "marketing collatoral" 17:11:07 FranciscoD++ 17:11:08 mattdm: Karma for ankursinha changed to 5: https://badges.fedoraproject.org/tags/cookie/any 17:11:12 yes thanks for working on that! 17:11:16 mattdm: well, anything that ambassadors can give out really 17:11:29 it's kinda sucky to have a booth, but nothing to give out :( 17:11:36 https://fedoraproject.org/wiki/Marketing/For_Ambassadors -> all the stuff here is pre-fedora.next 17:11:37 marketing collatoral = fancy word for "stuff to give out" :) 17:11:46 yeah :) 17:12:06 this is where we need the FOSCo group. 17:12:14 decause, any notes on that? 17:12:54 * decause starts typing 17:14:08 * mattdm hmmms jeopardy theme 17:14:27 * langdon impressed that decause knows in advance that he has a long message to write 17:14:43 FOSCo is an ongoing discussion. There are a few differing models that havne't been settled on yet. I think the important thing on this would be to not block on the organizational action, and get the collateral langauge decided on/approved by Fedora Marketing 17:15:08 decause: Can you take point on making sure that happens? 17:15:16 * mattdm readies bus-shoving 17:15:38 * decause puts on bus-resistant suit 17:15:44 * rdieter waves, sorry I'm late 17:16:21 #action decause to coordinate marketing collatoral for Fedora Editions for F23 (and ideally sooner, since currently ambassadors don't have anything to give out) 17:16:42 I can help with that. I'm happy to work on flyers and things. 17:16:47 FranciscoD: great 17:16:53 #info FranciscoD to help 17:16:56 cool 17:17:07 what does "collateral language" mean/ 17:17:26 FranciscoD: let's set a meeting with Marketing (croberts?) in the very near future to figure out how this stuff has been historically decided, so we can figure out what the process will look like in a post-FOSCo world 17:17:36 jwb: is marketing jargon for "fliers and brochures and media and other artifacts" 17:17:50 jwb: language that goes onto fliers/brochures 17:17:57 decause: sounds good - I've mailed the ML already, folks should be aware of flyers and things 17:18:04 https://ankursinha.fedorapeople.org/fedora-flyer-workstation/fedora-flyer-workstation-notumble.pdf -> stuff in there 17:18:05 so that has nothing to do with FOSCo then 17:18:08 FranciscoD: which list? 17:18:15 decause: the marketing ML 17:18:36 which is fine, but mattdm asked for an update on FOSCo 17:18:36 jwb: we can't block on FOSCo if we need materials now/yesterday because FOSCo doesn't even really exist yet 17:18:49 right. which is why mattdm asked for an update 17:19:39 jwb: I'm saying that we we need materials now, and if we want until we agree on what FOSCo is, then we won't get the materials in a reasonable amount of time 17:19:48 s/want/wait/ 17:20:25 yes, i'm not disagreeing with that. i'm asking for an actual update on FOSCo instead of a handy-wavy "don't wait" 17:20:37 sure, don't wait. now tell us about FOSCo 17:21:05 jwb: There are at least 2 proposals 17:21:19 one was put forward by cwickert 17:21:32 and one put forward by me 17:21:55 What's the plan for reconciliation of those two proposals? 17:22:00 or selection between? 17:22:02 I proposed that FOSCo be narrowly defined as a budgetary approval body, to help replace FAMSco, which decided not to run elections 17:23:58 decause: how was that received? much feedback yet? 17:24:01 mattdm: I've been trying to allow for discussion, but not much is happning on the lists 17:24:19 k 17:24:26 I think it might be time to kick it again. 17:24:30 rdieter: I haven't gotten any -1 or 0 yet, but neither has the previous proposals 17:25:06 mattdm: agreed 17:25:14 decause: will fosco also ensure that the various teams - design/mktg/ambassadors communicate with each other and so on? 17:25:17 I think this particular marketing coordination question, covering ambassadors, product wgs, and marketing is a perfect example of something $whatevergroup should cover 17:25:33 (I seem to recall some discussion over the functions/role of fosco sometime back) 17:25:50 FranciscoD ideally not so much "ensure" but "be the place for that to happen naturally" 17:25:57 ++ 17:26:22 well, as long as it's more than what we have now - pretty minimal 17:26:54 I'm beginning to wonder if the only way to get feedback is to just start 'doing stuff', and wait for cheers or cries of despair 17:27:06 rdieter++ 17:27:17 That is _generally the case_ :) 17:27:17 or (continued) crickets 17:27:26 crickets = assent 17:27:33 yay crickets 17:27:53 I think the composition of fosco was another thing that was under discussion - can't really move forward until that is sorted out, can it? 17:28:06 (composition = who will be part of fosco) 17:28:31 my main feedback for the fosco=budget proposal is that I don't think it's needed ... council can cover the top-level budget, and regions can continue to handle regional budgets 17:28:35 FranciscoD: I'm saying that if there are community loops that need moving forward, we need to go forward, and not block on FOSCo, which needs a thougtful long-term treatment 17:28:45 decause++ 17:29:30 mattdm: I liked that approach as well, and at the last FAMSco meeting, there was no -1 on that either 17:29:36 maybe FOSCo is unnecessary entirely 17:30:38 well, *something* needs to replace famsco, if famsco indeed is going away someday 17:30:46 otherwise, jwb++ 17:30:46 rdieter: Karma for jwboyer changed to 7: https://badges.fedoraproject.org/tags/cookie/any 17:31:00 I was sort of looking for something that will be a place where different teams can communicate, as mattdm said. i thought that's what fosco could do 17:31:22 is it? i mean, we proposed an alternative. nobody jumped no it. 17:31:45 So the alternative, I guess, is: we do that kind of coordination _here_ 17:31:53 and while i agree FOSCo could help communication, it certainly won't if nobody thinks it should exist or wants to be part of it 17:32:19 ++ 17:32:20 jwb right. theoretical structures only get us so far :) 17:33:13 If not fosco, some sort of "system" that enables teams to communicate would be sufficient. I say "system" because I have no clue what this could be at the moment. 17:33:24 personally, my gut reaction is against the addition of some new group/body. I'm in favor of -famsco, +fosco , only if we're sure if that makes things better 17:33:26 Could just be another app even, but that needs looking into. 17:33:37 So, basically, that approach would be: put that sort of thing on council agenda, bring to council-discuss. 17:34:01 FranciscoD, magic tools won't help. people have to WANT to communication and collaborate 17:34:02 FranciscoD: http://decausemaker.org/posts/proposal-commops-for-fedora.html 17:34:17 Here is what I would propose this "thing" would look like 17:34:19 i've not seen the overwhelming desire for the two major sides to meet and discuss here 17:34:19 If that starts being an overwhelming burden, that's actually _good_, because that'll naturally be a group that could be spun off 17:34:29 jwb: yes, but at the moment, we have no tools, magic is a long way off 17:34:43 we have email. we have irc. nobody is using either 17:34:57 jwb: you mean for the council? 17:34:59 Hubs is gaining ground as well, as a natural place ot start hanging the fruits of this activity of coordinating community 17:35:06 both e-mail and irc are seen more as intra team talk 17:35:06 well note that FranciscoD did bring this here :) 17:35:18 hardly any cross talk between teams happens 17:35:32 FranciscoD, that is because nobody is even trying. 17:36:06 seriously, if you cannot be bothered to send an email to a different list, i seriously doubt having some other tool is going to make you all of a sudden want to do anything even similar to that 17:36:20 jwb: I've sent mails about flyers to mktg + design + 3 wg MLs 17:36:31 * mattdm notes mails from FranciscoD on many different mailing lists 17:36:36 so. instead of saying "hey we need to communicate more", let's approach this differently. because it's too broad 17:36:57 * mattdm listening.... 17:37:07 FranciscoD, indeed you have and it's welcome. exactly that is what we need perhaps, instad of a distraction f creating a new committee or tool 17:37:22 because with those, people will sit on their thumbs and wait 17:38:14 so. if we need WG input for marketing flyers, and FranciscoD sends an email and gets 0 replies, that's a failure of the WG. FESCo needs to step in. if FESCo doesn't, the council needs to educate both 17:39:05 and while this may sound like "beatings will continue until morale improves", it's not really that. it's an opportunity for the council to remind people about why we need to work as a collective whole. 17:40:12 So, step one here, have council gently remind fesco to remind wgs to reply to those messages? 17:40:24 in this case, yes 17:40:43 and i'd be happy to take that message to the WGs directly 17:40:53 jwb++ 17:40:56 awesome. please do 17:40:56 or that thw WGs need to have some sort of marketing plan which they'll communicate to marketing and so on 17:41:21 #info jwb to "gently encourage" WGs to help with marketing messaging 17:41:57 Docs team can probably help turn technical notes from wgs into good copy, too 17:45:03 On the beatings will continue front :), the council does have a basic stick here. This kind of communication is expected of the Official Fedora Edition wgs -- the added responsibility is the flip side to having added prominence in the project 17:45:18 kinda. 17:45:42 i mean, i agree, but the editions are actually under the purview of FESCo, not the council 17:45:46 maybe we should fix that 17:46:11 jwb: We did initially have them have a dual approval 17:47:06 mattdm, you ahve yourself to blame for this, since you and sgallagh created them under FESCo first, then asked for Board approval (not council) 17:47:11 I think the technical side is under FESCo and should be, but things like the trademark and alignment with overall strategy are council (were board) level. 17:47:13 then i blew up the Board and here we are 17:47:26 good job, us! 17:47:58 our reporting structure matches most of the code in our distro. very spaghetti 17:48:04 jwb lol 17:48:16 ... 17:48:22 okay, so, yeah. Do we have some immediate action items here? 17:48:41 decause and FranciscoD are going to coordinate further on marketing collatoral 17:48:46 On another related note: some of the WGs PRD updates are available; I hope folks are reviewing them 17:48:52 jwb is going to work that same thing from FESCo side 17:48:55 ++ 17:48:56 mattdm: check 17:49:15 sgallagh do you have links for the minutes? 17:49:31 #link https://fedoraproject.org/w/index.php?title=User%3ASgallagh%2FServer_PRD_Draft&diff=415122&oldid=415115 17:49:37 decause: I'm looking at commops, just not discussing to avoid derailing the current discussion :) 17:49:39 #link https://fedoraproject.org/w/index.php?title=Workstation%2FWorkstation_PRD&action=historysubmit&diff=415199&oldid=398332 17:49:55 FranciscoD: nod nod 17:50:06 I should also note that the Cloud WG missed the June 12th deadline. 17:51:36 I'll chase that down - discussion happened, but I don't think it got followed through on 17:51:43 thanks roshi! 17:51:49 roshi++ 17:51:50 #action roshi to chase down cloud wg prd 17:52:27 np - sorry we missed the deadline 17:52:39 sgallagh: what's the next step? referring up to previous conversation, should these have council approval for any strategic changes? 17:53:22 mattdm: Right, the point of the refresh is to have the current Council re-read them and assert that they agree or disagree with Fedora's wider goals. 17:54:09 Which we need to assert at next week's meeting, because after that, it's too late for System Wide Changes. 17:54:33 sgallagh: k do we want to use ticket 27 for that or file a new one? 17:54:37 https://fedorahosted.org/council/ticket/27 17:55:03 mattdm: Might be sensible for us to file a separate ticket for each review, actually 17:55:16 so if I have the cloud PRD done and ready by this time next week, we'll be good? 17:55:16 #action sgallagh to file separate tickets for each prd review 17:55:18 :) 17:55:24 I walked right into that one 17:55:29 sgallagh++ 17:55:41 roshi: Please have it done within the next couple days so people have time to comment 17:55:46 roshi: ideally before, so that we can review before the meeting 17:55:51 You really don't want to have the Council say "no" on Monday. 17:56:35 sgtm, just trying to get a feel for what's wanted/expected 17:56:46 okay, so, we're approaching the hour. 17:56:52 roshi: Mainly, if anything controversial comes up, you will want a little time to argue for it. 17:57:06 anyone else what to get anything in in the next three minutes? 17:57:17 also, thanks sgallagh :) 17:57:44 sounds good sgallagh - thanks 17:58:47 ending meeting in a minute and change... 18:00:00 #endmeeting