-----BEGIN PGP SIGNED MESSAGE-----
Thanks for reaching out! You've made many interesting points and I
won't be able to reply to each of them now (see however my PS for a
reply about the target audience).
My takeaway from your message is that we would be super happy to
benefit for your experience in terms of QA, so I am glad you found us.
As you can imagine, right now we are going through the stage of
welcoming new people and structuring ourselves around key priorities
for refreshing the docs. I have to say this is rather a fast-paced
moment of interactions, and I have to admit that the mailing list is
probably going to be outpaced by a large margin.
So how about you join us on Telegram or Discord or the IRC? All these
platforms are bridged as far as our discussion group is concerned. Come
and say Hi so that we can make the most of your help!
- -- Long post-scriptum about target audience --
- - we want to prioritize new users but questions about pre-installation
are outside of the scope of our effort; this means that "new users" is
closer to "Linux-aware people willing to spend 10 minutes installing
their distro" to "absolute beginners who would prefer not having to pay
attention to installing / configuring things to their needs";
- - we want to prioritize new users but we care about knowledge transfer
over time, because that's the best way of having a genuine community
rather than a giant help desk, and this is why we want the docs to be
easy to maintain over time to keep up with the best practices (and not
just the descriptive technical information);
- - yes people near the "expert category" care mostly about not being
slowed down, but thanks to the immense work of the doc team there is
already ample documentation for experts; so in the short-run we
probably won't have much to contribute to the expert-oriented doc.
Le mardi 13 octobre 2020 à 11:47 +0200, sergio a écrit :
El lun, 12-10-2020 a las 17:16 +0200, Adrien Glauser escribió:
--- Join our team and help us improve the
I think it is a great idea.
(I was planning to do youtube videos in Spanish with
English/German/Greek subtitles for the same reason, but not only
openSUSE, also for SUSE products. There are still more people that
don't know/understand the difference between openSUSE and SUSE,
Leap/Tumbleweed/SLE than people not knowing what is Linux. Still sad
how even less people know about GNU).
I may come late to the party, since the launch seems to be next
you may have already plan and done a lot of work in a specific
But, better late than never.
I was my whole life surrounded by non-technical people (family,
friends, etc), and while that could give only an incomplete picture
non-technical people, I feel confident enough to say that I
non-technical people better than most of other technical people who
most of the time surrounded by technical people that just rejoice
themselves in their own world vision.
Also, the few technical people I was surrounded by, were using
or Mac, and they didn't like GNU/Linux because of the way they
to use computers. So, even between technical people, there aren't the
So, I would like to share my thoughts on that.
For new users, we want to make sure they can
what best fits their needs, get the right tools and seamlessly take
over from the post-installation screen.
The approach for non-technical new users and technical new users must
be different. They don't have the same mindset.
Non-technical people don't install their OS, they buy computers with
pre-installed OS. Their entry point is telling them where to get
computers with GNU/Linux pre-installed. There is no guarantee that
know a technical person who can install the OS for them. I have seen
that most of the time.
(That could be an opportinity to get sponsoring form the companies
sell computers with GNU/Linux pre-installed, specially openSUSE:
Tuxedo, SlimBook, etc, doing also unboxing and reviews of their
Also, remember that each time you tell them that they need to learn
to use the console or how the system internally works in order to use
it, Apple wins.
The server side is not an area for non-technical people, that is why
the functional superiority of GNU/Linux and potential improvements
won against Microsoft and the few Apple's intents.
You may have hear that Microsoft is loosing the battle against
GNU/Linux in the desktop.
And you may think that is the prove of GNU/Linux superiority. But,
technical users don't care about superiority, they care about
The real reason why Microsoft has lost the Desktop is because non-
technical people have left workstation and laptops to use Smartphones
and tablets. (Microsoft hadn't success on that Market) and then
workstation and laptops only have one type of customers that gives
money: technical people, and those are splitted between Windows, Mac
and GNU/Linux A, GNU/Linux B, GNU/Linux C, etc. So, they are not
technical customers to sustain Windows desktop (this is why they are
focusing on cloud services).
For experienced users, we want to provide them
documentation that is easy to update, so that their experience and
expertise can benefit others.
Technical people don't care if they have to install something or not,
but they care about how much time they need to get started (getting
started guide) and how good the documentation is for the time they
to know more (rereference documentation).
I assume that you are technical people and have already suffered bad
and incomplete documented software. But, there is also a problem that
even technical people overlook: Too much documentation.
A example of that is Open Build Service documentation (sorry ;)).
is no quick getting started for OBS, because all the needed
to getting started is spread in the vast, complete and long
If you are thinking on the people who were successful using that
documentation, think twice. If we want to bring new people, we need
think on those that run away because the documentation didn't work
them. And they will run away if/because there are other choices that
offer them what they want/need.
It is with this goal in sight that we are calling
the community for
- writing, editing and peer-reviewing: We would be delighted to
benefit from more knowledgeable people to help us refresh, deepen
harmonize openSUSE's wikis and other documentation platforms
I am sure that there are people with more knowledge, more thecnical
experts than me, but I would like to offer my knowledge where I can
most importantly help molding how that valuable technical knowledge
be presented in a easier way for newcomers.
- video editing: Our video staff is looking for
producing video contents and / or willing to script and record
tutorials in English
I also think that the main language should be English for several
I just want to mention that it is a pity how much native Spanish
speakers cannot consume content in English. And there are a lot of
native Spanish speaker in the world. My expectation is that producing
technical content for Spanish speaker could increase the
That is why my intention was to create content with Spanish as main
language and, because I can, adding English, German and Greek
So, I would not like to self-record English videos, but because I
to self-record Spanish videos, maybe they could be included in a
Spanish dedicated openSUSE channel.
- testing: We need more people to help us test
out already known
workflows and settings on new hardware, see if what used to be
recommended still should be.
As an idea, workflows can be automated using openQA, so if a workflow
stop working, openQA will tell.
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
on the following platforms:
So, hopefully I don't get too late for the approach of how to
My proposals would be split in three parts
1. Getting started
Contain just enough information to start using the software
Contain just enough information to know where to look for the list
of available features (reference doc)
Should also contain enough information to know where to look for
more information about features (reference doc)
2. Reference doc
Assumes that the getting started guide was followed
Contains a brief description list of features with no deep
Also contains deep feature documentation
alike (ideally on
stackexchange, which already has SEO and is known/used by a
where users can get answers about corner cases and where "we" can
about possible missing or misleading information on the
Avoid ML for non-technical people.
In addition to that structure,
Create and entry point for non-technical newcomers
- Where to get computers with GNU/Linux pre-installed
- Non-technical friendly guide/docs (click&go, no terminal, no typed
commands, let them decide when they are ready/want to use the
don't scare them to early!)
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-
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
I suppose that would be the right place to put "getting started"
for each distribution.
would be the place to put the reference
for the Q&A
I hope you find my thoughts helpful.
-----BEGIN PGP SIGNATURE-----
-----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