OpenLAIR / OpenLAIR/OpenSkill

Possible name collision with the existing OpenSkill (Bayesian rating library)

Open
#2 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PDDL
Stars
94
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Hi, and congrats on the paper: the open-world, supervision-free framing is a nice contribution.

Philihp Busby and I (Vivek Joshy) maintain OpenSkill (https://github.com/vivekjoshy/openskill.py), a Bayesian multiplayer rating system. It's published in JOSS (2024) and on arXiv since January 2024 (arXiv:2401.05451), distributed as the openskill package on PyPI and also on NPM, and used in production by projects including OpenAI, Marvel Rivals, HuntShowdown, and BeyondAllReason. It is also cited in many deep learning projects and papers (see sources below). The prior art goes back to 2020.

I wanted to flag a name collision: your project is also called "OpenSkill," in the same broad ML / cs.AI space. That's likely to cause search, citation, and packaging confusion for both of us; "openskill" queries, Scholar / Semantic Scholar disambiguation, and anyone trying to pip install openskill expecting the statistical rating library.

Since the code hasn't shipped yet, this seemed like the lowest-friction moment to raise it: a rename now would be much cheaper than after release and citations accumulate. Would you consider a different name for the framework? Happy to help brainstorm alternatives if that's useful.

No hard feelings either way, just trying to save us both some downstream confusion. Thanks!

CC: @philihp

Sources:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named, and the repository description says code is coming soon. Start by reviewing the project’s naming, packaging, and publication plans; done means the maintainers decide whether to rename the framework and record that decision.

Written by the indexing model from the issue text.

Assessment

Domain
ai
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.