- 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

[opensuse-web] WSL Leap on download page
by Jan Papež (honyczek) 03 Jul '20

03 Jul '20

Hello, openSUSE Leap 15.2 would be available as WSL distribution for Windows as well as Leap 15.1. But at download page for Leap distribution is not mentioned that this variant (will be) is available. It could be added here, could not? -- 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

2 1

[opensuse-web] CS Wiki TOC styling
by Jan Papež (honyczek) 27 May '20

27 May '20

Hello, I've noticed that TOC styling on CS wiki is not same as on EN wiki. It should be located on the right side, but on CS wiki is below the article. Could you check what's the issue? Articles to compare TOC styling behavior: https://cs.opensuse.org/Ozn%C3%A1men%C3%AD_nov%C3%A9ho_vyd%C3%A1n%C3%AD_15.1 https://en.opensuse.org/Release_announcement_15.1 Thanks. -- 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

1 0

[opensuse-web] Username
by Guo Yunhe 04 Mar '20

04 Mar '20

Hi, I used to have a wiki username guoyunhebrave with admin permissions in en and zh wikis. But I have registered a shorter username guoyunhe. The old username is not used anymore. To provide it, I have redirected the old user page https://en.opensuse.org/index.php?title=User:Guoyunhebrave&redirect=no Could you delete the old username guoyunhebrave and transfer the permissions to guoyunhe? Thanks! -- Guo Yunhe / @guoyunhe / guoyunhe.me -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

2 3

[opensuse-web] Wiki Chameleon
by vddmfb 01 Mar '20

01 Mar '20

