October 2016 - 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] 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] Social Media Plan for openSUSE Leap 42.2
by Douglas DeMaio 10 Nov '16

10 Nov '16

Hi all, We are nearing the release of openSUSE Leap 42.2 and we encourage everyone reading this email to help promote our newest release, however you want to do that. To help promote it, our marketing team has been brainstorming a few ways to promote it. One of those is to post messages on social media. The social media plan is updated in English at https://en.opensuse.org/openSUSE:Social_media_launch_plan Please consider translating it and posting it to your local or region openSUSE pages/profiles as well as to your own personal pages. We also encourage you to come up with your own tweets, posts, etc and just tag #openSUSE. Additionally, if you are interested in translations contributions, we would certainly welcome contribution to the project. With https://l10n.opensuse.org/, you can easily help translate release notes for 42.2 - https://l10n.opensuse.org/projects/release-notes-opensuse/leap_42_2/. I want to thank our contributors who have already translated the release notes. Also, please consider translating our landing page - https://l10n.opensuse.org/projects/landing-page/master/ There are more than 50 languages offered to translate and the dashboard gives an easy overview of what languages have been translated and those that could use translations. v/r Doug -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

14 17

[opensuse-project] SUSE Studio build broken?
by Jim Henderson 27 Oct '16

27 Oct '16

Just wondering if anyone on the SUSE side of things knows if there's a known issue with builds on SUSE Studio. It looks like it doesn't affect all builds - but largely affects SLE builds from what I can see. I've got some older openSUSE projects that do seem to build, but SLES12SP1, SLES12, and SLES11 don't seem to be working for me. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 5

Re: [opensuse-project] Social Media Plan for openSUSE Leap 42.2
by Nick Mantas 27 Oct '16

27 Oct '16

Greek translation is done 2016-10-26 12:01 GMT+03:00 Nick Mantas <nmantas.archery(a)gmail.com>: > Greek Translation is done > > 2016-10-25 22:48 GMT+03:00 Knurpht - Gertjan Lettink <knurpht(a)opensuse.org>: >> >> Dutch translation done. Let's get it on. >> >> Gertjan Lettink, a.k.a. Knurpht >> >> openSUSE Board Member >> openSUSE Forums Team >> >> Op dinsdag 25 oktober 2016 11:37:16 CEST schreef Douglas DeMaio >> <ddemaio(a)suse.de> : >> >> > Hi all, >> > >> > We are nearing the release of openSUSE Leap 42.2 and we encourage >> > everyone reading this email to help promote our newest release, however >> > you want to do that. To help promote it, our marketing team has been >> > brainstorming a few ways to promote it. One of those is to post messages >> > on social media. The social media plan is updated in English at >> > https://en.opensuse.org/openSUSE:Social_media_launch_plan >> > >> > Please consider translating it and posting it to your local or region >> > openSUSE pages/profiles as well as to your own personal pages. We also >> > encourage you to come up with your own tweets, posts, etc and just tag >> > #openSUSE. >> > >> > Additionally, if you are interested in translations contributions, we >> > would certainly welcome contribution to the project. With >> > https://l10n.opensuse.org/, you can easily help translate release notes >> > for 42.2 - >> > https://l10n.opensuse.org/projects/release-notes-opensuse/leap_42_2/. I >> > want to thank our contributors who have already translated the release >> > notes. Also, please consider translating our landing page - >> > https://l10n.opensuse.org/projects/landing-page/master/ >> > >> > There are more than 50 languages offered to translate and the dashboard >> > gives an easy overview of what languages have been translated and those >> > that could use translations. >> > >> > v/r >> > >> > Doug >> >> -- >> Gertjan Lettink, a.k.a. Knurpht >> >> openSUSE Board Member >> openSUSE Forums Team >> -- >> To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org >> To contact the owner, email: opensuse-project+owner(a)opensuse.org >> > > > > -- > Nick Mantas -- 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

[opensuse-project] Screenshots for 42.2
by Douglas DeMaio 26 Oct '16

26 Oct '16

Hi all, If you are running 42.2 RC1 and would like to help us get some screenshots for the wiki page, we would really appreciate it. There are already a few 42.2 screenshots on https://en.opensuse.org/Portal:42.2/Screenshots 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] Features list for openSUSE leap 42.2
by Douglas DeMaio 26 Oct '16

26 Oct '16

Hi all, Please consider adding any new features that will be included to openSUSE Leap 42.2 to the features page for the 42.2 Portal found at https://en.opensuse.org/Archive:Features_42.2 Once complete, the list will replace the https://en.opensuse.org/Features and 42.1 will be archived. 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] KIWI issue/question
by Axel Braun 25 Oct '16

25 Oct '16

