JC 12:02:04 UTC
Hi everyone, for today's meeting I would like to propose a change in the way we vote things. I believe, voting on the meeting is problematic as it assumes everyone is on the call, also delays decisions to the meeting which sometimes need to be addressed before the meeting. What I propose is that discussion can happen in the meeting but voting should happen over a GitHub issue for a week (so everyone can catch up) an then do simple majority.
Juan Pablo Tosso 12:04:35 UTC
Also I think we should release a RC2 because of the plugins api
JC 12:10:30 UTC
Yeah, we closed al tickets labeled as v3 as of now and thanks to @Matteo Pace we have a promising list of exceptions in ftw which means that we are sooo close to the final v3.0. I would wait for a release in go-ftw and fix the issue with host in coraza to release 3.0.0-rc.2 if that makes sense.
Juan Pablo Tosso 12:11:15 UTC
@fzipitria any idea if the fix is coming soon?
↳ JC 12:11:42 UTC
I think the fix is in place we just need a release cc @Matteo Pace
↳ Matteo Pace 12:12:09 UTC
Yep, just saw that also Felipe approved it. yay coreruleset/go-ftw#132
JC 12:11:25 UTC
I think plugins API was the last change API wise.
Juan Pablo Tosso 12:12:15 UTC
rc2 will probably be the last rc, right?
JC 12:12:30 UTC
I hope so.
Juan Pablo Tosso 12:15:43 UTC
regarding the default config, we should add commented response body processing rules and remove rules we don’t support, like: 200003, 200004, 200005
↳ JC 12:16:08 UTC
Please do create an issue for this.
JC 12:16:38 UTC
Related our branch strategy in the line of v3 I also wanted to discuss the branch naming. Right now we have v3/dev but soon we will move a trunk/master/main branch. I would like to call for a vote to see what branch name we should adopt as there is no consensus on it. I will create an issue on this but just wanted to highlight this here.
JC 12:46:48 UTC
Any other topic people would like to highlight?
fzipitria 12:58:06 UTC
Have a good time off! @JC