docs February 2010

docs@lists.fedoraproject.org

23 participants
40 discussions

Self-Introduction
by Eli 01 Mar '10

01 Mar '10

Hello, I wanted to send my self-intro and get my name out to everyone. My name is Eli and I live in Minnesota. I have a lot of interest in Fedora and would like to contribute where I can be of the most help. I do a lot of reading and editing of manuals and guides at work. I have good set of computer skills but I have never taken any college courses on the computer. It has all been self-taught. So I can make my way around but don't know the "technical" aspects. I have no programming skills and minimal command line skills. But I can write well and project what I am trying to say. I have been using GNU/Linux for about a year and a half. I have only used Gnome and will probably stick with that. I am really self-motivated and take pride in my work. I am open to trying new things and definitely learning all the things I can learn about Linux and Fedora in particular. And that I hope can have an impact on what Fedora is and will become in the future. I might need some help navigating around to start out with, and I'm sure I'm not the first to ask. But once I can get going and figure out what is where, I will be well on my way. Its taken me a little time to get all this figured out and I hope it correct. Thank you for your time. And I look forward to helping out the team and working with others on any projects. Eli gpg --fingerprint elijahm17(a)gmail.com pub 768D/D2BE01F8 2010-02-28 Key fingerprint = 8BBB 2C9C 240D 71AA F7EE A9B4 1D53 A315 D2BE 01F8 uid Eli Madrinich (Emad78) <elijahm17(a)gmail.com> sub 768g/EDF140AF 2010-02-28

2 1

Docs Meeting 2010-02-25 Summary
by Eric Christensen 25 Feb '10

25 Feb '10

1 0

Docs Meeting 2010-02-25 IRC log
by Eric Christensen 25 Feb '10

25 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 00:08:13 <sparks> #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:08:13 <zodbot> Meeting started Thu Feb 25 00:08:13 2010 UTC. The chair is sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:08:14 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:08:21 <sparks> #topic Roll Call 00:08:22 * sparks 00:08:27 * jsmith is here (for once!) 00:08:30 * shaunm . 00:08:38 * jjmcd . 00:08:41 * rudi is here 00:08:42 * bcotton is here 00:09:04 <sparks> #chair jjmcd 00:09:05 <zodbot> Current chairs: jjmcd sparks 00:09:19 <sparks> Sorry for the delay. I forgot when I was. 00:09:23 <sparks> Let's get started. 00:09:32 <sparks> #topic Desktop Help Summit 00:09:39 <sparks> #link http://live.gnome.org/DesktopHelpSummit2010 00:10:00 <sparks> shaunm: Last week we were trying to figure out if you had all the resources you needed from Fedora. 00:10:01 * jjmcd made reservations, posted arrive/depart on gnome page 00:10:36 <jjmcd> And I think we still had issues with talk if I recall 00:10:49 <sparks> What are the issues? 00:10:55 <jjmcd> No phone line, firewall could be a prob with IP 00:11:01 <shaunm> right 00:11:14 <shaunm> oh my 00:11:20 <shaunm> I just realized something 00:11:37 <jjmcd> You have to be in Nevada on the 20th 00:12:08 <shaunm> seattle on the 22nd, actually ;) what kind of idiot would schedule his own conference to conflict with something else he's doing? 00:12:37 <jjmcd> sounds like you'll miss the hackfest 00:12:53 <shaunm> one of the attendees has a 3G modem/router/thingamajig 00:13:08 <jjmcd> coolness 00:13:09 <shaunm> I'm flying late evening on monday, so we'll get hackfest time in 00:13:19 <jsmith> Mmmmnn... voip over 3G.... Enjoy that... 00:13:24 <shaunm> but I suppose that would chew threw his minutes 00:13:25 <sparks> That would work or someone with a cell phone, unlimited weekends, and a speaker 00:14:13 <shaunm> I have unlimited weekends, so that's an option 00:14:53 <shaunm> ok, so I'll check three options: 00:15:13 * jsmith will be right back 00:15:21 <shaunm> 1) ask kevin about the firewall at the venue, see if he thinks we'll have problems just doing voip from a laptop 00:15:41 <shaunm> 2) check with paul to see if his 3G hotness would be an option 00:16:04 <shaunm> 3) see if I can hook up some speakers and possibly an external mic to my cell phone and get decent sound quality 00:16:53 <shaunm> and then I should email everybody not on the confirmed-yes list to let them know they can participate remotely 00:18:15 * stickster has to lurk tonight, sorry guys -- I'm swamped 00:18:52 <jjmcd> Sounds like a plan 00:18:58 <stickster> shaunm: Sounds right to me 00:19:29 <shaunm> and I'll do (3) even if either of the other two look like they'll work 00:19:39 <shaunm> because that's the fallback with the least risk of failure 00:20:17 <sparks> shaunm: Do you need anything else from Fedora that you don't already have? 00:20:50 <stickster> Other than a passel of volunteers and a pitcher of martinis 00:21:15 <shaunm> no, I don't think so. you guys have been very helpful, thanks. 00:21:34 <sparks> Okay, anything else on this topic? 00:22:04 <sparks> Moving on.. 00:22:20 <sparks> #topic Release Notes 00:22:30 <sparks> jjmcd: Whatcha got for us? 00:22:41 <jjmcd> Not a lot 00:23:05 <jjmcd> joebebus is working on Alpha altho not sure he is doing a lot, but it looks as if talking points are slo 00:23:13 * quaid wanders in late 00:23:44 <jjmcd> I did exch a few emails w/joeb but haven't heard from mchua 00:24:33 <jjmcd> else not much 00:24:40 <sparks> Need anything? 00:24:56 <jjmcd> Well, we are on the cusp of starting on the beats 00:25:10 <jjmcd> so any beat writers you can find under a rock somewhere are welcome 00:25:45 <jjmcd> I did seed the beats with links to related feature pages 00:25:54 <jjmcd> so hopefully they don't get missed 00:26:30 <jjmcd> and it will save me a little time at the last minute when the beat is still empty 00:26:38 <sparks> jjmcd: Have you put anything on the Planet/Announce? 00:26:57 <jjmcd> No, not yet. I think that is on the sked for thurs if i recall 00:27:06 <sparks> Okay 00:27:09 <jjmcd> but rl has been bad this week and will continue 00:27:13 <stickster> jjmcd: sparks: The talking points are done 00:27:13 <sparks> Anything else? 00:27:20 <sparks> stickster: Cool 00:27:23 <jjmcd> Grand Rapids this weekend and Lansing tuesday 00:27:28 <stickster> jjmcd: sparks: You guys should be on the Marketing list 00:27:29 <jjmcd> stickster, good deal 00:27:29 <stickster> Are you? 00:27:37 <jjmcd> I don't think so 00:27:48 * sparks isn't sure what lists he's on anymore. 00:27:50 <stickster> http://lists.fedoraproject.org/mailman/listinfo/marketing 00:28:12 <stickster> We've got to keep abreast of what other teams are doing :-) 00:28:24 <stickster> Esp. when we're supposed to be working with them on something -- being on the list is a big help 00:28:44 * ianweller strides in 00:28:46 <stickster> http://lists.fedoraproject.org/pipermail/marketing/2010-February/011813.html 00:29:18 <jjmcd> Wow, we haven't seen the kansas contingent in a while 00:29:38 <sparks> I second that wow 00:29:49 <jjmcd> Cool, I actually have the wiki page up, just haven't had a chance to graze the history 00:30:32 <jjmcd> Oh cool, their link is wrong 00:33:19 <sparks> Anything else? 00:33:34 <jjmcd> not from here 00:33:57 <sparks> Moving on... 00:34:01 <sparks> #topic New Guides 00:34:08 <sparks> Any new guides in the works? 00:35:11 <sparks> #topic Guide Status 00:35:19 <sparks> Anyone want to talk about their guide? 00:35:29 <jjmcd> NOBODY has updated their schedule 00:35:39 <jjmcd> #link https://fedoraproject.org/wiki/Docs_F13_schedule 00:35:52 <sparks> I was JUST getting ready to do just that 00:36:33 <sparks> jjmcd: Can you write a reminder email to the Docs list, please? 00:36:40 <jjmcd> roger 00:37:00 <jjmcd> #action jjmcd tro remind guide owners to update schedule 00:37:03 <jjmcd> again 00:37:17 <sparks> Anyone know the status of Transifex? 00:37:19 <jjmcd> hmmm, I thought it was #action, oh well 00:38:03 <jjmcd> glezo_afk is on #fedora-docs 00:38:15 <sparks> jjmcd: There isn't any feedback to #action 00:38:32 <jjmcd> Ah, OK 00:40:23 <sparks> Well, until Transifex goes live I don't know that we have anything to really work on just yet. 00:41:34 <sparks> Anything else on this topic? 00:42:16 <sparks> #topic Outstanding BZ Tickets 00:42:25 <sparks> #link https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classificatio… 00:42:47 <sparks> This is the link to view all non-closed tickets for documenation. 00:43:02 * stickster gets off phone 00:43:10 <stickster> sparks: So you're still planning a bug stomping fest, yeah? 00:43:18 <sparks> On March 6 there will be a bug busting session to help get rid of some of these. 00:43:26 * stickster saw a short blog announcement, awesome! 00:43:55 <sparks> I'll send out a message to the list with the specifics but if you can be here your help would be appreciated. 00:44:31 <stickster> sparks: It would be awesome if you could blog your plan 00:44:37 <stickster> sparks: What do you need help with specifically? 00:45:10 <sparks> stickster: I honestly haven't had time to sit down and create a strategy or even look at what actually needs to be done. 00:45:32 <stickster> I would suggest setting up some broad priorities for the bugs, and even setting a field on them appropriately 00:46:12 <stickster> sparks: The question you'll want to start with is, what is the goal of the bug stomping? Is it to get any N% closed? Or do we want to concentrate on a specific set and close them first, moving on afterward? 00:47:21 <sparks> not sure what's there... I'm guessing that RN bugs can be dealt with first but it may be that someone just needs help reviewing something they've worked on. 00:48:12 <stickster> sparks: Here's what I'd start with -- see if there are large bunches of bugs you can fit into one logical group. If you can find a couple groups that are *super-easy* to close, let's start with those 00:48:18 <stickster> That should get us rolling 00:48:38 <stickster> Then move on to a group of bugs that maybe is more substantial, but important to us getting deliverables out for F13. 00:48:47 * stickster pulls up list 00:49:12 <stickster> sparks: We shouldn't worry about anything ASSIGNED. If it's ASSIGNED, someone should be working on it 00:49:24 <stickster> or at least know about it to the extent that we don't need to spend cycles on it right away 00:49:38 <sparks> Well... If it's assigned they SHOULD be working on it but there are some old ASSIGNED bugs 00:50:02 <sparks> We only have 24 NEW bugs 00:50:09 <sparks> so that shouldn't be awful to fix 00:50:19 <stickster> sparks: Let's talk about this on list, I don't want to waste everyone's meeting time 00:50:24 <stickster> But I think we can come up with a plan :-) 00:50:28 <sparks> Works 00:50:33 <stickster> sparks: Start the conversation on docs pls, and I'll help 00:50:34 <sparks> Okay, anything else? 00:50:52 <stickster> just need an #action 00:51:10 <sparks> what kind of an #action? 00:51:40 <stickster> action to start the convo ;-) 00:52:03 <sparks> #action sparks to start a conversation on the docs list to discuss the bug busting session 00:52:40 <sparks> #topic All other business 00:53:02 <sparks> Okay, we've reached the end of our agenda. Anyone have anything else they'd like to discuss? 00:53:26 <stickster> sparks: We can go into the bug thing a little further, and then you'd have something to start with 00:53:27 * jsmith has nothing 00:53:33 <stickster> We'll cut off at the hour 00:53:51 <sparks> jsmith: Thanks for being here tonight! 00:53:55 <stickster> Hey jsmith! 00:54:11 <stickster> So proceeding from what I was saying above... we could start by (1) triaging NEW bugs 00:54:14 <jjmcd> Looks to me like a huge fraction of the bugs are review requests 00:54:29 <stickster> then (2) moving to old ASSIGNED bugs, < #500000 00:54:36 <jsmith> sparks: I'm not sure I was much help, but I'm happy to be here when I can. 00:54:46 <jsmith> sparks: (You caught me on the road, so I had a few free minutes tonight) 00:55:02 <sparks> jsmith: Hope to hog-tie you again! 00:55:43 <stickster> The more the merrier :-) 00:55:45 <sparks> Okay, anything else? 00:55:55 <stickster> sparks: What would you suggest for (3)? 00:56:26 <sparks> start hitting the assigned bugs. 00:56:32 <stickster> sparks: Any in particular? 00:56:42 <stickster> relnotes first? IG first? 00:56:46 <stickster> What needs to be done first on the schedule? 00:56:47 <sparks> The review bugs might not be so high priority but they would be easy to complete 00:57:02 <jsmith> I tend to agree with stickster... we need a big more planning to hit the highest priority first 00:57:20 <jsmith> Sure, we could just do the low-hanging fruit, but that's not what's most important, right? 00:57:31 <sparks> The guides table already has a L10N priority assigned to each guide that is a priority so we could use that. 00:57:35 <stickster> jsmith: What do you think about (1) and (2)? Do you think a triage and killing off old weeds is a good or bad way to start? 00:57:52 <stickster> sparks: That's an excellent point! 00:58:11 <jsmith> stickster: I think it's a decent way to start... you know, get some eyes on the landscape, so we know how many acres we need to plow.... 00:58:14 <sparks> Old weeds are a problem. If people (customers) have asked for support and haven't received it then it makes Fedora look bad. 00:58:49 <stickster> Also we might find out where people's comfort zones are{,n't} with Bugzilla 00:59:03 <stickster> So we can put specific people on certain tracks for part (3) 00:59:28 * stickster <eof/> 00:59:30 <jjmcd> Maybe we need a bugzilla class for guide owners 00:59:38 <jjmcd> it is a pretty darned handy tool 00:59:44 <stickster> Might be more like a 15-minute primer 00:59:44 <sparks> It is a handy tool 00:59:55 <sparks> I haven't heard anyone say that they didn't know how to interact with it, though. 00:59:57 * quaid arrived just in time for farm analogies 01:00:06 <stickster> It's not hard to understand on its own, and it's really workflow that people don't grok right off 01:00:11 <stickster> quaid: You're just in time for the bell 01:00:17 <stickster> I promised to shut up at the hour mark :-) 01:00:26 <jjmcd> Sounds like you missed 01:00:35 <sparks> stickster: I don't believe you specified which hour 01:01:37 <sparks> Well, let's discuss which bugs to swat at first on the list 01:01:45 <sparks> I'll start the discussion there. 01:01:50 <sparks> Anyone have anything else? 01:02:58 <sparks> Okay... Well, thanks everyone for coming tonight. Come back next week and we'll do it all over again. Until then we can discuss all this on the list. 01:03:04 <sparks> #endmeeting - -- - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLhc72AAoJEDbiLlqcYamxiIoP/RI6ViIiLxJdxrh6UiQ3G/yi 1PXtdVxBN5NyvJMomhW4EU8Z1fvnBRoMdKWkBEh6pV2WBUbkT2LruDefjuO7tdQj zIukyKU3+u9ADxVJAeL0nmDA1NrlFLBB+g7EqRXfI0LqicMTRZhgCoi7HXoi75Ma yntCNeZEGRiEdcolIcXEN/A+5cxhL8B8RIGjcmLSTLTXSNQioRGLJj+eFLaijbpH Jfx8FBhLqU7z/JCbmhgrZ1o3ujjIV+OuplUH/yzRwiHXU/Pc5KJZElMNm7IhiV9/ VhNxM5GQ+NOzF5DnnVpIKiy8ZbuDvPozO0ZVyqXuAhQmUOw5ROxiuk2wcltM0COo zkpKOvzHZ8yD3GNq9pPFQnjlOeR9VFsG6JeZ3olRLybDOAm+t+D5CGHntUWeFYY6 OIx8tQq574pJfdE18Ac+IcqsetZ5WWSibZQF57wxUZ7d4UlxO2nhcaH/oxPcwLj6 z24iqM5ApyjSI8K6sOc42aAslIBMTSmIlB8YuJAwLT2woau2pVvjVAy2ES/H8/vw MzMlhxtGVli9wnMKDP3OixnHC2FaLccE2VatkBKhJkbu9U6QxCniEMLZdRFm4OHz GCmSZLPQfQ7I2tUErWV38VPNBhKHITY/yYPuEODizN/7LadwEyWZDABTohzf9Yt7 dHrv4a3oRdvRx6DHNXfQ =VJ28 -----END PGP SIGNATURE-----

