New package: ProblemSets v0.10.0

[JuliaRegistrator]

• Registering package: ProblemSets
• Repository: https://github.com/kagalenko-m-b/ProblemSets.jl
• Created by: @kagalenko-m-b
• Version: v0.10.0
• Commit: 78d29aaba48006b194bc4ab4ae24129f72d29c4a
• Reviewed by: @kagalenko-m-b
• Reference: kagalenko-m-b/ProblemSets.jl@78d29aa#commitcomment-175135408
• Description: Generate word problems for a group of students

[kagalenko-m-b]

I make this registration request together with PR #146594 following the guidelines for renaming an existing registered package.

The need for changing the name arises from the rule 3 for naming. In the course of developing this package, I came to recognize the need to introduce a type associated with its functionality.

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

• Package name similar to 1 existing package.
  1. Similar to ProblemSet. Damerau-Levenshtein distance 1 is at or below cutoff of 2. Damerau-Levenshtein distance 1 between lowercased names is at or below cutoff of 1. Normalized visual distance 2.26 is at or below cutoff of 2.50.

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[kagalenko-m-b]

[noblock] Thank you for clearing that for merge. The PR #146594 is still stalled, though: perhaps, somebody could take a look at it, as well? Thanks.

[DilumAluthge]

Hi @kagalenko-m-b, welcome, and thanks for your PRs! I'm coming here via #146594.

It looks like you'd like to rename your package from ProblemSet.jl to ProblemSets.jl.

I'm a little bit concerned about having both ProblemSet.jl and ProblemSets.jl in the registry, since the two names are very similar. Would there be a different way to accomplish your goals, without having both ProblemSet.jl and ProblemSets.jl being registered?

If I understand correctly, your motivation is that you'd like to have a type named ProblemSet. Would it be possible to have a different name for the type? E.g. maybe you could keep the package named ProblemSets, and then the type would be Pset? And then the user would do ProblemSets.Pset or using ProblemSets: Pset? This would allow us to keep the ProblemSets.jl name?

What do you think? I'm happy to brainstorm other ideas as well.

[kagalenko-m-b]

Hi @kagalenko-m-b, welcome, and thanks for your PRs! I'm coming here via #146594.

It looks like you'd like to rename your package from ProblemSet.jl to ProblemSets.jl.

I'm a little bit concerned about having both ProblemSet.jl and ProblemSets.jl in the registry, since the two names are very similar. Would there be a different way to accomplish your goals, without having both ProblemSet.jl and ProblemSets.jl being registered?

My reasoning for (temporarily) keeping both names in the registry is to avoid confusing some user (not sure how many of those really exist). Note that the old name will be pointing to the new package anyways, so a user installing the old package will see his code breaking; using ProblemSet will no longer work. The PR #146594 can be kept for a few months and then the old name may be deleted. This would be the preferred solution, as far as I am concerned.

If I understand correctly, your motivation is that you'd like to have a type named ProblemSet. Would it be possible to have a different name for the type?

The “rule 3” recommendation in the naming guidelines is followed by the majority of packages. Rather than exploring different naming schemes, if keeping the both names is a problem, I would prefer to make a clean break by getting rid of the old package after I develop version 1.0 of the new package and post announcement to the discourse.
[noblock]

[DilumAluthge]

Thanks for providing those details. I'm going to discuss this with the other registry maintainers, and one of us will follow-up with an update here.