Hey! I recently started contributing to the wiki and I have a question about the Chameleon theme: Does somebody know when the dark mode will be available? It's presented on https://static.opensuse.org/chameleon/ and the Github page but I couldn't figure out when it will be finally implemented on the Website/Wiki. It would be really nice for working late at night :-) Another question is related to the license of uploaded files. When I uploaded the new Thunderbird logo today I haven't been able to choose a license because the page doesn't give me options (only "none"). That's why I inserted Thunderbirds' CC-BY for the logo into the description (https://en.opensuse.org/File:Thunderbird_logo_60.png). What's the best practice for licenses on the wiki? Greetings from Vienna Eddy -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

2 1

[opensuse-web] Possible typing mistake for 'The end of the maintenance period for openSUSE Leap 15.1'
by Amey Abhyankar 23 Jan '20

23 Jan '20

Hello, The URL = https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.1/ 1 line says = The end of the maintenance period for openSUSE Leap 15.1 is now reached. But, openSUSE Leap 15.1 end of maintenance is November 2020 = https://en.opensuse.org/Lifetime The document mean to say = The end of the maintenance period for openSUSE Leap 15.0 is now reached? Regards, Amey. -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

2 1

[opensuse-web] Re: [opensuse-project] Google's Season of Docs
by Sarah Julia Kriesch 11 Oct '19

11 Oct '19

> Gesendet: Donnerstag, 14. März 2019 um 11:53 Uhr > Von: "Simon Lees" <sflees(a)suse.de> > An: opensuse-project(a)opensuse.org > Betreff: Re: [opensuse-project] Google's Season of Docs > > > > On 14/03/2019 20:03, Sarah Julia Kriesch wrote: > > > > > >> Gesendet: Donnerstag, 14. März 2019 um 10:06 Uhr > >> Von: "Simon Lees" <sflees(a)suse.de> > >> An: opensuse-project(a)opensuse.org > >> Betreff: Re: [opensuse-project] Google's Season of Docs > >> > >> > >> > >> On 14/03/2019 18:32, Sarah Julia Kriesch wrote: > >>> > >>> > >>>> Gesendet: Donnerstag, 14. März 2019 um 03:35 Uhr > >>>> Von: "Lana Brindley" <lbrindley(a)suse.de> > >>>> An: opensuse-project(a)opensuse.org > >>>> Betreff: Re: [opensuse-project] Google's Season of Docs > >>>> > >>>>> > >>>>> Most of openSUSE's current documentation is generated along side SUSE's so talking to SUSE's documentation team is probably the best starting point. As a result of this if you look at https://doc.opensuse.org/ it tends to cover things that are in SLE very well but doesn't tend to cover areas outside that, > >>>> > >>>> Yeah, the problem I see is that there is no community-based team for these docs, the community is just relying on a re-badging of the corporate docs. > >>>> > >>>>> for example there's a bunch of low hanging fruit in things like the Gnome User Guide could probably be extended to other desktops like KDE and there are probably a bunch of other features / things that we ship in openSUSE that aren't in SLE that could equally make there way into openSUSE's version of the documentation. > >>>> > >>>> A content audit seems like a good place to start. > >>>> > >>>> > >>>> Since there's no mailing list or IRC any more, it's a little hard to know how to go about building up a community around docs. Do you think this is the best list to try and kick that off, or is there a more appropriate place? > >>>> > >> > >> Given there seems to be interest you can ask the hero's nicely to create > >> a new mailing list or reactivate the old one (I don't know which is > >> easier) we only closed the old one due to inactivity. > >> > >>> Such a team exists. We had many questions on our wiki mailing list in the past how to contribute to the real documentation of openSUSE, because this documentation is only editable by the SUSE documentation team. > >>> > >>> The community is only allowed to edit the wiki and that is the documentation by the community at the moment. > >> > >> This is maybe less true now, all the documentation has been open sourced > >> and is on github, although it's currently in SUSE's github which has > >> traditionally meant that SUSE isn't really expecting external > >> contributions. But still it is technically possible to create a pull > >> request. But really it would be best to discuss the best way forward > >> with the documentation team, they maybe willing and happy to accept pull > >> requests as is they may also be completely unprepared and not have the > >> man power to review a significant number of pull requests. Maybe it > >> makes sense to do the work in some other "New openSUSE feature branch", > >> at worst its possible to fork the documentation into openSUSE's github > >> and work on new areas of the documentation there still using SUSE's > >> templates and methods for building the docs. There might be other ways > >> as well, but the best people to work that through with is SUSE's > >> documentation team. They are friendly people i've met a bunch of them > >> over breakfast at some point. > >> > > We know about the friendliness. 2 years ago we should receive 1 guy for the integration of openSUSE Contributions > > and a better cooperation between the SUSE Documentation Team and our wiki team. In addition, this guy should be allowed > > to contribute to our wiki improvement during the working time. We had a small discussion on our wiki mailing list that > > the technology behind doc.opensuse.org was difficult to understand for openSUSE newbies (without SUSE background). Therefore, > > SUSE wants to be responsible for doc.opensuse.org. > > We didn't watch any Contributions in the wiki by the special SUSE Documentation Team Member. We tried the integration, > > but that was not possible. > > Well a large amount can change in two years and it might be that the > people looking at it this time are willing to figure out the current > documentation system, especially if they have past experience in > documentation its probably what they are used to. From a quick glance > its mostly xml pretty similar to other documentation systems i've used > in the past. I'd be more then comfortable contributing a basic fix and I > haven't touched doco for years so i'm sure people who do it more > regularly will pick it up pretty easily. > > So I wouldn't say its not worth trying again just because of past > experiences especially if there are people familiar with documentation > that are willing to train other people which is the whole point of > Google's Season of Docs anyway. > > Cheers > > -- > > Simon Lees (Simotek) http://simotek.net > > Emergency Update Team keybase.io/simotek > SUSE Linux Adelaide Australia, UTC+10:30 Then let's discuss this topic on the opensuse-web mailing list. That's the mailing list with our wiki Contributors and interested Community Members for the openSUSE Documentation at the moment. Best regards, Sarah -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

4 3

[opensuse-web] [web dev] What cms to use for (potential) opensuse.org website?
by Imad Aldoj 27 Jun '19

27 Jun '19

I'm working on a new webpage as a contribution guide all in one place. I know about chameleon and bootstrap but I don't have experience with the back end stuff (mostly ruby here) So... The content of www.opensuse.org is hardcoded, right? in this case, what do you recommend for managing this webpage in order to integrate well with the rest of the site? the webpage is fairly simple, this "dynamic" functionality might be used to add a new team and its description. -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

4 8

[opensuse-web] Consider re/moving old archive from the wiki?
by Imad Aldoj 21 Jun '19

21 Jun '19

Hi, I just don't see how archive (weekly meetings, etc) should be part of the wiki. This effect the quality of the wiki itself since these pages are no longer relevant or valuable (for most members/users) and it makes up a large percentage of pages that have broken links, don't follow new templates, etc. I'm not saying we should throw it away, I understand that it can be handy at certain cases but similar to the mailing lists archive I suggest moving archive (including everything related to a specific timeframe and can't be updated) to a separate domain that fits the goal and has nothing to do with the wiki(maybe legacy.opensuse.org?) that is still accessible for future reference. -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

