You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi - looking for some fun side things to hack on during my spare time and got happily surprised to see lkpy having a spike of activity! Are these tickets open for contributors and if so is this a good starter ticket? Thanks!
Looked at this a little bit - I assume this should be now done with the new PopScore and either implemented as optional arguments/properties or as new classes?
Hi @ZiyaoWei — very glad you're interested in helping! You're right there's a lot of activity, and it makes things a bit of a moving target (and having built the pipeline and dataset abstractions, the next big lift there is to overhaul all of the model implementations to use them — so PopScore and friends are changing). I'm also on vacation this week, and will be returning to development on Aug. 26. I think this is a good first issue, though, and would love to provide what help you would need to contribute.
I think having it be a separate class from PopScore might make sense, just to keep PopScore simple.
If you wanted to work on a PR for the current APIs, you'd be welcome to; if you want to wait a couple weeks or so for the model API overhaul to land and do itagains the new code, that would remove the need to learn how to code for the current API.
Wow, thanks for the thoughtful and detailed response! I am traveling too this week and definitely can wait a few days, but overall would be happy to contribute :-)
Just curious about the API refactoring - is it happening in a branch I can check out? If not I can wait.
Right now,
Popular
is based on overall popularity.We should add support for time-bounded popularity: most popular items in the last N days.
Time-weighted popularity could also be interesting.
The text was updated successfully, but these errors were encountered: