pksunkara
Joined 15 years ago
Karma
708
Submissions
82
Member since
Sep 12
Recent submissions
Comment · 1 day ago
Yes, we will be offering official CI (though nowhere near as free as GitHub). We will also support 3rd-party CIs (like https://buildkite.com, https://depot.com) & self-hosted runners (similar to GitHub)
Comment · 1 day ago
I think they all have different philosophies in approaching the problem.
* https://juju.bi - Local-first architecture
* https://cursor.com/docs/origin - Scalable VCS backend (this is actually very easy to implement by others)
* https://tangled.org, https://radicle.dev - Distributed forges
* https://entire.com - Very agent-centric
Comment · 1 day ago
I think all they have to do is stop giving free CI to everyone and this reliability issue will be solved immediately.
Disclaimer: I am building a code forge myself at https://juju.bi
Comment · 1 day ago
I see in the post that lexicon has been finalized. Does that include putting the issue, pr & comment records under the repo scope instead of the user scope?
I am asking because I have been waiting for that change. I intend to make all the public repos from https://juju.bi (code forge I am building) interoperable with Tangled and basically behave as knot server.
Comment · 11 days ago
I am trying to approach this problem from a different perspective at https://juju.bi
Comment · 1 month ago
Can someone tell me why people prefer temporal over something like https://restate.dev?
Comment · 1 month ago
I am working on a code forge that can work offline for the collaborative stuff. https://juju.bi
Comment · 1 month ago
Yes, it is a cloud service and CI. It is not region specific for now since I am not in EU.
Comment · 1 month ago
How is this different from a custom forgejo hosted in europe? What features does this provide compared to traditional code forges?
Disclaimer: I am building https://juju.bi, therefore you don't need to answer if uncomfortable.
Comment · 2 months ago
I am working on a GitHub compatible API for my code forge at https://juju.bi, and thus all the existing integrations of GitHub should theoretically work with my code forge too.
Comment · 3 months ago
FWIW, I really like what Tangled is doing and I agree that we need a federation of forges. Which is why, I am planning to use ATproto too for public repositories in the code forge I am building, https://juju.bi
Comment · 3 months ago
I am building a new code forge at https://juju.bi
It's not agent-first, but I can't think of any features that are needed for agents other than scalability.
Comment · 4 months ago
Let me start off (assuming all code forges have PRs)
1. Branch protection rules
2. CI
3. Terraform provider (API)
http://github.com/pksunkara
https://www.linkedin.com/in/pksunkara
[ my public key: https://keybase.io/pksunkara; my proof: https://keybase.io/pksunkara/sigs/YXTiDymHTSwfTfEjI2dZWnYM9dPA_eYyck8jXzPT71Y ]