17:58:43 #startmeeting Fedora-Websites - https://fedoraproject.org/wiki/Websites 17:58:43 Meeting started Thu Mar 6 17:58:43 2014 UTC. The chair is shaiton. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:58:43 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:58:48 #meetingname Fedora-Websites 17:58:48 The meeting name has been set to 'fedora-websites' 17:58:56 #chair sijis robyduck 17:58:56 Current chairs: robyduck shaiton sijis 17:59:10 * robyduck is here 17:59:15 ping ryanlerch_laptop 17:59:20 * sijis is here 17:59:27 shaiton, pong 17:59:48 is mizmo around too? 17:59:56 not yet 18:00:07 there were a few more folks too, right? 18:00:24 yep I am looking for names 18:01:17 yes, but asrob and cydrobolt are not able to attend today, hopefully jreznik can join us 18:02:07 let's start from the wiki page: 18:02:10 #link https://fedoraproject.org/wiki/Website_redesign/fedora.next 18:02:13 he flooded out ;/ 18:03:09 I would be best to have mizmo also, we can probably wait 2 more minutes? 18:03:16 and we have also the first mockup: 18:03:20 #link https://fedorahosted.org/fedora-websites/ticket/248#comment:7 18:03:31 shaiton: yes, let's wait a few minutes 18:05:26 ok, let's start 18:05:51 #topic work needed 18:06:05 Basically, with the move to Fedora.Next, we need to change all websites... 18:06:20 we should figure out the priority order 18:06:33 yes 18:07:02 my thought was to replace fedoraproject.org first with updated info about fedora.next, and at the same time get.fedoraproject.org too 18:07:15 spins.fpo - not sure what is going to happen to spins 18:07:43 does anybody have the diagram handy? 18:07:48 ¢/win 18:07:48 ok, these are the main topics to start working on 18:07:58 https://fedorahosted.org/fedora-websites/ticket/248#comment:7 18:08:36 ehre it is http://i.imgur.com/zhwmY5g.png 18:09:15 yeh so in that context 18:09:23 www.fedoraproject.org / the brochure site is top priority 18:09:32 the community hub is going to need more time, and we have individual apps filling that role currently 18:09:52 mizmo_: depending on how many images we will have for each product we could also have ws.fpo, server.fpo or cloud.fpo 18:09:55 support site is similar - we have ask.fpo now 18:09:57 yeh thats true 18:10:24 so we should decide for a layout we can easily adapt if there will be more images 18:10:39 and the brochure as in the mockup fits really good 18:10:54 i have also started a mockup for the brochure site: http://ryanlerch.fedorapeople.org/getfedora/ 18:11:15 mizmo_: the hubs will be done for sure after this, in a second step 18:12:21 ryanlerch_laptop: I like this mockup, although it's perhaps too much for a brochure, but that could be the style we want to follow 18:12:48 i like that its simple. i could see us easily adding more 'products' onto the list with little changes 18:13:14 ryanlerch_laptop: did you change the bootstrap.css or did you just add this small custom css? 18:13:22 yeah, obviously i ahvent got the cloud one on there too 18:13:47 robyduck, i am using the bootstrap.css, with some (messy at the moment) custom CSS 18:13:51 so, if i get this straight. we are going to work on the brochure part first. 18:13:59 thats's great 18:14:16 sijis: yes, definitely 18:14:34 and we need to know what to do / how to use get.fpo 18:14:42 mattdm: hey, we are speaking about this try: http://ryanlerch.fedorapeople.org/getfedora/ 18:14:42 so, its that going to be fp.o or getfedora.ord (referring to mizmo's mockup) 18:15:05 if I understood it right, yes 18:15:28 yes to fp.o or getfedora.org? 18:15:49 fp.o 18:15:57 gotcha. 18:15:58 mizmo_: about spins, I'd like to close spins.fpo and implement the spins into the new website 18:16:00 it is logic to point get.fpo to main fpo as we won't give a default product. We have several 18:16:22 no more jump into spins and back (2 sites) 18:16:35 shaiton: i think that's a fair thing to do 18:16:45 thanks shaiton 18:16:47 * mattdm looks 18:17:13 shaiton, yeah, i think that is how it should work. it will be the main site where people *get* fedora. 18:17:16 yes, should we mark the points we agree on? Just to have a meeting index? 18:17:29 we can 18:17:36 color of visited links needs tweaked. :) 18:17:36 #agree get.fpo = fpo 18:17:56 mattdm, that is just me not setting the link color in that top thing 18:18:01 it is a WIP 18:18:02 mattdm: colors are not important right now, we will do this later 18:18:13 sorry :) 18:18:27 robyduck: about spins, we should drop it and see later if we provides some. I've got one concern about this. What about providing F20 (still many ISOs). 18:18:48 once we have a good structure to work on we can do all the things we want 18:18:56 so there was a question on how to have flexibility on product urls, (ws, cloud, sping, etc) right? 18:19:40 shaiton: ok, let's talk later about spins (but let's keep an open door for them in the workstation section) 18:19:53 yes 18:19:55 sijis, flexibility for the download URLs? 18:20:06 #info spins will probably drop to WS product. see later 18:21:35 I have a question about the brochure: seems we will have a jumbotron on the top, do we agree on this? What about a slider instead of a static jumbotron? 18:22:04 robyduck: could we just let sijis explain his flexibility question? 18:22:23 oh yes, for sure. Sorry 18:22:59 i may have misread the mesasge. but i thoguht it was something on how to 'address' these products. like fp.o/product/ or just fp.o/product 18:23:19 unless, there no info about the product, just a link to d/l the file(s) 18:24:27 * shaiton think about fpo//{index,help,join…} 18:24:29 my thought with my current mockup was that this site will be the main site that lists the three products. and each one will have a link to "more info" or similar 18:24:43 ryanlerch_laptop: +1 18:24:48 robyduck, im afriad about mixing spins and the main releases :-/ 18:24:49 yep 18:24:57 and ewach of the 3 products have a similar page to the main one, but focussed on the product itself 18:25:03 ok, is there a mockup for that 'more info' page? 18:25:08 all with prominent download links at the top 18:25:13 sijis, not yet, no 18:25:22 k 18:25:55 ryanlerch_laptop: prominent DL link = main DL link? 18:26:05 as we don't know how many images we will have 18:26:09 * sijis does like shaiton url suggestion fp.o//.. 18:26:18 * robyduck too 18:27:11 robyduck, hadnt really thought too much about how many images we will have TBH 18:27:30 ok 18:27:33 my first thought was a rolodex type thing 18:27:41 ryanlerch_laptop: we need to think about one-to-many... (like cloud!) 18:28:29 is the expectation to get the brochure site done by next release? 18:28:38 sijis: yes 18:28:40 that would be ideal 18:28:51 should be ALPHA release 18:28:59 i consider brochure (fp.o, and product-info pages) 18:29:35 is support site the next target after brochure? 18:30:27 sijis: good question, I don't think so. 18:30:28 or should it be something else (spins??) 18:30:48 i think the fedora hubs would be next in priority 18:30:54 mizmo_: what was your thought about features? 18:30:56 i put support site lower priority because we do have ask.fpo already 18:31:11 yeah, we have ask fedora at the moment that is doing an okay job for support... 18:31:17 gotcha. so what do we do about join.fp.o? 18:31:25 robyduck, the features section of the current www.fpo? 18:31:28 +1 to make hub.fpo the next 18:31:30 yes 18:31:34 sijis, join.fpo gets slurped up by the community hub 18:31:47 start.fp.o? 18:31:49 ryan and i were thinking there would be a newbie workflow built into the hub 18:31:57 start.fpo... not sure. maybe should live on 18:32:01 start.fpo should remain 18:32:04 mizmo_: good idea. 18:32:06 mizmo_: +1 18:32:18 * shaiton see start as the hub for not authentified users and others 18:32:29 mizmo_, +1 -- with a refresh to fit with the new style, of course 18:32:36 so linking start.fpo to hub.fpo once done. 18:32:43 yeh 18:32:51 yeh start.fpo should be driven by info on hub.fpo too i think 18:33:01 that's a nice idea, yes 18:33:06 Therefore we should not spend more than half a day on start redisign 18:33:10 shaiton: sounds like a good idea to me. 18:33:43 #agree to move start.fpo to match the new design, but should then be replaced by hub.fpo once out. 18:33:54 yeh exactly 18:34:04 mizmo_: why are you afraid about spins in fpo? 18:34:05 to summarize. join.fpo and start.fpo will point to hub.fpo 18:34:19 yep 18:34:20 yep 18:34:32 +1 18:34:36 +1 18:34:47 well for non authenticated hub users... i think there shouldnt be anything on the front page 18:34:57 and start.fpo should link to some special page on the hub 18:35:32 that would be some hub logic that would handle that 18:35:43 mizmo_, you think the unauthed hub should have a bit of info similar to the current join.fpo ? 18:35:45 (speculating) 18:35:49 yeh 18:35:56 ryanlerch_laptop, no i think unauthed hub should be pretty blank 18:36:02 it should be like if you're not logged into twitter or facebook 18:36:30 you want people feeling the *need* to have a FAS account? 18:36:32 :è) 18:36:49 * robyduck doesn't like the idea to see blank pages 18:36:50 mizmo_, so people will only get the "these are the skills you can contribute" if they login? 18:36:55 not blank! 18:37:01 but it'll give them a workflow to join 18:37:11 oh 18:37:15 thats a good question ryanlerch_laptop 18:37:31 maybe we should look at the mozilla community join pages as inspiration there 18:37:35 see hwo they handle it 18:37:37 i mean 18:37:40 thats what i was thinking, that page can be the advert for joining up 18:37:46 oh exactly 18:37:51 i wouldn't have as much content as the current join.fpo tho 18:37:51 we need to convince them to join! 18:37:59 mizmo_, def not 18:38:23 yes, and we are not facebook or similar, we need to put soemthing on there 18:38:29 IMHO 18:39:08 I like this idea. simple page with interesting content for simple user who's going to join 18:39:14 this is how mozilla does it https://www.mozilla.org/en-US/contribute/ 18:39:22 facebook and twitter both have a bit of info about thier servicesw 18:39:29 mizmo_: thx for the link 18:39:45 robyduck, yeh i think - i said it very badly. but my point is if you are not logged in, the page should be all about showing people how to join. it shouldn't be for current users. that's what i meant to say 18:40:10 it's nice, we can't (by random) promote products, values, SIGs... 18:40:20 mizmo_: ok gitcha 18:40:24 gotcha* 18:40:51 hey, now that we have too priorities, shouldn't we go forward on fpo and have few people defining the hub? 18:41:12 - and define next tasks for fpo 18:41:15 id like to know about spins...? ;) 18:41:22 yes, two other things 18:41:28 yes, sijis 18:41:38 I have one remark about spins 18:41:57 that's one: why are you afraid to have spins in fpo, mizmo_ ? 18:41:58 i think maybe the next step would be to blog post the mockup, which i can do 18:42:05 robyduck, oh i can explain 18:42:14 yes please :) 18:42:22 robyduck, so my worry if there are say 20 downloads, it's going to be hard to find the main 3 fedoras 18:42:32 so i just wanted the main supported ones to be a bit separate from the spins 18:42:39 since the spins are less supported / less QA / etc. 18:42:49 some spins are less supported, some not 18:42:53 yeh 18:42:59 mizmo: and I agree with you on that 18:43:11 we should really redefine "spins" 18:43:12 so i was thinking that the main ones should be front and center. those are the ones we offer to brand new people 18:43:14 sorry, I had troubles with network/IRV 18:43:17 spins are more for people who know what they are doing 18:43:17 but wasn't there the thought to have them like incubator? 18:43:24 or the products? 18:43:25 i'm not sure :( 18:43:40 that spins thread was really long and i couldn't follow what was going on 18:43:46 we could change the layout, I mean, in the WS product we would have max 6 spins 18:43:55 but spins would be only for WS. So we can have a small page WS/spins ? 18:43:57 robyduck: we are now preparing proposal for kde spin being supported education/scientific product 18:44:14 i do like mizmo's thought on leaving he 'primary' fedora's front and center 18:44:17 i think there are non ws spins aren't there? the security spin? 18:44:26 I agree sijis 18:44:32 i assume cloud is going to have multiple images to download too? 18:44:43 but the bar for products should be much higher than for spins - so don't expect more than 3-5 products 18:44:48 so, is the best thing to leave spins where it is for now, until its better defined what it will become? 18:44:54 mizmo: security is not desktop spin (not WS) 18:44:54 if all of the spins, or most, are workstations, we could have a link from the WS product page, 'learn more about alternative workstations' or something 18:44:55 then I agree spins should be a different page 18:45:01 ryanlerch yes, several. and also several ways to launch without download. 18:45:09 mizmo: probably, but do we still call it spins, or could it be just part of a product without the spin name? 18:45:26 mizmo: not sure, it should not be link from WS 18:45:27 shaiton, that is a very good question, and im not sure. i thoguht the names spins vs. remix, at least, had some legal component 18:45:29 mizmo: yes, let's keep a link for now, a sort of transitional website (for spins) 18:45:35 as these WS are going to be installable option 18:45:42 not standalone spins 18:45:46 jreznik, ohhh you can install it from within the WS? 18:45:47 oh okay 18:45:51 mizmo: yep 18:45:58 that's the plan 18:46:06 mizmo spins = all fedora content, remix = could add any non-fedora content (including proprietary, or not) 18:46:09 nice, finally :) 18:46:19 mattdm: remixes are out of scope of fpo 18:46:29 jreznik: then we need them on fpo 18:46:36 but i dont think all the spins (or remixes) should be listed on the site. 18:46:43 robyduck: no, not remixes, yes for spins 18:46:44 not front and centre at least. 18:46:44 ryanlerch: +1 18:46:55 and spins should probably be integrated to a product, therefore we can call it a specific release under a specific product... but we will see later 18:47:06 sure, I got it, we are talking about few spins 18:47:19 are we going to ship spins as stnadalone isos anymore then? 18:47:26 or would it make sense to advertise them as.... channels? 18:47:28 or add-ons? 18:47:28 ok, thx jreznik for the info 18:47:30 or something like that? 18:47:34 mizmo: for some, yes 18:47:43 are there spins that must be standalone isos? 18:47:49 would it make sense to go thru the list and classify them? 18:48:06 so what you can expect is - some former desktops/spins will be installable option from WS 18:48:21 some spins will still exist as spins 18:48:33 maybe some spins would be upgraded one day into product 18:48:44 (so front page) 18:48:49 ok, I see the WS/spins solution as a good one 18:49:09 remixes are out of scope of fpo (maybe except pidora) 18:49:38 we would always be able to add specific (spins or whatever) links/section. just need to know *who* decide this and *when* 18:49:59 so there's possibility there will be more than three main products on top level - just the barrier would be high and it does not happen... it's up to fesco, that's what they agreed 18:49:59 yeh, that i still dont think we know o_O 18:50:26 btw. note - all I said is how I understood discussion so far :) 18:50:38 since we don't know... lets just leave spins as-is? 18:50:41 so if a spin is not a standalone iso, do we advertise it on workstation page? e.g., "You can try these cool add-ons too after you install" ?? 18:50:41 ok, let's retalk about spins next time 18:50:43 yeh 18:50:52 spins, the mystery continued.. next time. 18:50:55 sijis: for now I think it's the best thing you can do 18:50:59 what about the footer? 18:51:11 how should it be in your opinion? 18:51:14 yeah, at the moment, the only *set in stone* thing we have is that there is going to be 3 Products 18:51:25 mizmo: yes, for spins that are going to be installable option of ws 18:51:39 I think spins.fpo should stay until F20 gets EOL. Then, we will see :) 18:51:40 i think the footer shold stay close to the same since we aren't going to replace EVERYTHING it links to right away. as stuff gets moved / updated / replaced then we should update the footer 18:51:51 shaiton: +1 18:51:54 eg we aren't moving docs 18:51:59 mizmo: +1 18:52:05 ok nice 18:52:07 mizmo: +1 18:52:21 we aren't moving the subproject wiki pages (At leats not right away. eventually those links shold point to the teams' hubs 18:52:23 jreznik, where was this discussoion about spins? /me would like some background info 18:52:37 #agree to share the same footer 18:52:39 ryanlerch: on -devel? I think 18:52:49 yes on -devel 18:52:53 that installable option happens on desktop 18:53:24 mizmo: no probs, we are moving, it's the important fact 18:53:50 ryanlerch: and for more than three products https://fedorahosted.org/fesco/ticket/1197 18:54:15 it's hard to follow, as it's discussed almost everywhere :( 18:54:19 we aren't keeping the same branded header though? (the one with RH logo on it) 18:54:34 I don't think so sijis 18:54:43 we can still refer to RH in the footer 18:54:49 are doing lang selection though? 18:54:53 yeh i think thats fair 18:55:02 lang selection, we should still do taht yes 18:55:08 yep 18:55:19 ryanlerch: take a look on the last comment in ticket - there's agreement on products and spins 18:55:28 "Spins continue to exist" 18:55:35 "AGREED: Close for now until the current products are released at least once and/or anyone proposes a new product " 18:55:44 "Many FESCo members think that the bar for the new products should be relatively high" 18:55:49 jreznik: it does not say we need to maintain the websites :D 18:55:57 haha 18:55:58 ooh! okay forget this! party time!!! 18:56:02 we should also think about different release cycles in the future (F22 perhaps). So products will have different release states. 18:56:06 * mizmo passes out shots of jamesons 18:56:17 robyduck: it's definitely not f22... 18:56:32 ok, so also F22 will have same release time? 18:56:33 and I'm not sure it will even ever happen 18:56:41 ok, great 18:56:43 robyduck: it does not change the fpo websites. just the way we want to promote new release 18:56:53 shaiton: yep 18:56:55 we may need to promote new releases more often than every 6 months 18:56:58 depending 18:57:42 so i have to run to another meeting shortly 18:57:48 shaiton: not sure, if there are different release cycles the page has to change, but let's not worry about it 18:57:49 so it sounds like our first focus is the brochure site 18:57:55 and we'll start thinking about how to do the hubs too? 18:58:02 ok, yes 18:58:06 yay! 18:58:10 yeah 18:58:22 who's going to work on the brochure? :) 18:58:25 should be expect a newer mockup (with lang select or anything else) 18:58:30 ill do a blog post hopefully tomorrow to summarize this meeting too and to show the mockup / diagram 18:58:36 ryanlerch is working on the brochure 18:58:36 nice thanks mizmo 18:58:47 ryanlerch, can you add a language selector to the brochure mockup? 18:59:16 sure. but insnt that usually done automatically? 18:59:38 it's a template, yes 18:59:42 ryanlerch: it can be taken from the browser, but some people might prefere an other language 19:00:04 I could be small on the footer probably? 19:00:13 * shaiton see this for test purpose also :) 19:00:18 yeah, that is what i was thinking, the footer 19:00:27 no need to add it to the top. 19:00:40 * robyduck doesn't see it on the top neither 19:00:52 footer fine by me 19:00:55 yes 19:01:04 shaiton: let's think about a nice footer solution 19:01:11 all for today? 19:01:12 anything left? 19:01:29 * shaiton does not have nice design solutions 19:01:49 should be fin 19:01:49 e 19:01:58 not from me, was a very useful meeting, thx for coming 19:02:33 #info top priority is get.fpo (static), then hub.fpo (web-app). designs in progress 19:02:47 yep thanks to all. 19:02:57 jreznik: when our website should be ready? 19:02:57 :) 19:03:58 ok no probs, let's close the meeting 19:04:01 shaiton: I was tasked by FESCo to prepare schedule for F21 aiming on Oct 14th - so I'll know tomorrow where alpha lands... 19:04:15 and the question is how much stuff do you want for Alpha/Beta/Final 19:04:15 ok thanks 19:04:18 shaiton: I think it doesn't make sense having it for alpha... 19:04:26 most of the content is F20 19:04:45 but GA plan right now is Oct 14th 19:05:29 we will see, but I think 2 months ago they might all product know where they go 19:05:39 or 3 months.. 19:05:43 yep 19:05:56 So we have time. even time to have a small hub.fpo :) 19:06:15 yep 19:06:28 jreznik: for us the more important is to have a nice way to know when there will be new release, what would be release, and how. 19:06:42 If each products follow the same process, that would be the best 19:06:58 be released* 19:07:22 it is too early to define, but we might be part of the discussion (with releng) 19:07:47 ryanlerch: you'll be the contact for anything brochure related, right? 19:07:58 sijis, ack! 19:09:22 closing? 19:09:24 ok if there isn't anything else let's end it for today 19:09:27 ha 19:09:33 #endmeeting