At least for the specific example given, I want developers to do the commit part themselves, so if their LLM is doing any part of that, its already a mistake IMO.

I had a very quick look at the AI agent guidelines, and nothing about them strikes me as overly burdensome for a human to fix up. So I’d rather just do that myself (if I were a kernel dev).

My main objection is forcing it on developers, it should be up to each dev to configure and manage their own agent. Making it a suggestion is fine, just don’t commit it. Also, if developers are using local hosted models, then context may be quite limited, so wasting it on an Agents.MD maybe be unideal.

I’m on board with committing formatter config, because thats deterministic and really should be shared amongst a team.

I don’t get why the agent needs to have the contrib guidelines, it should be a human doing the actual contrib part, so its just a waste of tokens for the LLM to read it?

I don’t get why agents.MD needs to be committed. It feels a bit like committing IDE settings, everyone is going to have slightly different preferences, so its better to just have everyone do their own thing. If anything, I prefer to .gitignore itso it doesnt get accidentally committed.

Of course, but the problem is that new users come here, see a sea of repost bots, and then conclude that its a ghost town.

And then they get mirrored to fediverse via bots…

I think its simpler than that, its just stock price pumping. They can tell the plebs that they have the tech to put servers in space, and the plebs will eat it up and pump the stock.

You can still destroy the terrestrial base stations.

Bed frames are feminine, put that mattress on the floor. While your at it, get rid of the sheets, bare mattress it up.

Lighting is too fancy, fancy is feminine. Plain flickering bulb is what you want for ambiance.