3 6

[opensuse-web] openSUSE: Localization_team wiki page is not protected from unwanted changes
by hayyan rostami 15 Jun '19

15 Jun '19

Hi. It seems that https://en.opensuse.org/openSUSE:Localization_team is editable by everyone.I think that's not ok because anyone can edit it's content and write wrong information in this page. For example, one person recently put his name as Persian language coordinator for openSUSE project in this page, while he is not responsible for this task anymore. ( see https://lists.opensuse.org/opensuse-translation/2016-10/msg00025.html ). Sarah Julia Kreisch removed him from list of coordinators in 2016. I but he keeps editing this page and puting his info on this page. I also sent a message to him on April 23 via Telegram and told him that he is not openSUSE Persian language coordinator anymore, with a link of conversations from mailing list in 2016. but it seems that he won't care and he keeps writing his info in this page for a reason. Anyway, shouldn't this page, openSUSE:Localization_team wiki page, be a protected page and only editable by moderators and not everyone? Regards Hayyan Rostami

3 2

Re: [opensuse-web] Update FAQ page
by Guo Yunhe 03 Jun '19

03 Jun '19

I already started editing. 😎 -- Guo Yunhe / @guoyunhe / guoyunhe.me 2019年6月3日下午3:32 来自 hvogel(a)opensuse.org: > Hey, > > On 02.06.19 20:08, Guo Yunhe wrote: > >> I have the following suggestions: >> > > You don't need to make suggestions, you need to make changes. This is a > wiki, everyone can edit and organize content :-) > > Henne > > -- > Henne Vogelsang > http://www.opensuse.org > Everybody has a plan, until they get hit. > - Mike Tyson > -- > To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

1 0

[opensuse-web] Update FAQ page
by Guo Yunhe 03 Jun '19

03 Jun '19

Some users have complained about here isn't an up-to-date FAQ page in wiki. We did have one https://en.opensuse.org/FAQ <https://en.opensuse.org/FAQ> but it is too old. For example, here is no information about Tumbleweed. And the content structure is not very clear. I have the following suggestions: FAQ page should be linked in wiki home page and sidebar. Content should really be what people have asked very often on forums, IRC, mail list, Bugzilla, etc. For example: choose TW or Leap, Btrfs, audio/video codecs, NVIDIA GPU, etc. FAQ for desktop users and server admins could be separated. Each Q&A shouldn't be too detailed. Just provide a link for more information. Would like to hear your opinions! -- Guo Yunhe / @guoyunhe / guoyunhe.me -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

2 1

[opensuse-web] Typos in German Wiki: Mailing lists page
by Maik Wagner 02 Jun '19

02 Jun '19

Hello everyone, I noticed two typos on the following page: https://de.opensuse.org/openSUSE:Mailinglisten Danke für dein interesse an den Mailinglisten -> Interesse (with a capital "I" as it is a noun) Auf lists.opensuse.org findest du eine komplette List aller verfügbaren mailinglisten. -> Liste (is missing an "e" the end and Mailinglisten should also be spelt with a capital "M") Have a good day, Maik www.linuxandlanguages.com -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

2 1

[opensuse-web] Re: [opensuse-project] Google's Season of Docs
by Lana Brindley 18 Mar '19

18 Mar '19

