On 10/8/19 1:32 AM, Frank Sundermeyer wrote:
On Sunday, 6 October 2019 12:47:15 CEST Ish Sookun wrote:
Hi,
I am a member of the SUSE doc team and can only confirm what has already been said before:
During the openSUSE Asia Summit's community meeting we discussed things that should be & can be done. One of those was about the openSUSE documentation.
I checked doc.opensuse.org.
I notice that all the documentation are currently copyrighted [1] by SUSE. Although the docs are granted GNU Free Documentation License it sounds proper to have the content ownership under openSUSE. Such a thing should not wait for the creation of a foundation.
SLE and openSUSE have the same code base and this is also true for the documentation. The SLE documentation is written by the SUSE documentation team and the copyright lies with SUSE. The openSUSE documentation is generated from the same sources as the SLE documentation (https://github.com/SUSE/doc-sle).
It also appears that the documentation workload is currently on the shoulders of the SUSE documentation team (only). I would like to help, more specifically collaborating with Kubic/MicroOS team to have a Container documentation. How should I proceed?
It was already pointed out that https://en.opensuse.org/Portal:Kubic is THE place for Kubic documentation. In case you want to contribute to the standard openSUSE documentation, above mentioned GitHub repository is the place to start. If you have got questions, feel free to contact me by PM.
I somewhat disagree here, from the discussions we've had in openSUSE it would be great if we had the documentation all in one place that means not half on the wiki and half in docbook. If openSUSE contributors can write documentation to an acceptable standard I don't see why we shouldn't have chapters on kubic or KDE or XFCE or any other openSUSE software that people are willing to contribute. My understanding is it should be simple enough to build these chapters just for openSUSE. Maybe there needs to be some modifications to how the repo is organized if the current setup can't handle that. It wouldn't be hard to for example move the openSUSE documentation into openSUSE's github and merge in the changes from the SUSE documentation given there probably won't be much overlap. There are parts of the openSUSE community that would like to be translating the documentation and providing parts of it in printed form to students and lecturers and in my opinion at least docbook is a far better format. This is one of the main things that came out of our community discussions on Friday. So if openSUSE contributors such as Ish would like to work toward adding new sections to the openSUSE docbook then I think that's something to be encouraged rather then telling people to go back to the wiki. If the SUSE documentation team doesn't have time to help getting this setup that's understandable but there are also people in the community happy to help with that part as well (It's just no one has started working on additional content creating the need for it). 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 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org