August 2012 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] How we will use the GSoC money
by Vincent Untz 18 Jul '24

18 Jul '24

Hi, (let's see how a public discussion about money goes :-)) The Google Summer of Code brings us great students, but also means that the openSUSE project will get $8000 (if I'm not mistaken) at the end of the summer. That's $500 per student. A while ago, I requested comments on my blog about what to do with the money, but didn't get any feedback. So I take this as "do what you feel is best", and this mail is about the plan. As a reminder, the main issue is that we will likely not have the openSUSE Foundation created in time for this. For instance, Google would like us to get some form filled before the end of June; this is not a mandatory timeline, but I think it shows that we won't be ready with the Foundation for that. The current plan is to give that money to another organization we feel close to, and I have two candidates in mind: - the Software Freedom Conservancy (http://sfconservancy.org/) it's a really nice org that provides a home for various cool projects (see http://sfconservancy.org/members/current/) and those projects help make openSUSE a great project. - the Desktop Summit (https://www.desktopsummit.org/) it's one of the biggest event this year, and this would help us have some more visibility (since we'd be sponsors, I guess). I'm sure they would welcome this to secure their budget. Note that an alternative solution would be to leave the money to Google for a future GSoC or similar program, but I feel it's better to use the money where it can make a difference today. Now, it's not too late to change the plan. If you have a better suggestion, please tell us. There's no need to argue forever about it, just explain why you think it's good. Keep in mind that if we cannot receive the money ourselves, this also means that we cannot use it to buy stuff for openSUSE. Pavol and I will take the final decision since we are the GSoC admins for openSUSE. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

22 38

[opensuse-project] download.opensuse.org IPV6 address breaks updates
by Gerald Pfeifer 15 Nov '13

15 Nov '13

I am seeing this with an openSUSE 12.1 system at home, and also a Factory system at work: % host download.opensuse.org download.opensuse.org has address 195.135.221.134 download.opensuse.org has IPv6 address 2001:67c:2178:8::13 And then, when running zypper patch or zypper up, I see Retrieving: repomd.xml [error] Download (curl) error for 'http://download.opensuse.org/update/12.1/repodata/repomd.xml': Error code: Connection failed Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable Alas, my provider nor that network at work support IPv6. Still, my system has IPv6 enabled since roaming around on different networks, IPv6 may be present, or even necessary there. (This does not happen all the time, sometimes if I retry a bit later the system uses IPv4 and everything works.) Now, is this just a setup problem and I should simply and unconditionally disable IPv6? Or are some parts of our update or network stack in need of some adjustments? For the time being, unless this is just me running into this, should we disable IPv6 on download.opensuse.org? Gerald -- Dr. Gerald Pfeifer <gp(a)suse.com> || SUSE || Director Product Management -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

12 41

[opensuse-project] Bugzilla requirements gathering exercise
by Will Stephenson 09 Sep '12

09 Sep '12

Following the recent thread [1] on opensuse-project about obstacles to the community's use of our shared bugzilla instance, SUSE has started an internal assessment of how we can improve things for community users, contributors, employees and enterprise customers - in defiance of the "we can't touch that part of the infrastructure" meme. To this end, I'd like to gather here information about your requirements. Some things I've pulled out of "Bugzilla account creation" and other places are: * Easy sign up ** Minimal user information required * Familiar branding * Working integrated login with other project web apps * Community visibility of bugs in openSUSE reported against SLE * Performance * Relating bugs to packages and maintainers * Package<->Bug relation * OBS<->Bugzillazilla relation * Tooling (eg Entomologist, integrated bug reporters like Dr Konqi) If you have any comments on these or on other topics, please add them here. I'm trying not to touch the Pandora's boxes of bug lifetimes, engineering responsiveness and mass-closing, but perhaps if we can make our Bugzilla more community friendly, it will attract more help to solve these. Will [1] http://lists.opensuse.org/opensuse-project/2012-08/msg00007.html -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

6 5

[opensuse-project] openSUSE 12.2 Release follow up
by Agustin Benito Bethencourt 03 Sep '12

03 Sep '12

Hi, this is a short summary of where we are and what is still left to do for this release process: Done or in progress * Gold Master declared. * Feeding mirrors with the Gold Master and extra isos * Promo DVDs ordered * Press kit in progress. Will be done (extracted from the Action Plan) * Finish the Highlight page and the Release announcement. * Once the Highlight page and the Release announcement are done (Monday), we will add them to the wiki. We will do this. * We would like to publish this for release the announcement and, if possible, the highlight page, in several languages, so the impact is bigger in places where English is not the mother tongue. On Monday (probably late) we will point translators to these pages in English so they have Tuesday to translate. This is not optimal, but at least it is an improvement. We will have more time in the next release. Max Lin, our team member in Taiwan, will be the link for this task. If any of you want to coordinate this, that would be great. We will be very busy doing other things. * On Monday afternoon we will try to put some effort into the social media promotion of the release. We will discuss with you a plan so we are partially organize on this. Many of you usually do promo through different social media so we want to make sure we know who you are, you have the contens you need to promote openSUSE and we do not miss any relevant channel. It could be nice also to experiment on social media in different languages. It would be very valuable if those of you willing to do promotion on Wednesday and following days help us here, specially in channels like FB or twitter, where many of us can contribute. Any idea that we can include in the planning, prepare on Tuesday (or even before if do not involve this team) and execute it during the Release day and the following days will be more than welcome. There are many many cool ideas we can try. We just want to make sure the ones we all choose are doable, they are coordinated (at least partially) and, very important, we can track them, so we can learn from them. * On Wednesday we will do the actions needed to make everything public, following the Action Plan that is on the wiki. If nothing really unexpected happens, we will have a good Release on Wednesday at 12:00 UTC. I would like to thank the current and former members of openSUSE Team at SUSE (former Boosters) for their work the last few months to get to this point, to SUSE for its support but, above all, to you, that work with passion to make this project possible. Now....let's make some noise. 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

5 8

[opensuse-project] Beautiful 1-Click Installer
by Saurabh Sood 02 Sep '12

02 Sep '12

Hi, Google Summer of Code has come to an end, and I am pleased to announce that the new 1-Click Installer is ready for testing by the community. While still requiring some work, it is still quite nifty, and simplifies the installation to a great extent. I will be working on the remaining tasks involved, and it would be awesome if I get feedback and how I could make it better. I welcome all feedback on the installer, and hope to make it even better in the future. I also take this opportunity to thank the entire organisation for the opportunity to work on this project, and my mentors, Cornelius Schumacher and Matt Barringer for guiding me throughout the course of the programme. OBS Repository : https://build.opensuse.org/package/show?project=home%3Asaurabhsood91&packag… Cheers, Saurabh Sood PS : I have not yet been able to handle the MIME types, so the application has to be run from the terminal, passing the ymp file as parameter. I will be working on this part soon. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 6

Re: [opensuse-project] Re: openSUSE 12.2 Release follow up
by Jim Henderson 31 Aug '12

31 Aug '12

On Fri, Aug 31, 2012 at 3:25 PM, Marcel Kühlhorn <susefan93(a)gmx.de> wrote: > attached you find the banners I came up with together with the artwork > team. Great, thanks, Marcel. What time do we expect to 'flip the switch' on the downloads becoming available? I'd like to make sure we switch the banner at around the same time (I think we can schedule it on our systems). Jim -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 2

[opensuse-project] 12.2 and GRUB2
by Basil Chupin 31 Aug '12

31 Aug '12

Will 12.2 have a fully working version of GRUB2 or would we still have to rely on Grub Legacy when installing 12.2? Thanks for any advice or info as to where I can find the answer. BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.3-1 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

1 1

Re: [opensuse-project] Request for a Blue-Ray version of the upcoming openSUSE 12.2
by Eugene Trounev 31 Aug '12

31 Aug '12

I'm not sure if something like this is possible for 12.2 which is only just a few days away... p Also there are a few important questions here: 1. How widespread is blueray this days? 2. What does Linux support of those devices look like 3. How much of our market has blue ray devices We should research on those topics and, if we see there is potential market, we can look into investing time and men power into development and deployment of blue ray media... Best regards, Eugene Trounev Alexey Eromenko <al4321(a)gmail.com> wrote: >Hi All, > >openSUSE project has nearly done it's 12.2 release ! > >One great feature to have - is blue-ray disc (BD) install media, in >addition to current DVD media. Why ? >Because it allows you download once, install everywhere, and >blazing-fast speeds, saving a lot of user time later from downloading >packages on-demand. > >Plus, it will once again let people enjoy the whole openSUSE >experience from a single media, and have a new marketing factor to >tell to the press release guys. > >The BD media should include the full openSUSE repository on a single >media. One BD for 32-bit and another BD for 64-bit PC. >Availability should be via bittorrent protocol-only, if the FTP >server's capacity is limited. >As a side bonus, BD media will let enjoy full openSUSE on offline workstations. >BD media is risk-free bonus, a feature that will not introduce >regressions into current DVD media anyway, and in fact can be done few >days post-release, if time is an issue. > >I'm looking forward into this release ! > >Best wishes and thanks to all the hard-working people, >-- >-Alexey Eromenko "Technologov" >-- >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] Re: [opensuse-marketing] Short success story
by Jos Poortvliet 30 Aug '12

