Hello community, I’d like to get a feedback of what you think:
With V1.0 I’d enjoy to have an /e/ introduction manual for new users: A comprehensive and compact document that is printable (PDF) and written in an accessible language (length 5-10 pages).
I am aware that there’s an online manual/wifi in preparation. But I do not see this as a concurrence product rather as a kind of (additional) starter document for less tech-affine future /e/ users.
The document should include (what I have in mind for now):
What is /e/ / Who’s behind / What does it mean Android without Google / Intro to data security privacy in the Internet
Guidance through the initial installation process (including how to get an e-email address)
Very brief explanation of the system and its different preinstalled apps with a special focus on the ones that are particular for /e/ - such as Trust
Explanation of the security features of /e/ as well as the webbased side of /e/.
Explanation of things to keep in mind when using /e/
– Traffic with /e/ services - if you are on a data connection this implies that photos are uploaded
– Naming folders that are synced with the /e/ services and how to switch off specific ones.
– How to (re)connect a device with /e/ services when it is not done in the initial setup process
Further references to the /e/ wiki (direct reference links to specific topics) to user forum and other sources for getting support (in what languages).
A summary that explains
– …especially what /e/ provides and what it doesn’t (/e/ is not and cannot be a fully secure tool for phone and internet use).
If this document is becoming a first reference document for new users, it can contain other stuff that is of particular importance for the /e/ team…
This manual could serve for instance as a perfect self-advertisement for /e/ - as a honest and transparent product. Furthermore it could be a great place to stress how /e/ is financed and that (satisfied) users are invited to support/donate (ideally on a regular basis) or to buy a subscription.
It could be a good place as well to underline the community driven aspect of /e/ and that respectful communication is key. The latter point is something I really enjoy in all interactions with the community so far but it will probably take some efforts to maintain that once /e/ will go public.
Hi, for 25 years I have implemented software for a big player and I have learned one thing: Noone is looking into a documentation if there is someone who could asked. So I think your request is not really needed or better, it will not used.
We do have a lot of wikis here in forum, but most people are asking in the telegram group for help.
But if you want write a new documentation, go head
Maybe. That’s why I talked about a different format, for instance a video or multiple videos that would explain what an OS is, what a fork is, why /e/ is important, how GAFAM spy on us, what do they know about us, how install /e/ fir each brand, an explanation of all settings in /e/, etc etc. It can’t be useless or a bad idea.
I thought about doing it myself but I don’t have all the skills required for this. I’m better with text than video. Still thinking about that for a few weeks though.
Nooooo, pls don’t make video’s. Are we unable to read ?? Video tutorials are the biggest shit I ever have seen. To follow a video tutorial you must have 4 eyes, 2 for the video and 2 for that what your fingers should do. And if you are stuck somewhere, you have only a bad chance to find the section where you get lost. In written tutorials, you can really step by step and if something was wrong you can easy scroll back to the section where you have to start over
Are we unable to listen and watch ? A video is less complicated than a big text for new users when it’s not made by a 12 years old child . And let’s people choose between text or video anyway, in order to make a video a text in needed so there is no problem, both would be available.
And explaining why /e/ is important doesn’t require a text, video is much better when it’s not a tutorial. (But of course both would be available)
It will take weeks/months to have an almost complete “Support” page or detailed documentation about /e/ and the open-source universe. And for now nothing is done so we have the time before thinking about videos anyway
Hi, for more than 25 years I’ve seen as support tech users lost in front of a computer because they had in their hands a complex system delivered without any kind of information except “press the power button to turn the computer on” or inside a readme file “open wordpad to read this document” !!! ??? @@
So a minimum of information is always needed and as someone said “When everything goes wrong read the fuc… manual”.
An example can you tell me where are located in /e/ the settings allowing me to choose what is synced on e.drive. It’s not obvious. [Settings/accounts/manage/settings…]
So a map or tree of the system settings with a short explanation would a valuable feature.
Yes I’m doing it. I should have finished the French version in 2 weeks. The English version should come in 3 weeks. For other languages, I will see with the rest of the translation team but we will see that later. The link in order to download the “Support” folder will be given on the forum.
Great suggestion @ralxx!
/e/ definitely needs to provide information about the OS that people will be using: the overall purpose, the OS itself, the launcher, the settings, the apps, how to use them and their settings; the services, how to use them and their settings… Etc.
It’s a lot to cover, but it needs to be done. I think that both text and videos are needed. Videos don’t need as much translation, they are more accessible (generally) and community members can easily make and share them. Docs can be more detailed, more comprehensive and importantly people can read them offline, when they’re trying to work out why they can’t get any internet access!
It also would be nice a summary that explains some of the icons in the status bar next to the time and battery indicator and a few other icons that are unfamiliar.
It’s been three years for this manual, what is it’s status?