nextcloud / nextcloud/talk-desktop
snap as a secondary distribution method
Open
Nobody has claimed this yet.
distribution 📦
- Dominant language
- JavaScript
- Stars
- 525
- Forks
- 85
- Avg merge
- 8h 5m
- Merged PRs (30d)
- 35
Description
Auto-update and adding checksums are moved to separate issues. Closing for now.
Additional distribution might be discussed in separate issues.
Originally posted by @ShGKme in #257
as per the above comment, this is a tracking issue for talk-desktop as a snap.
a few reasons for my preference of snaps are:
- install and forget: snap are auto updated
- potential for a talk client on my preferred mobile linux distro (Ubuntu Touch)
- mulitple update channels, which allow for testing pre-releases before pushing it for all users
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named in the issue. Start by reviewing the Electron packaging and current release configuration, then determine the Snap metadata and channel requirements. Done should mean that the desktop client can be distributed as a Snap with the intended update-channel behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript
- Domain
- desktop, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100