Hey <@UC9UK6BC1>, Will try and get you a review to...
# general
t
Hey @Evgeny Sidorov, Will try and get you a review today!
e
Thanks for the review, I'll make all the changes and get back.
The only thing I'd like to keep is column names like
capname
if it's possible, because they match the tokens AppArmor uses in it's logs, so I think it would be better to keep them consistent with AppArmor
t
That's fine. Would you mind leaving a note about that on the PR? Also it might help if you add more description information for the column, just so it's known why that was labeled as such perhaps?
e
Sure, I'll add a comment on that and add some links to linux kernel sources. I'm planning to fix all the issues by Monday
👍 1
I'm sorry I have a business trip, I'm working on the fixes, but they'll be ready in probably two weeks. Could you please take a look at my comments in the PR?
👍 1
Hello, I pushed a new bunch of changes and fixes according to the review comments. Could you please take a look? It also seems to be an issue with CI as code audit and freebsd build are still in pending state.
t
Sure, we'll take a look, unfortunately we're still in Lockdown right now, so it might be a while longer before things happen 😞
👍 1
e
Can you tell a few words about the overall development process? I'm trying to find out what time is the best to submit PRs
t
Ah, yeah sorry, this is just unfortunate timing really. Typically we try to stay on top of PRs, but considering the repo is on lock down temporarily we're not spending much time on reviews, as we're not currently accepting PRs, but will be again hopefully soon. @fmanco might have a better idea what the timeline looks like for when PRs will start landing again, sorry about that!
f
Hey @Evgeny Sidorov the current plan is to start accepting PRs again after the 19th of November. You can read the announcement at https://osquery.io/blog/osquery-lockdown.
👍 2