Review and reorganize details on Installing Spotify guide #493

Merged
ryanlerch merged 1 commit from update-spotify-installation-guide into master 2022-10-17 20:45:31 +00:00
Contributor

Motivation

As discussed in #491, the Spotify guide is missing the details about how lpf works and that is not so user-friendly.

Proposed solution

We've decided to present:

  • Move Flatpak option first
  • Add Snap option
  • Move lpf option last

Screenshot

(is there any guideline on uploading images for Pull Requests?)

## Motivation As discussed in [#491](https://pagure.io/fedora-docs/quick-docs/issue/491), the Spotify guide is missing the details about how `lpf` works and that is not so user-friendly. ## Proposed solution We've decided to present: - Move `Flatpak` option first - Add `Snap` option - Move `lpf` option last ## Screenshot - [Preview image in ImgBB](https://ibb.co/QrV5Zcz) (is there any guideline on uploading images for Pull Requests?)
Author
Contributor

1 new commit added

  • Add snapcraft to References on installing Spotify
**1 new commit added** * ``Add snapcraft to References on installing Spotify``
Contributor

Uh---is this really required to get snap working?

Uh---is this really required to get snap working?
Contributor

is sudo required? I thought the advantage of using snap, like flatpak, would be that users could just install whatever without needing sudo and system wide admin privileges?

is `sudo` required? I thought the advantage of using snap, like flatpak, would be that users could just install whatever without needing sudo and system wide admin privileges?
Contributor

Do we need to tell users how to add pkg-build to their user etc.? If this is on the github link, it'll be good to say "please refer to the github .. for information" perhaps?

Do we need to tell users how to add `pkg-build` to their user etc.? If this is on the github link, it'll be good to say "please refer to the github .. for information" perhaps?
Contributor

Thanks very much for this @wevtimoteo . Looks very good. I've left a few comments.

Thanks very much for this @wevtimoteo . Looks very good. I've left a few comments.
Contributor

Metadata Update from @ankursinha:

  • Request assigned
**Metadata Update from @ankursinha**: - Request assigned
Contributor

Metadata Update from @ankursinha:

  • Pull-request tagged with: improvement, needs changes, needs committer review
**Metadata Update from @ankursinha**: - Pull-request tagged with: improvement, needs changes, needs committer review
Author
Contributor

2 new commits added

  • Add Spotify installation page to the references section
  • Remove `sudo` from snap installation
**2 new commits added** * ``Add Spotify installation page to the references section`` * ``Remove `sudo` from snap installation``
Author
Contributor

1 new commit added

  • Remove details about `lpf` setup
**1 new commit added** * ``Remove details about `lpf` setup``
Author
Contributor

Uh---is this really required to get snap working?

@ankursinha Yes, this is the recommendation extracted from Snapcraft page

is sudo required? I thought the advantage of using snap, like flatpak, would be that users could just install whatever without needing sudo and system wide admin privileges?

Some packages require sudo on installing, I've checked Spotify installation page and it recommends installation without sudo, done in 40daf31 and f9d13a8.

Do we need to tell users how to add pkg-build to their user etc.? If this is on the github link, it'll be good to say "please refer to the github .. for information" perhaps?

Agreed! Done in e1cb92e.


@ankursinha could you review it again? Thanks for your comments!

> Uh---is this really required to get snap working? @ankursinha Yes, this is the recommendation extracted from [Snapcraft](https://snapcraft.io/spotify) page > is `sudo` required? I thought the advantage of using snap, like flatpak, would be that users could just install whatever without needing sudo and system wide admin privileges? Some packages require `sudo` on installing, I've checked [Spotify installation page](https://www.spotify.com/us/download/linux/) and it recommends installation without `sudo`, done in 40daf31 and f9d13a8. > Do we need to tell users how to add `pkg-build` to their user etc.? If this is on the github link, it'll be good to say "please refer to the github .. for information" perhaps? Agreed! Done in e1cb92e. --- @ankursinha could you review it again? Thanks for your comments!
Contributor

lgtm, merging. Thanks very much @wevtimoteo .

I'll also add you to the quick-docs-committers group. You should be able to work with tickets etc. and review other PRs to merge them and so on.

lgtm, merging. Thanks very much @wevtimoteo . I'll also add you to the quick-docs-committers group. You should be able to work with tickets etc. and review other PRs to merge them and so on.
Contributor

Pull-Request has been merged by ankursinha

Pull-Request has been merged by ankursinha
First-time contributor

That was fast, I think it's a great improvement.

I think that a general guide about choosing between different installation methodologies would also be useful to help people getting started. For myself I was keeping track a bit and by now I have installed software through:

dnf with its default repo's
RPM fusion
installed some downloaded RPM files
Flatpaks from flathub
Appimage

On the other hand maybe this is something people need to find out for themselves?

That was fast, I think it's a great improvement. I think that a general guide about choosing between different installation methodologies would also be useful to help people getting started. For myself I was keeping track a bit and by now I have installed software through: dnf with its default repo's RPM fusion installed some downloaded RPM files Flatpaks from flathub Appimage On the other hand maybe this is something people need to find out for themselves?
Author
Contributor

lgtm, merging. Thanks very much @wevtimoteo .

I'll also add you to the quick-docs-committers group. You should be able to work with tickets etc. and review other PRs to merge them and so on.

Thanks @ankursinha! Will do my best.

That was fast, I think it's a great improvement.

I think that a general guide about choosing between different installation methodologies would also be useful to help people getting started. For myself I was keeping track a bit and by now I have installed software through:

dnf with its default repo's
RPM fusion
installed some downloaded RPM files
Flatpaks from flathub
Appimage

On the other hand maybe this is something people need to find out for themselves?

Thanks for your considerations @dapperplant. I think this would cover "software alternatives methods on installing Third-party software". Maybe would be a new entry in the docs, then we can just refer to them when guiding people on getting these apps installed (maybe we should open a new issue to discuss it and gather more opinions).

> lgtm, merging. Thanks very much @wevtimoteo . > > I'll also add you to the quick-docs-committers group. You should be able to work with tickets etc. and review other PRs to merge them and so on. Thanks @ankursinha! Will do my best. > That was fast, I think it's a great improvement. > > I think that a general guide about choosing between different installation methodologies would also be useful to help people getting started. For myself I was keeping track a bit and by now I have installed software through: > > dnf with its default repo's > RPM fusion > installed some downloaded RPM files > Flatpaks from flathub > Appimage > > > On the other hand maybe this is something people need to find out for themselves? > > Thanks for your considerations @dapperplant. I think this would cover "software alternatives methods on installing Third-party software". Maybe would be a new entry in the docs, then we can just refer to them when guiding people on getting these apps installed (maybe we should open a new issue to discuss it and gather more opinions).
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Docs/quick-docs#493
No description provided.