February 2025

spec file copyright headers
by Andreas Stieger 27 Feb '25

27 Feb '25

Hello project, I would like to raise for open discussion the rpm spec copyright headers. Let's use the following as an entry example to see if we can find an general opinion or solution. This should not be considered escalation on the SR. systemd maintainer Franck declined my SR#1232931 [1] for boo#1234765 [2] with the following note: > Thanks. Can you please resubmit without changing the copyright ? > Allow me to lay out the following thoughts: openSUSE packages are licensed and … [View More]distributed under an OSI approved license. Changes to the package by another party create derivative works. That copyright is not owned exclusively by the original creator, the part that the contributor added is owned by them. Or, verbatim from the standard header: > # All modifications and additions to the file contributed by third parties > # remain the property of their copyright owners, unless otherwise agreed > # upon. Many packages contain "Copyright (c) {{ year }} SUSE LLC" . The vim .spec template, spec-cleaner and the corresponding source service update this regularly. They also update the copyright year to the current year unless the right parameters are passed, and even so if no people employed by SUSE LLC are involved. My original packages contain my own copyright. As a contributor I am happy to license my works to anyone, including SUSE LLC, under an open source license. What I am not doing is assign exclusive ownership to SUSE LLC, neither for my original packages nor for my contributions. I believe this is in the spirit of FLOSS. We should clarify the obvious: assigning exclusive copyright to SUSE LLC is not a requirement for contribution for openSUSE, the text makes that clear. But there is no single best way to reflect that, and who owns what, if "SUSE LLC" keeps getting added, automatically, at the top (!), while we reject contributors adding their own. You can reject such submissions, what what message are we sending to openSUSE contributors that are not bound to assign their work to the company? The following points may need to be part of the discussion: Should spec-cleaner/format_spec_file have a mode, default, for non-SUSE contributors? Specifically, do not add the SUSE LLC copyright or update it's year unless the contribution is done on behalf of SUSE LLC. There may be a triviality limit for what constitutes a copyrightable contribution to an rpm spec, given that many constructs are trivial, tool generated, or copied from another package, distribution, or the wiki. There may be bit of a stylistic problem of proliferation of copyright lines. Changing/removal of any lines not your own should be avoided. The spec header refers to the license of the upstream package. Upstream packages are known to change licenses. That means that in these cases the license of the spec file changes, but the copyright holder can do that. And in the case of a community contribution, that is not "SUSE LLC" exclusively. Re-licensing this is different from creating a derivative work under a compatible FLOSS license. Finally, I do not want to leave you without a specific proposal. Here it is: > # Copyright (C) YEAR openSUSE project and contributors, see package > changelog. > Not the best idea, but one that includes the outside contributors. Happy to discuss, Andreas [1] https://build.opensuse.org/request/show/1232931 [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1234765 [View Less]

15 36

HAM radio and SDR in openSUSE
by Andreas Stieger 26 Feb '25

26 Feb '25

Hello project@, I wanted to give an brief update on recent activities on HAM radio related packages in openSUSE. We have revived the maintainers of the hamradio project, and came to a good arrangement between packages in the hamradio and hardware:sdr projects: The former for packages of general amateur radio usefulness, the latter focusing on support for software defined radio shenanigans and DSP. We updated project's user and developer documentation here: https://en.opensuse.org/Portal:… [View More]HAM_Radio Recently we brought some packages back up to date and added them to openSUSE Tumbleweed when they were ready. Some new packages we introduced or reintroduced: * xdemorse: xdemorse is a simple morse decoder for x11 * aldo:Console-based morse tutor * grig: Graphical control program for hamlib * kappanhang:tool to remotely open audio channels and a serial port to an Icom transceiver * linsim: Amateur Radio Digital Mode evaluation under varying HF propagation conditions * qrq: CW (morse code) trainer * ibp: a terminal/X11 program showing data from the International Beacon Project, for ham radio HF usage * xdx: Dx-cluster client for amateur radio * xlog: Logging program for Amateur radio * tqsl: trustedqsl: digitally signed QSO records (records of Amateur Radio contacts) * wwl: CLI to calculate distance (qrb) of maidenhead locators used in Amateur Radio * wfview: program to control modern Icom (and Kenwood) ham radios from a computer. * direwolf: a software "soundcard" AX.25 packet modem/TNC and APRS encoder/decoder * tucnak: ham radio VHF and microwave contest log, needs libzia * libzia: library for tucnak, a ham radio contest logbook * qsstv: QSSTV is a program for receiving and transmitting SSTV and HAMDRM * cwstudio: fast, portable and lightweight Morse code signals generator The hamradio development project now hosts 30 packages that are in openSUSE Tumbleweed, hardware:sdr project counts 61 of the same. We are okay with there being some overlap. Chirp gets weekly updates, the AX.25 related packages point to a new upstream. Various digimode packages are either current or in the works. We have no particular goal here other than creating working packages that are generally useful, and maintaining them in the distribution. Where applicable we use them on own use as we progress in our mastering of the hobby. To our users we would like to signal that there are people working on this topic for openSUSE, and that they can send bugs. To potential contributors we would like to indicate that are willing to help review and guide you to get your packages in and into openSUSE proper. Happy to help and work together. I would like to acknowledge the work of the previous maintainers who are no longer active, and those who chose to run their projects in OBS solo without contributing to the distribution in a team. With Martin, Martin, Wojciech, and Дмитрий,.. 73, Andreas [View Less]

1 0

Outreachy Mentoring
by ddemaio openSUSE 26 Feb '25

26 Feb '25

Hi all, Outreachy is looking for open-source mentors for its June 2025 internship cohort [1]. This program provides paid, remote internships to increase diversity in open source. If you're interested in mentoring an intern, please let me know (ddemaio(a)opensuse.org) before March 7. Mentors will help guide interns on project contributions and are expected to commit 5–10 hours per week during the contribution and internship periods. v/r Doug [1] - https://www.outreachy.org/blog/2025-01-20/june-2025-call-for-mentoring-orga…

1 0

Latest Update Breaks DNS
by Chuck Payne 19 Feb '25

19 Feb '25

Hello, I have been using BIND for years on openSUSE Tumbleweed, the latest update breaks BIND. It will not start at all Feb 19 11:06:44 magi systemd[1]: Starting Berkeley Internet Name Domain (DNS)... ░░ Subject: A start job for unit named.service has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit named.service has begun execution. ░░ ░░ The job identifier is 316. Feb 19 11:06:44 magi root[1542]: … [View More]Warning: "/usr/share/bind/createNamedConfInclude" does not exist or is not executable. Check /etc/syscon> Feb 19 11:06:44 magi systemd[1]: named.service: Control process exited, code=exited, status=6/NOTCONFIGURED ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ An ExecStartPre= process belonging to unit named.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 6. Feb 19 11:06:44 magi systemd[1]: named.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The unit named.service has entered the 'failed' state with result 'exit-code'. Feb 19 11:06:44 magi systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). ░░ Subject: A start job for unit named.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit named.service has finished with a failure. ░░ ░░ The job identifier is 316 and the job result is failed. I saw article on SLE having the same issues. I have updated /etc/sysconf and update the line, which it states should fix it. This is the URL, https://www.suse.com/support/kb/doc/?id=000020819 NAMED_INITIALIZE_SCRIPTS="createNamedConfInclude" to NAMED_INITIALIZE_SCRIPTS=" " and I update /etc/named.conf #include "/etc/named.conf.include"; That does get named working again, but where do I now place all my zones that were there? This is really living up to my last name, because my DNS are public facing and down for nearly 36 hours. I am going to ask them to my named.conf but I don't think that is the best practice. Can someone please point me to the correct update way to place zones? -- Terror PUP a.k.a Chuck "PUP" Payne ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- Terrorpup openSUSE Advocate/openSUSE Member x/mastodon.social -- @terrorpup dicord -- terrorpup#3550 bluesky -- @terrorpup967.bsky.social uglyscale.press Register Linux Userid: 155363 openSUSE Community Member since 2008. [View Less]

2 1

Board meeting minutes 2024-01-20
by Douglas DeMaio 14 Feb '25

