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

Tag for preprint

Open
  • Is something wrong?
#83 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, python
Domain
documentation, release

Research direction

Start by reading the README and inspecting the existing preprint tag in the repository. Document that tag and the purpose of keeping main moving in the README, then verify that the new text explains how tagged versions relate to the paper and future versions.

Written by the indexing model from the issue text.

Description

I have introduced a first tag for the version of the code used for the preprint published. I should mention this in the readme. We can have more tags for the paper and different versions of it. We can keep main moving a make sure it won't stop working.

Dominant language
Python
Stars
37
Forks
10
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 cvxgrp/markowitz-reference

All issues in cvxgrp/markowitz-reference

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.