On 19/03/2019 00:32, Frank Sundermeyer wrote: > Hi, > > my name is Frank, I am the project manager for documentation in SUSE. The > whole doc team was on an offsite last week, so nobody from the team had a > chance to respond so far. > > This has become a long thread, so I hope you bear with me when I answer/ > comment in a single mail rather than replying to several posts > individually... . Thanks Frank for taking the time to reply, and apologies that this all blew up while you were at the offsite. > > ----------------- > > On Tuesday, 12 March 2019 11:44:39 CET Ancor Gonzalez Sosa wrote: > >> I usually read complaints about the bad state of openSUSE documentation. > Ancor, this is a rather vague and general statement, can you please provide > more details? Questions that immediately come to my mind are: > > * Does this refer to the openSUSE manuals at http://doc.opensuse.org/ or to > the openSUSE Wiki at http://en.opensuse.org/? Both? > * Where have you read these complaints and have they been passed on to the > Doc team or the Wiki team? If so, what happened to the feedback? > >> Maybe we can use Season of Docs (the Google's equivalent to Summer of >> Code) to fix some stuff. > Maybe we should first find out what needs fixing, where is this needed and > how to integrate existing resources... . I agree. Google's initiative is certainly interesting (and it's always nice to see people caring about open source docs), but it's also set up for groups and writers who have a plan in place, and processes to enable writers to contribute. At this point, we don't really have that. That said, assuming Google offer the program again next year, it could be feasible, if we have managed to get a community effort off the ground by then. > ---------------- > On Thursday, 14 March 2019 00:35:19 CET Lana Brindley wrote: > >> that even the docs mailing list got shut down a little while ago > We decided to shut it down because there was no traffic at all on this list > for one year... . If needed/wanted, we can set it up again on short notice. > Just let me know... Yes, please! > > On Thursday, 14 March 2019 03:35:25 CET Lana Brindley wrote: > >> Since there's no mailing list or IRC any more > That is not true - #opensuse-doc on Freenode exists since many years and the > SUSE doc team is present. Right now I see five people in that channel (including myself), and I've been sitting in there for close to nine months now, with no interaction. Seems like the definition of a dead channel to me. Slack has the extra added benefit of providing scrollback and threading, so it tends to work better for people in different timezones, because the conversation doesn't need to be synchronous like IRC. I also think there's value in being on the same platform as the Write the Docs community. > > On Saturday, 16 March 2019 04:32:41 CET Lana Brindley wrote: > >> Yeah, I'm very familiar with Docbook XML (less so daps), but it is very >> much a tech writer's toolchain. In my experience with upstream >> communities, switching to a markdown language can greatly improve >> contributions from non-tech writers. > I know from personal experience that many discussions in the community > (regardless of the topic) end in tools discussions. Before we open that can > of worms, I suggest to concentrate on content, collaboration and processes > first ;-D. I agree, and having been through community-based conversation projects in the past, it's important to get the team structure and processes right first. It's an important consideration, though, and I don't want it to be forgotten in all the political discussion. > ---------------- > On Thursday, 14 March 2019 09:02:22 CET Sarah Julia Kriesch wrote: > >> We had many questions on our wiki mailing list in the >> past how to contribute to the real documentation of openSUSE, because this >> documentation is only editable by the SUSE documentation team. > This is no longer true since more than 3½ years (June 2015). Since then, > _all_ SUSE product documentation is publically hosted on GitHub and licensed > under an openSource license (GFDL, Apache 2.0, Creative Commons). The SUSE > doc team happily accepts pull requests, bug reports and other help. > The openSUSE documentation that is hosted on http://doc.opensuse.org/, for > example, is hosted at https://github.com/SUSE/doc-sle (SLES, SLED, and > openSUSE documenation are generated from the same source). I suspect from this conversation thread that the invitation to make PRs to the doc team hasn't been well publicised. Another issue I see is that while the documentation is living in github, it's not being treated as docs-as-code, but rather long-form documentation, which makes it much harder to make quick patches. > > Again, we are open for cooperation and collaboration. We have NO intention > at all to exclude the community. > > BTW: The complete doc toolchain the doc team is using is also hosted on > GitHub and is used by people from outside SUSE. > The _complete_ work the SUSE doc team does is public and transparent for > everyone. This is great, and it gives us a really good starting point for a community effort. > On Thursday, 14 March 2019 10:33:46 CET Sarah Julia Kriesch wrote: > >> We know about the friendliness. 2 years ago we should receive 1 guy for >> the integration of openSUSE Contributions and a better cooperation between >> the SUSE Documentation Team and our wiki team. > [...] >> We didn't watch any Contributions in the wiki by the special SUSE >> Documentation Team Member. We tried the integration, but that was not >> possible. > I was involved in these conversations and supported the solution you > mentioned above. In hindsight, it would have been better to not make this > promise. Not because we did not want to help. Quite the opposite. We made > this promise because we really _wanted_ to help. Back then the doc team was > under heavy work load (and it still is). We had hoped to find time to > squeeze in the work for the wiki (because we wanted to). It turned out that > it did not work out. And still does not. > I should have let you know about this much earlier. I failed to do so and > you have every right to be angry about us not fulfilling our part of the > agreement. > But be rest assured that it was not done because of disrespect for the > community, but because of lack of resources. > ---------------- > On Thursday, 14 March 2019 10:06:57 CET Simon Lees wrote: > >> But still it is technically possible to create a pull >> request. > Yes! And bug reports, if you prefer that. > >> But really it would be best to discuss the best way forward >> with the documentation team, they maybe willing and happy to accept pull >> requests as is they may also be completely unprepared and not have the >> man power to review a significant number of pull requests. > Reviewing pull requests is part of our daily work and should be doable > (unless you do not attempt to rewrite everything with several hundered > requests ;-D). We may not always react within hours, but no work will be > lost or ignored. > the same is true for bug reports - they will usually take longer to get > fixed, but we will not ignore them. > >> Maybe it >> makes sense to do the work in some other "New openSUSE feature branch", > Our tool chain and DocBook XML make it possible to create parts of the > documentation that is only valid for one product flavor (openSUSE in this > case). This is true for single words, sections, chapters or even whole > guides. Therefore adding openSUSE-specific content should not be a problem. That's quite an unwieldy feature in Docbook, but it's a good beginning. >> at worst its possible to fork the documentation into openSUSE's github > I hope it will not come to this - all parties would lose in this case. I agree, and as I said in an earlier mail it only makes sense if the internal docs team is hostile to patches, which it would seem you are not. > >> There might be other ways as well, but the best people to work that >> through with is SUSE's documentation team. > That would really be appreciated. And I am volunteering to continue this > discussion with you - just let me know where (in case it is moved somewhere > else). > I think the suggestion was to move to opensuse-web, so I have added them to this mail. Lana -- Lana Brindley Technical Writer - SUSE Manager "The question is," said Alice, "whether you can make words mean so many different things." -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

