Skip to content

A decentralised package discovery and fetching for C3 #2077

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joshring opened this issue Apr 6, 2025 · 2 comments
Open

A decentralised package discovery and fetching for C3 #2077

joshring opened this issue Apr 6, 2025 · 2 comments

Comments

@joshring
Copy link
Member

joshring commented Apr 6, 2025

We could create a simple API and database to aggregate c3 projects.

A C3 project is defined as having a topic assigned like eg c3-module

A similar idea has happened here for zig

https://zigistry.dev/ has the output
https://zigistry.dev/help/ is how the topics are assigned to a repo

Searching GitHub API
Todo: initial search https://stackoverflow.com/questions/51912862/how-to-list-all-repositories-for-a-given-topic-with-rest-api-in-github

Decentralised in that we don't have to manage those projects, registration, emails, resetting password etc, who gets updated etc. But we could add a filter for malicious projects which we do not wish to allow.

@joshring joshring changed the title A decentralised package discovery and fetching for C3 We could create a simple API and database to aggregate c3 projects. A C3 project is defined as having a topic assigned like eg c3-module A similar idea has happened here for zig A decentralised package discovery and fetching for C3 Apr 6, 2025
@devin12422
Copy link

I'm confused about how the GitHub API is decentralized, but regardless, there's an idea I'd love to see made manifest in C3's package manager. That'd be Unison's Content Addressing. To pull the point from directly from the article; "No dependency conflicts"

@joshring
Copy link
Member Author

joshring commented Apr 7, 2025

Decentralised in that we don't have to manage those projects, registration, emails, resetting password etc, who gets updated etc. But we could add a filter for malicious projects which we do not wish to allow.

Thanks for the link, I'll have a look later on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants