October 2012 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] interviews to members
by Victor hck 13 Oct '12

13 Oct '12

Hi. I think that would be a good idea before the board elections to make one interview to each member elected and the president, of course! ;) It would be the way to present to the community these Geekos: what they think, what projects are involved, etc... In Linux.com ( https://www.linux.com/news/special-feature/linux-developers ) are making these interviews to kernel developers, for me I think that it's interesting to know who are behind the code, who are the persons behind the project... Maybe it's a good idea to make interviews to other members... just and idea... Bye -- 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] openSUSE Board elections 2012: looking for volunteers for the Election Committee
by Vincent Untz 11 Oct '12

11 Oct '12

Hi all, It's that time of the year again: we'll be having elections for the openSUSE Board in a few weeks! For this to happen, we need people to step up and join the Election Committee. At least three openSUSE members need to be in that committee. The Election Committee has the following responsabilities: + Defining how many vacant seats are "one year term" seats and how many vacant seats are "two year term" seats + Creating of a schedule for the elections + Collaborating with the Membership Officials to ensure that membership applications are processed in time + Handling and verifying of candidate nominations + Checking and testing of our voting setup before the real voting + Validating the election results + Resolving any post-results issues Of course, this is not the most glamourous job in the project, but it's a great way to contribute to building the community, and it's a nice opportunity to collaborate with two groups of people (current board and membership officials). If you'd like to volunteer, please notify board(a)opensuse.org before Friday October 12th. As a reminder, you can read our election rules at: http://en.opensuse.org/openSUSE:Board_election_rules Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 10

[opensuse-project] request: Change the way bugs are 'closed' -- require package info and verification by OP
by ar16＠imapmail.org 10 Oct '12

10 Oct '12

When filing a bug, assuming that it's valid, the acceptable, desired outcome is a verified & deployable fix. In our distro terms, that's a package, made available in a repo -- arguably one of the repos that the system reporting the bug has enabled, and that the OP has verified -- by using/deploying the updated package -- works (within an acceptable response time frame ...). @ Opensuse bugzilla, it's frequently true that bugs are 'closed' when a developer has made changes to code -- without, necessarily, evidence that an OBS request has been made, the package is in a test-repo, &/or that it works for the OP. For example, here are two bugs I've filed where that's occurred (it's an example, not a criticism of the work done/contributed in the bugs ): https://bugzilla.novell.com/show_bug.cgi?id=779087#c28 Bug 779087 - after 12.1->12.2 upgrade, system with ROOT on LVM-on-RAID fails to boot; loops VG not found/partial mode https://bugzilla.novell.com/show_bug.cgi?id=782835#c15 Bug 782835 - Xen HVM Guest fails (errors) to launch on Opensuse 12.2 + Xen 4.2 + 'xl' toolstack Reopening is certainly an option. Reopening is not always well received. The noise created by the open/close/reopen 'dance', and hunting for bug-specific information outside of the bug, simply wastes everybody's time, and, imo, discourages participation/contribution. I'd like to propose (at least for some discussion) that bug process/workflow be changed to require the inclusion/posting of target package info, and an OP-verification step. - ar -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

10 18

[opensuse-project]
by evy 10 Oct '12

10 Oct '12

Hallo ich habe eine frage ich habe per vmware ein vm erstellt mit opensuse und mein persönlichen einstellungen vorgenommen, nun möchte ich diese VM auf einen Usb stick kopieren, denn ich dann an jeden anderen belibigen computer anstecken kann und die vm starten kann. Nur leider finde ich im Internet keine passende anleitung hierfür wie ich dies genau machen muss ich wäre Ihnen sehr dankbar wenn sie mir helfen könnten. -- 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] promoDVD's shipping stop until after oSC
by Jos Poortvliet 09 Oct '12

09 Oct '12

Hi folks, We're receiving quite some orders for promo DVD's and that is cool. But unfortunately we're extremely busy with the openSUSE conference and that has priority. So, until after the conference on Oct 20-23, we will not be able to process shipping requests for DVD's and other promo materials. After the conf we'll get to it as quickly as we can, OK? Regards, Jos The openSUSE Team

2 2

[opensuse-project] Notes from the Q/A session during the openSUSE Summit
by Vincent Untz 09 Oct '12

09 Oct '12

