From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 12: Line 12:
Starting us off this week is a blast from the past: [[JesusRodriguez|Jesus Rodriguez]] running<ref>http://zeusville.wordpress.com/2010/12/01/os2-warp-4-in-virtualbox/</ref> OS/2 Warp 4 (in VirtualBox).
Starting us off this week is a blast from the past: [[JesusRodriguez|Jesus Rodriguez]] running<ref>http://zeusville.wordpress.com/2010/12/01/os2-warp-4-in-virtualbox/</ref> OS/2 Warp 4 (in VirtualBox).


As part of the process to review Anaconda's user experience, [[MairinDuffy|Máirín Duffy]] noted<ref>http://mairin.wordpress.com/2010/12/02/reinitializing-will-cause-all-data-to-be-lost/</ref> that the "REINITIALIZING WILL CAUSE ALL DATA TO BE LOST!" dialog is both unnecessarily scary and complicated. And this week in Anaconda (#7), [[User:Clumens|Chris Lumens]] also discussed<ref>http://www.bangmoney.org/serendipity/index.php?/archives/161-This-Week-in-Anaconda-7.html</ref> the storage component, specifically how it is tested and using hard disks with different sector sizes.
As part of the process to review Anaconda's user experience, [[MairinDuffy|Máirín Duffy]] noted<ref>http://mairin.wordpress.com/2010/12/02/reinitializing-will-cause-all-data-to-be-lost/</ref> that the "REINITIALIZING WILL CAUSE ALL DATA TO BE LOST!" dialog is both unnecessarily scary and complicated. And this week in Anaconda (#7), [[User:Clumens|Chris Lumens]] also discussed<ref>http://www.bangmoney.org/serendipity/index.php?/archives/161-This-Week-in-Anaconda-7.html</ref> the storage component, specifically how it is tested and using hard disks with different sector sizes. In Part #8<ref>http://www.bangmoney.org/serendipity/index.php?/archives/162-This-Week-in-Anaconda-8.html</ref>, Chris introduced "Lorax", a new project to rebuild the scripts that build an installation image.


While on the topic of disks, [[User:Sundaram|Rahul Sundaram]] outlined<ref>http://fedoranext.wordpress.com/2010/12/06/buttering-up-fedora-15/</ref> where btrfs is going (hint: one day you will likely see it as the default filesystem in Fedora). And the days of naming ethernet interfaces <tt>ethX</tt> may be coming to an end<ref>http://fedoranext.wordpress.com/2010/12/07/a-lesson-in-persistency/</ref>. "Starting in Fedora 15, Ethernet ports on servers will have a new naming scheme corresponding to physical locations, rather than ethX."
While on the topic of disks, [[User:Sundaram|Rahul Sundaram]] outlined<ref>http://fedoranext.wordpress.com/2010/12/06/buttering-up-fedora-15/</ref> where btrfs is going (hint: one day you will likely see it as the default filesystem in Fedora). And the days of naming ethernet interfaces <tt>ethX</tt> may be coming to an end<ref>http://fedoranext.wordpress.com/2010/12/07/a-lesson-in-persistency/</ref>. "Starting in Fedora 15, Ethernet ports on servers will have a new naming scheme corresponding to physical locations, rather than ethX."
[[TomCallaway|Tom Callaway]] posted<ref>http://spot.livejournal.com/316190.html</ref> a set of notes about tuning Fedora for use on an SSD.
[[User:Wwoods|Will Woods]] continued<ref>http://blogs.fedoraproject.org/wp/wwoods/2011/01/03/depcheck-tags-and-timing-2/</ref> describing how the Fedora infrastructure goes about building and testing packages before they arrive on a user's system.
Have you been wondering what the "Network Control Panel" will look like in Gnome 3? Wonder no more, as [[RichardHughes|Richard Hughes]]  posted<ref>http://blogs.gnome.org/hughsie/2010/12/16/gnome-3-and-the-network-control-panel/</ref> a bunch of potential screenshots.


[[User:Rjones|Richard W.M. Jones]] explained<ref>http://rwmj.wordpress.com/2010/12/02/tip-uploading-and-downloading/</ref> how you can use libguestfs, guestfish and its toolset to easily move files between host and guest systems.
[[User:Rjones|Richard W.M. Jones]] explained<ref>http://rwmj.wordpress.com/2010/12/02/tip-uploading-and-downloading/</ref> how you can use libguestfs, guestfish and its toolset to easily move files between host and guest systems.
Line 24: Line 30:
[[User:Jcm|Jon Masters]] suggested<ref>http://www.jonmasters.org/blog/2010/12/15/opinion-fedora-needs-an-architect/</ref> that perhaps the Fedora Project needs a Technical Architect. "FESCo should appoint a person as their technical representative who speaks for overall system architecture concerns. The person in this role should actively seek out compatibility or integration problems but should also be a “go to” person for concerns that arise in the interests of distribution cohesion."
[[User:Jcm|Jon Masters]] suggested<ref>http://www.jonmasters.org/blog/2010/12/15/opinion-fedora-needs-an-architect/</ref> that perhaps the Fedora Project needs a Technical Architect. "FESCo should appoint a person as their technical representative who speaks for overall system architecture concerns. The person in this role should actively seek out compatibility or integration problems but should also be a “go to” person for concerns that arise in the interests of distribution cohesion."


The Fedora Board had its 13 December meeting and posted<ref>http://blogs.fedoraproject.org/wp/board/?p=3</ref> the minutes on their new blog site.
[[MairinDuffy|Máirín Duffy]] mentioned<ref>http://mairin.wordpress.com/2010/12/16/fedora-board-blog/</ref> that the Fedora Board now has its very own blog where the December 13th meeting minutes have already been posted<ref>http://blogs.fedoraproject.org/wp/board/?p=3</ref>.


<references/>
<references/>

Revision as of 13:08, 5 January 2011

Planet Fedora

In this section, we cover the highlights of Planet Fedora[1] - an aggregation of blogs from Fedora contributors worldwide.

Contributing Writer: Adam Batkin

General

Starting us off this week is a blast from the past: Jesus Rodriguez running[1] OS/2 Warp 4 (in VirtualBox).

As part of the process to review Anaconda's user experience, Máirín Duffy noted[2] that the "REINITIALIZING WILL CAUSE ALL DATA TO BE LOST!" dialog is both unnecessarily scary and complicated. And this week in Anaconda (#7), Chris Lumens also discussed[3] the storage component, specifically how it is tested and using hard disks with different sector sizes. In Part #8[4], Chris introduced "Lorax", a new project to rebuild the scripts that build an installation image.

While on the topic of disks, Rahul Sundaram outlined[5] where btrfs is going (hint: one day you will likely see it as the default filesystem in Fedora). And the days of naming ethernet interfaces ethX may be coming to an end[6]. "Starting in Fedora 15, Ethernet ports on servers will have a new naming scheme corresponding to physical locations, rather than ethX."

Tom Callaway posted[7] a set of notes about tuning Fedora for use on an SSD.

Will Woods continued[8] describing how the Fedora infrastructure goes about building and testing packages before they arrive on a user's system.

Have you been wondering what the "Network Control Panel" will look like in Gnome 3? Wonder no more, as Richard Hughes posted[9] a bunch of potential screenshots.

Richard W.M. Jones explained[10] how you can use libguestfs, guestfish and its toolset to easily move files between host and guest systems.

Adam Williamson reported[11] that you may soon be able to install Unity on Fedora. "Why? Well, a few reasons. Mainly, Unity’s an interesting project. I want to look at it and compare it to GNOME Shell and I think quite a few others do too, so it seems nice to package it so you can run both on Fedora..." Adam followed-up[12] with some more technical details.

Bryan Clark mentioned[13] that there is now an experimental Thunderbird extension that can display conversations in a similar way to Gmail.

Jon Masters suggested[14] that perhaps the Fedora Project needs a Technical Architect. "FESCo should appoint a person as their technical representative who speaks for overall system architecture concerns. The person in this role should actively seek out compatibility or integration problems but should also be a “go to” person for concerns that arise in the interests of distribution cohesion."

Máirín Duffy mentioned[15] that the Fedora Board now has its very own blog where the December 13th meeting minutes have already been posted[16].