Jump to content
Compatible Support Forums
Sign in to follow this  
news

Fedora Weekly News 186

Recommended Posts

* 1 Fedora Weekly News Issue 186

o 1.1 Planet Fedora

+ 1.1.1 General

+ 1.1.2 POSSE Roundup

o 1.2 QualityAssurance

+ 1.2.1 Test Days

+ 1.2.2 Weekly meetings

+ 1.2.3 F12 Alpha blocker bug review meeting

+ 1.2.4 Xfce spin testing

+ 1.2.5 KDE QA tester request

+ 1.2.6 Bugzilla semantics debate

o 1.3 Translation

+ 1.3.1 F12 Translation Team Schedule Proposal

+ 1.3.2 Translation Quick Start Guide Updated

+ 1.3.3 Publican Version of Minor Fedora Documents Made Available

+ 1.3.4 New Members in FLP

o 1.4 Artwork

+ 1.4.1 Evaluating the Gallery

+ 1.4.2 A Small Icon Request

+ 1.4.3 Fedora 12 Theming Progress

o 1.5 Virtualization

+ 1.5.1 Fedora Virtualization List

# 1.5.1.1 New Release libguestfs 1.0.64

# 1.5.1.2 Swap Use in Guests

# 1.5.1.3 Clustering libvirt Hosts

+ 1.5.2 Virtualization Tools List

# 1.5.2.1 Virtual Machine Cloning

# 1.5.2.2 Virt Manager UI Rework

# 1.5.2.3 Support for Processor Affinity

# 1.5.2.4 Virt What?

 

- Fedora Weekly News Issue 186 -

 

Welcome to Fedora Weekly News Issue 186[1] for the week ending July 26,

2009.

 

In this week's issue, we begin with news from the Fedora Planet,

including tips on running Fedora 11 on an Intel Mac, tethering Fedora 11

to an iPhone, and another in the series of XI2 Recipes. Quality

Assurance reports on last week's Fit and Finish test day on power

management and suspend/resume, as well as much detail on QA-related

weekly meetings. Translation brings us detail of the Fedora 12

Translation Schedule, a new Translation Quick Start Guide, as well as

new Publican version of some Fedora documentation In Artwork/Design

news, testing details of the new gallery and an update on Fedora 12

theming, amongst other topics. This issue rounds out with Fedora

virtualization goodness, including details on new versions of

libguestfs, virt-what and redesigns of the virt-manager UI, as well as

details on how to cluster libvirt hosts. We hope you enjoy this week's FWN!

 

If you are interested in contributing to Fedora Weekly News, please see

our 'join' page[2]. We welcome reader feedback: fedora-news-list ( -at -) redhat.com

 

The Fedora News team is collaborating with Marketing and Docs to come up

with a new exciting platform for disseminating news and views on Fedora,

called Fedora Insight. If you are interested, please join the list and

let us know how you would like to assist with this effort.

 

FWN Editorial Team: Pascal Calarco, Adam Williamson

 

1. http://fedoraproject.org/wiki/FWN/Issue186

2. http://fedoraproject.org/wiki/NewsProject/Join

 

-- 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

 

1. http://planet.fedoraproject.org

 

--- General ---

 

Greg DeKoenigsberg responded[1] to slashdot[2] to correct what Nicholas

Negroponte actually said regarding the Sugar UI and OLPC. "But what we

did...was we had Sugar do the power management, we had Sugar do the

wireless management -- it became sort of an omelet. The Bios talked

directly with Sugar, so Sugar became a bit of a mess. It should have

been much cleaner, like the way they offer [it] on a stick now."

 

Jef Spaleta was excited[3] by the news that all of Launchpad has finally

been open sourced by Canonical.

 

Harish Pillay questioned[4] Microsoft's true motives behind contributing

GPL patches to the Linux kernel. Martin Sourada quoted[5] Linus'

response to the general feeling of hatred toward Microsoft in the Linux

community.

 

Daniel Walsh explained[6] how the SELinux "unconfined" domain works.

 

Peter Hutterer added[7] part 5 to the XI2 Recipes series, explaining

"grabs" and part 6[8], showing examples dealing with the client pointer.

 

Steven Moix provided[9] a few tips for natively running Fedora 11 on an

Intel Mac.

 

Jesse Keating described[10] how to tether an iPhone to Fedora over

bluetooth, for a truly wires-free internet experience.

 

1. http://gregdek.livejournal.com/52052.html

2.

http://linux.slashdot.org/story/09/07/20/1628228/Negroponte-Sees-Sugar-As-OLPCs-Biggest-Mistake?art_pos=3

3. http://jspaleta.livejournal.com/45216.html

4. http://harishpillay.livejournal.com/162161.html

5. http://mso-chronicles.blogspot.com/2009/07/true-meaning-of-open.html

6. http://danwalsh.livejournal.com/30084.html

7. http://who-t.blogspot.com/2009/07/xi2-recipes-part-5.html

8. http://who-t.blogspot.com/2009/07/xi2-recipes-part-6.html

9.

http://www.alphatek.info/2009/07/22/natively-run-fedora-11-on-an-intel-mac/

10. http://jkeating.livejournal.com/75270.html

 

--- POSSE Roundup ---

 

The Professors Open Source Summer Experience[1] just finished its Summer

2009 session, and here is a roundup of some of the Planet posts from the

event.

 

* http://gregdek.livejournal.com/52300.html

* http://blog.melchua.com/2009/07/21/posse-monday-how-seneca-got-involved/

*

