openSUSE Project May 2017

project@lists.opensuse.org

32 participants
12 discussions

[opensuse-project] Wiki update - call for testing
by Christian Boltz 30 May '17

30 May '17

Hello, [cross-post - please reply only on one of the mailinglists] Those who visited the Heroes talk at the openSUSE Conference already know - there is visible progress on the wiki update and I have a *test* wiki running :-) So, what's new? The highlights are: - updated MediaWiki to 1.27.x (LTS release) and all extensions - now running on a VM in Nuremberg - including files directly from github - better search (elasticsearch) - now searching all namespaces, but with different weight - login is now done using openID - but still with your openSUSE login - namespace-specific boilerplates (page templates) when creating new pages - switched extension for RSS feed integration - this will need adjustments on the pages that include RSS feeds - watching a category (when pages get added to or removed from it) is now part of MediaWiki core - Hermes notification was dropped (was broken anyway, and MediaWiki's own notifications work much better) There's also something that isn't too new - the database dump I used to setup the test wiki ;-) It's from last August, so please don't worry about the outdated content ;-) That all said - the test wiki is available for testing at https://en-test.opensuse.org/ Please check if everything still works, play with it, test the new features, ...! It is a test instance, so nobody will complain if you do test edits that don't make sense content-wise ;-) At the same time, remember that it is a test instance, so any changes you do will be lost when I re-import the database dump for whatever reason. If you notice any issues, please report them - either in one of the mailinglists (opensuse-wiki preferred) or send a mail to admin(a)opensuse.org If you enjoyed testing the new wiki, please also take some time to go to our current wiki (en.opensuse.org or $LANG.opensuse.org) - there are lots of pages that need an update ;-) And finally - thanks to everybody who helped me to get everything in shape! I still have to do some work "under the hood". That shouldn't cause any problem with testing, but it means that I won't do the production wiki move and update in a few days ;-) Regards, Christian Boltz PS: oSC visitors may wonder why it's en-test.o.o instead of en.test.o.o now. That name change is caused by a funny problem with our SSL certificate - *.opensuse.org doesn't match something with an additional dot, and en.test.o.o had such a dot ;-) -- Was habt Ihr denn? emacs ist doch ein tolles Betriebssystem! Das einzige was ihm fehlt, ist ein vernünftiger Editor (vim?) [Jan Trippler in suse-linux] -- 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] openSUSE Members retirement
by Michal Hrusecky 27 May '17

27 May '17

Hi everybody, as you all know, we have the openSUSE Members, a group of contributors through their sustained and substantial contributors that are eligible to participate in elections, have @opensuse.org mail and other perks. We have now about 600 of them, but as you can see[1] in last openSUSE Board elections only 150 of them voted. This could mean two things - either most of the members are not interested in elections or plenty of them are simply no longer around. I guess the truth is somewhere in middle. This is something we need to know when we take project wide decisions in order to correctly assess the communities interest in the topic. This is a recurring topic that has been discussed at the openSUSE Board Face to Face meeting last year, oSC 15, and on this list several times over the last few years. Taking these into consideration, we (in the board) think it would be a good idea to implement something to help with ensuring our Membership list accurately reflects our current Membership. I have put together a tool which attempts to detect an openSUSE Members activity on mailing lists, OBS, bugzilla, maybe more. This tool will remember when we last saw openSUSE Member on any of those channels and if they doesn't show for 6 months, we will send them an e-mail asking whether they still wants to be a member. A response to that email will automatically count as activity and preserve the Members status. If there is no response within 30 days of the notification, the Member will be 'retired' and be considered a 'Member emeritus'. If someone is retired incorrectly, or a 'Member emeritus' returns to the Project and wants a restoration of their voting privilege, they will be unretired without question by the Membership Committee. There are few implementation details to be worked out, so we don't expect this to go live overnight but consider this a "statement of intent" and an explanation of how we expect things to work before we start testing the process. ==== To answer some of the obvious questions: Q: Shouldn't we retire inactive members anyway after measuring and evaluating their activity? A: No, that would be too hard, too subjective and it could bother people that we cannot measure automatically. Automatic measurement is just an indicator that those people are no longer interested, but they might be just working on project aspects we cannot measure. openSUSE Members are members until THEY no longer want to be. We believe this system preserves that principle. Q: Wouldn't it offend active contributors if they will be falsely accused of not being interested? A: I hope not. If period will be long enough (6 months) and if we monitor even mailing lists, people will usually show up somewhere. We intend to word the 'ping' email in a way that is not judgemental, but just makes it clear that we have failed to automatically find evidence of contribution so want to make sure they are still interested in remaining a Member. Q: Doesn't it change the meaning of the openSUSE Member? A: Not really. So far once you got a membership status, it was forever without question. Now it would be forever as long as you are interested. No big change, just a little difference. Q: What if mail with warning gets lost? A: If you lose your membership by accident by losing an e-mail, you can still contact membership committee and as a retired member you will be reinstated immediately without voting/verification that takes time. And you should fix your e-mail in connect.opensuse.org in that case ;-) Q: Will retired members retain their email & IRC cloak perks? A: No, the intention is that retired members will no longer be eligible for @opensuse.org email addresses and Freenode IRC cloaks. [1] https://connect.opensuse.org/pg/polls/read/pluskalm/49480/opensuse-board-el… -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

