July 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] In search for a new mailing list admin
by Henne Vogelsang 29 Jul '16

29 Jul '16

Hey, for the last 15 years or so I have been the admin of the openSUSE mailing list server taking care of the technical and social aspects of it. That means handling the postfix MTA, the MLM (mlmmj) and the web archive (mhonarc + swish-e + apache). The social aspects means support for using the service (using the ml, creating new lists etc.) and handling conflicts among users (enforcing rules, trolls etc.). In the light of the recent developments around this service I would like to find a replacement for this responsibility as soon as possible. Sadly this task is only doable by SUSE employees because of the server location :-/ If that is not a problem for you and if you are interested to learn more about this very important openSUSE service, please contact me. Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 6

[opensuse-project] Board Meeting Minutes - 25 July 1600 CEST
by Richard Brown 27 Jul '16

27 Jul '16

# Board Meeting Minutes 25 July 1600 CEST ## Present - Richard Brown - Chair - Bryan Lunduke - Kostas Koudaras - Gertjan Lettink - Andrew Wafaa (Treasurer) ## Absent - Tomas Chvatal - Work - Michal Hrušecký - Moving home ## General Items ### oSC 17 Partnerships oSC 16 was a great success in part because of the wide selection of interesting Keynote speakers and Partners involved in the conference. We want to build on that success, which means we need to start thinking about who to involve with oSC 17 already. Next Board Meeting will be focused on this, and we will be inviting both Roland Haidl (Director of Operations & Communities at SUSE) and Douglas DeMaio (openSUSE Marketing Manager) to discuss this with us. ### Mailinglist Moderation Tomas sent a formal warning to a misbehaving mailinglist poster. Warning recieved a mixed response from the contributor. Board decided to continue to encorage and positively reinforce good behaviour. ### TSP Lots of positive feedback from users of the TSP for oSC 16 One bit of feedback from SUSE's finance team - Please submit applications in only one currency AI: Andrew to discuss with Ancor about changing the application to stop 'split currency' applications. ### openSUSE Asia Board has confirmed the amount of SUSE's sponsorship for openSUSE Asia with the openSUSE Asia team ### Trademark Request The Board have heard from the members with the outstanding Trademark request. Local legal requirements complicate our proposed solution. Negotiations ongoing. ### Membership Tidyup No action as Michal is busy moving house ### Infrastructure The Board remains concerned about ongoing Infrastructure issues. Board notes that some efforts have been made to improve the situation with www.opensuse.org and other Provo hosted openSUSE services, but would like to see a sustainable long term solution. Recent changes to www.opensuse.org are still not deployed. The Board has noticed some progress on tickets to admin(a)opensuse.org. AI: Richard to continuing having regular meetings with Roland and Lars to drive progress in this area. ### SLE Packages The Board has spotted a number of cases in Leap 42.2 Alpha 2 where packages inherited from SLE are newer than the ones available in Tumbleweed or Devel Repos. Reminders seem to have helped, but problem still ongoing. AI: Richard to send both general and directed reminders internally at SUSE to remind them of the SUSE company policy to contribute to Tumbleweed before/in parralel/in sync with their work on SLE. ### KDE The Board is very pleased to see Plasma 5.8 has been declared an LTS release, but notices it's estimated release date is possibly too close to Leap 42.2 estimated release date to make it's inclusion easy. As an LTS Plasma release seems to be a natural choice for a distribution like Leap, the Board will happily support in any way it can, any efforts from both the openSUSE Project and upstream KDE to investigate whether we can somehow integrate Plasma 5.8 before the release of Leap 42.2. ## Action Item Review Due to the large number of action items, the progress of these will be split into 3 sections - DONE; This task is complete and will not be discussed in future meetings - WIP; This task is in progress, and will be discussed in future meetings - TODO; This task is still waiting for some progress by the Board ### DONE ### WIP Board + Ludwig to figure out what to do with all the Volunteers for the "openSUSE Release Team" *Richard & Ludwig to discuss* Board is discussing some ideas with our various Desktop Teams Michal is retiring connect.opensuse.org and doing the Membership tooling and maintenance. Tomas has talked with Craig about OBS team preparing the code for maintaner tidyup *Feature in OBS teams TODO* Bryan has started arrange informal exploratory discussions with ownCloud, nextCloud and Kolab about closer relationships. Had some good chats at oSC 16. *Bryan to keep driving* Kostas is reaching out to our few bloggers on lizards.opensuse.org about moving to other platforms. Richard has been talking to Douglas about the possibility of moving news.opensuse.org to a new blogging platform. Richard's personal blog is running a potential candidate (Jekyll with custom openSUSE theme. http://rootco.de ### TODO Board to request release-team(a)opensuse.org list for the Release Team Board to investigate alternatives for voting & membership management _To be done after the Membership Tidy Up_ Tomas will investigate Helios voting system for openSUSE Richard to review/tune up filtering in current system so trademark enquiries don't get lost Tomas will talk with Andrew and Marketing teams about possible Kickstarter Board intends to create a skeleton of the getting started guides to help people get started with Using, Joining, and Partnering with openSUSE -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 4