Hi, We had a Q/A session at the end of the summit, and here are the notes that were taken. I encourage everyone who was present to add more details if they have (as those notes are based on the big board we had, thanks to Craig for taking notes there). We discussed four topics: the summit itself, the project in general, the board, and the release process. About the Summit ================ - overall, good event, should be done next year! - what was good: - session selection - the geeko lounge - food - parties - having people bring kids was nice (helped give an even bigger family feeling) - timing was not so good (especially given the openSUSE Conference is a month later) - slides need to be collected and published - communication can be improved: - need a contact form on the website so people can ask questions - "acknowledgement" (not sure what it means; Andrew might remember) - would be nice to have a skill level associated with each session - call for sessions was not visible enough; people missed it - venue in the US caused visa issues (many people from South America couldn't come in the end) - no lightning talks - we forgot the group photo! About the project ================= (we mostly focused on things that were bad/could be improved) - some discussion about the communication in the project: - too complex (many communication channels, hard to reach decisions, etc.) - bad signal/noise ratio - would be nice to collect in one place our key objectives - people commented that we started doing that for 12.3: http://en.opensuse.org/openSUSE:Goals_12.3 - ... and that we have a mission statement in general: http://en.opensuse.org/openSUSE:Strategy - in general, there are too few people for too many tasks - we need more mentoring and enablement - even though it will distract people from other important tasks in the short term, this matters a lot for the long term - more reporting is wanted to get news about the project (many of us raised the idea of doing quarterly reports) About the board =============== - people see it as the "face" and "voice" of the project - board should be passive (ie, should not control the project), but also active to address pain points - when contacting the board, it should be clearer when a +1 from one board member means "yes from the board" or if it's just "yes from board member" - everybody should know that the board has an "open door": don't be afraid to mail board(a)opensuse.org About the release process ========================= (quickly discussed, as requested by Jos) - 12.2 being late was felt as an exception, and exceptions happen - quality is more important than strictly respecting the schedule - there was some quick discussion about the (lack of) governance of many devel projects; this is painful for some people - some people wanted the automatic mails from coolo (reminding about submitrequests, build failures, etc.) to be enabled again Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- 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] Project Meeting Report
by Manu Gupta 04 Oct '12

04 Oct '12

Heya All, We discussed a lot of things in yesterday's meeting A. Conference updates from Jos and Tampakrap 1. If you want to help with conference, 1.1 Pick a task from https://trello.com/board/opensuse-conference/503b692a387cdc6d5388ad08 1.2 Interview interesting people from http://en.opensuse.org/openSUSE:Conference_Interviews 1.2.1 Add yourself here http://en.opensuse.org/openSUSE:Conference_volunteers 1.3 Bof sessions can now be scheduled: http://en.opensuse.org/openSUSE:Conference_BoF_sessions 1.4 People must step up to volunteeer for the conference As a side note, to join the trello board, mail the oo-conference list with your trello credentials And for those who don't follow the news.o.o and planet, we announced the schedule, we have 2 full days of presentations and workshops, and the 2 extra opensuse only days and a great event is ahead. B. Inactive Mailing Lists - The list that was presented today ( can be found in meeting logs ) will be sent to the mail to for either deactivation. If anyone has an objection please let us know asap C. Google Code-In 1. We are already in the bootstrapping phase thanks to Rajko 2. Robert, Matt and Me will be admins 3. We need mentors and tasks 4. Taks that are of top priority are of as of now include these *** review GCI wiki pages ( volunteer needed) *** GCI announcement for mentors and task (volunteer needed) D. Proposal For Project Meeting >From our discussions today, it seemed that everyone wanted a standing agenda to the meeting. So this is a proposal, we have a standing agenda for the first 5 / 10 minutes of the meeting. The meeting starts exactly at the scheduled time. E. Proposal, The Board being a reporter One of the roles of the board has been to facilitate communication with all areas of the community. To do that, I propose the Board should take up responsibility of publishing various things that are going in and around the community. For now, we can start off with small number of teams and learn from it and report bi-monthly. Later on as stuff matures, we increase the number of teams and the bimonthly part moves to a quarterly report. Also if the Board fails to report ( it can be treated as inactive / passive state ). What we hope to achieve with it - 1. What is happening between teams. 2. What is good and bad about the teams. The teams we want to start off with is 1. Travel-support team 2. Ambassador-welcome 3. Wiki team 4. Web stats The proposal has been agreed by Vincent so far and by what I know from Izabel Andy seems to agree with it. Since I dont know about others, and a general consensus was formed at yesterday's meeting I think we should move forward with it. The first report should come in by the second week of november, before that I will try to come up with a template that makes just life easier for us. Regards Manu PS I will try to make reports do not guarantee it. So keep more #info's in the meetings so that it becomes easier to take them down. -- 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] openSUSE Conference 2012 – Invitation to Lightning Talks and Speedy Geeko
by Izabel Valverde 04 Oct '12

04 Oct '12

