May 2018 - 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] Mailinglist changes going forward
by Simon Lees 01 Jun '18

01 Jun '18

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

9 17

[opensuse-project] Re: [opensuse-factory] Re: Mailinglist changes going forward
by Fraser_Bell 30 May '18

30 May '18

On 05/28/2018 09:39 AM, Neil Rickert wrote: > On 05/28/2018 09:50 AM, Anton Aylward wrote: > >> My experience has been that reporting my own mistakes and >> misconfiguration on bugzilla simply ends up in a WONTFIX. It may >> be that the developer didn't have time or patience to explain what >> *I* was doing wrong and that there really wasn't a bug, or it may >> be that (s)he didn't want to bothered tracing why this bug happens, >> what fringe/test-case brings it up. > > For users in this situation, my best advice would be to post to the > opensuse forums (forums.opensuse.org) Quite a few people do that > already. And theyare advised to open a bug report when that is > appropriate. Exactly. It is a great Forum, with great Volunteer Support, and is Moderated so that the garbage that floods these mail lists tends to be almost totally absent. -- -Gerry Makaro openSUSE Member openSUSE Forum Moderator openSUSE Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- 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] Re: [opensuse] Re: [opensuse-factory] Re: Mailinglist changes going forward
by Simon Lees 30 May '18

30 May '18

On 29/05/18 03:16, John Andersen wrote: > On 05/28/2018 08:28 AM, Anton Aylward wrote: >> What is left for the main list? Are you saying it should be a social group? > > As I've mentioned on another thread, the board would love to kill this list completely, > as well as all the others. The Board!!! Not the developers, not the users, but the board. > Well you could probably extrapolate that to at least some openSUSE Members as well, as they vote for the board and I personally and I believe others mentioned cleaning up some mailing lists as something we would like to see. So people appointed me to the board knowing I wanted to make changes to mailing lists. > Users are expected to join 20 mailing lists, and know exactly which of those they > dare post an issue upon, Its Not sufficient to know which department to file your > complaint with, you must also know the desk, and which in-basket to use. > The introduction of opensuse-support@ is meant to make it clear where all support issues can be emailed. > I admit I grow weary of long running wandering threads, as people devolve into discussing > the minutia of side issues, often leaving the original poster hanging in suspense. Also > annoying are the long copy-pastes of pointless console output that help nobody. > But I delete the threads and move on. > > Mostly what gets posted here are user-to-user questions. Nobody here is under the > slightest delusion that any developers participate here. Just other users that > may have seen a similar issue. > In the past when I first joined this list there was plenty of user-to-developer questions posted here, but over time many developers (including several on the board) got sick of the noise on this list and either unsubscribed or created mail filters to /dev/null The hope with the new opensuse-support mailing list is that we can keep it more ontopic and as such many of the developers that are willing to offer support but left this list as it was a waste of there time will return to the new list and offer support there. > Bug Reports? chuckle.... > The MAJORITY of Bug reports are closed two years later when that release falls > out of maintenance, or marked as a duplicate of another bug, which is eventually > marked as won't fix two years later. > When such bugs are closed it is made clear that you can reopen them against a newer version if the issue persists, this change is also more related to the mail on opensuse-factory@ rather then opensuse@ where we see lots of emails along the lines of ABC broke in the latest snapshot > There seems nowhere one can ask a question of other users, without invoking the > wrath of the board, or the swift admonition to go join another mailing list > and post your problem there. > Yes if you are asking "support" questions in the very broad term of support on the opensuse-support@ mailing list no one will get grumpy with you, if you want to ask other users how to cook fish or where to go on holiday etc opensuse-offtopic@ is a much better place. > I'm thinking the Forum would be a better place. It is for Manjaro, but > I'm not so sure it is for Opensuse. > openSUSE has excellent forums to the point where the board considered just moving all support questions to there rather then mailing lists, but as we know some people prefer mailing lists we decided against that. -- 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 2

[opensuse-project] Re: [opensuse] Re: [opensuse-support] expected behavior, or not?
by Fraser_Bell 29 May '18

29 May '18

