FUDCon days 1&2 “The Beefy Miracle Part 2: Let’s Burn This Mama-jama to the Ground!”

Day 1:

The most important thing to note about Day 1 (the day the BarCamp happened) is I WON A RASPBERRY PI! So look forward to many blogposts, micro-messages, and the such where I am pissed because something I dont understand is not working the way I expect 🙂

Lunch was provided by Ivan Makfinsky’s company, Endosys, Inc. (thanks it was great).

I sat in two ARM talks. I’ve never really been interested in ARM but Jared talked about its importantace in the future. I also sat in adamw’s talk about running your own cloud, something that ARM can be very useful in.

FUDPub was a blast I was hanging out with Klaatu for a bit and then found Mario, a new Ambassador with a million crazy stories about his globe trotting, and drank far too much [that is Mario’s fault :)].

Then we were up waaaaaaaaaaaay to late causing hell for the kid who was employed as a security guard.

OH! and once again there was insanity involving a wedding party (this time it wasn’t drunken ladies “enjoying each others company”, but a gentleman that said “don’t judge me” after he said “she’s not my real sister” [gotta love the south]).

Day 2:

Day two was more hackfests. I became a moderator for ask.fedoraproject.org [which I suck at and need to get my ass some learnin’ about]. I gave some input in on Fedora Insight [which I am super stoked about now], and I got my Ambassador on.

Lunch was again an Endosys, Inc event (thanks again!!)

Speaking of Ambassadors nb, get a hold of me about ILF after you make it home and catch up on some sleep.

Then I had to bail to catch my flight (where I am writting this right now).

I would like to thank the following:

Daddy Shaddow Man
Ben Williams – the host of the event
Robyn Bergeron – who I owe emencely for sorting out my travel and room (because I’m obviously not adult enought to sort this out myself [still]), and dinner ($insert weiner joke here)
Ruth – That Hoodie is awesome!
Spot – for lunch and the funny motorcycle Jesus church story
Paul Frield – for the ride to VT
John Stanley – for getting a hold of Paul for me
Mario – for the booze and ride
Matt Domsch – for the ride to the airport
MarkDude – for sharing a room with me
Senecac Collage – for the Raspberry Pi
Douchie Mc Wantstobeacop – for the lulz
Klaatu – for listening to my long ass diatribe night0, and taking all the shit I heaped on him about sleeping on a plank 🙂

and Everyone else who make FUDCon super awesome.

Fedora Contributors are like the Wu-Tang Clan… nothin’ to f’ with.

FUDcon day -1

This is going to be a” from the dents” kinda deal so here we go!

Wayne County corrections officer was arrested yesterday after being accused of having sex with female inmates bit.ly/gj9HKf /via @pi_news

An early morning standoff today at a Richmond east-side motel ended without injuries http://bit.ly/dLPDww /via @pi_news

Wow its nice to get out of town for a while.

On my way to the airport… Already have a list of things I forgot 😦

And I have since lost some stuff (more to come)

Made it to airport. Dayton is way more lowkey than Indy. Didn’t have the #pornscanner on so I had no issues. Hope Denver is the same !fedora

W00t take that TSA!!!

Bored already any !fedorians in the dayton airport?

Yeah, I was there alone…

Update: The Wayne Co. corrections officer accused of sexual misconduct with female inmates was fired http://bit.ly/fyifSm /via @pi_news

I’d rather be bored than that guy

‘Egyptian Christians said they will guard the Muslims from the police while they on Friday Pray.’Amazing solidarity. #Egypt /via @osamak

This is the kinda news I like getting

Just saw Dave Chappelle in the Dayton Airport. No I didn’t bug him and no I don’t have any pics


On the plane… Next stop Denver.

I talked with a really cool dude about everything from computers, to dogs, to college, to the increasing stupidity of people.

Denver next stop Phoenix.

Plane was a bit late so my hour layover became a 30 minute layover

FFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUUUUUU- i lost the charging cable for my phone… maybe its in the room but i doubt it

Yeah that’s right… I’m pretty sure I’m fracked. Maybe there is a big box store around here or something…

And now for some hanging out…

Security incident on Fedora infrastructure on 23 Jan 2011 — Don’t Panic

Jared Smith sent this to the announce list and I am passing it to y’all un-edited

Summary: Fedora infrastructure intrusion but no impact on product integrity

On January 22, 2011 a Fedora contributor received an email from the Fedora
Accounts System indicating that his account details had been changed. He
contacted the Fedora Infrastructure Team indicating that he had received
the email, but had not made changes to his FAS account. The Infrastructure
Team immediately began investigating, and confirmed that the account had
indeed been compromised.

At this time, the Infrastructure Team has evidence that indicates the account
credentials were compromised externally, and that the Fedora Infrastructure was
not subject to any code vulnerability or exploit.

The account in question was not a member of any sysadmin or Release Engineering
groups. The following is a complete list of privileges on the account:
* SSH to fedorapeople.org (user permissions are very limited on this machine).
* Push access to packages in the Fedora SCM.
* Ability to perform builds and make updates to Fedora packages.

The Infrastructure Team took the following actions after being
notified of the issue:
1. Lock down access to the compromised account
2. Take filesystem snapshots of all systems the account had access to
(pkgs.fedoraproject.org, fedorapeople.org)
3. Audit SSH, FAS, Git, and Koji logs from the time of compromise to the
Here, we found that the attacker did:
* Change the account’s SSH key in FAS
* Login to fedorapeople.org
The attacker did not:
* Push any changes to the Fedora SCM or access pkgs.fedoraproject.org in
any way
* Generate a koji cert or perform any builds
* Push any package updates

Based on the results of our investigation so far, we do not believe that any
Fedora packages or other Fedora contributor accounts were affected by this

While the user in question had the ability to commit to Fedora SCM, the
Infrastructure Team does not believe that the compromised account was used to
do this, or cause any builds or updates in the Fedora build system. The
Infrastructure Team believes that Fedora users are in no way threatened by this
security breach and we have found no evidence that the compromise extended
beyond this single account.

As always, Fedora packagers are recommended to regularly review commits to
their packages and report any suspicious activity that they notice.

Fedora contributors are strongly encouraged to choose a strong FAS password.
Contributors should *NOT* use their FAS password on any other websites or
user accounts. If you receive an email from FAS notifying you of changes to
your account that you did not make, please contact the Fedora Infrastructure
team immediately via admin@fedoraproject.org.

We are still performing a more in-depth investigation and security audit and we
will post again if there are any material changes to our understanding.

Jared Smith
Fedora Project Leader

Update on life

RL has been crazy but:

* I’m pretty sure I passed 2 of my 3 classes (still waiting for final grades)
* I had 4 wisdom teeth and a molar removed (the molar was broken by the pressure of the wisdom teeth)
* I’m going to FUDcon NA (check sidebar)
* Started doing kung-fu 4 months or so, and its going epicly! (I missed testing for my white sash because of the teeth)
* planning on taking an MMA class starting in the new year (its just my kung-fu class with a bit more contact)
* I’m losing weight (due to the kung-fu)

How to be a successful contributor

Mike McGrath & co. drafted a nice doc titled “How to be a successful contributor” it should help set expectations of and for new contributors. I’ve pasted the first version I have seen but you should go to https://fedoraproject.org/wiki/How_to_be_a_successful_contributor to see newer versions…

How to be a successful contributor
From FedoraProject


* 1 Audience for this document
* 2 Things to know before you join
o 2.1 Time commitment
o 2.2 Get permission from work
* 3 Joining
o 3.1 Observation
o 3.2 Pick what you want to work on
* 4 Don’t jump into the deep end
o 4.1 First contact
o 4.2 Find a mentor or sponsor
* 5 Contributing
o 5.1 Look for work
o 5.2 Quitting

Audience for this document

This document is targeted at people interested in contributing to the Fedora Project. In the Fedora Project, students, professionals and hobbyists all come together to produce software, marketing materials, art, documentation, etc. We all started as new volunteers at some point. The items below are designed to help you through the process of joining a team. It helps you know what we expect of you and what you can expect of us.
Things to know before you join

Everyone who joins a free software project does so with the best intentions of staying. However, few stay to become regular contributors, and fewer still become leaders within the project. The biggest difference between those that stay and those that leave is commitment and time.
Time commitment

Some volunteers may spend 15-30 hours per week contributing, doing that while holding down a proper day job is a difficult time management skill. As a volunteer, you should ask yourself whether you can devote 2-4 hours per week, even though it’s less than an hour per day. 4 hours a week for most people is an entire afternoon one day. That’s a significant chunk of time.
Get permission from work