30 Aug '12

On Friday 17 August 2012 13:37:16 Strainu wrote: > Hi, > > First, sorry for replying to another thread, hope it won't mess you > email client. > > I want to share a small openSUSE brand awareness success story with you. > > Last month I was in Washington for Wikimania and in one of the days I > went to visit the Capitol wearing my openSUSE T-shirt. While I was > waiting at the ticket counter, a guy from the Capitol police came to > me and said: „hey, are you using opensuse?” > > I said yes and he continued: „it'a great os, i love it because i don't > have all those problems with viruses.” > > I was very happy to see people on the street recognised our brand and > were aware they could interact with us. That's one of those things that makes someone happy :D Let's share it! > Strainu

2 1

[opensuse-project] Status: Distribution
by Stephan Kulow 30 Aug '12

30 Aug '12

Hi, Build0167 is the last we'll do for openSUSE 12.2. Maintenance team is already piling up updates and Factory will soon get a new glibc. All as it should be, thanks for your patience ;) Greetings, Stephan -- 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] Request for a Blue-Ray version of the upcoming openSUSE 12.2
by Alexey Eromenko 30 Aug '12

30 Aug '12

Hi All, openSUSE project has nearly done it's 12.2 release ! One great feature to have - is blue-ray disc (BD) install media, in addition to current DVD media. Why ? Because it allows you download once, install everywhere, and blazing-fast speeds, saving a lot of user time later from downloading packages on-demand. Plus, it will once again let people enjoy the whole openSUSE experience from a single media, and have a new marketing factor to tell to the press release guys. The BD media should include the full openSUSE repository on a single media. One BD for 32-bit and another BD for 64-bit PC. Availability should be via bittorrent protocol-only, if the FTP server's capacity is limited. As a side bonus, BD media will let enjoy full openSUSE on offline workstations. BD media is risk-free bonus, a feature that will not introduce regressions into current DVD media anyway, and in fact can be done few days post-release, if time is an issue. I'm looking forward into this release ! Best wishes and thanks to all the hard-working people, -- -Alexey Eromenko "Technologov" -- 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] Network configuration future
by Olaf Kirch 29 Aug '12

