• vas@lemmy.ml
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    7 hours ago

    That’s an example of a good LLM policy, especially for projects like forgejo / sourcehut / codeberg. Happy to see this approach is getting adopted more and more. (The main Rust repo recently also got a similar policy, although a bit weaker still.)

  • Voytrekk@sopuli.xyz
    link
    fedilink
    arrow-up
    5
    ·
    8 hours ago

    Reasonable. I would most vibe coders are just on GitHub because they don’t understand git in general.

  • toothbrush@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    7 hours ago

    This is a bit heavy handed I think. This also forbids AI assisted code review and lots of other things. Perhaps they should have defined it a bit more focussed on getting rid of vibecoded spam instead of forcing a specific developing format for their whole platform.

    • HelloRoot@lemy.lolOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      7 hours ago

      This also forbids AI assisted code review

      It’s worded in a convoluted way, but they explicitly allow it. In the chapter A matter of interpretation they say:

      “Moreover, the use of AI for purposes other than co-authoring code, tickets, emails, and so on, is discouraged but not prohibited. If you use LLMs privately to review your work, to ask questions of, to perform security analysis, and so on, and then write original code to push to SourceHut, your use-case is aligned with our policy.”

      • vas@lemmy.ml
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        5 hours ago

        The way I interpret it is that offline code review is fine. However, online AI-made comments or code suggestions on the platform are explicitly not allowed.

        A policy I find very reasonable for projects like forgejo / sourcehut / codeberg.