There is a mutually beneficial relationship between working for a living and volunteering. Many contributors will find their skill sets at work increase dramatically just by having access to and learning from another environment. This benefits employer and worker. It is completely worthwhile to sit down with an employer or manager and ask for permission to contribute during work hours, even if it’s only a couple of hours on a Friday afternoon. Explain the benefits to you and your employer.

If they say no, then you’ll have to volunteer in your own time.

The single biggest mistake most new contributors make is showing up “just wanting to contribute.” It’s important to take the time to observe the team (refer to the section below) and see how their work aligns with your own skills and personality. Know that getting work to do on day one is very rare, and those who are highly skilled in a specific technology will still have to take the time to get to know an environment before access is granted.

For example, if you’re a database expert it is very unlikely you’ll be given access to databases (where personal info, passwords, etc) are stored within your first several weeks of volunteering. If you’re looking to become an ambassador, it is unlikely you’ll get marketing materials shipped to you in your first week. This may seem unfortunate, but it’s necessary to keep the project members working well together. The same can be said about any major changes, like a complete redesign of a system or a new look and feel for a website. Don’t get discouraged. Show up as often as you can, and get to know the team.

It is important to get to know the organization and teams you are looking to work with before you try to join them. Learn what they do and how they do it, and try to get to know the people involved. It is extremely unlikely you will be able to actually contribute from day one. In organizations with hundreds or thousands of people working together, understanding how things work is critical.

Don’t be shy about asking questions and getting to know people. Plan to spend several days or even weeks attending meetings, emailing on mailing lists and hanging out on IRC before you get to do any actual work. Offer suggestions on topics being discussed, and share any experiences (good or bad) you’ve had that is relevant to the discussion.

Part of observing and making constructive suggestions may require withholding judgement. When making suggestions, don’t assume you come with all of the answers or that the Fedora Project is doing it all wrong. There is a good chance we can improve the way we are doing things, however most of our current practices were developed over long periods of time after lengthy discussion. Your criticism may be better received once you have established yourself in the community and are perceived as understanding our culture.
Pick what you want to work on

It’s your job to decide what you want to work on. Pick something that’s important to you and something you have passion for. You’ll see this advice repeated several times in this document: Don’t just show up looking to have work assigned to you. Get to know the teams and procedures they have in place. Ask questions and really get to know what you’re going to be working on _before_ trying to work on it.
Don’t jump into the deep end

When picking something to work on, don’t be the sole person to take on a huge task as your first contribution. Picking a task that’s too large signifcantly raises the chances of failure. Also don’t pick several things on several teams to work on. Start small, picking at most one or two things, and grow from there. The key is slow, steady, and sustainable growth. Don’t join with the immediate goal of becoming the next leader of the project. Start small.
First contact

After you’ve decided what you’re looking to do and what team you are looking to do it with, it’s time to send an introduction to the list. When sending an introduction (usually by mail list), include the following information:

* Name
* Time Zone / Country
* Basic skills and experiences
* Why you’re joining
* What you’re looking to do (be specific)
* How much time you can contribute (usually hours per week)

If any of the above questions are not clearly answered, don’t send the email yet. You’re not ready. Remember, be specific about what type of work you’re looking to do. Saying “Whatever needs to get done” isn’t helping anyone. Saying “I’d like to help document system A,” “I’d like to translate software for my native language,” or “I noticed this webapp is particularly slow sometimes and I’d like to help fix that” is perfect.
Find a mentor or sponsor

This step is both incredibly difficult and important. Finding a proper sponsor will increase your chances of being a successful contrubitor significantly. Sometimes it’s absolutely required. A sponsor will help with training, introductions and teaching new contributors how a team works.

Most teams have mailing lists. Email the list, say you’re looking for a sponsor, and explain what you are wanting to do. If you haven’t heard back in a few days, reply saying that you are still looking. Keep doing this. Most sponsors are people that have been in the project for a long time, and are often very busy.

They don’t mean to be rude and don’t want to send the impression they don’t want new contributors. It’s just that at the moment, some people will assume other people will take care of you and so for the moment, no one does. This is a common problem — in real life as well as in online communities — and a difficult one to fix. But sticking to it and continuing to ask for help without being annoying will show that you are serious and ready to contribute. Don’t send this kind of message more than once every couple of days, but be positive, and persistent if needed.

Once you’ve got something to work on, it’s time to actually do work. The first several tasks you will work on will likely be small or maybe mundane. Do them consistently, conscientiously and well. This will raise the level of trust you have from the other team members.

