locally storing issues/comments/projects

locally storing issues/comments/projects

[Sahil Gautam]

hi

i was previously on github but recently moved to gitea  as i want to be 
sure that things won't change over night because some big company thinks 
so, things like addition of an annoying chatbot button everywhere. i now 
feel that the things like issues/projects/comments should be stored in 
separate private branches in git so that one doesn't have to depend on 
the hosting service providers.

i asked it to the gitea devs 
https://github.com/go-gitea/gitea/issues/34993#issuecomment-3048363965 
and they said that most of these operations are database-based. I 
thought what if git supports it inherently, so i write this mail :)

sahil gautam

Re: locally storing issues/comments/projects

[Junio C Hamano]

Sahil Gautam <printfdebugging@gmail.com> writes:

> thought what if git supports it inherently, so i write this mail :)

As far as I know, no.

Your worry about these hosting providers taking the non-commit
project metainformation, like reviews and issues, hostage to prevent
their users from defecting may be real.  It would be very nice if
these hosting providers can agree to make project metainformations
interchangeable in an open way.  It would allow not just migration
between hosing providers, but may even allow federated operation to
be implemented.  You push your work to one site, somebody on another
site comment on your commits elsewhere, etc.

Re: locally storing issues/comments/projects

[Sahil Gautam]

On 7/9/25 3:01 AM, Junio C Hamano wrote:
> It would be very nice if these hosting providers can agree to make
> project metainformations interchangeable in an open way.

it's not just about migrations, it's about a repository being self 
reliant in itself. think of some git
hosting provider blocking my account because of some ai algorithm, think 
of some disaster striking
some data center or some malware deleting all the data on the servers, 
all these are quite possible.

having git store that data means that you clone the whole thing and 
doesn't matter what happens
to the hosting provider, if you have the repository, you have the whole 
thing.

Re: locally storing issues/comments/projects

[Eli Schwartz]

[-- Attachment #1.1: Type: text/plain, Size: 825 bytes --]

On 7/8/25 8:21 PM, Sahil Gautam wrote:
> 
> On 7/9/25 3:01 AM, Junio C Hamano wrote:
>> It would be very nice if these hosting providers can agree to make
>> project metainformations interchangeable in an open way.
> 
> it's not just about migrations, it's about a repository being self
> reliant in itself. think of some git
> hosting provider blocking my account because of some ai algorithm, think
> of some disaster striking
> some data center or some malware deleting all the data on the servers,
> all these are quite possible.
> 
> having git store that data means that you clone the whole thing and
> doesn't matter what happens
> to the hosting provider, if you have the repository, you have the whole
> thing.


You may be interested in https://github.com/git-bug/git-bug


-- 
Eli Schwartz

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

Re: locally storing issues/comments/projects

[Sahil Gautam]

On 7/9/25 6:11 AM, Eli Schwartz wrote:
> On 7/8/25 8:21 PM, Sahil Gautam wrote:
>> On 7/9/25 3:01 AM, Junio C Hamano wrote:
>>> It would be very nice if these hosting providers can agree to make
>>> project metainformations interchangeable in an open way.
>> it's not just about migrations, it's about a repository being self
>> reliant in itself. think of some git
>> hosting provider blocking my account because of some ai algorithm, think
>> of some disaster striking
>> some data center or some malware deleting all the data on the servers,
>> all these are quite possible.
>>
>> having git store that data means that you clone the whole thing and
>> doesn't matter what happens
>> to the hosting provider, if you have the repository, you have the whole
>> thing.
>
> You may be interested in https://github.com/git-bug/git-bug
>
thanks Eli,

i will look into git-bug try it out and see if it
does the job. i think like docker-compose, any other feature requests such
as this one have to first prove their worth in the wild, and since your 
suggestion
gave me a hint that they can exist separately, i will take that route.