{"thread":{"id":"63759","subject":"locally storing issues/comments/projects","startedAt":"2025-07-08T10:52:29Z","lastAt":"2025-07-09T01:00:08Z","messageCount":5,"participants":["Sahil Gautam","Junio C Hamano","Eli Schwartz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"521527","messageId":"3e964e0d-bb90-4074-a9ae-a10fb02b3f50@gmail.com","threadId":"63759","inReplyTo":null,"subject":"locally storing issues/comments/projects","fromName":"Sahil Gautam","fromEmail":"printfdebugging@gmail.com","sentAt":"2025-07-08T10:52:23Z","receivedAt":"2025-07-08T10:52:29Z","isPatch":false,"sender":{"key":"printfdebugging@gmail.com","avatar":"https://gravatar.com/avatar/b8432de9157687e76277bd6785da244201ea1f9f774b3f4727eb07ffc373a751?d=mp&s=160"},"body":"hi\n\ni was previously on github but recently moved to gitea  as i want to be \nsure that things won't change over night because some big company thinks \nso, things like addition of an annoying chatbot button everywhere. i now \nfeel that the things like issues/projects/comments should be stored in \nseparate private branches in git so that one doesn't have to depend on \nthe hosting service providers.\n\ni asked it to the gitea devs \nhttps://github.com/go-gitea/gitea/issues/34993#issuecomment-3048363965 \nand they said that most of these operations are database-based. I \nthought what if git supports it inherently, so i write this mail :)\n\nsahil gautam\n\n"},{"id":"521576","messageId":"xmqq4ivmtlnf.fsf@gitster.g","threadId":"63759","inReplyTo":"3e964e0d-bb90-4074-a9ae-a10fb02b3f50@gmail.com","subject":"Re: locally storing issues/comments/projects","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-08T21:31:16Z","receivedAt":"2025-07-08T21:31:18Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Sahil Gautam <printfdebugging@gmail.com> writes:\n\n> thought what if git supports it inherently, so i write this mail :)\n\nAs far as I know, no.\n\nYour worry about these hosting providers taking the non-commit\nproject metainformation, like reviews and issues, hostage to prevent\ntheir users from defecting may be real.  It would be very nice if\nthese hosting providers can agree to make project metainformations\ninterchangeable in an open way.  It would allow not just migration\nbetween hosing providers, but may even allow federated operation to\nbe implemented.  You push your work to one site, somebody on another\nsite comment on your commits elsewhere, etc.\n\n"},{"id":"521598","messageId":"3a8590f3-ab8d-4155-b8c1-7cd34dc9db00@gmail.com","threadId":"63759","inReplyTo":"xmqq4ivmtlnf.fsf@gitster.g","subject":"Re: locally storing issues/comments/projects","fromName":"Sahil Gautam","fromEmail":"printfdebugging@gmail.com","sentAt":"2025-07-09T00:21:59Z","receivedAt":"2025-07-09T00:22:04Z","isPatch":false,"sender":{"key":"printfdebugging@gmail.com","avatar":"https://gravatar.com/avatar/b8432de9157687e76277bd6785da244201ea1f9f774b3f4727eb07ffc373a751?d=mp&s=160"},"body":"\nOn 7/9/25 3:01 AM, Junio C Hamano wrote:\n> It would be very nice if these hosting providers can agree to make\n> project metainformations interchangeable in an open way.\n\nit's not just about migrations, it's about a repository being self \nreliant in itself. think of some git\nhosting provider blocking my account because of some ai algorithm, think \nof some disaster striking\nsome data center or some malware deleting all the data on the servers, \nall these are quite possible.\n\nhaving git store that data means that you clone the whole thing and \ndoesn't matter what happens\nto the hosting provider, if you have the repository, you have the whole \nthing.\n\n"},{"id":"521599","messageId":"c629f3a6-4749-4ac0-8fbb-fd1fb9db1d0a@gentoo.org","threadId":"63759","inReplyTo":"3a8590f3-ab8d-4155-b8c1-7cd34dc9db00@gmail.com","subject":"Re: locally storing issues/comments/projects","fromName":"Eli Schwartz","fromEmail":"eschwartz@gentoo.org","sentAt":"2025-07-09T00:41:13Z","receivedAt":"2025-07-09T00:42:10Z","isPatch":false,"sender":{"key":"eschwartz@gentoo.org","avatar":"https://avatars.githubusercontent.com/u/6551424?v=4"},"body":"On 7/8/25 8:21 PM, Sahil Gautam wrote:\n> \n> On 7/9/25 3:01 AM, Junio C Hamano wrote:\n>> It would be very nice if these hosting providers can agree to make\n>> project metainformations interchangeable in an open way.\n> \n> it's not just about migrations, it's about a repository being self\n> reliant in itself. think of some git\n> hosting provider blocking my account because of some ai algorithm, think\n> of some disaster striking\n> some data center or some malware deleting all the data on the servers,\n> all these are quite possible.\n> \n> having git store that data means that you clone the whole thing and\n> doesn't matter what happens\n> to the hosting provider, if you have the repository, you have the whole\n> thing.\n\n\nYou may be interested in https://github.com/git-bug/git-bug\n\n\n-- \nEli Schwartz\n"},{"id":"521600","messageId":"368ceaae-e8af-4b9d-9e4e-26cddaf689aa@gmail.com","threadId":"63759","inReplyTo":"c629f3a6-4749-4ac0-8fbb-fd1fb9db1d0a@gentoo.org","subject":"Re: locally storing issues/comments/projects","fromName":"Sahil Gautam","fromEmail":"printfdebugging@gmail.com","sentAt":"2025-07-09T01:00:03Z","receivedAt":"2025-07-09T01:00:08Z","isPatch":false,"sender":{"key":"printfdebugging@gmail.com","avatar":"https://gravatar.com/avatar/b8432de9157687e76277bd6785da244201ea1f9f774b3f4727eb07ffc373a751?d=mp&s=160"},"body":"\nOn 7/9/25 6:11 AM, Eli Schwartz wrote:\n> On 7/8/25 8:21 PM, Sahil Gautam wrote:\n>> On 7/9/25 3:01 AM, Junio C Hamano wrote:\n>>> It would be very nice if these hosting providers can agree to make\n>>> project metainformations interchangeable in an open way.\n>> it's not just about migrations, it's about a repository being self\n>> reliant in itself. think of some git\n>> hosting provider blocking my account because of some ai algorithm, think\n>> of some disaster striking\n>> some data center or some malware deleting all the data on the servers,\n>> all these are quite possible.\n>>\n>> having git store that data means that you clone the whole thing and\n>> doesn't matter what happens\n>> to the hosting provider, if you have the repository, you have the whole\n>> thing.\n>\n> You may be interested in https://github.com/git-bug/git-bug\n>\nthanks Eli,\n\ni will look into git-bug try it out and see if it\ndoes the job. i think like docker-compose, any other feature requests such\nas this one have to first prove their worth in the wild, and since your \nsuggestion\ngave me a hint that they can exist separately, i will take that route.\n\n"}]}