Cédric Bonhomme

For the graphical interface I have something like this in mind. Related vulnerabilities view, almost no change:  The new view for the comments/bundles:  It's just a draft.

yep, indeed it's better.

Should the admin of the platform review the comments before they get published ?

The last version of the JSON schema is available [here](https://github.com/cve-search/vulnerability-lookup/blob/41-comments-bundle/website/web/static/schemas/CIRCL/Security_Advisory_Comment.json#L63C8-L70), @adulau. There are minor changes to what you proposed. But maybe we need some more updates. Some suggestions/ideas/questions: - should...

> Can you document how to upgrade the bundled-in vulnogram code? It will make maintenance long term a lot easier I think. > > (and sorry if it's already there...

OK, i understand the fact that it must stays a single-user project. Concerning the way to deal with vulnerability edition I've checked vulnogram. It seems nice. I must take a...

I've started to implement a standard system of sessions. Users are able to Log In as normal users or as admin. As discussed this is optional and not used by...

I'll try to document everything here: https://vulnerability-lookup.readthedocs.io/en/latest/architecture.html#blueprints WIP WIP...

About orgs, to be honest it's something I've kept in my mind because we briefly talked about it while eating... I am totally fine to not implement Organization. And you...

OK, cool ! I do my best to reach the feature of creating a vuln with few code ;-) In the blueprint dedicated to the existing API, I will certainly...