Quick question @limited-student-10747. What type of discussions did you plan on having here? Would talking about specific project architectures not just go into their relevant channels? i.e. architecture around CLI would be discussed in proj-cli, etc.

It's a good question...

Please don't mind I will answer a bit because I thought about this before actually... • in the SDK, we expect to deal quite a lot with needs from downstream applications, it's an important part of the interfaces we design and focus of reviews etc • basically, architecture / code design always happens at multiple levels of abstraction, and some go through multiple repos • the

/clear

thread above spans multiple repos

I agree, but just for some context, I think we're trying to reduce the number of duplicated channels that cause confusion about where someone should post a message. I think it's OK to have this channel for cross-cutting concerns though

It's definitely not a big deal just my suggestion would be to have some guidance on what goes into this channel because it is pretty broad! Thanks for discussing!

May I ask what your current priorities are? So I can focus my contributions to fit your scope and actual needs.

Hi @refined-secretary-75241, have you done any PRs yet? If not, typically working on the things labeled as "good-first-issue" are a good way to familiarize with the codebase

@limited-student-10747 yes I've submitted two PRs and an issue after receiving guidance from @quiet-night-61895 on a security advisory. Waiting for reviewer feedback. I'll shift to the other open PRs to see where I can provide support.

OK, great! In terms of priorities, it's a great question, but generally we like people to work on things that they can get passionate about. So if you use OpenHands and find any issues that bother you and you'd like to fix then discussing them and working on them can be great.

Got it, diving into the PRs to see what aligns with my passion. I'll lend a hand where I have experience

Nelson, in addition, may I suggest that the focus we absolutely love to see and might be easier to get into, is on the SDK and CLI codebases, though depending on the case of course it's Web too. To elaborate: we have a bit of chaos right now, where the "OpenHands" repo contains multiple applications and versions: it's supposed to be actually "OpenHands-Web" that is, an app-server or two, and web frontend; it currently has both V0 and V1 codebases, and that gets a little difficult to follow. For example, I'm looking just now at this PR: fix(security): add sleep to container wait loop and I think it's on V0. V0 is a legacy version that we will clean up from the codebase. 🤔 The equivalent code should be for V1, in the OpenHands Agent SDK: https://github.com/OpenHands/software-agent-sdk

Good direction. Front ends are not my strength so I'll focus on the sdk and cli. I'm looking at the sdk #1828, #1957, and #2089 as starting points. I'll communicate through the appropriate channels as to not flood this one. I'm open to dms on these PRs if you have guidance or knowledge to share