August 2022 - openSUSE Project - openSUSE Mailing Lists

[Notice] - openSUSE Regular Board election 2021
by Ariez Vachha - openSUSE 01 Nov '22

01 Nov '22

Dear openSUSE members, openSUSE Board Election 2021 [1] It's time to elect new Board members to fill empty seats on the openSUSE Board. There are two seats for election in accordance per our normal election cycle. This is a regular election as defined in our Election Rules [2] ## Phase 0 01 November 2021 - Announcement of the Board Election 2021 - Call for Nominations and Applications for Board candidacy - Membership drive 22 November 2020 - Nominations and Applications for Board candidacy close ## Phase 1 22 November 2021 - Announcement of the final list of candidates - Campaign begins - Membership drive continues, opportunity to apply for openSUSE Membership, but members will only be eligible to vote and not run as a candidate ## Phase 2 13 December 2021 - Ballots open: Please cast your vote during this time - Campaign continues 30 December 2021 - Ballots close 31 December 2021 - Announcement of results To stand for a position in the openSUSE Board please send an email to: * project(a)lists.opensuse.org and * election-officials(a)lists.opensuse.org If a member would like to nominate another member, please inform the Election Committee and the officials will contact the nominee to ask whether they would like to run as a Board candidate. Only openSUSE members are eligible to run for openSUSE Board openings in accordance with the Eligibility and Validity section of our Election Rules [2]. The Election Committee [3] are hereby calling for Nominations & Applications for the openSUSE Board. [1] https://en.opensuse.org/openSUSE:Board_election [2] https://en.opensuse.org/openSUSE:Board_election_rules [3] Members: Ish Sookun, Edwin Zakaria and Ariez Vachha. -- Regards, The Election Committee election-officials(a)lists.opensuse.org

3 5

Community Meeting/ALP WG: Week 35
by ddemaio 29 Aug '22

29 Aug '22

Hi all, The ALP Work Group (WG) will take place tomorrow at 14:30 UTC. No specific topic is planned as we are waiting on some responses from people on holiday. The Community Meeting will be on Thursday at 19:00 UTC. We went over the asknot-ng section and will continue to expand on that. Both meetings will be in https://meet.opensuse.org/meeting You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. v/r Doug

1 0

Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)
by openSUSE Meeting Reminder 27 Aug '22

27 Aug '22

Hello all, The biweekly board conf call will be held in two days at 13:00 Europe/Berlin time (CET = UTC+1) Meeting will be in the regular Board Meeting Room https://meet.opensuse.org/OSBoard Current Topics: https://code.opensuse.org/board/tickets/issues?status=Open&tags=meeting Board Members: If you cannot participate, please advise by replying to this mail.

1 0

redirect connect-o-o to useful page
by Marcel Richter 24 Aug '22

24 Aug '22

hi, connect is dead, the subdomain still exists and could be useful. the subdomain should redirect to https://en.opensuse.org/openSUSE:Communication_channels or build a page like a linktree with similar Informations how new users can connect to the community. v/r marcel

2 1

Community Meeting/ALP WG: Week 34
by ddemaio 22 Aug '22

22 Aug '22

Hi all, The ALP Work Group (WG) will take place tomorrow at 14:30 UTC. I'm still waiting on info from our meeting last week, so I don't have any update on the topics listed on https://etherpad.opensuse.org/p/weeklymeeting20220816 The Community Meeting will be on Thursday at 19:00 UTC. Part of the plan will be to update some yml for asknot-ng. Both meetings will be in https://meet.opensuse.org/meeting You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. v/r Doug

1 0

Concern for open-source to consider
by doug demaio 18 Aug '22

18 Aug '22

Hi all, I am writing this email to the project to bring your attention to a troubling situation that has implications for the free open-source software community. Three related events took place last week that I believe threaten the open-source movement, restrict the freedom of expression of developers through code, and put us in a position to consider alternative solutions to approaching authoritarian constructs. Firstly, last week, the United States Treasury’s Office of Foreign Assets Control (OFAC) sanctioned open source software Tornado Cash. Make no mistake, this was a sanctioning of a technology. Writing code is a freedom and we as an open-source community value the freedoms to use, share, study, modify and share code. I don’t believe any of us want this freedoms to be taken away. In Bernstein vs. US, courts long ago that code is speech and is protected by the First Amendment. I realize we are a global community and US laws don’t apply to everyone, but it can influence and actions do extend beyond boarders, which led to the second and third events. GitHub removed the account of the code and removed its developers. [1] These developers were de-platformed from GitHub based on OFAC's whim. This brings up an important question. Should our community begin to think about alternatives to these source code hosting services like GitHub and GitLab? They are both companies and they do conform authoritarian constructs regardless of legal precedent. In this case, it proved to be not a private company decision based on media reporting, but a decision based on the repercussion from OFAC, which is very powerful if you know anything about financial authorities. I believe it is worth discussing the possibility of finding a decentralized solution. This event could provide that push we need to adjust the way we move the project forward. I understand we can host code ourselves, but believe joining an established decentralized solution would lower the attack vector of a single solution and allow for us to join a larger community that shares the same principles and values toward the freedoms of open-source software. The third event was that Dutch authorities arrested the developer Alexey Pertsev. There is little information about his arrest, but it appears to be done to intimidate developers from expressing their freedom to develop free software. Maybe more will come out, but this situation instantly brought back memories of Aaron Swartz.[2] My hope is that it does not end up like the way it did with him. The FSFE, FSF and Open-Source Initiative are organizations we have established that would help us in a similar situation. I hope that stand up and defend this developer given the situation aligns clearly with these organizations' purpose. Do you think there is a collective document we should create or something else that can be done for us to collectively voice our views on this overreach? Maybe even creating some sort of Developer Freedom pin that helps us establish a movement when things like this happen. It seems to be a repetitive thing, and maybe we should prepare for this. I ask that each of you voice your concern about the above situation to these helpful organizations if you would like to help. Questions Rephrased: 1. Should we begin to think about alternatives to source code hosting services like GitHub and GitLab? 2. Do you think there is a collective document we need or something else we can do to voice the views on this subject? I hope people find this information useful, discuss it and express their opinions in a manner where we can find an actionable response to this overrearch. I believe it is in the interest of the openSUSE Project, and other projects and organizations to collectively stand up together and voice an opinion that we reject these efforts to censor open-source code. [1] - https://www.theregister.com/2022/08/10/github_tornado_cookies/ [2] - https://youtu.be/vy9tSaZFlPI?t=43 v/r Doug

15 36

[opensuse-project] https://en.opensuse.org/SDB:Login_as_root RE: GDM
by Felix Miata 17 Aug '22

17 Aug '22

Some distros put GDM and Gnome on tty1 instead of tty7, e.g. RedHat/Fedora, home of systemd & Lennart Poettering (or at least used to be before his hiring by Microsoft). Is openSUSE one of them? I never install GDM or Gnome, so don't know, but recommendations in various docs, e.g. $SUBJECT, to open a tty via Ctrl-Alt-F1 need adjustment if the answer is true. Ctrl-Alt-F6 may now be the better recommendation. As I understand it, when GDM is on tty1, it sometimes also ties up tty2. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

1 0

https://en.opensuse.org/Portal:Teams
by Gerald Pfeifer 16 Aug '22

16 Aug '22

Hi folks, by chance I ran into https://en.opensuse.org/Portal:Teams and noticed a couple of oddities (= historical artefacts?) * There is a team "Community Council" listed, which "Solves internal and external conflicts and communication issues". I never heard of that, and indeed following the link it ... redirects to the Board page. => This team best should be removed to reduce possible confusion, alas I don't know how to? The page appears to be generated automatically? Who can help? * The "openSUSE team at SUSE" as such does not exist any longer. And the links is borken. => Same as above; how do we get rid of that entry on that page? * Ditto for https://en.opensuse.org/openSUSE:Openfate_screening (which should be removed) and its entry on that page under the label of "openFATE screening". Any help (or pointers) would be lovely - thank you! Gerald

2 2

Board Meeting Monday 2022-08-15 13:00 CEST
by Axel Braun 16 Aug '22

16 Aug '22

= Board Meeting Monday 2022-08-15 13:00 CEST = * Present: Gerald, Axel, Mau * Guests: Doug, Emily, Luna/bittin * Excused: Attila, Syds == openSUSE.Asia Summit: questions from organizers == * https://code.opensuse.org/board/tickets/issue/50 * https://groups.google.com/g/opensuseasia-summit/c/K-IIGC6SZms * AI Doug: respond re sponsoring * AI Mau:: check with Attila about co-presenting a keynote at Asia summit. Mau 50/50 maybe traveling * AI Gerald: respond that Mau/board are looking into == openSUSE moderation Team update == * Announcement and community meeting presentation postponed. WIP. No update at the moment == Tornado Cash situation and the consequences it could have for Free Software/openSUSE == * Discussion about the specific issue and whether/how to respond as project. * Next step: send an email to project@ ML to inform about what happened and the consequences to free software, to start a discussion also about GitHub and source code infrastructure. * Doug agreed to write such a email: * https://lists.opensuse.org/archives/list/project@lists.opensuse.org/thread/ SBZ3NSI27TN5WBJRIU6UJSHER3XLHO3M/ * Axel is talking with the FSFE * Big thanks to Doug for raising this! == openSUSE Foundation? Update == * Patrick sent an email with a number of good data point. * Gerald will answer with a follow-up thoughts, questions,..., hopefully getting more discussion going. Meeting closed at 13:48 CEST

1 0

Helping contributor onboarding with a new website
by Jacob Michalskie 16 Aug '22

16 Aug '22

Hi! A while back, a group of contributors was planning to take care of adapting asknot-ng, a Fedora application powering whatcanidoforfedora.org, for use by the openSUSE Project. That did not happen, so I decided to take it upon myself to get it going. However, I don't know everything that happens within the project, or how much everything within the project works, as much as I would like to, so I need some help with finishing this task. # How does asknot-ng work? asknot-ng works by providing a tree of choices, which it then uses to point people in a direction of things to do within a project. The tree is composed of a few layers of categories (as many as required by the branch) which always results in some link the person can follow to learn more about contributing to a certain part of the project. # How to help out with this task? If you are a person currently responsible for or know how to contribute to something within the project, we would most likely want to include you in this. There are a lot of ways to contribute, and individually we can't know them all, but all together we can find out ways to reach contributors and for the contributors to reach us. If you are just a contributor, that has been interested in contributing to a certain part of the project but couldn't figure it out, we would like to hear from you as well. I'm sure we will not get a full coverage from just the contributors here, so your feedback is essential for us to be able to reach out to the right people we might have not considered. # What are the requirements for inclusion? As you may be aware, some of the stuff that is developed within the openSUSE Project, or closely associated to the project, has guides helping out the new contributors to be able to contribute to it. In some cases that is CONTRIBUTING.md document in the root of a git repo, in others it's a wiki page like How to contribute to Factory, which is likely pretty well known to anyone that has ever pushed anything to Factory. This kind of documentation is something which we would like to help you develop for your branch of contributions, so that other people can help out in a more meaningful way. There are plenty of helpful resources for writing good contributing guides on the internet[1], though a lot of them apply to code and not necessarily to other forms of contributions. Remember that any contributor can be a newcomer, and may not necessarily understand things that may be obvious to you, and may want to use your repository as their learning experience. Explaining how things come together is one of the primary things that have to be written down. Ruby on Rails application repository doesn't look like a Ruby on Rails application repository to somebody who has never seen one, and even when using Weblate, it's easy to get lost when you first get started. For software development, we don't want to link people directly to git repos, because even if they are more familiar with concepts like git, programming languages and have coded before, contribution guides explain how the repo in particular is developed, how to test and run software, and what to consider before creating a pull request. For other forms of contributions, just linking to a homepage is not exactly helpful, we still want to explain how and why to contribute. It's really important to include some form of contact (mailing list, matrix, irc) to the maintainers and developers of the project. Projects not directly under openSUSE, but related to it in significant way (like KDE or GNOME upstreams for example) also count as something we would like to have included. # I have the guide now, how do I include it? If you don't want to mess around with editing yaml files, feel free to create an issue on asknot-ng GitHub page[2] or get in contact with us with methods listed below. If you do want to contribute more directly, there are example yaml files from Fedora side of things already[3], while the openSUSE ones[2] are a little bit empty. The existing content in the openSUSE yaml files is not final, I just wanted to get the website working, so feel free to either add your contribution based on the existing branches, or create a new one. The fact that your project is currently listed doesn't mean it will stay that way then, it may just be a placeholder. If you would like to know our opinion on this before you PR, we have the contact info listed below. Do not worry too much about images, I will likely be going over them later anyway, and will create whatever ends up being required. # Where will this be hosted? Currently the plan is contribute.opensuse.org, I have already submitted an MR to host it on our pinot machine, and it's being reviewed. It will likely come up online in the next couple of days for preview purposes, while we work on adding content. # How do I get in contact with you? There are a few ways: * GitHub issues on asknot-ng repo[2] * #web:opensuse.org on matrix * #web on discord.gg/opensuse * web(a)lists.opensuse.org mailing list * #opensuse-web on libera.chat [1] https://mozillascience.github.io/working-open-workshop/contributing/ also includes follow up resources [2] https://github.com/openSUSE/asknot-ng [3] https://github.com/fedora-infra/asknot-ng/blob/develop/questions/fedora.yml https://github.com/fedora-infra/asknot-ng/tree/develop/questions/includes/f… LCP [Jake] https://lcp.world/

1 0