-
Notifications
You must be signed in to change notification settings - Fork 75
OSS-CRS TI Sandbox Application #559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Jeff Diecks <55294502+GeauxJD@users.noreply.github.com>
|
Looking forward to seeing this accepted as a sandbox application |
marcelamelara
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm supportive of OSS-CRS joining as a sandbox project! Very excited to see how this project continues to grow.
| - **Resource management**: YAML-based configuration for CPU cores, memory limits, LLM budgets | ||
| - **LiteLLM integration**: Automated proxy deployment for LLM access control | ||
|
|
||
| ### Roadmap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocker, but I think it'd be helpful to get a sense for when the project plans to start/complete these different roadmap milestones.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The group presented an update on the roadmap in the most recent Cyber Reasoning Systems SIG meeting. Slides are here https://docs.google.com/presentation/d/1R9XAF6VOVimdlXL346CnNrMkOzJFVyFhJF9lrYtHnZI/edit?slide=id.g3b67cb90a0c_0_0#slide=id.g3b67cb90a0c_0_0
steiza
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Minor question about one of the links.
gkunz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very supportive of this.
| ## List of project maintainers (alphabetic order) | ||
|
|
||
| * Andrew Chin, Georgia Institute of Technology, @azchin | ||
| * Cen Zhang, Georgia Institute of Technology, @occia | ||
| * Dongkwan Kim, Georgia Institute of Technology, @0xdkay | ||
| * Fabian Fleischer, Georgia Institute of Technology, @fab1ano | ||
| * Hanqing Zhao, Georgia Institute of Technology, @hq1995 | ||
| * Jiho Kim, Georgia Institute of Technology, @jhkimx2 | ||
| * Taesoo Kim, Georgia Institute of Technology & Microsoft, @tsgates | ||
| * Younggi Park, Independent Researcher, @grill66 | ||
| * Youngjoon Kim, Georgia Institute of Technology, @acorn421 | ||
| * Yu-Fu Fu, Georgia Institute of Technology, @fuyu0425 | ||
|
|
||
| Note: Maintainers may be updated in the future (some can become inactive or other AIxCC team members may join). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our criteria is: "Projects must have a minimum of three maintainers with a minimum of two different organization affiliations." This really looks borderline...
lehors
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm concerned that about all of the maintainers seem to be students who will likely move on to other projects and leave this unattended.
+1, but I think given the convergence strategy discussed at the TAC meeting it seems like we will likely be archiving some of them and maintainers swarm onto one/two approaches? |
lehors
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approve based on the stated expectation (communicated on the TAC call) that maintainers from other organizations are planning to join the project.
OSS-CRS (Open Source Software Cyber Reasoning System) provides a standardized infrastructure for building, running, and evaluating Cyber Reasoning Systems (CRS) that perform automated vulnerability discovery and remediation in open source software.
Features include: