Skip to content
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

Feature request: keeping packages' title pages up to date. #4

Closed
rolling-robot opened this issue Mar 25, 2023 · 3 comments
Closed

Feature request: keeping packages' title pages up to date. #4

rolling-robot opened this issue Mar 25, 2023 · 3 comments

Comments

@rolling-robot
Copy link

Title pages for packages on https://juliapackages.com are generated from higly outdated readme files. For example it is quite misleading to see warning on https://juliapackages.com/p/outlierdetection about installation of versions before 0.2, while the actual version on github is 0.3.3. Examples from https://juliapackages.com/p/outlierdetection also do not work.

It turned out that the maintainer did not know how to update the information on title page of his package: OutlierDetectionJL/OutlierDetection.jl#37 (comment)

I see that the information was fetched from packages' readmes to data/readme_html/[packagename].txt 2 years ago and was not updated since then, so the situation might be quite similar for many projects. It seems that there is no mechanism for maintainers to update their title pages.

Given that often the link to juliapackages.com is on the first page of search engines, a very unfortunate impression of newcomers might be that julia ecosystem is abandoned, which is not the case.

I think it could be reasonable to have some mechanism for keeping title pages up to date.

@djsegal
Copy link
Owner

djsegal commented Jun 14, 2023

Is this fixed?

@rolling-robot
Copy link
Author

Yep, the source htmls are up to date now. Thanks for fixing this and for a great package navigation on juliapackages.com
BTW, are you planning to do some sort of regular update, e.g. with CI of package descriptions?

@djsegal
Copy link
Owner

djsegal commented Jun 14, 2023

Possibly in the future. Its hard to do with the war on APIs every company is creating nowadays

When I built JuliaObserver.com, I had cron jobs that updated 4 times a day. But sometimes the website would stop working and I only found out when people made github issues (i.e. if i was on vacation)

However I will try to do better than updating once every 2 years. The main hurdle here was Github blocked how I used to do API requests. Actually had to use ChatGPT to figure out how to port over to the new paradigm

@djsegal djsegal closed this as completed Jun 14, 2023
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