1 0

Docs Meeting 2010-02-18 Summary
by Eric Christensen 25 Feb '10

25 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings =================================================================================================== Meeting started by sparks at 00:00:30 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2010-02-18/fedora-meeting.2… . Meeting summary - --------------- * Roll Call (sparks, 00:00:36) * Desktop Help Summit and live collaboration (stickster, 00:11:48) * LINK: http://live.gnome.org/DesktopHelpSummit2010 (sparks, 00:12:09) * We need shaunm to let us know if he has what he needs for live collaboration, and what he is committed to do there (stickster, 00:12:18) * ACTION: stickster writing email to list and Shaun to summarize and see if there's anything left for us to do (stickster, 00:14:50) * There is a #desktop-help channel set up on Freenode, with zodbot eagerly awaiting (stickster, 00:15:01) * Release Notes (sparks, 00:17:32) * LINK: http://fedoraproject.org/wiki/Fedora_12_Alpha_release_notes (stickster, 00:20:56) * LINK: http://fedoraproject.org/wiki/Fedora_13_Alpha_release_notes (stickster, 00:24:36) * ACTION: joebebus to complete draft of F13 Alpha relnotes one-pager on wiki by Friday 2010-02-26 (stickster, 00:25:06) * ACTION: jjmcd to bird-dog joebebus (stickster, 00:25:14) * New Guides (sparks, 00:27:44) * Guide Status (sparks, 00:29:53) * LINK: https://fedoraproject.org/wiki/Docs_F13_schedule (sparks, 00:30:06) * ACTION: email to the list asking guide leads to accept their schedules (sparks, 00:30:52) * ACTION: jjmcd to make update to F12 docs in git to fix PackageKit security information (stickster, 00:38:14) * ACTION: sparks will push F12 updated rpm pursuant to jjmcd's change for PackageKit info (stickster, 00:38:24) * Transifex update (stickster, 00:45:48) * LINK: https://translate.stg.fedoraproject.org/ (stickster, 00:50:54) * Needs more testing by Docs and L10n, specifically translators should check that submissions work; Docs people should test that multi-POT (Publican-style) support is working (stickster, 00:51:47) * submissions are only enabled to the "virt-guide-localhost" test repo at https://translate.stg.fedoraproject.org/projects/p/publican/ (stickster, 00:55:20) * note extra /p/ in that URL (stickster, 00:55:24) * LINK: https://fedorahosted.org/fedora-infrastructure/ticket/1455 (stickster, 01:00:53) * ACTION: rudi to check on Tx staging behavior for one or more official guides and will report results to https://fedorahosted.org/fedora-infrastructure/ticket/1455 (stickster, 01:02:23) * Making docs.fp.o accessible for non-JavaScript equipped browsers (sparks, 01:04:09) * Outstanding BZ Tickets (sparks, 01:05:44) * LINK: https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classificatio… (sparks, 01:05:53) * AGREED: Saturday March 6, 10am-4pm EST (1500-2100 UTC) for Docs bug stomping session in IRC Freenode #fedora-docs (stickster, 01:12:02) * core hours can be extended for extra participation (stickster, 01:12:20) * ACTION: sparks to announce the bug stomping session on Planet (sparks, 01:13:54) * Anything else? (sparks, 01:15:09) * Use EasyFix keyword for easy BZ bugs for new people (stickster, 01:21:00) Meeting ended at 01:24:37 UTC. Action Items - ------------ * stickster writing email to list and Shaun to summarize and see if there's anything left for us to do * joebebus to complete draft of F13 Alpha relnotes one-pager on wiki by Friday 2010-02-26 * jjmcd to bird-dog joebebus * email to the list asking guide leads to accept their schedules * jjmcd to make update to F12 docs in git to fix PackageKit security information * sparks will push F12 updated rpm pursuant to jjmcd's change for PackageKit info * rudi to check on Tx staging behavior for one or more official guides and will report results to https://fedorahosted.org/fedora-infrastructure/ticket/1455 * sparks to announce the bug stomping session on Planet Action Items, by person - ----------------------- * jjmcd * jjmcd to bird-dog joebebus * jjmcd to make update to F12 docs in git to fix PackageKit security information * sparks will push F12 updated rpm pursuant to jjmcd's change for PackageKit info * joebebus * joebebus to complete draft of F13 Alpha relnotes one-pager on wiki by Friday 2010-02-26 * jjmcd to bird-dog joebebus * rudi * rudi to check on Tx staging behavior for one or more official guides and will report results to https://fedorahosted.org/fedora-infrastructure/ticket/1455 * sparks * sparks will push F12 updated rpm pursuant to jjmcd's change for PackageKit info * sparks to announce the bug stomping session on Planet * stickster * stickster writing email to list and Shaun to summarize and see if there's anything left for us to do * **UNASSIGNED** * email to the list asking guide leads to accept their schedules People Present (lines said) - --------------------------- * stickster (151) * sparks (79) * jjmcd (60) * joebebus (48) * rudi (33) * ricky (13) * zodbot (12) * quaid (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLhc7RAAoJEDbiLlqcYamxhgwP/A/0C/1ytmi3WgkHDXXcfbEN sQPsFXNaykxDczxEeKPLx9H5e5vd3U3ecOZ4SAD8Yxsy5696KptV8r/Z/hJxs97/ EwGOr3+DjrNVVVmywVHNFnJ0AOLIGB3o0K7RJGgmEgeW4QC9NQxTSUVJVXmRtFLO cANdMXilZpxblt+yv2i581EVxVemBeXEpvxY3WiV3R1rAxYJFRU+Dvzk6EnEUCGm TYYKUebSPGGuIEIxBuwAulPBnAncnsXh8v9Rr3iDQPcrtFqw47kd1x4QNoGr0Yc5 ttahvRVRanH76th3VodqLSIXeLbbdpaNCtMLSSf0OdM5XqpOVe+v81xNdNUmuNJT BNaO4dT/FmoLKI2AtJR4QH+ChV8hROQMpC4OQRiMAv9htZlPFpyT1mzOSMaMmM9W gXQteCf+cvQT7jQz0fVwgujf2A+prfo11juUJEMGEzAPqEZuXqrdhQVnmfc77BDq f2kBN+AjScIkafONDyUk4yAK4ehtOwiNmUwa0tKEFta6h5WGYg+T7xXzSdqE/3Cr VX/X1fRp+7PC1g1KT4R6O96YVKrfco9eAuyX0FB1WU69Yt403WSbGUVio9fpRP3W Xfjzu/xq3eNhyx+VNnzKqggN8+yCRNfd0SROx1dTsmmSMQUUiTLr+SQ8tvEHVfls ciolRhUTx3L9EJ7ii4a5 =rwV9 -----END PGP SIGNATURE-----

