January 2010 - openSUSE Boosters - openSUSE Mailing Lists

work report kw2 prusnak
by Pavol Rusnak 18 Jan '10

18 Jan '10

[GREEN] - connect.o.o (http://void.gk2.sk:3000/) - applied bento theme, still WIP - fixed problem with email sending - tried to gemify cells and apotomo plugins, not done yet, cooperating with upstream - preparations for the talk for Prague Unix Developers Day with Michal - small work on Contrib and Games repos -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

1 0

Work report puzel kw 1,2
by Petr Uzel 18 Jan '10

18 Jan '10

Week 1 - updated packages in Factory: whois, global, rsync, t-prot, libquicktime - updated packages in Contrib: cgdb, tcpjunk - worked on kpartx bugs: #552596, #548765 (fix ready for testing) - reported device-mapper bug: #568048 - closed #473297 (tcpdump, noresponse) - asked Jan Engelhardt to maintain xtables-addons and xtables-geoip in Factory - xtables-addons already there (fate#308441) - worked on #567497 (logrotate) - closed #464426 (kpartx, invalid) - worked on parted&dmraid bug #567652 - hunted race condition between parted & hal in cooperation with upstream - still not clear how to fix it Week 2 - vacation -- Petr Uzel, openSUSE Boosters Team

1 0

Work report KW 2 2010
by Klaas Freitag 18 Jan '10

18 Jan '10

Hello, here we go with 2010: [RED] [AMBER] [GREEN] - catch up with holiday backlog - organising FOSDEM travel by coach, sorting out all needs, too much work - talking about organisation of LinuxTag - worked on sponsoring and others for KDE Plasma Meeting - Meeting with Michael Appleboom - Meeting with Stefan Werden about open-slx engagement in the wiki - some packaging practice - Fixed Hermes' twitter module - some blogging about kraft and screenie - tried to clearify sprinting practice, ie. focussing. Klaas -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

1 0

Egbert's Weeks 50,51 2009 and 2,3 2010
by Egbert Eich 18 Jan '10

18 Jan '10

- Complete KMS integration into Factory and preparation for SLE11 SP1. * Fix mkinitrd to determine the required driver(s) and and pack them into initrd. Modify linuxrc to parse the boot options and pass the required option to enable/disable KMS. * Fix yast2-bootloader and perl-Bootloader to add the required options to the boot command line for each menu entry. * Modify udev to disable automatic loading of DRM modules. This is required as udev cannot be used to enforce a specific order of modules to load while KMS requires the agp module to be loaded. * create a modprobe install script which checks for blacklisted PCI device IDs and prevents those modules from being loaded. * Submitted fixes for both Factory and Enterprise products, tested results: Factory integration is not complete, yet: - mkinitrd: while applying patches newly created files were accidentally omitted. - udev: the latest version of the patch has not yet been incorporated. NOTE: To test KMS integration on Factory you presently still need to add http://download.opensuse.org/repositories/home:/eeich:/Factory-KMS/openSUSE… - Added an image scaler to the SUSE kernel bootsplash code which allows to rescale the bootsplash image to arbitrary resolutions. This allows to show a bootsplash image in both VESA and KMS mode even if both modes differ in resolution. It should allow us to only ship a single bootsplash image (hopefully in higher quality than presently) - Got started on KMS and DRI2 integration into radeonhd. -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

1 0

Retrospectiva
by Michal Hrusecky 16 Jan '10

16 Jan '10

Hi, I've been 'boosted' by one our community member and I started a little cleanup of our Retrospectiva. Before the Xmass we discussed how we thing it works and how we want to use it. But currently there are some leftovers from our previous usage that should be probably deleted. As coolo is using it as it is I didn't touch it. Instead I created new project 'Boosters Work'. If you click on project info of 'Boosters Work' in projects page [1], I tried to somehow summarize how we decided that Retrospective should work for us. Comments are welcome, I hope it is at least a little bit understandable. Other thing I did is that I entered all our Milestones [2] in Retrospective. So everything should be ready to start entering goals and stories. Again, comments are welcome and as we've got a meeting scheduled during next week (IIRC), we can discuss it there and postpone real usage of the new project till then. I thing that if we will really use it, it will help our community to track what we are doing and it will help them to jump in. [1] http://retro.opensu.se/projects [2] http://retro.opensu.se/projects/boosters-work/milestones -- Michal HRUSECKY SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz

1 0

status of factory.o.o sprint
by Stephan Kulow 16 Jan '10

16 Jan '10

Hi, I hope http://retro.opensu.se/milestones/1/sprints/2/stories is a link that works for everyone - I had to click around quite a bit to get to the stories :) anyway I would like to summarize the current status complete: - initial web page is there - requests handling finished - ignore build failures of older sources active: - differences in devel projects (90% done, coolo) - mark packages as out of date (vuntz) - clean up the code, make it less complex (tom) pending: - Maintainer information, mainly useful for filtering - rpmlint warning status (out of scope IMO) - allow to mark known problems in the devel project (will) - Fix recursive devel projects As you can see we're almost done, but there are large blocks left. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

1 0

Sprints and Focus (AI for squad leads)
by Klaas Freitag 13 Jan '10

13 Jan '10

Hi, in our retrospective in the OPS week we were talking about staying on topic in the sprints. The rational is that if we make the sprints to huge we never get something useful out to the customer. And that is the most important because that is the major way to get feedback and contributions. So here is a nice example of how we should not blow up our tasks, and this is not to blame the squad but to illustrate what I mean. Yesterday I talked to Darix about the state of the Umbrella Sprint. On the whiteboard I read things like "Investigate social media stuff" and "implement a key-value storage" and such. This tasks should not be part of the umbrella sprint. Of course they can be useful, yes, there is potential that if we use a framework that can we safe work later etc etc. - all granted, but still: No. Off topic for the umbrella sprint. Go the direct way and get stuff out the door. Make stuff even more cool and efficient etc. in later steps/sprints. Simply create new sprint proposals for these things. So what is the umbrella-sprint than? Good question, and I see it in the responsibility of the squad to define that. Try to answer the question "When is the project considered successful?" and write the answers down and start an open discussion around it. This list should answer the question when the sprint is finished and avoid them being infinite. That should be the first step actually, and I want each of the squads to come up with a few lines of specification what the current sprint is about and what not. AI Squad Leads: Have this little spec for the current sprints ready in Wiki by next sprint meeting (tuesday next week I guess). Again: This is not to blame the umbrella squad but this was an example jumping in my eye. We're all one mischpoke. Yours, Klaas -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

1 0

work report kw1 prusnak
by Lubos Lunak 11 Jan '10

11 Jan '10

[GREEN] - read a lot of mail - updated machine to 11.2 - finished changes that make turnaround rebuild times of KDE OBS projects noticeably faster - wrote some documentation and did some cleanups for the cross-distro KDE building (now that Will is going to present the OBS at CampKDE) - some bugreports -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak(a)suse.cz , l.lunak(a)kde.org -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

2 1

week report 2010#1
by Thomas Schmidt 11 Jan '10

11 Jan '10

- fixed some bugs on build.opensuse.org - development of build.opensuse.org/stage (sprint): - project requests Before the holiday: - Created appliances of the upcoming obs 1.7 release: http://www.digitalflow.de/index.php?seite=blog&postid=32 Greetings -- Thomas Schmidt (tom [at] opensuse.org) openSUSE Boosters Team "Don't Panic", Douglas Adams (1952 - 11.05.2001) -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

1 0

Week report 2010#1
by Vincent Untz 11 Jan '10

11 Jan '10

Hi, What I did last week: - caught up with mails (especially some GNOME Foundation stuff that took time) - L3 work - touched many packages to remove the GNOME 1.x stack. - worked on various maintenance updates - looked at bugzilla. I promise I didn't just look, but also read it. And closed some bugs. - attempted to switch GNOME packages to xulrunner192. Failed in a big way, but did not investigate. What I plan to do this week: - lots of mails to send... - put upstream version in OBS attributes - take at least two days to finally do some upstream coding that can't wait anymore - look closer at xulrunner192. - some GNOME 2.29.5 upstream and packaging work, I guess. What has been annoying me: - I keep discovering new ways to find out about packages depending on GNOME 1.x stack. I was first looking at Requires of the libgtk library. Then I realized that some packages were cheating and using gtk1-compat (sigh). Then I realized some packages were BuildRequiring it for no reason. -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

1 0