The openSUSE Conference in Prague is about to happen and one more time with great talks and workshops and the warmth of the openSUSE Community. Being there is really awesome and being a part of it is really great. This year we'll bring one more time the openSUSE lightning talks and Speedy Geeko. We encourage everyone to come and be a part of it. Please READ MORE http://news.opensuse.org/2012/10/02/opensuse-conference-2012-invitation-to-… Informations and submissions about Lightning Talk please contact "izabelvalverde at opensuse dot org" with subject title: Lightning talks Informations and submissions about Speedy Geeko please contact "warlordfff at opensuse dot org" with subject title: Speedy Geeko Join us! Your hosts Izabel Valverde and Kostas Koudaras -- 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] Tasks and Mentors needed for Google Code-In
by Robert Schweikert 04 Oct '12

04 Oct '12

All, It is time for the next Google event, hurray :) , and once again we would like to participate as a mentor organization. Having successfully participated in the Google Summer of Code and also last year's Google Code-In we are once again aiming to participate in a Google event; Google Code-In 2012, see http://en.opensuse.org/openSUSE:GCI for details. Therefore we need tasks and mentors. This year the rules have changed a bit and this should put things on a different footing compared to last year. Google is not handing out money to the students, rather a trip to Google HQ in Mountain View, CA for an awards ceremony is provided for 2 students plus guardian for each of the participating projects. Only 10 open source projects will be selected. Therefore, it is time to get your good ideas and things that are on your list but that you are never going to get to onto the the task list. We are looking for tasks in the following 5 categories: 1.) Code: Tasks related to writing or refactoring code 2.) Documentation/Training: Tasks related to creating/editing documents and helping others learn more* 3.) Outreach/Research Tasks related to community management, outreach/marketing or studying problems and recommending solutions 4.) Quality Assurance: Tasks related to testing and ensuring code is of high quality 5.) User Interface: Tasks related to user experience research or user interface design and interaction *Note: Translation tasks are not allowed As you add tasks to the list please remember that the students targeted by this contest are 13-17 years of age, thus adding a task to fix a kernel bug to the list is probably not the best fit. We want to provide an environment where these students can learn, but also are challenged and stretched out of their comfort zone a little bit. With this lets get moving, please add your tasks to: http://en.opensuse.org/openSUSE:GCI_tasks The application deadline for organizations is Monday November 5, this gives us basically 4 weeks to get our task and mentor list into shape. Lets get cracking an put some tasks on the list. Mentor organizations will be announced on November 12 and the contest runs November 26, 2012 through January 14, 2013. In advance thanks to those stepping up to be mentors and those that add tasks to the list. Your GCI Organizing Committee Manu Matt Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- 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] 12.3 Schedule and development
by Will Stephenson 03 Oct '12

03 Oct '12

Given that 12.2 slipped by 2 months, and the development process for 12.3 is "to be discussed", what schedule are we working on towards 12.3 at the moment? Every time I've been involved in a project without a schedule, we've had a long period of (probably highly satisfying for developers) of 'undirected hacking' followed by crisis, followed by a rush to 'get it out before people forget who we are' which inevitably had some fallout (I'm thinking of the period leading up to KDE 4.0 here ;). So I'd like to start the discussion now before we lose a month waiting to discuss it at osc12, where only a fraction of the active members of the project are is going to be present anyway. You don't want everything to be decided by German Engineers* for you do you? Some ideas to start the ball rolling: * openSUSE 12.2 original schedule + 8 months = openSUSE 12.2 actual release + 4 months = Do a short cycle and release in March 2013, essentially 12.2 + bugfixes and updates * openSUSE 12.2 actual release + 8 months = May 2013, business as usual, using a fixed process to solve the problems that caused the 12.2 slip * Extend the release cycle keeping same process and longer stabilization period (effective 12.2 release process; leads to shipping 'outdated' stuff) * Change the process to plan more features in advance (as much as this is realistic given we mostly ship what our upstreams deliver) and work together to achieve these Please, save your 'my vote is for this' type of replies. And if you're an armchair general willing to type paragraphs of email here but not a single OBS checkin, meeting participaton or wiki update to 12.3, go do something more pleasurable with your fingers instead. This discussion is not about your favourite kind of icecream, as if that will change anything. This need a reasoned discussion on what to do in future, to get a majority of the actors in the project to agree to act together, and then action. Otherwise we will default to an arbitrary schedule, several months of undirected hacking and taking what comes from upstream, reactive release management to get the result bootable and not too likely to blow up in users' faces, and frantic analysis of the brew by -marketing to make it sound like a consistent whole offering an attractive narrative of improvement (Guess what I did for the last few weeks). Will (* Something Pascal was moping about on IRC last week, I'm hoping to tempt him out of his cave) -- 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

35 182