jpk68: you can follow progress here monero-project/monero #10369

.merge+ 10474 10482 10483 10484 10485

Added

.merges

10457 10463 10464 10466 10474 10482 10483 10484 10485

<r4v3r23> selsta: v0.18.5 will be a release or skipping to .1?

i don't know what will happen in the future lol

so far no .1 planned

need +1 on 10457 10464 10466

ty plowsof

.merge+ 10516 10515

Added

no need to wait 1 week for doc fixes

my v0.18.5.0 chain sync is at 98%

ship it

Hi all, I was wondering where the monero C++ style guide can be found. Does monero projects use clang-format or something similar?

keep the same style as existing code

it depends on the file

How come there is no general style guide or defined clang-format? I'm specifically looking at the core monero project.

<ofrnxmr:xmr.mx> The guide is whatever the current file or section of code that youre editing follows

luigi1111: please tag v0.18.5.0

Is there any good issues for new comers to monero?

To specify more, C/C++ code related issues

<ofrnxmr:xmr.mx> Check the issues on the repo

<ofrnxmr:xmr.mx> github.com/monero-project/monero/issues

what's your skill level? for example monero-project/monero #8024 would require an updated version but that might be a bit too much work as a first issue

monero-project/monero #10513 is C/C++ issue, but it requires above beginner skill level

sech1: does the linked PR not solve it?

oh right, didn't see it

Hi everyone, just wanted to say hi. I'm new to monero and sent my first PR today, I hope to contribute more in the future :)

Hi. Welcome ^_^

Thabk you :D

done

testing from irssi

what platform do you guys use for this IRC chat? Libera or some other?

<ixr3:matrix.org> moneromooo: p2p encryption is added to the beta wishlist

<ixr3:matrix.org> seraphis-migration/monero #354

<ofrnxmr:xmr.mx> Probably the best place to test it is, imo, on stressnet

<jpk68:matrix.org> About clang-format: it would always be possible to have a file in the root of the repo with general codebase rules, and then specific stuff (i.e. two vs. four spaces of indentation, weird capitalization in RingCT code) in each directory. Somewhat like how CMake files are done

<jpk68:matrix.org> I'm guessing people wouldn't like that, though