[opensuse-project] openSUSE.Asia Summit and LAS GNOME
by ddemaio 18 Jul '16

18 Jul '16

Hi all, I wanted to bring your attention to two events that are coming up. The openSUSE.Asia Summit (https://events.opensuse.org/conference/summitasia16) will be in Yogyakarta, Indonesia, Oct. 1 - 2. You can still submit talks until Aug. 3, which means you have 16 days left to submit a talk - https://events.opensuse.org/conference/summitasia16/program/proposal Also, openSUSE is sponsoring the Libre Application Summit hosted by GNOME (http://las.gnome.org) in Portland Sept 19 - 23. This is a new summit that focuses onevolving the desktop experience to match non-Linux platform competitors. If you want to help represent openSUSE at the summit, please email me. v/r Doug

2 1

[opensuse-project] Board Meeting Minutes - 11 July 1600 CEST
by Richard Brown 14 Jul '16

14 Jul '16

# Board Meeting Minutes 11 July 1600 CEST ## Present - Richard Brown - Chair - Michal Hrušecký - Bryan Lunduke - Tomas Chvatal - Gertjan Lettink - Andrew Wafaa (Treasurer) ## Absent - Kostas Koudaras - Sick ## General Items ### Devel Project Maintainers Board is concerned about reports from Package maintainers that their submissions are being ignored or over-ridden by Project Maintainers. The Board would like to remind Devel project maintainers are responsible for encoraging and supporting Package maintainers. Submitters should be supported, if their submission doesn't pass muster then teach them how to do it better, don't just reject it or replace it with your own (especially if your own doesn't resolve the issues the Package maintainer was trying to resolve) ### Mailinglist Behaviour AI: Tomas to send 1 formal warning to a misbehaving mailinglist poster. ### oSC 16 It was lovely, went really well, complete success. Thanks to all who made it happen. ### oSC 17 Board discussed and agrees that oSC 17 should hopefully occur in Nuremberg, during the first week of June. ### openSUSE Asia No news from the openSUSE Asia team, everything seems to be going smoothly. ### TSP All submissions who have returned receipts have been accepted. Still one outstanding. ### Trademark Request The Board have heard from the members with the outstanding Trademark request. Local legal requirements complicate our proposed solution. Negotiations ongoing. ### Membership Tidyup First and Second round of reminders are sent, some responses recieved, a few more days will be left AI: Richard to make openSUSE Emeritus group. AI: Mical to send the final warning and start migrating inactive members to the Emeritus group ### Infrastructure The Board remains concerned about ongoing Infrastructure issues. Board notes that some efforts have been made to improve the situation with www.opensuse.org and other Provo hosted openSUSE services, but would like to see a sustainable long term solution. The Board is also concerned by the long lead time on tickets to admin(a)opensuse.org. Richard had a meeting with Roland. Roland shares the Boards concerns. MicroFocus IT are not able to process requests in a timely manner, so SUSE IT are stepping up to replace some infrastructure which will be easier for the community to also maintain and support. AI: Richard to have regular meetings with Roland and Lars. ### SLE Packages The Board has spotted a number of cases in Leap 42.2 Alpha 2 where packages inherited from SLE are newer than the ones available in Tumbleweed or Devel Repos. Reminders seem to have helped, but problem still ongoing. AI: Richard to send both general and directed reminders internally at SUSE to remind them of the SUSE company policy to contribute to Tumbleweed before/in parralel/in sync with their work on SLE. ### KDE KDE are forming an Advisory Board. Board is nominating Antonio Larossa to represent openSUSE on this Board. We're very pleased to see Plasma start offering LTS releases with 5.8, which hopefully might smooth out some of the issues we've faced with KDE in Leap. ## Action Item Review Due to the large number of action items, the progress of these will be split into 3 sections - DONE; This task is complete and will not be discussed in future meetings - WIP; This task is in progress, and will be discussed in future meetings - TODO; This task is still waiting for some progress by the Board ### DONE ### WIP Board + Ludwig to figure out what to do with all the Volunteers for the "openSUSE Release Team" *Richard & Ludwig to discuss* Board is discussing some ideas with our various Desktop Teams Michal is retiring connect.opensuse.org and doing the Membership tooling and maintenance. Tomas has talked with Craig about OBS team preparing the code for maintaner tidyup *Feature in OBS teams TODO* Bryan has started arrange informal exploratory discussions with ownCloud, nextCloud and Kolab about closer relationships. Had some good chats at oSC 16. *Bryan to keep driving* Kostas is reaching out to our few bloggers on lizards.opensuse.org about moving to other platforms. Richard has been talking to Douglas about the possibility of moving news.opensuse.org to a new blogging platform. Richard's personal blog is running a potential candidate (Jekyll with custom openSUSE theme) http://rootco.de ### TODO Board to request release-team(a)opensuse.org list for the Release Team Board to investigate alternatives for voting & membership management _To be done after the Membership Tidy Up_ Tomas will investigate Helios voting system for openSUSE Richard to review/tune up filtering in current system so trademark enquiries don't get lost Tomas will talk with Andrew and Marketing teams about possible Kickstarter Board intends to create a skeleton of the getting started guides to help people get started with Using, Joining, and Partnering with openSUSE -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

5 9

Re: [opensuse-project] Board Meeting Minutes - 11 July 1600 CEST
by Henne Vogelsang 14 Jul '16

14 Jul '16

Hey, On 13.07.2016 19:51, Chuck Payne wrote: > I been helping with Facebook Page/Group, and the Mailing list. I do go > to show when people ask. I am wondering what else I could do? Let me know. You could for instance organize the collaboration around our social media accounts. Talk to the people that operate the accounts, analyze what we are currently doing, identify gaps, set goals and define a plan how to reach them. Then document all that so new people can join in and participate. Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- 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] My blog/writeup on oSC16
by Amey Abhyankar 14 Jul '16

