Inconsistent naming on NetworkManager packages
Open
Nobody has claimed this yet.
Packaging Problem
- Dominant language
- Python
- Stars
- 141
- Forks
- 146
- Avg merge
- 11h 7m
- Merged PRs (30d)
- 407
Description
We are kinda inconsistent at naming NetworkManager packages. Most of them use networkmanager-.. and others network-manager-... The one that use network-manager are:
network-managernetwork-manager-fortissvpnnetwork-manager-applet=> This one correctly use its upstream name
Contributor guide
No contributing guide indexed for this repository
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
Locate the package definitions for network-manager, network-manager-fortissvpn, and network-manager-applet, then compare their names with the other NetworkManager packages. Confirm the intended naming convention from the repository’s existing package layout; done means the affected names follow an agreed convention without changing the upstream name of network-manager-applet.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100