fsprojects / fsprojects/FSharpLint

Checking on on maintainers status

Open
#721 4 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
F#
Stars
327
Forks
74
PR merge metrics
No merged PRs in 30d

Description

Hi @duckmatt, @knocte, @jgardella,

A friendly check-in on maintainer status in this repo! There was discussion on https://batsov.com/articles/2025/03/30/why-fsharp/ about this not being maintained recently and I wondered if you'd like us fsprojects backup maintainers to put out a "Call for Additional New Maintainers"?

I'd reckon there would be interest from a few people to bring this up-to-date

We're here to help, see policies at https://github.com/fsprojects

Thanks!
Don, also for @sergey-tihon

Contributor guide

Open the contributing guide

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

This issue is a maintainer-status check-in rather than a code change. Start by reviewing the linked discussion and the fsprojects policies; no file, test, entry point, or concrete completion criteria are provided.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.