October 2020 - openSUSE Documentation - openSUSE Mailing Lists

[opensuse-doc] opensuse-docs team sync message 20201027
by Attila Pinter 27 Oct '20

27 Oct '20

This is a sync message collecting key information from the Telegram group (bridged to #docs:opensuse.org and #docs at discord.gg/opensuse) and Trello. These "sync" messages are intended to keep everyone in the Docs team informed utilizing the mailing list. The "sync" messages are going to be sent on a weekly basis or if something is important will be shared pretty much immediately. If you have something to add please feel free to do so here and will be added by me on Trello for example. ========================================================================= ========================================================================= What we've been discussing on Telegram and Trello since the last meeting: - Planning the next meeting Badr said: "I propose another 2 or 3 consecutive meeting since we have a lot to discuss. For example the website, we need to discuss my proposal and any other proposals out there. I've also added some options to discuss regarding the documentation platforms in a Trello list. etc." Adrian said: " I am all for having more meetings but I also hear those who want to start being productive. How about this: - we meet the upcoming week Thursday or Friday - we carve up our live time so that every subgroup/role (collecting support data, doc contents & platform, videos) have their fare share, perhaps 10-15 min max. - the rest of the time is for new tasks or "meta" things (i.e. adjusting how we work)" Attila said: "Maybe in the meanwhile we could get a few things rolling on Trello for instance - which I'm going to sync tomorrow to the ML -. Like populating the "Reference documentation" list which already has some really great topics/tasks listed. Would be also nice to settle internally on the platform we going to use." Infrastructure related: ======================= - Looking into acessing either the Elastic deployment on the openSUSE infrastructure (if exists) or deploying our own by myself for analysing the main openSUSE communication channels. This would aid our effort greatly in terms of prioritizing issues. If I deploy ELK acess will be provider to the Docs/Web/Heroes team as well. - Moving Trello to a Kanban deployed on openSUSE infrastructure. Maybe we can help out with this the Web/Heroes team. https://en.opensuse.org/Help:Kanban - We're looking for a documentation platform to be utilized for publishing documentations. Currently we have the following solutions on our list (do feel free and raise your opinion): - Github pages - Read the Docs - MkDocs - Gitbook.com - Gatsby - VuePress - Docusaurus - Antora - en.opensuse.org (current wiki) - Adoc (it uses asciidoc and antora and used for SUSE Manager docs as well, upstream doc: https://www.uyuni-project.org/uyuni-docs/uyuni/index.html Toolchain: https://github.com/uyuni-project/uyuni-docs. Lana said: "interestingly, since we moved the suse manager docs from docbook to adoc, we've also had a huge uptick in external contributors, too") Actual documentation work ========================= - Reference documentation list population. Currently has the following items and looking to add more: - Comparison chart for supported desktop environments? - Guide similar to GNOME guide for all supported desktops - Tumbleweed snapshots workflow vs. Tumbleweed packages workflow - Teams: You can find more here: https://en.opensuse.org/Opensuse-docs/prep-meeting-10-23#Roles Still looking for volunteers fo the Video team, Collectors of Most Pressing Issues and writers of course. If interested feel free to reach out! As a refresher from the last meeting: > "2) Continuity >Job => Make sure no one is left behind, takes minutes in meetings and tries to >keep the mailing list people in the loop, keep tabs on who does what, etc. > >3) Pressing Issues >Job => Mobilize search & data aggregation tools (oS Heroes may grant access to >Elastic Search). Consolidate data about the pressing issues. > >Attila volunteers for 2 and 3. > >4) Videos >- Ivo, Emmanuel >- They will work on a script they will share on the wiki. >Topics: >1) explain the differences between the distros & differences with Debian-based >distros >2) Yast & openSUSE specifics, especially YaST >3) Plasma "tips & tricks": power-user workflows, widgets, tiling features, >exposé-like features, mult-desktops / multi-monitors >They will get in touch with the marketing department, seeking for help and >syncing up for *promotional* contents. >They will share their exact needs. -- Br, A. -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

1 0

[opensuse-doc] Meeting minutes of openSUSE-doc meeting 20201023
by Attila Pinter 23 Oct '20

23 Oct '20

Thank you all for joining the meeting! As a side note: in future meetings please avoid going so hard off-topic ;) -- Br, A. Minutes 23rd of October 2020 ============================ 3 rules of communication ------------------------ Agreed that: - everyone use their favorite channel of communication - every decision made are first shared to MLs & then stored on the Wiki at some point. Some reasonable delay should be tolerated. - MLs will be used on a regular basis to keep contributors & others in the loop. Ivo's proposal to add to the documentation ------------------------------------------ Need to add clear guidelines catering to professional or more generally *conservative* users -- typically corporate -- to keep their workflow afloat pre- , during and after *migrating* from SLES to Leap. Need to chart the most useful repositories for professional users. Groups ------ 1) Docs proper Every section of the docs has 1 maintainer; everyone can move throughout sections freely. - Mike - Attila - Baldr - Adrien Need to make explicit how we approve and peer-review every step along the way. Need to decide for a platform -- static doc generators seem to fit the bill. Need to have to make sure who takes responsibility of the 3 sections (before, during, after). 2) Continuity Job => Make sure no one is left behind, takes minutes in meetings and tries to keep the mailing list people in the loop, keep tabs on who does what, etc. 3) Pressing Issues Job => Mobilize search & data aggregation tools (oS Heroes may grant access to Elastic Search). Consolidate data about the pressing issues. Attila volunteers for 2 and 3. 4) Videos - Ivo, Emmanuel - They will work on a script they will share on the wiki. Topics: 1) explain the differences between the distros & differences with Debian-based distros 2) Yast & openSUSE specifics, especially YaST 3) Plasma "tips & tricks": power-user workflows, widgets, tiling features, exposé-like features, mult-desktops / multi-monitors They will get in touch with the marketing department, seeking for help and syncing up for *promotional* contents. They will share their exact needs. -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