29 Aug '12

Hi all, I would like to revive a proposal that I have made a while ago, regarding a framework for managing network interfaces. I called it wicked at that time, and it's still called that way, but because of potential confusion with WICD I'll probably change the name soonishly. This project has been going on for a while now, and is getting into a more presentable shape. Given the breadth and the width of the whole topic, I won't be able to cover all aspects of the system in one email - instead, I want to give you my perspective on why I think we need something new here, and what it should look like from my point of view. Your feedback is very much welcome! Regards, Olaf -- Neo didn't bring down the Matrix. SOA did. (soafacts.com) -------------------------------------------- Olaf Kirch - Director SUSE Linux Enterprise; R&D (okir(a)suse.com) SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

4 3

Re: [opensuse-project] Network configuration future
by Richard Brown 29 Aug '12

29 Aug '12

>>> Andrew Wafaa 08/29/12 11:39 AM >>> >Definitely need the name changing, I'm unfortunately failing to come >up with any suitable cheesy names. Naked? Network Adapter Konfiguration Editor Daemon (KDE Friendly!) Nipple? Network Interface Parameters Provide Lousy Entertainment Connie? Connection Interface Editor Nanager? They're probably cheesy enough, if not good enough -- More seriously, I'm a happy NM user, and I haven't had a problem with it for some time now. When NM was too unusable for me, WICD was a great substitute. Like Andrew, I use ifup/down on my servers, but would ideally like 1 method, something nicely integrated in the UI for desktop work and solid, stable, yet easily controllable from the shell Regards -- 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] Call for help: 12.2 feature collection
by Christopher Hofmann 28 Aug '12

