[Feature] Support P2P data storage

Open
#135 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
git
Domain
databases, distributed-systems

Research direction

Start by reading the linked git-bug storage model and examining how gitly currently stores issues in a database. Define the repository format, synchronization behavior, and migration or alternative-storage scope before implementation. Done would require a decided design and clear acceptance criteria for self-contained issue data.

Written by the indexing model from the issue text.

Description

With that I mean, supporting things like the git-bug issue storage format, which stores issues inside the git repo, instead (or at least alternative to) storing them in a database.
The general idea is, to have projects entirely self-contained within their repo, and thus be truly independent of the platform they are hosted on. In reality today, this is only true for the source code. the whole rest - roughtly "the community" part - is not distributed. This would be a killer feature!

Dominant language
V
Stars
1.5k
Forks
79
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vlang/gitly

All issues in vlang/gitly

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.