August 2012 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] REMINDER - August 20th is the last day to apply for openSUSE Conference Travel Support
by Izabel Valverde 19 Aug '12

19 Aug '12

Hello all, August 20th is the last day to apply for sponsorship support to attend openSUSE Conference. Please read http://news.opensuse.org/2012/08/10/opensuse-conference-is-coming-sponsorsh… How to apply http://en.opensuse.org/openSUSE:Travel_Support_Program Best regards, -- Izabel Valverde openSUSE Travel Support Program http://en.opensuse.org/openSUSE:Travel_Support_Program http://news.opensuse.org/ -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] fdisk project - GSoC weekly report 13
by Davidlohr Bueso 19 Aug '12

19 Aug '12

Hi, This week, with help from Petr, and I have been going over the GPT implementation for fdisk. Mostly dealing with newly found bugs and test cases. So far everything looks to be going well and will probably be sent for upstream revision in a couple of days. This final week I plan to continue testing and, once satisfied, write some automatic regression testing based on the scsi_debug kernel module. Thanks, Davidlohr -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] 12.2 Public Release tasks: call for coordinators (3/3)
by Agustin Benito Bethencourt 19 Aug '12

19 Aug '12

Hi, This is the last mail of this series. A. Introduction In order to get the biggest possible impact for our Release some tasks needs to be accomplish.We in SUSE will take care of some of them and your input will be needed in order for other to happen. Since we do not have much time, coordination play a key role at this point. So we would like to propose the following. B. Proposal In the 12.2 Public Release Action Plan wiki page[1] you can see some tasks that we'll need your input in order to happen. In the process of getting input for the Release Process Document, some other might arise. We believe the best way to coordinate efforts will be to have one coordinator for each task/group of people that put effort in each task. At SUSE we have done the same, as you can see in the Organization Chart. This way we make sure the communication is efficient and each group can organize as they wish. Mailing lists, works in general, but for tight deadlines and having so many people involved in this process, we think a person acting as point of contact is a good improvement. C. Example For example: If three people contribute doing artwork, it would be great if one of them works as contact for this release process, making sure the communication among the artwork contributors and other teams involved, from SUSE and the community, works. D. Coordination Ludwig Nussel will add the contact data of that person in the wiki and will make sure that we all are aware of the tasks that need to be done and the deadlines/constrains we have. He will be our "Schedule Master" (he hates this role :-) ). E. Final Note We do not expect to be perfect this first time, but there is room for improvements during following releases. We take this as a learning process. [1] 12.2 Release Action Plan: http://en.opensuse.org/openSUSE:Public_Release_Action_Plan saludos -- Agustin Benito Bethencourt openSUSE Team Lead at SUSE abebe(a)suse.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 2

[opensuse-project] 12.2 Road Map - Public Release Schedule (2/3)
by Agustin Benito Bethencourt 17 Aug '12

17 Aug '12

Hi, last week the openSUSE Team at SUSE had a meeting to discuss the proposal for openSUSE 12.2 Release schedule made by the Release Manager. This proposal was supported past Tuesday in a coordination meeting where managers from SUSE involved in the process participated. Please check the Road Map[1] wiki page to get the confirmed dates: Basically are: * Technical contributions freeze: August 24th 13:00 UTC * Gold Master Declaration: August 30th * Release date: September 5th 12:00 UTC Please spread the word about the dates so our contributors now them. [1] Road Map: http://en.opensuse.org/openSUSE:Roadmap saludos -- Agustin Benito Bethencourt openSUSE Team Lead at SUSE abebe(a)suse.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Release Process Action Plan (1/3)
by Agustin Benito Bethencourt 17 Aug '12

17 Aug '12

