public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tim FitzGeorge <ipfr@tfitzgeorge.me.uk>
To: development@lists.ipfire.org
Subject: Re: [PATCH 0/3] Help for GUI
Date: Mon, 18 May 2020 21:18:05 +0100	[thread overview]
Message-ID: <235d452b-478f-331a-78d4-8b1bdad18ddd@tfitzgeorge.me.uk> (raw)
In-Reply-To: <6390F8AE-998D-489E-A983-1A875E2761F2@ipfire.org>

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

Hi Michael,

On 16/05/2020 10:35, Michael Tremer wrote:
> Hi Tim,
>
> Thank you very much for submitting these patches.
>
> I am afraid that I must say that I oppose these changes.
>
> This has recently been discussed on the community portal and although
I still have not made my mind up entirely, I think this not helpful to
anyone:
>
> * We do not have documentation for everything for a start

Actually, it's not too bad.  The only menu items (out of 72) in the core
that I couldn't find help for are:

Status / VPN: Net-to-Net Statistics
Firewall / Firewall Groups
Firewall / Blue Access
Firewall / OpenVPN Roadwarrior connections log

Status / Qos Graphs			*
Status / Modem Status
Status / Atm-status
Network / Network configuration		*
Firewall / UPnP
IPFire / Help				*
Log / Open VPN Log			*

and at least four of those (*) don't appear to exist.  There might well
be pages for some of these which I didn't see when I was adding the links.
There are also four pages which obviously require further work:

Status / Entropy
Status / Connections
Status / MDstat
Network / URL Filter

> * There is never this “just read one sentence and you suddenly will be
an expert” thing this kind of promotes
>
True.  But in the extreme this could be argued to say that IPFire
shouldn't provide any information in the wiki unless it's much more
detailed than the current wiki.  Where do you draw the line?


> Should we not rather link the wiki somewhere in the footer and
encourage people to start reading the whole thing from the start before
they do something?

I think the best place for this is either on the download page or in the
installer, so they get prompted to read the wiki before they start playing.

I suspect putting a link in the footer wouldn't help many people.  If
they can't find the wiki on the website they're probably not going to
find it in the GUI footer.

>
> What is your rationale to implementing this?

I was following the discussion in the community, and several people
seemed to be in favour of the idea. And to quote 'This suggestion has
been made plenty of times. I would be happy to accept patches, but so
far nobody wanted to work on it.'

So I submitted the patches.

I understand that there are two sides to the argument.  Having the wiki
pages linked as help will be beneficial to some people and will just get
other people into a mess quicker when they try to do something they
don't understand - but having a link to the wiki page may help some of
this latter group to realise that they don't understand and need to
learn more.

Which is going to be of most benefit to most people?  I think for me,
having the help links would be preferable, but that's for me, with my
skill set and personality.

Tim

>
> Best,
> -Michael
>


  reply	other threads:[~2020-05-18 20:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 21:39 Tim FitzGeorge
2020-05-15 21:39 ` [PATCH 1/3] Help for GUI - ipfire theme code Tim FitzGeorge
2020-05-15 21:39 ` [PATCH 2/3] Help for GUI - Help links Tim FitzGeorge
2020-05-15 21:39 ` [PATCH 3/3] Help for GUI - help link style Tim FitzGeorge
2020-05-16  9:35 ` [PATCH 0/3] Help for GUI Michael Tremer
2020-05-18 20:18   ` Tim FitzGeorge [this message]
2020-05-22 13:07     ` Michael Tremer
     [not found] <mailman.1.1589630401.3663.development@lists.ipfire.org>
2020-05-16 16:10 ` Jon Murphy
     [not found] <F683B9F1-464A-44C5-9E5B-13F91CAEE77F@gmail.com>
2020-05-19 20:45 ` Tim FitzGeorge
     [not found] <04413F0C-96CD-4213-AC55-8012E649FB64@gmail.com>
2020-05-21 18:51 ` Jonatan Schlag
2020-05-22 13:19   ` Michael Tremer
     [not found] <851be8bf-9193-3c8a-1802-94a54b70909f@tfitzgeorge.me.uk>
2020-05-22 13:22 ` Michael Tremer
     [not found] <mailman.125.1590157028.797.development@lists.ipfire.org>
2020-06-10  0:05 ` Jon Murphy

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=235d452b-478f-331a-78d4-8b1bdad18ddd@tfitzgeorge.me.uk \
    --to=ipfr@tfitzgeorge.me.uk \
    --cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox