Re: The case for a Commons component

2021-05-03 Thread Ralph Goers
I apologize. I started another thread regarding the vote before seeing this. Maybe that will get more attention? Ralph > On May 2, 2021, at 3:59 PM, Gilles Sadowski wrote: > > Hi. > >> [... Discussion about GA data-structures...] > > I'd suggest that we finalize the [Vote] before getting int

[Discuss][Vote] Create repository for "machine learning" algorithms.

2021-05-03 Thread Ralph Goers
How long is this vote going to stay open? This vote has already been open for 12 days. To this point we have Sebb - no actual vote but somewhere between 0 and -1. (Binding) Ralph - +0 (Binding) Emmanuel: -1 (Binding) Paul King: +1 (Non-Binding) Gilles: + 1 (Binding) Arijit: +1 (Non-Binding) So

Re: [all] OSS-Fuzz Issue Publication

2021-05-03 Thread Fabian Meumertzheim
Hi, The behavior you are observing has only become the standard somewhat recently [1], which is also why I had decided to point it out before we performed the integration [2]. Let me first confirm the facts: It is correct that OSS-Fuzz will automatically open the Monorail bugs to the public rough

Re: [all] OSS-Fuzz Issue Publication

2021-05-03 Thread Gary Gregory
Voting takes three days or less if we decide we need an emergency release for a security issue for example. In reality, it can take weeks for a release manager to volunteer for a given component, review code, PRs, Jiras, an so on, before going through all the hoops to create a release candidate and

Re: [Vote] Create repository for "machine learning" algorithms.

2021-05-03 Thread Avijit Basak
Hi Gilles Thanks for voting on behalf of me. Regards --Avijit Basak On Mon, 3 May 2021 at 18:14, Gilles Sadowski wrote: > Recording a vote in the proper thread on behalf of Avijit Basak (who > inadequately posted his vote in two other threads). > > Le mer. 21 avr. 2021 à 19:05, Gilles S

[all] OSS-Fuzz Issue Publication

2021-05-03 Thread Stefan Bodewig
Hi (Fabian) by now we've resolved the first issues detected by ClusterFuzz (and I forgot to credit it OSS Fuzz in Compress, my bad). What we observed is that the issues became public automatically once the patch fixing the issue was merged into master and ClusterFuzz reran the test. In the case of

Re: The case for a Commons component

2021-05-03 Thread Gilles Sadowski
Hello. Le lun. 3 mai 2021 à 08:53, Avijit Basak a écrit : > > Hi > > I would like to vote for *commons-ml*. Wrong thread, again. Sorry for the nit-picking, but whenever a vote is requested, it is often the basis of an official decision that must be traceable by other parties, such as

Re: [Vote] Create repository for "machine learning" algorithms.

2021-05-03 Thread Gilles Sadowski
Recording a vote in the proper thread on behalf of Avijit Basak (who inadequately posted his vote in two other threads). Le mer. 21 avr. 2021 à 19:05, Gilles Sadowski a écrit : > > [...] > > Name of component: "Commons Machine Learning" > Name of "git" repository: "commons-machinelearning" > Top-