Hi, this is the first of three e-mails related with 12.2 Release. It deals with the diagram done about the Release process. A. Background We have invest some effort in talking internally to the people from different departments involved in openSUSE Release process to define the actions that each one of them take to make each release happen. We have concentrate in those that are currently happening or will need to take place the following weeks. We having consider most of those that take place during the Candidate release process or before that. We also haven't consider promotion activities that we do after each release. But above all, we haven't consider yet most of the work you guys do. Our team is willing to receive you input, so we can analyze together how to approach the next release trying to be even more efficient and engage even more people. >From SUSE side, we have detected already some points of improvements and more will arise the following weeks. We area specially interested in those actions that we currently we do internally and can be opened and those that already are, but for several reasons, the community cannot help us on. This process is part of the strategy of empowering more and more, little by little, the community in key aspects for the project. B. The documents We have used a simple tool (planner) to make a simple Gantt diagram with the tasks. The goal at this point is just to have a picture of what needs to be done and who is responsible for doing it. We will go further in following releases, adding time lines (start and finish dates) and effort (manpower involved) where is possible. We are already using this document internally for managing the tasks that we are currently doing. C. Why we think your input is needed This document must be accurate to be effective. Right now it only contains SUSE vision, which is partial, of what our release process is. We want to include those tasks you do or you participate on so it becomes useful also for others. We believe it can become a key element in the release process coordination in the near future. It is also an opportunity of defining the tasks we will be doing the following weeks to make openSUSE 12.2 happen. Please check the openSUSE 12.2 Release Process[1] wiki page for details. D. How to contribute We have identified some groups of people that work on the Release in an organized way and some other less organized. Some examples could be: * Editors * Translators * Technical contributors (organized around opensuse-packaging(a)opensuse.com) * Ambassadors * This contributors organized around the marketing mailing list * Artwork team There are probably several others we are missing. Since we are in the middle of the Release process, it would be great is those groups name a coordinator or one person from each group steps up and give us some input about the tasks they do during the release. Please feel free to edit directly the wiki page and add to the table the tasks. Ludwig Nussel[2], one of the new engineers on the openSUSE Team at SUSE will process and include you input in the document. If you contribute but are not organized in a group or simply prefer to use mail instead of editing the wiki, post what you do during the release process in this mailing list. We will discuss and include your input in the document. It doesn't matter if you work on the technical side, marketing, artwork, promotion.... all counts. It is extremely important that you include as soon as possible those tasks directly related with the Public Release phase in the 12.2 Public Release Action Plan table[3], since we want to make sure we don't skip them for 12.2 Release. [1] Release Process wiki page: http://en.opensuse.org/openSUSE:Release_process [2] Ludwig Nussel http://en.opensuse.org/openSUSE:Release_process#Organization_chart [3] 12.2 Public Release Action Plan: http://en.opensuse.org/openSUSE:Public_Release_Action_Plan Saludos -- Agustin Benito Bethencourt openSUSE Team Lead at SUSE abebe(a)suse.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] A simple report of preparation for COSCUP
by Max Lin 16 Aug '12

16 Aug '12

Hi All, You might known we've got COSCUP at 8/18 - 8/19 - and the complete official program list already announced, you can found it at http://coscup.org/2012/en/program/. This mail just want to let you know what is the current state of preparation for COSCUP. COSCUP, the largest FLOSS conference organized by local communities in Taiwan, and it keeps grow up. According to statistics from the registration website, this year, COSCUP will over 1200 participants! Collaboration KDE and openSUSE will collaboratively organize a full two-day track at the COSCUP this year. This time we bring a lot of exciting content, Will Stephenson and Aaron Seigo will be cooperation in the keynote talk; Yin-Yyun Qiao who work on Qt at Nokia will talk about new features of Qt5; Michal Chang will introduce what changes from openSUSE 12.1 to 12.2; others topics are cover KLyDE(lightweight KDE pattern), OBS, Akonadi, maintenance model, etc. It sounds nice, isn't it? openSUSE Team & Community COSCUP 2012 is the first conference that openSUSE Team supported since rename from Boosters Team. Will Stephenson and mine to participate COSCUP this year, local community and us would host a booth and brings talk, the important one is we will host a BoF at first night, chatting with local community and obtain the feedback. About booth, we prepared some cool stuff, ex. T-Shirt[1], flyers, stickers, Geeko doll, etc. If the entire venue can see Green Geeko, that will be very cool! Above is what we preparation for COSCUP, I will send a simple summary report after end of COSCUP(with pictures :). See you there and sorry for my poor English! Cheers, Max [1] http://goo.gl/Hj8id - Thanks Ben who are t-shirt' model. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Upstream Tracker - Weekly Update
by N B Prashanth 16 Aug '12

16 Aug '12

