00:00:36 <xmr-pr> > https://github.com/monero-project/monero/pull/11025
02:15:35 <xmr-pr> bsandham opened pull request #11026: simplewallet: show default value in Y/N prompts
02:15:36 <xmr-pr> > https://github.com/monero-project/monero/pull/11026
10:30:35 <xmr-pr> maogo opened issue #11027: why wallet cannot refresh by public rpc
10:30:36 <xmr-pr> > https://github.com/monero-project/monero/issues/11027
12:45:35 <xmr-pr> tobtoht opened pull request #11028: depends: boost: don't embed absolute paths in cmake config
12:45:36 <xmr-pr> > https://github.com/monero-project/monero/pull/11028
16:14:43 <selsta> .merge+ 10989 10988
16:14:43 <xmr-pr> Added
17:15:35 <xmr-pr> jpk68 opened pull request #11029: cryptonote_protocol: avoid copying block span in add_blocks
17:15:36 <xmr-pr> > https://github.com/monero-project/monero/pull/11029
17:30:35 <xmr-pr> jpk68 opened pull request #11030: wallet2: fix faulty bounds check
17:30:36 <xmr-pr> > https://github.com/monero-project/monero/pull/11030
18:00:35 <xmr-pr> tobtoht opened pull request #11031: depends: native_protobuf: don't include debug symbols in protoc binary
18:00:36 <xmr-pr> > https://github.com/monero-project/monero/pull/11031
18:28:05 <selsta> tevador: what is the goal of the policy? is it a document that can be cited if a PR is closed and someone complains, or is it something that needs to be followed to the letter?
18:28:12 <selsta> I mean apart from the copyright stuff of course
18:28:27 <selsta> but if I as maintainer see something that is clearly useful but it looks like it's written by a bot do I have to close it?
18:36:43 <tevador> Hopefully, the AI agent will read the policy and act accordingly.
18:39:32 <br-m> <jpk68:matrix.org> Having to close LLM-authored PRs that fix legit bugs will be nothing but a burden
18:39:47 <br-m> <jpk68:matrix.org> Why not just keep doing things the way we've already been doing them?
18:40:39 <selsta> I do not want to play LLM detective, and I do not want to reject legit useful changes.
18:42:33 <tevador> I would take it as a gate to stop the flood of AI submissions. If an AI agent submits a valid issue, I don't think it needs to be closed.
18:43:30 <selsta> the current suspected AI agents that submit PRs are not an annoyance in my opinion, and so far also haven't produced a flood
18:43:38 <selsta> 3 months ago I had a different opinion but there was a change in quality
18:44:06 <tevador> Can you guarantee there won't be another change of quality for the worse?
18:45:05 <selsta> the same happened on HackerOne, previously AI reports were mostly hallucination while around 4 months ago it changed to legit vulnerability findings
18:48:08 <br-m> <slowbeardigger:matrix.org> tevador: no one can guarantee that
18:48:08 <br-m> <slowbeardigger:matrix.org> sure, AI can do crappy stuff, but it is responsibility of the ones who use it
18:48:08 <br-m> <slowbeardigger:matrix.org> i use it, i am transparent and i take full responsibility for the things i do
18:50:39 <tevador> https://github.com/monero-project/monero/pull/11002#issuecomment-5159828820
18:51:17 <br-m> <ofrnxmr:xmr.mx> I think the question is about allowing the codebase to be damaged by bloated, unmaintainable garbage
18:52:05 <selsta> in general I'm okay with the current version of the document
18:53:04 <selsta> I think there is a large gap between using AI to reproduce another projects copyrighted work and a one line but fix but I assume we don't need to detail that in that document
19:45:35 <xmr-pr> jpk68 opened pull request #11032: doxyfile: remove comments, improve build performance
19:45:36 <xmr-pr> > https://github.com/monero-project/monero/pull/11032
19:45:59 <br-m> <jpk68:matrix.org> Wow, it took less than half an hour this time!
19:46:12 <br-m> <jpk68:matrix.org> :)