As with other volunteer organizations, there are high turnover rates in the free software universe. Training volunteers is time consuming, especially for more complex tasks, and requires a commitment from currently busy volunteers. Spending days or weeks training someone only for them to vanish can be disheartening for mentors and sponsors. By giving out small tasks that have been hanging around, a sponsor can help you take small but vital steps, and learn whether or not the work you’re going to be doing is really for you.
Look for work

If you have access to a repository, system, or content, consider yourself a partial owner. This doesn’t mean you should immediately re-design everything. Remember that other owners have time and effort invested in the current material as well. It does mean, though, that you should take pride in the work you are doing. If you see something not quite right, do research on it and notify the list. Seek work out, keep yourself busy and help others.

If volunteering isn’t for you, that’s OK. You don’t need to be embarrassed that you can’t contribute further. Contributors will not make you feel bad about it either. Realize that lots of contributors come and go every day. Being busy with your day job or not having enough free time is a perfectly valid reason for not being able to contribute. It’s even possible that you might not feel a good fit with the team or organization. You’re entitled to offer help as a volunteer how you want and when you want.

First and foremost, though, don’t just vanish. When a contributor or potential contributor agrees to do work, can’t follow through for a valid reason, and vanishes, the team may not know the work can be reassigned. In some cases, people in the team may even worry about the contributor’s health or well being.

When you’ve decided it’s time for you to go or take a break, let your sponsor or the list know and let them know what you were working on. Having people think you are working on something when you aren’t slows the team down, and ultimately doesn’t benefit you or the team.

Announce: OLPC software strategy

Chris Ball posted this to an OLPC announce mailinglist and I thought I would share with you all.

Now that the 10.1.1 release for XO-1.5 is out, it’s a good time to
talk about OLPC’s software strategy for the future. We’ve got a few
announcements to make:


OLPC wasn’t planning to make a Fedora 11 release of the XO-1 OS, but
a group of volunteers including Steven Parrish, Bernie Innocenti,
Paraguay Educa and Daniel Drake stepped up and produced Fedora 11 XO-1
builds that follow the OLPC 10.1.1 work. I’m happy to announce that
we’re planning on releasing an OLPC-signed version of that work, and
that this release will happen alongside the next XO-1.5 point release
in the coming weeks. So, OLPC release 10.1.2 will be available for
both XO-1 and XO-1.5 at the same time, and will contain Sugar 0.84,
GNOME 2.26 and Fedora 11. We think that offering this fully
interoperable software stack between XO-1 and XO-1.5 laptops will
greatly aid deployments, and we’re very thankful to everyone who has
enabled us to be able to turn this XO-1 work into a supported release!

To prepare for this XO-1 release, we’ve started working on fixing
some of the remaining bugs in the community F11/XO-1 builds. Paul Fox
recently solved a problem with suspend/resume and wifi in the F11/XO-1
kernel, which was the largest blocker for a supported release. We’ll
continue to work on the remaining bugs, particularly the ones that
OLPC is uniquely positioned to help with.

The first development builds for this release will be published later
this week.


We’ll be continuing to work on XO-1.5 improvements, incorporating
fixes to the “Known Problems” section of the 10.1.1 release notes¹
into the 10.1.2 release.

XO-1.75 and beyond:

XO-1.75 software development is underway. Today we’re announcing
that we’re planning on using Fedora as the base distribution for the
XO-1.75. This wasn’t an obvious decision — ARM is not a release
architecture in Fedora, and so we’re committing to help out with that
port. Our reasons for choosing Fedora even though ARM work is needed
were that we don’t want to force our deployments to learn a new
distribution and re-write any customizations they’ve written, we want
to reuse the packaging work that’s already been done in Fedora for
OLPC and Sugar packages, and we want to continue our collaboration
with the Fedora community who we’re getting to know and work with

We’ve started to help with Fedora ARM by adding five new build
machines (lent to OLPC by Marvell; thanks!) to the Fedora ARM koji
build farm, and we have Fedora 12 and Sugar 0.86 running on early 1.75
development boards. We’d prefer to use Fedora 13 for the XO-1.75, but
it hasn’t been built for ARM yet — if anyone’s interested in helping
out with this or other Fedora ARM work, please check out the Fedora
ARM page on the Fedora Wiki². We’re also interested in hiring ARM and
Fedora developers to help with this; if you’re interested in learning
more, please send an e-mail to jobs-engineering at laptop.org.