On 05/29/2018 02:02 PM, John Andersen wrote: > On 05/29/2018 11:09 AM, cagsm wrote: > >> Forums is for webtards ;p and bugreport >> is for proper precise reporting with already distilled details. > > Unfair, and rather insulting. Correct. Guidelines? Principles? > > New users can post in a forum, and some one or two people can take them > in hand and lead them to a solution or maybe @mention someone else known to > be knowledgeable on the subject at hand and thereby call their attention to > the thread. > > But the rest of the forum can just stay away from that thread, and never > have it filling their mailbox weeks or months after it has wandered off > track. > > Bug reports are where you go once you are sure the problem is real, > after talking to other, on a list or a forum. ... this is very well said, John. Thanks. -- -Gerry Makaro openSUSE Member openSUSE Forum Moderator openSUSE Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

Re: [opensuse] Re: [opensuse-project] Re: Mailinglist changes going forward
by Fraser_Bell 29 May '18

29 May '18

On 05/29/2018 03:23 AM, Knurpht @ openSUSE wrote: > Op dinsdag 29 mei 2018 11:21:58 CEST schreef ellanios82: >> On 29/05/18 11:57, David C. Rankin wrote: >>> This seems like action being taken to address a problem that isn't readily >>> apparent or very well defined from your original post. >> - believe Chairman Brown in most eloquent spokesperson for these >> fragmentation-thought-processes >> > The board has talked about this, *not* out of some wicked idea, but because it > was asked to many times. Yes, *asked for* by the Users and the Community, for a long time, now. > And this has nothing, *absolutely* noting to do with what the board "wants". Read the board > pages in the wiki and you'll see the board has no authority to act except when > asked for. Can we please have that illusion out of the world and these > suggestions over and done with. The Board is *not* allowed to dictate to the Community, and it *does not*! The Board represents the wishes of the Community -- this is why they are elected and not appointed -- and acts according to the wishes of the majority. When they do not, it is because it is something the Board cannot do anything about. Simple as that. > And whilst doing so also stop mentioning individual board member names, since the board operates as a team. > ... Guiding Principles. -- -Gerry Makaro openSUSE Member openSUSE Forum Moderator openSUSE Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- 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] Re: Opening private bugs
by Simon Lees 29 May '18

29 May '18

On 29/05/18 02:09, John Paul Adrian Glaubitz wrote: > On 05/28/2018 05:19 PM, Anton Aylward wrote: >> As I said, elsewhere, not all problems are bugs. >> Those that are not are better solved by the Wisdom of Crowds than annoying a >> single developer who has limited time and patience. > > I agree with that. I have made the experience from Debian that many users > abuse the bug tracking system as a support forum. It can be quite frustrating > when you are overrun with invalid bug reports which were just reported because > users are unable to tell a bug from a local configuration issue. > >> But not all problems are bugs. Deep debugging can be challenging and >> infuriating, but the resolution gives satisfaction. >> Dealing with users making their own <strike>idiocies</strike> mistakes into bug >> reports is frustrating and annoying. >> >> I hope this *IS* a short term solution since in the longer term the Suse >> developers will get annoyed enough to stop volunteering <strike>to deal with >> idiots</strike>. > > Yes. If you tell people to report a bug every time they run into a problem, > you will have your bug tracker flooded with invalid bug reports. > Again 2 different issues that we are trying to be solved differently have been mixed up here. If as in the case suggested in this email you have tried to setup a webserver for example and something is not working and your not sure if you did it wrong or you found a bug, you should not file a bug you should ask for help on opensuse-support@ on the other hand if you zypper dup in tumbleweed and something breaks which is likely a bug then rather then reporting it on opensuse-factory@ we would like you to create a bug report. Sorry if this wasn't clear in the original email. -- 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

1 0

[opensuse-project] Re: [opensuse] Re: [opensuse-support] expected behavior, or not? (was: Mailinglist changes going forward)
by Simon Lees 29 May '18

29 May '18

On 29/05/18 05:31, Felix Miata wrote: > Simon Lees composed on 2018-05-28 21:21 (UTC+0930): > >> 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. > > I don't get stuck "filing" bugs. I get stuck figuring out whether something is > expected behavior, or constitutes a bug. > And that is where you should use opensuse-support@ > Who's going to do all that extra triage work if every time someone has that > dilemma and proceeds to file a bug instead of asking first? Mailing lists seem > to generate responses, useful or otherwise, faster. Bugs apparently get seen by > a select few, and are often ignored for long periods. > > Just what constitutes "filing a bug" on a mailing list? There are many posts on opensuse-factory@, that are along the lines of I updated to the latest snapshot and XYZ broke, these are what we'd prefer to have as bugreports. > >> 1. https://en.opensuse.org/openSUSE:Bug_reporting_FAQ >> 2. https://en.opensuse.org/openSUSE:Submitting_bug_reports > > I don't think these clarify, but at least indirectly may be inducing list > "filing". From the latter: > > "Non-technical users: You may try first http://forums.opensuse.org ." > -- 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