1 0

Docs Meeting 2010-02-18 IRC log
by Eric Christensen 25 Feb '10

25 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 00:00:30 <sparks> #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:00:31 <zodbot> Meeting started Thu Feb 18 00:00:30 2010 UTC. The chair is sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:00:33 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:00:36 <sparks> #topic Roll Call 00:00:40 * sparks 00:00:43 * jjmcd . 00:00:52 <sparks> #chair jjmcd 00:00:52 <zodbot> Current chairs: jjmcd sparks 00:02:51 <jjmcd> need mchua_afk, shaunm es guide owners 00:03:42 <jjmcd> you didn't make an announcement on #fedora-docs 00:04:08 * sparks just did 00:05:26 * stickster 00:07:30 <sparks> Not a lot of people on tonight! 00:07:42 <sparks> Guess everyone is watching the Olympics 00:09:18 * sparks wonders if we have enough people here to handle the agenda 00:09:53 <jjmcd> Well, we need shaunm for the summit, but all we really wanted was to see if he had everything he needs 00:10:07 <sparks> ya 00:10:26 <stickster> everything he needs for live collaboration? 00:10:32 <sparks> yes 00:10:33 <stickster> or other stuff as well? 00:10:48 <jjmcd> Well, we certainly should ask 00:10:54 <jjmcd> hi rudi 00:11:02 <rudi> hi! 00:11:10 <jjmcd> he speaks! 00:11:11 <rudi> Wow! I can haz talk! 00:11:31 <stickster> #topic Desktop Help Summit and live collaboration 00:11:35 <joebebus> hi there! 00:11:37 <stickster> Oh, maybe that doesn't work for me :-) 00:11:44 <sparks> #chair stickster 00:11:45 <zodbot> Current chairs: jjmcd sparks stickster 00:11:48 <stickster> #topic Desktop Help Summit and live collaboration 00:12:09 <sparks> #link http://live.gnome.org/DesktopHelpSummit2010 00:12:18 <stickster> #info We need shaunm to let us know if he has what he needs for live collaboration, and what he is committed to do there 00:12:48 <jjmcd> We should also ask whether there are other areas we could help 00:14:34 <stickster> jjmcd: I'm writing the email 00:14:41 <jjmcd> coolness 00:14:50 <stickster> #action stickster writing email to list and Shaun to summarize and see if there's anything left for us to do 00:15:01 <stickster> #info There is a #desktop-help channel set up on Freenode, with zodbot eagerly awaiting 00:16:04 <stickster> Anything other than IRC or F-Talk? 00:16:11 <sparks> zodbot is so patient 00:16:47 <jjmcd> Not that we know of. He was going to check phones, projectors. We did ask about multiple projectors but not sure if needed 00:17:11 * stickster sent email 00:17:19 * stickster moves that we move on 00:17:25 <sparks> ok 00:17:32 <sparks> #topic Release Notes 00:17:39 <jjmcd> OK 00:17:55 <jjmcd> mchua was going to be here tonight to recruit helpers for alpha 00:18:08 <jjmcd> They are still working on talking points as of yesterday 00:18:18 <jjmcd> Talking points is a prereq for alpha RNs 00:18:47 <jjmcd> Also, cleaned out beats, put link to relevant feature pages in beats where I suspected they might belong 00:18:58 <stickster> The Talking Points are going to be set by Tuesday 2010-02-23 at the Marketing meeting 00:19:03 <jjmcd> but on some features that can be a bit of a challenge 00:19:10 <jjmcd> OK, great 00:19:44 <jjmcd> So if someone else would like to work with Mel next week (joebus?) that is a short task 00:19:54 <joebebus> OK 00:20:02 <stickster> What's the task? Writing the alpha RN? 00:20:06 <jjmcd> Yes 00:20:15 <stickster> joebebus: So you're taking that one? 00:20:17 <joebebus> I could try 00:20:21 <joebebus> my best 00:20:28 <sparks> that's all we ask 00:20:29 <jjmcd> I'll make sure I'm around to help 00:20:34 <stickster> joebebus: We have previous editions available too 00:20:37 <stickster> Let me find some links 00:20:40 <joebebus> ok 00:20:56 <stickster> #link http://fedoraproject.org/wiki/Fedora_12_Alpha_release_notes 00:21:09 <joebebus> I'll go check it out 00:21:27 <jjmcd> joebebus, mchua is in the UK I think, so not such a huge time delta 00:21:35 <stickster> joebebus: Keep in mind some sections of that page (top and bottom, really) can probably be copied 00:21:45 <joebebus> Ah 00:21:51 <stickster> jjmcd: Is mchua_afk traveling there this week? 00:22:02 <stickster> I thought she was in Rochester NY right now. 00:22:07 <stickster> Normally she's in Boston area. 00:22:21 <jjmcd> OK, her IRC said UK time 00:22:32 <jjmcd> but I talked to her late for the UK yesterday 00:22:48 <stickster> joebebus: Do you think you could have the page created by either Thursday night 2010-02-25 or Friday 2010-02-26? 00:22:50 <jjmcd> joebebus, I assume you are eastern or central 00:22:55 <joebebus> central 00:23:14 <joebebus> I never have gotten the time for the meeting correct 00:23:17 <jjmcd> bellsouth had to be one of those 00:23:24 <joebebus> yeah 00:23:35 <joebebus> I could probably get it done by one of those dates 00:23:48 <stickster> joebebus: If you can't, that's OK, but you need to let us know so we can help 00:23:53 <joebebus> ok 00:23:55 <stickster> If we don't know you can't do it, we can't help :_) 00:23:56 <jjmcd> The feature pages are a good place to get some background 00:24:03 <stickster> Oops, my nose fell off my face --> :-) 00:24:16 <joebebus> I am homeschooled and have no job... so I have plenty of time to commit ;) 00:24:25 <jjmcd> But the main feed will be the marketing talking points 00:24:35 <stickster> It looks like someone's started them here 00:24:36 <stickster> #link http://fedoraproject.org/wiki/Fedora_13_Alpha_release_notes 00:24:43 <stickster> So you won't be starting from scratch! 00:24:47 <joebebus> thats good 00:24:51 <joebebus> :-) 00:25:06 <stickster> #action joebebus to complete draft of F13 Alpha relnotes one-pager on wiki by Friday 2010-02-26 00:25:14 <stickster> #action jjmcd to bird-dog joebebus 00:26:29 * stickster thanks joebebus, with an extra dollop of gratitude for contributing! 00:26:52 <stickster> jjmcd: Anything else on release notes? 00:27:00 <joebebus> I am glad to help... I feel like I have been sitting around looking at the IRC logs for too long 00:27:09 <jjmcd> No, I think that's it. Status updated on the schedule page 00:27:12 <stickster> joebebus: That is an awesome pitch-in attitude! 00:27:20 <stickster> sparks: Move we move on? 00:27:30 <joebebus> Thank you! Im ready to move on 00:27:34 <sparks> joebebus: Thanks a bunch! 00:27:38 <stickster> +1000 00:27:44 <sparks> #topic New Guides 00:27:52 <sparks> Anyone have a new guide they'd like to discuss? 00:28:08 <joebebus> is there a terminal guide in the works? 00:28:21 <sparks> I think there is a CLI guide... is that what you mean? 00:28:25 <joebebus> oh yes 00:28:26 <joebebus> sorry 00:28:27 <sparks> CLI = command line interface 00:28:33 <joebebus> I am used to calling it terminal 00:28:37 <sparks> Someone one working on one... 00:28:42 <joebebus> ok 00:28:50 <jjmcd> I'm sure they wouldn't mind help, tho 00:28:56 <joebebus> ok 00:29:19 <sparks> move on? 00:29:30 <joebebus> I have nothing else to discuss 00:29:38 <jjmcd> go 00:29:53 <sparks> #topic Guide Status 00:30:06 <sparks> #link https://fedoraproject.org/wiki/Docs_F13_schedule 00:30:14 <jjmcd> none of the guide leaders have yet accepted their schedule 00:30:15 <sparks> ^^^ That's the link to the schedule for the docs 00:30:46 <rudi> Sorry; I'll get onto that today 00:30:52 <sparks> #action email to the list asking guide leads to accept their schedules 00:31:20 * sparks will get on it tonight as well 00:31:42 <sparks> jjmcd: Did you/we ever come up with updated text to go in the F12 RN and SG for the PolicyKit thing? 00:32:10 <jjmcd> No. I was looking for that the other day, couldn't find the bug. DId it get deleted or something? 00:32:22 <sparks> Not that I'm aware of. 00:32:43 <jjmcd> I was going through the F12 bugs and that one never surfaced 00:33:14 <sparks> Didn't we reference the bug in the RN and SG? 00:33:36 <jjmcd> Not in the rn - I'll look in the SG 00:33:42 <sparks> Should be the same text 00:33:57 <jjmcd> RNs were out before we discovered the problem 00:34:13 <joebebus> If I may ask what is the SG? I know the RN is Release Notes... 00:34:19 <stickster> Security Guide? 00:34:20 <sparks> SG is the Security Guide 00:34:23 <stickster> *jinx! 00:34:26 <jjmcd> Oh, maybe the common bugs, I'll look 00:34:31 <joebebus> Thank you :-) 00:35:00 * stickster couldn't find that bug in BZ just now either. 00:35:09 <sparks> hmmm 00:35:21 <sparks> maybe it was a figment of our imaginations 00:35:33 <jjmcd> I swatted all the easy ones and was surprised that one wasn't there 00:36:20 <stickster> Well, let's decide what to do here and record it, and move on 00:36:37 <stickster> Do we want to have an update to the relnotes as currently published? 00:36:43 <jjmcd> Yes 00:36:50 <stickster> OK, who's going to make the update and republish? 00:36:59 <sparks> Well, I'd like to update the F12 docs and remove it from F13 00:37:06 <jjmcd> I have a number of fixes in git, just a couple more to do. I will make the update, Sparks will push the rpm 00:37:14 <stickster> Awesomeness! 00:37:26 <sparks> I will? I mean, I will! 00:37:39 <stickster> #action jjmcd to make update to F12 docs in git 00:37:45 <joebebus> Yay! He will! 00:37:48 <jjmcd> I think I have 2 others to do before I build the rpm 00:37:53 <stickster> #action sparks will push F12 updated rpm 00:38:02 <stickster> oh crud 00:38:03 <stickster> #undo 00:38:03 <zodbot> Removing item from minutes: <MeetBot.items.Action object at 0x27c2bf90> 00:38:04 <stickster> #undo 00:38:04 <zodbot> Removing item from minutes: <MeetBot.items.Action object at 0x2b6f948374d0> 00:38:14 <stickster> #action jjmcd to make update to F12 docs in git to fix PackageKit security information 00:38:21 <jjmcd> there ya go 00:38:24 <stickster> #action sparks will push F12 updated rpm pursuant to jjmcd's change for PackageKit info 00:38:39 <stickster> Anything else on this? 00:38:46 <sparks> Is that all? I want to talk about Transifex. 00:38:52 <rudi> That permission issue is also what was blocking branching 00:39:07 <stickster> #topic Transifex update 00:39:07 <rudi> Sorry, PackageKit issue 00:39:29 <stickster> oops rudi, did I go past you there? 00:39:41 <rudi> Yeah; but it's no biggie 00:39:53 <stickster> #undo 00:39:54 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x2b6f969a4710> 00:39:57 <stickster> oh bugger 00:40:01 <stickster> #action sparks will push F12 updated rpm pursuant to jjmcd's change for PackageKit info 00:40:11 <stickster> Well, sorry zodbot and all :-D 00:40:15 <jjmcd> We basically need to craft some weasel words 00:40:18 <stickster> yeah 00:40:44 <stickster> #undo 00:40:45 <zodbot> Removing item from minutes: <MeetBot.items.Action object at 0x2b6f945ba5d0> 00:40:49 <stickster> OK, now we're clean :-) 00:40:54 <sparks> stickster: You're good, nwo 00:40:55 <sparks> now 00:41:05 <joebebus> Isn't Transifex for translating documents? 00:41:15 <stickster> rudi: So the PK issue needs to be fixed before branching? 00:41:21 <sparks> joebebus: Yes... 00:41:26 <joebebus> ok 00:41:35 <joebebus> I am reading about it 00:41:56 <jjmcd> We still have some weeks before we HAVE to branch 00:42:07 <rudi> I think so, yes 00:42:23 <stickster> rudi: jjmcd: sparks: Is it just that we want to fix it so the new branch inherits the change? 00:42:28 <stickster> I'm confused, but that's not new for me 00:42:38 <sparks> Well... 00:42:47 <jjmcd> No, the release notes are a start from scratch 00:42:47 <rudi> jjmcd -- yeah, this time round though, the branching will also have implications for POT/PO file generation 00:43:06 <stickster> time out guys 00:43:22 <stickster> Are we talking about the PackageKit security policy change issue now, or Transifex? 00:43:27 <sparks> PK 00:43:29 <jjmcd> Tfx 00:43:33 <jjmcd> LOL 00:43:34 <stickster> haha 00:43:36 <stickster> See? 00:43:37 <joebebus> LOL 00:43:39 <rudi> jjmcd -- including those bits of boilerplate test that don't change much from release to release 00:43:47 <sparks> rudi: What are YOU talking about? 00:43:56 <stickster> Yeah, let's get one topic at a time. 00:44:04 <rudi> Both; the one being the trigger for the other 00:44:18 <stickster> rudi: How so? 00:44:18 <sparks> rudi: So can we move the topic to Transifex? 00:44:43 <rudi> stickster -- it's always been our intention to leave past releases of guides in a buildable state 00:44:57 <rudi> So once the PK issue is solved in the release notes 00:45:01 <sparks> #topic Transifec update 00:45:17 <rudi> We can branch at that point to leave the RN in a (publican 0) buildable state 00:45:23 <joebebus> Transifec? 00:45:26 <stickster> rudi: I get it. 00:45:37 <sparks> #undo 00:45:37 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x2b6f966bc150> 00:45:40 * sparks stops trying 00:45:48 <stickster> #topic Transifex update 00:45:51 <rudi> Yeah; so we can then move on to make the Master branch (and therefore F13) Publican 1 buildable 00:45:55 <jjmcd> OK, so the F13 branch (Publican 1) waits until we are done with the F12 RPM 00:46:11 <rudi> Which is a prerequisite for *whatever* Tx solution we go with 00:46:23 <rudi> jjmcd -- exactly! :) 00:46:33 <jjmcd> OK, np 00:46:57 <jjmcd> I see the F12 update within the next couple weeks, we have some time before we can actually begin F13 XML 00:46:58 <stickster> rudi: So are we waiting so that we don't have to enter a second "project" into Tx to handle translating the small bit of fixed content for PK? 00:47:41 <jjmcd> stickster, there are another 5-10 bugs already fixed in git waiting for a build so it's not just Pk 00:47:47 <rudi> More that we can close off the F12 doc in a sane state 00:48:32 <stickster> O... K... I guess I'm still a bit confused, because I thought the point of branching was to enable that work to continue without holding up the other branch(es) 00:48:40 <stickster> But let's move on, you don't need to convince me :-) 00:48:54 <sparks> So... 00:49:15 <sparks> What's the status of Transifex? I know there were several updates to the ticket but I haven't had a chance to look at them. 00:49:25 <stickster> There is a staging instance at https://translate.stg.fedoraproject.org/ 00:49:31 <stickster> It uses your FAS credentials. 00:49:47 <ricky> It's currently waiting on more testing - my two tests have worked fine, and we've worked out the last bug in the migration instructions, as far as I know 00:50:06 <ricky> Note that it uses the credentials from admin.stg.fedoraproject.org/accounts/, so if you changed your password recently, the data could be out of sync with the real FAS 00:50:21 <ricky> There are two test repos setup - please test :-) 00:50:33 <stickster> ricky: Oh yeah, I forgot that part. Everyone ignore my FAS statement :-) 00:50:41 <stickster> ricky: What do you need people to test? 00:50:54 <stickster> #link https://translate.stg.fedoraproject.org/ 00:51:12 <ricky> Translators should probably check that their translation submissions work fine, and that the multi-POT support works as expected 00:51:30 <ricky> If they don't find any failures, then we should be ready to move onto production 00:51:47 <stickster> #info Needs more testing by Docs and L10n, specifically translators should check that submissions work; Docs people should test that multi-POT (Publican-style) support is working 00:51:58 <ricky> Note that submissions are only enabled to the test repos 00:52:13 <ricky> So refreshing stats on any other repos will most likely fail - that's expected 00:52:16 <stickster> ricky: Is that just the two that are listed in the ticket? 00:52:27 <ricky> The test repos are in https://translate.stg.fedoraproject.org/projects/p/publican/ 00:52:33 <ricky> And one more thing that translators should be aware of 00:52:51 <ricky> This release of transifex changes URLs - the /p/ in the above URL didn't use to be there 00:52:58 <ricky> So just something to note 00:53:11 <stickster> #info submissions are only enabled to the test repos at https://translate.stg.fedoraproject.org/projects/p/publican/ 00:53:23 <stickster> #info note extra /p/ in that URL 00:54:13 <stickster> ricky: The "localhost" repo is something anyone can push random crap to and it won't affect the actual Virtualization Guide repo on fedorahosted, right? 00:54:42 <ricky> Yup - I should actually correct my statement again 00:54:49 <ricky> submissions are only enabled to the localhost test repo, sorry :-) 00:54:57 <stickster> Yes, just discovered that too 00:55:02 <stickster> #undo 00:55:03 <zodbot> Removing item from minutes: <MeetBot.items.Info object at 0x28010610> 00:55:03 <stickster> #undo 00:55:04 <zodbot> Removing item from minutes: <MeetBot.items.Info object at 0x28010dd0> 00:55:20 <stickster> #info submissions are only enabled to the "virt-guide-localhost" test repo at https://translate.stg.fedoraproject.org/projects/p/publican/ 00:55:24 <stickster> #info note extra /p/ in that URL 00:55:32 * jjmcd suspects that stickster must be an old HP calculator guy 00:55:37 <stickster> heh 00:55:43 <jjmcd> or forth programmer 00:55:45 <stickster> rudi: This reminds me of something 00:56:13 <stickster> rudi: There is a problem in ccurran's Virtualization_Guide repo, in that he's got both multi-POT format in the pot/ folder, and a standard single-POT in the po/ folder 00:56:36 <stickster> rudi: He may have been maintaning that for compatibility reasons while Tx was broken 00:56:39 <rudi> Let me see 00:56:56 <rudi> It might also have to do with the choice of book... 00:56:59 <stickster> But when Tx is fixed, that hack will break 00:57:09 <rudi> Neither of the directories linked to were ever intended for Tx access 00:57:17 <stickster> Aha 00:57:21 <rudi> s/directories/branches 00:57:31 <stickster> Well, as it turns out, if you get rid of the po/ file all works as expected 00:57:37 <stickster> s/file/folder/ 00:58:45 <stickster> OK, so specifically... rudi, will you check that behavior here on the staging instance is what you expect? 00:59:19 * stickster looking for action items so we can give Infra what they need to move this to production when the freeze ends, and get on with the biz 01:00:08 <stickster> rudi: If you want to check a specific guide, make the request in the ticket and I'm sure ricky will be happy to add it to the Tx-staging instance. 01:00:39 <rudi> stickster -- I'll check 01:00:53 <stickster> #link https://fedorahosted.org/fedora-infrastructure/ticket/1455 01:01:02 <rudi> And I confirm that the doubled-up PO files exist even in the branch intended for Tx access (f12-tx) 01:01:24 <rudi> I'm sure it's just an oversight on my part (I handled the branching) 01:02:23 <stickster> #action rudi to check on Tx staging behavior for one or more official guides and will report results to https://fedorahosted.org/fedora-infrastructure/ticket/1455 01:02:29 <stickster> Anything else on this then? 01:02:41 <rudi> First impressions are that it's right on the money! :) 01:02:47 <stickster> yeah baby! 01:03:13 <stickster> Shall we move on? 01:03:23 <joebebus> Ok 01:03:45 <stickster> sparks: ready? 01:03:52 <joebebus> I am 01:03:54 <sparks> Okay 01:04:09 <sparks> #topic Making docs.fp.o accessible for non-JavaScript equipped browsers 01:04:20 <sparks> Since rudi is here tonight... 01:04:42 <rudi> I've always been here :) 01:04:49 <rudi> Just muzzled :) 01:05:07 <sparks> Last week we discussed an alternative to the JavaScript for docs.fp.o. 01:05:18 <rudi> Yep; I'm good to take that 01:05:20 <sparks> rudi: Can you make that page non-JS capable? 01:05:24 <sparks> TU 01:05:35 <sparks> moving on 01:05:40 <rudi> NP 01:05:44 <sparks> #topic Outstanding BZ Tickets 01:05:53 <sparks> #link https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classificatio… 01:06:04 <stickster> rudi: There's a bug for that JS issue by the way 01:06:14 <stickster> rudi: https://bugzilla.redhat.com/show_bug.cgi?id=544656 01:06:19 <rudi> Thanks :) 01:06:23 <stickster> np, hth 01:06:28 <sparks> I'm still planning on planning a bug killing session on an upcoming weekend. 01:06:36 <stickster> Any idea which weekend? 01:06:45 * stickster will set aside some time to help as long as he can plan for it 01:06:48 <sparks> BUT, don't let that stop you from visiting the above link and starting today! 01:07:09 <sparks> stickster: I don't. I haven't been able to get farther than the next day in my calendar. 01:07:42 <stickster> sparks: Can we pencil something in now? I find that's very helpful in getting people to commit. 01:08:05 <stickster> i.e. "Show up on X date" as opposed to "Let's do this someday" 01:08:20 <sparks> How about March 6? 01:08:25 <stickster> sparks: THAT IS WEIRD. 01:08:30 <stickster> I was looking at the exact same weekend. 01:08:50 <sparks> :) 01:09:13 <stickster> Cool, shall we set aside, say, 10am-4pm EST as core hours? 01:09:36 <sparks> WORKSFORME 01:09:49 <stickster> Work can continue late if we have West Coasties, and/or we can add a late night session EST to catch anyone willing/able in BNE 01:09:56 <stickster> jjmcd: Sound do-able? 01:10:04 <stickster> quaid: ^^^ 01:10:12 <jjmcd> Looks like one of the few weekends I CAN make it 01:10:16 <stickster> awesome! 01:10:33 <joebebus> I'd have to check my calendar 01:11:01 <stickster> #agreed Saturday March 6, 10am-4pm EST (1500-2100 UTC) for Docs bug stomping session! 01:11:02 * sparks marks his calendar appropriately 01:11:23 <joebebus> I like late night sessions 01:11:26 <joebebus> I think I can make it 01:11:57 <stickster> #undo 01:11:58 <zodbot> Removing item from minutes: <MeetBot.items.Agreed object at 0x28010dd0> 01:12:01 * quaid reads up 01:12:02 <stickster> #agreed Saturday March 6, 10am-4pm EST (1500-2100 UTC) for Docs bug stomping session in IRC Freenode #fedora-docs 01:12:20 <stickster> #info core hours can be extended for extra participation 01:12:28 <joebebus> Ah I make a mistake. That is good too 01:12:32 * quaid is great with that weekend 01:12:34 <joebebus> That time is good 01:12:38 <joebebus> me too 01:13:01 <stickster> WOOHOO! 01:13:32 <stickster> sparks: Will you announce on Planet? 01:13:32 <sparks> Okay, anything else on this? 01:13:54 <sparks> #action sparks to announce the bug stomping session on Planet 01:13:58 <stickster> w00t 01:14:33 * stickster is close to hard stop, fyi 01:14:37 <sparks> Anything else on this? 01:14:46 <stickster> nada 01:15:09 <sparks> #topic Anything else? 01:15:18 <sparks> Anything else anyone wants to talk about? 01:15:37 <joebebus> What if I need help with writing on the RN? 01:15:46 * jjmcd will be around 01:15:55 <joebebus> ok 01:16:12 <stickster> joebebus: Feel free to pipe up on IRC #fedora-docs anytime 01:16:14 <jjmcd> Ping me on #Fedora-docs 01:16:21 <joebebus> Ok 01:16:21 <jjmcd> Yeah, exactly 01:16:37 <joebebus> I will be sure to do that if (when) I need help 01:16:37 <stickster> joebebus: camping there is welcome, we can help you with that if needed 01:16:38 <jjmcd> There are lots of people not typing there 01:17:05 <jjmcd> or dm me on twitter if you have to :-) 01:17:10 <joebebus> ok 01:17:10 <stickster> sparks: I'm really happy to see a new contributor here tonight. I'd like to see if we can ramp up a few people who've piped up on the list recently. 01:17:30 <sparks> Yeah, I need to play some serious catch up on the list. 01:17:43 <stickster> We seem to lose people right at the outset if we don't get them involved quickly with an easy social contact. 01:18:07 <joebebus> I have noticed that 01:18:12 <stickster> My involvement with Fedora probably turned very specifically on my contact with quaid 01:18:24 <jjmcd> Yeah, we need more folks looking over the list. If i'm heads-down on something, odds are sparks is too 01:19:01 <stickster> The list is not very high traffic, so we can do a lot better with on-ramping 01:19:33 <sparks> Okay, anything else? 01:19:36 <rudi> It would also help if we had a nice queue of easy tasks somewhere that we could feed to people as they come on board 01:19:50 <joebebus> I second that 01:19:54 <stickster> rudi: Yes. I proposed one to new entrant Eliot Smith this afternoon 01:19:57 <rudi> Tsagadai suggested this some time ago, but we haven't managed to pull it off yet 01:20:13 <stickster> rudi: It's as simple as marking bugs in our queue with EasyFix keyword. 01:20:22 <rudi> True 01:20:24 <stickster> That's an existing, well known keyword project wide 01:21:00 <stickster> #info Use EasyFix keyword for easy BZ bugs for new people 01:21:03 <sparks> I'm not sure what would be considered "easy" 01:21:26 <sparks> You have to know how to interface with the guides and how to file a diff... 01:21:37 <stickster> sparks: That information should be on the wiki page for each guide. 01:21:40 <stickster> If it's not, that's a bug. 01:21:59 <stickster> So the EasyFix can apply to: 01:22:08 <stickster> 1. Read the guide's Trac wiki page to check it out 01:22:12 <stickster> 2. Make the small fix needed 01:22:19 <stickster> 3. Read the guide's Trac wiki page to email your patch 01:22:22 <stickster> done. 01:23:17 <stickster> The things that happen in between 1 and 3 are where people may need mentoring, and that's natural and expected. We need to take advantage of that stage to be convivial, helpful, and grateful :-) 01:23:25 * stickster eof 01:23:36 <stickster> I have to run guys 01:23:39 <stickster> Thanks for the great meeting 01:23:54 <sparks> Okay... anyone have anything else? 01:24:02 <jjmcd> sparks, it was a really great meeting 01:24:12 <joebebus> it was :-) 01:24:24 <sparks> Well, glad folks came out to make it great! 01:24:34 <sparks> thanks everyone 01:24:37 <sparks> #endmeeting - -- - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLhc6vAAoJEDbiLlqcYamxtt0QAKVOQB7cncvXwvkUATmqcFdH Rlxk3LGNB+uLkOn2HdRviH12iyplQnbbZHu4a5D+dytbgQUZZ3tSDWnvAcOKKudR PQoQcqgE3mDVjYAS/ou/3Gd9wo/qTaFMFVmPhClitoHo1eTWnBD4UrcsTTcQJRub itkYGQC2S6AApIL6sGQHiVKm+P3QLNr5WvCUseizHfjamlDvQtSGyRRlGpsHjuXG wz7Zd8YmKj5D4i8s42pvMHhQijKzghZ8b2cUq8LdxOooSkokZm6W6AOQFkocQgw5 H3u6YUwajBgJrF/f0eHjstIhKvnuCOgkYrcr5I2OFqYNuv+fDkntvpMQr8PauBKy 2m+W3o07dd75OP/dI8wD3U9Czd5dwDB+MnRuFSi9zE1cCrIGcmZg8S3UDKce8MGp 4dty2aeNQlnx/XFS3UJ8LY0SovWPQjNjJm56jNi+nbLhtZa2+TggWjCAqpR+rp+F 2ZCa2tySlzUwuV9Iovu7wuM+1oX/yx5oqBHRVoMF8KZgQxINo0wSKLt9ZFKynnZ9 rXfZ39zM1R2xnWgm0ALF5JWBidpwk2y2PE/CW1yVUd1tstd8pp+CyAs3/CJ0mdEJ YOPzbfX/ysfZq5BHtVLJKxG6bOul0aPSi/MOuqhn7pNkNixKJolR8DI21yUmteFw DfgnlNJnhcbs442hdoSy =/X2H -----END PGP SIGNATURE-----