Hi, Last week a lot of things have been updated in the project. 1. The python backend now uses multiple threads to process records. 2. Added paper trail support for reverting to older versions of the record. 3. Added record history table showing the details of record changes. 4. Added Devise for user authentication (sign up/sign in). Applicable for reverting and deleting records. 5. Updated and improved DEHS support. 6. Added multiple branch support (currently i/p and o/p are in CSV format). 7. Several small UI enhancements. What's left : 1. Documentation on setting up and working with the upstream tracker with examples on using the API. 2. Add a ToDo list in the documentation which indicates possible future enhancements. 3. Multi branch support should return multiple branch details in proper XML rather than in CSV format. -- Regards, N.B.Prashanth -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [gsoc] osc2 client - summary of week 12
by Marcus Hüwe 15 Aug '12

15 Aug '12

Hi, here’s a small summary of the 12th (coding) week. The last week I continued the work on the new user interface. As a result the "request" command is more or less implemented. Yesterday I pushed the current code and it's also possible to play around with it: - checkout the code [1] - cd osc2/osc/cli - export PYTHONPATH=/path/to/osc2 - python cli.py -h (for more information) Example: In order to list a request it is sufficient to run "python cli.py request api://your_project" (Note: all https requests are _insecure_ - so far the certificate etc. is not checked). Some implementation details: In my last mail/post I described how a new (sub)command can be specified so I'll leave out the details here. In the following I'll shortly explain how the arguments specified by the user at the commandline are passed to a function (which does the actual work - like listing the requests). class RequestList(CommandDescription, Request): """ ... """ cmd = 'list' args = 'api://project?/package?' opt_user = Option('U', 'user', 'list only requests for USER') func = call(request.list) As we can see the project and package parameters are optional. After the parsing process a so called "info" object is returned which encapsulates the specified arguments. Assume the user runs "request list api://test_prj" then the info object has the following attributes: info.apiurl = <the default apiurl> info.project = 'test_prj' info.package = None The question is how can we pass this data to the request.list function? A simple (and naive) approach would be to simply pass the "info" object to the request.list function that is "list" has the following signature "def list(info)". As a consequence inside the method we always have to use "info.project", "info.package" etc. which is a bit awkward - at least for parameters which are quite frequently used in the method definition. So it would be nice if there's a way to pass frequently used parameters directly to the method (that is they're declared as formal parameters in the method definition) and infrequently used parameters can still be accessed via the info object. Exactly like this it is currently implementend in osc2. So the following signatures would be correct for our example: def list(project, package, info) def list(project, package, user) def list(project, package, user, info) def list(project, info) def list(info, project) def list(project) # using the info object is not mandatory def list() # quite useless... ... Invalid signatures: def list(prj, pkg, info) def list(foo, info) ... So it is up to the developer how to define the signature of the request.list function - it is not completely dictated by osc:) Marcus [1] https://github.com/openSUSE/osc2 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] GSoC: AppStream / Software-Center project #8
by Matthias Klumpp 15 Aug '12

15 Aug '12

