docs July 2009

docs@lists.fedoraproject.org

46 participants
85 discussions

Removing inactive members from the Docs FAS Group
by Eric Christensen 25 Jul '09

25 Jul '09

The following members of the Docs FAS Group are showing as inactive in FAS. Is there any reason to NOT remove these users from the Docs group? zachfedora sopwith mumumu mcgiwer dpniner mattb csellers clennert mjbrej ddeutsch sfolkwil manix rmoreira splinux acapur rue cepxat drpixel gawain mbrennan naga bbcradio andrew kburtsev fcrhuser dtypald vmlinz jmtaylor denity kwade angelven mcisback rbianchi xiaoshao laong sfaure eitch ghenry anukul vglafirov shivakant jjesse Thanks, Eric

6 8

Allowed Content
by Ricky Zhou 25 Jul '09

25 Jul '09

Hey, I mentioned a few recent fedora-docs-list threads at the last IRC support operators[1], and they were generally very positive about some of the howto/knowledge base ideas that have been brought up. One concern that they brought up was whether we have a policy on what content can/cannot be on Fedora's wiki (or "official" Fedora docs), something more specific than http://fedoraproject.org/wiki/ForbiddenItems. One example that was brought up is that we currently have a howto for installing flash at http://fedoraproject.org/wiki/Flash, so there may be some current confusion about this. I will keep in touch with the IRC support operators team and see what allowed vs. not allowed topics are FAQs for them. Thanks, Ricky [1] http://meetbot.fedoraproject.org/fedora-meeting/2009-07-23/fedora-meeting.2…

5 4

Re: Removing inactive members from the Docs FAS Group
by Robert 'Bob' Jensen 25 Jul '09

25 Jul '09