19 44

[opensuse-project] Re: [security-announce] openSUSE Leap 42.1 has reached end of SUSE support
by Mathias Homann 25 May '17

25 May '17

...have we at any time in the past ever had a situation where there was only ONE version of openSUSE officially supported? I mean, Leap 42.3 is not out yet... Am 17.05.2017 um 15:07 schrieb Benjamin Brunner: > Hi all, > > With the release of release-notes-openSUSE on May 17th, 2017 the SUSE > sponsored maintenance of openSUSE Leap 42.1 has ended. > > openSUSE Leap 42.1 is now officially discontinued and out of support by > SUSE. > > The currently maintained stable release is openSUSE Leap 42.2, which > will be maintained until the Q2/2018. See https://en.opensuse.org/Lifetime > > Upgrading is easy. See the links below for instructions: > > https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.star… > https://en.opensuse.org/SDB:System_upgrade > https://en.opensuse.org/SDB:Offline_upgrade > > > openSUSE Leap 42.1 was released on November 4th 2015, making it ca. 18 > months of security and bugfix support. > > It was the first hybrid distribution which used sources from SUSE Linux > Enterprise and from our community developers to bridge a gap between > matured packages and newer packages found in openSUSE Tumbleweed. > > Some statistics on the released patches (compared to 13.2): > > Total updates: 1442 (+98) > Updates imported from SUSE Linux Enterprise: 507 > Updates provided by community developers: 935 > Security: 598 (-109) > Recommended: 807 (+182) > Optional: 36 (+24) > Feature: 1 (1) > > Fixed CVE-entries: 2434 (-217) > Fixed Bugs (overall): 3735 (-170) > > A huge thanks to our awesome packagers, community, and all involved > people, who made the next great release possible! > > Your maintenance- and security-team > -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

15 30

[opensuse-project] openSUSE Annual Board Meeting in Nuremberg 23-25 May
by Richard Brown 23 May '17

23 May '17

Hi all, Next week the openSUSE Board will be guests at SUSE's Nuremberg office for the annual openSUSE Board Face to Face meeting. This is the main meeting for the year for the Board to review the current status of the openSUSE Project and work on setting the agenda and direction for the next year. This year the two main themes already on the agenda for discussion are - "Settling Organisational Debt"; The last few years has seen openSUSE's technical offerings transform, from being a project primarily about a single Linux distribution, to a more diverse open source umbrella project hosting many different projects, including two Linux distributions. This has led to some 'organisational cruft', with bits and pieces of the project, infrastructure, documentation, etc no longer aligned with the current direction of travel of the project. The Board wishes to take the opportunity to identify and start driving a collective cleanup in these trouble spots. This will likely involve cleaning up and removing old policies, structures, and concepts in the project, and driving the documentation of the realities which the community is really holding to. - "Emphasising and broadcasting our uniqueness"; openSUSE has a lot of unique attributes which sets it apart from our 'competition' in the FOSS world. Our technical offerings are getting growing attention, but openSUSE is a lot more than our technical offerings. Our culture, our outlook on things like FOSS licensing, our openness to contributions from anyone, the nature of our relationship with SUSE, are all things which set us apart, but how would the rest of the world know that? The Board wants to investigate and drive improvements in this area, identifying these unique strengths of the Project and better exposing and amplifying their visibility to help strengthen alignment within the project, and growth of the project with new users & contributors. But, this is not all the Board wants to be doing! You have a unique opportunity to get involved, share your ideas, and influence the Boards work and the Project as a whole. If you have anything you'd like to add to the Board's agenda, please email board(a)opensuse.org and we'll be sure to add it to the list. And if you do not have anything for the agenda but you'd like to meet the Board and you're going to the openSUSE conference, you can meet us all there on the Friday-Sunday after our meeting :) Have a lot of fun. -- 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] openSUSE for Small- and Medium Sized Business
by Stefan Schäfer 20 May '17

20 May '17

Hi openSUSE members, we (Klaas Freitag "Kraft", Stefan Schäfer, Ines Armbrust, Ingo Göppert und Dimitri Asarowski "invis-Server.org") are organizing a workshop at this year's openSUSE Conference around the productive use of openSUSE in small and medium-sized enterprises. From our own experience, we believe that especially openSUSE Leap is very suitable for small- and medium business use cases. We would like to invite all those to participate in the workshop, who use openSUSE in small or medium-sized enterprises or maintain their own openSUSE based open-source-projects. The goal of the workshop is to organize ourselves within the openSUSE community as a team or group to strengthen openSUSE as an operating system for productive use in companies and to organize a permanent exchange of experience among all interested parties. The bundling of our work, such as packaging or developement, could also be of interest to all participants. Anyone who wants to contribute can describe his own project or his experiences with the productive use of openSUSE in companies inside this workshop. Hope to see you there Stefan -- www.invis-server.org Stefan Schäfer Ludwigstr. 1-3 63679 Schotten -- 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] Re: [security-announce] openSUSE Leap 42.1 has reached end of SUSE support
by Richard Brown 19 May '17

