14:08:28 #startmeeting design-team 14:08:29 Meeting started Thu Apr 20 14:08:28 2017 UTC. The chair is mizmo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:08:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:08:29 The meeting name has been set to 'design-team' 14:08:29 meetbot.meeting.start -- duffy started meeting "design-team" in #fedora-design 14:08:48 #topic some announcements first 14:08:49 meetbot.meeting.topic.update -- The topic of duffy's "design-team" meeting changed to "some announcements first" in #fedora-design 14:09:03 #action F26 wallpaper improvements 14:09:03 meetbot.meeting.item.action -- duffy noted an action in the "design-team" meeting in #fedora-design: "F26 wallpaper improvements" 14:09:16 I'm not actually sure of the timeline we have for getting F26 wallpaper improvements into the beta 14:09:17 lemme look 14:10:24 Beta freeze is 5-16, so we really want any edits ready to be packaged in the next week or 2 14:10:30 sam08: have you seen our alpha wallpaper? 14:10:35 maybe you'd have ideas for pushing it further :) 14:11:13 yep, i've read something on the ml, not sure which is the final version though 14:11:25 hey sam08 and mizmo 14:11:34 hey mleonova! 14:11:38 sam08: lemme grab you a link 14:11:50 thanks, mizmo 14:11:58 hey mleonova! 14:13:32 sam08: here it is http://imgur.com/a/gc9Zx 14:13:58 i also read something about the default logo overlay clashing with the bg, has that been solved? 14:14:11 sam08: these are the sources - https://duffy.fedorapeople.org/art/f26/ 14:14:25 sam08: i think so, there's a BZ, the logo in f26 is going to be swapped for a dark one 14:15:15 one issue tho - luya put together a time color changing one, which might also cause issues with the color of the logotype 14:15:29 so we might want to tweak the color change ones to make sure they always work with a dark logo 14:16:51 well, i really like this one, i can't remember a light default wp in fedora 14:17:02 yeh i think we've always had dark 14:17:15 they're generally all set in some darker blueish hues 14:17:18 i know there's some minor errors, there's a horizontal line above the treeline somehow 14:17:42 jw, is the 5:4 version still used? 14:18:05 guess it's called normalish 14:18:54 sam08: yep 14:19:30 is it cropped out from this one? 14:20:13 i dont know if we packaged a 5:4 version in alpha, but it would have to be yeh 14:21:45 i can try to expand this either or both on top or bottom, would be a pity cropping that fading trees thing 14:22:17 sam08: that would be great!! 14:22:27 sam08: ill make a ticket for it and assign to you ok? 14:22:36 sure! 14:22:36 can you have something by next weekish? 14:22:43 awesome 14:22:52 #action mizmo to make beta wallpaper ticket, assign to sam08 14:22:52 meetbot.meeting.item.action -- duffy noted an action in the "design-team" meeting in #fedora-design: "mizmo to make beta wallpaper ticket, assign to sam08" 14:23:17 i'll be afk next i'm afraid, so i will try to come up with something during this weekend 14:23:26 #action sam08 to work on iteration of f26 wallpaper for beta (expand for 5:4 version as to not crop treeline), will try this weekend 14:23:26 meetbot.meeting.item.action -- duffy noted an action in the "design-team" meeting in #fedora-design: "sam08 to work on iteration of f26 wallpaper for beta (expand for 5:4 version as to not crop treeline), will try this weekend" 14:23:28 that's fine! 14:23:33 okay other stuff 14:23:45 so we should start ramping up probably on Flock design stuff 14:23:55 Ryan kicked things off with an initial logo and website design 14:24:12 i riffed on the logo a bit, and did a blog post, sec - 14:24:47 oh #info beta freeze 5-16; lets have beta wallpaper ready to package no later than 5-9 14:24:50 er 14:24:54 #info beta freeze 5-16; lets have beta wallpaper ready to package no later than 5-9 14:24:54 meetbot.meeting.item.info -- duffy raised a point of information in the "design-team" meeting in #fedora-design: "beta freeze 5-16; lets have beta wallpaper ready to package no later than 5-9" 14:25:07 #info flock design work kicking off 14:25:07 meetbot.meeting.item.info -- duffy raised a point of information in the "design-team" meeting in #fedora-design: "flock design work kicking off" 14:25:59 http://blog.linuxgrrl.com/2017/04/18/flock-cod-logo-ideas/ 14:26:00 meetbot.meeting.item.link -- duffy linked to more information in the "design-team" meeting in #fedora-design: "http://blog.linuxgrrl.com/2017/04/18/flock-cod-logo-ideas/" 14:26:51 I think F / F inverse is the way we should go 14:27:03 the main difference is the rope 14:27:28 the knot tie is corrected, but some people have complained it's a 'wimpy' knot (i don't know so much about this) 14:27:41 I like the knot on the rope 14:27:42 so maybe we avoid it 14:27:57 i like it too, honestly 14:28:08 so maybe let's say F inverse is how we're going 14:28:10 it's great visually 14:28:16 #info we're going with the F inverse logo 14:28:16 meetbot.meeting.item.info -- duffy raised a point of information in the "design-team" meeting in #fedora-design: "we're going with the F inverse logo" 14:28:20 is this going to be screen printed somewhere? idk, t-shirts, swags 14:28:34 and we can work out treatment on it, change up the colors / etc as needed / as we want 14:28:47 sam08: potentially. we may or may not be doing T-shirts this year. but the design is such it works well one-color 14:29:16 yep, exactly, F would need two separate colors, F inverse just one 14:30:02 yeh agreed :) 14:30:28 #info the logo will work one-color if needed 14:30:28 meetbot.meeting.item.info -- duffy raised a point of information in the "design-team" meeting in #fedora-design: "the logo will work one-color if needed" 14:30:57 so mleonova and i chatted about it this morning - i think we'll want a sticker sheet design 14:31:07 and in aggregate the series of logos looks pretty nice 14:31:15 so one idea would be to make a sticker sheet with all the logo variations on it 14:31:21 yeah, I created this one for myself: https://pagure.io/design/issue/513 14:31:33 maybe make them a little more different from each other, adding in more fonts, design elements (besides the lighthouse) etc 14:31:36 yep! 14:32:00 maybe not all of them, but a few + separate word as flock and cape cod or maybe the lighthouse etc 14:32:10 i got a price quote from sticker giant, we could get 300 sheets at $.69 a sheet and have unlimited cuts per sheet, 5" x 8" size sheet 14:32:55 mleonova: right, sorry, theres too many to have on a sheet that size. the best ones + new variations if needed 14:33:26 so I'd vote A, B , F obviously 14:33:53 J is pretty cool) 14:34:05 maybe come up with 2 more new variations? and have a fedora logo sticker too? make a 6 sticker sheet? 14:34:18 I'll play around with variations, sounds good! 14:34:28 also the background of the sheet doesnt have to be white, the area you peel from can have a design too 14:34:41 neat =) 14:34:43 you could do a beach scene as the background and the stickers are on top of it, something like that 14:34:48 i cant wait to see what you come up with :) 14:34:57 #info mleonova working on a sticker sheet design for flock 14:34:57 meetbot.meeting.item.info -- duffy raised a point of information in the "design-team" meeting in #fedora-design: "mleonova working on a sticker sheet design for flock" 14:35:00 ha, me too ;) 14:36:23 ok the other thing i wanted to point out - i wrote flock-planning list with a list of design tasks, i'm not 100% which ones we're definitely doing this year or not, but we'll eventually want tickets and folks working on them 14:36:45 lemme grab the url 14:37:18 https://lists.fedoraproject.org/archives/list/flock-planning@lists.fedoraproject.org/thread/Z4Y65RQHA5OPCTQQVCGIQZO7GDEUVV2G/ 14:37:19 meetbot.meeting.item.link -- duffy linked to more information in the "design-team" meeting in #fedora-design: "https://lists.fedoraproject.org/archives/list/flock-planning@lists.fedoraproject.org/thread/Z4Y65RQHA5OPCTQQVCGIQZO7GDEUVV2G/" 14:37:53 one change from past years - a number of people noted that the schedule in the flock book was out of date and ryan did an awesome wall calendar paste up that ended up being really useful 14:38:24 so we may not want to include the schedule in the book and instead design a system of generating printable PDFs for cut-out schedule items that could be pasted up (make sense?) 14:38:50 I was voting for keeping the book, but it does make sense, yes 14:39:25 mleonova: oh we'd keep the book, just not have the schedule in it 14:39:31 book is great for carrying around and looking at when internet connection is bad 14:39:47 then I don't see why not keep the schedule 14:39:52 maybe instead of having the schedule in it, we could have an alpha list of the planned talks with checkboxes for people to mark the ones they want to go to and a space to write room number / time? 14:40:08 maybe yes - some sort of planning system 14:40:13 and they could look up the room / time on the wall schedule 14:40:14 yeh 14:40:53 my point was when you are away from the wall and don't have internet, but want to discuss schedule and plan, books are handy 14:40:57 oh man 14:41:02 i just had a random weird idea 14:41:14 what if we had sticker sheets that had talk names on them 14:41:25 and a blank schedule in the book 14:41:34 hah =) that's fun 14:41:41 and people could build their own personal schedule that way 14:41:52 another idea - 14:41:57 huhu 14:42:07 hey gnokii 14:42:13 hi gnokii 14:42:17 instead of having the schedule printed in the book, having a print out done of sched.org the day before and we have it available as an insert 14:42:18 hey gnokii! 14:42:26 he sam08 mizmo 14:42:46 mizmo, 2nd one would certainly be easier to do 14:43:25 yeh the stickers might be too fussy for attendees 14:43:31 the difference tho - 14:43:38 1) build your own schedule - just has the sessions you plan to go to 14:43:53 2) printed schedule day before - has all sessions including the ones you're not going to 14:44:17 maybe do the printed schedule the day before and have stickers people could use to mark the ones they want to go to? lol they can just use a pen tho 14:44:25 * mizmo just likes stickers today 14:44:31 =) 14:44:47 schedule.dingens has this already 14:45:37 gnokii: whats that? 14:46:02 the schedule service we used for flock always has the personal schedule feature already 14:46:15 was it sched.org I dont know right now 14:46:28 gnokii: yep thats right 14:46:29 yeh 14:46:42 im making it too complicated :) i think a print out day before should be fine. i can arrange for that. 14:46:51 well, hopefully sched.org provides an easily printed version :) 14:47:01 nope 14:47:16 #agreed we'll have a printed schedule insert for the booklet done the day before - it's handy to have on paper if the internet goes down 14:47:17 meetbot.meeting.item.agreed -- duffy noted agreement in the "design-team" meeting in #fedora-design: "we'll have a printed schedule insert for the booklet done the day before - it's handy to have on paper if the internet goes down" 14:47:36 gnokii: i might investigate if theres any kind of api for sucking the data down that we could automate a printable version 14:47:46 #action mizmo to look into if theres a way to autogenerate a printable schedule version for sched.org 14:47:46 meetbot.meeting.item.action -- duffy noted an action in the "design-team" meeting in #fedora-design: "mizmo to look into if theres a way to autogenerate a printable schedule version for sched.org" 14:48:45 ok can anybody think of anything else flock we might want to think about? 14:48:47 any awesome ideas? 14:49:06 5 years flock - 5 years faces 14:49:32 oh thats a nice idea - a portrait project? 14:49:54 yes, I have taken each flock portraits and jsmith as kushal as well 14:51:20 gnokii: do you think it'd be possible to do a flock faces post each night of the event on fedora magazine? 14:51:49 mizmo, I already did this all the years in my personal blog 14:52:24 gnokii: oh i know, but to consolidate them in one nightly post might be nice, make them easier to find 14:52:48 http://karl-tux-stadt.de/ktuxs/?p=4932 14:52:48 meetbot.meeting.item.link -- gnokii linked to more information in the "design-team" meeting in #fedora-design: "http://karl-tux-stadt.de/ktuxs/?p=4932" 14:53:29 http://karl-tux-stadt.de/ktuxs/?p=4808 14:53:29 meetbot.meeting.item.link -- gnokii linked to more information in the "design-team" meeting in #fedora-design: "http://karl-tux-stadt.de/ktuxs/?p=4808" 14:54:06 http://karl-tux-stadt.de/ktuxs/?p=4634 14:54:06 meetbot.meeting.item.link -- gnokii linked to more information in the "design-team" meeting in #fedora-design: "http://karl-tux-stadt.de/ktuxs/?p=4634" 14:54:48 better not try to find the other ones, takes to many traffic 14:55:12 these are so great 14:56:14 maybe we could do a sort of restrospective of some of these in the booklet 14:57:11 sure 14:57:53 i don't know how many of these are there, but could be nice doing something like a mosaic 14:58:00 yeh! 14:58:13 #info idea: photo mosaic of flock faces retrospective for flock booklet 14:58:14 meetbot.meeting.item.info -- duffy raised a point of information in the "design-team" meeting in #fedora-design: "idea: photo mosaic of flock faces retrospective for flock booklet" 14:58:29 if there are enough of them i could try to animate it so it can be used in the looping video too 14:58:46 ooh that could be cool! 14:58:47 its around 40 a year I did shoot 14:59:44 another random booklet idea 14:59:45 hehe 14:59:46 its probably dumb 14:59:46 but what if we had a flock bingo 15:00:02 meet certain people at flock 15:00:29 it might be interesting, if first-time attendees were on the bingo, it would be a way to encourage old timers to say hi to them and make them feel welcome 15:00:38 if you complete the bingo maybe you get some swag 15:00:46 uhm, like, how many of them can you spot? 15:01:01 i think we want them to say hi and introduce themselves, and maybe ask a question 15:01:46 mmh 15:02:03 an ice breaker question 15:02:06 i dont know maybe it's hokey 15:02:13 ill put it on the planning list and see what ppl think 15:02:30 all right we're at the top of the hour now 15:02:34 anything else we should cover? 15:03:43 ok im gonna end meeting! thanks everybody for coming :) 15:03:44 #endmeeting