Planet Fedora
In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide.
http://planet.fedoraproject.org
Contributing Writer: Max Spevack
Events & Trip Reports
Yaakov Nemoy wrote[0] about his trip to the Central Pennsylvania Open Source Conference.
[0] http://loupgaroublond.blogspot.com/2008/10/cposc-endnotes.html
Max Spevack posted[1] about his experiences at Athens Digital Week, as did Diego Zacarao[2].
[1] http://spevack.livejournal.com/67628.html
[2] http://diegobz.net/2008/10/18/athens-digital-week-day-1-and-2/
Greg DeKoenigsberg and Chris Tyler both[3] posted[4] about the first day of FSOSS in Toronto. Of particular interest is the "Teaching Open Source" track[5], as well as the FSOSS planet[6] and flickr[7] page. Jack Aboutboul posted[8] about his first day at FSOSS, as did[9] Paul Frields.
[3] http://gregdek.livejournal.com/37958.html
[4] http://blog.chris.tylers.info/index.php?/archives/145-FSOSS-Begins.html
[5] http://fsoss.senecac.on.ca/2008/?q=node/78
[6] http://zenit.senecac.on.ca/~chris.tyler/fsoss-planet/
[7] http://flickr.com/photos/tags/fsoss2008
[8] http://jaboutboul.blogspot.com/2008/10/id-rather-be-with-animal-part-1.html
[9] http://marilyn.frields.org:8080/~paul/wordpress/?p=1243
Sandro Mathys had done a fantastic job preparing for FAD EMEA, and he posted the latest status update about that event to all the Ambassadors[10].
[10] http://blog.sandro-mathys.ch/2008/10/23/fad-emea-2008-3-weeks-to-go
Tech Tidbits
Fabian Affolter prepared[11] five activities for the XO, and submitted the packages for review.
[11] http://fabaff.blogspot.com/2008/10/xo-activities-for-fedora-part-ii.html
Jeremy Katz discussed[12] some tips about the best way to make the Fedora 10 Snapshot 2 work on the XO.
[12] http://katzj.livejournal.com/441143.html
Dan Walsh wrote[13] an interesting blog post about "security vs. usability" tradeoffs, based on his experiences at a conference in Washington. The full post is related to both SELinux and Xen.
[13] http://danwalsh.livejournal.com/25265.html
John Poelstra posted[14] an article that emphasisizes the WHY, as opposed to the HOW, of bug triage. Two of the reasons that he mentions are that triage "saves package maintainers time chasing down missing information in bug reports" and that it "allows maintainers to spend their finite time on bugs that are ready to be worked on".
[14] http://poelcat.wordpress.com/2008/10/20/why-bug-triage/