Hi! Sorry for the late report this time (since I switched to weekly reports), but I had a crazy time the last days and haven't had the time to write this report. Stuff dome the last week: * Wrote some more documentation about AppStream stuff * Discussed the AppStream index library, we now have very concrete plans * Tried to track down a Zif bug with Richard - I need this Zif bug solved to continue testing the SC properly, so unfortunately this stuff took lots of time and isn't finished yet * More SC madness: Added some more code to make using the SC easier, found some more things to port to the new API * Various improvements on the SC Unfortunately, because testing is very difficult, I'm not really fast with the SC stuff. In a few days I have to write a important exam again, so I will now focus on minor improvements and changes, which don't break the SC much and might produce other difficulties. (This was planned anyway, since we're now past the suggested-pencils-down date) As always, if you have questions, ask! I'll write a complete report about the stuff I've done after firm 'pencils down' date as a blogpost - there'll also be a video inside to show you how the SC works on other distributions, because it's still hard to set-up. I hope I can do as many improvements as possible before. Cheers, Matthias -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] GSoC: AppStream / Software-Center project #7
by Matthias Klumpp 14 Aug '12

14 Aug '12

Hi! Work done during the last week: * Discussed writing a libappstream with developers of other Software-Centers, which will allow accessing the AppStream-DB via an easy GObject-based interface. This will allow us to have all SC projects agree on a common DBagreement ("standard") which would be the AppStream database. All like the idea, so I added this to my post-SoC-TODO - some talking still has to be done. * Finished PackageKit parallelization, the most important part of my work! - wrote remaining unit tests - added lots of documentation and a extended the porting-guide for PackageKit backends - tested with Zif and Aptcc backend * PackageKit 0.8.3 release with all changes upstream, released today! :-) * Run some performance tests on Fedora * Added a whole bunch of improvements to the SC code, including some bugfixes - E.g. we no use the more advanced PkTasks object for some actions now (where it makes sense) - Fixed some crashes - Adjusted to new PK 0.8.x API - Directly connect to the AppStream database, so we can Resolve() as many packages as possible * Unfortunately, the Zypper backend of OpenSUSE is not yet ready * Experienced some new problems, details below I also had a meeting with people from OpenSUSE/SUSE to talk about what is necessary to get Software-Center support in OpenSUSE. It was a very productive meeting, and I hope you'll see the results later. For now, I will create a step-by-step plan about what needs to be done to make AppStream/SC work in any distribution. I already have some drafts for it (notes I wrote down during my work on the AppStream DB) and will publish the list this week. Also, the PK backends are in a not-so-great shape, which makes testing the SC really, really hard and annoying. This will become better soon, but I don't think it will work in time with my SoC. So I will probably not have a usable SC and the end, but I'll have a SC which will work good as soon as PackageKit backends are fixed. The remaining time I'll try to squash as many annoying bugs I can find and make the SC work well enough for basic testing. To get a great and usable project, I'll have to invest some more time after the SoC, which I'll do. These are the recent changes/findings, I'll keep you updated! As always if you have questions, feel free to ask! Cheers, Matthias -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

[opensuse-project] How does the decision making progress is called
by Togan Muftuoglu 13 Aug '12

13 Aug '12

Hi, In a recent mail to opensuse-factory [1] , regarding the implementation of Secure Boot for openSUSE - a proposal for the coming openSUSE release here is what Andreas wrote "Based on the feedback on this mailing list as well on opensuse-project, this is a clear "go" for the proposal." Now let me begin by stating the proposal is fine, and I am in favor of it. Nevertheless, the way "clear go " is defined makes me wonder, if the community is a follower or the leader. I thought the poll system was to include the community in situations like this, giving the opportunity to be involved in the decision process. If what has been preached is not practiced then what does opensuse member system stands for other than giving the email, irc cloaking and similar things. Togan http://lists.opensuse.org/opensuse-factory/2012-08/msg00294.html -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

10 14

Re: Fwd: Re: [opensuse-project] UEFI Secure Boot
by Greg Freemyer 11 Aug '12

11 Aug '12

On Fri, Aug 10, 2012 at 8:59 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > > > On Fri, Aug 10, 2012 at 8:25 AM, Basil Chupin <blchupin(a)iinet.net.au> wrote: >> >> On 10/08/12 19:44, Vojtech Pavlik wrote: >>> >>> On Fri, 10 Aug 2012 18:59:26 +1000, Basil Chupin wrote: >>> >>>> My question is: what would happen when one should use - as I did today - >>>> a bootable CD like System Rescue Disc? (I am guessing that if this were >>>> the openSUSE installation DVD then it would have some code in it which >>>> would allow it to boot without problems.) >>> >>> The openSUSE installation DVD will of course boot, having all the >>> proper signatures that you needed to install the OS in the first place. >>> And it will be booting the kernel present on the DVD, which is signed by >>> the SUSE key. >>> >>> In case you wanted to create your own rescue DVD that'd be booting >>> custom kernels, that'll be possible, too, using the same shim loader >>> you'll be able to enroll your MOK, or just use one if already present on >>> the system. >> >> >> Thank you for confirming what I suspected. >> >> My apologies for using the wrong name for the CD I mentioned above, >> however I was wondering how a bootable CD such as the SystemRescueCD which >> comes from systemrescuecd.org >> (http://www.sysresccd.org/SystemRescueCd_Homepage) and similar bootable >> media, would boot under this UEFI process? >> >> >> BC >> It was my impression that most UEFI bios solutions would not test CD boot media. Forcing CD/DVD boot media to be signed with a well known key would end the use of CD/DVD boot media for all but Microsoft I suspect. (ie. How does the initial openSUSE install get on to a box if install media doesn't have a way around the signing/validation rules.) The same will also need to apply to USB boot media I hope. Greg -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 5

