This has become a common occurrence across various open-source projects. It seems like there’s a massive investment in tokens—a desperate scramble to find any opening to shoehorn a patch into the codebase, just to post about it on LinkedIn.
I’ve seen a range of attitudes toward this: from code maintainers fully embracing it (which is actually a bit unsettling) to outright blocking anything AI-generated (sometimes discarding potentially interesting contributions in the process). I think the best suggestion I’ve seen is a middle-ground approach. Projects could build the necessary infrastructure internally to support AI-driven activities, treating them as native to the project rather than the work of an external entity simply scouring for opportunities. This would allow interested individuals to contribute their tokens to run whatever tests they deem appropriate. I don't believe the current volume justifies the effort. But once it starts to become excessive, that idea might be worth considering. -- Douglas Fernando Fischer Engº de Controle e Automação
