March 2016 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] openSUSE Board Face-to-Face Meeting 2016 Minutes - Part 3/3
by Richard Brown 22 Mar '16

22 Mar '16

openSUSE Face to Face Board Meeting 2016 Minutes 18th-20th March Present: Richard Brown - Chair Michal Hrušecký Kostas Koudaras Tomas Chvatal Gertjan Lettink Bryan Lunduke - Extra special thanks goes to Bryan for attending via video conference at ridiculous hours in his local timezone after urgent personal matters kept him from attending the meeting in person. As this years Board Meeting Minutes are so long, they are split into 3 sections Meetings - Covering the meetings the Board had with various SUSE executives, managers, and engineers. General - Covering the general agenda items/day-to-day issues Strategy - Covering the 'big picture' issues the Board discussed This email is Part 3, containing 'big picture' strategy issues discussed Part 2 is available http://lists.opensuse.org/opensuse-project/2016-03/msg00039.html Part 1 is available http://lists.opensuse.org/opensuse-project/2016-03/msg00038.html = Strategy = == Improve Visibility == Obviously, we want to improve the visibility of the openSUSE Project. We have great distributions, great tools, and great technologies, and we want them to be adopted by as many people and other projects as possible. We also want to be a natural choice for new contributors and new projects to come to openSUSE, work with us, and host their projects with us. === SUSE === SUSE is our closest, largest, partner. We have strong practical ties with them, but that does not mean we can forget about things such as regular clear communication and 'internal marketing' SUSE are working on a number of exciting new things, and it's important that internally openSUSE is seen as a natural home for SUSE's open source contributions. Working closely together also should enable SUSE's corporate marketing experts to help spread the good word about all the awesome stuff the openSUSE Project is doing AI: Bryan to investigate the possibility of Doug being invited to Weekly team meetings for SUSE Corporate Communications AI: Bryan to drive ensuring openSUSE is well integrated with SUSE's ongoing marketing. === Outreach === There's no point only targeting our existing contributors and partners like SUSE. Any open source project needs new people and with new people comes new ideas, new solutions, and new exciting projects for people to hack on A huge challenge for new contributors and projects is understanding what is available - Who is the openSUSE Project? - What services do we provide? - Where do I go to get involved? - How do I get started? These are questions which are _key_ to have simple, clear, easy to find answers to CALL FOR HELP: The Board wants to see getting started guides for - New Users - New Contributors - New Projects - to encourage other projects to come use openSUSE as their home to answer the above questions. These should be simple, clear, and relatively short. The produced guides should be easily usable on a wiki, the website, on flyers at conferences, short blog posts..we want to be able to spread them _everywhere_ The guides for new Contributors and new Projects are considered a Priority by the board - to use a football related quote "There is no point having fans, if you don't have your 11 on the pitch to play for them" AI: Board intends to create a skeleton of the above guides to help bootstrap this idea, and will drive this, but the Board is keen to see if anyone from the community dives in and gets to work on this immediately. === Other Projects === While openSUSE is keen to see other projects call the openSUSE Project it's home, we recognise that it's not viable for many, especially those larger ones with their own established communities In cases like this the Board wants to encourage strong relationships with such Projects, and seek out partnerships and other arrangements with such Projects for the benefit of all involved Examples include ownCloud and Kolab, where we believe openSUSE is in a perfect position to offer tools, community, and a solid environment for these projects to use as a default or recommended platform for their users AI: Bryan to arrange information exploratory discussions === Hardware vendors === Having hardware sponsors and partners is nice but is hard. Solid hardware support requires the hardware to be available and in the hands of the right contributors to make it happen Otherwise there is no way how to support special hardware without the things available for testing. However, we do have some relationships which are happening, and we want to highlight those who do stuff with us, such as - Soft Iron are shipping 64-bit ARM servers with openSUSE Tumbleweed as standard - Fujitsu offer openSUSE Tumbleweed to thier customers who want a Linux option on their Desktop & Server Hardware - Epson have some printers using openSUSE and YaST - Open Mainframe are investigating the possibility of building an openSUSE distribution for s390x == Reform and Remove Mess == Improving viability and reaching out to new areas is all well and good, but we need to make sure the project internals are tidy, clear, and easy to use Board discussed the state of many infrastructure and project policies and processes. We agreed a principle of, when something is imperfect, we Reform (aka improve) or Remove it. Services identified to be removed or reformed: - Software.o.o: 1) Media download needs to be easier, prefferable static page 2) package search adds too much mess to the installed systems. Invalid repos should not be distributed by 1-click installs 3) somehow redesign and reduce confusion to ensure that users do not end up with 80+ additional repos. - Wiki: 1) In order to fix the wiki quickly ,the board approved the idea of deploying the latest version of mediawiki on a new server without branding 2) branding can always be redone later - Blogs/Planet: 1) Only a handful of people use Planet, but it takes a lot of resources to keep it running. We want to shut it down, and encourage it's users move to their own blogs, which will then be aggregated on planet.opensuse.org 2) Improve planet.opensuse.org. Find a maintainer, use a clean upstream OSS soltion if possible AI: Kostas to contact the few Lizards bloggers to discuss their migration options - News.o.o: 1) Wordpress consumes too many resources and poses too many security risks 2) Replace with something lightweight AI: Richard talk with Douglas about this - i18n.o.o: Translations site is being migrated to l10n.o.o as we speak and i18n will be killed including the svn prior Leap 42.2 release. - Legal layout of Board/membership: The current layout of the Board Election Rules, Membership Rules, and such are sometimes confusing and missing some details The documents will be updated and restructured to be more clear This should set the framework for discussing any reforms of the Membership process once the Membership tidy-up is complete AI: board - get Infra team to provide list of services we have, soon to help with this endevour -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