1 0

Docs Meeting 2010-02-11 Summary
by Eric Christensen 25 Feb '10

25 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings =================================================================================================== Meeting started by sparks at 00:02:41 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2010-02-11/fedora-meeting.2… . Meeting summary - --------------- * Roll Call (sparks, 00:02:51) * Desktop Help Summit (sparks, 00:06:50) * LINK: http://live.gnome.org/DesktopHelpSummit2010 (sparks, 00:07:07) * ACTION: stickster Find out if shaunm or proxy is willing to run IRC in real time during hackfest (stickster, 00:14:13) * ACTION: stickster Find out if shaunm will have access to conference phone (stickster, 00:14:22) * ACTION: stickster Find out if shaunm wants to use gobby.fp.o or wiki for other collaboration options (stickster, 00:14:55) * ACTION: stickster Provide pointers to shaunm for Fedora Talk recording options (stickster, 00:16:42) * shaunm will have a projector at the site, and is checking into the availability of a conference phone. (stickster, 00:20:47) * Release Notes (sparks, 00:25:48) * LINK: http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-tasks.html (stickster, 00:35:47) * LINK: http://poelstra.fedorapeople.org/schedules/f-13/ (stickster, 00:36:16) * New Guides (sparks, 00:40:06) * Guide Status (sparks, 00:41:12) * LINK: https://fedorahosted.org/fedora-infrastructure/ticket/1455 (stickster, 00:44:06) * LINK: https://fedoraproject.org/wiki/Docs_Project_meetings#Guides (sparks, 00:47:23) * ACTION: sparks to request guide leads update the table before next week (sparks, 00:48:58) * Making docs.fp.o accessible for non-JavaScript equipped browsers (sparks, 00:55:21) * To see the problem, install w3m or links, and use it to visit http://docs.fedoraproject.org -- try to select an existing guide (sparks, 00:55:40) * rudi reports Good response from L10n for DocBook stuff... committing upstream but might not make it down in time for F13 (stickster, 00:56:36) * I need to approach some translators to fix some slight changes we made to the Common Content in Publican 1; but all RH-sponsored languages (plus a few others) are in good shape (sparks, 00:58:31) * ACTION: laubersm Bring branching topic to docs list to decide how we want to do this going forward, and record it for posterity. (stickster, 01:03:01) * ACTION: stickster Ask rudi through list to provide non-JS fallback (HTML form submit or something else). If he can't do it, file ticket with websites to ask for help. (stickster, 01:08:05) * All other business (sparks, 01:11:00) * ACTION: sparks to setup a bug busting weekend (sparks, 01:11:15) Meeting ended at 01:14:50 UTC. Action Items - ------------ * stickster Find out if shaunm or proxy is willing to run IRC in real time during hackfest * stickster Find out if shaunm will have access to conference phone * stickster Find out if shaunm wants to use gobby.fp.o or wiki for other collaboration options * stickster Provide pointers to shaunm for Fedora Talk recording options * sparks to request guide leads update the table before next week * laubersm Bring branching topic to docs list to decide how we want to do this going forward, and record it for posterity. * stickster Ask rudi through list to provide non-JS fallback (HTML form submit or something else). If he can't do it, file ticket with websites to ask for help. * sparks to setup a bug busting weekend Action Items, by person - ----------------------- * laubersm * laubersm Bring branching topic to docs list to decide how we want to do this going forward, and record it for posterity. * shaunm * stickster Find out if shaunm or proxy is willing to run IRC in real time during hackfest * stickster Find out if shaunm will have access to conference phone * stickster Find out if shaunm wants to use gobby.fp.o or wiki for other collaboration options * stickster Provide pointers to shaunm for Fedora Talk recording options * sparks * sparks to request guide leads update the table before next week * sparks to setup a bug busting weekend * stickster * stickster Find out if shaunm or proxy is willing to run IRC in real time during hackfest * stickster Find out if shaunm will have access to conference phone * stickster Find out if shaunm wants to use gobby.fp.o or wiki for other collaboration options * stickster Provide pointers to shaunm for Fedora Talk recording options * stickster Ask rudi through list to provide non-JS fallback (HTML form submit or something else). If he can't do it, file ticket with websites to ask for help. * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * sparks (109) * stickster (91) * jjmcd (34) * laubersm (19) * quaid (18) * shaunm (9) * zodbot (8) * radsy (7) * ianweller (1) * bcotton (1) * mprice (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLhc5KAAoJEDbiLlqcYamxlrEQAMOmocCf10njwJHHZttPqc1A QQGTg/g3Jg3DCuYrI7VF0Or8DzpujFpB+7fusIaqXKyZRizV4VjFH5jAMiyEJACt pXNNxQc4edpkWbtKHCo4XTfyFLcM4TWmIo194DDN4fLYU2MdwD4d7n6THFSLr+nS 9KE6MtcuyGUz1eHLEXA7tYNntCom4gr77VZ1V73sjGMfUF0Slr+/XcELav0v9gRK rUWsCWXPdosiVTl9TPr3JQCVLqfbv/Vy54kYGBYBMdAsLV/495sYsujKi35VOGOM 51aaXfz+Hy3pBfurXRzLpV2kkOHYG73Kv3xRyDXSoge900fWuYRdG4iIdZCyjE4x 75zuA+6d10nH8TIzFnGrGz5EeQjlp7FM9BZXfIxcjZseghKr6trKa+UZP5WCK14t LXNUL1BW2JuhbG+8gc1HY6tDtSn4Wq1YR38TQkSnxHqaNkzXFu7t8u48nGOJ8Kji L/TaUccX/RZJYDvDwM6nfzcNyNoY9yDJBMvbsrW02NyyNRKE9Trey3+AoFKrX3xt Duuzqvaob++fzLPC51lEgaYviV5+3oPjBu31K9k4sMA3NFjsirrqPD+3yHunyLoN pIvSBKo6xYrUsT52RaIE8fA7dp6ZWWIowUw4bB0kg/reFnCcyKMYHKVwk+Ctwnrz w/jXqVdBb4GM/gPBOHZ4 =+vbV -----END PGP SIGNATURE-----

