On 8/8/21 8:17 PM, Adrien Glauser wrote:
It's simple, Richard: - you want to question, contest or otherwise undermine presuppositions that will require to (re) build part of the context behind the initiative and trigger further arguments? awesome! start new topic on the docs ML or on GitHub, so that other volunteers working with me can have their voices heard too (I am not their speakperson outside of the scope of the request at the origin of this thread and they are not subscribed to this ML let alone follow this topic) - you want to help in a way that complies with the request at the origin of the topic? nice, that's the right topic!
Have a nice week!
Given that a large part of this topic is not just limited to docs but also the wiki I believe that this project list is a perfectly reasonable place for such discussions. As the docs team you are more then entitled to take content from the wiki and use it within new docs, how ever without broader project consent you can't remove content from the wiki. While I know you have presented some justification for this at the openSUSE conference not everyone has seen that, the best place for you to present your case for removing content from the wiki and moving to a new docs system is this list (but probably not this thread). Really it is up to the docs team to justify to the rest of the project why they think it is the best way forward and to sell the move. Yes if you don't get broader project consent to remove content from the wiki it will be a bit more work for you but at the end of the day I don't think it has to lead to a significantly worse user experience. After all the docs team is well within its rights to add a link in a banner at the top of any page saying this topic is also covered in the docs with a link to the page. I am sure people also don't have a problem with removing information that is so out of date that it is no longer useful. Or with adding banners that indicate that info on a page is likely out of date and may not be reliable (There has been a number of times where out of date wiki pages have still provided me with useful info on resolving a problem). Beyond that it shouldn't be hard for the docs team to either write a tool or manually watch certain pages for changes and integrate them into the new docs, from the sound of this thread such an approach seems like it would appeal to members of the project that have had a significant history of contributing to our docs. Yes fragmentation isn't always good but if it leads to more contributions from more people maybe it also isn't bad. At the end of the day though the decision around whether we have fragmentation or not here is one for the broader community in this area not just the current docs team, as its the broader community that has spent the last 10+ years putting the wiki together. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B