dimensionalOS / dimensionalOS/dimos
Figure out where dimos stores state
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
We probably need a directory for storing state at this point. For example, spatial memory uses assets/output/> memory/. For most other stuff we use ~/.local/state/dimos. But maybe we need a local directory we can dump > all sorts of stuff? That way you wouldn't have to specifically ignore this in .gitignore.
https://github.com/dimensionalOS/dimos/pull/1769#discussion_r3135460100
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 linked pull request discussion, then inspect the uses of assets/output/memory/ and ~/.local/state/dimos mentioned in the issue. Determine whether the project needs one shared local state directory and how it should relate to .gitignore. Done means the storage convention and its scope are clearly decided and recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100