Bug#908678: Update on the security-tracker git discussion

[Salvatore Bonaccorso <carnil@debian.org>]

Hi,

On Mon, Jun 24, 2019 at 01:57:36PM +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Sun, Jun 09, 2019 at 01:48:58PM +0200, Salvatore Bonaccorso wrote:
> > On Sat, Jun 08, 2019 at 06:29:24PM +0200, Salvatore Bonaccorso wrote:
> > > Notes on possible CVE/list splits
> > > ---------------------------------
> > [...]
> > 
> > After a face-to-face conversation with Daniel, Daniel suggested to
> > create a priority list out of that, we will followup with that to that
> > (ideally as gitlab task-list) here with a link once we have made our
> > minds on it.
> 
> The plan was initially to do that in that week. Due to some other
> issues (Debian related, and other) this was not possible. The plan
> still holds to prioritize these tasks so that people wanting to help
> contribute have something to tackle.

So I'm starting to track those here be better/more easily track work
on those:
https://salsa.debian.org/security-tracker-team/security-tracker-service/issues/1
(but they need to reshuffle an consolidate the items). Basically
before the switch the two major topics (the security-tracker code base
itself) and tools involved in the workflow for triaging/updating CVEs
need to be adapted to a split repo situation, which makes many of the
items go into the first group anyway, but not all.

So slow still work in progress.

On personal note, it would be nice to have some dedicated time for
this only, but ...

Regards,
Salvatore

p.s.: Question is if we should do a split as well for the other types of
      files which are supported (DSA, TDSA, ...) while at it.