From Fedora Project Wiki
| -!- ricky changed the topic of #fedora-websites to: Websites Meeting - Who's here? | <a href="#t17:00" class="time">17:00</a> | |
| ricky | hiemanshu, markg85, mizmo, ianweller, mchua, onekopaka_away, nb, anybody I forgot: ping | <a href="#t17:00" class="time">17:00</a> |
|---|---|---|
| nb | oh | <a href="#t17:01" class="time">17:01</a> |
| * nb is here | <a href="#t17:01" class="time">17:01</a> | |
| * nb forgot about the meeting | <a href="#t17:01" class="time">17:01</a> | |
| * markg85 is here | <a href="#t17:01" class="time">17:01</a> | |
| * hiemanshu will be here in 5 mins | <a href="#t17:01" class="time">17:01</a> | |
| -!- mchua_ [n=mchua@host232.155.212.137.conversent.net] has joined #fedora-websites | <a href="#t17:02" class="time">17:02</a> | |
| ricky | mchua_: Hey | <a href="#t17:02" class="time">17:02</a> |
| -!- mchua [n=mchua@nat/redhat/x-f7551ede865e4856] has quit Nick collision from services. | <a href="#t17:02" class="time">17:02</a> | |
| mchua_ | hey, sorry I'm late; took a while to reconnect to wifi. | <a href="#t17:02" class="time">17:02</a> |
| mchua_ | can someone pastebin me a backlog? | <a href="#t17:02" class="time">17:02</a> |
| * mchua_ pulls up task list | <a href="#t17:02" class="time">17:02</a> | |
| ricky | mchua_: <a href="http://dpaste.com/57245/">http://dpaste.com/57245/</a> | <a href="#t17:03" class="time">17:03</a> |
| mchua_ | thanks, ricky | <a href="#t17:03" class="time">17:03</a> |
| -!- mchua_ is now known as mchua | <a href="#t17:03" class="time">17:03</a> | |
| -!- ricky changed the topic of #fedora-websites to: Websites Meeting - Release | <a href="#t17:03" class="time">17:03</a> | |
| ricky | Everything went pretty smoothly with the release | <a href="#t17:03" class="time">17:03</a> |
| ricky | We tried a new way of working with git branches, which worked out really well :-) | <a href="#t17:04" class="time">17:04</a> |
| mizmo | hi | <a href="#t17:04" class="time">17:04</a> |
| mchua | hey mizmo! | <a href="#t17:04" class="time">17:04</a> |
| ricky | The one hitch was that there were some docs links that weren't right on release day, so we had to do last-minute fixing :-/ | <a href="#t17:04" class="time">17:04</a> |
| ricky | Next time, I'll send out "please check this website" emails to websites, docs, and design lists. | <a href="#t17:04" class="time">17:04</a> |
| -!- ricky changed the topic of #fedora-websites to: Websites Meeting - Task List | <a href="#t17:05" class="time">17:05</a> | |
| * ricky hands it over to mchua | <a href="#t17:05" class="time">17:05</a> | |
| mchua | <a href="https://fedoraproject.org/wiki/Websites/Tasks#The_list">https://fedoraproject.org/wiki/Websites/Tasks#The_list</a> | <a href="#t17:05" class="time">17:05</a> |
| mchua | so, people did check their email, and the list should be all up to date :) | <a href="#t17:05" class="time">17:05</a> |
| * mchua is new, and begs pardon for the many questions and the learning on the job | <a href="#t17:05" class="time">17:05</a> | |
| mchua | but before we all start getting busy again, i was wondering if the team had any targets for f12 - what do we want to accomplish this round? | <a href="#t17:06" class="time">17:06</a> |
| mchua | reading through the list, a lot of things seemed scattered to me, I couldn't tell where it was all going, but I may be missing something | <a href="#t17:06" class="time">17:06</a> |
| mchua | ricky, mizmo, ianweller, quaid, jonmasters... folks who have been around here longer, any thoughts of where we're headed? | <a href="#t17:07" class="time">17:07</a> |
| * hiemanshu pardons for being late | <a href="#t17:07" class="time">17:07</a> | |
| ricky | My main goal is to get join.fp.o much more friendly. That'd be a big gain. | <a href="#t17:07" class="time">17:07</a> |
| hiemanshu | ricky, i would rename that as Noob proof | <a href="#t17:07" class="time">17:07</a> |
| hiemanshu | We have people asking us stuff in #fedora that can be found on the site | <a href="#t17:08" class="time">17:08</a> |
| ricky | Ah | <a href="#t17:08" class="time">17:08</a> |
| hiemanshu | for example people asked for links for x86_64 | <a href="#t17:08" class="time">17:08</a> |
| ricky | Having join info at fp.o would be nice also because it would be translated. | <a href="#t17:08" class="time">17:08</a> |
| ricky | Ah, x86_64 downloads are another issue we'll have to think on for F12 :-/ | <a href="#t17:09" class="time">17:09</a> |
| markg85 | ricky, isn't the only thing missing on j.fp.o a clear description of what those category's mean? | <a href="#t17:09" class="time">17:09</a> |
| mizmo | this is really hard to do without understanding what exactly fedora is meant to be | <a href="#t17:09" class="time">17:09</a> |
| * mchua agrees with n00bproof join.fp.o, but isn't sure exactly what that means | <a href="#t17:09" class="time">17:09</a> | |
| * giarc shows up late | <a href="#t17:09" class="time">17:09</a> | |
| ricky | mizmo: Sorry, which part were you referring to? | <a href="#t17:09" class="time">17:09</a> |
| mizmo | ricky: are we a distro for developers or are we a 'consumer desktop' distro | <a href="#t17:10" class="time">17:10</a> |
| ricky | I think n00bproof is too strong a term, even. I can see how a page like <a href="http://fedoraproject.org/wiki/PackageMaintainers/Join">http://fedoraproject.org/wiki/PackageMaintainers/Join</a> could be confusing to anybody. | <a href="#t17:10" class="time">17:10</a> |
| mizmo | ricky: the difference between those two is a difference of a million miles in the approach to take for fpo | <a href="#t17:10" class="time">17:10</a> |
| hiemanshu | ricky, we should have explain as though you were teaching a 8 year old | <a href="#t17:11" class="time">17:11</a> |
| ricky | hiemanshu: Based on what you've seen in #fedora - what kind of person do you think wants x86_64 downloads? | <a href="#t17:11" class="time">17:11</a> |
| hiemanshu | ricky, people who just want to try those | <a href="#t17:11" class="time">17:11</a> |
| hiemanshu | The thing is the links are not on the get-fedora page, which should have been there | <a href="#t17:11" class="time">17:11</a> |
| mchua | hrm. | <a href="#t17:12" class="time">17:12</a> |
| hiemanshu | you need to click another button and people ignore that and waste more thing getting that question answered | <a href="#t17:12" class="time">17:12</a> |
| hiemanshu | it should be made obvious to people | <a href="#t17:12" class="time">17:12</a> |
| mizmo | hiemanshu: what kind of people are these? these are technical people no? | <a href="#t17:12" class="time">17:12</a> |
| ricky | Can we profile each specific type of user into more categories than just "developer vs. consumer" ? | <a href="#t17:12" class="time">17:12</a> |
| mchua | so, I'm not sure if this would be a useful metric at all, but <a href="https://fedoraproject.org/wiki/Websites/Brainstorms#j.fp.o_experience">https://fedoraproject.org/wiki/Websites/Brainstorms#j.fp.o_experience</a> was one thing I've been thinking of. | <a href="#t17:12" class="time">17:12</a> |
| hiemanshu | mizmo, non technical | <a href="#t17:12" class="time">17:12</a> |
| mchua | "one possible effectiveness metric for our website might be the number of contributions each release gets from new contributors (i.e. contributors whose first contributions were in that release) - in other words, "does join.fp.o work"?" | <a href="#t17:12" class="time">17:12</a> |
| mizmo | hiemanshu: you're telling me a non-technical person insisted on x86_64? | <a href="#t17:12" class="time">17:12</a> |
| hiemanshu | mizmo, yes | <a href="#t17:13" class="time">17:13</a> |
| mizmo | hiemanshu: if i mentioned the word 'x86_64' to my mom, she would be like, 'huh?' | <a href="#t17:13" class="time">17:13</a> |
| mizmo | hiemanshu: so on the scale of my mom <=> linus torvalds, what do you mean by "non-technical"? because i think we have very different definitions | <a href="#t17:13" class="time">17:13</a> |
| hiemanshu | mizmo, people how have some idea or heard from friends want 64 bit OS just because they have a 64 bit proc | <a href="#t17:13" class="time">17:13</a> |
| mizmo | hiemanshu: the very fact the person was talking to you in IRC right away tells me they are at least a little technical | <a href="#t17:13" class="time">17:13</a> |
| mizmo | hiemanshu: this was in IRC, right? | <a href="#t17:14" class="time">17:14</a> |
| hiemanshu | mizmo, non technical means who does not want to try to get this way around | <a href="#t17:14" class="time">17:14</a> |
| hiemanshu | yes | <a href="#t17:14" class="time">17:14</a> |
| mizmo | my mom doesn't know how to use IRC or even what it is | <a href="#t17:14" class="time">17:14</a> |
| mizmo | hiemanshu: can you reword that? im not sure what you were trying to say | <a href="#t17:14" class="time">17:14</a> |
| hiemanshu | there way* | <a href="#t17:14" class="time">17:14</a> |
| ricky | I'm slightly confused at how somebody knows enough to be aware that there is an x86_64 version, but doens't click the "show me all options" link. | <a href="#t17:14" class="time">17:14</a> |
| ricky | Maybe the wording is confusing? Should that link be "show me all options" instead of "show me all options on one page" ? | <a href="#t17:15" class="time">17:15</a> |
| hiemanshu | mizmo, according to me a Non Technical user is one who knows he has a computer and a OS, but does not know what to when he has problems and comes to IRC | <a href="#t17:15" class="time">17:15</a> |
| mizmo | well we could make the show me all options stuff more obvious | <a href="#t17:15" class="time">17:15</a> |
| hiemanshu | ricky, below download link add looking for x86_64, find it here | <a href="#t17:15" class="time">17:15</a> |
| mizmo | hiemanshu: okay that's a very big difference in my definition of a non-technical user, who is someone who has a computer perhaps but who doesn't know how to use IRC and just wants to try out linux | <a href="#t17:15" class="time">17:15</a> |
| mchua | so... wait, hang on a second. before we get into the definition of a nontechnical user looking for x86_64 stuff, maybe we should figure out what improvements we want from the website this release. | <a href="#t17:16" class="time">17:16</a> |
| ricky | hiemanshu: That would very possibly be confusing to somebody that doesn't know whether they need x86_64 or not though | <a href="#t17:16" class="time">17:16</a> |
| mchua | hiemanshu, it sounds like you want to make sure folks looking for 64-bit stuff can find it. | <a href="#t17:16" class="time">17:16</a> |
| markg85 | Just a crazy idea but what if the download page in done in a question like way? | <a href="#t17:16" class="time">17:16</a> |
| hiemanshu | Make every thing _obvious_ so we dont have people asking us stuff | <a href="#t17:16" class="time">17:16</a> |
| markg85 | for example: | <a href="#t17:16" class="time">17:16</a> |
| giarc | if x86_64 is too hard for some users to find, couldn't we just add a lozenge like we have for KDE etc? | <a href="#t17:16" class="time">17:16</a> |
| mizmo | mchua: i think the goal should be, for get.fpo, keep the newb-focused stuff the same, but make the 'more options' link way more obvious | <a href="#t17:16" class="time">17:16</a> |
| markg85 | Do you have more than 3GB of memory? (x64) | <a href="#t17:16" class="time">17:16</a> |
| mizmo | giarc: if we added a lozenge for everything people have asked for a lozenge for, the lozenge list would be longer than richard stallman's beard | <a href="#t17:17" class="time">17:17</a> |
| markg85 | then download that x64 | <a href="#t17:17" class="time">17:17</a> |
| mizmo | markg85: i dont even know how much ram is in my laptop | <a href="#t17:17" class="time">17:17</a> |
| mchua | it's hard to figure out what words like "obvious" and "intuitive" and "user friendly" mean. | <a href="#t17:17" class="time">17:17</a> |
| markg85 | mizmo, ^_^ | <a href="#t17:17" class="time">17:17</a> |
| ricky | giarc: That's another possibility, but it'd quickly get complicated, because then we'll have to account for KDE x86_64 live media too | <a href="#t17:17" class="time">17:17</a> |
| hiemanshu | markg85, i586 with PAE supports 64GB ram | <a href="#t17:18" class="time">17:18</a> |
| mizmo | mchua: okay make the more options link more prominent and eye catching, is that better than 'obvious' ? o_O | <a href="#t17:18" class="time">17:18</a> |
| hiemanshu | RAM* | <a href="#t17:18" class="time">17:18</a> |
| mizmo | hehe | <a href="#t17:18" class="time">17:18</a> |
| giarc | mizmo, heh, sure...but we *can* continue to say no to all the other requests | <a href="#t17:18" class="time">17:18</a> |
| ricky | Then there will be two links that match somebody that wants the KCD x86_64 live media. | <a href="#t17:18" class="time">17:18</a> |
| markg85 | hiemanshu, ... true | <a href="#t17:18" class="time">17:18</a> |
| mchua | mizmo: way better. :) | <a href="#t17:18" class="time">17:18</a> |
| mizmo | giarc: what makes x86_64 more important than all the others? | <a href="#t17:18" class="time">17:18</a> |
| giarc | ricky, had not thought of that | <a href="#t17:18" class="time">17:18</a> |
| giarc | mizmo, nothing, just that seems to be a constant complaint | <a href="#t17:18" class="time">17:18</a> |
| mchua | mizmo: making it prominent and eye catching so that people who want the non-default dl option will be able to find it, I reckon? | <a href="#t17:18" class="time">17:18</a> |
| mizmo | giarc: the others are constant as well :) | <a href="#t17:19" class="time">17:19</a> |
| mizmo | mchua: yep | <a href="#t17:19" class="time">17:19</a> |
| * markg85 would still like to point to this option: <a href="http://fedora.mageprojects.com/">http://fedora.mageprojects.com/</a> | <a href="#t17:19" class="time">17:19</a> | |
| hiemanshu | My aim to decrease people asking the same stuff on #fedora by making it Obvious | <a href="#t17:19" class="time">17:19</a> |
| mchua | markg85 also had a cool idea with the questions-based page, which I'm guessing has a similar motivation... letting people who want (or need, but don't know that they want) the non-default option land at the right place. | <a href="#t17:19" class="time">17:19</a> |
| * giarc needs to run for 5 mins ( boss bellowing for me ) | <a href="#t17:19" class="time">17:19</a> | |
| mizmo | markg85: huh? you're saying we shold go from having 2 links where people complain about not having others, to having one link? and how does that help exactly? | <a href="#t17:19" class="time">17:19</a> |
| hiemanshu | and add a documentation link before download actually starts | <a href="#t17:19" class="time">17:19</a> |
| mchua | hiemanshu so, reducing repetitive questions on #fedora. which you see the x86_64 thing crop up on a lot? | <a href="#t17:20" class="time">17:20</a> |
| mizmo | i think it's okay to have a questions => link for the non-default download page, but not for the front download page | <a href="#t17:20" class="time">17:20</a> |
| ricky | mchua: One general problem we've had with websites is that we don't have a clear decision making process. That's one other area I'd like to improve. | <a href="#t17:20" class="time">17:20</a> |
| mchua | ricky: I'm starting to understand what you mean by that. :) | <a href="#t17:20" class="time">17:20</a> |
| hiemanshu | mchua, not only those, those are once in a while, but make them so obvious that an 8 year old can download it | <a href="#t17:20" class="time">17:20</a> |
| mizmo | hiemanshu: we have documentation links before the download starts. see the grey 'resources' boxes next to each link? | <a href="#t17:20" class="time">17:20</a> |
| * mchua frantically trying to summarize things people want to work on | <a href="#t17:21" class="time">17:21</a> | |
| mizmo | we provide the install guide, release notes, and a link to the full docs site | <a href="#t17:21" class="time">17:21</a> |
| hiemanshu | mizmo, i mean people to get-fedora page and start downloading and overlook those resources | <a href="#t17:21" class="time">17:21</a> |
| ricky | mchua: It's tough, because on one hand, we don't want any suggestion to instantly go live, and on the other hand, we don't want suggested changes to completely fall to the side. | <a href="#t17:21" class="time">17:21</a> |
| mizmo | hiemanshu: that is on the get-fedora page. | <a href="#t17:21" class="time">17:21</a> |
| markg85 | mizmo, all i'm saying is that it would be a nice idea to have the most common options appear at the download page. If that's like my idea on that link or just 2 seperate links... both will do fine i think | <a href="#t17:21" class="time">17:21</a> |
| markg85 | separate | <a href="#t17:21" class="time">17:21</a> |
| hiemanshu | mizmo, change them a little so that people will first click a link where it make it _obvious_ then another link to start download | <a href="#t17:22" class="time">17:22</a> |
| mizmo | hiemanshu: that doesn't make sense to me, though, because you said that people were complaining about having to click another link to get to x86_64. but to me, it sounds like you are suggesting forcing everyone to click another link to get links to documentation? | <a href="#t17:23" class="time">17:23</a> |
| mizmo | i guess i'm simply just not following | <a href="#t17:23" class="time">17:23</a> |
| hiemanshu | mizmo, you have got me wrong | <a href="#t17:23" class="time">17:23</a> |
| markg85 | another think i would like a lot is just by looking at the user-agent of the user visiting the download page then select a default download architecture based on that | <a href="#t17:23" class="time">17:23</a> |
| mizmo | it sounds like you are suggesting: get-fedora => documentation links => download link | <a href="#t17:23" class="time">17:23</a> |
| mchua | okay, uh... hang on. I want to see if I'm hearing everyone correctly here. | <a href="#t17:23" class="time">17:23</a> |
| mchua | mizmo wants to help people who want the non-default dl option find the non-default dl-option by making it more prominent and eye-catching. | <a href="#t17:23" class="time">17:23</a> |
| markg85 | the user agent tells the architecture so why not use that valuable info | <a href="#t17:23" class="time">17:23</a> |
| mchua | markg85 wants to help people who want (or need, but don't know that they want) the non-default option land at the right place. | <a href="#t17:23" class="time">17:23</a> |
| mchua | hiemanshu wants to reduce repetitive questions on #fedora (example: x86_64) by making resources that 8-year-olds could use. | <a href="#t17:23" class="time">17:23</a> |
| hiemanshu | get-fedora =>Docs link =>15 sec delay to download | <a href="#t17:23" class="time">17:23</a> |
| mizmo | markg85: how do you know the user is downloading the image for the same computer they have the browser open on? | <a href="#t17:24" class="time">17:24</a> |
| mchua | ricky wants to have a clear decision making process on the websites team that balances ease-of-experimentation with moderation to make sure changes are good ones. | <a href="#t17:24" class="time">17:24</a> |
| mizmo | markg85: in many situations someone is trying to download a linux image for a machine that is broken. | <a href="#t17:24" class="time">17:24</a> |
| mchua | and I'm trying to figure out what the hell is going on. :) and raise the number of new contributors in this release through improving the website. | <a href="#t17:24" class="time">17:24</a> |
| ricky | I'm kind of against going by the user agent. That can cause major confusion if I go to the library to download Fedora, for example | <a href="#t17:24" class="time">17:24</a> |
| markg85 | mizmo, well the same can be asked for the situation as it currently stands. you just don't know | <a href="#t17:24" class="time">17:24</a> |
| mizmo | markg85: right which is why it's better to have the user select than auto select it for them and get it wrong. | <a href="#t17:25" class="time">17:25</a> |
| * mchua wonders if we agree on the purpose and audience of the design details we're debating about... | <a href="#t17:25" class="time">17:25</a> | |
| hiemanshu | mizmo, where there is a download now button add another button download x86_64 | <a href="#t17:25" class="time">17:25</a> |
| mizmo | markg85: if the page changes based on the machine you're on, then it becomes more difficult for folks like hiemanshu to help people because they may not even be looking at the same page anymore | <a href="#t17:25" class="time">17:25</a> |
| mizmo | mchua: i think we really need to start there | <a href="#t17:25" class="time">17:25</a> |
| hiemanshu | and below that why x86_64 | <a href="#t17:25" class="time">17:25</a> |
| markg85 | mizmo, true | <a href="#t17:26" class="time">17:26</a> |
| mizmo | i do not want to add more buttons to the main get fedora page. | <a href="#t17:26" class="time">17:26</a> |
| mizmo | there are enough as it is. | <a href="#t17:26" class="time">17:26</a> |
| mizmo | we worked really hard to simplify it down to where it's at now. | <a href="#t17:26" class="time">17:26</a> |
| mizmo | i think the problem with get fedora | <a href="#t17:26" class="time">17:26</a> |
| mizmo | is that it's difficult for more technical users to use. | <a href="#t17:26" class="time">17:26</a> |
| ricky | If the x86_64 link on get-fedora is as prominent as the 32 bit one, you will almost definitely get new questions in #fedora asking whether people need 32 bit or 64 bit. | <a href="#t17:26" class="time">17:26</a> |
| ricky | I've seen that myself back when get-fedora was <a href="http://fedoraproject.org/en/get-fedora-all">http://fedoraproject.org/en/get-fedora-all</a> | <a href="#t17:26" class="time">17:26</a> |
| mizmo | so i think our goal for f12 should be to address the 'view more options' so that it's easier to find for those users. | <a href="#t17:26" class="time">17:26</a> |
| hiemanshu | ricky, that why i said a link below to a page why x64 | <a href="#t17:26" class="time">17:26</a> |
| markg85 | mizmo, my issue with getting f11 x64 was that it's currently guesswork to even find it | <a href="#t17:27" class="time">17:27</a> |
| mchua | uh... folks, before we start talking about specific implementation ideas, can we take a step back and breathe a little and figure out where everyone is coming from? | <a href="#t17:27" class="time">17:27</a> |
| mizmo | markg85: exactly. so we shold make the full page of 'other options' easier for you to find | <a href="#t17:27" class="time">17:27</a> |
| ricky | hiemanshu: Nobody ever clicks those links. If anybody bothered to click the install guide linnk first, all their questions would be answered. | <a href="#t17:27" class="time">17:27</a> |
| mchua | I'm feeling a bit like I'm watching ships pass each other in the night right now... | <a href="#t17:27" class="time">17:27</a> |
| mizmo | markg85: eg we could have a button that says, 'View more options (x86_64, ppc, KDE, and more)' | <a href="#t17:27" class="time">17:27</a> |
| * giarc is back, ( june birthdays here at work... ) | <a href="#t17:27" class="time">17:27</a> | |
| mchua | hey, giarc. discussion is a bit scattered at the moment. I'm trying to keep up with all the threads. :) | <a href="#t17:28" class="time">17:28</a> |
| hiemanshu | ricky, yeah that could be one thing, people just dont want to read | <a href="#t17:28" class="time">17:28</a> |
| ricky | mizmo: Ooh, that's a good idea. | <a href="#t17:28" class="time">17:28</a> |
| markg85 | mizmo, that's yet another possible idea | <a href="#t17:28" class="time">17:28</a> |
| mizmo | ricky: yeh we could do them in fine print | <a href="#t17:28" class="time">17:28</a> |
| ricky | Yeah. | <a href="#t17:28" class="time">17:28</a> |
| mizmo | ricky: so people looking for the keyword 'x86_64' would skim and it would jump out at them | <a href="#t17:28" class="time">17:28</a> |
| ricky | As it is, I'm not crazy about grouping KDE and PPC together :-( | <a href="#t17:29" class="time">17:29</a> |
| mizmo | ricky: then we avoid having a matrix of the combinatorial options on the front page, but at tthe same time the keywords the technical users are working for are there | <a href="#t17:29" class="time">17:29</a> |
| giarc | mizmo, sort of like a tag cloud? | <a href="#t17:29" class="time">17:29</a> |
| ricky | Yes, that's good. | <a href="#t17:29" class="time">17:29</a> |
| hiemanshu | Yes thats better | <a href="#t17:29" class="time">17:29</a> |
| mizmo | giarc: sort of. i wouldn't do the different font sizes the way a tag cloud is though. | <a href="#t17:29" class="time">17:29</a> |
| mizmo | giarc: they should be consistent | <a href="#t17:29" class="time">17:29</a> |
| markg85 | a reason why people don't look at the install guide (didn't look at it myself so just guessing here) is that there is so much text in it that it scares people away | <a href="#t17:29" class="time">17:29</a> |
| ricky | I agree with markg85 | <a href="#t17:29" class="time">17:29</a> |
| giarc | mizmo, right, ok | <a href="#t17:29" class="time">17:29</a> |
| mizmo | people don't want to read text on get.fpo. they want to get f. :) | <a href="#t17:29" class="time">17:29</a> |
| hiemanshu | markg85, +1 | <a href="#t17:29" class="time">17:29</a> |
| mizmo | any solution that involves users reading more text = FAIL | <a href="#t17:29" class="time">17:29</a> |
| hiemanshu | people hate to READ | <a href="#t17:30" class="time">17:30</a> |
| ricky | Here's a sad fact: | <a href="#t17:30" class="time">17:30</a> |
| markg85 | i personally always move away from pages that have way to much text :P | <a href="#t17:30" class="time">17:30</a> |
| ricky | The table of contents of our install guide: <a href="http://docs.fedoraproject.org/install-guide/f11/en-US/html/">http://docs.fedoraproject.org/install-guide/f11/en-US/html/</a> is about as long as the entire openSUSE Live CD install guide: <a href="http://en.opensuse.org/Installation/11.1_Live_CD">http://en.opensuse.org/Installation/11.1_Live_CD</a> | <a href="#t17:30" class="time">17:30</a> |
| markg85 | specially if they start with a bunch of notices at the top | <a href="#t17:30" class="time">17:30</a> |
| mizmo | yet people keep propposing we add more text ot the screen :) | <a href="#t17:30" class="time">17:30</a> |
| ricky | And their install guide is filled with screenshots too. | <a href="#t17:30" class="time">17:30</a> |
| ricky | I want an install guide like that :-) | <a href="#t17:30" class="time">17:30</a> |
| mizmo | ricky: that's insane | <a href="#t17:30" class="time">17:30</a> |
| ricky | (And here's their DVD install guide: <a href="http://en.opensuse.org/Installation/11.1_DVD_Install">http://en.opensuse.org/Installation/11.1_DVD_Install</a>) | <a href="#t17:30" class="time">17:30</a> |
| hiemanshu | ricky, i could try that | <a href="#t17:30" class="time">17:30</a> |
| ricky | To anybody interested on working on something like that: Please make sure to talk to the docs team first | <a href="#t17:31" class="time">17:31</a> |
| ricky | I wouldn't want to start any documentation projects without letting them know and hearing their thoughts on it first. | <a href="#t17:31" class="time">17:31</a> |
| hiemanshu | ricky, i ll do this part, i ll write the install Docs with Screens | <a href="#t17:31" class="time">17:31</a> |
| giarc | ricky, wow, that is striking | <a href="#t17:31" class="time">17:31</a> |
| mizmo | the docs team is planning a new system for displaying the docs | <a href="#t17:32" class="time">17:32</a> |
| markg85 | ricky, well.. you can make all the screenshots prior to making the documentation..(or not?) | <a href="#t17:32" class="time">17:32</a> |
| hiemanshu | markg85, you can | <a href="#t17:32" class="time">17:32</a> |
| markg85 | hiemanshu, if i install fedora i might just do that :D | <a href="#t17:32" class="time">17:32</a> |
| ricky | markg85: Making the screenshots shouldn't be an issue, the main thing would be communicating to the docs team about this | <a href="#t17:32" class="time">17:32</a> |
| hiemanshu | markg85, we can take this up together. what say? | <a href="#t17:32" class="time">17:32</a> |
| markg85 | hiemanshu, ask me again after my exams in just over one week | <a href="#t17:33" class="time">17:33</a> |
| mizmo | okay so, so far our goals for f12 are: | <a href="#t17:33" class="time">17:33</a> |
| mizmo | - make get.fpo better for technical users | <a href="#t17:33" class="time">17:33</a> |
| ricky | mizmo: Do you know if they're looking at changing the format of the docs, or just the infrastructure for the docs site? | <a href="#t17:33" class="time">17:33</a> |
| mizmo | - makes docs.fpo better | <a href="#t17:33" class="time">17:33</a> |
| mizmo | ricky: not sure :( i would imagine both | <a href="#t17:33" class="time">17:33</a> |
| ricky | Hopefully :-) | <a href="#t17:33" class="time">17:33</a> |
| mizmo | do we have any other goals for f12 | <a href="#t17:34" class="time">17:34</a> |
| mizmo | i have one :) | <a href="#t17:34" class="time">17:34</a> |
| mizmo | - improve www.fpo. it's a bit sparse right now. we could have a bit more information on what fedora is and why you'd want to use it. a section with profiles of real fedora users with picutres | <a href="#t17:34" class="time">17:34</a> |
| markg85 | mizmo, just wondering.. are there plans for a new decoration theme in fedora 12? | <a href="#t17:34" class="time">17:34</a> |
| -!- mchua_ [n=mchua@nat/redhat/x-ffcdfe22a665039d] has joined #fedora-websites | <a href="#t17:35" class="time">17:35</a> | |
| ricky | - Get a decision-making process that we can stick to :-) | <a href="#t17:35" class="time">17:35</a> |
| hiemanshu | mizmo, a user gallery | <a href="#t17:35" class="time">17:35</a> |
| mizmo | markg85: what do you mean by decoration theme? | <a href="#t17:35" class="time">17:35</a> |
| markg85 | mizmo, a nodoka replacement? | <a href="#t17:35" class="time">17:35</a> |
| mizmo | hiemanshu: yeh exactly! a gallery of real fedora users, where you can learn how fedora changed their life kind of thing | <a href="#t17:35" class="time">17:35</a> |
| * mchua_ wonders if she got disconnected, and sheepishly asks for another backlog. | <a href="#t17:35" class="time">17:35</a> | |
| mizmo | markg85: not afaik | <a href="#t17:35" class="time">17:35</a> |
| * mchua_ vows to get a proxy this weekend. | <a href="#t17:35" class="time">17:35</a> | |
| ricky | mchua_: <a href="http://ricky.fedorapeople.org/2009-06-19.log">http://ricky.fedorapeople.org/2009-06-19.log</a> | <a href="#t17:35" class="time">17:35</a> |
| giarc | ricky, +1 | <a href="#t17:35" class="time">17:35</a> |
| mchua_ | Thanks again, ricky. | <a href="#t17:36" class="time">17:36</a> |
| -!- mchua [n=mchua@host232.155.212.137.conversent.net] has quit Nick collision from services. | <a href="#t17:36" class="time">17:36</a> | |
| -!- mchua_ is now known as mchua | <a href="#t17:36" class="time">17:36</a> | |
| mizmo | okay so we have 4 goals so far | <a href="#t17:36" class="time">17:36</a> |
| markg85 | mizmo, oke. i really would like to see something else other then that blue stuff | <a href="#t17:36" class="time">17:36</a> |
| mizmo | 1) get.fpo | <a href="#t17:36" class="time">17:36</a> |
| mizmo | 2) www.fpo | <a href="#t17:36" class="time">17:36</a> |
| mizmo | 3) docs.fpo | <a href="#t17:36" class="time">17:36</a> |
| mizmo | 4) decision process | <a href="#t17:36" class="time">17:36</a> |
| hiemanshu | mizmo, something like where people can add their own images and say something | <a href="#t17:36" class="time">17:36</a> |
| ricky | mizmo: Also join.fp.o :-) | <a href="#t17:36" class="time">17:36</a> |
| hiemanshu | mizmo, 5) User Gallery | <a href="#t17:36" class="time">17:36</a> |
| mizmo | markg85: okay but right now we're having a websites meeting. i suggest bringing that up on the design team list | <a href="#t17:36" class="time">17:36</a> |
| ricky | One thing I'd like everybody to keep in mind is that everything we do has to be translatable. | <a href="#t17:37" class="time">17:37</a> |
| markg85 | mizmo, ^_^ sorry, for me websites is designing as well | <a href="#t17:37" class="time">17:37</a> |
| ricky | I know it can feel limiting at times, but I really don't want to move back to relying on things that are 100% English-only. | <a href="#t17:37" class="time">17:37</a> |
| hiemanshu | ricky, is there a Geo IP redirector? | <a href="#t17:38" class="time">17:38</a> |
| mizmo | ricky: has anything we've proposed so far been problematic for translation? | <a href="#t17:38" class="time">17:38</a> |
| mizmo | ricky: or is just the timing so we can get translations out a concern? | <a href="#t17:38" class="time">17:38</a> |
| ricky | mizmo: I haven't sen anything yet other than RSS feeds. | <a href="#t17:39" class="time">17:39</a> |
| mizmo | k | <a href="#t17:39" class="time">17:39</a> |
| mchua | current list o' goal-ness: get.fpo, www.fpo, docs.fpo, decision process, user gallery, join.fpo, translation. | <a href="#t17:39" class="time">17:39</a> |
| ricky | News is a tough one. I'd love to have news on the site, but I wouldn't want english-only news front and center on the Chinese home page. | <a href="#t17:39" class="time">17:39</a> |
| * markg85 note to self: install fedora 11 in dutch and see how much is really dutch | <a href="#t17:39" class="time">17:39</a> | |
| mizmo | any other ideas? or should we move on to prioritization? | <a href="#t17:39" class="time">17:39</a> |
| hiemanshu | mizmo, Geo IP redirector | <a href="#t17:40" class="time">17:40</a> |
| mchua | +1 prioritization | <a href="#t17:40" class="time">17:40</a> |
| ricky | hiemanshu: That's probably an infrastructure team thing :-) | <a href="#t17:40" class="time">17:40</a> |
| hiemanshu | thats with the websites right? must be wrong :P | <a href="#t17:40" class="time">17:40</a> |
| ricky | We try to keep the pages totally static so that it's a breeze on release day though. | <a href="#t17:40" class="time">17:40</a> |
| mizmo | i think maybe get.fpo should be a top priority cuz we get so many complaints | <a href="#t17:41" class="time">17:41</a> |
| ricky | mizmo: +1 to moving on prioritization | <a href="#t17:41" class="time">17:41</a> |
| hiemanshu | ricky, auto redirect to the local language, is it there or needs to be implemented? | <a href="#t17:41" class="time">17:41</a> |
| ricky | 17:41:06 < mizmo> i think maybe get.fpo should be a top priority cuz we get so many complaints | <a href="#t17:41" class="time">17:41</a> |
| mizmo | decision process too | <a href="#t17:41" class="time">17:41</a> |
| ricky | hiemanshu: That's implemented in that if you set your language priorities in your browser, you'll see the right one automatically. | <a href="#t17:41" class="time">17:41</a> |
| mchua | mizmo: maybe we should have everyone reorder the list the way they think it should be prioritised | <a href="#t17:41" class="time">17:41</a> |
| mchua | and see where we end up | <a href="#t17:41" class="time">17:41</a> |
| hiemanshu | mizmo, make the goals list and we know how to prioritize them | <a href="#t17:42" class="time">17:42</a> |
| mchua | hiemanshu: get.fpo | <a href="#t17:42" class="time">17:42</a> |
| mchua | www.fpo | <a href="#t17:42" class="time">17:42</a> |
| mchua | docs.fpo | <a href="#t17:42" class="time">17:42</a> |
| mchua | decision process | <a href="#t17:42" class="time">17:42</a> |
| mchua | user gallery | <a href="#t17:42" class="time">17:42</a> |
| mchua | join.fpo | <a href="#t17:42" class="time">17:42</a> |
| ricky | Here's my tohught: get.fpo, decision process, docs.fpo, join.fpo, www.fpo, user gallery (and translation is something that happens throughout) | <a href="#t17:43" class="time">17:43</a> |
| mchua | translation | <a href="#t17:43" class="time">17:43</a> |
| ricky | **thought | <a href="#t17:43" class="time">17:43</a> |
| mchua | (that was a list, not my ordering) | <a href="#t17:43" class="time">17:43</a> |
| mizmo | ricky: i'd bump www a bit higher just because of its prominence | <a href="#t17:43" class="time">17:43</a> |
| mizmo | maybe swap docs and www | <a href="#t17:43" class="time">17:43</a> |
| mchua | my ordering is join.fpo | <a href="#t17:43" class="time">17:43</a> |
| mchua | decision process | <a href="#t17:43" class="time">17:43</a> |
| mchua | get.fpo | <a href="#t17:43" class="time">17:43</a> |
| mchua | docs.fpo | <a href="#t17:43" class="time">17:43</a> |
| mchua | www.fpo | <a href="#t17:43" class="time">17:43</a> |
| mchua | user gallery | <a href="#t17:43" class="time">17:43</a> |
| mchua | translation | <a href="#t17:43" class="time">17:43</a> |
| ricky | mizmo: I'm trying to think in terms of "what does a user want to do that's currently hard for them to do" | <a href="#t17:43" class="time">17:43</a> |
| hiemanshu | get.fpo, decision process, www.fpo, docs.fpo, join.fpo, user gallery | <a href="#t17:44" class="time">17:44</a> |
| mchua | markg85, thoughts? | <a href="#t17:44" class="time">17:44</a> |
| markg85 | my order: get.fpo www.fpo join.fpo user gallery decision process | <a href="#t17:44" class="time">17:44</a> |
| markg85 | translation | <a href="#t17:44" class="time">17:44</a> |
| mchua | I think we have a clear front-runner with get.fpo. | <a href="#t17:44" class="time">17:44</a> |
| ricky | I see "get documentation/help" as a more important task than "find out what Fedora is" for now, although maybe I can be convinced otherwise :-) | <a href="#t17:44" class="time">17:44</a> |
| mchua | does anyone other than me think something is more important than get.fpo in terms of work-on priority? | <a href="#t17:45" class="time">17:45</a> |
| mchua | I'm *totally* willing to be convinced of this. | <a href="#t17:45" class="time">17:45</a> |
| * giarc needs to run, can some one post a log of the meeting so I can catch up? | <a href="#t17:45" class="time">17:45</a> | |
| ricky | giarc: Will do, thanks for coming! | <a href="#t17:45" class="time">17:45</a> |
| markg85 | and why. get and www are identical to me. join.fpo is slightly more annoying | <a href="#t17:45" class="time">17:45</a> |
| giarc | thanks ricky | <a href="#t17:45" class="time">17:45</a> |
| ricky | mizmo: www is talking about the main page more, while get is specifically about the get-fedora page | <a href="#t17:45" class="time">17:45</a> |
| ricky | join.fp.o and docs.fp.o are both thing that span over into a bunch of other groups in the Fedora Project. | <a href="#t17:46" class="time">17:46</a> |
| hiemanshu | ricky, my order is in what users actually do | <a href="#t17:46" class="time">17:46</a> |
| mizmo | ricky: if the front page of fpo isn't appealing, you wont have people needing to get help with it | <a href="#t17:46" class="time">17:46</a> |
| mizmo | :) | <a href="#t17:47" class="time">17:47</a> |
| hiemanshu | mizmo, i dont think most of the people would even join, you might get people to docs and not join | <a href="#t17:47" class="time">17:47</a> |
| ricky | I guess, but I don't really see our front page as the way that most people find out what Fedora is right now (although that could be seen as a problem that we need to fix) | <a href="#t17:47" class="time">17:47</a> |
| -!- Sonar_Guy [n=Who@fedora/sonarguy] has joined #fedora-websites | <a href="#t17:47" class="time">17:47</a> | |
| * mchua notes that ultimately, people will vote with their feet, so the stuff that happens is the stuff individuals are going to want to work on themselves | <a href="#t17:47" class="time">17:47</a> | |
| * mchua looks back at votes | <a href="#t17:47" class="time">17:47</a> | |
| ricky | Rather, I think most people get directed to fp.o through things like news sites, or other things which is where they first find out exactly what Fedoar is. | <a href="#t17:47" class="time">17:47</a> |
| ricky | **Fedora | <a href="#t17:48" class="time">17:48</a> |
| markg85 | people please know the first impressions rule | <a href="#t17:48" class="time">17:48</a> |
| markg85 | they are what makes a person join or leave | <a href="#t17:48" class="time">17:48</a> |
| mizmo | ricky: it is the 'official' definition of what fedora is though (or at least it should be) because we can't control what news media outlets explain us as (and sometimes they get it quite wrong) | <a href="#t17:49" class="time">17:49</a> |
| markg85 | right now (just being fair) my first impressions with both the fedora site and distribution are far from good and i'm in this world for a few years | <a href="#t17:49" class="time">17:49</a> |
| ricky | True. I don't think I'm fully clear on exactly what we're trying to do with the front page | <a href="#t17:49" class="time">17:49</a> |
| mchua | I agree with markg85; first impressions are important. | <a href="#t17:49" class="time">17:49</a> |
| markg85 | fedora runs good one just ONE pc here (and there are roughly 6) | <a href="#t17:49" class="time">17:49</a> |
| hiemanshu | To tell the truth fp.o just isnt attractive | <a href="#t17:49" class="time">17:49</a> |
| mchua | So, I tallied up all our priority lists. | <a href="#t17:49" class="time">17:49</a> |
| mchua | get.fpo is the front-runner. decision process is not far behind. www.fpo, docs.fpo, and join.fpo seem more or less on par... not many people incredibly excited about translation or user gallery, but that could be a small-team-takes-it-on thing. | <a href="#t17:49" class="time">17:49</a> |
| markg85 | so making that very abstract it means that fedora runs as intended on 1 out of every 7 pc's!! that's not good at all | <a href="#t17:50" class="time">17:50</a> |
| mchua | all these are separate pieces - separate pieces that interact, but separate pieces. | <a href="#t17:50" class="time">17:50</a> |
| mizmo | ricky: well right now the front page is kind of bare. visiting it, you don't really get an idea of why you would want to use fedora or what it can do for you | <a href="#t17:50" class="time">17:50</a> |
| ricky | markg85: That is probably a development issue and maybe not websites though. | <a href="#t17:50" class="time">17:50</a> |
| mizmo | ricky: i'd like it to be more like the fedora community tour page | <a href="#t17:50" class="time">17:50</a> |
| ricky | I'd love to have something like that. | <a href="#t17:50" class="time">17:50</a> |
| mizmo | <a href="https://admin.fedoraproject.org/community/pages/tour/">https://admin.fedoraproject.org/community/pages/tour/</a> | <a href="#t17:51" class="time">17:51</a> |
| mchua | question: does anybody want to run point on the fp.o page? | <a href="#t17:51" class="time">17:51</a> |
| markg85 | ricky, i know but that issue ends up by a person going to the fedora website | <a href="#t17:51" class="time">17:51</a> |
| mizmo | we break it down and explain what YOU can do with it | <a href="#t17:51" class="time">17:51</a> |
| markg85 | and that's where they find... not what they are looking for: answers | <a href="#t17:51" class="time">17:51</a> |
| ricky | All right, so I'll agree with www being before docs then :-) | <a href="#t17:51" class="time">17:51</a> |
| * Cheshirc wanders in | <a href="#t17:52" class="time">17:52</a> | |
| ricky | So what's next now that we have some priorities? Should we start discussing each in detail and getting some research into what we need? | <a href="#t17:52" class="time">17:52</a> |
| mchua | my impression of current order: get.fpo is the front-runner. decision process is not far behind. www.fpo, docs.fpo, and then join.fpo in that order. nobody really picking up on translation or user gallery. | <a href="#t17:52" class="time">17:52</a> |
| mizmo | sounds right mchua | <a href="#t17:52" class="time">17:52</a> |
| mchua | well, i think we need to figure out who's going to run point on each thing. | <a href="#t17:52" class="time">17:52</a> |
| markg85 | and please all of you look with a objective view at fp.o and tell me what you see | <a href="#t17:52" class="time">17:52</a> |
| mizmo | mchua: well except i think translation is a thread that runs across all of them | <a href="#t17:52" class="time">17:52</a> |
| ricky | mchua: Translation isn't so much of a task on its own, just something to keep in mind throughout. | <a href="#t17:52" class="time">17:52</a> |
| mchua | because right now we have N cooks trying to make N pots of soup. | <a href="#t17:52" class="time">17:52</a> |
| markg85 | what i see: a superman packager !!! and a very short description of fedora | <a href="#t17:53" class="time">17:53</a> |
| mchua | ok, then someone should be on point for making sure translation is incorporated into all projects. | <a href="#t17:53" class="time">17:53</a> |
| mchua | else we'll drop translation and then look back at f12 and go *wap* why did we forget? | <a href="#t17:53" class="time">17:53</a> |
| mizmo | ricky: do you have those top 10 tasks for www.fpo handy somewhere? | <a href="#t17:53" class="time">17:53</a> |
| mizmo | i vaguely remember them being on your fedora people site? | <a href="#t17:53" class="time">17:53</a> |
| ricky | Let me find those | <a href="#t17:53" class="time">17:53</a> |
| mchua | the problem i've seen here in the brief time I've been around is that people keep colliding into each others work | <a href="#t17:53" class="time">17:53</a> |
| hiemanshu | mizmo, one immediate thing is to update MediaWiki | <a href="#t17:54" class="time">17:54</a> |
| mchua | <a href="http://ricky.fedorapeople.org/fedora-web">http://ricky.fedorapeople.org/fedora-web</a> | <a href="#t17:54" class="time">17:54</a> |
| mchua | mizmo: ^ | <a href="#t17:54" class="time">17:54</a> |
| ricky | Ah, cool. | <a href="#t17:54" class="time">17:54</a> |
| ricky | THanks | <a href="#t17:54" class="time">17:54</a> |
| ricky | hiemanshu: That's kind of a separate issue that will have to be discussed with Infrastructure | <a href="#t17:54" class="time">17:54</a> |
| ricky | But like I told you, it's not very likely unless there is a serious pressing need. | <a href="#t17:54" class="time">17:54</a> |
| markg85 | mizmo, could you tell me what you currently like on fp.o? | <a href="#t17:54" class="time">17:54</a> |
| mchua | markg85, hiemanshu, can we hang on a moment until we figure out who's working on what? | <a href="#t17:55" class="time">17:55</a> |
| mizmo | so our get.fpo goal we're prioritized highly today | <a href="#t17:55" class="time">17:55</a> |
| hiemanshu | ricky, following the Fedora rule, latest and greatest | <a href="#t17:55" class="time">17:55</a> |
| * ricky certainly likes get-fedora. It's one of the pages that we've put the most work/polish into. | <a href="#t17:55" class="time">17:55</a> | |
| mizmo | is #8 on the fedora-web list | <a href="#t17:55" class="time">17:55</a> |
| * markg85 waits... | <a href="#t17:55" class="time">17:55</a> | |
| mchua | thanks markg85 :) | <a href="#t17:55" class="time">17:55</a> |
| mizmo | we've got #1 on that list done | <a href="#t17:55" class="time">17:55</a> |
| mizmo | #2 is our docs.fpo item from today | <a href="#t17:55" class="time">17:55</a> |
| * hiemanshu sits next to markg85 | <a href="#t17:55" class="time">17:55</a> | |
| mizmo | #3 is the www.fpo item, and #5 is also | <a href="#t17:55" class="time">17:55</a> |
| mizmo | #4 is join .fpo | <a href="#t17:55" class="time">17:55</a> |
| mizmo | #6 - what's happening in fedora - we haven't really identified today so we can drop it in priority | <a href="#t17:56" class="time">17:56</a> |
| mchua | even after looking at the old list, I'd go by the ordering we chose before. It seems more... pertinent to right now. | <a href="#t17:56" class="time">17:56</a> |
| mizmo | #9 fedora bling - we didnt bring that up - but i think it's good too. if we had something like spreadfirefox.com but for fedora | <a href="#t17:56" class="time">17:56</a> |
| mizmo | mchua: i think #8 in the old list needs to be #1 now though | <a href="#t17:56" class="time">17:56</a> |
| hiemanshu | mizmo, fedora shop? | <a href="#t17:56" class="time">17:56</a> |
| ricky | Yeah. | <a href="#t17:57" class="time">17:57</a> |
| mchua | mizmo: yeah, I meant the one we just did in this channel with get.fp.o as #1 | <a href="#t17:57" class="time">17:57</a> |
| mizmo | mchua: oh i agree we should stick with the ordering we came up with today | <a href="#t17:57" class="time">17:57</a> |
| mizmo | mchua: sorry i misunderstood ya | <a href="#t17:57" class="time">17:57</a> |
| ricky | hiemanshu: Hehe, that's another thing that has been discussed with fedora marketing, but not much luck :-( I'd love to see the efforts for that start up again | <a href="#t17:57" class="time">17:57</a> |
| mchua | the old list has tonnes of resources though which is great | <a href="#t17:57" class="time">17:57</a> |
| hiemanshu | ricky, i can help push up people | <a href="#t17:57" class="time">17:57</a> |
| ricky | hiemanshu: spevack is one person that I remember heading that up, he can probably get you in touch with whoever has the latest on that. | <a href="#t17:58" class="time">17:58</a> |
| mizmo | i would like to take point on get.fpo | <a href="#t17:58" class="time">17:58</a> |
| mchua | so our ordering from the discussion just now is get.fpo, decision process, www.fpo, docs.fpo, and then join.fpo, translation, and user gallery. | <a href="#t17:58" class="time">17:58</a> |
| hiemanshu | mchua, user gallery one step up please | <a href="#t17:58" class="time">17:58</a> |
| ricky | Decision process is still a tough one that will be a part of everything else :-( | <a href="#t17:59" class="time">17:59</a> |
| mchua | hiemanshu: get.fpo, decision process, www.fpo, docs.fpo, and then join.fpo, user gallery, and translation. though things won't be done unless someone steps up like mizmo just did for get.fp.o. | <a href="#t17:59" class="time">17:59</a> |
| mchua | +1 to mizmo taking point on get.fp.o, btw. :) | <a href="#t18:00" class="time">18:00</a> |
| ricky | Mind if we discuss some of the properties of a good decision making process for a moment? | <a href="#t18:00" class="time">18:00</a> |
| mchua | can we have other people step up to take point on some other stuff first? | <a href="#t18:00" class="time">18:00</a> |
| hiemanshu | mchua, i am a PHP guy and go the user gallery | <a href="#t18:00" class="time">18:00</a> |
| mchua | hiemanshu: you want to take point on the user gallery? | <a href="#t18:00" class="time">18:00</a> |
| hiemanshu | do the* | <a href="#t18:00" class="time">18:00</a> |
| ricky | I'll gladly take docs.fp.o and decision process | <a href="#t18:00" class="time">18:00</a> |
| mizmo | good decision making process != saying yes to every suggestion, because that's like making dinner by dumping out the contents of your fridge into a pot. | <a href="#t18:00" class="time">18:00</a> |
| hiemanshu | mchua, yes | <a href="#t18:00" class="time">18:00</a> |
| markg85 | mchua, i'm joist going for www.fp.o and get.fp.o | <a href="#t18:01" class="time">18:01</a> |
| markg85 | just* | <a href="#t18:01" class="time">18:01</a> |
| hiemanshu | i ll help markg85 with www.fp.o | <a href="#t18:01" class="time">18:01</a> |
| mchua | sweet. okay, we have mizmo on get.fp.o, hiemanshu on the user gallery, markg85 on www.fp.o and working with mizmo on get.fp.o, ricky on decisionmaking process and docs.fp.o, which is perfect because I wanted to work on join.fp.o. | <a href="#t18:01" class="time">18:01</a> |
| mizmo | id like to take the make www.fpo have a section like the fedora community tour section task but its a subtask of www.fpo | <a href="#t18:01" class="time">18:01</a> |
| markg85 | hiemanshu, add your name to it on the wiki plz | <a href="#t18:01" class="time">18:01</a> |
| mchua | nobody is doing translation yet. | <a href="#t18:01" class="time">18:01</a> |
| ricky | Some properties I desire of a decision making process: | <a href="#t18:01" class="time">18:01</a> |
| hiemanshu | markg85, where? | <a href="#t18:01" class="time">18:01</a> |
| ricky | 1) Not a dictatorship :-) | <a href="#t18:02" class="time">18:02</a> |
| markg85 | hiemanshu, brainstorms? | <a href="#t18:02" class="time">18:02</a> |
| ricky | 2) Bad ideas (for some definition of bad) get rejected | <a href="#t18:02" class="time">18:02</a> |
| ricky | 3) Good ideas (for some definition of good) don't get sidelined | <a href="#t18:02" class="time">18:02</a> |
| * markg85 would like the time now | <a href="#t18:02" class="time">18:02</a> | |
| * mchua checks list: mizmo on get.fp.o, with markg85's help, hiemanshu on the user gallery, markg85 on www.fp.o with hiemanshu's help, ricky on decisionmaking process and docs.fp.o, mchua on join.fp.o, translation as a "we need to find someone." | <a href="#t18:02" class="time">18:02</a> | |
| mizmo | backseat driving is undesirable i think | <a href="#t18:02" class="time">18:02</a> |
| mchua | markg85: it's 2:04pm, or 18:04 UTC if I did math correctly. | <a href="#t18:03" class="time">18:03</a> |
| ricky | The definitions of good and bad will be deeply tied into what the goal and the target audience of the website is. | <a href="#t18:03" class="time">18:03</a> |
| mchua | 2:04 for me in Boston, EST. | <a href="#t18:03" class="time">18:03</a> |
| * markg85 is not pointing to the real time :P | <a href="#t18:03" class="time">18:03</a> | |
| * mchua is confused | <a href="#t18:03" class="time">18:03</a> | |
| hiemanshu | 23:34 here | <a href="#t18:03" class="time">18:03</a> |
| * markg85 means the time to propose something here | <a href="#t18:03" class="time">18:03</a> | |
| mizmo | ricky: which we still haven't really solidifed on :( | <a href="#t18:03" class="time">18:03</a> |
| ricky | markg85: Propose away. | <a href="#t18:03" class="time">18:03</a> |
| markg85 | oke | <a href="#t18:04" class="time">18:04</a> |
| ricky | mizmo: Yeah. It's important that we do so that we have a basis for saying yes and no to things instead of bickering endlessly :-/ | <a href="#t18:04" class="time">18:04</a> |
| markg85 | mizmo, ricky mchua hiemanshu : i would like you all to go to fp.o and get.fp.o and write down what you really like. because the rest is what has to change or go | <a href="#t18:04" class="time">18:04</a> |
| * hiemanshu will be back in 10 mins | <a href="#t18:05" class="time">18:05</a> | |
| markg85 | personally i like nothing on www.fp.o and just a few things in get.fp.o | <a href="#t18:05" class="time">18:05</a> |
| ricky | That's kind of subjective. | <a href="#t18:05" class="time">18:05</a> |
| ricky | I'd rather have the purpose/audience in mind for the website before doing something like ths. | <a href="#t18:05" class="time">18:05</a> |
| mchua | markg85: +1 - I'll do it, can you shoot out an email to the list reminding people? some folks couldn't make this meeting but would probably chime in. | <a href="#t18:05" class="time">18:05</a> |
| markg85 | ricky, it is but if we combine all our opinions ^_^ | <a href="#t18:05" class="time">18:05</a> |
| mizmo | i dont think thats useful if we dont know who our audience is | <a href="#t18:05" class="time">18:05</a> |
| mchua | ricky: anything we do would be subjective; I don't think it's going to get us everything, but I think it's a good starting point. | <a href="#t18:05" class="time">18:05</a> |
| mizmo | we should rather, for each target audience user type, summarize what that type of user would like vs wouldn't like about the site | <a href="#t18:06" class="time">18:06</a> |
| ricky | I'd rather phrase the like/dislike thing as: X user in our target audience will have a hard time doing Y task in our website's purpose. | <a href="#t18:06" class="time">18:06</a> |
| mizmo | if www.fpo was targeted for me, it would be mostly blank | <a href="#t18:06" class="time">18:06</a> |
| ricky | Instead of "X is ugly, I don't like it" | <a href="#t18:06" class="time">18:06</a> |
| mchua | we're also users. we're not the only users, and we're a special weird involved type of user, but we're users, and this will also help us get our assumptions on the table. | <a href="#t18:06" class="time">18:06</a> |
| hiemanshu | mizmo, as i said, make it so anyone who reads likes it | <a href="#t18:06" class="time">18:06</a> |
| mizmo | the user classifications we could target | <a href="#t18:06" class="time">18:06</a> |
| ricky | I think that is totally impossible :-) | <a href="#t18:06" class="time">18:06</a> |
| mchua | besides, if markg85 is running with this, then that's his prerogative. :) | <a href="#t18:07" class="time">18:07</a> |
| mizmo | (1) i've never used linux before. i don't know what IRC is. i heard i should try it because it would make bill gates cry. | <a href="#t18:07" class="time">18:07</a> |
| markg85 | i just think this would be a very nice point to start with | <a href="#t18:07" class="time">18:07</a> |
| mizmo | (2) i've used linux before, but not fedora. you'll have to win me over. | <a href="#t18:07" class="time">18:07</a> |
| markg85 | mchua, yes i will run this | <a href="#t18:07" class="time">18:07</a> |
| mizmo | (3) i've been using fedora 4eva and it's awesome! | <a href="#t18:07" class="time">18:07</a> |
| mizmo | i think depending on which section we've got, we'd care about 1, 2, or 3 in a different priority order | <a href="#t18:07" class="time">18:07</a> |
| mchua | mizmo, ricky - well, markg85 isn't saying "everybody has to do this," he's saying "if you could do this please, it would help me think about some things I might not be considering just yet." | <a href="#t18:07" class="time">18:07</a> |
| mizmo | for www.fpo we would care more about 1 & 2 | <a href="#t18:08" class="time">18:08</a> |
| ricky | Maybe what we need is a feedback form or email. | <a href="#t18:08" class="time">18:08</a> |
| ricky | Like: Let us know what you're doing with Fedora at blah@fp.o | <a href="#t18:08" class="time">18:08</a> |
| markg85 | mchua, i will add that task to.. myself on the tasklist | <a href="#t18:08" class="time">18:08</a> |
| ricky | Because I have absolutely no idea what types of users are | <a href="#t18:08" class="time">18:08</a> |
| mchua | if people want to do that, they can do that. markg85 was telling us what he's planning on doing with the project he offered to run point on. | <a href="#t18:08" class="time">18:08</a> |
| hiemanshu | We should have something on first page like, here for the first time, back again | <a href="#t18:09" class="time">18:09</a> |
| mizmo | im not going to do it because i dont think my opinion is very useful | <a href="#t18:09" class="time">18:09</a> |
| mizmo | :( | <a href="#t18:09" class="time">18:09</a> |
| hiemanshu | i ll do it | <a href="#t18:09" class="time">18:09</a> |
| mchua | similarly, if mizmo asks for a hand on get.fp.o, she'll ask us to pitch in, and ricky was asking for input on decisionmaking a few minutes ago and people were chiming in... | <a href="#t18:09" class="time">18:09</a> |
| markg85 | I would say: first ask it on the websites list. if the feedback is to diverse there (thus not useful) then move it to a more populated list like jsut fedora | <a href="#t18:09" class="time">18:09</a> |
| hiemanshu | and help markg85 with that | <a href="#t18:09" class="time">18:09</a> |
| mizmo | the problem is that | <a href="#t18:10" class="time">18:10</a> |
| mizmo | if you dont think about the audience you are trying to reach | <a href="#t18:10" class="time">18:10</a> |
| mizmo | and you just randomly ask people | <a href="#t18:10" class="time">18:10</a> |
| mizmo | your results are going to be way skewed | <a href="#t18:10" class="time">18:10</a> |
| mizmo | and probably not in a way you would want them to be if you had actually thought about what audience you want to reach first | <a href="#t18:10" class="time">18:10</a> |
| mizmo | if you know the audience you want to reach, then you can survey THEM | <a href="#t18:10" class="time">18:10</a> |
| ricky | I don't think we're applying the soon-to-be extant decision making process here. | <a href="#t18:10" class="time">18:10</a> |
| mizmo | and weigh the results appropriately based on who answered the question | <a href="#t18:10" class="time">18:10</a> |
| * ricky agrees with mizmo | <a href="#t18:10" class="time">18:10</a> | |
| mizmo | and how high on your priority list that user class is | <a href="#t18:10" class="time">18:10</a> |
| mizmo | eg | <a href="#t18:10" class="time">18:10</a> |
| hiemanshu | mizmo, +1 | <a href="#t18:11" class="time">18:11</a> |
| mchua | I agree, and I also think that this shouldn't stop markg85 from moving forward. | <a href="#t18:11" class="time">18:11</a> |
| mizmo | if linus torvalds tells me he thinks get.fpo sucks | <a href="#t18:11" class="time">18:11</a> |
| mizmo | but i want to target people who have never used linux before | <a href="#t18:11" class="time">18:11</a> |
| markg85 | mizmo, i agree and disagree | <a href="#t18:11" class="time">18:11</a> |
| mizmo | than linus' opinion is probably not something i should weigh as heavily as the girl walking down the sidewalk | <a href="#t18:11" class="time">18:11</a> |
| mizmo | who doesnt use linux | <a href="#t18:11" class="time">18:11</a> |
| markg85 | mizmo, you just have to start somewhere | <a href="#t18:11" class="time">18:11</a> |
| mchua | markg85 + 1 | <a href="#t18:11" class="time">18:11</a> |
| mizmo | markg85: you have to know where you are going before you can start walking there | <a href="#t18:11" class="time">18:11</a> |
| mizmo | if you head off without a map you dont know if you're going to end up anywhere useful and how much time you are going to waste going the wrong way | <a href="#t18:12" class="time">18:12</a> |
| ricky | I just don't want to have flamewars based on subjective opinions start up. Please :-) | <a href="#t18:12" class="time">18:12</a> |
| mchua | mizmo + 1 also. I think the "know what you're aiming for" thing is a very good thing. I also think that knowing that *while* starting means you'll eventually figure it out. | <a href="#t18:12" class="time">18:12</a> |
| markg85 | mizmo, the users don't mather for me because every single one will do fine. users from websites: fine. users from documentation: fine.. anyone is fine so there is no real target | <a href="#t18:12" class="time">18:12</a> |
| mchua | or rather, that if you know you don't know, and start moving with that in mind, you'll soon know. | <a href="#t18:12" class="time">18:12</a> |
| mizmo | huh | <a href="#t18:12" class="time">18:12</a> |
| * mchua blinks, reboots mel.speaks_english module | <a href="#t18:13" class="time">18:13</a> | |
| mizmo | markg85: if our target was beginning linux users, the resulting design would be a million miles away from a design primarily targeted for experience technical users | <a href="#t18:13" class="time">18:13</a> |
| ricky | I think we have some fundamentally conflicting opinions about what information to use and what information to discard thoguh. | <a href="#t18:13" class="time">18:13</a> |
| ricky | **though | <a href="#t18:13" class="time">18:13</a> |
| -!- onekopaka_away is now known as onekopaka | <a href="#t18:13" class="time">18:13</a> | |
| onekopaka | hello. | <a href="#t18:13" class="time">18:13</a> |
| mizmo | i mean heres the thing right | <a href="#t18:13" class="time">18:13</a> |
| * mchua has to leave in 15 minutes. | <a href="#t18:13" class="time">18:13</a> | |
| mizmo | what i do, is design UI | <a href="#t18:13" class="time">18:13</a> |
| mizmo | and there's a process to it | <a href="#t18:13" class="time">18:13</a> |
| mchua | hey onekopaka - you came in the middle of a somewhat frantic meeting. :) | <a href="#t18:14" class="time">18:14</a> |
| mizmo | and one of the essential things you have to identify up front, is who is this UI for | <a href="#t18:14" class="time">18:14</a> |
| markg85 | mizmo, you are right but right now i see fp.o as (boldly said) useless. so in my point of view anything and any input will do fine | <a href="#t18:14" class="time">18:14</a> |
| mizmo | if i went and designed UIs willy-nilly asking my friends what they thought about it, i would be making a big mistake | <a href="#t18:14" class="time">18:14</a> |
| onekopaka | mchua: I ran from my school bus home. | <a href="#t18:14" class="time">18:14</a> |
| onekopaka | to home* | <a href="#t18:14" class="time">18:14</a> |
| markg85 | mizmo, once there is some input from one list (websites) you can choose to get further with other groups or bast "the new design" on just the input from the websites list | <a href="#t18:14" class="time">18:14</a> |
| markg85 | hey onekopaka | <a href="#t18:14" class="time">18:14</a> |
| * onekopaka catches up | <a href="#t18:14" class="time">18:14</a> | |
| mizmo | markg85: the reason www.fpo sucks RIGHT NOW is because that is the approach that has been taken in the past - it doesn't matter | <a href="#t18:15" class="time">18:15</a> |
| ricky | What if the input is wrong? What do we do then? | <a href="#t18:15" class="time">18:15</a> |
| mchua | onekopaka: we're talking about the projects we want to work on for f12 - in order, they're get.fpo, decision process, www.fpo, docs.fpo, and then join.fpo, translation, and user gallery. | <a href="#t18:15" class="time">18:15</a> |
| hiemanshu | Make some assumptions, and work out the best we can | <a href="#t18:15" class="time">18:15</a> |
| mizmo | markg85: but what i am telling you right now as a professional design practicioner is that is the wrong approach, a good design hinges on identifying and prioritizing your target users | <a href="#t18:15" class="time">18:15</a> |
| markg85 | mizmo, then where do you suggest i gather feedback? | <a href="#t18:15" class="time">18:15</a> |
| mizmo | markg85: it depends who you have identified as your target users! | <a href="#t18:15" class="time">18:15</a> |
| mchua | onekopaka: right now it's mizmo on get.fp.o, with markg85's help, hiemanshu on the user gallery, markg85 on www.fp.o with hiemanshu's help, ricky on decisionmaking process and docs.fp.o, mchua on join.fp.o, translation as a "we need to find someone." | <a href="#t18:15" class="time">18:15</a> |
| mizmo | markg85: if your target users are beginners, then you go to where you can talk to beginners and ask them | <a href="#t18:15" class="time">18:15</a> |
| mizmo | markg85: if your target users are experienced hackers, then you go and ask experienced hackers what they think | <a href="#t18:16" class="time">18:16</a> |
| markg85 | mizmo, that's the biggest problem of fedora.. there isn't one group! | <a href="#t18:16" class="time">18:16</a> |
| onekopaka | yep | <a href="#t18:16" class="time">18:16</a> |
| mizmo | markg85: if you dont think about *who* you are talking to, you're going to get way skewed results | <a href="#t18:16" class="time">18:16</a> |
| mizmo | markg85: that's right there are multiple groups, | <a href="#t18:16" class="time">18:16</a> |
| mizmo | (1) never used linux before | <a href="#t18:16" class="time">18:16</a> |
| hiemanshu | you make a general idea of stuff and continue | <a href="#t18:16" class="time">18:16</a> |
| mizmo | (2) have some tech experience, used another linux | <a href="#t18:16" class="time">18:16</a> |
| mizmo | (3) current fedora users | <a href="#t18:16" class="time">18:16</a> |
| mizmo | what we should decide | <a href="#t18:16" class="time">18:16</a> |
| mizmo | is in what order do we care about these users | <a href="#t18:16" class="time">18:16</a> |
| mizmo | for each project we are talking about taking on | <a href="#t18:16" class="time">18:16</a> |
| mizmo | then | <a href="#t18:16" class="time">18:16</a> |
| markg85 | oke stop :P | <a href="#t18:16" class="time">18:16</a> |
| mizmo | you can ask epople in each category, but weigh them appropriately | <a href="#t18:16" class="time">18:16</a> |
| hiemanshu | we care for 1 first and then 2 | <a href="#t18:17" class="time">18:17</a> |
| mizmo | hiemanshu: i agree | <a href="#t18:17" class="time">18:17</a> |
| * ricky agrees as well | <a href="#t18:17" class="time">18:17</a> | |
| mizmo | hiemanshu: for www.fpo we care about 1, then 2 | <a href="#t18:17" class="time">18:17</a> |
| markg85 | mizmo, then lets say i want to target beginning linux users. users that have installed fedora but not users that haven't used any linux ever yet | <a href="#t18:17" class="time">18:17</a> |
| mizmo | hiemanshu: for docs.fpo, we care a little less about 1, because if they don't use it they don't need help yet | <a href="#t18:17" class="time">18:17</a> |
| * mchua looks at the time, and now has to leave in 10 minutes. Can we move towards wrapping up? | <a href="#t18:17" class="time">18:17</a> | |
| ricky | Perhaps for join.fp.o, we care more about 2 and 3. | <a href="#t18:17" class="time">18:17</a> |
| mizmo | markg85: then talk to beginner users and ask them what they care about www.fpo | <a href="#t18:17" class="time">18:17</a> |
| mchua | can any of this discussion go to list, or to next week? | <a href="#t18:17" class="time">18:17</a> |
| markg85 | mizmo, so where do i start then and that's probably the biggest group :P | <a href="#t18:17" class="time">18:17</a> |
| hiemanshu | ricky, i would say 3 for join.fpo | <a href="#t18:17" class="time">18:17</a> |
| ricky | mchua: I think it might be good to get some of these disagreements worked out - we'll post logs to list later if you have to go | <a href="#t18:18" class="time">18:18</a> |
| markg85 | mizmo, i did on my school with 5 persons and all where ashamed that opensource software brings that crap out.. and they said that because it wasn't fully working on any of there pc's | <a href="#t18:18" class="time">18:18</a> |
| mizmo | markg85: thats neither here nor there, though | <a href="#t18:18" class="time">18:18</a> |
| ricky | OK, so now that we have some groups and some priorities, where do we go from here? | <a href="#t18:19" class="time">18:19</a> |
| hiemanshu | ricky, Feedback | <a href="#t18:19" class="time">18:19</a> |
| hiemanshu | from users | <a href="#t18:19" class="time">18:19</a> |
| markg85 | finally we are moving a bit | <a href="#t18:19" class="time">18:19</a> |
| mizmo | i dont know if i can meet next week because ill be in berlin | <a href="#t18:19" class="time">18:19</a> |
| mizmo | but what i will try to do | <a href="#t18:19" class="time">18:19</a> |
| mizmo | is have a summary of get.fpo tasks to usability test | <a href="#t18:20" class="time">18:20</a> |
| mizmo | and maybe some initial test results | <a href="#t18:20" class="time">18:20</a> |
| ricky | Cool. | <a href="#t18:20" class="time">18:20</a> |
| ricky | mizmo: For the rest of us, can you give some advice on how to go about getting these tests/feedback? | <a href="#t18:20" class="time">18:20</a> |
| mizmo | maybe a good systematic approach that you can adapt as you've got resources | <a href="#t18:21" class="time">18:21</a> |
| mizmo | is have a print out of the page(s) you're working on | <a href="#t18:21" class="time">18:21</a> |
| mizmo | and show it to three never-used-linux-before people (maybe parents, maybe friends, maybe co-workers) | <a href="#t18:21" class="time">18:21</a> |
| mizmo | then take some screenshots and make them available somewhere maybe on the wiki | <a href="#t18:22" class="time">18:22</a> |
| mizmo | and go into different tech IRC channels and try to grab 3 people who are familiar with linux | <a href="#t18:22" class="time">18:22</a> |
| onekopaka | Mozilla's feedback system, Hendrix, seems like a good tool for collecting feedback | <a href="#t18:22" class="time">18:22</a> |
| mizmo | and then go into #fedora-devel to get feedback from experience hackers | <a href="#t18:22" class="time">18:22</a> |
| mizmo | and for the page you're working on | <a href="#t18:22" class="time">18:22</a> |
| mizmo | come up with a list of questions to get feedback on | <a href="#t18:22" class="time">18:22</a> |
| mizmo | eg for get.fpo i'm going to ask | <a href="#t18:22" class="time">18:22</a> |
| mizmo | 'if you wanted to download x86_64, what would you click on?' | <a href="#t18:22" class="time">18:22</a> |
| mizmo | 'if you were going to install fedora on your machine today, which link would you click on?' | <a href="#t18:23" class="time">18:23</a> |
| mizmo | have at least 5 questoins to ask and note any other stuff the people you talk to note about the page | <a href="#t18:23" class="time">18:23</a> |
| mizmo | onekopaka: ive not heard of it | <a href="#t18:23" class="time">18:23</a> |
| onekopaka | mizmo: yep. <a href="http://hendrix.mozilla.org/">http://hendrix.mozilla.org/</a> | <a href="#t18:23" class="time">18:23</a> |
| hiemanshu | make the default page for Mozilla a feedback page | <a href="#t18:23" class="time">18:23</a> |
| onekopaka | mizmo: and the source is in mozilla CVS in mozilla/webtools/hendrix | <a href="#t18:24" class="time">18:24</a> |
| * mizmo takes a look | <a href="#t18:24" class="time">18:24</a> | |
| mizmo | onekopaka: i think having osmething like that for the website would be good (altohugh we already get messages to webmaster@fpo) | <a href="#t18:24" class="time">18:24</a> |
| mizmo | but here we're talking more about very targeted feedback | <a href="#t18:24" class="time">18:24</a> |
| mizmo | in response to questions/tasks we come up with rather than open format | <a href="#t18:24" class="time">18:24</a> |
| onekopaka | yeah | <a href="#t18:24" class="time">18:24</a> |
| onekopaka | but feedback in general | <a href="#t18:24" class="time">18:24</a> |
| ricky | Yeah, webmaster@ email is usually not very feedback-related at the moment. | <a href="#t18:25" class="time">18:25</a> |
| onekopaka | it's more complaining about servers that aren't ours | <a href="#t18:26" class="time">18:26</a> |
| ricky | Heh | <a href="#t18:26" class="time">18:26</a> |
| * onekopaka curses underneath his breath about those emails | <a href="#t18:26" class="time">18:26</a> | |
| ricky | OK, so tasks for next week: | <a href="#t18:26" class="time">18:26</a> |
| mizmo | hehe | <a href="#t18:26" class="time">18:26</a> |
| ricky | Can all task owners strat a thread on the mailing list stating their task and actoins | <a href="#t18:27" class="time">18:27</a> |
| ricky | Then they can post updates on that thread? | <a href="#t18:27" class="time">18:27</a> |
| mizmo | sure | <a href="#t18:27" class="time">18:27</a> |
| hiemanshu | ricky, i am new here so might need some help :P | <a href="#t18:27" class="time">18:27</a> |
| onekopaka | hiemanshu: you're on the fedora-websites-list, right? | <a href="#t18:27" class="time">18:27</a> |
| hiemanshu | just joined in | <a href="#t18:28" class="time">18:28</a> |
| ricky | So one task is to gather feedback in the way that mizmo described | <a href="#t18:28" class="time">18:28</a> |
| ricky | For any person that you interview, make sure to get some background on what category of user they fall in. | <a href="#t18:28" class="time">18:28</a> |
| onekopaka | ricky: should I be updating the task list on the wiki at this point? | <a href="#t18:28" class="time">18:28</a> |
| ricky | onekopaka: That'd be great if you can | <a href="#t18:29" class="time">18:29</a> |
| markg85 | mizmo, sant me to go through with asking for feedback on fp.o on the websites mailing list or now? the question i will ask is: What do you really like about this site: fp.o, get.fp.o. If it where gone what would you miss? | <a href="#t18:29" class="time">18:29</a> |
| onekopaka | mmkay I've got it open in my browser for editing | <a href="#t18:29" class="time">18:29</a> |
| markg85 | sant = want | <a href="#t18:29" class="time">18:29</a> |
| ricky | mizmo: Does that sound like the right kind of question, or do you have any other suggestions for markg85? | <a href="#t18:29" class="time">18:29</a> |
| mizmo | markg85: that sounds like the right question but i dont think the websites list is the right place to ask | <a href="#t18:30" class="time">18:30</a> |
| ricky | Should the questions be more task-focused? | <a href="#t18:30" class="time">18:30</a> |
| ricky | Like: Show me what you would do if you wanted to download the x86_64 KDE live cd | <a href="#t18:30" class="time">18:30</a> |
| mizmo | ricky: yeh, for www.fpo though forming a task like that is a bit trickier | <a href="#t18:30" class="time">18:30</a> |
| ricky | True. | <a href="#t18:30" class="time">18:30</a> |
| mizmo | markg85: i can handle asking the questions for get.fpo if you can handle www.fpo | <a href="#t18:30" class="time">18:30</a> |
| markg85 | mizmo, want me to crosspost it to: fedora, fedora-devel, fedora-websites and fedora-design ? | <a href="#t18:30" class="time">18:30</a> |
| mizmo | markg85: i think the question you've come up with will work for www.fpo | <a href="#t18:31" class="time">18:31</a> |
| mizmo | markg85: i wouldn't spam mailing lists, i would ask in the venues i suggested above (friends, #fedora, #fedora-devel) | <a href="#t18:31" class="time">18:31</a> |
| ricky | markg85: People in real life could be good as well - especially for the people that don't know what Fedora or Linux is | <a href="#t18:31" class="time">18:31</a> |
| hiemanshu | I change that and put it up for User Gallery | <a href="#t18:31" class="time">18:31</a> |
| onekopaka | ricky: I think we should really have a Websites/Tasks/Feedback page for Feedback-related tasks to keep the task list cleaner | <a href="#t18:33" class="time">18:33</a> |
| onekopaka | ricky: what do you think about that? | <a href="#t18:33" class="time">18:33</a> |
| ricky | Yeah, that sounds better than spamming the mailing list | <a href="#t18:34" class="time">18:34</a> |
| hiemanshu | onekopaka, +1 | <a href="#t18:34" class="time">18:34</a> |
| nb | ricky, /me would go to torrents to download everything :) | <a href="#t18:34" class="time">18:34</a> |
| nb | but i dont know how many people know about torrents.fedoraproject.org | <a href="#t18:34" class="time">18:34</a> |
| ricky | OK, so does everybody know what to work on? If so, we can close for the week :-) | <a href="#t18:34" class="time">18:34</a> |
| onekopaka | recently, I've been cleaning the wiki up | <a href="#t18:34" class="time">18:34</a> |
| * hiemanshu is ready to fire up | <a href="#t18:35" class="time">18:35</a> | |
| markg85 | mizmo, for the question. don't make it questions because that again will scare users away. That one question i made up will probably do fine for fp.o and get.fp.o | <a href="#t18:35" class="time">18:35</a> |
| ricky | Oh, one more thing - how is this meeting time for everybody? | <a href="#t18:35" class="time">18:35</a> |
| * mchua --> train - logs plz! | <a href="#t18:35" class="time">18:35</a> | |
| hiemanshu | Midnight here, fine with me | <a href="#t18:35" class="time">18:35</a> |
| mchua | this time is fine | <a href="#t18:35" class="time">18:35</a> |
| ricky | Only a couple of people filled out mchua's whenisgood thing, so this time was pretty much based on 4 peoples' times. | <a href="#t18:35" class="time">18:35</a> |
| nb | is pretty good for me, i don't normally work till about 30m inst from now | <a href="#t18:35" class="time">18:35</a> |
| nb | altough sometimes i would have to work | <a href="#t18:35" class="time">18:35</a> |
| onekopaka | ricky: good for the summer, but once school starts again it'll be a pain | <a href="#t18:35" class="time">18:35</a> |
| markg85 | ricky, this time is fine for me | <a href="#t18:35" class="time">18:35</a> |
| ricky | onekopaka: Heh, I'm in the same situation, actually | <a href="#t18:35" class="time">18:35</a> |
| nb | don't really include me in your planning, my schedule changes every week | <a href="#t18:36" class="time">18:36</a> |
| ricky | OK, for those reading on the mailing list: if you didn't fill in your time, please do so | <a href="#t18:36" class="time">18:36</a> |
| ricky | I think mchua's whenisgood thing is closed now, so we'll figure out some way to get times. | <a href="#t18:36" class="time">18:36</a> |
| ricky | nb: Heh, no worries | <a href="#t18:36" class="time">18:36</a> |
| -!- ricky changed the topic of #fedora-websites to: Websites Meeting - Meeting End | <a href="#t18:36" class="time">18:36</a> | |