Solus Linux has announced a new policy on using AI and large language model tools in project contributions, explaining where these tools can and cannot be used.

The Solus team says developers can use AI to help with contributions, but they must take full responsibility for their work. Anyone submitting code or package changes needs to test them first. If AI was used, the commit should include an ‘Assisted-by LLM’ note. Only developers, not automated bots, can submit contributions.

“Contributions to Solus that were made with AI/LLM tools are allowed, as long as they follow our policy.”

Solus explains that the policy helps keep the operating system high-quality and easy to maintain. Since many people use Solus every day, contributors need to check and understand their submissions, not just share code made by AI.

However, the rules are stricter for written content. Solus does not allow any AI-generated or partly AI-generated material in its blog or official communications.

The team warns contributors not to hide their use of AI tools. If someone tries to cover up AI involvement, their work could be rejected, and they might be blocked from future contributions. Solus adds that the goal is to encourage open teamwork, not to watch every detail of how people work.

Solus says its new rules are based on the Budgie Desktop AI policy, which itself takes ideas from projects like the Linux kernel and Fedora. Still, they’re leaving the door open as the team also points out that this policy may change as AI tools become more common in software development.

For more details, see the official Solus announcement.

  • @hperrin@lemmy.ca
    link
    fedilink
    English
    4•
    edit-2
    5 hours ago

    Version 2 explicitly declares that dependencies are not considered:

    This does not include source codes and object codes of dependencies that are merely linked to, not stored, within the project, and any portions of object code resulting from the compilation of the imported source codes of linked dependencies when compiled during the normal build process of the project.

    Version 1 basically could be interpreted this way, but it wasn’t explicitly stated.

    If it’s a fork, and you want to accept upstream patches that have AI code into the codebase, then you can use the the upstream excepted version:

    https://sciactive.com/human-contribution-policy/version-2-up/

    As long as you clearly identify the upstream project as an upstream project.