-
Notifications
You must be signed in to change notification settings - Fork 457
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
New package: PeriodicHiddenMarkovModels v0.1.2 #91965
New package: PeriodicHiddenMarkovModels v0.1.2 #91965
Conversation
JuliaRegistrator
commented
Sep 22, 2023
- Registering package: PeriodicHiddenMarkovModels
- Repository: https://github.com/dmetivie/PeriodicHiddenMarkovModels.jl
- Created by: @dmetivie
- Version: v0.1.2
- Commit: 4f656ebfaaace5a53e84f218df86f1f53f00a336
- Reviewed by: @dmetivie
- Reference: dmetivie/PeriodicHiddenMarkovModels.jl@4f656eb#commitcomment-128064289
- Description: Extension of the package HMMBase.jl that deals with non-homogenous Hidden Markov Models
UUID: 4873b48c-7fd1-4fb6-93c5-649b25bdde2e Repo: https://github.com/dmetivie/PeriodicHiddenMarkovModels.jl.git Tree: f3beae4f9ab631e64381b0d9532ae3e38ddec038 Registrator tree SHA: f73a20c99934db92a256057d0d83ba394036a701
Your Since you are registering a new package, please make sure that you have read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1 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] Hey @dmetivie! Congrats on the package :) |
[noblock] Ho woah, I was reading that when I got your message! Some many questions, would you be available for a chat? |
[noblock]
@cmantoux is one of my best friends ^^
Sure, hit me up on the Julia slack or via email at [email protected] and we'll talk ;) |
[noblock] @gdalle FYI: You blocked registration of the package. Both of you @dmetivie need to [unblock], and I though putting [unblock] in your last comment would be enough, but I'm apparently wrong. I guess it happens if you update all of your comments. If you unblock/register now it would become package 9999, or if you time right then package 10,000... |
[noblock] This was voluntary on my end, we're having a meeting tomorrow with @dmetivie to see if we can work together on this |
[noblock] @gdalle it seems both of you want to unblock, but it seems it didn't happen, since you missed adding [unblock] to your first comment here. Since both of your have otherwise unblocked then now it's in your hands if it gets unblocked early or as package 10,000. If by "working together" and "voluntary on my end" you mean maybe this package should NOT be registered, rather merged into yours then, maybe not unblock... |
[noblock] Yeah I left the first comment unchanged on purpose since I didn't know if @dmetivie wanted to wait for our meeting. But since he modified his comment in the meantime to unblock, I assume he wants to register and that's also fine by me. We can always tag a new version after if we decide to join forces |
[noblock] Thanks! I had no clues about no/blocking and I thought Julia was already over 10,000 pkg! |
Nr. 9999 is still a cool number, I was kind of hoping this one would become 10,000 though... Package 10001 is not yet registered, also a cool number. |
Where do you see the package number? |
I just tested this it works. A few minutes ago it turned to 10000 |
@gdalle I.e. I have an obvious human way (look up the file and subtract 13); and already Ruby code already to extract the number. I bumped that issue, ideally you or someone could fix there. Would be great if modulecounts.com would work by now for Julia too. For the actual count of this package or any other, I was just monitoring https://github.com/JuliaRegistries/General/commits/master You can know the latest, it's tedious to scroll back to a not-recently registered package, right now, this one is the last one and easy. There may be no good automated way, you would need to filter out "New package", but more importantly and ideally get the same info from some Github API. |
Thanks for the detailed walkthrough! |