POh yeah right let's get this nailed out.
Pso for codeowners, currently it's me for everything unless someone else specialises in a particular area.
Pso that is:
- @Deleted User for maths and silktouch
- @thomasmiz for input
- me for everything else
Pare we ok with that? obviously for 3.0 kai will be codeowner of all of silktouch except the scraper and CLI (as that's essentially what buildtools is which is my area atm)
Pthat'd be (will update this message as we discuss)
Pdid we want more codeowner discrimination? e.g. did we want to have bindings codeowners as well?
Por is that good as is
Pi personally want to make kai codeowner of tests as he's the driving force behind silk.net testing
DI'm happy to review any tests, but I think the project owner should be the test owner.
Who is windowing? I definetly want to make the browser integration, and would be owner of that then. Not yet sure how much I will help with the desktop versions. Right now I plan on making the WPF/Winforms/MAUI/Avalonia integrations as well, but there we will also see.
I do think we should make owners for the native libs too. I know we don't provide support for any, but we should have someone responsible for each lib that tests whether things are working and verifies when a user says they are not. I'd be happy to be that for Vulkan, for example.
Who is windowing? I definetly want to make the browser integration, and would be owner of that then. Not yet sure how much I will help with the desktop versions. Right now I plan on making the WPF/Winforms/MAUI/Avalonia integrations as well, but there we will also see.
I do think we should make owners for the native libs too. I know we don't provide support for any, but we should have someone responsible for each lib that tests whether things are working and verifies when a user says they are not. I'd be happy to be that for Vulkan, for example.
Pi personally want to do WPF and Winforms because i've had a good idea on how to do it for a while.
same for MAUI (there's an OpenGLView type we can piggyback off and use external memory extensions to do the rest), but I don't think I can champion that in addition to the other two. so you can be owner of that if you'd like.
for avalonia i have no strong thoughts or opinions, so you can be owner of that too.
for blazor you can definitely be owner of that if we end up doing that.
same for MAUI (there's an OpenGLView type we can piggyback off and use external memory extensions to do the rest), but I don't think I can champion that in addition to the other two. so you can be owner of that if you'd like.
for avalonia i have no strong thoughts or opinions, so you can be owner of that too.
for blazor you can definitely be owner of that if we end up doing that.
DThat's not an if, just a when 
Pif it's a when it'd be a very distant when, i doubt we have time for 3.0 initial release 
PWho is windowing?no clue
Not yet sure how much I will help with the desktop versionsi think i'm on windowing again, which is fine. the mobile ones were probably always going to be me seeing as i have android and ios dev licenses. does this much scope coverage constitute me being codeowner?
Pwe should have someone responsible for each lib that tests whether things are working and verifies when a user says they are notagree
i'd like to nominate thomas for opengl, as he's had the most hands-on experience with silk.net.opengl out of all of us here.
yep, you can do vulkan as well.
i'm happy to be openxr.
the others, no idea.
Pdo examples need codeowners too?
DNah its probably fine
DWell... Do we have no one that knows OpenCL or DX or like any of the others?
Pnot really, or at least not to the extent that we're familiar with the other graphics apis.
Pi can probably be a good enough gearhead in maintaining the binding to DX but from an actual usage standpoint i won't be as useful
Pthat being said i have written lab applications for both opencl and dx which I have used in the past to verify the bindings work
Poh cool you can pin in threads too
TThe OpenGL bindings for me?
PPoh yeah bots don't work in here lol
Pi'd like to nominate thomas for opengl, as he's had the most hands-on experience with silk.net.opengl out of all of us here.
TAlright, what would I do in OpenGL?
THaven't touched gl for quite a while tho
Pyou'd mainly just be responsible for making sure the bindings work and helping users out if they're experiencing odd behaviour or find a bug.
Pfrom the generation perspective, i've got you covered (which is the majority of the work) so beyond that it'd just be suggesting things you want added to the generator or finding other ways to improve your set of bindings
Pyou'd basically just be the opengl "advocate"
Dyeah, by extend also just knowing OpenGL and saying if something conflicts with the way OpenGL works
Dlike I've been doing for Vulkan for some time
TSounds good, so I can decide overloads for gl functions?
Ppretty much, obviously that also conflicts with kai's area (on the overloads front) but you'll be responsible for deciding which ones to turn on 
TOkay
P@Maintainer we should revisit this
KDo you mean update 2.x or for 3.0?
P3.0 as above
Pbump to keep the thread alive
Kbump once more
PI mean, you guys need to decide then we can stop bumping haha
KSet it to 1w now, and will have a think ofc
Li call dibs on the opengl imgui controller
PXD
Pdoesn't even exist yet for 3.0 haha
Lyet