Re: [opensuse-project] UEFI Secure Boot
by Basil Chupin 10 Aug '12

10 Aug '12

On 10/08/12 22:59, Greg Freemyer wrote: > > > On Fri, Aug 10, 2012 at 8:25 AM, Basil Chupin <blchupin(a)iinet.net.au > <mailto:blchupin@iinet.net.au>> wrote: > > On 10/08/12 19:44, Vojtech Pavlik wrote: > > On Fri, 10 Aug 2012 18:59:26 +1000, Basil Chupin wrote: > > My question is: what would happen when one should use - as > I did today - > a bootable CD like System Rescue Disc? (I am guessing that > if this were > the openSUSE installation DVD then it would have some code > in it which > would allow it to boot without problems.) > > The openSUSE installation DVD will of course boot, having all the > proper signatures that you needed to install the OS in the > first place. > And it will be booting the kernel present on the DVD, which is > signed by > the SUSE key. > > In case you wanted to create your own rescue DVD that'd be booting > custom kernels, that'll be possible, too, using the same shim > loader > you'll be able to enroll your MOK, or just use one if already > present on > the system. > > > Thank you for confirming what I suspected. > > My apologies for using the wrong name for the CD I mentioned > above, however I was wondering how a bootable CD such as the > SystemRescueCD which comes from systemrescuecd.org > <http://systemrescuecd.org> > (http://www.sysresccd.org/SystemRescueCd_Homepage) and similar > bootable media, would boot under this UEFI process? > > > BC > > It was my impression that most UEFI bios solutions would not test CD > boot media. > > Forcing CD/DVD boot media to be signed with a well known key would end > the use of CD/DVD boot media for all but Microsoft I suspect. > > (ie. How does the initial openSUSE install get on to a box if install > media doesn't have a way around the signing/validation rules.) > > The same will also need to apply to USB boot media I hope. > > Greg OK, interesting. Sorry for being 'dense' on this matter but a bootable disc like SystemRescueCD is a Linux bootable disc which loads a system with a kernel and contains many tools to be able to access and alter an existing system installed on an HDD. I even used this disc to remove encryption from my /home directory when an update to openSUSE 12.1 went wrong. Would such a disc be affected by this UEFI? BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.0-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 5

Re: Fwd: Re: [opensuse-project] UEFI Secure Boot
by Vojtech Pavlik 10 Aug '12

10 Aug '12

On Fri, 10 Aug 2012 18:59:26 +1000, Basil Chupin wrote: > My question is: what would happen when one should use - as I did today - > a bootable CD like System Rescue Disc? (I am guessing that if this were > the openSUSE installation DVD then it would have some code in it which > would allow it to boot without problems.) The openSUSE installation DVD will of course boot, having all the proper signatures that you needed to install the OS in the first place. And it will be booting the kernel present on the DVD, which is signed by the SUSE key. In case you wanted to create your own rescue DVD that'd be booting custom kernels, that'll be possible, too, using the same shim loader you'll be able to enroll your MOK, or just use one if already present on the system. -- Vojtech Pavlik Director SuSE Labs -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 3

[opensuse-project] update about openSUSE Team at SUSE
by Agustin Benito Bethencourt 10 Aug '12

10 Aug '12

