From: Dan Partelly <dan_partelly@rdsor.ro>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Improving the README and new user experience
Date: Wed, 20 Jun 2018 12:39:25 +0300 [thread overview]
Message-ID: <C59F7EC5-A7A7-4A35-BA57-CE3BACDD3F13@rdsor.ro> (raw)
In-Reply-To: <87lgb9exex.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2447 bytes --]
It is my oppinion that first you should very clearly define what you want from GuixSD
a) is GuixSD to be a system which sees wide adoption , or is a system by developers for developers.
b) What kind of users ? Industrial use or amateurs at home ?
c) Server space, desktop space or both ?
d) if server space, actively think at security and to the stability of the OS. Identify potential security risks of running the custom kernel you have. Document it. Be open about it . Think at the implications of running a conservative garbage collector in several system demons. Uptime should be measured in year(s). See if it is a problem or not.Measure it . Document it.
e) GuixSD is decent OS and follows NIX on the path of innovation . It would be a pitty to remain a niche used by a very small group of ppl . Do not focus just on the fact that the system is transactional, atomic and so on. Make it rock stable.
> I'm not quite sure yet how to improve the experience to new users.
1. Once you know this there is a lot you can do. Scheme is a good configuration language, but if you lack info on all the basics administration tasks and the semantics of the DSL the user is screwed. Documenting it is a must, for all common adminsitrative tasks
2. Make sure you use sound development practices, do not inflict the users upon the bleeding edge of your repository. I cannot stress enough how important this is, regardless of what you shoose to be the market of your product.
3. Treat it as a product, not as a hacking playground. I know it is not funny, but my guess is that it will help with adoption
4. Once you reach 1.0 , stop. Reflect on the bugs you have, and what documentation you lack. Make bug solving a priority for several point releases over new features. Or do both if you have sufficient manpower.
e) AIX Smitty is a great rpogram for configuring the system. It generates scripts, which the admin can execute and bring the OS in the desired state. You can generate Scheme from a similar system configuration tool, indicate the user it should review it, then
execute system recofniguration with guix command.
> On Jun 20, 2018, at 10:20, Pierre Neidhardt <ambrevar@gmail.com <mailto:ambrevar@gmail.com>> wrote:
>
> I'm not quite sure yet how to improve the experience to new users. I'd
> need to install it several times, with other people and for different
> scenarios before I can be a better judge.
[-- Attachment #2: Type: text/html, Size: 5684 bytes --]
next prev parent reply other threads:[~2018-06-20 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 4:46 Improving the README and new user experience swedebugia
2018-06-20 6:13 ` Dan Partelly
2018-06-20 7:20 ` Pierre Neidhardt
2018-06-20 9:39 ` Dan Partelly [this message]
2018-06-24 14:02 ` Dan Partelly
2018-06-20 8:24 ` Danny Milosavljevic
2018-06-20 9:57 ` swedebugia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C59F7EC5-A7A7-4A35-BA57-CE3BACDD3F13@rdsor.ro \
--to=dan_partelly@rdsor.ro \
--cc=ambrevar@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).