mirrors/rcl
1
0
Fork 0
mirror of https://github.com/ruuda/rcl.git synced 2025-12-23 04:47:19 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
rcl/CONTRIBUTING.md
Ruud van Asseldonk b43e0692a8 Add LLM policy to the contribution guide 
Now that "vibe coding" is starting to become a thing, and there are some
tasks in RCL that presumably could be vibe-coded, like support for more
editors, I think it's a real risk that people start making pull requests
for code that was primarily written by an LLM and not by a human.

I don't use such tools myself, but based on what I've seen, this
technology is at a level where it is able to write a (mostly) working
solution, but it is not nearly at a level where it produces acceptable
code. Output is far too verbose, and even when humans are driving, if
it's so easy to generate more code, then instead of thinking "how can I
abstract this so I don't have to duplicate it", you just accept the
generated duplicates. Kind of the antithesis of RCL itself.

Aside from that, there is still the legal grey zone of whether LLMs
enable mass copyright infringement by repeating snippets verbatim from
other codebases without attribution. I don't want to argue about where
the boundary is, I want to stay far away from the boundary.

In short, I don't want any AI slop in this codebase, so it's better to
warn people ahead of time to prevent disappointment.
2025-04-06 19:17:42 +02:00

757 B
Raw Permalink Blame History

Contributing

Contributions in the form of bug reports or pull requests are welcome. For pull requests, please consider:

  • Write a proper commit message and keep the history clean. Put unrelated changes in separate commits.
  • Basic checks (formatting, rustfmt and black, and typechecks, cargo check and mypy --strict) should pass at every commit.
  • Contributions must be authored by a human, LLM-generated code is not allowed.
  • You agree to license your contribution under the Apache 2.0 license.

Code of conduct

  • Be nice.
  • Please do not discuss politics in the issue tracker, the issue tracker is for technical issues.