28 Aug '12

Hi all, openSUSE 12.2 will be released on Sept 5th, so there are only about 3 weeks left. To prepare a proper press release we need to collect the most interesting new features of 12.2. For collecting them we need help. So if you know of any super-duper-high-end-brand-new things that are on 12.2 and should go into a press release feel free to add them to http://en.opensuse.org/openSUSE:Major_features A good source for finding more product highlights might be http://download.opensuse.org/factory/repo/oss/ChangeLog If you are coltish, feel free to read http://en.opensuse.org/openSUSE:Product_highlights_writing and help us to bring the collected items in a proper form Sorry for the cross post, Christopher -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

5 6

[opensuse-project] Announcement for openSUSE-Artwork page on Google+
by Marcel Kühlhorn 27 Aug '12

27 Aug '12

Hello Artwork team! We are excited to announce that a number of us have been working on a few social media projects to facilitate easier participation and team collaboration efforts. As many of you know, we have recently started a new Flickr page where friends, fans and users can submit various forms of artwork to share with the rest of the openSUSE community. Our hope is that this new venture will create a portal that increases participation and collaborative efforts on a platform that is very user friendly and recognized by an even greater audience thus pulling from a larger pool of contributors. In addition to the new Flickr project, we are excited to share our announcement of the new G+ page established for the openSUSE-Artwork group. The G+ page will promote a global line of communication between collaborators and those who wish to become one. By providing a means that others can see and share the efforts and motivations of the openSUSE-Artwork group and community, our idea is to increase global collaborative efforts. In other words, we hope to draw more contributors to our group! On this page we will share news and events, artworks found, created and shared related to the openSUSE project, and provide a resource for fans and users to turn to for the latest "what's happening" within the openSUSE-Artwork community. The description on the page is going to be as follows: -- Tagline: Welcome to openSUSE-artwork. Have a lot of fun! Introduction: We are the openSUSE-artwork group. Our mission is to provide a portal for fans, users and members to easily share their thoughts and ideas concerning the development and improvement of the artwork involved with the openSUSE project. We encourage artists and enthusiasts from around the world to share their creativity to help us make the openSUSE project one of the most collaborative, fun and colorful Linux distributions available. Occupation: Global collaborative artwork support for the openSUSE project -- So stop by, join our circles, say "Hi" and leave a little behind to share with the rest of the community. We look forward to everyone’s additions and contributions! Thank you, -- Marcel Kühlhorn freenode: tux93 Have a lot of fun!

2 2

[opensuse-project] GSoC: AppStream / Software-Center project - completed
by Matthias Klumpp 26 Aug '12

26 Aug '12