Hi, As you probably know, the team within SUSE supporting the openSUSE community is going through some changes. To begin with, I have joined SUSE as Team Leader [1] and we are hiring [2] to fill other vacant positions. Secondly, to reflect the team's increased responsibility for openSUSE within the company, we've dropped the term 'Boosters' to become simply 'the openSUSE team'. We are concentrating our efforts on three main tasks. a.- 12.2 Release b.- openSUSE Conference and openSUSE Summit (especially the first one since it is larger) c.- Internal reorganization a.- 12.2 Release Those of you involved in the technical side are already aware that Ismail Doenmez is now part of the (virtual) Release Team, assisting Coolo with release management. This team is working alongside you on having the best possible openSUSE 12.2 release from the technical point of view. The release process of openSUSE, like any other complex integration process, requires the participation of people from different teams and expertise areas. An open project combines community, SUSE and other professional contributions as well as external involvements like media production. This makes the management/coordination perspective even more complex. One of the things we think is needed is to update the documentation related with the release. We thought it was the first step to go through the entire process, analyze it and improve it for future releases. So, we are talking internally with the people involved in previous releases collecting what they did, trying to have a simple document as an early result. Yes, this is preventing some of us on focusing on "real release work" for a few days, but we hope that will save us time in the near future. Whatever we do can only ever be partial if we do not take account of the huge amount of work on openSUSE done by the community. So next week, we will publish a draft describing the release processes, so that you can give us input for an open release process. The goal is not to have a perfect document this first iteration, but a useful document. This draft will include the actual 12.2 release date. As you can see, we are aiming to meet the adjusted schedule. b.- oSC'12 We will give you some update about the openSUSE Conference (from our perspective) later this month. Please ping any of the team members if we haven't done it by the end of August. Obviously you can ask Michal Hrusecky for details any time. c.- Internal reorganization SUSE is concentrating the professionals that work full time on openSUSE around a single team. So in addition to the technical support we usually provided, this team will also provide community, marketing and economic (coordination) support to the Free Software project. We will also serve as link to the service team, who takes care of the infrastructure, and other teams within SUSE which work is directly on indirectly related to the community. The goal of this new configuration is: 1.- Simplify management and coordination. 2.- Increase community engagement. 3.- Improve efficiency. We expect to provide a clearer view of how these changes can be executed during the openSUSE Conference. The idea right now is to use the event to collect as much input from you as possible. we will close our Action Plan afterward. [1] http://lists.opensuse.org/opensuse-project/2012-06/msg00258.html [2] http://www.suse.com/careers Saludos -- Agustin Benito Bethencourt openSUSE Team Lead at SUSE abebe(a)suse.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 3

[opensuse-project] larger openSUSE deployments?
by Ludwig Nussel 10 Aug '12

10 Aug '12

Hi, I'm currently investigating whether and how openSUSE is used in larger deployments. Does anyone know someone who manages like let's say 30 or more openSUSE machines at once? I'm interested in e.g. what tools are used in such a scenario and what rough edges in the distro we maybe have that could be improved. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

13 19

Re: [opensuse-project] Getting OpenSUSE community together
by Richard Brown 10 Aug '12

10 Aug '12

> How does the idea sound like to you? Interesting, I do like the idea of better exposing the tools and facilities we already have in the hope that it will encourage their use. > Your always thoughtful ARTWORK TEAM Did I miss an artwork team meeting where we agreed on this idea? If not, I don't think you should be signing in the name of the team - not exactly the best foot for community relations.. Richard / Ilmehtar on IRC >>> Eugene Trounev 08/06/12 9:34 PM >>> Dear OpenSUSE, As a part of an ongoing effort to make our distro better visually and user experience-wise we have come to a realization that things would be much easier if we had some sort of a unified community tool (or a set of those) to help us widen our outreach. We are aware that there is already SUSE Connect, as well as an abundance of various mailing lists and IRC channels. However, few of our users actually know about those, or actively use them. So the idea so far is to make a desktop application which would ultimately bind all those services together into a sort of a single SUSE account (just like the service available in by Ubuntu, and OSX). So far this is just an idea and we need your input to see just how far can we take this and just what exactly we should be looking into in terms of functionality. So the brief description so far is this: "A desktop application connecting the whole of openSUSE fandom into a single network in order to widen the community, lower the communication and contribution barriers and add a unique twist to openSUSE ecosystem where every new user has an opportunity to share and communicate with other openSUSE users." Basically this should be as simple as integrating all our existing social services (Open Fate, SUSE Connect, mailing lists and IRC canals into a single easy to use "Control Centre". How does the idea sound like to you? What would be advantages of this effort? What would be the drawbacks of it? Would you create yet another account for our openSUSE social services? Your always thoughtful ARTWORK TEAM-- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

5 5

[opensuse-project] Re:
by Single Dating Online 09 Aug '12

09 Aug '12

Meet Hot Singles Online Largest Casual Dating Site In The World Speed Dating & Hookup Tonight No Cost To Join Now! http://hailey91.info/goto.php You will not get anymore of our emails if you go here: http://natalie555.info/unsubscribe.php?email=opensuse-project@opensuse.org This email and any files transmitted with it are personal and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. 1502 Redfield Road, Riverside, California, CA, 92507 USA -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Getting OpenSUSE community together
by Eugene Trounev 08 Aug '12

08 Aug '12