Hi all, I did not find a distinct kiwi mailing list in https://lists.opensuse.org/ so I try my luck here: I have run successfully the prepare step for a kiwi build, and now want to create the image: T520:~/image # kiwi -c /root/image/result/root -d /root/image/result/iso Oct-25 12:04:00 <1> : Description provides no MD5 hash, check Oct-25 12:04:00 <1> : Reading image description [Create]... Oct-25 12:04:00 <3> : Requested image creation with filesystem "clicfs"; but tool to create the file system could not be found. failed >From what I could find, the error should come up if no mkisofs or genisofs is installed T520:~/image # zypper se mkisofs genisoimage Repository-Daten werden geladen... Installierte Pakete werden gelesen... S | Name | Zusammenfassung | Typ --+-------------+--------------------------------------------------------------------+-------- i | genisoimage | A Program for Creating CDs in Linux | mkisofs | A program to generate an ISO-9660/JOLIET/HFS/UDF hybrid filesystem | package -> genisoimage is installed. The attempt to install mkisoimage causes a conflict: Problem: cdrkit-cdrtools-compat-1.1.11-21.4.x86_64 steht in Konflikt mit mkisofs, das von mkisofs-3.01-1.5.x86_64 zur Verfügung gestellt wurde Lösung 1: Folgende Aktionen werden ausgeführt: Deinstallation von cdrkit-cdrtools-compat-1.1.11-21.4.x86_64 Deinstallation von kiwi-desc-isoboot-7.03.68-8.1.x86_64 Lösung 2: mkisofs-3.01-1.5.x86_64 nicht installieren Any idea how to cotinue or work around the issue? Thanks Axel -- 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: [FOSDEM] [CFP] FOSDEM 2017 - Distributions Devroom
by Bruno Friedmann 24 Oct '16

24 Oct '16

I'm forwarding the call for Cfp for the distribution devroom. I'm looking forward to see nice talks about openSUSE ;-) ---------- Forwarded Message ---------- Subject: [FOSDEM] [CFP] FOSDEM 2017 - Distributions Devroom Date: lundi, 24 octobre 2016, 10.31:45 h CEST FOSDEM 2017 - Distributions Devroom Call for Participation The Distributions devroom will take place 4 February, 2017 at FOSDEM, in room K.4.601 at Université Libre de Bruxelles, in Brussels, Belgium. Distributions are more than just hosted collections of software from various upstreams. Each distribution is responsible for problem-solving in building, testing, and releasing software as well as managing the lifecycle of each application in the collection. Additionally, distributions do very important work in ensuring that various versions of upstream software work well together and can co-exist. Distribution are also, often responsible, for "de-vendoring" upstream software so that security fixes can be applied more quickly. We welcome submissions targeted at contributors interested in issues unique to distributions, especially in the following topics: - Managing Build/Test/Release processes around shared ideas and resources - Lifecycle management, especially in the areas of sandboxing, containerization, vendoring, and bundling - Distribution construction tools and infrastructure development and implementation (building, signing, testing, distribution, etc.) - Cross-distribution collaboration on common issues, eg: content distribution, infrastructure, and documentation - Working with vendors and including them in the community - Building trust and code relationships with the upstream components of a distribution and between distributions - The future of distributions, emerging trends and evolving user demands from the idea of a platform - The place of distributions in today's world (including concepts of containerization, IoT, etc.) - Onboarding new users and mentorship, facilitating technical growth within the contributor base - Solving traditional problems like package management, and content management (eg. rpm/dpkg/ostree/coreos ) - Integration technologies like installers, deployment facilitation ( eg. cloud contextualisation ) - Principals of Rolling Releases, Long Term Supported Releases (LTS), Feature gated releases, and calendar releases Ideal submissions are actionable and opinionated. Submissions may be in the form of 25 or 50 minute talks, panel sessions, round-table discussions, or Birds of a Feather (BoF) sessions. Dates ------ Submission Deadline: 25-Nov-2016 Acceptance Notification: 5-Dec-2016 Final Schedule Posted: 11-Dec-2016 How to submit -------------- Visit https://penta.fosdem.org/submission/FOSDEM17 1.) If you do not have an account, create one here 2.) Click 'Create Event' 3.) Enter your presentation details 4.) Be sure to select the Distributions Devroom track! 5.) Submit What to include --------------- - The title of your submission - A 1-paragraph Abstract - A longer description including the benefit of your talk to your target audience, including a definition of your target audience. - Approximate length / type of submission (talk, BoF, ...) - Links to related websites/blogs/talk material (if any) Administrative Notes ---------------- We will be live-streaming and recording the Distributions Devroom. Presenting at FOSDEM implies permission to record your session and distribute the recording afterwards. All videos will be made available under the standard FOSDEM content license (CC-BY). If you have any questions, feel free to contact the devroom organizers: distributions-devroom(a)lists.fosdem.org (https://lists.fosdem.org/listinfo/distributions-devroom) Cheers! Brian Exelbierd (twitter: @bexelbie) and Brian Stinson (twitter: @bstinsonmhk) for and on behalf of The Distributions Devroom Program Committee _______________________________________________ FOSDEM mailing list FOSDEM(a)lists.fosdem.org https://lists.fosdem.org/listinfo/fosdem ----------------------------------------- -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- 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] # Board Meeting Minutes
by Bruno Friedmann 09 Oct '16

09 Oct '16

I miss you so much :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0