1 0

[opensuse-project] Re: [opensuse-factory] Opening private bugs
by Simon Lees 29 May '18

29 May '18

On 29/05/18 02:59, Anton Aylward wrote: > On 28/05/18 12:12 PM, Simon Lees wrote: >> As I said in my >> original email SUSE Engineering is currently looking into how they can >> do this but at the same time stay within there various requirements that >> ensure customer information stays private. > > I can read that as "they can benefit from our experience and bug reports because > we're not 'professional' enough but we can't benefit from theirs". > > Please explain why this is not the case. > There are various certifications that SUSE needs to have in order to fulfill many of there contracts with customers, these state alongside other things that customer info must remain private. In the past before the shared code base the easiest most logical way to do this was to simply make all SLE bugs private, as I said SUSE Engineering understands this won't work into the future and are looking into alternatives. -- 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

1 0

[opensuse-project] Re: [opensuse-factory] Re: Mailinglist changes going forward
by Carlos E. R. 28 May '18

28 May '18

On 2018-05-28 16:50, Anton Aylward wrote: > On 28/05/18 07:51 AM, Simon Lees wrote: >> 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). > > I understand your concern. > What you are complaining about is people too lazy or disinclined to use bugzilla > to report valid bugs. I know (and you know, Anton) of some people that bluntly refuse to use bugzilla, and nothing will change their thinking ;-) > However ... > >> We would ask that you search for your issue prior to reporting > > Not just on bugzilla but ... > > I'm sure there are users less experienced than me who are unsure of themselves > and unsure if what they see as something wrong is a bug or their own mistake. > The mistake may be wrong assumptions about what is supposed to happen or it may > be misconfiguration rather than a bug. > > My experience has been that reporting my own mistakes and misconfiguration on > bugzilla simply ends up in a WONTFIX. It may be that the developer didn't have > time or patience to explain what *I* was doing wrong and that there really > wasn't a bug, or it may be that (s)he didn't want to bothered tracing why this > bug happens, what fringe/test-case brings it up. > > And perhaps I'm not alone ... > > So before reporting to bugzilla I ask on the list "Is this my mistake?" I do that. :-) I hate to report a bugzilla and then find out that it was my fault, and that I wasted a contributor time. I really hate that. > To date, a better than 90% of the cases has been "MY mistake and guidance, often > from people that I don't think would be opensuse-support(a)o.o. And yes, I've > been referred to the kde- list and the btrfs- list and the xfs- list and the > people there have always been helpful in telling me what I was doing wrong. > > MY opinion is that using bugzilla as a 'first resort' will result in a lot of > <strike>highly pissed off</strike> irritated developers as well as lots of even > more <strike>highly pissed off</strike> irritated users. I agree. > > Yes, opensuse-support(a)o.o will work, *IF* you publicise the hell out of it and > keep telling people who subscribe, naturally enough, to the main and other lists. > Perhaps you need a sign-up notice a monthly notice, such as the sort that > Mailman can send, telling users about opensuse-support(a)o.o and the other lists, > kde-, btrfs-, xfs- and so on, and to take specific problems there. Perhaps. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

1 0

[opensuse-project] Retiring the Ambassadors/Advocates names
by Simon Lees 28 May '18

28 May '18

Hi All Another thing that came out of last weeks board meeting is that we would like to retire the ambassadors and advocates names, instead we would like to encourage anyone to be an ambassador / advocate for openSUSE. There is a list of things you can do / consider if you would like to run an event or a booth at someone elses event at [1] and a list of events where openSUSE representatives are already planing to attend at [2] 1. https://en.opensuse.org/openSUSE:Events 2. https://en.opensuse.org/openSUSE:Upcoming_events Thanks -- 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

1 0

[opensuse-project] Leap 15: Thank You
by ddemaio 28 May '18

28 May '18

