YunoHost/doc
1
0
Fork 0
mirror of https://github.com/YunoHost/doc.git synced 2024-09-03 20:06:26 +02:00
Code Issues Projects Releases Packages Wiki Activity

Typos

Browse source 
Co-authored-by: tituspijean <titus+yunohost@pijean.ovh>
This commit is contained in:
Alexandre Aubin 2023-09-04 17:55:53 +02:00 committed by GitHub
parent eaa531784c
commit 23768116cb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
pages/05.community/20.faq/faq.md
View file

@ -122,8 +122,8 @@ If you really want to have a feature implemented or documented, or an app packag
### Why won't you include [feature X] ? ### Why won't you include [feature X] ?
YunoHost is primarily designed for not-so-tech-savvy users and aims to remain relatively simple in terms of UI/UX. At the same time, the project has limited time and energy available to be maintained and developed. Therefore we may lower the priority of features, or refuse entirely the inclusion of features, based on the criteria that they: YunoHost is primarily designed for not-so-tech-savvy users and aims to remain relatively simple in terms of UI/UX. At the same time, the project has limited time and energy available to be maintained and developed. Therefore we may lower the priority of features, or refuse entirely the inclusion of features, based on the criteria that they:
- would only meaningful for advanced / power-users stuff which is out of the scope of the project ; - would only be meaningful for advanced / power-users stuff which is out of the scope of the project ;
- would introduce too much UI/UX bloat ; - would introduce too much UI/UX bloat ;
- would only cover unrealistic thread models ; - would only cover unrealistic threat models ;
- would be there only to satisfy purists ; - would be there only to satisfy purists ;
- or overall would not be worth it in terms of development/maintenance time/energy for what it brings to the project. - or overall would not be worth it in terms of development/maintenance time/energy for what it brings to the project.