unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Quiliro <quiliro@riseup.net>, guix-devel@gnu.org
Subject: Manual (was: fully functional desktop installation)
Date: Mon, 15 Jan 2018 15:18:19 +0000	[thread overview]
Message-ID: <20180115151819.ez3uyqykip4xp4y4@abyayala> (raw)
In-Reply-To: <87shotx3eq.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2918 bytes --]

Ludovic Courtès transcribed 1.7K bytes:
> Hi Quiliro!
> 
> Quiliro <quiliro@riseup.net> skribis:
> 
> > On Mon, 02 Jan 2017 22:11:01 +0100
> > ludo@gnu.org (Ludovic Courtès) wrote:
> 
> [...]
> 
> >> The desktop example contains all of GNOME, when choosing GNOME, which
> >> provides an email client, Web browser, and lots of other things.
> >
> > I don't find the email client.
> > The web browser will not reproduce videos.
> 
> This is a bug that needs to be treated separately.  Clearly Nautilus
> should be able to play videos.

I can confirm this for some file, I just had the opinion Nautilus wasn't
very capable and didn't report it when I first noticed it.

> > I have no idea how to chat in Gnome. (Of course I will investigate.)
> 
> There’s Pidgin, but maybe it’s not really part of GNOME.
> 
> > What you say makes sense. But what users that cannot learn to install
> > need to work on their own matters is very important in order for them to
> > be able to advocate the free system. Perhaps we do not want to promote
> > the use of Flash or Microsoft Office formats. These issues are
> > critical. But they are not against the FSDGs. And the user must notice
> > we are able to offer those capabilities. We must always insist in
> > suggesting to use the libre alternatives. In this case, we should not
> > avoid including the ability to read those formats.
> 
> I agree, but again, I think GNOME provides everything for these tasks.
> Also, at this point, the target audience of GuixSD is not “users that
> cannot learn to install”—if someone managed to install GuixSD, surely
> they’ll find out how to install LibreOffice.

In my opinion we could extend examples in the Manual.
We already expect people to read the Manual, even if it's hard to
digest for newcomers in some passages (different problem). To add
an 'from 0 to full Desktop' walk through or just extension of the existing
material with references to the appropriate sections would be good.

Even if we don't expect people who are not willing to play around, break parts
and play around with the system, we need clear examples. Even people who are
experienced want some kind of help instead of high expertise expectation.

People keep asking me obvious question that should be in the manual.
Sometimes things which could be snippets in an example chapter.
For example (home-directory (string-append "/home/" name)). Super obvious,
I know.

> > I have also had problems with Mimetypes. Many files will not open
> > because the Gnome will not identify which program is appropriate.
> 
> Sounds like a bug.  Could you report all the details to
> bug-guix@gnu.org: how to reproduce, what you expected, and what you got?
> 
> Thank you!
> 
> Ludo’.
> 
> 
> 
> 

-- 
ng0 :: https://ea.n0.is
A88C8ADD129828D7EAC02E52E22F9BBFEE348588 :: https://ea.n0.is/keys/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

       reply	other threads:[~2018-01-15 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161229171045.263747a9@riseup.net>
     [not found] ` <87bmvpb21m.fsf@gnu.org>
     [not found]   ` <20170108041145.6d9a5cbc@riseup.net>
     [not found]     ` <87shotx3eq.fsf@gnu.org>
2018-01-15 15:18       ` ng0 [this message]
2018-01-15 15:35         ` Manual (was: fully functional desktop installation) Amirouche Boubekki
2018-01-15 16:52           ` ng0

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=20180115151819.ez3uyqykip4xp4y4@abyayala \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=quiliro@riseup.net \
    /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).