Hi everyone, As you might be aware, the community released openSUSE Leap 15 on Friday. On behalf of the project, I would like to personally thank everyone who helped to make the release possible. From filing bugs, to testing, to updating the wiki, to submitting packages for the release, you all helped to make the release possible. Ludwig gave a great talk while releasing Leap at the openSUSE Conference - https://youtu.be/GpBXNIc2ys4. We know that not everyone is able to attend the conference, but want extend a thank you for all of you who helped that were not able to make it to the conference. Enjoy Leap 15 and have a lot of fun! v/r Doug -- 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-factory] Re: Mailinglist changes going forward
by Simon Lees 28 May '18

28 May '18

On 29/05/18 00:20, Anton Aylward wrote: > On 28/05/18 07:51 AM, Simon Lees wrote: >> 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). > > I understand your concern. > What you are complaining about is people too lazy or disinclined to use bugzilla > to report valid bugs. > > However ... > >> We would ask that you search for your issue prior to reporting > > Not just on bugzilla but ... > > I'm sure there are users less experienced than me who are unsure of themselves > and unsure if what they see as something wrong is a bug or their own mistake. > The mistake may be wrong assumptions about what is supposed to happen or it may > be misconfiguration rather than a bug. > > My experience has been that reporting my own mistakes and misconfiguration on > bugzilla simply ends up in a WONTFIX. It may be that the developer didn't have > time or patience to explain what *I* was doing wrong and that there really > wasn't a bug, or it may be that (s)he didn't want to bothered tracing why this > bug happens, what fringe/test-case brings it up. > > And perhaps I'm not alone ... > > So before reporting to bugzilla I ask on the list "Is this my mistake?" > > To date, a better than 90% of the cases has been "MY mistake and guidance, often > from people that I don't think would be opensuse-support(a)o.o. And yes, I've > been referred to the kde- list and the btrfs- list and the xfs- list and the > people there have always been helpful in telling me what I was doing wrong. > > MY opinion is that using bugzilla as a 'first resort' will result in a lot of > <strike>highly pissed off</strike> irritated developers as well as lots of even > more <strike>highly pissed off</strike> irritated users. > > Yes, opensuse-support(a)o.o will work, *IF* you publicise the hell out of it and > keep telling people who subscribe, naturally enough, to the main and other lists. > Perhaps you need a sign-up notice a monthly notice, such as the sort that > Mailman can send, telling users about opensuse-support(a)o.o and the other lists, > kde-, btrfs-, xfs- and so on, and to take specific problems there. > The biggest % of emails we see at the moment in the factory mailing list are along the lines of I did a zypper dup package XYZ broke, these are the sorts of things we would like to see bugs raised for. If you are setting up something for the first time or doing something different are are wondering if the issue is caused by your setup or a bug in the program then opensuse-support@ is the right place to ask your questions. -- 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

1 0

[opensuse-project] Re: [opensuse-factory] Mailinglist changes going forward
by Simon Lees 28 May '18

28 May '18

On 28/05/18 22:35, Neal Gompa wrote: > On Mon, May 28, 2018 at 8:01 AM Jan Engelhardt <jengelh(a)inai.de> wrote: > > >> On Monday 2018-05-28 13:51, Simon Lees wrote: >>> >>> 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 [...] > >> Rename it to opensuse-devel (carry over all present subscribers)? > > I think this is absolutely a solid idea. It makes it clear that this is a > development list rather than a general list. > This was also discussed in our meeting but again we decided against it for now anyway partly because in openSUSE since the dawn of time factory==devel. Again if enough people want this change as well we can look at it again in the future. * Yes mailing list threading is probably now broken from people replying on the wrong mailing list :-) -- 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

1 0

[opensuse-project] Leap 15 Release and Highlights from the openSUSE Conference
by ddemaio 28 May '18

28 May '18

Hi everyone, It was a long and productive weekend. I wanted to point out the release of openSUSE Leap 15 and some highlights from this weekend's openSUSE Conference. We released openSUSE Leap 15 on Friday. The release was announced on various social media, on news.o.o at https://news.opensuse.org/2018/05/25/based-on-enterprise-code-tested-millio… and by the various media organizations. Ludwig released Leap 15 with a nice touch of a button https://twitter.com/binary_sequence/status/999959373370871810. Let us amplify the release by sharing the post and talking its release. I want to thank the video team and c3voc for once again providing great videos and streams of the conference. The put forth a lot of effort at all the conferences they do and we are very thankful for their time, professionalism and efforts that enhance the openSUSE Conference. Another big announcement that you might have missed was the announced fork of spacewalk - https://news.opensuse.org/2018/05/26/uyuni-forking-spacewalk-with-salt-and-…. You can see the talk about it here - https://youtu.be/8EYYNtOTmhc We also had a night present for the GNU Health Project. The openSUSE Project donated 10 Raspberry Pi's to the GNU Health Project - https://news.opensuse.org/2018/05/26/opensuse-donates-10-more-raspberry-pis…. Andy presented the gift at the beginning of Luis' talk https://youtu.be/uUnd4yrvdwY We had lighting beer talks for the first time and it was real success. I was a blast and we should do it again. Thank you Ana and thank you Andy for https://twitter.com/sysrich/status/1000404597935091712 portraying releases of SUSE and openSUSE represented in interpretive dance. The board was introduced to the community at the conference. The discussion went well and you can view it at https://youtu.be/AI0TQckPrLw. TUXEDOComputers donated an InfinityBook Pro 13, which you can not order online with Leap 15 preinstalled, and one happy attendee received it during the conference - https://twitter.com/openSUSE/status/1000747063716524035 On behalf of the project, I would like to thank our sponsors SUSE, arm, ownCloud, MySQL and TUXEDOComputers for their continued support of the openSUSE community and the openSUSE 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

1 0

[opensuse-project] Github: please allow Codecov.io
by James Mason 21 May '18