5 10

[opensuse-project] openSUSE Board Face-to-Face Meeting 2016 Minutes - Part 1/3
by Richard Brown 21 Mar '16

21 Mar '16

openSUSE Face to Face Board Meeting 2016 Minutes 18th-20th March Present: Richard Brown - Chair Michal Hrušecký Kostas Koudaras Tomas Chvatal Gertjan Lettink Bryan Lunduke - Extra special thanks goes to Bryan for attending via video conference at ridiculous hours in his local timezone after urgent personal matters kept him from attending the meeting in person. As this years Board Meeting Minutes are so long, they are split into 3 sections Meetings - Covering the meetings the Board had with various SUSE executives, managers, and engineers. General - Covering the general agenda items/day-to-day issues Strategy - Covering the 'big picture' issues the Board discussed This email is Part 1, containing meeting minutes of meetings with SUSE = Meetings = == Meeting with openSUSE Release Manager - Ludwig Nussel == The Board met the new openSUSE Release Manager - Ludwig Nussel He shared the following tentative information about the planned release for Leap 42.2: Leap 42.2 will be based on SLE 12 SP2 and their release scheduled are 'aligned' (ie. They will be developed together, but not necessarily release together) Target release date for Leap 42.2 is 1st week of Nov 2016 Expected to have an updated systemd, GNOME, Qt, kernel all inherited from SLE 12 SP2 KDE of course will want to upgrade from 5.5, expected 5.6, discussions underway about what upgrade policy will make sense for the lifespan of Leap 42.2 We don't expect X will be updated, which will mean 42.2 will have the same version as 42.1, which is newer than the version in SLE 12 SP1 or expected in SP2 Leap 42.2 will start with a base of Leap 42.1, with packages updated from that point. The process for contributing to Leap 42.2 needs explanation We discussed the shape of how we'd like to see the wiki We all agreed want to see a big tidy up. Many of the Portals have little benefit and serve little purpose. We want to see the namespaces removed/flattened to help the search Tumbleweed deserves a Portal. Questions the page must answer include "What is Tumbleweed?" "Why use Tumbleweed?" and "Why might Leap be better for you?" Leap is similarly important, needing to answer the questions "What is Leap?" "Why use Leap?" and "Why might Tumbleweed be better for you?" Packaging Polices and the Factory process are other 'key' pages which must be preserved, polished, and refreshed during any wiki cleanup Team pages would be 'nice to have' but many Team pages are currently woefully out of date. We would like to see a solution investigated where the wiki team page is inherited from a devel project We discussed the idea of forming a "Release Team" with specific roles that are responsible for ensuring that key parts of the Release process are carried out Obvious roles include "Website coordinator" to ensure the website is updated "Wiki Coordinator", "Marketing Coordinator", "Test Coordinator", "Translation Coordinator" are other obvious roles These people would not necessarily be responsible for doing the work, but for coordinating with Ludwig and ensuring that the work gets done by someone. AI: Ludwig to mail the Board with any other "Roles" which are expected to be needed AI: Board + Ludwig to send a 'Call for Volunteers' for the roles, and to put together the team AI: Board to request release-team(a)opensuse.org list for this team Discussed some of our local teams. We share concerns that those teams with their own forums, own wikis, and own websites ultimately 'split' the community and make it harder for everyone to benefit from the shared knowledge, experience, and feeling of 'collective ownership' of the project. We'd like to see such sub-communities bought closer together and go forward more 'aligned' with the rest of the openSUSE Project We discussed some concerns regarding the current openSUSE Infrastructure software.opensuse.org serves two very important roles, both as the main download portal for our distributions, and as a software search for OBS PROPOSAL: Split software.opensuse.org to have the download portal and search separate. The download portal could be a simple, clean, fast, static site that would offer the Leap and Tumbleweed ISOs Software search would continue as it is...but we considered some problems with that The current implementation of One-Click installs is often dangerous. Because they add all the repos setup in the OBS repo you often end up with crazy things like Factory:ARM repos being added on systems where they are not relevant Furthermore, making it very easy to install packages from 'non-official' repos dramatically reduces the motivation and impetus for developers to put their packages in the Distribution Having packages in the Distribution though is the best way to ensure your package works, is tested, and is integrated So we would like to see One Click only pulling from the official repos If Packages are not in the official repos, we would like the software search to put users in touch with devel project maintainers to encourage the packages be added to the distributions CALL FOR HELP: We would like a maintainer for software.opensuse.org to help implement the above changes to the search and download functions of software.opensuse.org == Meeting with the SUSE Infrastructure Team == The Board received an update from Gerhard Schlotter, Marcus 'darix' Rueckert, and Lars Vogdt from the Infrastructure Team at SUSE SUSE host 12 physical servers for openSUSE services. This is in addition to the 127 OBS & openQA physical servers Those 12 macines host a total of 60 VMs The OBS and openQA hardware host a total of 820 VMs www.opensuse.org has 2.3 million visitors per month - how can we make that bigger? Discussed the immediate problems with some part of the infrastructure, especially the wiki. Some is hosted in SUSE's datacenter in Provo, some is hosted in Nuremberg Nuremberg datacentre has room and admins, but limited bandwidth (not enough for how busy stuff gets on releases) Provo datacenter has room and bandwidth, but limited admins. SUSE have an engineer moving from Nuremberg to Provo to help illivate that problem. Having sponsored hosting elsewhere is an option we want to actively pursue. We have hardware available if we can find a host. CALL FOR HELP: Please help us find sponsors willing to help find openSUSE infrastructure Infrastructure guys would like the Sponsorship leaflet to be updated in order to better court possible hardware and hosting sponsors AI: Douglas to update sponsorship guide Improvements to the @opensuse.org email system are being investigated Infra team would like connect.opensuse.org to be shutdown AI: Board to investigate alternatives for voting & membership management == Lunch == The Board had lunch with dozens of SUSE Engineers. Lots of different conversations but the key topics that stuck with the board include Discussions about how to improve translation/l10n tools and workflows Communication with the KDE Project How to get started with openSUSE, as a contributor and as a Project that wants to be part of the openSUSE Project. == Meeting with Ralf Flaxa - President, Product Engineering at SUSE == Ralf thanked the Board for coming and their ongoing work for the openSUSE Project, and expressed SUSE's pleasure with the success of Leap and the general direction of the openSUSE Project Ralf shared some ideas regarding oSC and his departments Hackweek AI: Board to discuss the ideas with the oSC organisers == Meeting with Roland Haidl - Director, Operations & Communities at SUSE == Roland reaffirmed SUSE's intention to continue funding the openSUSE Project at similar levels. Roland shared Douglas DeMaio's plan to refill our merchandise before openSUSE Conference 2016 Board requested budget for openSUSE Asia at the same levels as last year - Approved Discussed the possibility of the Board appointing a Treasurer to be the primary contact with SUSE on financial matters (Sponsorships, TSP, etc) - Approved Discussed the possibility of a hackathon for the Release Team, once it's formed - Approved in principle (Needs the team first) Discused the possibility of more 'minisummits' consisting of openSUSE presentation tracks and related events colocated at other events around the world - Approved in principle (Needs events and volunteers) Discussed the current wiki problems. Roland volunteered to help drive a solution AI: Richard - Infrastructure to be a standing topic in regular Chairman meetings with Roland == Tour == The Board was given a tour of the SUSE HQ, including the recently expanded office space and server rooms. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

