For absolutely no reason, today I'm looking into systems where issues/prs exist within a git repo itself so they can be pushed to alternative hosts easily.
Replying to @andrewnez@mastodon.social
@andrewnez lessons learned from SourceForge…
@andrewnez quite excited about git-bug, for that matter! https://github.com/git-bug/git-bug
Replying to @andrewnez@mastodon.social
@andrewnez I would assume that there are neat tools for this, and that they create a structure that one could easily search for.
Replying to @andrewnez@mastodon.social
@andrewnez Also, easier to archive? Not sure if something like https://github.com/git-bug/git-bug would work with https://git-scm.com/docs/git-bundle (but it probably would)
GitHubGitHub - git-bug/git-bug: Distributed, offline-first bug tracker embedded in gitDistributed, offline-first bug tracker embedded in git - git-bug/git-bug
Replying to @andrewnez@mastodon.social
@andrewnez I'm hacking on one of those. My general opinion is that it is going to be impossible to be pleasant without a server component and would scale to maybe 2-3 contributors. My core idea is that keepachangelog-fragments look like jira tickets
https://github.com/matthewdeanmartin/keepachangelog-manager/tree/main/tickets
GitHubkeepachangelog-manager/tickets at main · matthewdeanmartin/keepachangelog-managerEdit, Validate CHANGELOG.md files. Bump version and push GH release. - matthewdeanmartin/keepachangelog-manager
@andrewnez This seems like a natural thing to do, to me. The SQLite version control system, Fossil, does things that way.
Replying to @andrewnez@mastodon.social
@andrewnez
https://github.com/xit-vcs/haxy
This is very interesting, still in early stages though
GitHubGitHub - xit-vcs/haxy: a git forge from the future-pasta git forge from the future-past. Contribute to xit-vcs/haxy development by creating an account on GitHub.