{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic4cc7br3rxusz5vkpt4nufq6jecpzh6ncqxohrn7zkb5gwf34wgi",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3ml5dmqzcfrx2"
  },
  "path": "/t/call-for-proposals-reviewing-testing-and-managing-llm-generated-haskell/14041#post_1",
  "publishedAt": "2026-05-05T23:22:48.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "[1]",
    "↩︎"
  ],
  "textContent": "Hey everyone,\n\nThings are moving pretty fast in the world of LLMs and we’re all trying to navigate our way through it. In Open Source we wonder how projects should deal with LLM-based code contributions, or maybe even have strict policies about it. In industrial code-bases we don’t have the random drive-by LLM contribution problem, but we do have issues around trust/correctness.[1]\n\nThe Haskell Foundation is considering running an online 1-day workshop on how companies are managing/navigating their use of LLMs and how open source maintainers view LLM contributions.\n\nIdeally this would be a quick turnaround, hosted sometime mid-June (likely June 19th), as there’s lots of hunger for folks to learn from each other.\n\nIf you would like to give a talk at this online event (and therefore the speakers can be anywhere), please send a short 1-2 paragraph talk proposal to jmct@haskell.foundation, by end of day May 12th (anywhere in the world).\n\nPotential topics include but are not limited to:\n\n  * best practices around testing LLM generated code\n  * Creative use of types in enforcing LLM conformance\n  * Prompting that helps with getting ‘good Haskell’\n  * Observed/experienced pitfalls with LLM generated Haskell code.\n\n\n\nThe idea here is that we learn from each other and figure out, as a community, how to best leverage these tools, whether we’re forced to by company policy, or whether we’ve found the tools useful. We know that the use of these tools is controversial, a talk proposal does not have to be ‘pro’ LLM, but we do want it to be useful and _actionable_ , the idea is to learn from each other.\n\n* * *\n\n  1. This problem isn’t unique to industrial code-bases, but what used to be a “we trust our team” has now become “do we trust our LLM?”. ↩︎\n\n\n",
  "title": "Call for proposals: Reviewing, testing, and managing LLM generated Haskell"
}