JuliaRegistries / General

The official registry of general Julia packages
https://github.com/JuliaRegistries/General/blob/master/README.md
MIT License
607 stars 465 forks source link

Clearer when-to-register criteria #74283

Closed Rratic closed 1 month ago

Rratic commented 1 year ago

Here's the original comment:

https://github.com/itsdfish/JokerJailBreak.jl/issues/1#issuecomment-1356193634

I don't know how many packages have sneaked in the registery, but it could be necessary, I guess.

DilumAluthge commented 1 month ago

Here is what the General registry README currently says:

https://github.com/JuliaRegistries/General/blob/aedbcb2b258933cd17b8e73c1c0a9ad03a913961/README.md?plain=1#L93-L122

I think this covers your question, right? Are there specific questions that you have that are not answered by the above? Or specific information that you'd like us to add to the README?

Rratic commented 1 week ago

That's a good move, but does not solve the original problem in the comment.

I am still confused about the policy because the term "personal use" is not defined, which makes it impossible to know if I am in violation of the policy.

I recommend opening an issue in the general registry and proposing clearer criteria on what constitutes personal use and perhaps a method for enforcing the policy. For example, a package must satisfy 3 out of 4 criteria to be registered. If the package does not meet the guidelines, an individual can submit an issue on the general registry with an explanation detailing how the package fails the guidelines. In the example, the author mentioned the package "JokerJailBreak", a game that is neither classic or serious. That cannot be defined as "personal use". I do apologize for not finding out that it fits the rule of "utility functions", but that type of expression do leave unexpected loopholes.

And as quoted, there should be practical ways to deal with sneaky packages. I guess a feasible way would be adding lines of notification in register posts.