- openSUSE Project

Community Meeting: Week 2
by ddemaio openSUSE 08 Jan '24

08 Jan '24

Hi all, Welcome to 2024! We have a calendar!!! A big thank you to the contributors that made this happen. You can find out information about openSUSE meetings at https://calendar.opensuse.org and add the calendar invitations with all the details for reminding you about the openSUSE Community Meetings. The meeting take place at https://meet.opensuse.org/meeting, which if down will be at https://meet-test.opensuse.org/meeting We will have a community meeting tomorrow (Tuesday) at 14:30 UTC (60 minutes). Community Meeting 2 is scheduled for Thursdays at 20:00 UTC. Submit a talk and register for the openSUSE Conference 2024 at https://events.opensuse.org/ Find all meeting notes at https://etherpad.opensuse.org/p/weeklymeeting v/r Doug

1 0

Community Meeting: Week 2
by ddemaio 08 Jan '24

08 Jan '24

Hi all, Welcome to 2024! We have a calendar!!! A big thank you to the contributors that made this happen. You can find out information about openSUSE meetings at https://calendar.opensuse.org and add the calendar invitations with all the details for reminding you about the openSUSE Community Meetings. The meeting take place at https://meet.opensuse.org/meeting, which if down will be at https://meet-test.opensuse.org/meeting We will have a community meeting tomorrow (Tuesday) at 14:30 UTC (60 minutes). Community Meeting 2 is scheduled for Thursdays at 20:00 UTC. Submit a talk and register for the openSUSE Conference 2024 at https://events.opensuse.org/ Find all meeting 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 01 Jan '24

01 Jan '24

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.

3 2

openSUSE Board minutes 2023-12-04
by ddemaio openSUSE 18 Dec '23

18 Dec '23

= Board Meeting Monday 2023-12-04 13:00 CET = * Present: Doug, Gerald, Mau, Neal, Patrick * Excused: Gertjan * Guests: Attila, Axel, bittin, Georg * This week's report to be sent by: Doug == Membership == * In the last board meeting with quoram the idea was brought up to automatically grant membership after a certain period unless the application was explicitly denied. * Gerald could not attend that meeting and raised concerns afterwards. ** generally from a governance perspective ** if membership officials are overwhelmed/unavailable approving, who would filter membership requests * AI Gerald to reach out to membership officials again, asking their take == Logo Competition == * Doug provided an update on logo competition and the next steps to take place ** Meeting to go over the logos after the competition is complete will take place on Dec. 12 ** Doug will send the Project logo winner design to legal for processing == IT == * Gerald will communicate with infra to help establish a relationship to gain help from SUSE IT based on needs from heroes, etc. Board Meeting ends at 14:02 CEST.

2 2

Will openSUSE fork ISC DHCP on Github and maintain it?
by renmingshuai 18 Dec '23

18 Dec '23

Hi! As far as I know, OpenSUSE has forked some software packages that are no longer maintained by upstream on GitHub and maintains them by yourselves, such as xinetd. ISC DHCP has announced the end of its life in 2022. Is openSUSE going to fork it and maintain it in the future? Regards,

1 0

Will openSUSE fork ISC DHCP on Github and maintain it?
by renmingshuai 18 Dec '23

18 Dec '23

Hi! As far as I know, OpenSUSE has forked some software packages that are no longer maintained by upstream on GitHub and maintains them by yourselves, such as xinetd (https://github.com/openSUSE/xinetd). ISC DHCP has announced the end of its life in 2022 (https://www.isc.org/blogs/isc-dhcp-eol/). Is openSUSE going to fork it (https://github.com/isc-projects/dhcp) and maintain it in the future? Regards,

1 0

Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)
by openSUSE Meeting Reminder 16 Dec '23

16 Dec '23

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

Insights from the openSUSE Logo Contest
by ddemaio openSUSE 16 Dec '23

16 Dec '23

Hi all, I want to bring your attention to the following blog post about the logos contest and the discussions we had during the community meeting regarding the topic. We figured out a pathway forward, but the timeline isn't fully set as there are topics already submitted for the openSUSE Conference, which you can submit a talk proposal at https://events.opensuse.org/. I've already submitted one. The title "Brand Therapy - Getting Emotions Off My Chest". v/r Doug Link to article - https://news.opensuse.org/2023/12/15/insights-from-the-os-logo-contest/ The past few weeks have been an exciting time for the openSUSE Project as discussions about the visual identity of the project offers a glimpse into people’s various views about the project and its brand identity. The recent conclusion of the openSUSE logos contest has sparked extensive discussions among both members actively engaged in the openSUSE Project and those participating in it. Our logo contest has provided us with a wealth of creative input and diverse perspectives that lay a strong foundation for deliberations on the future direction for the project. The contest provided a voice for the many who aren’t as vocal as some about selecting a new logo. While there were some who were vocal on various platforms, the contest gave openSUSE Project members an opportunity to gauge how the broader community perceives the project. The submissions and voting outcomes offered a glimpse into the collective vision of open-source enthusiasts who may not be directly involved in the project but are crucial stakeholders nonetheless. As efforts move forward with the outcome of this, inclusivity and community involvement remain at the core of the decision-making process. During the community meeting this week where the results were discussed, participants expressed the view that members of the openSUSE Project have an opportunity to participate in the selection of our new logo, and that SUSE, which holds the trademark to the openSUSE logo, be involved with the process for selecting a branding decision with regard to the results. After all, this decision impacts the collective identity. To facilitate this, there is a plan to organize a vote between the current logo and the proposed new design, allowing our community to have a say in this important decision. Furthermore, members of the project are collaborating with SUSE on the implications of the branding initiatives and some have expressed the desire for SUSE’s input to ensure there is an aligned vision for the future of openSUSE. A two-step approach to spearhead the discussions and decision-making processes with key stakeholders is crucial in driving a plan of action forward and implementing any changes to our branding strategy. Outlined below are the proposed steps that will guide the project through this journey: Step 1: Evaluation of Contest Results (completed) Assessing the Path Forward (completed) Engaging with SUSE for Brand Consideration & Assessing Contributions Presentation of Branding Strategy Community Voting Engagement Organizing a voting process for openSUSE Project members to choose between the Old and New Logo Step 2: Collaboration with Stakeholders Aligning Logo Ownership with SUSE Trademarking and Implementation The aim is to ensure transparency, inclusivity, and alignment with the collective goals of the openSUSE Project throughout this process. For a detailed review of the survey results from the logo contest, visit our Logo Contest page. People interested in becoming a member of openSUSE should visit our wiki on How to become a member. Thank you for your continued support and enthusiasm. A big thank you to all the people who submitted a design and those who voted. Winners of the contests have been contacted about winning and will be shipped a Geeko Mystery Box. The winners of the openSUSE logo contest across various categories are as follows: openSUSE: AO01 Tumbleweed: Three-way tie AO31, AO05, and AO11 Leap: AO01 Slowroll: AO03 Kalpa: AO03

1 0

[project] cannot login on https://forums.opensuse.org/ in SeaMonkey, Pale Moon, or Falkon
by Felix Miata 12 Dec '23

12 Dec '23

https://progress.opensuse.org/issues/152413 has been summarily closed. Rather than limiting follow-up to the few who ever address or have interest in progress.opensuse.org issues, I thought it better to comment to a larger openSUSE audience. You may open the above link to see the initial report and "closing" (about 1600 characters). What follows is the further comment I originally intended to make there: I'll cede some power might be in short supply, but you admins have all the decision power you need. You chose the site software. You installed it. As the site maintainers, you can revert the ostensible "upgrade", revert to the software used previously, or install other software, such as the user-friendly software used by https://www.linuxquestions.org/. I did none of those things. I'm not a discourse user or admin. I'm a website user. The forum admins are the discourse users. The admins chose it. The admins installed it. The admins maintain it. They should be taking it up with upstream if they can't figure out how to solve the problem themselves. Partaking in openSUSE user assistance via email is what the mailing lists are for. What exactly are these so-called "security updates" that necessitate shutting out users of multiple web browsers? Were there any issues that applied generally, such as to include forums.opensuse.org, or were they limited in applicability, thus not forums.opensuse.org? Were there not release notes for the update that warned multiple web browsers would no longer be "supported", even though "web browsers" are not what websites are supposed to support, but user agent functionality? The concept of "web browser" support has been broken from day one. W3 instructs it's function to sniff for if sniffing is necessary, which itself should be limited. -- 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

2 1

RE: Board Member vs Community Member
by Patrick Fitzgerald 12 Dec '23

12 Dec '23

To my mind, this is all about the difference between "asking for permission vs asking for forgiveness". Linux has thrived, in part, because people have acted first and asked for forgiveness later. Personally I think the current logos are fine, but if the community feels that they want to change them, let them come up with alternatives that be submitted to Suse as suggestions. Suse have every right to refuse the submissions, but who knows, someone out there might come out with the perfect logo. On the other hand, I think that money is better spent on events and infrastructure than trademark lawyers... but having enough for both would be even better ;) /p -- -------------------------------- Patrick Fitzgerald All Support queries to: isupport(a)i-layer.com <mailto:isupport@i-layer.com> -----Original message----- From: ddemaio openSUSE <ddemaio(a)opensuse.org> Sent: Monday 11th December 2023 8:58 To: Richard Brown <rbrown(a)suse.de> Cc: project(a)lists.opensuse.org; Gerald Pfeifer <gp(a)suse.com> Subject: Re: Board Member vs Community Member On 2023-12-09 09:52, Richard Brown wrote: > On 2023-12-08 10:18, Douglas DeMaio wrote: > > Have a look at every single reddit, telegram, twitter, or matrix > discussion on the topic and you will find words from others than > myself also either echoing similar concerns or just outright disliking > the idea of changing the logo. I find this latest email from you to be > obscenely patronising and unbecoming of an openSUSE Board member who > is meant to represent the wishes of the Project as a whole, and > especially it's voting membership. Please explain to me the difference between acting as a board member vs acting as a community member? I certainly don't speak on behalf of the board with this. If the suggestion is that my position within the project infringes too much or carries too much influence on this decision, let the marketing team from Telegram drive it. I'll certainly take a backseat to the process and discussion going forward. > >> And with the trademark aspects, that statement is there for a reason. >> The phrase "If you don't know, you better ask somebody" isn't just >> military jargon. Silence on the trademark for the month between the >> submissions and time to vote isn't being railroaded in my opinion; >> there was certainly a sufficient amount of time. > > It took several years from initiating discussions on trademarking > Kubic before it progressed. > As I have repeatedly pointed out on several other venues, every single > change, alteration, or addition to the openSUSE trademark has also > been a process lasting several years. > If you think a month is a good time for a topic of this complexity, > then frankly, I think you're unfit to be driving this matter, and I > respectfully request that Gerald take the lead, giving his > professional responsibility as Chairperson. Point taken. I don't shy away from criticism and this conversation goes as far back as 2019? What do others think? v/r Doug

4 5