---
# System prepended metadata

title: Meeting minutes (AMA-F meeting 3) (3rd October 2020)

---

# Meeting minutes (AMA-F meeting 3) (3rd October 2020)

1. Status check on developer environment
    * Milan couldn't try out aries (don't know which one he is refering ?) and indy-sdk
    

2. Status check on knowledge building
    * Milan, John is starting up
    * George will present on Tuesday, about DID, DIDComm, DID methods
    * Milan asked questions relating persistence of DIDDoc
    
3. John showed his workflow and how he manages a project
    * Architecture document
    * Repository README.md with project description and developer help (Environment variable documentation)
    * Tools used - Spinnacker, Kong gateway, Casbin for RBAC (Authorization), AWS DynamoDB, Keycloak (Authentication)
    * CI/CD - SonarQube, 
    * Deployment plan
    * Database data model
    * Swagger integration
    * PRD
    * Trello boards
    * Jira (Project manager)
    * React admin - 
    * Flow daigram using draw.io
    * They have promeatheaus for metrics
    * Design document
    * GitHub integrations
        1. CI ->
            * Docker registry used is Quay.io
        2. Static analysis (Sonarqube plugin in Jenkins)
        3. Sonarqube pulls the latest source code (using a particular user create in the github)
            * Gives a diff information
            * Code smells
            * Linting
            * Code quality badges in github (If sonarqube is public) (will be nice little addons for opensource)
            * Needs a client and server,
                1. Scanner (Jenkins hits sonarqube (it is written as stage in Jenkinsfile))
    * George have to deploy sonarqube in cluster and then John will help in configuration with the deployed Jenkins
    * Lal, asked John if sonarqube is useful in the context of Dart (Flutter)
    * Suggestion,
        1. Travis CI
        2. Basic linting
        3. CodeMagic
        4. Unit tests must be written in 
    * George suggested it might be bit of an overkill on an opensource project, unless you have funding
    * John suggested that since it is a small team, developers can run sonarqube locally
    * Lal, suggested George to decide whether to go ahead with SonarQube
    * Lal, asked George to copy developer workflow, to docs repository, then all contributors can suggest newer changes
4. Lal talked about requirements document (Work packages, Activities), Codemagic subscription
    * Lal ask about requirement handling to John, GitHub issues,
    * Confluence account
    * Zoho (iGrant.io current tool)