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