-----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:
...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: firstname.lastname@example.org To contact the owner, e-mail: email@example.com