Dear OpenSUSE, As a part of an ongoing effort to make our distro better visually and user experience-wise we have come to a realization that things would be much easier if we had some sort of a unified community tool (or a set of those) to help us widen our outreach. We are aware that there is already SUSE Connect, as well as an abundance of various mailing lists and IRC channels. However, few of our users actually know about those, or actively use them. So the idea so far is to make a desktop application which would ultimately bind all those services together into a sort of a single SUSE account (just like the service available in by Ubuntu, and OSX). So far this is just an idea and we need your input to see just how far can we take this and just what exactly we should be looking into in terms of functionality. So the brief description so far is this: "A desktop application connecting the whole of openSUSE fandom into a single network in order to widen the community, lower the communication and contribution barriers and add a unique twist to openSUSE ecosystem where every new user has an opportunity to share and communicate with other openSUSE users." Basically this should be as simple as integrating all our existing social services (Open Fate, SUSE Connect, mailing lists and IRC canals into a single easy to use "Control Centre". How does the idea sound like to you? What would be advantages of this effort? What would be the drawbacks of it? Would you create yet another account for our openSUSE social services? Your always thoughtful ARTWORK TEAM-- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

12 19

[opensuse-project] Upstream Tracker - Weekly Report
by N B Prashanth 08 Aug '12

08 Aug '12

Hi, Progress last week: 1. Implemented DEHS import. DEHS watch files can now be used to track upstream versions. 2. Optimized CustomURL support. Supports HTTP, FTP and Sourceforge. 3. Added Multithreading and Job Queue support. 4. Added paper trail support with a history table for each record. Each row displays a previous version of the record and contains a revert button. What's left: 1. Security. Reverting and deleting records should only be done by site administrators. However, anyone can add new records and update existing records. 2. Minor UI updates. 3. Documentation. -- Regards, N.B.Prashanth -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [gsoc] osc2 client - summary of week 11
by Marcus Hüwe 07 Aug '12

07 Aug '12

Hi, here's a small summary of the 11th (coding) week. Last week I worked on implementing the new commandline interface. While doing so I faced several "issues": * How to combine argparse and our oscargs url-like syntax? Basically we have to run our oscargs parser on the result which is returned by argparse.ArgumentParser's parse_args method. The problem is that both parsers have a different "syntax" that is using a naive approach will lead to some redundancies (we specify the ui twice: one time for argparse and one time for oscargs). In order to avoid this we need some "interface" to which the oscargs syntax is passed and which configures the argparse parser accordingly. * How to support custom commands? We also have to provide an "easy" way to specify custom commands. Additionally it might be handy if existing commands can be enhanced (either by adding additional options etc. or by adding a new subcommand etc.). The best would be if the user simply drop his/her plugins in a specific directory and osc will scan this directory and use the new plugins/commands. * Specifying the ui programmatically is somehow confusing/cluttered. It would be much better if the ui can be specified in a more "declarative" way without the syntactic "overhead" (well that's a bit exaggerated) which is needed to configure the parser. Additionally it would be nice to have a convenient way to specify a multi line description for a command (hardcoding the str into the source makes the code "harder" to read). Finally I ended up with a small DSL which can be used to specify the ui in a "declarative" way (the initial idea + syntax is taken from the django framework (see [1])). Example: Assume we want to implement a request command which consists (for the sake of simplicity) of 2 subcommands "list" and "accept". This can be specified like the following: # file: osc/cli/request/ui.py class Request(CommandDescription, OscCommand): """Show and modify requests.""" cmd = 'request' class RequestList(CommandDescription, Request): """List requests. By default open requests for a specific project or package will be listed. Examples: osc request list api:// osc request list api://project osc request list api://project/package """ cmd = 'list' args = 'api://project?/package?' opt_user = Option('U', 'user', 'list only requests for USER') opt_group = Option('G', 'group', 'list only requests for GROUP') opt_state = Option('s', 'state', 'list only requests with state STATE', choices=['new', 'review', 'accepted', 'revoked', 'declined', 'superseded'], action='append') func = request_list class RequestAccept(CommandDescription, Request): """Accept a specific request. ... """ cmd = 'accept' args = 'api://reqid' func = request_accept In order to add the request command it is sufficient to add an import osc.cli.request.ui statement to the main cli module. This produces the following output: marcus@linux:~/osc2/osc/cli> python cli.py request -h usage: cli.py request [-h] {list,accept} ... Show and modify requests. positional arguments: {list,accept} list List requests. accept Accept a specific request. optional arguments: -h, --help show this help message and exit marcus@linux:~/osc2/osc/cli> and marcus@linux:~/osc2/osc/cli> python cli.py request list -h usage: cli.py request list [-h] [-s {new,review,accepted,revoked,declined,superseded}] [-G GROUP] [-U USER] api://project?/package? List requests. By default open requests for a specific project or package will be listed. Examples: osc request list api:// osc request list api://project osc request list api://project/package positional arguments: api://project?/package? optional arguments: -h, --help show this help message and exit -s {new,review,accepted,revoked,declined,superseded}, --state {new,review,accepted,revoked,declined,superseded} list only requests with state STATE -G GROUP, --group GROUP list only requests for GROUP -U USER, --user USER list only requests for USER marcus@linux:~/osc2/osc/cli> How does it work? First of all each class which defines a command or subcommand has to inherit from class "CommandDescription". If a subcommand is to be defined it also has to inherit from the "parent" command (that is in our example "RequestList" and "RequestAccept" inherit from class "Request" (which in turn inherits from class "OscCommand" (from this class all toplevel commands have to inherit))). In short: with the help of the inheritance hierarchy it is possible to define a command <- subcommand hierarchy. Note: actually the classes "RequestList" and "RequestAccept" only inherit from "CommandDescription". The "parent" command base class is only needed for a "marking" purpose (it is filtered out with the help of a metaclass when the concrete class is "constructed" - I'll leave out the details for now and may write a dedicated blogpost about it). Now the remaining task is to define and implement the commands (note: we will definitely not finish the project on the "suggested pencils down" date and use the week until the "firm pencils down" date for coding...). Marcus [1] https://docs.djangoproject.com/en/1.4/topics/db/models Here's a small example how to modify an existing command: # plugins/myrequestaccept.py from osc.cli.description import Option import osc.cli.request.ui class MyRequestAccept(osc.cli.request.ui.RequestAccept): # add a new option opt_foo = Option('f', 'foo', help='foo option') This leads to marcus@linux:~/osc2/osc/cli> python cli.py request accept -h usage: cli.py request accept [-h] [-f FOO] api://reqid positional arguments: api://reqid optional arguments: -h, --help show this help message and exit -f FOO, --foo FOO foo option marcus@linux:~/osc2/osc/cli> -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] UEFI situation
by Chris Jones 07 Aug '12

07 Aug '12

17 55

[opensuse-project] [reminder] openSUSE Project Meeting tomorrow at 17:00 UTC
by openSUSE Meeting Reminder 07 Aug '12

07 Aug '12

Hello all, The biweekly project meeting will be held tomorrow at 17:00 UTC in #opensuse-project on freenode. Everybody is invited to join and participate! Find out what time the meeting will be in your timezone: http://timeanddate.com/worldclock/fixedtime.html?day=8&month=8&year=2012&ho… Agenda of the meeting: http://en.opensuse.org/openSUSE:Project_meeting#Agenda_for_the_next_meeting If you cannot participate and want a specific question to be answered during the meeting, please add your question to: http://en.opensuse.org/openSUSE:Project_meeting#Questions_Section Minutes and logs of previous meetings can be found at: http://community.opensuse.org/meetings/opensuse-project/ Thanks, -- openSUSE Meeting Reminder -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] fdisk project - GSoC weekly report 10
by Davidlohr Bueso 05 Aug '12

05 Aug '12

Hi, As mentioned in last week's report, this week I focused entirely on GPT, implementing the following features: - List partitions - Delete partitions - Write data to disk - Verify data integrity (header and partitions). Now I plan on working on adding partitions and looking into supporting hybrid MBRs. Thanks, Davidlohr -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Clossing of old bugs
by Carlos E. R. 02 Aug '12

02 Aug '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have had several bugs closed withing minutes, with a copy pasted excuse, because they are reported against 11.4 and 12.2 is coming. This is demeaning! Why on earth should I care and report bugs, if nobody is going even to read them! - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAlAasfEACgkQtTMYHG2NR9WjdQCffVDr3P8SZoKBAnH1V4nqo2c8 /TUAnj7JkitOnQU7jM8ymVLD/HYF7Flq =sbzB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 3