14 Feb '25

= Board Meeting Monday 2025-01-20 14:00 CET = * Present: Doug, Neal, Gerald, Patrick, Shawn * Excused: Simon * Guest: Luna * Minutes: Doug == Handover from current Board to 2025 Board == * Next meeting planned for Feb. 10 * Cancel Feb. 3 meeting as people will be returning from FOSDEM == Discussed Items for Next Board == Branding topic & possible policies for usage Defer discussions about project membership, with regards to New Member Criteria, and the evaluation of Emeritus status … [View More]

1 0

No Leap 16 feature review meeting today -- cancelled
by Luna Jernberg 10 Feb '25

10 Feb '25

Hey! Today meeting https://calendar.opensuse.org/teams/release/events/feature-review-meeting is cancelled as Lubos is out on Ski vacation this week

1 0

A (re) Introduction and update on the Geeko Foundation.
by Patrick Fitzgerald 10 Feb '25

10 Feb '25

Greetings all. I want to re-introduce the Geeko Foundation, its origins and reason to exist, and progress so far. I suspect that most of you are already familiar with this information, but it's time for a bit of a refresher. TL;DR: Support the Geeko Foundation! The concept of a foundation-like structure has been long debated within the community. This is because "openSUSE" is essentially nothing but a name. It has no legal standing (apart from being a SUSE trademark). This means... * There … [View More]is no place to make donations to, because there is no bank account (1) * Therefore, the community is 100% reliant on SUSE for it's survival * Further, no individual or company is likely to make a donation to a public or private company (2) Of course, with a foundation, the following becomes true: * Any person or organisation can donate * Depending on the location of the donor, there may be a corporate or individual tax benefit * The Foundation can dispense funds in a timely and efficient manner achieve it's aims - without seeking permission of a corporate sponsor Obviously there are many other benefits - but you get the idea. How did it come to pass? At the openSUSE Conference in 2022, I volunteered to produce a report for the board to show potential solutions for establishing a foundation of some sort. For those of you who are unaware, openSUSE's funding had been slashed by SUSE's management (at the time led by Melissa Di Donato). At the time there appeared to be very little interest or understanding of the role of the community and its role in the development of SUSE's own products. It was my understanding that the project was operating with 30% of the budget allocated in previous years, and as a result SUSE ceased to sponsor many open source events, even one that SUSE themselves had originally started. So basically, at that time there was a sense of desperation in the air. Some of the questions asked: What is the future of the openSUSE community (and name and logo) if: * SUSE goes bankrupt? * SUSE decide to abandon the brand? * SUSE is purchased by another company (who may or may not keep the brand alive)? * SUSE just lose interest and de-fund the project entirely? Any of these reasons should make any community member (or user) concerned. After producing the initial report, (attached) I decided that the risk was worth taking - so I created the Geeko Foundation as a UK-based Not-For-Profit organisation. We swiftly established bank accounts and an accounting system. My own company, i-Layer, donated server time and covered for professional fees (ie, legal, insurance and accounting) for the first 12 months. Some Geeko Quick facts: * We have donations from SUSE, ARM and Google, and hundreds of individuals. * For the last 18 months or so we have been managing the TSP (Travel Support Fund). Payments have been much faster as a direct result - sometimes a fast as next day. I am looking into making these payments automatic - further speeding this process. * Currently no salaries are paid to the trustees and there are no employees (yet). * We aim to spend 90% of our income on charitable activities * At FOSDEM this year we raised more than €1200 from donations via our card machine! (thanks to everyone at the stand!) * The Foundation is shortly to become a full UK charity. * There are no shareholders, or owners. * Anyone can apply to be a trustee. * Help is needed! But what is a Not-For-Profit? * A good summary can be found here: https://en.wikipedia.org/wiki/Nonprofit_organization But why not just call it the "openSUSE Foundation"? * Apart from potential conflict with SUSE over trademarks, it would raise legal questions as to if it was simply a tax avoidance mechanism by SUSE. * Similarly, if it was to be controlled by SUSE (for example, all trustees were SUSE employees) this would also raise questions both in the eyes of the tax authorities and donors. But why is it based in the UK and not in Germany? * Setup costs are lower (and no upfront capital is required) * British law is widely understood * The community is global, as is SUSE - are we going to set up in every country? * Historically, there had been a LOT of discussion featuring various European states, but no action was taken * German language would be a must, as trustees have a level of legal responsibility. This would automatically limit the type of trustees that could be attracted to be engaged. This is not to say that there can't be a German subsidiary, but right now, we already have too much to do. Hopefully the UK government will reverse Brexit and things will get easier, at least in Europe. The Situation Now: * At the openSUSE conference last year SUSE suggested that the project change its name, the main reason provided was that represented a risk to the SUSE trademark. For the reasons outlined above, the Geeko Foundation broadly support this initiative, so long as there is a corresponding budget (marketing, infrastructure and personnel) allocated by SUSE to support this move. * If you've used the TSP in that last 2 years, or been to the openSUSE Conference, FOSDEM, FROSCON, FOSSCOMM, openSUSE Asia, SUSECON, Dors/CLUC, GSOC, or others that I cant recall right now, you've already been a part of what we do. Even if you don't realise it! * As an entity, the Geeko Foundation have proven that there is appetite for donations! We are currently finalising accounts for the last financial year, which show a large increase (up to 3x) in donations based on the previous year. (3) We'd love to continue to help, which is, actually, was my primary reason to create the foundation in the first place. Personally, I believe that that open communities build better products and engage more users. I've known that from the beginning of my career. Mindshare is important! However, the foundation is yet to receive any formal approach from SUSE related to a path forward, however we are look forward to solidifying our relationship in an upcoming meeting as we have already done most of the legwork required. But who am I? If you don't already know - in 2019 I was presenting at the openSUSE conference in Nuremberg, and about 5 minutes in, I suffered a cardiac arrest. Thanks to the swift actions of the community members present - I am amongst the 6% of survivors of this kind of incident. I figured that setting up the Geeko Foundation was the best way to pay it forward - so that's what I did. I've had 40 years in Technology and my company, i-Layer, is currently hosting cloud solutions for major financial organisations in the UK and Switzerland. i-Layer have been an SUSE partner for about 15 years. How can YOU help? * If you are a donor - thank you. * If you have any free time - we have programming, marketing, and accounting and legal needs. Get in touch! * If you have resources available - bandwidth, hosting, rackspace, hardware... Get in touch! If you've made it this far - thank you for your attention and have a lot of fun! Patrick Fitzgerald Geeko Foundation https://geekos.org Notes: (1) You can't use a private bank account for tax reasons (amongst others); therefore a form of legal entity is required (2) Not only are individuals and corporates unwilling to donate to a for-profit entity (why would they?), their accounting departments are unable to match payments product codes, and any funds donated are unlikely to be allocated to... anyone. (3) I know that there have been calls in the past for greater transparency over and above the publication of rather dry accounts data that is publicly available (here: https://find-and-update.company-information.service.gov.uk/company/14662457) however, mining the data and producing higher quality reports takes time. If anyone wants to help out with automating that process - feel free to get in touch. (python/REST skills would be great!) -- [View Less]

1 0

OpenSUSE on Destination Linux This week
by Luna Jernberg 10 Feb '25

10 Feb '25

Hey! CubicleNate is talking openSUSE on Destination Linux this week: https://www.youtube.com/watch?v=BwQQ9Kj9gwU https://tuxdigital.com/podcasts/destination-linux/dl-406/

1 0

openSUSE Board Election — Results
by Ariez Vachha - openSUSE 05 Feb '25

05 Feb '25

Dear openSUSE members, In accordance with our schedule the voting period is now closed. The final tally of votes out of 148 ballots cast are as follows: * Chuck Payne - 72 Votes * Ish Sookun - 119 Votes - Elected * Jeff Mahoney - 104 Votes - Elected * Rachel Schrader - 76 Votes - Elected We congratulate our new board members and thank all nominees for participating. Regards, Ariez Vachha // on behalf of the Election Committee [1] … [View More]

22 31

Main

Development

Information

Community

Social Media

Other

openSUSE Project