- openSUSE Boosters

Contrib cleanup (and push to Factory)
by Pavol Rusnak 06 Apr '11

06 Apr '11

Hello all! Currently, there is almost no difference between maintaining the package in Contrib and in Factory so we'd like to encourage Contrib maintainers to push their packages into various devel projects and then to Factory. As the first steps are hardest to do, I went through all 351 Contrib packages and tried to figure out in what devel project these packages might below. I am not 100% right, so please take this info as a suggestion, not as a dogma :-) There are two lists attached: - users.txt - list of contrib maintainers, sorted by maintained packages - as you can see this is not some procedure I invented and force you to go through, I will have to do the same thing for 60 packages :-) - packages.txt - list of packages with the suggested devel projects - the format of the lines is following: * package name * maintainer(s) * suggested devel project (I couldn't figure out 4 packages, so they have "?" there ...) * comment - about renaming 4 library packages from libfooX to libfoo Unfortunately, some of the packages are not in the ideal shape for submission to Factory. Please update your packages to the latest upstream version and do some cleanup. For this you can use the tool spec-cleaner[1] (which is not perfect, so please review the results, hopefully it will get some love during the Summer of Code). [1] http://gitorious.org/opensuse/spec-cleaner/blobs/raw/master/spec-cleaner Once you are done, you can submit your packages to devel project. I'm sure you know the following procedure: Example: $package is 3dto3d, $develproject is graphics osc sr openSUSE:Factory:Contrib $package $develproject Once the package is accepted you should request adding yourself as a maintainer/bugowner using the following command: osc creq -a add_me maintainer $develproject $package \ -a add_me bugowner $develproject $package Once applied you can create submitrequests to Factory! Isn't that great? :-) Maintainers of the Contrib packages will receive another email with the packages maintained by them, so they don't have to dig through the large list :-) Hopefully we'll be able to push as much packages from Contrib to Factory as possible before the next release! In case there are any questions don't hesitate to ask on opensuse-contrib(a)opensuse.org. Thanks! -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic

1 1

ambassador program
by Jos Poortvliet 06 Apr '11

06 Apr '11

