FWN/Beats/Developments

From FedoraProject

< FWN | Beats
Revision as of 19:10, 17 May 2009 by Ush (Talk | contribs)

Jump to: navigation, search

Contents

Developments

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

Contributing Writer: Oisin Feeley

Broken Dependency Brouhaha

The deliberate introduction of a broken dependency by Richard W.M. Jones resulted prolonged discussion and two FESCo discussion items tabled for the 2009-05-15 meeting. One of those items was the possible removal of "provenpackager" status from Richard.

Michael Schwendt noticed[1] that an update for libguestfs</ref>This exciting library's ability to perform modifications within virtual machine images without the need to actually run those images has been covered previously in the FWN virtualization beat</ref>[2] had been pushed by developer Richard W.M. Jones in the full knowledge that Fedora 10 users would need to import a Fedora 11 qemu package. An anonymous comment on Bodhi situated the decision to release the update as an example of Richard not respecting the release process. Richard arguedCite error: Invalid <ref> tag; refs with no name must have content that as the libguestfs package was completely new only those aware of what they were doing would install it (and consequently would be aware that they needed the qemu from Rawhide or Fedora 11.)

A strong reaction against "[c]reating broken deps when you know they won't be corrected[...]" ensued[3] and led[4] to Seth Vidal deciding to question Richard's suitability as a "provenpackager" on the basis that he lacked common sense.

A sidethread on the advantages of introducing dependency-checking was started by drago01. While Josh Boyer agreed[5] that it would be useful he asked for help in solving the difficult problems which he listed.

The 2009-05-15 FESCo meeting resolved[6] that Toshio Kuratomi and Richard W.M. Jones should draft a Packaging Guideline for approval by the Fedora Packaging Committee. The meeting also decided that as Richard's introduction of a broken dependency was made in the absence of a clear prohibition against such actions, and he was clear that it would not recur, then no sanction should be taken. The handling of similar requests in the future were agreed to be best handled on a case-by-case basis.

  1. https://admin.fedoraproject.org/updates/F10/FEDORA-2009-4696
  2. http://fedoraproject.org/wiki/FWN/Issue175#libguestfs_on_non-Fedora_Platforms
  3. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01094.html
  4. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01130.html
  5. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01111.html
  6. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01320.html

Verilog Emacs Add-Ons

The prime mover behind the Fedora Electronic Lab Spin, Chitlesh Goorah, asked[1] for feedback on splitting-out "verilog-mode" into a separate package so that upstream changes could be tracked more rapidly. This would also have the benefit of laying the groundwork to support OVM and VMM (see FWN#161[2]).

Jonathan Underwood made[3] some good points concerning the danger of missing out on emacs trunk integration of such packages if they were split out. He suggested instead: "[...] a packaging strategy whereby we don't rip out verilog-mode from the core emacs packages, but we can also have an add-on package which contains the latest and greatest verilog-mode which, if installed, is loaded in preference to the one from the core emacs packages[.]" This seemed to be accepted as a positive direction by Chitlesh and a review of the emacs-verilog-mode package was started[4] by Jonathan.

Jerry James raised[5] the issue of XEmacs also having its own version of the package, due to byte-code divergence between Emacs and XEmacs, and also some GPLv2 versus GPLv3 compatibility issues.

  1. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01290.html
  2. https://fedoraproject.org/wiki/FWN/Issue161#Electronic_Design_Automation_Content_Without_Tools_.3F
  3. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01303.html
  4. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01305.html
  5. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01316.html

Open JDK7 Experimental Package

Lillian Angel asked[1] where the OpenJDK[2] team should post their unstable java-1.7.0-openjdk package: 1)to RPMFusion; 2) to a personal FedoraPeople page; 3) to the main Fedora repositories.

Lillian disliked the last option: "I am not keen on getting this package pushed into Fedora since java-1.6.0-openjdk already exists, and jdk7 will not be stable until sometime after Feb 2010[3]."

Following several suggestions it was decided[4] that a personal FedoraPeople repository was the best solution as there would be six or seven packages with no interdependencies.

  1. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01251.html
  2. http://openjdk.java.net/
  3. http://openjdk.java.net/projects/jdk7/milestones/
  4. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01264.html

Making Noise About Moksha

When Dimi Paun continued[1] to report problems using PulseAudio (see FWN#Cite error: Invalid <ref> tag; refs with no name must have content) responses suggested[2] that his use of non-Free Flash or tweaking of GStreamer settings was responsible. Debugging using gstreamer-properties to ensure that "pulsesink" or "autoaudiosink" was the default sink was recommended[3].

Lennart Poettering wanted a bug filed instead of posts to @fedora-devel and when Dimi explained that Bugzilla was too slow and he had already spent a lot of time on the problem Rahul Sundaram suggested[4] using Bugz instead.

Criticism of the display of possibly thousands of "CLOSED" bugs by Bugz led Tom Callaway to offer[5] the hope that Fedora Community will allow developers to "[...] show new/open packages only on a per package basis[.]" This occasioned[6] some apparent criticism from Rahul Sundaram of a lack of openness "[...] it is a giant silo [...]" around the development of Fedora Community[7]. Tom Callaway offered[8] a list of resources to contradict this. When Rahul returned[9] with the criticism that there "[...]is definitely a big lack of communication on this development with the rest of the Fedora community. There was a very brief mail to fedora-announce list but how much input are you getting input from Fedora maintainers whose job this is supposed to make easier?" there was a distinct lack of enthusiasm for more aggressive marketing. Josh Boyer reaffirmed the involvement of several developers with large package lists and expressed[10] a fear that bike-shedding would result from any more exposure. Paul W. Frields pointed[11] to a useful interview[12] with Luke Macken about the Moksha web-application framework upon which Fedora Community is being built.

Moksha is built on a collection of python-based web-frameworks and uses Orbited instead of AJAX to connect rich web applications to servers. Reportedly this is more responsive than AJAX techniques.

A test instance of Fedora Community and AJAX was reported[13] by Tom Callaway to be up. He emphasized that it was a test instance, currently not to be relied upon at all and a disinclination "[...] to spend time wading through the `OMG THIS IS SLOWER THAN BUGZLILLA!!!1!'" reports.

  1. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01003.html
  2. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01005.html
  3. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01010.html
  4. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01018.html
  5. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01021.html
  6. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01022.html
  7. https://fedorahosted.org/fedoracommunity/
  8. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01029.html
  9. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01030.html
  10. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01051.html
  11. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01059.html
  12. https://fedoraproject.org/wiki/Moksha_in_Fedora_11
  13. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01132.html

Be Excellent to Each Other

Regular readers are no doubt aware that flamewars have become more common on @fedora-devel. Project Leader Paul W. Frields posted[1] to the @fedora-advisory-board that the FABCite error: Invalid <ref> tag; refs with no name must have content had decided to deal with the "[...] degradation in tone and signal [...]" by appointing moderators.

Mike McGrath worried[2] that this would constitute an extra burden for board members and also objected to any censorship on principal. [User:Mmcloughlin|Mark McLoughlin]] wondered how posters warned privately by moderators that their behavior was problematic could defend themselves. Seth Vidal replied[3] that this was not a court of law and that problems with moderators could be reported to the board. Later posts along these lines drew[4] a response from Luis Villa which argued strongly that over valuing one's own liberty was a problem: "Or to put it another way: The Fedora community exists to work together towards some common goals. Sometimes, in the name of reaching those goals, you have to be polite and adult towards others so that you can work efficiently and constructively with those other people even when you disagree with them, and work with them in the future after you have stopped disagreeing. This use of words like 'freedom' and 'oppression' suggests to me that some people think their highest reason for being here is about them. It's not about you, it's about working together to build something bigger and better than you. And if you can't play nicely with others in the name of those bigger and better things, or don't understand why sometimes you have to play nice in order to get to those bigger and better things, then maybe this isn't the right place for you."

Paul W. Frields reported[5] that a good deal of work led by Kevin Fenzi was going on to moderate the IRC channels. A later post made[6] by Max Spevack referenced IRC bans in the #cobbler channel and suggested that Red Hat employees needed to be tough-minded and hold themselves to higher standards than other contributors.

  1. https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00026.html
  2. https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00031.html
  3. https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00059.html
  4. https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00072.html
  5. https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00043.html
  6. https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00052.html

Best Way to Store Information Across Desktops

Kushal Das requested[1] tips on making a truly cross-desktop application.

Adam Williamson noticed that many applications were storing information in ~/.config files and Mathieu Bridon providedCite error: Invalid <ref> tag; refs with no name must have content the information that this was an XDGCite error: Invalid <ref> tag; refs with no name must have content spec from freedesktop.org which resulted in replacing a plethora of .app directories with only two: .config to store configuration and .local/share/ to store data.

Jaroslav Řezník pointed[2] to work by the KWallet and gnome-keyring developers to develop[3] a single-sign-on solution on top of a DBUS-based protocol.

  1. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00901.html
  2. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00966.html
  3. https://bugs.freedesktop.org/show_bug.cgi?id=16581