openSUSE Project June 2018

project@lists.opensuse.org

17 participants
7 discussions

by Axel Braun

Hi, dunno if this is the right list to ask about infrastructure, so just giving it a try: I'm subscribed to opensuse-support, and receive mails every now and then. I tried yesterday and today to send a question to the list, but none of the mails showed up.....any issue with this list? Or with my provider (GMX)? Cheers Axel -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 years, 10 months

[opensuse-project] distribution release timing

by Felix Miata

It bugs me to see reports like https://bugzilla.opensuse.org/show_bug.cgi?id=1096913 https://bugzilla.opensuse.org/show_bug.cgi?id=1096971 https://bugzilla.opensuse.org/show_bug.cgi?id=1096960 so soon after a new release. In the past two weeks there have been 20 new Distribution reports on Installation, 7 on Upgrade Problems, 9 on YaST2, 7 on Network, 2 on Bootloader, 13 on Basesystem, and 186 on simply Distribution, of which explicitly 15.0. Does anyone have any recollection if this is a typical result of a new release? It makes me wonder if releases should better be timed to _not_ coincide with social gatherings as happened with 15.0, so that last weeks' testing time isn't disrupted by plans and preparations for a social event. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 years, 11 months

[opensuse-project] Board meeting minutes 2018-06-05

by Christian Boltz

Hello, here are the meeting minutes of the 2018-06-05 board meeting. == Attendees == * Ana * Christian * Knurpht * Richard * Sarah * Simon == Action Items from the face2face board meeting == * Handling feature requests / replacement of openFATE * ongoing work (Sarah) on https://en.opensuse.org/openSUSE:Submitting_feature_requests * we'll list some / most important upstreams, but can't list them all * feedback welcome * Conference comittee * Richard talked to Doug to get it started * mailinglist cleanup * we'll shut down mailinglists that are not active for a year * before doing so, we'll ask on opensuse-project and the affected mailinglist * Communication channels * a few community members started to "play" with Matrix * Involving community in board meeting agenda * Ana will write to opensuse-project that community members can add items to the board agenda via https://en.opensuse.org/openSUSE_talk:Board_meetings or a mail to board@ * make openSUSE subprojects more visible * Ana and Gertjan will add our subprojects (openQA, OBS, Jangouts, ...) to the wiki main page * www.o.o needs a similar update - but one job at a time * news.opensuse.org license * news.o.o should get an open source license * Richard will talk to Doug to choose one * openSUSE money independence * Simon will investigate options like SPI to handle sponsor's money independent of SUSE * projects and events sponsored by openSUSE * Richard speaks with Doug about it * we got a sponsoring proposal from a community member - Ana will reply and forward it to Doug == Membership == * we'll update the documentation about becoming a member to match the simplified rules * we'll make sure non-technical contributions (for example helping at openSUSE conferences or helping with translations) are included as examples * membership for proven active contributors: * we (ideally someone from the membership commitee) will reach out to groups like forum admins and remind them that they can easily become a member for what they are doing * we won't send out such reminders to individual persons == oSC18 review / post mortem == * we decided to dedicate the next meeting complete for the conference * AI everybody (board and community): send feedback about oSC18 - what did you like, what should we improve? == Leap 15 == * download statistics will be late and incomplete because logging was partially broken You can also find this summary on https://en.opensuse.org/Archive:Board_meeting_2018-06-05 Regards, Christian Boltz -- Immer noch am Squid oder lieber Knöpfchen drücken und anstarren, ob sich was tut? Vergiß es, der Computer sitzt am längeren Hebel und ist, was solche Geschäfte angeht, ein Sturkopf. [Helga Fischer 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 years, 11 months

[opensuse-project] Re: Reminder: openSUSE.Asia summit call for paper deadline in 2 days (6/15)

by Max

Hi ALL Just reminder, please submit your talk before 6/15. ( Just in 2 days ) Please submit yours at: https://events.opensuse.org Types of sessions We will invite the three types of sessions as below. If you apply for TSP, long talk or workshop is strongly recommended. * Long talk (30 min + Q&A) * Short talk (15 min + Q&A) * Workshop (120 min) If you need more time or additional resources, feel free to get in touch with the organizing team. You could see more detail here https://news.opensuse.org/2018/05/17/opensuse-asia-summit-2018-taiwan-call-… -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 years, 11 months