19 May '17

On 19 May 2017 at 17:26, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > > On Fri, May 19, 2017 at 11:09 AM, Richard Brown <RBrownCCB(a)opensuse.org> > wrote: >> >> 42.3 isn't released yet, so, no, not yet :) >> >> But it will be supported when it releases in July, and it will be >> awesome, true :) > > > > July! > > What rock have I been hiding under? I do not know https://en.opensuse.org/openSUSE:Roadmap https://lists.opensuse.org/opensuse-factory/2017-03/msg00302.html https://www.phoronix.com/scan.php?page=news_item&px=openSUSE-Leap-42.3-Roll… https://nwrickert2.wordpress.com/2017/05/18/opensuse-leap-42-3-alpha/ http://news.softpedia.com/news/opensuse-developers-implement-rolling-develo… etc, etc, etc.... -- 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] UPDATE: openSUSE Services Outage
by Richard Brown 16 May '17

16 May '17

Hello all, The situation with that led to the distribution of openSUSE infrastructure the last few days has been resolved. The shutdown of openSUSE infrastructure was triggered by SUSE's Corporate policies designed to err on the side of caution in order to protect their assets and our data. We're pleased to be able to report that after an extensive review and audit of the systems involved we are confident that nothing was compromised and all of our code and personal information housed within was adequately protected throughout. Therefore all of the systems that were shut down are now back online. We apologise for the inconvenience or confusion caused. I'd also like to thank everyone for their understanding, and especially thank our admins who worked tirelessly over the weekend to investigate and restore services as quickly as possible. Regards, Richard Brown openSUSE Chairman -- 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] Several openSUSE services disabled due to a security breach
by Richard Brown 14 May '17

14 May '17

Dear openSUSE Community, We have been informed of a security breach of the MF authentication system used by several openSUSE services. As a result, the openSUSE services using this authentication method are immediately being set to read-only mode/preventing authentication. This includes the openSUSE OBS, wiki, and forums. The scope and impact of the breach is not yet fully clear. The disabling of authentication is to ensure the protection of our systems and user data while the situation is fully investigated. Based on the information available at this time, there is a possibility that the breach is limited to users of non-openSUSE infrastructure that shares the same authentication system. Regardless, is recommended that all users of the affected services and openSUSE bugzilla change their password at the following link: https://secure-www.novell.com/selfreg/jsp/protected/manageAccount.jsp https://status.opensuse.org/ can be used to monitor the status of the services as the incident is further investigated. We do not believe any of the openSUSE Download infrastructure has been compromised, as it does not interact with the MF authentication system. Therefore www.opensuse.org , download.opensuse.org and software.opensuse.org remain operational and safe for all of our users to use. Thank you all for your understanding and support, and expect a further update as soon as we have more information. Regards, -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

6 8

[opensuse-project] @opensuse.org member addresses were temporary broken
by Christian Boltz 12 May '17

12 May '17

Hello, as the result of some configuration changes, the <member>@opensuse.org mail addresses were temporarily broken. The breakage started yesterday around 15:30 and was fixed today around 9:15. As a result, mails sent to <member>@opensuse.org in that timeframe were rejected by mx2.suse.de with Recipient address rejected: User unknown in virtual alias table In the meantime, the <member>@opensuse.org addresses are back to normal. Note: this issue is _not_ related to the security breach Richard announced today. Regards, Christian Boltz -- > oder das absolut berauschende ;-)) > [ -d "/test/" ] || echo mkd Danke, zum Glück muß ich heute nicht mehr mit dem Auto fahren :-) [> Thomas Preissler und Al Bogner in suse-linux] -- 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] Re: [opensuse-factory] openSUSE Leap's Next Major Version Number
by Richard Brown 09 May '17

09 May '17

On 24 April 2017 at 07:16, Neal Gompa <ngompa13(a)gmail.com> wrote: > On Sat, Apr 22, 2017 at 7:37 AM, Richard Brown <RBrownCCB(a)opensuse.org> wrote: >> There are only a few packages in our distribution that reference the >> 42.x versioning, and they should be easily handled as part of a zypper >> dup, so we are not concerned about this decision impacting users >> upgrading. > > > This statement concerns me more than anything else. What about all the > people who build solutions around openSUSE or for it? We *just* > managed to figure out the new mess that is SUSE versioning, and now > you want to break us again? > > The number of conditionals I need for supporting the SUSE platform > keeps growing with each release, and that's extremely aggravating. Yes, I understand that, but one of the benefits of this change means you'll be able to get rid of some of those conditionals when Leap 42.3 reaches end of life, as opposed to needing to keep conditionals around for 4x.y forever -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

10 13

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Project May 2017