We’ll also be continuing to use Open Firmware on the XO-1.75, and
Mitch Bradley has an ARM port of OFW running on our development boards

EC-1.75 open source EC code:

OLPC is proud to announce that the XO-1.75 embedded controller will
have an open codebase (with a small exception, see below). After much
behind-the-scenes effort, EnE has agreed to provide us with a public
version of the KB3930 datasheet and is allowing our new code to be
made public.

The code is not available yet due to a few chunks of proprietary code
that need to be purged and some other reformatting. A much more
detailed announcement will be provided once the new code is pushed to
a public repository. The code will be licensed under the GPL with a
special exception for OLPC use.

The exception is because EnE has not released the low-level details on
the PS/2 interface in the KB3930, so there will be some code that is
not available — relative to the codebase this is a very small amount
of code. The GPL licensing exception will allow for linking against
this closed code. We’re going to investigate ways to move away from
this code in the future. (As far as we’re aware, this will make the
XO-1.75 the first laptop with open embedded controller code!)

Multi-touch Sugar:

We’ve begun working on modifications to Sugar to enable touchscreen
and multitouch use (the XO-1.75 will have a touchscreen, as will
future OLPC tablets based on its design), and we’ll continue to do so.
The first outcome from this work is Sayamindu Dasgupta’s port of the
Meego Virtual Keyboard³ to Sugar — you can see a screencast of it in
action here⁴.

It’s an exciting time for software development at OLPC. Many thanks
for all of your support and efforts!

– Chris, on behalf of the OLPC Engineering team.

¹: http://wiki.laptop.org/go/Release_notes/10.1.1
²: http://fedoraproject.org/wiki/Architectures/ARM
³: http://gitorious.org/fvkbd
⁴: http://dev.laptop.org/~sayamindu/sugar_vkbd_multi.ogv

Chris Ball
One Laptop Per Child

Fedora Board and FESCo Election results

The Fedora elections for the Fedora Project Board and the Fedora
Engineering Steering Committee (FESCo) have concluded, and the results

The Board is electing 3 seats this cycle. A total of 229 ballots were
cast, meaning a candidate could accumulate up to 1374 votes (229 * 6).
The results for the Fedora Board election are as follows:

name | # votes
– ————————–+—————————–
Tom Callaway (spot) | 1001
Máirín Duffy (mizmo) | 978
Rex Dieter (rdieter) | 772
– ————————–+—————————–
Stephen Smoogen (smooge) | 559
John McDonough (jjmcd) | 437
Larry Cafiero (lcafiero) | 430

Therefore, Tom Callaway, Máirín Duffy, and Rex Dieter are elected to
the Board for a full two-release term.

* * *

FESCo is electing 5 seats this cycle. A total of 180 ballots were
cast, meaning a candidate could accumulate up to 1260 votes (180 *
7). The results for the FESCo election are as follows:

name | # votes
– ——————————+———————————–
Bill Nottingham (notting) | 937
Kevin Fenzi (kevin) | 749
Matthias Clasen (mclasen) | 681
Kyle McMartin (kyle) | 545
Steven M. Parrish (tuxbrewr) | 516
– ——————————+————————————
Bruno Wolff III (bruno) | 492
Justin M. Forbes (jforbes) | 460

Therefore, Bill Nottingham, Kevin Fenzi, Matthias Clasen, Kyle
McMartin, and Steven M. Parrish are elected to FESCo for a full
two-release term.

* * *

Congratulations to the winning candidates, and thank you to each of
the nominees for running, and our volunteers and team members for
their assistance.

FADNA 2010 day -1

tomorrow FADNA 2010 starts and I’m still sitting in Indiana. One might ask, “hey, isn’t FADNA 2010 in Aimes, IA?” and One would be correct. I screwed up my booking and will be arriving tomorrow around 12 noon… and the FAD starts at 9am. Brilliant, I know. I have never flown or booked a flight so something was bound to go wrong. I hope this is the only thing.

On the upside Larry gets a night to himself at the hotel (enjoy it sir, you deserve it). I was travelling light anyway so I shouldn’t be too much of a distraction when I show up. I won’t come busting in with one of those bags on wheels or anything.

When I arrive I should be fairly well rested, angry as hell (I just know the TSA will do something to piss me off), and ready to get down to business. I’ll try to follow as much as possible over IRC and talk.fp.o as possible so I don’t throw things off to much.

