- openSUSE Web

Search page localization
by Jan Papež (honyczek) 29 Jun '23

29 Jun '23

Hi, I’ve noticed that search page search-o-o offers localization selection, but when the language is selected, the top bar keeps English strings. And also I would expect the page autodetected the system language, but it starts with Enghlish by default. Could anybody take a look, please? Thanks. Jan -- Jan Papež (honyczek)

2 1

Helping contributor onboarding with a new website
by Jacob Michalskie 19 Aug '22

19 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/

2 2

oSC22 site is down
by Attila Pinter 16 Apr '22

16 Apr '22

Hi, Not sure if this is the right track to report this, or should be reported to the Heroes, but visiting https://events.opensuse.org/conferences/oSC22 currently results in error 500. Wanted to submit my talks finally, feels like a sign lol. -- Br, A.

2 1

Hello
by Maciej Żychliński 27 Feb '22

27 Feb '22

Hello, I'm new and I want to contribute to the wiki section, but I'm not sure how to go about it. Could you please guide me and show me what I can do? Br, Maciej

1 0

Initiative for migrating some wiki contents
by Adrien Glauser 10 Aug '21

10 Aug '21

Dear all, Along with other volunteers I am pushing for a plan to improve the state of the documentation platforms, trying make the docs more accessible, usable and overall better for the end users. I've compiled a couple of thoughts about how to go about it here: https://en.opensuse.org/openSUSE:Documentation_migration I'd like to know two things: 1) Are there people whose interests overlap this initiative and who would work in person with us to move this forward? 2) Among the people in (1), what is the minimum amount of things you would change to the document mentioned above to support it community-wide (for example by placing a shortened version of this document on the wikis landing page or portals). Looking forward to listening to you, Best, Adrien PS: https://en.opensuse.org/openSUSE:Wiki_team mentioned this address but Postorius web service mentions an another. Sorry if you receive this message twice.

1 0

[opensuse-web] Re: [opensuse-doc] Re: [opensuse-project] Re: Refreshing the openSUSE learning experience
by adathor 16 Oct '20

16 Oct '20

