Write Documents for ipc
Open
Nobody has claimed this yet.
easy
good first issue
help wanted
PRs-welcome
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 237
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 1
Description
So far, the ipc system inside Wayfire has developed a lot. It is getting more and more necessary to write a document for the ipc system.
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
The issue does not name any files, tests, or entry points. First map Wayfire’s existing IPC implementation and behavior, then document the system’s purpose, interfaces, and usage based on that code. Done means the IPC system has a usable document covering the parts that have already developed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100