1 0

Docs Meeting 2010-02-11 IRC log
by Eric Christensen 25 Feb '10

25 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 00:02:41 <sparks> #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:02:42 <zodbot> Meeting started Thu Feb 11 00:02:41 2010 UTC. The chair is sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:02:44 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:02:51 <sparks> #topic Roll Call 00:02:52 * sparks 00:02:53 * ianweller is sorta kinda not really here 00:03:26 * laubersm is here (for a change) 00:03:27 * stickster 00:03:53 * jjmcd just 00:03:57 * mprice is here 00:04:12 * bcotton is here and cooking 00:04:36 <radsy> . 00:04:45 <sparks> #chair jjmcd 00:04:46 <zodbot> Current chairs: jjmcd sparks 00:05:43 * quaid is here 00:05:52 <sparks> WOOT! 00:06:41 <sparks> Okay... Let's get started. 00:06:50 <sparks> #topic Desktop Help Summit 00:07:07 <sparks> #link http://live.gnome.org/DesktopHelpSummit2010 00:07:16 <sparks> jjmcd: Are you still planning on going? 00:07:26 <jjmcd> yes of course 00:07:30 <sparks> Great! 00:07:45 <laubersm> I know I will NOT be in Chicago the week before or after... they couldn't get me scheduled there. 00:07:53 <laubersm> I do not know where I will be those weeks though 00:07:54 <jjmcd> bummer 00:08:01 <sparks> laubersm: Handy. Isn't that always how it works? 00:08:13 <jjmcd> But at least now I can be pretty confident there won't be a Monday 00:08:14 <quaid> can we use the power of remote access? 00:08:21 <sparks> Did we ever figure out a remote solution for shaunm? 00:08:25 <laubersm> If it is not too hard to work out the travel, there is still an option - it is penciled in on my calendar 00:08:35 <jjmcd> We've been talking about that 00:08:53 <stickster> sparks: I mentioned several last week. shaunm didn't follow up with me about anything. 00:08:57 <sparks> okay 00:09:05 <laubersm> remote options would be good. 00:09:08 <stickster> shaunm: I suggested several options last meeting, including IRC and Fedora Talk. 00:09:16 <stickster> shaunm: What would help you move forward with this? 00:09:18 <sparks> Can someone follow up with shaunm on remoting the Summit? 00:09:30 <stickster> Do you want me to raise a topic on our docs list, or elsewhere? Or something else? 00:09:51 * sparks didn't see shaunm on the roll call... 00:09:58 <sparks> stickster: Maybe email directly? 00:10:04 <quaid> stickster: cool, on list would mean we could contact people who may have the new Events A/V Kit (right?) 00:10:06 * stickster thinks we need to have a specific commitment from shaunm that he can do one or more of some remote access thingy. 00:10:19 <quaid> +1 00:10:19 <stickster> quaid: Sure 00:10:24 <jjmcd> I think we concluded all we needed was a conference phone 00:10:38 <quaid> yep 00:10:42 <jjmcd> Since there is a Chicago dial in number 00:10:48 <quaid> "all we need" is sometimes a long way, though 00:10:49 <stickster> So let's be clear about what you want me to do 00:10:52 <sparks> #action stickster to work with shaunm on remoting the Desktop Help Summit and make sure everything is squared away. 00:10:57 <sparks> :) 00:11:00 <stickster> let's be clearer than that please. 00:11:15 <stickster> 1. See if shaunm is willing to run an IRC session in real time alongside hacking 00:11:20 <jjmcd> Yes, make sure we have a conference phone and a phone line where we will be meeting 00:11:27 <stickster> 2. See if shaunm will have access to a conference-able phone. 00:11:41 <quaid> 3. Gobby 00:11:43 <quaid> 4. Wiki 00:11:55 <stickster> Wiki is not that good for realtime participation, frankly. 00:12:05 <stickster> Although if it's needed, certainly GNOME has one. 00:12:22 <stickster> Wiki is great for capturing things to a more semi-permanent state, just not good for r-t collaboration. 00:12:29 <quaid> wiki is crucial for ongoing status updates to allow for async 00:12:39 <stickster> or meetbot 00:12:42 <quaid> every ~1 hour dump gobby docs 00:12:47 <quaid> well, sort of 00:13:08 <sparks> We have a lot of options... I'm not sure shaunm has had them all laid out in front of him, though. 00:13:16 <quaid> this all comes down to, are folks who are present willing to assign documenters, etc. 00:13:23 <sparks> He liked the idea of using Talk, IIRC. 00:13:31 * stickster wonders if he can #action properly hee 00:13:33 <stickster> *here 00:13:39 <sparks> you should be able to 00:13:48 <sparks> #chair stickster 00:13:48 <zodbot> Current chairs: jjmcd sparks stickster 00:13:51 <sparks> just to be sure 00:14:00 <stickster> #action stickster Find out if shaunm or proxy is willing to run IRC in real time during hackfest 00:14:07 <stickster> #undo 00:14:08 <zodbot> Removing item from minutes: <MeetBot.items.Action object at 0xff73550> 00:14:10 <stickster> #undo 00:14:11 <zodbot> Removing item from minutes: <MeetBot.items.Action object at 0x2b599d4ed6d0> 00:14:13 <stickster> #action stickster Find out if shaunm or proxy is willing to run IRC in real time during hackfest 00:14:22 <stickster> #action stickster Find out if shaunm will have access to conference phone 00:14:47 * sparks forgets about #undo 00:14:55 <stickster> #action stickster Find out if shaunm wants to use gobby.fp.o or wiki for other collaboration options 00:15:01 <stickster> OK, anything else? 00:15:01 * laubersm thinks undo is cool 00:15:30 * sparks thinks that is all... 00:15:46 <sparks> stickster: did we ever get that recording of conference rooms working? 00:15:51 <stickster> sparks: Yes 00:16:08 <sparks> might want to mention that as well 00:16:22 <stickster> What's not ready is a web app to make it a smoother fit for people who don't know much about it. 00:16:42 <stickster> #action stickster Provide pointers to shaunm for Fedora Talk recording options 00:17:09 <shaunm> oh, shaun shaunm shaunm 00:17:42 <sparks> heh... speak his name enough and he appears! 00:17:46 <shaunm> IRC absolutely yes. don't see any problems with that. I need to check if we can get a conference phone 00:17:54 * shaunm puts it on his todo list for tomorrow morning 00:18:03 <stickster> hehehe 00:18:29 <stickster> shaunm: We're big Gobby fans around here too 00:18:39 <shaunm> do we want to transcribe to irc real-time? 00:18:54 <quaid> as close as you can 00:19:04 <laubersm> I will likely only be able to participate remotely 00:19:07 <laubersm> so yes 00:19:08 <quaid> if >1 person is in IRC and transcribing/note taking 00:19:11 <stickster> shaunm: At our live sessions, we rotate duty for that around the room per hour or so 00:19:18 <laubersm> it also make good logs 00:19:20 <stickster> So no one's stuck doing it all day. 00:19:26 <quaid> what about projecting IRC on the wall so people can more closely participate? 00:19:49 <stickster> shaunm: Will you have a projector available at the site? 00:20:25 <shaunm> yes 00:20:32 <jjmcd> 3 - slides, gobby, irc 00:20:34 <stickster> shaunm: Awesome! 00:20:47 <stickster> #info shaunm will have a projector at the site, and is checking into the availability of a conference phone. 00:20:56 <shaunm> (so I was told. I should double-check that though) 00:20:59 <sparks> shaunm: We also have meetbot, too 00:21:32 <shaunm> yes, I'm jealous of your bot's powers. I want him for my gnome meetings 00:21:42 <sparks> we rent him out on the weekends 00:21:51 <shaunm> heh 00:22:07 <jjmcd> shaunm, I think we stole him from some other distro 00:22:24 <jjmcd> They're still trying to find him 00:22:44 <sparks> shhh they may be listening! 00:23:18 <stickster> shaunm: Why don't we make a meeting room for your event, and I have the ability to invite zodbot there. 00:23:26 <jjmcd> Watch out for guys with them funny spirals on their shirt 00:23:54 <stickster> shaunm: Let's work on this in #fedora-docs so the meeting can proceed 00:24:15 <shaunm> sounds good 00:24:58 <sparks> Anything for the summit? 00:25:43 <sparks> Okay, moving on... 00:25:48 <sparks> #topic Release Notes 00:25:59 <sparks> jjmcd: What's going on with the RN? 00:26:04 <sparks> Are you still on schedule? 00:26:22 <jjmcd> YEah, but I blew it yesterday so gonna need to post to mktg-list 00:26:31 <jjmcd> showed up at the wrong place :-( 00:26:50 <sparks> heh 00:27:15 <sparks> Are you getting good input? Should a message be sent out "encouraging" submissions? 00:27:15 <jjmcd> I thought it was kinda techhie for mktg, turned out to be fesco 00:27:44 <jjmcd> I was surprised to see some input, but real wiki input needs to be solicited a little later 00:27:54 <sparks> ok 00:27:56 <laubersm> I think they are either in their channel or in meeting-1 00:28:21 <jjmcd> Yeah, too late when I figured out they were elsewhere 00:28:31 <quaid> is this back around to recruiting beat writers and relevant content not in Feature pages? 00:29:14 <jjmcd> Yes, we are still over a week from the one pager, so pretty early to start soliciting beat writers 00:31:16 <sparks> jjmcd: Need anything from me/us? 00:31:25 <jjmcd> Not yet 00:32:33 <sparks> Okay... anyone have anything else on the RNs? 00:32:35 <quaid> no worries about the content on the one pager? 00:32:46 <quaid> quantity and importance, mainly 00:33:16 <jjmcd> And on F12 marketing mostly took the lead there 00:33:31 <jjmcd> Our role was mainly to keep them on point 00:33:38 <jjmcd> Alpha RN's are a one pager 00:34:17 <jjmcd> Which is why it is so different from beta/GA 00:34:41 * stickster notes that talking points discussion is underway 00:34:53 <stickster> sparks: When is the publication date for one-page relnotes for Alpha? 00:35:30 <sparks> stickster: I'd have to look... I forget 00:35:44 <stickster> Ah 00:35:47 <stickster> #link http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-tasks.html 00:35:48 <sparks> jjmcd: Did the schedule ever get published as an .ical? 00:35:49 <stickster> March 1 00:35:57 <sparks> TU 00:36:08 <jjmcd> poelcat has it on his people site 00:36:11 <stickster> sparks: They're always published alongside an .ics file 00:36:14 <sparks> So just over two weeks 00:36:16 <stickster> #link http://poelstra.fedorapeople.org/schedules/f-13/ 00:37:11 * sparks adds that to his calendar. 00:37:18 <sparks> I knew I had been lost... 00:38:09 <sparks> So Beats and Feature review doesn't start until 23 Feb 00:38:19 <jjmcd> right 00:38:44 <sparks> Okay, I'm good, now 00:39:44 <stickster> Next? 00:39:47 <sparks> Okay, anything else? 00:40:02 <sparks> Moving right along... 00:40:06 <sparks> #topic New Guides 00:40:18 <sparks> Anyone have a new guide they'd like to present/talk about? 00:40:54 <sparks> No>? 00:41:12 <sparks> #topic Guide Status 00:41:35 <sparks> Okay, so last week the big discussion was on the Transifex update 00:41:57 <sparks> Last I heard there were significant strides to get authentication working. 00:42:14 <sparks> Now I think they are waiting on data migration, maybe. 00:42:37 <sparks> The date of doom was added to the ticket, as well. 00:43:46 <sparks> As soon as it gets up and we get the thumbs up, I'd like for all guide leads to get your latest POTs uploaded so they can start being worked. 00:43:48 <stickster> sparks: Good idea to post a link to the ticket in the notes here 00:43:54 <sparks> yes 00:44:06 <stickster> #link https://fedorahosted.org/fedora-infrastructure/ticket/1455 00:44:36 <sparks> stickster: Thanks, you beat me to it. 00:45:11 <sparks> Anyone have any needs for their guide? 00:45:58 <sparks> Starting next week I'll start asking for status reports on each guide so we can make sure of what we'll have for F13. 00:46:29 <stickster> sparks: Is there a list somewhere of who's responsible for each guide? 00:46:35 * stickster is woefully out of touch there, sorry 00:46:41 <sparks> Yes... 00:46:52 <sparks> On the agenda page... scroll down to Guides 00:46:52 <laubersm> #link http://fedoraproject.org/wiki/Docs_Project_meetings 00:47:03 <laubersm> at the bottom 00:47:15 <sparks> #undo 00:47:15 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0x2b599dab73d0> 00:47:23 <sparks> #link https://fedoraproject.org/wiki/Docs_Project_meetings#Guides 00:47:27 <stickster> heh 00:47:29 <stickster> Okey doke 00:47:38 <sparks> It's woefully out of date. 00:47:39 <laubersm> see if I help again. 00:47:41 <laubersm> :) 00:47:56 <sparks> laubersm: Just taking your great link and putting a shine on it. 00:48:29 * laubersm was just using what was already in buffer from searching for the list before stickster even asked... 00:48:35 <sparks> ya 00:48:43 <sparks> So that Guide table needs to be updated... 00:48:58 <sparks> #action sparks to request guide leads update the table before next week 00:49:46 <sparks> radsy: Is rudi in the office? 00:50:51 <radsy> sparks, yup 00:51:24 <sparks> radsy: Can you ask him what the status is of the non-guide translations items in that table, please? 00:51:34 <sparks> radsy: Or just bonk him on the head and ask him to join us? 00:52:52 <sparks> Okay, anyone have anything else on this topic? 00:53:18 <radsy> asking, he couldn't talk even when identifying a new nick 00:53:24 <sparks> Hmmm 00:53:29 <radsy> irc client gremlins maybe 00:53:35 <sparks> maybe 00:53:48 <sparks> we should try to work on that in #fedora-docs post meeting 00:55:07 <sparks> Okay, moving on to stickster's topic. 00:55:21 <sparks> #topic Making docs.fp.o accessible for non-JavaScript equipped browsers 00:55:40 <sparks> #info To see the problem, install w3m or links, and use it to visit http://docs.fedoraproject.org -- try to select an existing guide 00:55:51 <radsy> sparks, "Awesome response from L10N for the DocBook stuff; I'm committing upstream but don't know how long it will take to trickle back down; probably not in time for F13" 00:56:02 <sparks> radsy: Thanks 00:56:16 <sparks> stickster: Would you like to introduce this? 00:56:36 <stickster> #info rudi reports Good response from L10n for DocBook stuff... committing upstream but might not make it down in time for F13 00:56:39 <stickster> sparks: Sure. 00:56:50 <radsy> "I need to approach some translators to fix some slight changes we made to the Common Content in Publican 1; but all RH-sponsored lanaguages (plus a few others) are in good shape" 00:56:52 * stickster points to zodbot, make him work for us! :-) 00:56:53 <radsy> sorry 00:57:30 * stickster waits to see if sparks is #info'ing that last bit too 00:57:55 <sparks> Ok 00:58:07 <sparks> #info I need to approach some translators to fix some slight changes we made to the Common Content in Publican 1; 00:58:10 <sparks> but all RH-sponsored lanaguages (plus a few others) are in good shape 00:58:12 <laubersm> sparks, looks like most guide leads need to branch for F13 too... sometime soon so work can start 00:58:16 <sparks> #undo 00:58:16 <zodbot> Removing item from minutes: <MeetBot.items.Info object at 0x2b599cfa9450> 00:58:31 <sparks> #info I need to approach some translators to fix some slight changes we made to the Common Content in Publican 1; but all RH-sponsored languages (plus a few others) are in good shape 00:58:49 <sparks> laubersm: Yeah... that didn't work like I wanted it too. 00:59:05 <sparks> laubersm: The day after F12 was released there should have been a F13 branch. :( 00:59:39 <stickster> sparks: mm... that depends, branching methods differ. 00:59:52 <laubersm> history looks like there is F11 and F10 and master... so master should go to F12 and master becomes the next (rawhide like) 01:00:03 <laubersm> at least in the few that I work on. 01:00:07 <stickster> Many would say you hold on to a "development" or moving branch until you *know* that you need to work on both a specific "next" version and stuff that won't make it to the next version. 01:00:22 <stickster> laubersm: Right 01:00:22 <sparks> well... branching == working on F13 guide and leaving F12 alone, short of bugs, etc. 01:00:35 <sparks> yeah 01:00:42 <stickster> yup, but then "master" or "devel" or whatever would be F13 until such time as we needed to work on F14 01:00:46 <sparks> yes 01:00:48 <stickster> Which might happen before F13, or it might not 01:01:14 <stickster> It's kind of up to a community to figure that out, document it, and then do it regularly. 01:01:31 * stickster realizes we're way into a new topic here though. 01:01:40 <stickster> Would be good to do this on the list instead of using meeting time :-) 01:01:47 * stickster has a hard stop in 5 min. 01:02:02 <stickster> sparks: Should I give a quick intro to this topic? 01:02:03 <sparks> yes 01:02:23 <stickster> laubersm: Can you bring up the branching topic so we can make a decision and record it 01:02:24 * jjmcd wonders how much effort to put in before we understand what zikula will do to us 01:02:24 <stickster> ? 01:02:38 <laubersm> yes 01:02:45 <sparks> jjmcd: I agree. 01:03:01 <stickster> #action laubersm Bring branching topic to docs list to decide how we want to do this going forward, and record it for posterity. 01:03:07 <stickster> Thanks laubersm! 01:03:13 <stickster> jjmcd: That depends, the only plan we had talked about to a great extent was publishing RPMs and HTML on Zikula. 01:03:13 <stickster> jjmcd: Unless you guys are planning abandoning source code repos, branching matters. 01:03:13 <stickster> (which you might be doing, I'm not assuming anything) 01:03:13 <jjmcd> Oh, I was back to the javascript topic, sorry 01:03:13 <stickster> Ah 01:03:13 <stickster> Well, still worthwhile since there's no Zikula ETA 01:03:13 <jjmcd> RNs is a different branching prob than guides anyway 01:03:13 * stickster gets back on topic 01:03:13 <stickster> sparks: jjmcd: Who created the current HTML indeces? 01:03:13 <jjmcd> rudi 01:03:20 <jjmcd> If I recall, I had a cockamamy scheme but rudi beat me to the punch with a prettier scheme 01:03:23 <stickster> OK, so really we just need to see if rudi can put a graceful fallback in that allows people to use a HTML form submit if no JS is available. 01:03:53 <stickster> I think most people have browsers that handle JS. But unfortunately, most of them aren't a11y (accessibility) challenged 01:04:03 <stickster> s/them/those people/ 01:05:01 <stickster> So I suggest that I just bring this to the list to see if this is a fix that is relatively minor, and if so, if rudi can do it, and if not, we can file a websites ticket to get help from someone who knows what they're doing. 01:05:20 <stickster> +/-1? 01:05:32 <sparks> +1 01:05:57 <jjmcd> I'm pretty sure it will be a useability delta, but I think codewise easy 01:06:22 <stickster> jjmcd: If it's a proper fallback, it shouldn't make any difference to people who have JS browsers. 01:06:35 <stickster> You make your dropdown selection, and things will just happen as they do now. 01:06:53 <stickster> If you happen to be sans JS, you hit the button afterward, and then everything works 01:07:13 <jjmcd> Yeah, I think I can see how that would work 01:07:15 * stickster is specifically referring to adding a "GO" button or some such. 01:07:22 <jjmcd> Yep 01:07:39 <jjmcd> So each dropdown needs a noscript block 01:07:41 <stickster> So I think it's essentially no delta for people other than those for whom the delta is positive :-) 01:08:03 * stickster takes the action item 01:08:05 <stickster> #action stickster Ask rudi through list to provide non-JS fallback (HTML form submit or something else). If he can't do it, file ticket with websites to ask for help. 01:09:01 * sparks is getting close to a hard stop 01:09:48 * stickster is there 01:09:52 <sparks> Okay, anything else on this topic? 01:10:18 <stickster> Nothing here 01:10:53 <sparks> Okay 01:11:00 <sparks> #topic All other business 01:11:15 <sparks> #action sparks to setup a bug busting weekend 01:12:04 <sparks> Anyone have anything? 01:12:43 <stickster> sparks: Are you going to send some email about that this week? 01:13:04 <sparks> I hope to 01:13:11 * sparks needs to get his head on straight 01:14:24 * stickster jets, g'night all 01:14:35 <sparks> Well... thanks everyone for coming tonight. 01:14:45 <sparks> Let's do this again next week! 01:14:50 <sparks> #endmeeting - -- - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLhc4UAAoJEDbiLlqcYamxdy4P/3zzPoyFBvLrNZoYzhV1VbsR XyqpCRoEhRtZlvRbuY7GHe20j0YawLCe2nT06YchDvlqsQQU1M2gitHkDmfTy+XX Yy0v6nGu/jmfQoZls686380iO4bzSTCzcMbl07FSzKXugdfi5kKUPCjQx5rXdn/Y OdBl6WxGmRKdGq8HsEc38y2KO7AIs/DcM7PCVw6r/hGWy/tHv9OSwWDZFHoeH3bg Z6wf7+WwCG1OtuJrP3u2YG5LFmjhkA5ttan+sFkGxxXECKLLJqU7qhjbtRLz/IkV Ock/WuTB9gdqh9O6iUR0K0lvW5j06f3slU3HGdVRKf/NX0rJEhFNLzAzOJrnG64i dwuIPK1cpKWwT1lqknlPsU4v9ksxrYToXFcA3rDYLX2wnTHKb/b5mkwkCrvQsDAU x54Ou2kaFDISaUzfeZil0aGvOsTAF+MJBwjaaHuSe7Ft3ceniY0npArl9D/ke3D7 jKOrCimcxlY5VDTrldRi/iYGBMcmlM4SK4PohcSVn3ebBqYZ5psEwRIgnh/4YlI1 qx0gNaifMKGUYJBL73siibs0Qwo0GkRIUZMUf5KU2eOn2643PKYkRkhRlF6XxRyE /yBPARPMxZPgUZUygeKvDNO4OieHaWWu0RvMFY9fmg1dt9iChhyLywPF7AgJ8G8e hjM6kx2C/eZh8Jntv9w5 =iEXh -----END PGP SIGNATURE-----