Have to fully agree with Adrien, but just to clarify our intentions: We wish to sort the wiki in a way that is easier to find information on given matters for users who are struggling with a problem or just generally wish to find information on a topic or on openSUSE. This project is not about excluding other platforms where contribution is currently happening. This project is not about gatekeeping. This project is not about control or setting limitations on contributors. This project is not about "questioning openSUSE's guiding principles". This project is purely about knowledge sharing and encouraging new users to openSUSE to learn, find out more about openSUSE and maybe later down the road contribute to the project in some form if they feel like it. > So if you read 3 minutes into the backlog you'll see that "Protect" in > the context has nothing to do with dogma or exclusion or control, but > on the contrary was about propagating up-to-date information and > empirically tested good practices. We've already established with Adrien a point in our list which calls for "Collectors" who are collecting issues and materials from all the places where discussions happening what we can work with. This assumes that we can map these places successfully. So if you're a contributor who is documenting on X platform that's fine. Nobody will force you into doing anything that you don't want to or using a platform or format you don't feel comfortable with. Drop a link to your documentation(s) so we can include it in form of a link at least. Life goes on, business as usual. Furthermore, what we settled on during our first meeting with Lana and Frank is to turn doc.opensuse.org into a hub from where the current documentations will be accessible in their current format and will link to certain topics - like FAQ - on en.opensuse.org. We're more than happy to hear other suggestions, however, considering that the Welcome app is pointing to doc.opensuse.org seems like a reasonable decision. The goal is simple: lower the barrier of entry, make documentations easier to find by making them available on en.opensuse.org in collaboration with the maintainers/contributors. A. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, October 16, 2020 7:06 AM, Adrien Glauser <adrien.glauser(a)gmail.com> wrote: > > I have to agree with Lars on this topic. > > "Protect" sounds to me like > > And that's where the discussion went bankrupt, where the topic was > shifted to how someone felt about a word when instead there was a > precise definition of what the word meant, and a concrete context > against which that definition was illustrated. Perhaps I am the one to > fault for this as I've been quite long winded on this topic. > > So if you read 3 minutes into the backlog you'll see that "Protect" in > the context has nothing to do with dogma or exclusion or control, but > on the contrary was about propagating up-to-date information and > empirically tested good practices. > > Anyway, I have little interest in building a theory of learning in the > FOSS environment, let alone defending it on this ML. Just wanted to > keep people in the loop. I will continue to do so, but at the end of > the day, only concrete results matter. Anyone here will have plenty of > time to make constructive criticisms of every aspect and detail of the > results, and I have no reason to doubt that we will try our best to > honour them. > > See ya later > > the team wants to artifically limit me (as > > > a contributor) on which platforms I can use to engage with other > > openSUSE contributors and define exactly where I must go if I wish to > > provide information to openSUSE users. > > I assure you, if that is the case, then I will cease contributing to > > any "official" openSUSE documentation platform and only provide > > information via platforms of my own control. > > Like Lars says, we're a diverse bunch, and respecting that diversity is > > a key value of the openSUSE's guiding principles. > > I do hope I have misunderstood what you mean by "Protect", but if I > > have not, then I hope I make it very clear where I stand on the matter. > > > > > Le mercredi 14 octobre 2020 à 16:22 +0200, Lars Vogdt a écrit : > > > > > > > Am 2020-10-14 15:11, schrieb Adrien Glauser: > > > > > > > > > My beef with it is that it kinda assumes that we want to > > > > > accept the status quo with the current level fragmentation in > > > > > support > > > > > material, while this "refreshing the learning experience" is > > > > > about > > > > > challenging the status quo. To be clear, we are talking about two > > > > > strategies: > > > > > (Repair) Bite the bullet about fragmentation, make or customize a > > > > > search engine able to fight fragmentation after the facts, so > > > > > that > > > > > support material is dynamically aggregated. > > > > > (Protect) Refuse to bite the bullet, prevent fragmentation in the > > > > > first > > > > > place by collecting information into a static (yet easy to > > > > > maintain) > > > > > single "source of truth & best practices", and then hope it > > > > > irrigates > > > > > all platforms. > > > > > > > > I have to admit that I really like your enthusiasm and wish your > > > > project > > > > all the best! > > > > I just fear that "Repair" is the only realistic option, especially > > > > long > > > > term. > > > > Why? We are an open source project with a lot of individuals trying > > > > to > > > > work on their areas of interest. Often enough these areas produce > > > > very > > > > interesting and useful stuff, but the results could - at least in > > > > the > > > > beginning - not be integrated under your "protect" umbrella > > > > (mostly > > > > because of resource or time restrictions). You can decide to loose > > > > some > > > > of these projects because of your restrictions, but I'm not sure if > > > > this > > > > is a good idea. > > > > We are diverse. Everyone has different opinions and different > > > > favorite > > > > tools. Trying to press everyone into the same tooling will not help > > > > to > > > > get more volunteers. I even tend to say that people who provided > > > > content in "their" tool in the past will neither spent their > > > > current > > > > time to migrate their content nor will they update their parts in > > > > the > > > > new setup later. > > > > I have seen this in the past with the "wiki migration". A lot of > > > > people > > > > stopped their voluntary contributions once others decided that > > > > they > > > > have to move and refresh their provided content in the new wiki > > > > pages. > > > > Since than, for me, it's clear that forcing volunteers to re-do > > > > their > > > > former work is a way to push good contributors out of the system. > > > > And as I said before: so far I see the reason behind each tool that > > > > we > > > > (as openSUSE community) provide to our "customers". What I miss on > > > > the > > > > other side is kind of a portal (page) that helps people to > > > > identify > > > > these tools and ways to collaborate and contribute. And I miss - > > > > like > > > > you - volunteers that review the existing content. > > > > > > > > > About your other point about the tools that the openSUSE > > > > > platforms > > > > > provide, is there an up-to-date list of every single tool hosted > > > > > by > > > > > openSUSE? Yes I am being lazy, but better being lazy than risking > > > > > overlooking things. > > > > > > > > For projects hosted and maintained in the openSUSE universe (this > > > > includes infrastructure provided by the heroes as well as SUSE > > > > powered > > > > stuff) I suggest to look at: > > > > https://status.opensuse.org/ > > > > ...and if you click on the icon in the upper right corner of that > > > > page, > > > > you should get a cool overview of all currently known openSUSE > > > > related > > > > stuff. > > > > With kind regards, > > > > Lars > > > > -- > > Richard Brown > > Linux Distribution Engineer - Future Technology Team > > Phone +4991174053-361 > > SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 > > Nuernberg > > (HRB 36809, AG Nürnberg) > > Geschäftsführer: Felix Imendörffer > > -- > To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org </adrien.glauser(a)gmail.com> -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

