From Fedora Project Wiki

< FWN‎ | Beats

m (→‎RawERhide ?: add missing ref)
 
(12 intermediate revisions by the same user not shown)
Line 7: Line 7:
Contributing Writer: [[User:Ush|Oisin Feeley]]
Contributing Writer: [[User:Ush|Oisin Feeley]]


=== Presto A-Go-Go ! ===
=== Would You Like to Write This Beat ? ===


Thanks to some hard work by Fedora Infrastructure folk [[User:Lmacken|Luke Macken]], [[User:Skvidal|Seth Vidal]], [[User:Notting|Bill Nottingham]] and [[User:Jwboyer|Josh Boyer]] <code>Fedora 11</code> will<ref>http://jwboyer.livejournal.com/31831.html</ref> come Presto-enabled contrary to last week's gloomy forecast<ref>http://fedoraproject.org/wiki/FWN/LatestIssue#Presto_No_Go</ref>.  
Following this issue (FWN#178) I will, with regret, no longer be covering the @fedora-devel list. If you are interested in writing this weekly summary of the deeds and doings on the list then please contact fedora-news-list@redhat.com or [[User:Pcalarco|Pascal Calarco]]. A short overview of what you may need to do can be obtained by reading the workflow<ref>http://fedoraproject.org/wiki/FWN/WorkFlow</ref> section of the wiki. The @fedora-news list is also extremely open and helpful. Joining<ref>http://fedoraproject.org/wiki/FWN/NewsProject/Join</ref> the News Project is quite straightforward.


[[User:Pfrields|Paul W. Frields]] described the potential saved download bandwidth as "[t]ypically [...] in double digits, but I’ve heard of cases already (using our development branch Rawhide) where people were saving 90% or more of their download time."
<references/>
 
=== Is gNaughty a Hot Babe ? ===


<references/>
[[User:Sundaram|Rahul Sundaram]] posted<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02071.html</ref> the results of a survey conducted, primarily on @fedora-list and on the forums, to discover which non-repository-packaged software Fedora consumers were using.


=== PPC as a Secondary Architecture ===
One interesting point is that CMUCL<ref>One of the Common Lisp implementations: http://www.cons.org/cmucl/</ref> was revealed<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02088.html</ref> to be only available for 32-bit systems. However what got people really excited was<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg02136.html</ref> Rahul's question about what to do concerning the <code>gNaughty</code> package. Its sole purpose seemed<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg02203.html</ref> to be downloading pornography. Rahul referenced the <code>hot-babe</code> CPU monitor which enjoyed controversy in Debian packaging circles due to its use of female nudity.  Rahul wanted to find out "[...] is this allowed in Fedora?"


The 2009-05-07 FESCo summary reported<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00581.html</ref> that there is interest in moving PowerPC to secondary architecture status. [[DavidWoodhouse|David Woodhouse]] suggested<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00614.html</ref> that it would be interesting to hear from existing secondary architecture teams on the problems they had experienced. To date there are no secondary architectures ready to ship in Fedora.
Amusingly a good deal of the controversy focused on whether the content was freely redistributable, but a predictable moral angle was raised<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02242.html</ref> by [[User:Alsadi|Muayyad AlSadi]] who asked for help in producing a spin which removed content deemed objectionable. Muayyad is a Jordanian developer who has been producing an Arabic-localized Fedora spin named "Ojuba" for some time. Muayyad sought a way to make identifying and tagging packages easier to facilitate this spin. [[User:Notting|Bill Nottingham]] was<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02312.html</ref> skeptical about the chances of tags keeping meaning unless there was some sort of review board. Equally predictable was<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02295.html</ref> the reaction typified by [[User:Skvidal|Seth Vidal]] which resisted any attempt to restrict packages according to standards which had nothing to do with licensing or patent issues. [[User:bochcecha|Mathieu Bridon]] thought<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02355.html</ref> that the creation of a wiki-page by Muayyad would allow anyone interested in co-ordinating work on "Inappropriate Content" to just go ahead and do it without dragging in bureaucracy.


<references/>
<references/>


=== Retiring Packages ===
=== Chrome9 Vx800 Graphics Support on LiveUSB ===
 
[[KristapsViesalgs|Kristaps Viesalgs]] asked<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02146.html</ref> for help in getting the Fedora Live USB to boot correctly on a machine using a Via Vx800 "Chrome9" GPU. Kristaps had some success with the latest upstream version (from their subversion repository) and asked: "Is there any brutal option how to properly boot X with vesa driver, install Fedora, then make openchrome svn installation? Is Fedora planning to make for VIA graphic chipset autoconfiguration utility?"


The decision of the 2009-05-07 FESCo meeting to orphan packages from de-activated maintainers led<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00596.html</ref> [[User:Toshio|Toshio Kuratomi]] to advertise that <code>PackageDB</code> will soon be able to retire packages.
[[User:Ajax|Adam Jackson]] asked<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02154.html</ref> for a more specific bug report because the chip should be supported. He preferred not to ship an autoconfiguration utility instead of just getting the driver correct. Similar points were made by [[User:Adamwill|Adam Williamson]] and [[User:|Xavier Bachelot]]. The latter asked<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02163.html</ref> any interested developers to help out the openchrome project in both the 2D and 3D(Gallium) sides.  


<references/>
<references/>


=== RawERhide ? ===
=== Who Wants a Pony? ===
 
[[User:Kushal|Kushal Das]] promised<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02139.html</ref> a pony to anyone that would take the trouble to review<ref>http://bugzilla.redhat.com/show_bug.cgi?id=503021</ref> one of his packages.


[[User:Jkeating|Jesse Keating]] asked<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00359.html</ref>: "How is it we have 182 stable updates pending for F11 already?  How have these seen any testing by a wider audience?  Are we really just not bothering with updates-testing anymore?  Do we not care about distro stability?" An interesting thread discussed the ways in which developer workflow and the availability of updates for testing can be re-aligned to each other. Among the complications discussed were the need to provide a way to upgrade for a previous release and the coupling of DVD image preparation with a release.
<references/>


[[User:Till|Till Maas]] replied that updates-testing requests for <code>Fedora 11</code> had apparently not been processed and [[User:Kkofler|Kevin Kofler]] argued<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00573.html</ref> that the chances were high that packages which built succesfully on an earlier release would build on a later one. This was disputed by [[User:Jkeating|Jesse Keating]]. [[User:Dcantrel|David Cantrell]] and [[User:Skvidal|Seth Vidal]] shared<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00382.html</ref> their experience of users not responding to requests to test and comment on updates provided in <code>Bodhi</code>.
=== Firestarter Retired as Unportable to PolicyKit ===


A debate over the problems caused between the mismatch between the rolling, continuous nature of development and the need to freeze packages in a known state to produce a release received substantial contributions from [[RalfCorsepius|Ralf Corsepius]], who argued<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00435.html</ref> that Release-Engineering should change the workflow considerably. [[User:Jkeating|Jesse Keating]] responded<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00469.html</ref> with a defense of the current system which emphasized the need of maintainers to adhere to the current workflow and "good development practices."
[[User:Maxamillion|Adam Miller]] asked<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02089.html</ref> whether he should just retire the <code>Firestarter</code><ref>Firestarter is a firewall configuration GUI</ref> package for which he had recently become the maintainer. His query was based on the recent filing of RFEs to integrate <code>Firestarter</code> with <code>PolicyKit</code>. These suggested to Adam that a large amount of work would be needed due to the lack of any upstream activity for four years and the need to grok <code>PolicyKit</code>.


[[RichardJones|Richard W.M. Jones]] was<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00398.html</ref> in favor of rolling releases.
Following confirmation from [[User:Sundaram|Rahul Sundaram]] and [[User:Skvidal|Seth Vidal]] a decision was made<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02094.html</ref> by Adam: "I would honestly rather retire the package than do a WONTFIX, if the project as a whole is going the direction of PolicyKit and upstream is dead then I don't want to keep old and busted cruft around the repositories as Fedora continues to look towards the future."
A further suggestion from "Cry" prompted<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02122.html</ref> Adam to start filing RFEs against <code>system-config-firewall</code> for any features present in <code>Firestarter</code> but missing in <code>system-config-firewall</code>.
<references/>


[[User:Mschwendt|Michael Schwendt]] explained<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00554.html</ref> the problems arising when the <code>updates-testing</code> repository was not used as intended.
=== Russian Fedora ? ===


[[MichalHlavinka|Michal Hlavinka]] proposed<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00448.html</ref> breaking the freeze solely for the updates-testing repository shortly before the GA release.
When [[User:Peter|Peter Lemenkov]] asked<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02013.html</ref> about the idea of creating a Fedora Foundation outside of the U.S.A. the usual arguments from the past few years were rehashed. [[User:Kkofler|Kevin Kofler]] gave<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02025.html</ref> an able summary why this would still present Red Hat with a problem.


There's a lot more in this thread beyond the ability of your correspondent to summarize adequately. It's worth a read for anyone trying to understand how and why Fedora is produced.
An assertion by [[User:|Alexey Torkhov]] that there existed<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02390.html</ref> a Red Hat-sanctioned "RussianFedora" spin which contained mp3 codecs and other material excluded from the actual Fedora Project repositories drew demands for proof from [[User:Sundaram|Rahul Sundaram]].


<references/>
<references/>


=== Crypto Consolidation ===
=== Will FESCo Revisit Kmods ? ===


[[AdamGoode|Adam Goode]] asked<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00349.html</ref> whether <code>NSS</code> was ready to provide <code>TLS</code> support. Adam referenced the Crypto Consolidation project<ref>http://fedoraproject.org/wiki/FedoraCryptoConsolidation</ref> (see also FWN#107<ref>http://fedoraproject.org/wiki/FWN/Issue107#Crypto_Consolidation</ref>).
A discussion of why <code>VirtualBox</code> will not be a feature due to its code not yet heading upstream and consequently remaining as <code>kmods</code> drew a statement of support from [[User:Kkofler|Kevin Kofler]] for reverting the current banning of <code>kmods</code> should he become a FESCo member. Upon request from [[RichardJones|Richard W.M. Jones]] for a dispassionate summary of the reasons to avoid <code>kmods</code> drew<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02254.html</ref> a concise response from [[User:Skvidal|Seth Vidal]].


[[Dwinship|Dan Winship]] confirmed<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00370.html</ref> that for the present <code>NSS</code> was best used directly with applications rather than by other libraries. [[RobertRelyea|Robert Relyea]] provided<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00493.html</ref> a detailed response to Adam including the hopeful sounding news that some of the issues around <code>NSS_Init</code> may be fixed in a few months.
[[User:Adamwill|Adam Williamson]] and [[User:Mdomsch|Matt Domsch]] (Dell's DKMS mastermind) kicked<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02368.html</ref> some ideas back and forth over the advantages of <code>akmods</code> versus <code>kmods</code>.


<references/>
<references/>


=== Intel Moblin Pushing Proprietary Poulsbo ? ===
=== Upgrade from Fedora 10 to Rawhide (Fedora 11) ===
 
Last week's thread<ref>http://fedoraproject.org/wiki/FWN/LatestIssue#Moblin2_Mostly_Fedora-derived_.3F</ref> about the significant amount of Fedora-originating code being rolled into Intel's <code>Moblin2</code> platform without much kudos or thanks continued. Questions were asked<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00212.html</ref> about why Intel was not providing code for the <code>Poulsbo</code> graphics chipset (common in many netbooks) except via obscure repositories.  The appearance of ex-Red Hatter [[ArjanvandeVen|Arjan van de Ven]], who argued in defense of binary blobs in these drivers, occasioned<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00248.html</ref> some wry commentary.


When [[User:Adamwill|Adam Williamson]] pointed to a "huge new pile of crack [...] in the Ubuntu Mobile special-sauce repositories [...]" [[DanWiliams|Dan Williams]] asked<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00326.html</ref>: "What makes the Poulsbo team so special that they are exempt from the upstreaming policy that every other part of Intel seems to follow so well these days?" Later discussion suggested<ref>https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00491.html</ref> that it ought to at least be possible to produce a "[...] basic native accelerated 2D driver which doesn't depend on all the horrible proprietary crack [.]"  
Following a report from [[UweKiewel|Uwe Kiewel]] that a <pre>yum upgrade</pre> had spewed all sorts of errors the supported methods for upgrades were re-stated<ref>http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02041.html</ref> by [[User:Adamwill|Adam Williamson]]: "[I]f you talk to the people most involved in implementing it (Seth) and testing it (Will) they will tell you that doing live upgrades via yum can't really ever be 100% safe for various reasons, but preupgrade can get very close and is useful in all the same cases. So their position is, we support preupgrade, we don't support yum. If yum works, great, if it doesn't, you can bug people to fix whatever it stopping it working, but it's not 'required' by any policy or guideline."


<references/>
<references/>

Latest revision as of 01:15, 1 June 2009

Developments

In this section the people, personalities and debates on the @fedora-devel mailing list are summarized.

Contributing Writer: Oisin Feeley

Would You Like to Write This Beat ?

Following this issue (FWN#178) I will, with regret, no longer be covering the @fedora-devel list. If you are interested in writing this weekly summary of the deeds and doings on the list then please contact fedora-news-list@redhat.com or Pascal Calarco. A short overview of what you may need to do can be obtained by reading the workflow[1] section of the wiki. The @fedora-news list is also extremely open and helpful. Joining[2] the News Project is quite straightforward.

Is gNaughty a Hot Babe ?

Rahul Sundaram posted[1] the results of a survey conducted, primarily on @fedora-list and on the forums, to discover which non-repository-packaged software Fedora consumers were using.

One interesting point is that CMUCL[2] was revealed[3] to be only available for 32-bit systems. However what got people really excited was[4] Rahul's question about what to do concerning the gNaughty package. Its sole purpose seemed[5] to be downloading pornography. Rahul referenced the hot-babe CPU monitor which enjoyed controversy in Debian packaging circles due to its use of female nudity. Rahul wanted to find out "[...] is this allowed in Fedora?"

Amusingly a good deal of the controversy focused on whether the content was freely redistributable, but a predictable moral angle was raised[6] by Muayyad AlSadi who asked for help in producing a spin which removed content deemed objectionable. Muayyad is a Jordanian developer who has been producing an Arabic-localized Fedora spin named "Ojuba" for some time. Muayyad sought a way to make identifying and tagging packages easier to facilitate this spin. Bill Nottingham was[7] skeptical about the chances of tags keeping meaning unless there was some sort of review board. Equally predictable was[8] the reaction typified by Seth Vidal which resisted any attempt to restrict packages according to standards which had nothing to do with licensing or patent issues. Mathieu Bridon thought[9] that the creation of a wiki-page by Muayyad would allow anyone interested in co-ordinating work on "Inappropriate Content" to just go ahead and do it without dragging in bureaucracy.

Chrome9 Vx800 Graphics Support on LiveUSB

Kristaps Viesalgs asked[1] for help in getting the Fedora Live USB to boot correctly on a machine using a Via Vx800 "Chrome9" GPU. Kristaps had some success with the latest upstream version (from their subversion repository) and asked: "Is there any brutal option how to properly boot X with vesa driver, install Fedora, then make openchrome svn installation? Is Fedora planning to make for VIA graphic chipset autoconfiguration utility?"

Adam Jackson asked[2] for a more specific bug report because the chip should be supported. He preferred not to ship an autoconfiguration utility instead of just getting the driver correct. Similar points were made by Adam Williamson and [[User:|Xavier Bachelot]]. The latter asked[3] any interested developers to help out the openchrome project in both the 2D and 3D(Gallium) sides.

Who Wants a Pony?

Kushal Das promised[1] a pony to anyone that would take the trouble to review[2] one of his packages.

Firestarter Retired as Unportable to PolicyKit

Adam Miller asked[1] whether he should just retire the Firestarter[2] package for which he had recently become the maintainer. His query was based on the recent filing of RFEs to integrate Firestarter with PolicyKit. These suggested to Adam that a large amount of work would be needed due to the lack of any upstream activity for four years and the need to grok PolicyKit.

Following confirmation from Rahul Sundaram and Seth Vidal a decision was made[3] by Adam: "I would honestly rather retire the package than do a WONTFIX, if the project as a whole is going the direction of PolicyKit and upstream is dead then I don't want to keep old and busted cruft around the repositories as Fedora continues to look towards the future."

A further suggestion from "Cry" prompted[4] Adam to start filing RFEs against system-config-firewall for any features present in Firestarter but missing in system-config-firewall.

Russian Fedora ?

When Peter Lemenkov asked[1] about the idea of creating a Fedora Foundation outside of the U.S.A. the usual arguments from the past few years were rehashed. Kevin Kofler gave[2] an able summary why this would still present Red Hat with a problem.

An assertion by [[User:|Alexey Torkhov]] that there existed[3] a Red Hat-sanctioned "RussianFedora" spin which contained mp3 codecs and other material excluded from the actual Fedora Project repositories drew demands for proof from Rahul Sundaram.

Will FESCo Revisit Kmods ?

A discussion of why VirtualBox will not be a feature due to its code not yet heading upstream and consequently remaining as kmods drew a statement of support from Kevin Kofler for reverting the current banning of kmods should he become a FESCo member. Upon request from Richard W.M. Jones for a dispassionate summary of the reasons to avoid kmods drew[1] a concise response from Seth Vidal.

Adam Williamson and Matt Domsch (Dell's DKMS mastermind) kicked[2] some ideas back and forth over the advantages of akmods versus kmods.

Upgrade from Fedora 10 to Rawhide (Fedora 11)

Following a report from Uwe Kiewel that a

yum upgrade

had spewed all sorts of errors the supported methods for upgrades were re-stated[1] by Adam Williamson: "[I]f you talk to the people most involved in implementing it (Seth) and testing it (Will) they will tell you that doing live upgrades via yum can't really ever be 100% safe for various reasons, but preupgrade can get very close and is useful in all the same cases. So their position is, we support preupgrade, we don't support yum. If yum works, great, if it doesn't, you can bug people to fix whatever it stopping it working, but it's not 'required' by any policy or guideline."