[opensuse-project] invitation to add items to Board Meeting Agenda

by Ana Martínez

Hi! The board is always happy for people to reach them with things that need to be discussed. Because of this we encourage everybody to add items they find important to the next meeting agenda. To make this easy, we have created the following Wiki page, where you can add your items: https://en.opensuse.org/openSUSE_talk:Board_meetings. You can of course also reach the board privately via email board(a)opensuse.org with your topics if your prefer. In the next meeting (19-6-2018) we will make a retrospective of the last openSUSE conference (what was good, what was not that good, what things need to be improved for next year, etc.) I you have anything to say regarding this topic please let us know. ;) You can find more information about the Board meetings (including the summaries of the meetings) here: https://en.opensuse.org/openSUSE:Board_meetings Regards, Ana -- Ana María Martínez Gómez http://anamaria.martinezgomez.name -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 years, 11 months

[opensuse-project] openSUSE Conference Organizing Team

by ddemaio

Hi all, I wanted to start this thread early since we just finished oSC18. The board discussion (https://youtu.be/AI0TQckPrLw?t=18m41s) had a section that talked about having an organizing team for future openSUSE Conferences. If you are interested in helping to organize the openSUSE Conference, please email me. I will begin to look for dates that will work for oSC19 and have been in discussions with two people for keynote talks at oSC19. It would be great to have more people join plan the conference together. I look forward to chatting with anyone who has an interest in collectively planning the conference. v/r Doug -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 years, 11 months

[opensuse-project] Mailinglist changes going forward

by Simon Lees

Hello everyone, Firstly I am cross posting this across a number of mailinglists because this post affects several, but I would ask that you keep your replies / feedback on the openSUSE project list as not to fragment discussion. It has been raised with the board by several members of the community that some of our mailinglists have not been working as effectively as we would like. As such and as raised in our annual discussion with the community during the conference, the board has decided to take a couple of steps that we hope will resolve these issues or that will at least be a starting point in resolving these issues. Firstly we have created a new opensuse-support(a)o.o mailing list, we as the board felt that in the transition from factory -> tumbleweed in particular the change in role for opensuse(a)o.o did not work well and in many cases there was an attitude that factory/tumbleweed issues should still be posted on the factory mailing list. As such we have created the support mailing list to help clarify these changes in policy that we don't believe worked when we tried to change them last time. In short we would like you to use opensuse-support(a)o.o whenever you require support whether it is for Tumbleweed, Leap (regardless of whether you are using a Leap beta or not) or any other project under the openSUSE umbrella. This brings us to the next issue, posting bugs / bug reports on mailing lists rather then bugzilla. This is a practice we would like to see stopped and we will be gently reminding people if they continue posting bugs on mailinglists, this especially includes if a package / application breaks when updating tumbleweed / leap (including beta's). We would ask that you search for your issue prior to reporting but in case you accidentally report a duplicate bug its easy for us to mark it as such, also if you report something that is intentional and not a bug it doesn't take long to mark it as such, so if in doubt file a bug rather then posting to a mailing list, there is useful information for filing bugs at the following links [1][2]. But if you are really stuck with trying to file your bug the friendly people at opensuse-support(a)o.o can support you through the process. The board hopes that with the changes outlined above the contents of the opensuse-factory(a)o.o will go back to just being general distro development discussion so if your post to openSUSE factory is something other then that think twice about where the more appropriate place to post is. The new tumbleweed snapshots will continue to be posted to factory but we would ask you do not reply to them in order to report issues / bugs. If a bug is reported that a package maintainer believes will cause significant issues for most tumbleweed users ie not being able to boot / login or severe data loss we still invite the maintainer to post a warning to opensuse-factory but such issues happen very rarely and as such we don't expect to see many such posts. The board has decided that it would like to see how well these changes work before deciding to add / remove / change openSUSE's mailing lists further. Although we have discussed several other possibilities that we could also try in the future. 1. https://en.opensuse.org/openSUSE:Bug_reporting_FAQ 2. https://en.opensuse.org/openSUSE:Submitting_bug_reports -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

2 years, 11 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Project June 2018