Well see you all (late) for FADNA Day 0

Fedora Community Gaming Session armacycles-ad

Bruno Wolff posted this to the Announce list:

There will be another Fedora Community Gaming session this weekend.
We will be playing armacyles-ad which is a light cycle game.

We will be starting at:
UTC: 1700 Saturday May 22, 2010
EDT: 1pm Saturday May 22, 2010

The game has short rounds, so drop ins and outs should be easy to accomodate.
I’ll be hanging around at least two hours, and can let the server run as
long as people want to play.

This game comes recommended by a third party, but I’m still acting as
the organizer.

We’ll meet pregame in #fedora-games . If any experienced players want to
recommend server settings, please speak up in the pregame meet up.
We’ll also use in-game chat and I’ll have Fedora Talk set up as well.

A bit more information is at

screenshot of armacycles-ad

screenshot of armacycles-ad © threethirty 2010 NO RIGHTS RESERVED PLEASE USE AS YOU PLEASE UNDER THE CC ZERO LICENSE

Some Updates from All Around Fedora Land

Finally got my ticket for FADNA 2010 they went up $100 USD in the time I proposed it and they were ordered. That is insane but there is no other way I could go. Thanks to Max for suffering through all my BS

Some imminent deadlines for Fedora Summer Coding 2010:

* 13 May — mentors stop submitting ideas. **this one is already past**

We’ve got a mighty list so far, so don’t feel you need to rush in
with more. 🙂 Save a few for the Sep – Feb southern hemisphere run,

* 20 May — student proposals due.

Hopefully students are already working with mentors on so there are
fewer surprises when the mentors start working through the


* 21 May — sponsors pledge funding.

For this summer, last chance to be a sponsor. Want to know more?
Read these posts:



Fedora 14 Release Name:

Thank you to the community for helping us select the name of the
followup to Fedora 13, “Goddard.” The Fedora 14 release name is:


Following are the full election results.

Voting period: Tue 2010-05-04 00:00:01 – Mon 2010-05-10 00:00:01
Number of valid ballots cast: 206

Using the range voting method, each candidate could attain a maximum
of (206*6) = 1236 votes.


votes | name
– ——-+———–
610 | Laughlin
594 | Laramie
507 | Ventnor
482 | Mitikas
459 | Hoppin
403 | Fytnargin

FESCo and Board elections are right around the corner.

In each election cycle, a series of town hall meetings is conducted to
give the community an opportunity to ask the candidates questions –
and hear their answers – on IRC. The town halls for each election are
held twice, to allow for participation by community members in varying
time zones.

The town hall schedule is as follows:

Friday, May 14, 2010 – FESCo town hall – 16:00 UTC (12:00pm US Eastern)

Monday, May 17, 2010 – Fedora Project Board town hall – 00:00 UTC
(8:00pm US Eastern, -SUNDAY-, May 16)

Monday, May 17, 2010 – Fedora Project Board town hall – 17:00 UTC
(1:00pm US Eastern)

Wednesday, May 19, 2010 – FESCo town hall – 02:00 UTC (10:00pm US
Eastern, -TUESDAY-, May 18)

The town hall schedule, as well as important information about how you
can participate in the town halls via IRC, can be seen on the wiki at
http://fedoraproject.org/wiki/Elections#IRC_Town_Halls .

For more details on the elections and candidates, please visit

There will be a One Week Slip on the release of Fedora 13 Goddard.

The F13 final readiness meeting, also known as the “go/no-go” meeting,
was held this evening. As the meeting notes indicate, there are bugs
remaining on the blocker list:


According to the release criteria , the decision was made to slip
the release of Fedora 13 by one week, to Tuesday 2010-05-25.

During composition of any further release candidates, the Fedora
Release Engineering and Quality Assurance teams plan to be
conservative in accepting fixes for the release, and will limit these
to blocker items and critical fixes.

The Fedora 13 release schedule has been updated to reflect the new
release date. We regret any inconvenience to the community. Thank
you for your patience as we try to ensure the best possible Fedora

Fedora and Active Directory

I have been asked a couple of times about integrating $GNU/LinuxDistro into Active Directory and I have always had to turn them away with a joking “that’s above my pay grade” because I have no idea what they were talking about and still don’t but there was a great discussion on the ambassador list about it. Check it out here: