You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We didn't get to discuss this too much during this morning's meeting (we had a lot to talk about on CI and NVD challenges, particularly around a bug @anthonyharrison found in our API2 code and ongoing availability issues), so I'm going to just open a thread here. We might resume the discussion in our May meeting.
This is a place to brainstorm new cve-bin-tool ideas or revisit ones that we haven't worked on yet. They don't have to be good ideas or even feasible ideas yet, it's mostly a chance to discuss. Some of these might be viable for our summer release (no date yet but usually partway through the GSoC term), some may be longer-term ideas.
Some things that are already on our radar (but you can discuss further below):
@b31ngd3v has got some initial data export code already merged in main and an open pull request to add signing feat: add support for pgp signing (#2577) #2882 (signing was requested by the folk who'll be hosting the mirrors -- they just want to be able to prove that they mirrored what we have exactly)
We know we're pushing up on the deadlines for when NVD is going to turn off the "legacy" systems (September... ish?)
All the gsoc projects. We're not allowed to give any hints that might indicate what projects have been ranked so assume for now that everything is in scope and we'll wait for the Google announcement on May 4 before we go into plans around those.
One exception: we had a few ideas that got 0 applicants, so some of those might get released into the bug pool a bit early while the hackathon folk are looking for self-contained issues to work on.
So... what do you think might be interesting to do with cve-bin-tool? What bugs you right now?
The text was updated successfully, but these errors were encountered:
terriko
added
the
discussion
Discussion thread or meeting minutes that may not have any trivially fixable code issues associated
label
Apr 26, 2023
We're about due for a new annual discussion on this, so I'm going to go ahead and close this older thread and a new one will likely pop up in conjunction with a monthly meeting!
We didn't get to discuss this too much during this morning's meeting (we had a lot to talk about on CI and NVD challenges, particularly around a bug @anthonyharrison found in our API2 code and ongoing availability issues), so I'm going to just open a thread here. We might resume the discussion in our May meeting.
This is a place to brainstorm new cve-bin-tool ideas or revisit ones that we haven't worked on yet. They don't have to be good ideas or even feasible ideas yet, it's mostly a chance to discuss. Some of these might be viable for our summer release (no date yet but usually partway through the GSoC term), some may be longer-term ideas.
Some things that are already on our radar (but you can discuss further below):
So... what do you think might be interesting to do with cve-bin-tool? What bugs you right now?
The text was updated successfully, but these errors were encountered: