August 2022 - openSUSE Project - openSUSE Mailing Lists

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

Re: Concern for open-source to consider
by Richard Brown 16 Aug '22

16 Aug '22

On 2022-08-16 10:28, Alberto Planas wrote: > No, it does not control how to use the distribution but the trademark. > > I can download openSUSE Leap 15.4, install it into my new nuke and > control it. > Maybe I cannot say "Nuke powered by *openSUSE* Leap 15.4", as I would > be using > the trademark. But I definitively can run the software at my will. > > In other case this will be in contradiction with some (all?) the > licenses that > compose the distribution, that are explicit in granting the freedom of > running > the software. > > For example, in the GPL Faq[1] > > """ > Can I use GPLed software on a device that will stop operating if > customers do > not continue paying a subscription fee? (#SubscriptionFee) > > No. In this scenario, the requirement to keep paying a fee limits > the > user's ability to run the program. This is an additional requirement on > top of > the GPL, and the license prohibits it. > """ > > [1] https://www.gnu.org/licenses/gpl-faq.en.html The statement was that open source licensed software has no restrictions on use The reality is, many open source licenses have restrictions on use The GPL as an example restricts “use” in the context of redistribution. You can’t use the GPL in something that is provided to others without providing the source - that’s a restriction. The GPLv3 goes further, restricting hardware manufacturers from locking down their hardware from installing other software. It’s a restriction the name of user freedom, but ultimately it’s a restriction, the people building the hardware can’t do whatever they want with GPLv3 software. And the openSUSE license also has restrictions on use. Whether or not the openSUSE license can be changed like Simon suggests, and even accepting your example above, my fundamental point remains Open source licenses can and habitually do have restrictions limiting their use, which undermines the argument that once open source software is released it can be used for anything by anyone. -- Richard Brown Linux Distribution Engineer - Future Technology Team SUSE Software Solutions Germany GmbH, Frankenstraße 146, D-90461 Nuremberg, Germany (HRB 36809, AG Nürnberg) Managing Directors/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman

1 0

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

15 Aug '22

Hi all, The ALP Work Group (WG) will take place tomorrow at 14:30 UTC. The Community Meeting will be on Thursday at 19:00 UTC. 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 15 Aug '22

15 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.

2 1

Birthday/Asia Summit/Community Meeting/Community Install Feedback: Week 32
by ddemaio 08 Aug '22

08 Aug '22

Hi all, Tomorrow, our openSUSE Community turns 17!!! To celebrate this, you are invited to join in on a 24-hour party in the openSUSE Bar at meet.opensuse.org/bar. Please join us. You can find more information about it at https://news.opensuse.org/2022/07/26/community-to-celebrate-os-birthday/. There will be a giveaway event taking place on our Reddit - https://www.reddit.com/r/openSUSE/. openSUSE.Asia Summit The Call for Papers has been extended. The new deadline is August 13. Please login and submit your talk at https://events.opensuse.org/ There will also be a community install feedback session tomorrow at 14:30 UTC during the ALP Work Group (WG). This will also take place on August 11 during the week's regularly schedule Community Meeting. Find out more information at https://news.opensuse.org/2022/08/03/wg-shifts-to-feedback/. Watch this video to install and test out MicroOS https://youtu.be/--hoHcNjWgE Test these things with MicroOS and provide feedback. https://docs.google.com/spreadsheets/d/1AGKijKpKiJCB616-bHVoNQuhWHpQLHPWCb3… You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. v/r Doug

2 1

openSUSE Board meeting 2022-08-01
by Attila Pinter 03 Aug '22

03 Aug '22

(Apologies for the delay. Also you can find the Board meeting archive here: https://en.opensuse.org/openSUSE:Board_meetings) = Board Meeting Monday 2022-08-01 13:00 CEST = * Present: Attila (a bit later), Axel, Gerald, Gertjan, Maurizio * Guests: Doug, Emily, Luna(bittin), Patrick * Excused: Neal, Syds == openSUSE Board Meeting Future? === * Gerald shares some observations on logistics around this meeting * Collaboratively taking notes via Etherpad generally seems to work well * As does the issue tracker at code.opensuse.org (though few topics raised outside the board) * However, still struggling to publish minutes of this meeting * Proposes to "resume" (rather: transform) previous role of minutes taker to ** do final pass over minutes and send (within 24h, max 48h of meeting) to project@ and Wiki ** clear and prepare Etherpad for next meeting * Everyone to prepare the Etherpad (topics, non-availability,...) before the next meeting ** if possible up to 1 hour before meeting * AI: Gerald to share proposal with full board == openSUSE moderation Team update == * https://code.opensuse.org/board/tickets/issue/9 * Team can now cover most platforms: Discord/Matrix/Telegram/Reddit - mailing lists to be confirmed * Moderator Team Community Meeting? -- Announcement on http://news.opensuse.org and mailing lists * openSUSE Pagure page created: https://code.opensuse.org/project/mod-team * AI: Wiki page for the mod team would be useful * Announcement and meeting tentatively on Thursday 11th August == TSP Program Update == * Doug had a meeting with VP of SUSE Finance this morning and will know more during next week. Continued at private part at CEST 13.35 Meeting closed at CEST 14.00 -- Br, A.

1 0

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

01 Aug '22

Hi all, Tomorrow at 14:30 UTC during the ALP Work Group (WG), we will do an install workshop https://news.opensuse.org/2022/07/27/microos-install-workshop-feedback-sess… The event will be recorded in our openSUSE Jitsi and added to the openSUSETV Youtube account. We will do a feedback session on August 9 and August 11 during next week's regularly schedule WG and Community Meeting. This week, the Community Meeting scheduled for Thursday at 19:00 UTC is cancelled since we agreed in the last meeting to attend Fedora nest during the normally scheduled meeting. https://fedoraproject.org/wiki/Nest_with_Fedora_2022_Schedule# The workshop and feedback sessions 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. openSUSE.Asia Summit The Call for Papers has been extended. The new deadline is August 13. Please login and submit your talk at https://events.opensuse.org/ v/r Doug

1 0

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

01 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.

2 1