linux-credentials / linux-credentials/credentialsd
Define a D-Bus API with Portal conventions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 259
- Forks
- 19
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 12
Description
XDG Portals have their own conventions, for example, they avoid using signals for long-running async processes.
I think that the portal implementation should be separate from the credential service D-Bus API itself, so we should basically create a new API that maps to calls on the credential service. (For one reason, this moves a lot of the complexity out of the main xdg-desktop-portal implementation, and allows using other languages like Rust without having to touch that repo's build system.)
Review the [Portal Common Conventions](https://flatpak.github.io/xdg-desktop-portal/docs/common-conventions.html) for more guidance.
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
Start by reading the XDG Portal Common Conventions linked in the issue, then compare them with the existing credential service D-Bus API. Define the separate portal-facing API and document how its calls map to the credential service, including the required asynchronous-operation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100