From Fedora Project Wiki

< FWN‎ | Beats

Revision as of 23:27, 15 November 2009 by Abatkin (talk | contribs) (General)

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

This week is an amalgamation of posts from the past two weeks. Two for the price of one!

General

Andrew Vermilya Jamison took a look[1] at the new Fedora Community[2] (Beta) site. "This is a great hub for communication in the distribution and promises to add new features that will make it more useful to other non Package contributing groups in Fedora...I can very well see this becoming a portal for the average Fedora user to: Check forum replies to topic you create, Reporting bugs using the Bugzilla API (would make it far easier to report a bug), Search the Smolt DB for hardware that works on Fedora, Tracking Wiki discussions and pages you might be involved with. All that and so much more, this site has great potential."

Ujjwol Lamichhane examined[3] the Sugar desktop. "Most of you, Linux users have always been lim­ited to the two big desk­top names in Linux. GNOME and KDE today rep­re­sent the Linux desk­top. But there exist other desk­top envi­ron­ment along with these two; XFCE, LDE etc. All these desk­top environment was made with a nor­mal desk­top or lap­top in mind but one desk­top was made with small screen and chil­dren in mind. Yes, the Sugar; the XO’s desk­top from Sugar Labs...Though named as child's desk­top envi­ron­ment, I found Sugar as easy as GNOME, as plas­mic as KDE and as light­weight as XFCE."

Richard Hughes' GNOME Color Manager progressed[4] further with a website[5] and mailing list[6]. Feature-wise, the calibration process is now easier, and and there is initial scanner support[7].

Richard W.M. Jones performed a bunch of benchmarks using guestfish's new sparse disk file creation capability. First was a terabyte[8], but apparently that wasn't good enough. Next up was a Petabyte and an Exabyte[9]. Next up was an analysis[10] of the metadata overhead of various filesystems, then of the mkfs times[11]. And if you are "baffled by the 269 calls that libguestfs provides" check out the libguestfs API overview[12].