It Breaks a Village: Bevy's 6th Birthday
blog.fallible.net
This post, like all my posts, was written by me. It came out of a lot of conversation and reflection with many people. It is long. I promise you there's valu...
  • rhamph@awful.systemsEnglish
    4·
    4 days ago

    I had some interest in trying out Bevy for some future projects, in no small part due to their anti-slop policy. Guess I won’t bother?

    • Alex@lemmy.mlBanned from communityEnglish
      31·
      4 days ago

      The policy itself is pretty sound and puts the emphasis on human ownership of the code while explicitly forbidding it for communication, commit messages and assets. It’s trying to encourage disclosure and doesn’t force any maintainer to take the code.

      A lot of the drama seems to be around the code of conduct changes which seem to be a result of some very acrimonious debates within the community.

      • rook@awful.systemsEnglish
        1·
        1 day ago

        while explicitly forbidding it for communication, commit messages and assets

        This is absolutely the best bit of the policy, and clearly shows how much thought went into the whole thing. Everyone knows that ai generated art is shit, so that’s forbidden, ai generated summaries are just inadequate so that’s forbidden too, using a chatbot to communicate with someone is deeply fucking insulting, so that’s forbidden as well, but… uh… using the bo-bot to write your code for you is apparently a-ok! for reasons! in a project which is primarily a a collection of code! 🤠

        I can’t imagine why there’s acrimony. The whole thing is entirely coherent and well considered 🤗