January 2025 - openSUSE Project - openSUSE Mailing Lists

spec file copyright headers
by Andreas Stieger 23 Jan '25

23 Jan '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 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

12 21

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

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

20 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/archives/list/project@lists.opensuse.org/thread/… - What's your opinion about flagging as welcoming community and inviting everybody to the project? - Can you explain to me, as I really want to get the bigger picture, how the future of legal setup the openSUSE project looks like? What is the status of the Geekos Foundation and what are the goals of the board regarding this matter? Thanks a lot in advance and happy hacking. Best regards -- Thorsten Bro <tbro(a)opensuse.org> - Member of openSUSE Heroes - https://en.opensuse.org/openSUSE:Heroes - Member of openSUSE VideoTeam - https://en.opensuse.org/openSUSE:Video

3 2

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 Advocate/openSUSE Member x/mastodon -- terrorpup discord: terrorpup#3550 Register Linux Userid: 155363 openSUSE Community Member since 2008.

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

openSUSE Board Election — End of the nominations phase
by Ariez Vachha - openSUSE 18 Jan '25

18 Jan '25

Dear openSUSE members, In accordance with our schedule the nomination period is now closed. Ish Sookun has resigned from the election committee in order to run for election to the board. We therefore have four candidates for the three seats as below. * Chuck Payne * Ish Sookun * Jeff Mahoney * Rachel Schrader Their details may be found on the election page [1] You will be receiving your ballots in due course. Regards, Ariez Vachha // on behalf of the Election Committee [1] https://en.opensuse.org/openSUSE:Board_election [2] https://en.opensuse.org/openSUSE:Board_election_rules

2 1

Google Summer of Code 2025
by ddemaio openSUSE 16 Jan '25

16 Jan '25

Hi all, Applications for Google Summer of Code 2025 open from Jan 27 to Feb 11. If anyone from openSUSE is interested in mentoring, please email me at ddemaio(a)opensuse.org. As a side note, this year GSoC is prioritizing security and AI/ML projects. v/r Doug

1 0

Nomination of Ish Sookun for Board candidacy
by Lubos Kocman 15 Jan '25

15 Jan '25

Hello openSUSE! I was thinking a lot about the current election situation and how I could personally help. I believe we have a strong candidate from SUSE who I'd like to support rather than go against as there is only one SUSE seat free. I was patiently waiting to see somebody from the community standing up. I'm happy that has recently happened with Rachel. But there is more than one free seat. I was having multiple discussions, and thinking about who'd be the best candidate from the community, and with that said. I would like to nominate *Ish Sookun as a candidate for the current openSUSE Board election. Of course, I have asked Ish for approval in advance, and Ish confirmed that he was already thinking about it himself, but was a bit worried regarding his responsibilities in the election process and the transferring of these responsibilities; based on our last conversation, it seems that this part is being taken care of as we speak. Ish answered me "Someone nominating me is the best recognition coming from the community". Ish is very active in the community in his homeland. He has been deeply involved in the openSUSE election process. He is willing to travel long distances to meet with the community at the openSUSE Conference. We all rely on the openSUSE election process to simply work. Things he's responsible for just work. Based on knowing Ish, he has a strong sense of responsibility and ownership, which I believe is very important. I'll leave the introduction part to Ish :-) [0]https://en.opensuse.org/User:Ishwon -- Best regards Luboš Kocman openSUSE Leap Release Manager

5 5

Fwd: Throwing my name in for the board
by Charles Payne 14 Jan '25

14 Jan '25

I can't send this from terrorpup(a)gmail.com, GMAIL bonuses my email for the weirdest reasons. I did send this to Ish and Gerald on the 7th. I am resending this with my fingers crossed that it doesn't get bounced back. ---------- Forwarded message --------- From: Charles Payne <chuck.payne(a)softmeta.com> Date: Tue, Jan 7, 2025 at 10:07 AM Subject: Throwing my name in for the board To: Ish Sookun <ish.sookun(a)lasentinelle.mu>, Gerald Pfeifer <gp(a)suse.com> Guys, Sorry for the direct email, but GMail and the mailing list don't get along. Seeing that no one is willing to step, with a heavy heart. I am going to step up and run agian for the board. As you guys know I have run a few times in the past. I have used it since 96. I don't want to see the project fail. -- Chuck Payne SoftMeta (470) 535-3647

1 0

Re: This should really not happen on Leap.....
by Axel Braun 13 Jan '25

13 Jan '25

Am Sonntag, 12. Januar 2025, 22:00:36 Mitteleuropäische Normalzeit schrieb Robert Kocher: [pls reply to list, so everybody can read....] > I agree! > > And i wonder how long it will last, until it is corrected! The error > appears since several days now! > > Are there any news about this? No, but running 'zypper up' works flawless (although some GTK-packages are not installed, without this message). However, as posted, this should not happen for Leap - 'my' Leap users are already stuck with this message! Axel

4 3