5 7

Re: AW: [opensuse-project] SUSE Studio drops 13.1
by jdd 20 Mar '16

20 Mar '16

Le 20/03/2016 20:32, Michael Kromer a écrit : > Everything you do with studio can be done with kiwi. Why not simply > asking people to use kiwi instead for anything older, and there you can > keep your stuff as outdated as you wish. A lot of things have changed > since 13.1, we had 13.2, leap 42.1 and also tumbleweed, 13.1 was > released end of 2013, I get your point with evergreen and such, but I > sincerely believe that the infrastructure, etc. does not have to be able > to build images for these outdated things. Outdated behavior is exactly > what brought us to a desolate wiki state, etc. > > Any second opinions? very good answer. However, https://doc.opensuse.org/projects/kiwi/doc/ do not say (at least not at first glance) if kiwi is big and demanding? Is it possible to use a studio config with own kiwi, because the lack of a gui makes it hard. may be we could ask in "feature" for any kind of kiwi gui? nothing similar here: https://features.opensuse.org/query/run?search_string=kiwi&exclude_closed=t… thanks jdd -- 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] Has anyone considered if the "blog" re the board is factual?
by Basil Chupin 15 Mar '16

15 Mar '16

The current -- as of a few minutes ago -- contents of the info. about the members of the board (here: https://en.opensuse.org/Board ) states that these names are members of the board: Richard Brown Michael Hrusecky Kosta Koudaras Tomas Chvatal Gertjan Lettink but as there has not been an announcement of who was appointed by the owners of SUSE to play the role of chairman of the board for the year 2016/2017 the question arises if the list shown at the above URL is accurate or is up-to-date. To add to this, I thought that there are supposed to be 6 members on the board -- but there are only 5 mentioned. BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.4.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- 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] oSC16 - Organizing Team Meeting 5 Notes
by ddemaio 15 Mar '16

15 Mar '16

Hi all, Here is the update from our Organizing Team Meeting from March 8. I will not be doing the meeting next week since I'll be on holiday. ChrisBrwill chair next week's meeting. The take away from this week's meeting is: 1. Reserve your hotel ASAP. The NorisRing races take place the sameweek as the conference - http://bit.ly/1QBp3o8<http://bit.ly/1QxzN2H> 2. Currently there are 52 registered attendees with 32 proposal submission - Submit your proposal https://events.opensuse.org/conference/oSC16/program/proposal/new 3. The pre-conference party will start at 19:00 / 7 p.m. on June 21 at Kater Murr - http://kater-murr.com/ 4. Posters being made to advertise oSC locally. Advertising video should be ready by mid-April. 5. To have items included in the swag bag, send them to: SUSE Linux GmbH c/o Douglas DeMaio MaxfeldStr. 5 Nuremberg, Germany 90409 v/r Doug Week 5 notes - http://community.opensuse.org/meetings/opensuse-project/2016/opensuse-proje… Week 4 note - http://community.opensuse.org/meetings/opensuse-project/2016/opensuse-proje… Week 3 note -<http://community.opensuse.org/meetings/opensuse-project/2016/opensuse-proje…>http://community.opensuse.org/meetings/opensuse-project/2016/opensuse-proje… Week 2 notes -<http://community.opensuse.org/meetings/opensuse-project/2016/opensuse-proje…>http://community.opensuse.org/meetings/opensuse-project/2016/opensuse-proje… Week 1 notes -<http://community.opensuse.org/meetings/opensuse-project/2016/opensuse-proje…>http://community.opensuse.org/meetings/opensuse-project/2016/opensuse-proje…

3 2

[opensuse-project] oSC - Track list when editing a talk
by Christian Boltz 15 Mar '16

15 Mar '16

Hello, when I edit one of the talks I submitted for the conference, there's a dropdown "Track" that lists the subconferences (Kolab, SUSE Labs etc.), but not the main openSUSE Conference. a) is that intentional? b) if yes, is "leave blank" the correct option for talks that are meant for the main openSUSE Conference? BTW: It would be nice to get the "submit new talk" and "edit talk" forms in sync - currently, "edit talk" displays more fields that "submit new talk". Regards, Christian Boltz -- Man kann nicht Leuten helfen, die nicht verraten, was sie wollen. Das ist so sexy wie zum Arzt zu gehen und nicht zu verraten, wo es weh tut. [Peer Heinlein in mailman-de] -- 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] Official openSUSE Docker Images
by Aleksa Sarai 15 Mar '16

15 Mar '16

Hello, everyone. Currently, it appears as though the Docker Hub's build system is having issues (and any recently released official images will likely have the same issue). As a result, the latest version of the library/opensuse:{leap,harlequin} images are broken (opensuse:tumbleweed works but is outdated). You can check if your local version of the opensuse images are broken by running the following command: % docker run opensuse:leap test If the program produces the following error, then you have a broken version of the opensuse images: exec: "test": executable file not found in $PATH Error response from daemon: Cannot start container a6a3663cc29e6a542101306dfc007e796db1fc67b12eb12134c77d24cffcbf45: [8] System error: exec: "test": executable file not found in $PATH In order to allow users to use the official openSUSE Docker images (while the Docker Hub's build process is being fixed), we have pushed all of the latest builds to the opensuse/ namespace. You can get them like so: % docker pull opensuse/amd64:leap % docker pull opensuse/amd64:harlequin % docker pull opensuse/amd64:tumbleweed If you have any Dockerfiles that rely on `FROM opensuse`, you can tag the new images like so: % docker tag opensuse/amd64:leap opensuse:leap Which will allow you to build all of your Dockerfiles as before. Sorry for the inconvenience, and we're working with upstream to fix this problem. Please make people aware of this issue (for example by retweeting https://twitter.com/lordcyphar/status/709699748412850176) -- Aleksa Sarai Docker Core Specialist SUSE Australia https://www.cyphar.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] Self Introduction: Aditya Prakash
by Aditya Prakash 15 Mar '16