Hey marketing team, Based on our IRC discussion yesterday a more extensive proposal, connected to the mail I just send to the boosters with you in CC: Our ambassadors are often local (many don't even speak English, or barely); so what we do with/for them has to be translatable, easy to read or in their hands. They often spend not a huge amount of time on openSUSE; so what we do for/with them should not take much time. And the fact they are ambassador gives them some credibility; so we should make that clear. Currently, we have an ambassador mailinglist. Some ambassadors are on there; many are not (like most of the active people in Brazil or Greece - despite those countries being among the most active for us, as far as we know). They usually have a local mailinglist (not on openSUSE infrastructure) which they use for planning and discussing. First, I would like to propose to bring such mailinglists to openSUSE infrastructure. That means - let ambassadors ask for a language/region specific mailinglist. Not too many rules, if they feel they need one for something, give it. But there should be one limitation: at least one or two active people on that list should be on the international ambassador mailinglist; and we need a one-way, moderated mailinglist to reach ALL ambassador lists at once for things that concern everybody. Second, let them create a localized ambassador team page on the wiki (or on connect.opensuse.org, dunno what makes most sense). Actually, it'd be great if they had an English page which is translated - so each team (the Greek team, Brazil team etc) has a page on the wiki; and it is translated in their language(s). They can have links there to the mailinglist and the forum place they hang out, as well as their IRC channel(s). This will allow countries/regions to build their own team. Yet, due to the requirement of having 1-2 ppl on the international list, we are connected. Now we need to make sure there is communication as much as possible. The ambassadors should get the word out on what they do - that's what the ambassador report stuff is for, which I mailed to the Boosters team. I hope we can make that happen. Cheers, Jos

6 11

work report cw 13
by Ismail Doenmez 05 Apr '11

05 Apr '11

What I did: - Profiled devel:languages:python and found the contributors in last 6 months - Created a list of emails with number of packages - Got blocked by moving to new flat & bureaucratic work - Took over KDE Live DVD project from Will - GSoC student handling What I plan to do: - Finish KDE Live DVD (90% done) - Email devel:languages:python committers and get them to commit to Factory - More student handling for GSoC, help them with their proposals -- İsmail Dönmez - openSUSE Booster SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- 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 cw 13
by Michal Hrusecky 04 Apr '11

04 Apr '11

What I did: * GSoC - students applications are open, students started contacting me more intensively - followed up discussions with students I already have - finished up blog posts about my GSoC ideas - results: - two students submitted their proposals for their projects - one more will submit this week as he was busy with Gnome Asia - discussed ideas with all students even with regards to their coding skills and I'm confident that they all enough skills and enthusiasm to make these projects successful. * followed up discussion regarding Elgg OpenID provider plugin - it exists, it works, unfortunately not on our server - works on my testing server - doesn't work on connect.opensuse.org - I blame iChain (iChain is responsible for everything these days, right?), but it will need some more investigation What I plan to do: * GSoC - this time, there will be hopefully not so much work left * bugs, bugs, bugs -- 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

work report prusnak cw 13
by Pavol Rusnak 04 Apr '11

04 Apr '11

What I did: * started a discussion on opensuse-ruby about pushing gems to Factory - they're in a constant flux, it is better to keep them in d:l:r:e - users may use rvm as well * got positive feedback from Pascal about moving games packages from Packman to OBS - the rest of the maintainers seem to have no problem with that or they just don't care * GSoC administration What I plan to do: * import games packages from Packman to OBS * start Contrib discussions -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- 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 Klaas Freitag cw 13/2011
by Klaas Freitag 04 Apr '11

04 Apr '11

[RED] [AMBER] [GREEN] - april fooling, collaboration with an interesting group of poeple from all participating distros, created the canterbury project webside. - administrative stuff such as travel forecast, various mails etc. - Azubis - Hermes documentation updates - Hermes (herminator) login adopted to LDAP - again some Hermes packaging - GSoC advertising and students care - other useful Hermes 'consulting' for Meego related projects - Hermes diagnostics: went through the subscriptions with coolo and get clearified why he gets which emails - some discussions and readings about openAuth, the planned openSUSE authentication system - tried to get some activity around the new "based on openSUSE" design Planing for this week: - Some more Hermes cleanup - do more fuzz around GSoC topics -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

1 0

Proposal for Building, Managing Code Testing Ecosystem
by Tony Su 01 Apr '11

01 Apr '11

Hello Group, I was informed that this was the best place to submit a rather large and potentially influential openSUSE project. Through Bryen and the openSUSE marketing group, I came to understand that a call for Users willing to test code has been made. Along with one other in that group and considering my ongoing participation in the openSUSE Technical Help forums, the two of us are proposing building a state of art ecosystem of Users willing to test and assist in developing Code. Please take a few minutes to read the proposal I've posted at the following URL, the website is set to be accessible only by those who know the URL (it's not supposed to be publicly searchable) and although it's visible anonymously, editing requires logging in with a Google account. https://sites.google.com/site/projectcodedev/ Do be forthright with any opinion about the proposed Project, myself and anything else, I will take any comment constructively and after many years have seen and experienced just about anything that can and has been said in unmoderated as well as moderated forums. If the Proposal is deemed unsupportable, I might be disappointed but can accept that as well. :) Thank you, Tony Su -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

4 6

ambassador reports
by Jos Poortvliet 01 Apr '11

01 Apr '11

Hi boosters, The marketing team has been brainstorming on how to give ambassadors a tad more attention in openSUSE; motivate them to make a bit more noise; and reward them for what they do. Now we have a few ideas, but for one, we thought it might make sense to use connect. Yes, it could probably be done via the wiki and other ways but I know you guys have a hammer and might see this as a nail :D *what is the problem* the ambassadors _sometimes_ create event reports. We want those reports for several reasons: - to have an idea of what they are doing - to measure how much we do - to motivate others - to SHOW what we do Unfortunately, not so many event reports are made although we're fairly sure many events have openSUSE attendance. This is due to several issues. *First*, not all ambassadors are so connected to us - many are not 'official ambassador' or their English skills are minimal and they are not internationally involved. I will send a follow-up mail with ideas on how to solve that. *Second*, filling in an event report on the wiki is not exactly easy for many. Some send one by mail - which is fine but leaves little record. *Third*, the reports receive little visibility. They are mentioned somewhere in the weekly news if you're lucky and of course on the marketing ML, but that's it pretty much. Numbers in it are not saved, we don't realy do anything with it as there is no real easy record. *The solution?* Ideally, the reports would end up in a central place, some database... And ideally, they would be connected to the ambassadors - so they can build up a trackrecord of events they have visited. Once we have this we can also show reports on eg news.o.o in a feed box on the side for example, or on our homepage. We can analyze and use statistics (for promo), promote events, do monthly articles - all kinds of things. We have an events page on en.opensuse.org/openSUSE:Ambassador_events which suffers from similar issues - most people don't create a page because it is not easy and not localized. *connect.o.o* In short. We wonder - would Connect not offer a much better way of handeling events, event reports and the like? Would it not offer a better place for ambassador user accounts (with associated event reports as track records)? Culd it offer an easy place for ambassadors to add info for an event and afterwards add a report & pictures which we can then display in the planet feed (localized, if needed)? In case you think this is relevant, chuck and manu might have some time to help with this both in 'how to do it' (I would also love to think abou that) and the doing itself. Cheers, Jos