----- "Eric Christensen" <eric(a)christensenplace.us> wrote: > > They can come back at any time. No one on the list is anyone that > has > been active in the Docs Project in some time (that I'm aware of). > > I think that when the account goes inactive then their password is > expired and they wouldn't be able to edit the wiki or access anything > else that is FAS related until they do a password reset. > I hope you exercise due diligence in this matter. You already have screwed up along these lines in the past. You lost at least one contributor that time, I don't think losing more is a good idea. There seems to be a lot of this going on, removing people from groups. Is there a good reason for it? So what if someone is "inactive" maybe they could want to contribute something tomorrow or next month. Why should they have to do anything in order to do what they have been able to do before. Why is having inactive accounts such a big deal? If I was counting numbers I would rather be able to count "125 contributors, 12 are inactive" than "113 contributors" when we all know that a large part of that 113 have not done anything in docs in a long time if ever, they just happened to re-set their password. -- Bob ------------------------------------------------------------------------ | Robert 'Bob' Jensen || Fedora Unity Founder | | bob(a)fedoraunity.org || http://fedoraunity.org/ | | http://bjensen.fedorapeople.org/ | | http://blogs.fedoraunity.org/bobjensen | ------------------------------------------------------------------------

3 4

Release Notes for Fedora 12
by John J. McDonough 25 Jul '09

25 Jul '09

The Release Notes Beat page at: https://fedoraproject.org/wiki/Documentation_Beats has been updated to reflect Fedora 12. IF YOU WERE A FEDORA 11 BEAT WRITER Review the page, if you intend to write the same beat for Fedora 12 that you wrote for Fedora 11, remove the asterisk from your name. If you would like to contribute to an additional beat, add your name to that beat. IF YOU ARE A DEVELOPER Check the Developer PoC column for your name. If you are on the list, and will still be the point of contact for Fedora 12, remove the asterisk from your name. If you are not on the list, and would like to ensure that the area you are working in gets proper attention in the release notes, add your name. Multiple names are fine. Perhaps you felt that your particular area didn't get the attention it deserved in Fedora 11. Consider writing the beat yourself. Add your name to the Writer column. IF YOU WOULD LIKE TO CONTRIBUTE TO THE RELEASE NOTES Look through the beats for an area that interests you, and add your name to the Writer column. If there is already someone there, that is fine. Two (or more) heads are better than one. IF YOU ARE UNCERTAIN Feel free to contact me by email, via the fedora-docs-list, or on the #Fedora-Docs IRC channel. You don't need to be some sort of expert to contribute to the release notes. All it takes is an interest, and the ability to string a few words together into a coherent sentence. Even if you don't feel like you are a writer, that is fine; there will be plenty of editing and review opportunities. What we really need is for folks to capture the changes. --McD

1 0

REMINDER: Release Notes Meeting
by Eric Christensen 23 Jul '09

23 Jul '09

We'll have a Release Notes meeting at 1500UTC today. We'll meet in #fedora-meeting. The purpose of this meeting is to discuss the F12 Release Notes and discuss any changes from F11. Eric

2 1

Release Notes Meeting 2009-07-23 IRC log
by Eric Christensen 23 Jul '09

23 Jul '09

15:02:17 <Sparks> #startmeeting Release Notes Meeting 15:02:22 <Sparks> Who is here? 15:02:23 * Sparks 15:02:25 * zoglesby is here 15:02:27 * rudi is here 15:02:42 * bcotton is here 15:02:57 * jjmcd is taking a break from spending the state's money 15:03:23 * laubersm found you 15:04:54 <Sparks> Okay... I'd like to discuss the following: 15:05:08 * laubersm goes to refill coffe mug before settling in for this hour of fun 15:05:29 <Sparks> 1. How to improve on the F12 RNs 15:05:43 <Sparks> 2. What products need to be generated. 15:05:55 <Sparks> 3. Using Publican for the RNs 15:06:30 <Sparks> 4. Training people to write beats. 15:06:44 <Sparks> laubersm: Hour? We've got this channel all day. 15:07:08 <Sparks> Anything else we need to discuss? 15:07:14 * zoglesby get coffe IV 15:07:38 * laubersm found only dregs and was too lazy to make more - but returned to this fun anyways 15:08:02 <jjmcd> Probably we should discudd who the audience is before attempting to answer those questions 15:08:10 <Sparks> jjmcd: yes 15:08:12 <jjmcd> sheesh the typing 15:08:58 <Sparks> anything else? 15:09:17 <rudi> Packaging 15:09:32 <rudi> As in, when and what 15:09:34 <jjmcd> Influenced by 2 of course 15:09:40 <rudi> Yeah 15:10:29 <Sparks> Okay, let's get started... 15:10:41 <Sparks> #topic Audience 15:10:48 <jjmcd> I see 3 15:10:57 <jjmcd> People who just installed and want to know what's new 15:11:06 <jjmcd> People preparing to install 15:11:12 <jjmcd> People looking for a new feature or fixed bug 15:11:24 <Sparks> Wouldn't the second one be the IG? 15:11:35 <jjmcd> Not necessarily 15:11:51 <jjmcd> For example, database changes almost always require you to do something before install 15:11:52 <Sparks> errr... shouldn't it be included in the IG 15:11:57 <jjmcd> those won't be in the IG 15:12:00 <Sparks> True 15:12:11 <Sparks> So more of an upgrade guide 15:12:29 <zoglesby> I think there is one more 15:12:33 <jjmcd> Yeah, almost anything that needs a backup or something before upgrade needs to be captured 15:12:54 <zoglesby> People that hear about Fedora and are trying to see what it has to offer 15:13:17 <zoglesby> I often look at release notes when I hear about a new distro 15:13:33 <jjmcd> Yeah, probably looking for more detail than the announcement 15:13:37 <Sparks> Okay, so I see this as: 15:14:00 <Sparks> The BIG RNs goes to the third group. 15:14:10 <Sparks> A "Welcome to Fedora ##" for the last 15:14:44 <Sparks> The "pretty" RN (from Marketing) for the first 15:14:47 <jjmcd> I think welcome can also address the first group in an introductory way 15:14:51 <Sparks> yes 15:15:14 <jjmcd> good point. Perhaps marketing should do the welcome to fedora xx 15:15:29 <Sparks> definitely 15:17:13 <Sparks> So we are already working on the "pretty" version with Marketing. 15:17:34 <Sparks> And we currently have the BIG RNs 15:17:35 <laubersm> I generally find most "users" - new or upgrading - think of wiki and IG and UG as resources more than the RN - they tend to think Release Notes are for the geeks 15:17:46 <Sparks> So we need to figure out the Upgrade guide 15:17:49 <laubersm> The RN can include links to those general resources - and should 15:18:01 <laubersm> UG = users guide 15:18:03 <Sparks> agreed 15:18:24 <laubersm> do we really need a separate upgrade guide? can't it be in the IG? 15:18:27 <jjmcd> So the beat writers will need to be upgrade writers too, or at least help guide the upgrade writers 15:18:51 <jjmcd> laubersm, I doubt if the experienced user will look at the install guide 15:18:53 <Sparks> Well, I think the IG should have information on upgrading 15:19:15 <rudi> FWIW, the IG already details several different upgrade paths 15:19:47 <laubersm> jjmcd, I was thinking more of the reminders of good general practices - RN would still be for the "this time it is bar than needs to be reconfigured instead of foo" 15:19:58 <jjmcd> But does it include things like "save your qle database to sql before upgrading and reimport after the upgrade"? 15:20:25 <jjmcd> Yes, I don't see the upgrade guide as including all the version specific details 15:20:32 <rudi> jjmcd -- no; and I think that's probably out of scope 15:20:33 <laubersm> jjmcd, if that is an everytime you upgrade the db than it should be in a general guide and not repeated with every RN 15:21:09 <Sparks> So beat writers talk about new stuff and also issues to upgrading 15:21:27 <jjmcd> Yes, but most of the time you don't need to, seems like every third or fourth time with MYSQL, Postgres, and some others there are special things to do 15:21:39 <jjmcd> But I agree, if its every time, then the upgrade guide 15:22:27 <jjmcd> I see beat writers as listing all changes, but providing prose for "important" changes and upgrade issues 15:23:15 <jjmcd> That way the change that you care about, but I don't see as important, is at least noted 15:23:48 <laubersm> remind me - who makes up the beat writers? some are docs team members but aren't some from other teams that just help with RN? 15:24:08 <jjmcd> Mostly docs team members but not always 15:24:25 <jjmcd> We generally seem to do better with team members 15:24:43 <laubersm> I ask because maybe docs members - or people more familiar with the many guides - should be reviewing to make sure RN stays trim and important stuff gets rediurected to the guides 15:24:57 <laubersm> it seems to me that we just haven't had time for that in the past - 15:25:02 <laubersm> even though the intent has been good 15:25:24 * laubersm prefers reviewing to writing by the way 15:25:25 <jjmcd> I'm hoping to have more lists and less prose this time around 15:25:35 <jjmcd> Should give us more opportunity to review 15:26:21 <jjmcd> And less work for translators 15:26:37 <laubersm> and will the review period be as free form as last time or will it be a bullet on the docs team schedule (or in a wiki chart)? 15:27:09 <jjmcd> I hope to take poelcat's schedule and add in some docs and l10n bullets 15:27:19 <laubersm> cool. 15:27:35 <jjmcd> We never got the l10n notifications in there and we need that 15:27:40 <Sparks> Yeah, I think we need to make sure we get these beats done well ahead of time 15:28:44 <laubersm> I think if beat writers trade reviewing it will help the overall flow of all the RNs as well - and catch more duplication (or need for general docs tips) 15:28:57 <Sparks> Okay... I don't want to drag this meeting out... :) 15:29:00 <Sparks> laubersm: I agree. 15:29:14 <Sparks> So can we say that three "RNs" will make this work? 15:29:30 <jjmcd> Most of that has to do with communications with other teams. Looking at the F11 beats, the only writer who wasn't a docs member at all was Chitlesh, although Jens I think is in the group, but not at the meetings etc 15:29:42 <jjmcd> what three? 15:29:54 <Sparks> 1) Big RNs 15:29:56 <zoglesby> I think we had so much duplicate stuff last time cause on the last day 3 of of were writing all the stuf that didnt get done 15:29:59 <laubersm> How are we naming these so they catch the correct audience? 15:30:00 <Sparks> 2) "Pretty RN" 15:30:08 <Sparks> 3) Upgrade "Guide" 15:30:23 <jjmcd> You don't see the "pretty RN" as chapter one of big rn? 15:30:44 <Sparks> The "Pretty RN" will be very graphical 15:30:50 <jjmcd> ahhh good 15:30:52 <Sparks> kind of like a "newsletter" 15:30:59 <Sparks> a flyer 15:31:11 <jjmcd> sounds like a bitch to translate 15:31:31 <jjmcd> but we did it with IG if I recall 15:31:46 <rudi> Not as long as people are careful to keep text out of the graphics 15:31:58 <rudi> And rely on captions, or callouts 15:32:18 <rudi> And yeah, the IG has about 70 images in each of about 35 localisations 15:32:35 <Sparks> So are we good with those three? 15:32:47 <jjmcd> question fro rudi 15:33:03 <jjmcd> did you do those with dot or something so that you could translate easily? 15:33:26 <rudi> Yeah, where needed. 15:33:41 <jjmcd> cool 15:33:57 <jjmcd> I like it Sparks 15:34:26 <Sparks> #idea Three "RN" guides: big RN, "pretty" RN, and Upgrade Guide 15:34:30 <rudi> jjmcd -- http://docs.fedoraproject.org/install-guide/f11/en-US/html/s1-guimode-texti… 15:35:31 <Sparks> Okay to move on? 15:35:33 <rudi> Do we have any specific plan to keep down the bigness of the big RN? 15:35:45 <jjmcd> tables 15:36:29 <rudi> Hmmm -- tables might get L10N hating us for whole new reasons :) 15:36:36 <zoglesby> I think that one of the big issues for 11 was the amount of info trans had to deal with if we add 2 more we need to cut some down 15:36:39 <jjmcd> Nothing in the tables to translate 15:36:47 <rudi> Oh OK. 15:37:05 <rudi> Just that elements in lists and tables are very challenging 15:37:09 <jjmcd> Jus package name, old version, new version link 15:37:29 <jjmcd> Specifically intended to not need translation 15:37:38 <zoglesby> lol 15:37:57 <rudi> Without any description of what actually changed? 15:37:59 <zoglesby> I think we can automate that to, 15:38:14 <jjmcd> zoglesby, a lot of the prose was just fluff. Already automated ;-) 15:38:27 <jjmcd> rudi, only "important" changes 15:38:33 <rudi> OK 15:38:49 <jjmcd> https://fedoraproject.org/wiki/User:Jjmcd/Drafts/Fedora_12_tables 15:39:06 <jjmcd> Not organized by beats, and needs a lot of editing 15:39:35 <rudi> sure, but yeah, I get the picture now 15:39:46 <zoglesby> why do we have meetings again? Why not force jjmcd to 6S everything for us 15:40:24 <Sparks> +1 15:40:34 <jjmcd> We still need ppl who can reed and spel gud 15:40:40 <laubersm> zodbot, because last time he built and rpm and left town and it had to be redone before he returned 15:40:53 <laubersm> arg... that was for zoglesby 15:40:55 <zoglesby> this is more of a fedora change log then release notes 15:41:09 * laubersm relies on tab complete too much without looking 15:41:40 <jjmcd> Well, we do need the change log. In my view, we still need prose for "important" changes, but this way someone looking for a feature or bugfix can see if it is there 15:41:47 <zoglesby> laubersm: ah yes that was a good day 15:42:09 <jjmcd> ANd that list is long because it is against rawhide. As we close in on release it will get shorter 15:42:17 <rudi> zoglesby; true to some extent, but then, there was a lot of stuff in previous RNs that was basically "Package X has been upgraded from version 1.7 to 1.9" 15:42:19 <zoglesby> jjmcd: very true, it takes care of one group 15:42:34 <jjmcd> Yes, and the prose takes care of the others 15:42:49 <zoglesby> ok 15:42:58 <jjmcd> rudi, and that prose only provided useless work for translators 15:43:06 <rudi> Yep. 15:43:12 <Sparks> jjmcd: Are you reviewig bug reports for stuff to go into the RN? 15:43:22 <jjmcd> Yes, hit a bunch last week 15:43:33 <laubersm> How about a para on how to use a tool to find that list and not include it at all :) 15:43:51 <jjmcd> One "content" bug I still needs more research 15:44:00 * laubersm thinks such lists reinvent the wheel and will always miss something 15:44:19 <jjmcd> And the remaining RN bugs either need a lot of work or need to wait for something else 15:44:21 <zoglesby> put a link to the fedora community site 15:44:29 <jjmcd> laubersm, probably not a bad idea 15:45:02 <Sparks> jjmcd: Are people actually flagging items to be included in the RNs? 15:45:02 <zoglesby> but there went your 0 trans :P 15:45:13 <jjmcd> Sparks, generally no 15:45:25 <Sparks> jjmcd: Maybe we should encourage that and then query that. 15:45:40 <jjmcd> I wonder how good an idea that is actually 15:45:56 <jjmcd> For the person working on a package, any change is "important" 15:46:47 <jjmcd> Although when you have someone like Chitlesh or Jens who sees the bigger picture, it is great when they can work on the prose 15:46:57 <laubersm> jjmcd, will the list at least be at the end - ie "other updates include:" so I don't have to scroll through it to get to the prose? 15:47:12 <jjmcd> yes, that was my view - but by beat 15:47:22 <jjmcd> So you get the database prose, then the list 15:47:33 <laubersm> ok 15:47:57 <jjmcd> Problem is, the yum groups are all screwed up, so organizing the list by beat is going to be a bit of a job 15:48:12 <jjmcd> That drafts page is by yum group 15:50:42 <jjmcd> But as you said, perhaps we make a page that gets updated nightly for the list, or make the tool easy enough for people to use 15:51:11 <jjmcd> That way you can see what changed from F11 to NOW rather than to the initial release of 12 15:51:46 <zoglesby> +1 15:52:54 <jjmcd> is there a php interface to sqlite? 15:53:10 * Sparks notes nine minutes left 15:53:45 <jjmcd> Still have most agenda items left 15:53:51 <Sparks> Yes 15:54:08 <jjmcd> yes sqlite or yes agenda? 15:54:13 <Sparks> yes agenda 15:55:08 <jjmcd> What is the issue with Publican? I thought we had that answered. 15:55:19 <Sparks> Well... If you can do what you need to do then I'm fine. 15:55:36 <Sparks> I can't get the SRPMs to generate in koji. They fail 15:55:37 * jjmcd has no issue with Publican 15:55:55 <rudi> The Beta for Publican 1.0 should be announced soon now 15:56:27 <jjmcd> I've been manually building the SRPM, if Publican can do it right, great, but making the RPM isn't a biggie 15:57:10 <rudi> I can't help with the SRPMs, but until 1.0 appears, we now have hackish fixes to most of the glitches in 0.44 up on the wiki 15:57:13 <Sparks> Well, hopefully the "new" version of Publican will fix the problems. 15:57:38 <jjmcd> If we still include N docs in the RN RPM it doesn't matter anyway 15:57:49 <zoglesby> rudi: the fedora wiki or publican wiki? 15:57:55 <rudi> Fedora wiki 15:58:15 <laubersm> Even if there are glitches with the building the SRPM, I have no issues with publican - all items should be created with publican 15:58:24 <rudi> https://fedoraproject.org/wiki/Publican#Publican_on_Fedora_Tips_and_Tweaks 15:58:25 * laubersm did not like the old toolchain adventure 15:58:41 * jjmcd agrees with laubersm 15:59:15 <jjmcd> I'm afraid we need at least another meeting to answer the "what products" question though 15:59:29 <Sparks> jjmcd: That's cool. Is this time good with everyone? 15:59:46 * Sparks notes that it is awfully late/early for rudi 15:59:48 * rudi isn't crazy about it, but will turn up with enough warning :) 15:59:58 <jjmcd> This time on Thursday is suboptimal but doable 16:00:05 <rudi> 2AM here in the middle of an Australian winter 16:00:18 <zoglesby> rudi: thats me every docs meeting! 16:00:44 <zoglesby> well not the winter part 16:00:49 <rudi> :D 16:01:00 * jjmcd will probably be out of town the next few Wednesdays, tho, so Thursday is better than Wednesday 16:01:03 <zoglesby> and I only wish I was in Australian 16:01:34 <laubersm> I will have a harder time next week - afternoon would be better when students are more likely to be doing labs instead of listening to me talk.... 16:01:38 <zoglesby> Sparks: any time is good with me, if I have to I will use my phone and not talk so much 16:02:00 * laubersm is EDT when refering to afternoon 16:02:14 * Sparks is EDT, too 16:02:46 <jjmcd> If you move to 2000Z you are starting to get into a semi-sensible morning time for rudi 16:03:17 * Sparks notes 2000z is drive time for us in EDT 16:03:38 <rudi> Don't worry about me; I'm happy to work around you guys 16:03:52 <Sparks> rudi: Time and a half at 1A? 16:04:06 <rudi> I wish! :) 16:04:08 <zoglesby> lol 16:04:17 <Sparks> I miss shift-differential 16:04:49 <jjmcd> Not me ... back when I got it, I was making $1.82 an hour 16:05:17 <Sparks> Okay, anything else we need to discuss today? 16:05:19 <zoglesby> I missing getting paid for the amount of time I work not working 80 hour weeks and getting the same as everyone else working 40 16:06:21 <rudi> Not discuss, but a thought to leave with people that we should perhaps try to get a package into rawhide rooner rather than later 16:06:41 <Sparks> I agree 16:06:41 <zoglesby> indeed 16:07:00 <laubersm> +1 16:07:14 <rudi> ECS will be able to help out with some of the heavy lifting content-wise, but not so much with the packaging 16:07:40 <rudi> (and hopefully there will be less heavy lifting this time round anyway) 16:08:04 <Sparks> Okay, anything else? 16:08:40 <Sparks> Okay, while we didn't get through everything we did have a good discussion. 16:08:44 <Sparks> Good ideas 16:10:04 <Sparks> Okay, thanks for coming! 16:10:07 <Sparks> #endmeeting

1 0

Looking for pointers wrt metrics for LISA QA 3.1
by sandeep shedmake 23 Jul '09

23 Jul '09

Hi, I wondered unlike Quality Assurance/QA metrics which exists for Software Development projects, are there any QA metrics defined for Localization QA ? Thereby, I came across two such specifications namely --- SAE J2450 and LISA QA 3.1. Metrics for SAE J2450 model is available at http://www.apex-translations.com/documents/sae_j2450.pdf, but I couldn't locate any such document for LISA QA 3.1 model. Any pointers/point-of-contact wrt "metrics for LISA QA 3.1 model/specifications" would be helpful. Thanks, sandeeps

1 0

Self-Introduction:
by Robert Antoni Buj i Gelonch 23 Jul '09

23 Jul '09

# What other projects or writing have you worked on in the past? I have worked in Babelzilla, Officeshots, OpenSolaris, PC-BSD, Ubuntu & Wordpress extensions (Translation projects) # What level and type of computer skills do you have? I am Computer Science Engineer. # What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc. system administrator, programmer # What makes you an excellent match for the project? I think that I can do it. I would like to translate it to catalan language. # GPG KEYID and fingerprint pub 1024D/B4623A0F 2009-07-05 Key fingerprint = DB34 728A 5B78 ECB1 727B 38E0 253E 78B4 B462 3A0F -- ca: M'agradaria millorar el món, però Déu no em dóna el codi font! de: Ich würde gern die Welt verbessern, doch Gott gibt mir den Quellcode nicht! en: I would like to improve the world, but God not gives to me the source code! es: Me gustaría mejorar el mundo, pero Dios no me da el código fuente!

2 1

[Bug 430721] Additional Information Requested for Apache Setup
by Red Hat Bugzilla 22 Jul '09

22 Jul '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=430721 David Nalley <david(a)gnsa.us> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |david(a)gnsa.us AssignedTo|kwade(a)redhat.com |dhensley(a)redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

Docs Meeting 2009-07-23Summary
by Eric Christensen 22 Jul '09

22 Jul '09

======================================================================================================================================= #fedora-meeting: Docs Project - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings#Thursday_July_23.2C_20… ======================================================================================================================================= Meeting started by Sparks at 00:01:38 UTC. The `full logs`_ are available. .. _`full logs`: fedora-meeting.2009-07-23-00.01.log.html Meeting log ----------- * **Status on CMS (Zikula) <-- ke4qqq** (Sparks-00:06:35_) * *ACTION*: Sparks to follow up with the News people about Zikula (Sparks-00:21:20_) * *ACTION*: Sparks to meet with News people and solicit a list of their needs (Sparks-00:22:37_) * **Status on CC license rollout. <-- ianweller** (Sparks-00:23:01_) * *ACTION*: Sparks to write rollout plan for license change (Sparks-00:30:37_) * *ACTION*: ianweller to write press release (ianweller-00:30:59_) * *ACTION*: rudi to help sparks on changing the fedora-brand in Publican for CC license (Sparks-00:33:08_) * **Shared open-source style guide <--ke4qqq** (Sparks-00:35:17_) * *LINK*: https://www.redhat.com/archives/fedora-docs-list/2009-June/msg00163.html (Sparks-00:35:24_) * **Outstanding BZ Tickets** (Sparks-00:37:25_) * *LINK*: https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classificatio… (Sparks-00:37:36_) * **Guide needs?** (Sparks-00:43:14_) * *LINK*: https://fedoraproject.org/wiki/Docs_Project_meetings#Guides (Sparks-00:44:11_) * **New Guides** (Sparks-00:48:04_) * *ACTION*: Sparks to create BZ component for Installation Quick Start Guide (Sparks-00:52:10_) * *ACTION*: Sparks to create a BZ component for Virtualization Guide (Sparks-00:55:33_) * **All other business** (Sparks-01:04:10_) * *LINK*: https://fedoraproject.org/wiki/Classroom (nirik-01:04:44_) * *ACTION*: Sparks to send out reminder about the RN meeting (Sparks-01:19:22_) .. _Sparks-00:06:35: fedora-meeting.2009-07-23-00.01.log.html#l-13 .. _Sparks-00:21:20: fedora-meeting.2009-07-23-00.01.log.html#l-74 .. _Sparks-00:22:37: fedora-meeting.2009-07-23-00.01.log.html#l-80 .. _Sparks-00:23:01: fedora-meeting.2009-07-23-00.01.log.html#l-83 .. _Sparks-00:30:37: fedora-meeting.2009-07-23-00.01.log.html#l-133 .. _ianweller-00:30:59: fedora-meeting.2009-07-23-00.01.log.html#l-135 .. _Sparks-00:33:08: fedora-meeting.2009-07-23-00.01.log.html#l-148 .. _Sparks-00:35:17: fedora-meeting.2009-07-23-00.01.log.html#l-166 .. _Sparks-00:35:24: fedora-meeting.2009-07-23-00.01.log.html#l-167 .. _Sparks-00:37:25: fedora-meeting.2009-07-23-00.01.log.html#l-176 .. _Sparks-00:37:36: fedora-meeting.2009-07-23-00.01.log.html#l-177 .. _Sparks-00:43:14: fedora-meeting.2009-07-23-00.01.log.html#l-192 .. _Sparks-00:44:11: fedora-meeting.2009-07-23-00.01.log.html#l-198 .. _Sparks-00:48:04: fedora-meeting.2009-07-23-00.01.log.html#l-208 .. _Sparks-00:52:10: fedora-meeting.2009-07-23-00.01.log.html#l-226 .. _Sparks-00:55:33: fedora-meeting.2009-07-23-00.01.log.html#l-242 .. _Sparks-01:04:10: fedora-meeting.2009-07-23-00.01.log.html#l-287 .. _nirik-01:04:44: fedora-meeting.2009-07-23-00.01.log.html#l-290 .. _Sparks-01:19:22: fedora-meeting.2009-07-23-00.01.log.html#l-359 Meeting ended at 01:20:14 UTC. Action Items ------------ * Sparks to follow up with the News people about Zikula * Sparks to meet with News people and solicit a list of their needs * Sparks to write rollout plan for license change * ianweller to write press release * rudi to help sparks on changing the fedora-brand in Publican for CC license * Sparks to create BZ component for Installation Quick Start Guide * Sparks to create a BZ component for Virtualization Guide * Sparks to send out reminder about the RN meeting Action Items, by person ----------------------- * ianweller * ianweller to write press release * rudi * rudi to help sparks on changing the fedora-brand in Publican for CC license * Sparks * Sparks to follow up with the News people about Zikula * Sparks to meet with News people and solicit a list of their needs * Sparks to write rollout plan for license change * Sparks to create BZ component for Installation Quick Start Guide * Sparks to create a BZ component for Virtualization Guide * Sparks to send out reminder about the RN meeting * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * Sparks (145) * stickster (46) * ianweller (44) * rudi (43) * ke4qqq (24) * jjmcd (18) * perspectival (17) * nirik (10) * Tsagadai (5) * danielsmw (4) * mchua (3) * bcotton (2) * onekopaka_laptop (2) * laubersm (1) Generated by `MeetBot`_ .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

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 July 2009