• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: September 4th, 2025

help-circle



  • I can’t speak for the community, however in 2022 when ChatGPT was in development, lots of us were excited about it. When ChatGPT came out, and the image AIs came out, I tried them and was pretty impressed at first. However as I learned more about them and time went on, I learned to not like them, and avoid them. This is what happened:

    • I realized that ChatGPT would make subtle mistakes that were impossible to catch if you didn’t have expert knowledge
    • I wasted a lot of time using AI trying to get it to give me right answers
    • People at work used ChatGPT to make subtle mistakes which negatively affected me
    • I learned about how writers and artists were having their work stolen and put into these large models without their consent
    • I learned about the environmental costs
    • Computer hardware started getting stupidly expensive :(
    • I learned how using AI can make you rely on it, and you lose critical thinking skills.
    • I have seen people in the real world defer to “AI” as an authority on a subject.
    • I learned how many of the AI tech bros sincerely believe their own hype and think that Advanced General Intelligence is going to develop out of the same tech as llm and pose a threat to humanity and/or save humanity
    • Companies have started using AI to make customer service worse
    • Small businesses turned to AI to make awful flyers and menues which make my experience in the world worse
    • Bosses use AI as a way to fire people and or control the workforce better
    • The surveillance state is using AI to destroy privacy

    So that’s why i don’t like it and try not to use it any more.



  • The Maintainers Summit reached consensus to deprecate the Assisted-by
    tag. Remove the documentation requiring it.
    
    Signed-off-by: Sasha Levin <[email protected]>
    ---
     Documentation/process/coding-assistants.rst   | 21 +------------------
     Documentation/process/submitting-patches.rst  | 10 ---------
     .../it_IT/process/submitting-patches.rst      | 10 ---------
     scripts/checkpatch.pl                         | 11 ----------
     4 files changed, 1 insertion(+), 51 deletions(-)
    
    diff --git a/Documentation/process/coding-assistants.rst b/Documentation/process/coding-assistants.rst
    index 051f0d819f68e..509dbf23a099b 100644
    --- a/Documentation/process/coding-assistants.rst
    +++ b/Documentation/process/coding-assistants.rst
    @@ -40,24 +40,6 @@ is responsible for:
     * Adding their own Signed-off-by tag to certify the DCO
     * Taking full responsibility for the contribution
    
    -Attribution
    -===========
    -
    -When AI tools contribute to kernel development, proper attribution
    -helps track the evolving role of AI in the development process.
    -Contributions should include an Assisted-by tag in the following format::
    -
    -  Assisted-by: LLM [TOOL1] [TOOL2]
    -
    -* ``[TOOL1] [TOOL2]`` are optional specialized analysis tools used
    -  (e.g., coccinelle, sparse, smatch, clang-tidy)
    -
    -Basic development tools (git, gcc, make, editors) should not be listed.
    -
    -Example::
    -
    -  Assisted-by: LLM coccinelle sparse
    -
     Procedure for finding and fixing bugs
     =====================================
    
    @@ -82,8 +64,7 @@ these steps:
        another one. The fix must not add build warnings and must pass the
        checkpatch.pl checks (see submitting-patches.rst).
     6. Commit the working fix with a detailed message describing the problem, the
    -   solution and a Fixes tag. Do not add a Signed-off-by tag, and add an
    -   Assisted-by tag, as described above.
    +   solution and a Fixes tag. Do not add a Signed-off-by tag.
     7. Identify the maintainers and lists using scripts/get_maintainer.pl.
        Documentation/process/security-bugs.rst shows how to do that.
     8. Indicate what could not be done. If the fix could not be built or tested, or
    diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
    index 7ae79452e1b46..5f4e0156cca78 100644
    --- a/Documentation/process/submitting-patches.rst
    +++ b/Documentation/process/submitting-patches.rst
    @@ -632,16 +632,6 @@ bugzilla.kernel.org is a public place in this sense, but email addresses
     used there are private; so do not expose them in tags, unless the person
     used them in earlier contributions.
    
    -Using Assisted-by:
    -------------------
    -
    -If you used any sort of advanced coding tool in the creation of your patch,
    -you need to acknowledge that use by adding an Assisted-by tag.  Failure to
    -do so may impede the acceptance of your work.  Please see
    -Documentation/process/coding-assistants.rst for details regarding the
    -acknowledgment of coding assistants.
    -
    -
     .. _the_canonical_patch_format:
    
     The canonical patch format
    diff --git a/Documentation/translations/it_IT/process/submitting-patches.rst b/Documentation/translations/it_IT/process/submitting-patches.rst
    index a742610cb0709..d0e0d6c9ecc2e 100644