simonw / simonw/llm

Actively invite people to contribute

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

Nobody has claimed this yet.

documentation
Dominant language
Python
Stars
12.5k
Forks
991
Avg merge
3d 13h
Merged PRs (30d)
10

Description

Discord conversation: https://discord.com/channels/823971286308356157/1128504153841336370/1147297935353204746

When asked about contributions I said:

Two biggest things are support and plugin research/development

Lots of people are asking questions in tickets - but the bigger thing is figuring out things like which models work best for different plugins, do they need extra configuration? And generally getting more models working
(I really wish llm-gpt4all didn't spew xtra junk to stderr)

Really I'd like there to be a solid chance that any model you might want to try can run in LLM, either via an existing plugin (with documented steps to run it) or via a new one

The most ambitious version of LLM is that it has a documented, clear path to getting model X running, on multiple platforms, for as many X as possible - and that it's widely used enough that model providers themselves start contributing plugins or plugin configuration documentation as part of their own releases

I need to actually turn this into a proper invitation - update the README and https://llm.datasette.io/en/stable/contributing.html page and really put the word out that I'm looking for help.

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

Start by reviewing the repository README and the contributing page at https://llm.datasette.io/en/stable/contributing.html, then compare their current guidance with the contribution needs described in this issue. Done means both pages contain a clear invitation covering support, plugin research and development, model compatibility, and documented setup paths; the requested outreach should also be clarified.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.