Hi! Sorry for writing this mail relatively late, but I am very busy with stuff again and just haven't had the time for mailing until today. Same applies for my GSoC final blogpost, but this post is delayed because I want to make a video with the working stuff, because screenshots don't say much. So, what did I achieve this summer? == PackageKit == Most work has been done on PackageKit. When I started the project I thought I would spend lots of time on the Software Center, but in fact the stuff I did on PackageKit was far more important. At the beginning PackageKit was not suitable for software-center-like applications, but now it is. The PackageKit backend API is now improved and PackageKit contains many nice options for improved backend-code which backends can use. Also, cache-handling is much easier now. Also, I applied a some speed-optimizations which make PackageKit in general much faster. The biggest new feature is parallel-transactions, which allows PackageKit to execute transactions in parallel if the backend supports this too. This makes it possible to query data like package details while other actions like a installation of new packages is running. It also allows faster querying, because we can run multiple searches at the same time. I'm really excited about the changes done on PackageKit and hope backends will follow soon and implement the new API. Many thanks go to Richard Hughes for his constructive criticism and help. == AppStream == I talked to many people about AppStream to find out what people expect from it, what users want and what distributors want. The results went into my work on all three projects. I created the new software "AppStream-Core" which allows anyone to access the AppStream database using a nice GObject-based API. It also contains some more infrastructure to generate the AppStream database and maintain it. This project will make it possible to build other software-centers based on AppStream really quick. It also makes us independent from the Ubuntu Software Center (USC), because we now don't need to have it installed anymore. (this was required before to generate the AppStream db). This also makes it possible to create e.g. a software-center for KDE sharing lots of the AppStream codebase. I already implemented some small parts of AppStream in Apper last week. (after my GSoC project has finished, as this was not part of it) I also requested a project space for AppStream at Freedesktop, so I can make a release of this software soon, so other project can start using it. There's another software-center implementation, "Light Software Center", which was designed for use with PackageKit from the beginning, which will use my AppStream access library soon. == Software Center == I ported the Software Center to our new API and removed some quirks. I also optimized it for parallelization and improved it's startup time a lot. The SC received many small improvements and bugfixes. Although many things have changed for the better, using it is still not much fun. The USC is optimized for Ubuntu which results in many issues with interfering code. Also, the way SC handles PackageKit is the same way it uses Aptd on Ubuntu, which is not great, as both tools are different in some aspects. Tracking down bugs in SC isn't very easy too. So, summary for the SC: Usable to other distros (when combined with appstream-core, see above), but still no great user experience, unfortunately. I'll do some more changes on it in future, but to be honest: I also count on other software-center projects as possible replacement, if the SC plans turn out to be impossible. (but first see if we can't do more improvements on the SC code) So, that's a short summary of what has been done. I'll keep you updated on my blog [1]. As always, if you have questions, please contact me via mail or just reply here. I also have some more plans for the AppStream stuff, so there will be some more news about this in future too :-) Cheers, Matthias ---- [1]: http://blog.tenstral.net -- 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] Bugzilla account creation.
by Rajko 26 Aug '12

26 Aug '12

This is what new bug reporters and everyone else that needs Novell account have to fill in before they can access openSUSE infrastructure: https://secure-www.novell.com/selfreg/jsp/createAccount.jsp Don't you think that is a bit excessive if we want more contributors? Is there any other way to have account? -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

17 58

[opensuse-project] 12.2 feature list for release PR
by Will Stephenson 24 Aug '12

24 Aug '12

The openSUSE Team is preparing an big 12.2 feature list. This is intended to be an exhaustive list for the technical reader. We're writing up that using milestone announcements and changelogs into a descriptive wiki page, going to distill a Product Highlights page from it, and that in turn will inform PR materials and the release announcements. If you have additional features we have missed please add them in the bottom MISSING FEATURES section to the wiki page here [1], and we will add them to the descriptive document (in preparation) on the next iteration on Monday. [1] http://en.opensuse.org/openSUSE:Major_features Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] Board Appointment Announcement
by Alan Clark 22 Aug '12

22 Aug '12

Hi, Within the past few weeks, board member Peter Linnell accepted a position with SUSE. Peter will continue to participate in the the openSUSE community but to maintain compliance with the openSUSE project election rules, Peter recognized that he needed to resign from the openSUSE Board. The rules state that "In the event that individuals affiliated with a company or organization hold more than 40 per cent of the electable seats, affiliates from that corporation will be required to resign until fewer than 40 per cent of electable seats are controlled by that company or organization." With Peter's resignation, the Board has opted, in accordance to the election rules, to appoint a new member to fill the vacancy until the election is completed later this year. Having reviewed the results from last years elections and discussed the opportunity with the top vote recipients, the openSUSE board members would like to announce and welcome Manu Gupta to the board. Welcome Manu! Manu, we look forward to working with you. Regards, openSUSE Board -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

6 5

[opensuse-project] Lizards go swim!!!
by Stathis Iosifidis (aka diamond_gr) 22 Aug '12

22 Aug '12

Hello friends, After our summer camp in Greece, take those pictures. Some people are fanatics!!! http://diamond.vipfree.us/imageupload/images/imgp9041.jpg http://diamond.vipfree.us/imageupload/images/imgp9042.jpg http://diamond.vipfree.us/imageupload/images/imgp9043.jpg Check the place here: http://bit.ly/NRgaDG Sikia, Chalkidiki!!! Have a lot of fun, Stathis -- http://about.me/iosifidis http://iosifidis.co.cc or http://eiosifidis.tk http://blogs.gnome.org/eiosifidis http://eiosifidis.wordpress.com Facebook: http://www.facebook.com/eiosifidis Google+: http://bit.ly/IU5p3I Connect: https://connect.opensuse.org/pg/profile/diamond_gr Ένα γραμμάριο δράσης αξίζει ένα τόνο θεωρίας -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

Re: [opensuse-project] [reminder] openSUSE Project Meeting tomorrow at 17:00 UTC
by Alan Clark 21 Aug '12

21 Aug '12

Top on the agenda for this weeks project meeting is an overview of the openSUSE Summit. At the project meeting, the latest plans, program, parties and fun will be shared. The Summit plans are very exciting. It is going to be a great event and a lot of fun. Come check it out. AlanClark >>> On 8/21/2012 at 04:00 AM, openSUSE Meeting Reminder <no-reply(a)opensuse.org> wrote: > 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=22&month=8&year=2012&h… > =17&min=00&sec=0 > > 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, -- 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] [reminder] openSUSE Project Meeting tomorrow at 17:00 UTC
by openSUSE Meeting Reminder 21 Aug '12

21 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=22&month=8&year=2012&h… 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] UEFI Secure Boot
by Andreas Jaeger 21 Aug '12

21 Aug '12

Olaf Kirch and Vojtech Pavlik, two SUSE colleagues of mine that are also kernel developers, have been looking with others at the UEFI situation and wrote up their findings and a proposal on what to do for openSUSE. We'll share here whatever they write, I guess they do a post a day for the next few days. First post is at: http://www.suse.com/blogs/uefi-secure-boot-overview/ I'm copied the text: In case you don’t know what this blog is talking about: UEFI is the “Unified Extensible Firmware Interface”, and “Secure Boot” is one of its more recent features that is generating a bit of a stir in the Open Source world. At SUSE, we have been looking at UEFI Secure Boot long and hard. On one hand, we agree that closing down some of the loopholes in the boot process is a worthwhile goal. For decades, we have accepted that this process has been one of the soft spots that are essentially unfixable without a major change in the BIOS. Now that this change is coming, we are ready to embrace it. And we’re also happy to see a much bigger change happening as part of this, which is the establishment of UEFI as the standard firmware on all x86 platforms. On the other hand, as a Linux company, we are seeing a number of issues that have been causing us quite some headaches, which we wanted to resolve before we publicly state our plans in this regard. In order to explain our concerns, let’s take a brief look at what Secure Boot really does, in a nutshell. In the world of UEFI, securing the bootstrapping process means establishing a chain of trust. The “platform” is the root of this chain of trust; I tend to think of it as the motherboard and the on-board firmware ROM. Or, put slightly differently, it’s the hardware vendor, and the chain of trust flows from that hardware vendor to the component manufacturers, the OS vendors, etc. On the legal side, this trust is established by a lot of contracts and other legal paperwork. On the level of bits and bytes, this trust is expressed via public key cryptography. The vendor puts a so-called Platform Key into the ROM, representing the root of trust. The trust relationships with operating system vendors and others is documented by signing their keys with the Platform Key. Finally, security is established by requiring that no code will be executed by the firmware unless it has been signed by one of these “trusted” keys – be it an OS boot loader, some driver located in the ROM of some PCI Express card, or be it an update of the firmware itself. Of course, one could make this a very long chain of trust, by requiring that everything that ever gets run on that machine be signed: the OS itself, the modules it loads, the binaries and shared libraries it loads, all the scripts executed by any random interpreter, and even the commands you type into a shell session. So obviously, that has to stop somewhere; and in the UEFI specification, that point is reached when the firmware hands control to the operating system. Essentially, if you want to use Secure Boot, you need to have your OS loader signed with a key trusted by the firmware, and you need the OS loader to verify that the kernel it loads can be trusted. Admittedly, this is glossing over quite some details – but that is of no real importance for this discussion. The crux of the matter is that this conflicts with the way the Open Source community has been developing code for several decades now. The Open Source movement began as an act of emancipation from the operating system vendors of that time. Open Source was and is about Freedom, not in a dogmatic, but really in some very practical sense. The Linux community is where it is today because people could just start their own distribution, build their own boot loader and kernel, and grow a community. It is thriving the way it is thriving today because there are thousands of people around the globe who rebuild their kernel ten times a day to fix bugs, to add enhancements, or to run their test harness on the latest set of changes. And it will only continue to thrive in this way if we keep it that way. From this point of view, Secure Boot is very much at odds with the Linux development model. Just for the record, I do not think this is a conspiracy, or a sinister attempt to kill Linux. That’s not going to happen. But while Secure Boot can be a significant improvement for many, it definitely creates obstacles for the Linux community. Granted, the Windows 8 Logo certification requires that BIOS vendors should allow users to turn off Secure Boot on x86 platforms, and we have hope that all BIOS vendors will actually implement this in a way that works well for Linux developers. But ideally, Linux developers should not be required to switch off a security feature in order to run their operating system. Thus, over the past months, our guiding questions when dealing with Secure Boot have been, how can we make it work for our customers, and how can we reconcile the requirements of Secure Boot with the needs of the Linux community. We plan to continue this series of blog postings soon with an overview of how we intend to support Secure Boot in SUSE Linux Enterprise, and what solutions we propose to the openSUSE community. -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

13 18

[opensuse-project] Scanny: week report
by Piotr Niełacny 20 Aug '12

20 Aug '12

Hi guys, this is my first report about scanny for #1 week: http://ruby-blog.pl/GSoC/2012/05/28/scanny-week-1/ -- Piotr Niełacny -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 12

[opensuse-project] Leaving the board.
by Peter Linnell 20 Aug '12

20 Aug '12

Hi, Some of you know, I have recently taken a position at SUSE here in Silicon Valley. I've joined the Sales Engineer/ SUSE Linux Technical Specialist team. It has been a bit more than a month and I can say it has been a really great experience. As I am now on the "inside", I can see that SUSE has never been better positioned to succeed in a long time. I've not had the chance to engage the business side of SUSE before in the same way I have with the engineering and openSUSE team side of things. That said, I've never had the kind of welcome joining a company like I have at SUSE. It's been extraordinary. Because of this, I must resign from the board. I've thoroughly enjoyed working with my fellow board members and I now consider them friends. It does not matter if they are SUSE employees or not. They all care a lot about the community. All my dealings with them have been very forthright and correct. As for me, I will not disappear from the community. Far from it. Now that I am here in North America, I am one more voice inside the company who will be actively evangelizing on the community's behalf. As I have reached out to my new colleagues, there is definitely an openness to listen, learn about and engage the community. I could go on longer, but I do want to thank publicly Alan Clark for helping me get on board. We as a community are really lucky to have him as a board member and chair. Alan has done a terrific job on behalf of the community, though often times it is quite invisible and not recognized publicly. I've learned he has enormous respect inside SUSE and he is a great ambassador for the community. Thanks for listening. Peter Linnell -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 4

[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

[opensuse-project] Created openSUSE-artwork group in Flickr
by Rajko 01 Aug '12

01 Aug '12

Created openSUSE-artwork group on Flickr: http://www.flickr.com/groups/opensuse-artwork/ it is open group so anyone with affinity to collect artwork for openSUSE benefit can join. Basic idea is described in this thread: http://lists.opensuse.org/opensuse-artwork/2012-07/msg00031.html Gist is a collection of artwork and some selection that will go into next release. Why Flickr: http://lists.opensuse.org/opensuse-artwork/2012-07/msg00050.html it has few tools that will allow people that are not active in other parts of openSUSE to communicate. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 2

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

01 Aug '12

Hi, Last week, I have managed to : Implement a customURL class which supports two URL formats. Normal URL with Regex Two parameters separated by a pipe. In this case, the first parameter is processed and the links are retrieved. The second parameter (the regex) is applied to the links obtained. Fixed a few bugs in the system both on the Rails frontend and Python Backend. Implemented very basic threading to process only X records for every Y seconds. The values of X and Y can be chosen by the user. This helps spreading the load evenly on the system. Written a blog post with the basic concepts of the project. http://nbprashanth.wordpress.com/2012/07/30/the-upstream-tracker-project-2/. I am currently working on implementing multithreading on to the system to improve overall performance and speed of processing. Since custom URL is also implemented to the system to an extent, I will be working on DEHS import. -- 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