1 0

[Fwd: Re: [opensuse-doc] Upcoming meeting]]
by TomasK 23 Oct '20

23 Oct '20

On Fri, 2020-10-23 at 11:23 +0200, Adrien Glauser wrote: > > > I am using these things to strike a balance between the pain of > > > turning very circumstantial texts into media wiki syntax and the > > > pain for others to have to jump between too many tools. So far > > > we've been able to work with just trello, google docs, the > > > opensuse wiki, telegram and emails -- not too bad don't you > > > think? :) . > > > > There is no need to get defensive. > > > > I am using these things to strike a balance between the pain of > > > > turning very circumstantial texts into media wiki syntax and > > > > the pain for others to have to jump between too many tools. So > > > > far we've been able to work with just trello, google docs, the > > > > opensuse wiki, telegram and emails -- not too bad don't you > > > > think? :) . > > > > > > There is no need to get defensive. local = opensuse.org > > I specifically refer to opensuse documentation on this link: > > https://docs.google.com/document/d/1zERjqqQrWBAoM3B25BIQ4hvTFU_Y7S8 > > L57b > > h-wb6ld4/edit?usp=sharing > > Followed by bunch of third party resources listed in your telegram > > post. > > > > These "third party resources" are websites, which don't do much > except > serve HTTP requests. I mentioned them so that we can visit them, look > around, a more forward with some baseline of an idea. Nothing else. > Pure references. > > My understanding is that you want all of us to abide by a principle > that says that there is moral requirement not to use non-FOSS > software > when there is a FOSS alternative. But I fail to understand how this > principle applies to websites in general, or to the use of them as I > was suggesting. If you meant this principle to rule out not websites > but Telegram, I don't know what to say except: > 1) that I am trying to make everything to not create a gap between > users and non-users, as you can witness from my activity on the MLs; > 2) that the entire openSUSE community is present on many of these > non- > FOSS platforms, such as Discord and Telegram (if we mean "non-FOSS" > to > cover server code and not just client code). > > On the other hand, I am trying to acknowledge the fact that you don't > feel at ease with these websites, and my assumption was that this was > the case because you felt like the normative principle stated above > made them morally wrong to use / browse. > > I think you are mistaken in you application of the moral principle (I > mean, does Richard Stallman buys his airplane tickets from Emacs?), > but > I am ready to suspend judgment and to make a step in your direction. > Hence my suggestion that you clarify which tools you think are > permitted as per your understanding of the moral principle. > > I hope this is crystal clear now. > How is all this relevant to opensuse documentation and website improvements? This is a statement with question mark - no answer or explanation needed - I have no interest in digressing from the and discussing politics I interpret your long email as - we work though the social media and do not intend to change for now. Fair enough - I will find different place/way to help. Tomas -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

1 0

[opensuse-doc] Upcoming meeting
by Attila Pinter 23 Oct '20

23 Oct '20