1 1

week report #13
by Thomas Schmidt 01 Apr '11

01 Apr '11

What was up this week: - software.o.o: getting rid of flags for languages, use text - wiki: working on content and bugs - canterbury distribution - managing gsoc, have a good student application in melange now - moved office 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 1

Re: Fw: [opensuse-boosters] Proposal for Building, Managing Code Testing Ecosystem
by Bernhard M. Wiedemann 30 Mar '11

30 Mar '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Date: Mon, 28 Mar 2011 10:47:59 -0700 > From: Tony Su <tonysu(a)su-networking.com> > To: opensuse-boosters(a)opensuse.org > Subject: [opensuse-boosters] Proposal for Building, Managing Code > Testing Ecosystem > > > Hello Group, > > I was informed that this was the best place to submit a rather large > and potentially influential openSUSE project. > > Through Bryen and the openSUSE marketing group, I came to understand > that a call for Users willing to test code has been made. > > Along with one other in that group and considering my ongoing > participation in the openSUSE Technical Help forums, the two of us are > proposing building a state of art ecosystem of Users willing to test > and assist in developing Code. > > Please take a few minutes to read the proposal I've posted at the > following URL, the website is set to be accessible only by those who > know the URL (it's not supposed to be publicly searchable) and > although it's visible anonymously, editing requires logging in with a > Google account. > > https://sites.google.com/site/projectcodedev/ > > Do be forthright with any opinion about the proposed Project, myself > and anything else, I will take any comment constructively and after > many years have seen and experienced just about anything that can and > has been said in unmoderated as well as moderated forums. If the > Proposal is deemed unsupportable, I might be disappointed but can > accept that as well. > > :) > > Thank you, > Tony Su Hi, I have been driving quite some part of the testing efforts for 11.4 (sometimes jokingly calling myself "HobbyQA") In particular, I created http://openqa.opensuse.org/ on a dedicated machine in Nuremberg (because it needs hardware virt and plenty resources). This helps a lot to auto-maintain the factory-tested repo as something that will not be arbitrarily broken and thus is better suited for human testers than openSUSE-Factory. for testing coordination/communication there is atm the ML http://lists.opensuse.org/archive/opensuse-testing/ and wiki http://en.opensuse.org/openSUSE:Testing and IRC meetings http://en.opensuse.org/openSUSE:Testing_meeting and the new social thingy: https://connect.opensuse.org//pg/groups/12174/opensuse-testers/ in principle, there is also testopia on bugzilla.novell.com, but until now it was not really put to good use - possibly because of certain shortcomings in the setup which we can not influence. I read most of the proposal pages and was thinking, that Linux Distributions do not do "Waterfall" model much, because there are a) rarely detailed specs upfront, b) design often happens as needed during implementation, c) verification is rarely comprehensive or specific to new code d) there are several pre-releases allowing for feedback and subsequent improvements (even Factory(-tested) providing daily updates) of course, distributions also mainly consist of upstream project code with their own devel/release cycles and methods. However, some way to better coodinate testers and testing would be nice. Giving credits and/or rewards to testers is also a good thing to do. And there is more room for improvement. Ciao Bernhard M. - -- you have to know your goal for it makes it much easier to reach -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk2R40oACgkQSTYLOx37oWRlkwCbBZc/fgUxJDvAa9e+5j8AjXBt 6rAAoMSwq+fBXvT3Fh4EWtVqPUhIVzg2 =ELSM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org

2 1