14 Jul '16

Hello All, Feel free to read my blog/writeup on 'oSC16' = http://osc16germany.blogspot.in/ Once again thanks to TSP aka 'Travel Support Program' for sponsoring some part of my travel expenses. This was my 5th consecutive attendance. openSUSE conference is like a pilgrimage trip to me already. ^_^ Group photo of oSC16 = https://news.opensuse.org/wp-content/uploads/2016/06/DSC_0007_1.jpg Regards, Amey. -- 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] Notes from the oSC16 GSoC Meeting
by Henne Vogelsang 05 Jul '16

05 Jul '16

Hey Peepz, here are my notes from the GSoC Meeting we had during oSC16. 1. Introduction Round * Chris reminded us to do our Mid-Term evaluation! In the meantime all students have passed the mid-term, hooray :-) 2. Blogging * Ancor highlighted Martins blogging style with nearly daily posts about technical details. Check it out -> https://thingsofgeek.com/ Other blogs: * Matheus: http://msfernandes.github.io/ * Ana Maria: https://gsocwithopensuse.wordpress.com/ * Joaquin: http://joaquinyeray.me/ * Rishabh: https://rishabhstr.wordpress.com/ * Shalom: https://shalom7blog.wordpress.com/ * Ana reported she got visitors to her blog from countries she didn't know existed ;-) * Mentors agreed that blogging is an important skill to learn for Free Software hackers * We need to do a better job at distributing what is blogged. * Do weekly digests on news.o.o * Josef suggests to spread the blog posts to opensuse-project 3. Mentor<>Student Meetings * Josef likes daily Video calls * A telegram group works for Hernan/Artem + student * IRC for Chris/Henne + Ana Maria * Maybe additionally we need some place to hang out and talk to each other about real life? Something that is easier to operate than IRC. Chris & Henne will investigate. 3. What kind of support is missing for students? * More introduction to the general openSUSE community from the mentors. * Some introduction to the ways of Free Software. Like what are you expected to do. Commit early, often. What happens during code reviews etc. 4. Code reviews * Different types of comments, functionality vs. style * Josef suggests to be more verbose in in the beginning. More links to documentation, blog posts etc. * YaST uses different tags to signify importance of comments (NITPICK/NICETOHAVE) * Mentors should share their experience about code-reviews * Stella and Henne are a bit frustrated at the merge rate and think more merges would be a good feeling for mentors and students * Hernans team @SUSE assigns PRs to people and they are expected to review it within a day * In general we agreed that mentors need to share their experience and best practices about code-reviews more 4. How did students get involved in openSUSE. Why us? * Ana had a selection of 6 projects she liked and the friendliness of the OSEM community was the biggest factor for her decision * For Rishabh is was a senior student from his university that encouraged him to do Free Software in general and in the end it was Chris encouragement that sucked him in. * Stellas student is doing this as his mandatory practical training * Matheus said the main reason was 101.opensuse.org that pulled him in * Ancor used Chris slides in his own university to attract students https://speakerdeck.com/chrisbr/opensuse-101 * Everyone said that they feel that support from Universities about GSoC is lacking That's what I noted down, hope you like it! Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- 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] Stop the overstepping maintainers issue now
by Jan Engelhardt 01 Jul '16

