---
# System prepended metadata

title: November 21 Call

---

# November 21 Call

Attendees (**add your name here**):
- Joao Santos
- Dominik Muhs
- Josh Reid
- Dean Pierce
- Mirko

Note taker: Joao

## Agenda
- Sync
- Sprint Review

## Summary
- We need to deploy the Groups to QA or production
    - It’s blocking the clients release
- Move the retro to Monday, before the kickoff call
    - Because we always do stuff on friday and weekend, so doing it on monday’s will give everyone a better notion of the current status of the sprint is.
- Joshua (CS)
    - There was an alert from opgenie about API latency
        - Ernani solved it
    - Tickets
        - Just 1 regarding a business enquiry
        - Works well with the slack integration
- Regarding the new resource
    - Using him to get started with API unit tests
    - When he finds somehting that us not documented (or not clear), he should document it and wrote a message on the API channel.
        - By commenting the codebase
        - We should have more public discussions on all of his findigns
        - That way everyone knows what is up
-   Demos
    -   Daniel (user dashboard)
        -   Call it Analyses Batches instead of Analyses Groups
        -   Or call 
    -   Dominik (MythX CLI)
-   Dominik discusses alternative issue format
    -   Indexed by source file rather than by issue
    -   A similar process is already being used on the dashboard to index the issues
    -   Should we do the reformat on the tools or on the API?
        -   Joao: On the API, so that not all clients need to make their own adapter. The API could still expose the
        -   Dominik: By adding an API parameter such as `?format=v2`
        -   We need a spec
-   Should we make the groupName into a label that is not unique?
    -   Revisit it later (create a ticket to track the discussion)
-   Issue regarding two different clients producing different analyses results
    -   Most likely the clients are generating different requets to Mythx API
    -   Mirko and Daniel will review it and if the issue format is different, will escalate to Dominik and/or Joran to check the backend.
- @joao   Inside a group, if the same files are imported muliple times, the issues will duplicated. So weshould an a warning saynig that that might happen.
- @joao make a ticket to make files with no errors to green and not the blue that is now being used for low severity