Dear All, Just a heads up. The next meeting will be held on 10/23 Friday at 6pm UTC. Do check the pinned message from the Telegram group (even if you can't join) here: https://telegra.ph/pinned-2-10-15 -- A. -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

3 5

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

16 Oct '20

> 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

2 1

[opensuse-doc] Re: [opensuse-project] Re: Refreshing the openSUSE learning experience
by Adrien Glauser 14 Oct '20

14 Oct '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hey again Lars, Yes, we are not foolish, Repair and Protect should absolutely work together. For us it's definitely Protect now and Repair later. Of course we are living in a world of entropy: docs decays, code rots, volunteers marry and grow a belly. We have to live with that and the best we can do is promote *knowledge transfer* to fight the entropy, throughout all scales of proficiency between engineers and absolute newcomers. Be assured that we don't want to find the one-size-fit-them-all kind of solution. I think we are going to be very empirical about this -- start from most common and painful issues and give visibility to the most simple combination of technical details and best practices for preventing or fixing them. Anyway, all this is just words until we have something concrete to show you, so I better go back to work. Have a pleasant end of the week, Adrien 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 > -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEU4ol/0bSQTwqpAkNMy9Aieh+wJwFAl+HbzkACgkQMy9Aieh+ wJxHRgf7B/xaaiWvIwFzQZGLWBE+2ypVEcJhDzh+N9dOV4FPyvXcIPTgRadtK5sY HVWd68tEgdc/mD5lhtGPTClOao44aEu17PnRQtC57y9evUC4ZRgp3ufIwgi/YVfm NBk7t1dYoyn8RJZO4rEmcJTQ8NkGjW2YDKUK1dwC0HeGJE4XPcllo52IJ2PU2r/D 0hgkFsZy9HA6/EhnF1gAiMCcdlBs4huQVNHym7X1MrTwmWjRJkmQgAxZ6N8JNDn8 KViF/b7Gbbs5uGngI4QIdPbFJ7wxpJTJGVYvl0IFTBiHUA7QPJlA5ql1BuHhzdte TdHmgLgtK2Eqtgwz8DqAUtkmftP/Lg== =PJUf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

1 0

[opensuse-doc] Re: Refreshing the openSUSE learning experience
by sergio 14 Oct '20

14 Oct '20

Hi Lars, El mié, 14-10-2020 a las 16:22 +0200, Lars Vogdt escribió: > 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. I have always missed that button. Couldn't that menu be shown always as the footer? Kind Regards -- Sergio Lindo Mansilla <slindomansilla(a)suse.com> QA Engineer SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer

1 0

[opensuse-doc] Re: Refreshing the openSUSE learning experience
by Adrien Glauser 14 Oct '20

14 Oct '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi again Lars, Your point about a general-purpose, cross-platform search engine for all things openSUSE has a lot for it, especially in view of the fact that support on instant messaging platforms is currently not discoverable. 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. As I see it our "refreshing the learning experience" project is primarily trying to implement the second. If we follow this logic it is clear that if someone has a great idea that falls under the "source of truth & best practices" category, it should be fed back into whatever static doc we have so that things don't stop improving. But again, I don't think this requires a cross-platform search engine. To be sure, I agree we need a search engine, just not for fighting fragmentation; I think we need one to simply make everyone squeeze out as much juice possible from "the source of truth & best practices", and indeed it shouldn't be too difficult to avoid relying on Gooooooooooooooooogle for that. 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. Cheers, Adrien > The heroes meanwhile have control over all tools, that you need for > this purpose. That means especially that they have access to the > data(bases) with the content in it. > > I think it might be a cool (SoC?) project to provide a search engine > that covers: > * forums > * wikis > * docs > * mailing lists > * matrix (and the bridged chats) > * ... (and other tools I forgot) > > That does definitively not mean that I want to stop you with your > project. I just think we could try to work on multiple areas, > keeping an overall picture in mind. > All our tools provide specific solutions for our community. All have > their meaning and a right to stay. > > But if we want to help our community to get good answers for their > specific question, I think relying on Google alone is not the b > estidea. > > Lars > -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEU4ol/0bSQTwqpAkNMy9Aieh+wJwFAl+G+OoACgkQMy9Aieh+ wJxniwf/QLsFU9HD2d6AQMvIAYlNcOr+kt6NL47K2IaoZ55of0RDIGOFkz79OR8o 2BTVHI5+eySeGo8dTbusVTcsk5cNQN7O2h6c7JXSWDKt2HEfX9/WKXbKTHFrruct tU7vnuq9n8QWa0Mdmo7X0NVXf5Fn01IkA53ePg/nBRVroRtm6vAB4zxvHxcca4OL TuXFPVMolHOAc63If/Y3eML11i2BIfJBBXOisCeDIkghYH9lFZoHhk6kkVGO6jAb aCiBRXYEZG0fpUh6jWUCaJ1+4JUBnd/HCiOwYYB2j1QlVswxOfuIgQmkNXUZ3PnF HHYeRxtsK+/I3CxYwwPhyvOhdVm2Qg== =H6kQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

1 0

[opensuse-doc] Re: [opensuse-project] Re: Refreshing the openSUSE learning experience
by Adrien Glauser 14 Oct '20

14 Oct '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hey Lars, Thanks for jumping in! Moodle surely taps into my memories of college! :-P I think it has a place in an educational setting but my worry is that it might feel a bit too formal to the end user while lacking the flexibility we want to be able to make the most of both visual and textual contents. For example I doubt Moodle packs a full-text engine, right? Or more generally that it shines at allowing the end user to discover topics just as good as a wiki... So yeah, we need: - - something full-text searchable - - with good discoverability features - - easy to update - - pleasant to browse and visually enticing. The last point is perhaps where wikis fall flat the hardest (though there are exceptions), but all things considered these conditions don't really decide between a wiki or a documentation generator engine with full-text search. I think the precise platform will become obvious once we're done with our first todo list. So yeah, if you have other suggestions that tick these boxes that'll be very useful, but Doodle makes me squint a bit. Cheers, Adrien Le mercredi 14 octobre 2020 à 06:03 +0000, Lars Vogdt a écrit : > Am October 13, 2020 12:59:03 PM UTC schrieb Adrien Glauser < > adrien.glauser(a)gmail.com>: > > 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. > > Please excuse me jumping in here, but maybe it's helpful information > for you or others that I started: > > https://moodle.opensuse.org/ > > a few weeks ago. This is not about documentation, but a learn > management system, that could - theoretic ally - help users to learn > to understand the details of some Linux or open source parts by > reading documentation or presentations, discussing in topic centric > forums/ chats or even prove their knowledge in tests - around > specific topics. > > So far, the login with your IDP account should already work. What is > obviously missing there is content and trainers/ teachers, that want > to provide course material and teach people. > > > > > > Any help is welcome, especially > > > > for: > > > > > > > > - writing, editing and peer-reviewing: We would be delighted to > > > > benefit > > > > from more knowledgeable people to help us refresh, deepen and > > > > harmonize > > > > openSUSE's wikis and other documentation platforms > > > > > > > > - video editing: Our video staff is looking for people > > > > interested > > > > in > > > > producing video contents and / or willing to script and record > > > > video > > > > tutorials in English > > JFYI: moodle would allow to summarize/ combine tutorial videos, docs, > dedicated wikis and other stuff under one umbrella. One .opensuse.org > umbrella with full control for interested community members. > > Regards, > Lars > > > -- > Lars Vogdt <Lars.Vogdt(a)suse.com> > - BuildOPS Engineering Team Lead - > SUSE Software Solutions Germany GmbH > (HRB 247165, AG München), GF: Felix Imendörffer -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEU4ol/0bSQTwqpAkNMy9Aieh+wJwFAl+GyFMACgkQMy9Aieh+ wJzDvwgAgv3Cxdb976JxsHkkTjKFEQXzdANw3enuYIFifWiQv8JDEUzrnqjaf3Bm 0LVkKRZp7O2GpVsd9BOYrYJypVfcv0VYgCcpFvDZh+8hp9ZSesjiRW/BdAhayIC6 mkER6awx307kHFoOvJbEkOvVDPV8Aep2lc9yHdGHsOdJ8vVeq3IDcd986rl72ytz udQtLgz3uLtNOKOU1trgJpEWifBO7KKyxcRj99ohW+3IwTUprlaq3V97Ims7qD27 Zx6CEG2Tv5jihnyZGFI/5C9CgG2gay2ET0mrzfkGLiKDJhZa2x/O1qnzibZZDcaW SqkS6r7x4JzX6+4S11xkzGE9tYHdbw== =1ALA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

1 0

[opensuse-doc] Re: [opensuse-project] Refreshing the openSUSE learning experience
by Adrien Glauser 13 Oct '20

13 Oct '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 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 - - https://t.me/openSUSE_group bridged with the Freenode IRC and the Discord ("chat" channel) - - "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. 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 Le mardi 13 octobre 2020 à 07:10 +0000, Lubos Kocman a écrit : > Thank you very much for your effort Adrien, > > what I'd love to see is less question on reddit.com and more > questions > on *.opensuse.org hosted domains. Or perhaps we just need to better > integrate with reddit :-) > > On Mon, 2020-10-12 at 17:16 +0200, Adrien Glauser wrote: > > Hello, > > > > On behalf of our group of volunteers working with the doc team I > > wanted > > to share with you this annoucement. > > > > Cheers, > > > > Adrien > > > > --- Join our team and help us improve the openSUSE learning > > experience > > ! --- > > > > For years openSUSE has meant more than one distribution. With the > > recent addition of Kubic and MicroOS to the Leap & Tumbleweed > > family, > > different package sets, release models and workflows can be > > difficult > > to keep tabs on. openSUSE's ecosystem is in full blossom, but even > > jungles sometimes need a clearing. > > > > This is why a group of volunteers has taken up the task of > > improving > > the learning experience for all users -- regardless of their > > experience > > and expertise. For new users, we want to make sure they can > > identify > > what best fits their needs, get the right tools and seamlessly take > > over from the post-installation screen. For experienced users, we > > want > > to provide them with detailed documentation that is easy to update, > > so > > that their experience and expertise can benefit others. > > > > We believe that from engineers to end-users, everyone deserves to > > have > > confidence not only in their OS, but in the way they're using it. A > > chain of trust like this is made of a user-friendly documentation > > where > > technical details are balanced with evidence-based good practices. > > > > It is with this goal in sight that we are calling the community for > > more volunteers. We are already set on course but the journey will > > be > > quicker -- and funnier -- with you. Any help is welcome, especially > > for: > > > > - writing, editing and peer-reviewing: We would be delighted to > > benefit > > from more knowledgeable people to help us refresh, deepen and > > harmonize > > openSUSE's wikis and other documentation platforms > > > > - video editing: Our video staff is looking for people interested > > in > > producing video contents and / or willing to script and record > > video > > tutorials in English > > > > - testing: We need more people to help us test out already known > > work- > > flows and settings on new hardware, see if what used to be > > recommended > > still should be. > > > > So now you can't say you didn't know. Do reach out and come with us > > shape the future of the openSUSE learning experience! You can find > > us > > on the following platforms: > > > > - Telegram group: https://t.me/opensuse_docs > > > > - IRC bridge: https://matrix.to/#/#docs:opensuse.org > > > > - Discord bridge: https://disboard.org/fr/server/366985425371398146 > > then Contributing > docs > > > > - mailing list: https://lists.opensuse.org/opensuse-doc/ > > > > Last but not least: this is part of a collective effort so we are > > happy > > to relay to you that get.opensuse.org -- the future entry-point to > > the > > openSUSE web platforms -- is also looking for volunteers. Their > > goal > > is > > to deploy by November and they are still looking for committers to > > the > > repo at https://github.com/opensuse/get-o-o as well as translators. > > Translation tasks can be picked up at http://l10n.opensuse.org. > > Everyone interested is welcome to get in touch with Stasiek > > Michalski > > for details. > > > > Looking forward to meeting you! > -- > > Best regards > > Luboš Kocman > > Release Manager openSUSE Leap > > SUSE Software Solutions Germany GmbH > Maxfeldstr. 5 > 90409 Nuremberg > Germany > > (HRB 36809, AG Nürnberg) > Managing Director: Felix Imendörffer > -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEU4ol/0bSQTwqpAkNMy9Aieh+wJwFAl+FpJcACgkQMy9Aieh+ wJyn2gf9FKPPNGAnKOX5hfjwRyK0RKja3XqJVimYoegyeUMx5ZkVwbtlGgI1rxcs RniQjgoB0iKyf02tCnUU0dXvOb5BtvlW7mbMu8RI7dWhZp8jxcLASJmHtUrWszJu Iv2Pyjo2Qq0cXyhVTUV/yk+PgCo49SIQqGreNC/hFU/BF9UJgKAZ+ml1GV+QaPAs /t4KSSX4BbPNYoNnBGiZOouTYZqMXARDBFZZBRPmdEmSdZcGsqBMhH/xwT4h98Wm x3XHkR4yXZM+WmGaxg9c9sH9DnyrXlYew76KY+yt0O1bMazTq0V2s98vR9cSNFLZ 1XngFTPlaVyH5Oz+NysGmGcL7NiBuw== =ebzv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

1 0