Skip to content

recommendation of https://nimpkgs.dayl.in #3086

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

Merged
merged 1 commit into from
Aug 1, 2025
Merged

Conversation

ringabout
Copy link
Member

ref #2995

@esafak
Copy link
Contributor

esafak commented Jul 30, 2025

It's not going to be open sourced so I disapprove.

I was confusing it with https://npacks.pages.dev

@hugosenari
Copy link

It's not going to be open sourced so I disapprove.

We are recommending a URL (an actual hosted site) so it doesn't matter if it is open or closed source, unless we are actually crowdfunding its operations.

@daylinmorgan
Copy link
Contributor

It's not going to be open sourced so I disapprove.

Over on the other issue navid-m was saying npacks.pages.dev won't be open sourced.

nimpkgs is already open-source.

@esafak
Copy link
Contributor

esafak commented Jul 30, 2025

Sorry, I was thinking of the other site mentioned in that thread, https://npacks.pages.dev, not your https://github.com/nimpkgs/website

Furthermore, I did not realize we had two competing registries; https://github.com/nimpkgs/nimpkgs and https://github.com/nim-lang/packages (right?) This is unfortunate.

What if we kept the existing monolithic registry and simply designed a better web site? The good thing about having the registry in one json file is that it simplifies web site design. Otherwise you have to clone the repo to fetch everything, which is not feasible in a static client-side web site.

@daylinmorgan Are you open to PRs to the website?

@daylinmorgan
Copy link
Contributor

Just to remove some confusion.

nimpkgs exists (for fun mostly) to take the ground truth from nim-lang/packages and give a pretty website.

nimpks/nimpkgs is not a competitor it's just an implementation detail of the website.
The "registry" at nimpkgs/nimpkgs is just a data dump I use to populate the site with extra info that isn't relevant to the package registry.

I'm open to PRs to the website (though I would expect first some discussion about issues or feature requests).

@esafak
Copy link
Contributor

esafak commented Jul 30, 2025

I see you set up a https://github.com/nimpkgs/crawler to automatically synchronize it with https://github.com/nim-lang/packages, so users still interact only with the latter. That is fine.

I'm open to PRs to the website (though I would expect first some discussion about issues or feature requests).

Would you like to open up Discussions in https://github.com/nimpkgs/website to hold these discussions or do you want people to use Issues for suggestions too? Done, thank you.

@ringabout ringabout merged commit 657bda4 into master Aug 1, 2025
2 checks passed
@ringabout ringabout deleted the ringabout-patch-1 branch August 1, 2025 14:59
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

Successfully merging this pull request may close these issues.

4 participants