Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide advisory on naming of custom features to avoid possible conflicts #9557

Open
alimirjamali opened this issue Nov 3, 2024 · 0 comments · May be fixed by QubesOS/qubes-core-admin-client#316
Open

Provide advisory on naming of custom features to avoid possible conflicts #9557

alimirjamali opened this issue Nov 3, 2024 · 0 comments · May be fixed by QubesOS/qubes-core-admin-client#316
Assignees
@alimirjamali
Labels
C: core P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@alimirjamali
Copy link

alimirjamali commented Nov 3, 2024 •
edited
Loading

How to file a helpful issue

The problem you're addressing (if any)

If user sets a feature for their local personal program (or whatever reason), it might be allocated by Qubes OS project in the future and break something. Just like how it is mentioned in #7730

The solution you'd like

  1. Allocate some prefixes (e.g. user-, custom- or dev-) for user custom features workflow. Never use them it in future developments. Document this.
    Optional:
  2. Have a database of all known features. If user tries to set an unknown feature without the above prefixes, warn them that it might conflict with future features and they would better prepend the custom prefixes.

The value to a user, and who that user might be

Advanced users and 3rd party developers who might need custom features.

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)
@alimirjamali alimirjamali added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. labels Nov 3, 2024
alimirjamali added a commit to alimirjamali/qubes-core-admin-client that referenced this issue Nov 3, 2024
@alimirjamali
Dedicate user-, custom- & dev- prefixes
57cba2c 
Allocating `user-*`, `custom-*` and `dev-*` feature prefixes to end
users.

resolves: QubesOS/qubes-issues#9557
@alimirjamali alimirjamali linked a pull request Nov 3, 2024 that will close this issue
Open
@andrewdavidwong andrewdavidwong added the pr submitted A pull request has been submitted for this issue. label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alimirjamali alimirjamali

Labels
C: core P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Dedicate user-, custom- & dev- prefixes alimirjamali/qubes-core-admin-client
2 participants
@alimirjamali @andrewdavidwong