1 0

Upcoming Schedule Tasks
by John Poelstra 23 Feb '10

23 Feb '10

Start End Name Wed 18-Nov Tue 04-May Create POT files for All Guides Tue 23-Feb Tue 23-Feb Start Alpha Beat and Feature Page Review Tue 23-Feb Thu 25-Feb Comb Beats and Feature Pages for Alpha Thu 25-Feb Thu 25-Feb Alpha Project Wide Release Readiness Meeting Thu 25-Feb Fri 26-Feb Prepare Alpha Release Notes (1 page) Thu 25-Feb Mon 01-Mar Create Alpha Announcement (Marketing & Docs) Mon 01-Mar Mon 01-Mar Post Alpha Release Notes One-Page Tue 02-Mar Tue 02-Mar Alpha Public Availability Tue 02-Mar Wed 10-Mar Write Unclaimed Wiki Beats

1 0

Wiki:Package_update_HOWTO
by Shivam 22 Feb '10

22 Feb '10

On Sun Feb 21 20:02:50 UTC 2010, Luigi wrote : > Hi Paul and Shivam, > i've updated the developer tabel. I need feedback, if it's OK, enough intuitive, > or others (is better color or text (X) in the cross-section ?). > > If it's good I could end here and we see another time ... > > The intersections are controlled: OK. > > Luigi > > Hi Luigi I personally like the new table a LOT better compared to the last one. Though I wonder if Paul agrees. Maybe we can also try having the color AND the 'X' in the table. In the meantime, I'll try to improve the text in the 'Testers' table. -- Shivam 0F1CFA75 pub 1024D/0F1CFA75 2010-02-18 Key fingerprint = A381 A782 D746 8C4A B5CE 4079 71D5 B520 0F1C FA75 uid finkler <finkler(a)fastmail.fm> -- http://www.fastmail.fm - A no graphics, no pop-ups email service

1 0

Wiki:Package_update_HOWTO
by Luigi Votta 21 Feb '10

21 Feb '10

Hi Paul and Shivam, i've updated the developer tabel. I need feedback, if it's OK, enough intuitive, or others (is better color or text (X) in the cross-section ?). If it's good I could end here and we see another time ... The intersections are controlled: OK. Luigi

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs February 2010