http://blog.melchua.com/2009/07/21/posse-monday-helping-students-find-projects-that-make-them-come-alive/

*

http://blog.melchua.com/2009/07/22/posse-tuesday-contributor-types-and-making-safe-spaces/

* http://blog.melchua.com/2009/07/22/posse-wednesday-our-classroom-setup/

* http://michaeldehaan.net/2009/07/24/fedora-has-a-posse/

 

1. http://teachingopensource.org/index.php/POSSE

 

-- Quality Assurance --

 

In this section, we cover the activities of the QA team[1].

 

Contributing Writer: Adam Williamson

 

1. http://fedoraproject.org/wiki/QA

 

--- Test Days ---

 

There was no main track Test Day last week. The Fit and Finish project's

Test Day track continued with its second Test Day, on power management

and suspend/resume[1]. The event was a success, with several testers

turning out, many bugs filed, and some fixed during the day or soon

afterwards, especially relating to laptops with multiple batteries.

 

No Test Day is scheduled for next week. If you would like to propose a

main track Test Day for the Fedora 12 cycle, please contact the QA team

via email or IRC, or file a ticket in QA Trac[2].

 

1.

https://fedoraproject.org/wiki/Test_Day:2009-07-21_Fit_and_Finish:Batteries_and_Suspend

2. https://fedorahosted.org/fedora-qa/

 

--- Weekly meetings ---

 

The QA group weekly meeting[1] was held on 2009-07-22. The full log is

available[2]. James Laska reported that he had published a blog post

asking people to help with the process of writing Debugging pages[3].

Adam Williamson mentioned that he had looked into creating some of the

desired pages, but did not know what kind of information was actually

required for any of the components concerned. Jesse Keating suggested

doing an informal interview-style session with maintainers to discover

what information is needed, and then having QA take responsibility for

turning that information into a finished Wiki page.

 

James Laska had created a meeting time matrix[4] for the purpose of

re-scheduling the QA meeting to make it possible for as many group

members as possible to attend. The group agreed that the new meeting day

and time should be Mondays at 16:00 UTC, moved from Wednesdays at 16:00 UTC.

 

James Laska noted that a Fedora 12 Alpha blocker bug review meeting was

scheduled for Friday 2009-07-24. It was agreed that Adam Williamson

would send out an announcement of the meeting, and James would send out

a recap after it had finished. Jesse Keating mentioned it would be good

to do some Rawhide install testing prior to the meeting, but a

combination of two significant bugs was preventing almost any Rawhide

install from working.

 

James Laska explained that a test compose for Fedora 12 Alpha was

scheduled for 2009-07-29, and Liam Li had made an announcement

requesting help on install testing[5]. Jesse Keating pointed out that it

would not be easy for the general public to take part, as the test

compose would not be generally distributed. This led to another long

discussion about the practicality of distributing time-critical test

composes to the public. No definite conclusion was reached, but a

tentative agreement was made to look into a system which would allow

access to such composes to members of the QA group in FAS.

 

Jóhann Guðmundsson noted that there were some problems with Dracut, the

nash/mkinitrd replacement being introduced as a feature in Fedora 12. It

has no implementation plan by which the progress of the feature can be

externally measured, and no detailed contingency plan beyond 'revert to

mkinitrd'. Jóhann agreed to contact the feature mantainer, Harald Hoyer,

to help develop a full test plan and contingency plan.

 

Will Woods reported on the progress of the AutoQA project. He has now

automated the first four test cases in the Rawhide Acceptance Test

Plan[6], and is now working on automating the installation tests. He

noted that separate i386, x86-64 and PowerPC test hosts would be

necessary for some tests, and that PPC might be difficult in the absence

of the Fedora standard libvirt virtualization framework on that

platform. Jesse Keating worried that the installation tests may be

adding too much complexity to the system, and asked how much faster the

process would be if only repository level tests were considered. Adam

Williamson pointed out that the full set of repository level tests were

the ones that had already been automated. Will promised that they would

be updated to send the results somewhere publicly accessible soon.

 

Sebastian Dziallas brought up the topic of a Test Day for the Sugar on a

Stick project[7] - essentially for the integration of Sugar with a stock

Fedora distribution. It was agreed that the SoaS project would host the

Test Day themselves using the SOP created for this purpose[8]. A

tentative date of 2009-09-03 was agreed for the test day.

 

The Bugzappers group weekly meeting[9] was held on 2009-07-21. The full

log is available[10]. No-one had heard from Brennan Ashton regarding the

status of the triage metrics project. Adam Williamson agreed to contact

him by email to find out the current status, and ask if he would be

interested in having a co-maintainer on the project, in the interest of

smoother development.

 

The group discussed the current draft of the critical path-based triage

component list[11]. There was a general feeling that the list was very

long and might contain components that, practically speaking, would not

benefit hugely from triage. It also seemed to contain at least some

binary (rather than source) package names, while Bugzilla is based on

source package names. Niels Haase and Matej Cepl volunteered to adjust

the list to use source package names, and break it up into groups for

ease of digestion, for further review at next week's meeting.

 

Adam Williamson gave an update on the status of the kernel bug triage

project. He admitted it had not progressed very far as he had been

focussing on anaconda triage. He outlined a plan under which a volunteer

would, as a test, triage bugs on one particular component of the kernel,

to see if the process could be made to work. Edward Kirk thought the

proposal a sound one, and Adam agreed to try and put in into practice in

the next week.

 

Finally, the group discussed the 'Bugzilla Semantics' proposal Adam

 

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×