January 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

Cockpit
by Charles Payne 31 Jan '25

31 Jan '25

Hey Guys, Has anyone one see the update to Debian 12 cockpit? I only ask because you don't need to have apps like VirtViewer to open virtual guest. The newer version of Cockpit shows the virtual gueston the page. It's like using Proxmox. Can we get our version of Cockpit to use the same? -- Chuck Payne/terrorpup SoftMeta (470) 535-3647

3 2

Fwd: please include me to the project (GitHub -> aneisner)
by Luna Jernberg 31 Jan '25

31 Jan '25

---------- Forwarded message --------- Från: antonio.eisner--- via openSUSE Factory <factory(a)lists.opensuse.org> Date: fre 31 jan. 2025 kl 14:13 Subject: please include me to the project (GitHub -> aneisner) To: <factory(a)lists.opensuse.org> Hi Guys, I work at the SUSE company, my colleague has asked me to join the openSUSE project so that I can contribute to the code if needed. My GitHub name is: aneisner Thanks Best Regards Toni

1 0

Re: openSUSE Release Engineering meeting 29.01.2025
by ish＠sysadmin-journal.com 30 Jan '25

30 Jan '25

> On 30 Jan 2025, at 00:56, Lubos Kocman via openSUSE Factory <factory(a)lists.opensuse.org> wrote: > > Can we all like Jeff Geerlings's openSUSE t-shirt. I wrote a comment > on behalf of openSUSE account. Let's make sure he wears it more often! > :-) https://www.youtube.com/watch?v=eLtE2kMTVOQ Like it & shared just because of the t-shirt. Regards, Ish Sookun

1 0

Question to board candidates
by Christian Boltz 30 Jan '25

30 Jan '25

Hi board candidates, I have a question: What is your opinion about renaming / "rebranding" openSUSE? I'm looking forward to your answer - or even two answers, a personal and a "political" one ;-) Regards, Christian Boltz -- Security does only work as long as it does not get into the way of whatever fills the fridge. [Kristian Köhntopp in https://plus.google.com/+KristianKöhntopp/posts/PY9GZduTsrd]

4 5

BCL GM openSUSE discussions
by Rick Spencer 28 Jan '25

28 Jan '25

openSUSE Community, First, I want to take a moment to re-introduce myself on this list. My name is Rick, and I am the General Manager of SUSE’s Linux team, responsible for all of the core Linux products that we make at SUSE. I have been at SUSE now for just over a year. tl;dr - In December, I had an AMA with some community members to learn about the openSUSE community, and I am planning another one. Now that I have been in the role for a year, I would like to build a stronger connection with … [View More]

2 1

Question to the candidates
by Thorsten Bro | openSUSE Member 28 Jan '25

28 Jan '25

Dear candidates to the openSUSE board, as I need to decide about my vote and carefully read through your introduction. I'm happy that we got some candidates together. I would like to ask you some questions which I guess would highly influence my choice. - What is your pet project at openSUSE - name anything that comes to your mind (e.g. code, wiki, whatever comes to your mind...)? - How would you react to an escalation like this[1] on the mailing list? [1] https://lists.opensuse.org/… [View More]

5 4

Platform Page
by Rachel Schrader 22 Jan '25

22 Jan '25

I wanted to attach and send out a link to the platform page I created. https://en.opensuse.org/openSUSE:Board_Election_2024_Platform_Rachel_Schrad… If anyone has questions feel free to reach out by email, matrix or discord. :) Thank you everyone - Rachel

1 0

My Platform Page
by Chuck Payne 18 Jan '25

18 Jan '25

Dear Ariez, Hi. I open this one gets to you. I will still send it to you from my softmeta.com as well. I have setup my election campaign page at https://en.opensuse.org/openSUSE:Board_Election_2024_Platform_Chuck_Payne Feel free to reach out to me on this or softmeta or even discord. -- Terror PUP a.k.a Chuck "PUP" Payne ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- Terrorpup openSUSE … [View More]

1 0

My Platform Page for the 2024 Election
by Charles Payne 18 Jan '25

18 Jan '25

Dear Ariez, Hi. I hope this one get this one. I will still send it to you from my gmail.com as well. I have setup my election campaign page at https://en.opensuse.org/openSUSE:Board_Election_2024_Platform_Chuck_Payne Feel free to reach out to me on this or softmeta or even discord. -- Terror PUP a.k.a Chuck Payne SoftMeta (470) 535-3647

1 0

Main

Development

Information

Community

Social Media

Other

openSUSE Project