Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat: Support mlflow as a board to read/write model pins

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

The issue names VetiverModel, boards, and an mlflow registry but no files or tests. Start by locating the board and model-pin entry points, then compare how model versions, metadata, dependencies, and API deployment are represented. Done means an mlflow-backed board can read and write model pins while preserving the existing user experience.

Written by the indexing model from the issue text.

Description

enhancement

Vetiver and mlflow speak similar languages so it likely possible to view mlflow as a board to pull model versions into a VetiverModel and then deploy as an API. From the user's perspective, things would be more or less the same, but model itself and its metadata, deps, etc. would be coming from an mlflow registry.

Dominant language
Python
Stars
71
Forks
20
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from rstudio/vetiver-python

All issues in rstudio/vetiver-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.