01 Jul '16

I find it outrageous that the top-level maintainers of the build.opensuse.org project "games" have the audacity to remove maintainers from packages. It is the second time this has happened. And it is getting evermore unscrupulous. Concerning /games/grabpng, r5 | jengelh | 2016-06-30 19:33:43 CET | 643e6e9a47e99e0c1745b29da380db27 | unknown was placed. Minutes later, a competing SR was force-pushed by r6 | DarkSS | 2016-06-30 19:34:12 CET | d150387bd8be724af181ecd059c3246a | unknown | rq405768 The timely proximity makes this veer into a "oh well, happens" domain. BUT, OBS should have shown a merge conflict to start with, which would make this would instance 1 of overstepping. The SR was just an hour old, so here is also instance 2, aka. the year-long problem with trigger-happy prj-level maintainers. Using copypac to just get back r5, access rights get rescinded minutes later on the grounds of vandalism. Not only was this supposed vandalism not reverted, it indeed got submitted as-is by DarkSS to Factory and showing up in my review list, so this can only mean someone is pulling a really bad prank. As mail trickles in later, two OBS comments get delivered for asking for a specific procedure and a announcement of rights removal due to not heeding the procedure. In other words, DarkSS is also expecting people to read - and receive - mail in short intervals, ignoring the fact that interwebs do not always work that way. In all, this is unacceptable. The openSUSE Project is being asked to restore rights and take appropriate measures to turn off such behavior, because it is adversely affecting the project atmosphere. If your maintainer rights get revoked at any point in time for *acting* like a maintainer, who would want to stay with the openSUSE Distribution project? -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1