1 0

Re: [opensuse-web] Re: [opensuse-project] Refreshing the openSUSE learning experience
by Sergio Lindo 13 Oct '20

13 Oct '20

Hi Carlos, > El 13 oct 2020, a las 17:41, Carlos E. R. <robin.listas(a)telefonica.net> escribió: > On 13/10/2020 14.59, Adrien Glauser wrote: >> >> - r/openSUSE > > Er... what is the meaning of the 'r/' above? That is a slang for a Reddit section. >> - https://t.me/openSUSE_group bridged with the Freenode IRC and the >> Discord ("chat" channel) > > No idea what t.me is, either. :-? This is the URL shortener from Telegram and points usually to a telegram chat/channel. Kind regards -- Sergio Lindo Mansilla Software developer with DevOps tendencies Portfolio: http://binary-sequence.github.com/

1 0

[opensuse-web] Re: [opensuse-project] Refreshing the openSUSE learning experience
by Carlos E. R. 13 Oct '20

13 Oct '20

On 13/10/2020 14.59, Adrien Glauser wrote: > Hey Lubos, > > Thanks, hope we won't be losing steam during the journey, but at least > we're off onto something! > > Support for openSUSE is indeed quite fragmented: > - r/openSUSE Er... what is the meaning of the 'r/' above? I'm sorry, but I'm lost as to what may it mean. I suppose it is obvious to others, but to me it is new. > - https://t.me/openSUSE_group bridged with the Freenode IRC and the > Discord ("chat" channel) No idea what t.me is, either. :-? > - "support" channel on Discord bridged with the Freenode IRC > - mailing lists > - https://forums.opensuse.org > - all the non-English forums > > Now even though I don't see fragmentation as a problem in itself, there > are two kinds of fragmentation that do hurt: > > 1) The Problem of Good Answers Take Luck > When a question needs more than just descriptive material, and ought to > be answered by something like a recommendation or a short deliberation > where pros and cons have to be weighed against each other (i.e. should > I install NVIDIA proprietary drivers or openSUSE NVIDIA package or just > use Nouveau?); in this case, depending where you ask you will get > different answers, not all equally good > > 2) The Problem of Good Answers Evaporate > When a question has been met by a very good answer, which unfortunately > is not conveniently discoverable by web search engines. Heh. > And now to your remark: I don't think that r/openSUSE is an issue > because in my experience -- perhaps other experiences will tell > differently -- it avoids both Problems above, and I don't see another > Problem it'd run into. > > For me the issue is more with the instant messaging services. I use > them all the time and they are super good for coordination, but run > into both issues full throttle. There is no magic cure I can think of > right now. > > My only hope is that if we consolidate and update all documentation > material *while also offering recommendations over and above mere > descriptive material* we will be able to have a "source of truth" > useful enough to knock down the two Problems, at least as far as new > users are concerned. > > Just my opinion though. > > Cheers, > > Adrien > Ok :-) -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

1 0

[opensuse-web] Kanban access for doc team
by adathor 12 Oct '20

12 Oct '20

Hi, We're currently using Trello for organizing our tasks around the docs and wiki. Would it be possible to provide us with access to the openSUSE Kanban mentioned here: https://en.opensuse.org/Help:Kanban Maybe we could also help each other with some overlapping issues. -- Br, A.

1 0

[opensuse-web] Fwd: Landing page translation update
by Jan Papež (honyczek) 21 Jul '20

21 Jul '20

Hello, Czech landing page has incomplete translation. It's because of out of date strings at Weblate. Could somebody help and update translation strings from Github? Thanks. -- Jan Papež (honyczek) ---------- Forwarded message --------- Od: Jan Papež (honyczek) <honyczek-mailing(a)email.cz> Date: út 26. 5. 2020 v 22:54 Subject: Landing page translation update To: <opensuse-translation(a)opensuse.org> Hello, I've found some untranslated strings in Czech on the landing page www.opensuse.org, but in weblate at l10n.opensuse.org is Czech translation status 100%. I made an update for POT file and put pull request to landing-page repository at github, which was accepted. But now it is 2 days ago and strings at Weblate are not updated. [1] Could somebody help to do merge? [1] https://l10n.opensuse.org/projects/landing-page/#history -- Jan Papež (honyczek) -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

3 5