15 Mar '16

Hi everyone, I'm would like to introduce myself as a new member of your community. I am a computer Science undergraduate student in junior year from National Institute of Technology, Durgapur, India. I am maintainer at GlitterGallery[1], and recently I have been hacking on OSEM[2]. I am working on my Ruby skill and it is exciting to see that openSUSE has so many Ruby projects. I hope that this summer I will get to work on enhancing submission process[3] on OSEM under GSoC. You can read my rather opinionated blog at: http://chasingcrazydreams.wordpress.com/ or find me on Github @sonalkr132[4] Cheers, Aditya [1] https://github.com/glittergallery/GlitterGallery [2] https://github.com/openSUSE/osem/issues?utf8=%E2%9C%93&q=author%3Asonalkr13… [2] https://docs.google.com/document/d/1FElqRCAY1IVOPv7xvex1TxU9P4iQ-v4sUgoyJfs… [4] https://github.com/sonalkr132 -- 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] GSoC
by Nick Mantas 14 Mar '16

14 Mar '16

Greetings Geekos, I'm a member of the project and think about joining opensuse in GSoC. I am particularly interested in Alternatives YaST Modules. Thing is i don't know ruby but am really good with python and am willing to learn. Do you think I can cope with the difficulties or try next year? -- Nick Mantas -- 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] GSoC 2016
by Nick Mantas 14 Mar '16

14 Mar '16

Greetings Geekos, I'm a member of the project and think about joining opensuse in GSoC. I am particularly interested in Alternatives YaST Modules. Thing is i don't know ruby but am really good with python and am willing to learn. Do you think I can cope with the difficulties or try next year? -- Nick Mantas -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 2