1 0

[opensuse-web] Pls update following values at https://en.opensuse.org/Portal:Build_Service
by Amey Abhyankar 14 Mar '19

14 Mar '19

Hello, I don't have access to https://en.opensuse.org/Portal:Build_Service Hence, request you to update following fields = i) Update following old values with new 1's from https://build.opensuse.org/ = currently ( June 2018 ) hosts 53,219 projects, with 468,316 packages, in 79,794 ii) openSUSE:Factory project, = Replace broken link with new link i.e. https://en.opensuse.org/Portal:Factory Thanks & Regards, Amey. -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

3 2

[opensuse-web] bad wiki Info| output
by Felix Miata 08 Mar '19

08 Mar '19

https://en.opensuse.org/index.php?title=Template:Sandbox http://fm.no-ip.com/SS/Suse/wiki20190307editInfo1.jpg What am I doing wrong to get {{{1}}} instead of the content following "{{Info|" in the editing textarea? "Here is how to use <tt>nomodeset</tt>. When the first openSUSE Installation menu appears, move the highlight to "<tt>Installation</tt>" and strike the "<tt>e</tt>" key. Then move the cursor to the end of the line (which may be wrapped) beginning with "<tt>linux</tt>" and ending with "<tt>splash=silent</tt>" and/or "<tt>quiet</tt>", and without typing any quote marks, append a space and "<tt>nomodeset</tt>", then proceed by striking <tt>F10</tt> or <tt>Ctrl-X</tt> to see if black screen and no signal are avoided. If you see a green bar moving across the bottom of the screen that's good. Strike the <tt>ESC</tt> key to see more information while the boot process proceeds." My object is to make it look like the paragraph near the bottom: inxi may not already be installed. It's in the OSS repos ready for zypper or YaST to install. Output from inxi -GxxSM is a good starting point to provide information about your computer in any video issue help request. on https://en.opensuse.org/SDB:Nomodeset:_Work_Around_Graphic_Upgrade_&_Instal… -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

3 3