21 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello github/opensuse maintainers: Osem has moved from coveralls.io to codecov.io for analysing code coverage (as coveralls has poor support for paralellized test suites, and well, just doesn't report status reliably). Please enable codecov.io to submit status to the openSUSE organization: https://github.com/organizations/openSUSE/settings/installations/16908 Thanks, - -- James Mason <jmason(a)suse.com> SUSE -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEg/RjZ+RraZBnLRN4GzlRiGxEkCMFAlsC9zEACgkQGzlRiGxE kCO29gf/X4+Jt8IBAGnT0uGykChW1NEzNb6l+Bd/KjNZ3Rfm7iGUHIPQlMZLz3J9 ACvl4j+1ScWON8v9/tXcFTKZLic8x2sTQBqiAYbdwQ2DNE+/0XCE3GHqzPC8Dnry INPV5B9WbnkYmmMIgC/A7GpS+E0pSGNCK7A0qZ+RHfqLboW+huufLAblL9oHQpMw 7NzNa/Gjjsn1IriJ5XHeu84veXIS4rverY/0ePpZWk4OtZna8hvJZuNSAq5Vtzlg OzFy+hG2NCNcx9bKfhZEN+BwMhQh42nRVDjY7Fnc5XJ5i9ftirlkDLYcdQqTUqET 08PthKNKco32+90cSSpIXaaL1eyztg== =VXD/ -----END PGP SIGNATURE----- N��r��y隊Z)z{.��k�7��맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.��k�7��0��Ǩ�

1 0

[opensuse-project] Board meeting 2018-05-15
by Ana Martínez 18 May '18

18 May '18

Hi! On Tuesday, 15th May 2018, took place the first meeting of the new openSUSE Board. # Attendees Ana Christian (his connection dropped and he didn’t participated in point 4) Gertjan Richard Sarah Simon # Agenda 1. Summaries of Board Meetings 2. Resolve old differences 3. F2F Board Meeting 4. GDPR and TSP email from KDE ## 1. Summaries of Board Meetings Ana proposed that the Board take its habit of writing summaries of the meetings up. All of the members agreed. From now on (including this meeting) a summary of the meeting will be written and shared with the community. Every time a different member will write the summary and we will rotate alphabetically: Ana, Christian, Gertjan, Richard, Sarah and Simon. ## 2. Resolve old differences There was some old differences between some board members which needed being discussed. All the the Board members gave their opinion and an agreement that allows them to keep working in a friendly environment was reached. ❤❤❤ ## 3. F2F Board Meeting The Face to Face Board Meeting will take place on Prague from 2018-05-22 to 2018-05-24, where the new Board will discuss, plan and start driving it's collective agenda. The outcome of this meeting will be presented in the Annual Discussion with openSUSE Board during the openSUSE Conference: https://events.opensuse.org/conference/oSC18/program/proposal/1939 All Board members will attend this meeting completely, with the exception of Sarah, who due to her university commitments will only join in person on the 22nd and via video conference for the remaining days when she is available. Next online meeting is moved to 2018-06-05. ACTION: Ana creates and shares a document so that all Board member can add their topics for the F2F meeting. ACTION: Richard changes the automatic reminder for the next meeting. ## 4. GDPR and TSP email from KDE The Board received an email from the KDE e.V. Board asking if we know if how GDPR affects the TSP installation. Nobody in the board is sure of the answer. ACTION: Richard asks the legal team in SUSE. ACTION: Richard writes KDE e.V. Board back with an update You can also find this summary in our Wiki: https://en.opensuse.org/Archive:Board_meeting_2018-05-15 Future summaries will be linked from: https://en.opensuse.org/openSUSE:Board_meeting 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

1 0

[opensuse-project] The CFP for All-Systems-Go 2018 is open
by ddemaio 16 May '18

16 May '18

Hi all, I wanted to let you know that the CfP for All-Systems-Go 2018 is open. openSUSE is a sponsor again this year. If you plan on attending, let me know. It would be great to some submissions. Submit your proposals for consideration to the CFP submission site - https://kinvolk.us14.list-manage.com/track/click?u=1357cb4149750098f861b3a0… The CFP will close on July 30th. Notification of acceptance and non-acceptance will go out within 7 days of the closing of the CFP. Presentation Topics All topics relevant to foundational open-source Linux technologies are welcome. In particular, however, we are looking for proposals including, but not limited to, the following topics: * Low-level container executors and infrastructure * IoT and embedded OS infrastructure * BPF * OS, container, IoT image delivery and updating * Building Linux devices and applications * Low-level desktop technologies * Networking * System and service management * Tracing and performance measuring * IPC and RPC systems * Security and Sandboxing While the focus is definitely more on the user-space side of things, talks about kernel projects are welcome, as long as they have a clear and direct relevance for user-space. v/r Doug -- 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] Leap 15 Social Media Posts & Translations
by ddemaio 16 May '18

16 May '18

Hi all, I know not everyone is signed up to the translations email list, but I figured I would send it to the projects as well as many of us speak multiple languages. We have a few social media posts we would like to put out in multiple languages and it would be great if you would translate them on the wiki at https://en.opensuse.org/openSUSE:Social_media_launch_plan and post them in your local language at at the corresponding time. Thank you for any help you can provide. I'll also add this info to a news article I'll post tomorrow about the countdown banner and release parties. v/r Doug -- 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] Elections Results
by Kostas Koudaras 14 May '18

14 May '18

Hello people of openSUSE after the longest election period in the history of the project elections ended in a successful way. 237 people voted out of 400 which is a record of participation both in percentage and in actual number. It was the first year we attempted to vote through Helios Voting System and we solved all problems that came to our attention. I must say that although the work of the election committee ends somewhere around here the new elected members have a long way ahead of them and us as the election committee wish them all the best. With no further delay I present you the results of the elections for 2018: Gertjan Lettink (Knurpht) 166 Simon Lees 133 Ana María Martínez 185 Gerry Makaro (Fraser_Bell) 98 Aaron Luna 72 The First three: Gertjan Lettink (Knurpht),Simon Lees and Ana María Martínez,will serve a two year term. Best Regards Kostas "Warlordfff" Koudaras -- --- \m/ --- If you're not failing every now and again, it's a sign you're not doing anything very innovative. --- \m/ --- me I am not I --- \m/ --- Time travel is possible, you just need to know the right aliens -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

13 19

[opensuse-project] Event Report: LinuxFest Northwest 2018
by James Mason 14 May '18

14 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi All, LinuxFest Northwest took place the last weekend in April, the 28th & 29th, in Bellingham, WA USA. The free, open source and data privacy oriented confererence, for which openSUSE was once again a Gold Sponsor, drew a crowd of 1600+ people this year. Internally, this biggest changes for LFNW this year included the retirement of some long-time staff, and the onboarding of more partner- teachers from Bellingham Technical College; the event's host. The new organizing board was able to move swiftly and make some structural changes that will benefit the event for years to come; most notably switching from the poorly maintained COD module for Drupal, to OSEM, which the LFNW organization has contributed 96 commits, and nearly 5K LoC. Externally, LFNW made stronger inroads into social media, and has gone from nearly zero, to > 1000 Twitter & Facebook followers. As a direct result, individual sponsorship of the event has grown significantly, allowing the event to maintain it's "fully free" stance of not requiring registration or any attendance fee for participation in sessions and the expo hall. We had more diverse speaker group, from highly experienced speakers to ~20 first-time speakers. Survey results showed a 97% positive rating overall, 91% relevant to work, and 100% (!!!) positive to session content. With an established program, LFNW will go into it's 20th year, next year, with a strong focus on refinement of what works, and tuning of what didn't (registration is, and probably always will be, a headache). No... to more openSUSE specific; I'll defer to Carl Symons and Adrian Klaver, openSUSE volunteers who organized and staffed our minisummit and expo hall booth, respectively: openSUSE mini-summit at LinuxFest Northwest April 29, 2018 The mini-summit was intended to be an opportunity for openSUSE supporters to get together at LinuxFest Northwest (LFNW). Presentations were unnecessary as LFNW already had a full schedule, including several talks related to openSUSE. Although pre-registration was set up at events.opensuse.org, registrations there were scanty. We were much more successful getting people to participate by talking with them during the first day of the Fest. So rather than having the mini-summit be a branded destination, it was more of an adjunct event with LFNW … come to LFNW, the original grassroots FOSSFest, and see openSUSE at the Expo and the mini-summit. On Saturday, April 28th, activity centered around the openSUSE Expo booth where people were told of the openSUSE activities the next day. We gave t-shirts to people who use and support openSUSE. We asked that people wear the t-shirts the following day and join us on Sunday. A word about the shirts—bright. Also distinctive and all gone. Several people commented that the Alex Geeko logo was Best of Show. Many thanks to Doug DeMaio for designing them and sending to us. The fluorescent green shirts were highly visible throughout LFNW on Sunday. Adrian Klaver organized and managed the Expo booth. For the mini-summit, LFNW organizers gave us a hacker space classroom with wired access. We also commandeered the Haskell Atrium adjacent to it. It was a friendly space where people discussed ideas and talked about the upcoming LEAP 15 release. We gave away some plushy Geekos on Saturday, and handed out many more on Sunday. There was a drink dispenser with cold Lizard Sweat (Margarita mix & water). We also dealt with problems people were having with openSUSE, and did a few fresh installs. All issues were resolved with assistance from a group of eager helpers. The relationship between the various SUSE distributions was explained several times. Both SUSE customers and openSUSE users were interested to hear about enterprise SLE+community openSUSE+stable LEAP +experimental Tumbleweed+well-tested openQA. The openSUSE mini-summit was mostly an informal gathering of openSUSE users and an opportunity to share information about openSUSE. It worked well in conjunction with LFNW because the Fest attracts people from throughout the western U.S., including many openSUSE users. The distinctive shirts and BoF-like meeting highlighted the involvement of openSUSE. Many thanks to James Mason for his leadership and work on the mini- summit, the openSUSE booth and on LinuxFest NW itself as an Organizer and main Web-ster using and improving OSEM. - - Carl Symons LFNW 2018 Booth Report Thanks to James Mason, Bob Potter, Carl Symons and Josephine Hollandbeck for working as booth volunteers over the two days of the Fest. The booth received many visitors over the two days of the conference. Quite a few of those indicated genuine interest in trying openSUSE, especially newcomers to Linux. The distinction between a stable version(Leap) and a rolling release(Tumbleweed) seemed to resonate with folks. The Linux Magazine with the openSUSE Leap 42.3 DVD where a big hit. So for that matter where the Geeko stuffed toys. Having SUSE employees in attendance worked out well. There where more then a few people that wanted toand did talk to them on matters business and community related. All in, interest in openSUSE/SUSE was there and was returned by the volunteers. - - Adrian Klaver As you can see, the Pacific Northwest includes a growing complement of dedicated openSUSE volunteers, who are enthusiastically joined by a few members of SUSE staff each year (this year we were thankful to see so many members of the docs team ) who help answer questions and guide the event's curious attendees. I hope openSUSE continues to foster this relationship by sponsoring future LFNW events, and as a result we will see our support, and our volunteership, grow! - -- James Mason <jmason(a)suse.com> SUSE -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEg/RjZ+RraZBnLRN4GzlRiGxEkCMFAlr5qaoACgkQGzlRiGxE kCPsPgf9Greqcco9tsp3NcWdtl8bjkKFoSpxkmKSroz7QnJCI7RX+ck4X8yGYSMs pCkutSRnRdaCfx18V6Z6e0LAmehCL8UeedZ1G6d5sRWzga97c8I/zZ3fj1hNx47a bsM4FrPW4+NUQnLohXtvBDH7+znyGWsCDk+UXuJeCIQI3fR+IF2ntWu3iU/Xazh8 e9OnrNpPtiDq4k8LfUtbjXAhfqnOFQGQN35LHOogfBCfHK1Il6nAQdWXz0wxB/cB aoTfhO+O65LL8DkZd3Ffy9h8kQgjLG8aj1L1cK/fK9Sch/9iVzcZn0krWQDaCE87 388BgaVnVCtLnwCHAmhyPNEm8UXokQ== =jlFu -----END PGP SIGNATURE----- N��r��y隊Z)z{.��k�7��맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.��k�7��0��Ǩ�

1 0

[opensuse-project] Features for Leap 15
by ddemaio 14 May '18

14 May '18

Hi all, The release of openSUSE Leap 15 is scheduled for next week. Please consider adding features and screenshots to the wiki. Some features are already listed on https://en.opensuse.org/Features_15.0 but there is certainly room for more. There are some screenshots already updated from 42.3 to 15 on https://en.opensuse.org/Portal:15.0/Screenshots. Please consider updating the screenshots for the ones that still show 42.3. v/r Doug -- 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] openSUSE Leap 15 Release Announcement Translations
by ddemaio 07 May '18

07 May '18

Hi all, So we are a few weeks away from releasing openSUSE Leap 15. I have placed the release announcement on the openSUSE wiki at https://en.opensuse.org/Release_announcement_15. It would be highly appreciated if you could help to translate the release announcement to your native language to help propagate the news of our next release. Currently there are English and Deutsch versions linked to the release announcement. Feel free to link your translated version to the top and include your ISO 639-1 Code language code. If you have any questions, please let me know. v/r Doug -- 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] Fwd: Re: Big Data Day Sponsorship Prospectus
by ddemaio 07 May '18

07 May '18

Hi all, I was asked to forward this info about Big Data Day LA 2018. openSUSE is a partner sponsor of the event and we plan on having a booth there. Email me if you want to help run the booth. Call for Speakers, Sponsors and Volunteers Big Data Day LA 2018 is scheduled for Saturday, August 11th, 2018 at the University of Southern California. We are now opening up calls for speakers, sponsors and volunteers. We look forward to hearing from you! OPEN CALL FOR 2018 TECH TALK SPEAKERS Do you have something interesting to share with your fellow data technologists? We are looking for proposals for tech talks of 40 minutes in length including Q&A. The deadline for submissions is June 15th, 2018. Here are the 2018 tracks: * Data - Big Data, Databases/RDBMS, Hadoop/Spark/Kafka, NoSQL/NewSQL and other technologies that support databases, and data storage * AI / ML / Data Science - Artificial Intelligence, Machine Learning, Data Science, Data Analytics, Data Analysis methods and applications * Emerging Tech - Blockchain, IoT, Serverless, AR/VR and other new and emerging technology * Infrastructure & Security - DevSecOps, Security, Data Governance and Privacy * Visualizations / UI / Use Cases - Data Visualization, User Experience / User Interface developments with respect to data, and real world applications Please submit your proposal via the Tech Talk Proposal Form <https://www.bigdatadayla.com/#speakers> on the Big Data Day LA site. The are looking for volunteers to help run the event. If you are interested, complete the form at https://goo.gl/vVzg9c <http://bigdatadayla.com/#volunteers>. v/r Doug

1 0

[opensuse-project] Volunteers for openSUSE Conference 2018
by Petr Hodac (Hody) 04 May '18

04 May '18

Hello, The openSUSE Conference 2018 in Prague (May 25 - 27) is coming and we are looking for volunteers that would help us with organizational tasks. If you are interested, please register yourself via the following form: https://bit.ly/2JOsxUt Thanks for your help and have a lot of fun <(") Hody University coord.

1 0