documentation-packages team mailing list archive
Mailing list archive
[Bug 1658785] Re: Snap documentation in 17.04?
Hi Gunnar, I'm proposing to make minor changes to the following pages:
As regards installing and removing applications I'm proposing to say
that there are two package formats: Debian packages and snap packages.
In order to install or remove an application available as a snap package
the user has to log on to Ubuntu One. Snap packages have advantages over
Debian packages (I'm not planning to say what they are) so it's
recommended that where there's a choice of format the user installs the
snap package, which should be the first of the two applications listed.
The change to disk-partitions.html will be three or four words only. I'm
not planning to say what loop devices are. It's not relevant to that
What do you think of this proposal?
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
Snap documentation in 17.04?
Status in ubuntu-docs package in Ubuntu:
Do we say anything about snaps in the 17.04 desktop help and if so
what do we say? If snaps are experimental and subject to change then
perhaps we should say nothing? Below I give some points about snaps
worth thinking about (as regards how we document them):
The logon to Ubuntu One in Ubuntu Software when one tries to install a
snap will surely create confusion. I saw one example on the #ubuntu
channel where people were confused by it (with good reason in my
opinion). At present you don't have to logon to Ubuntu One if you
install a snap from the command line. Why are Ubuntu Software and the
command line treated differently in this respect?
I don't know much about snaps but in the manual for the snap command
there are options to buy a snap and log on to the snap store. I would
imagine that at present there are no snaps that one has to pay for -
but there will be soon?
Snaps are visible in the Disks application as "devices". This is very
confusing in my opinion.
To manage notifications about this bug go to: