---
# System prepended metadata

title: december delivery plan

---

# december delivery plan

1. using svn and gitlab repository access (not yet granted) and other tribal knowledge sources: compile a comprehensive, living list of omantel applications with metadata for each application which includes as much of the following information as we are able to ascertain:
   - group name
   - name
   - category
   - description
   - programming languages (list)
   - dependencies (list)
   - repository uris (list)
   - package uris (list)
   - environments (list)
   - contributors (list)
   - itbr identifiers (list)
   - clickup identifiers (list)
1. publish the living application list internally and securely, to allow others to contribute missing applications or application metadata. most likely the list will take the form of a new repository in omantel gitlab that contains application definitions in json or yaml format with a new file for each identified application and its metadata. In this way we can:
   - track changes to the list
   - automate discovery of applications with machine-readable data-sources (like gitlab and svn)
   - automate list inclusion, additions and updates
   - build a gitlab pages dashboard that provides transparency and visibility on the list state and changes
1. in collaboration with yaqoub: assess each application according to:
   - unified repo inclusion
   - nightly build existence
   - nightly build health
   - sonarqube integration
   - sonarqube technical scores
      - code coverage score
      - bug / issue count
      - vulnerability count
      - duplications
   - in-house vulnerability checks. ie: 
      - secrets in source
      - long-lived secrets
      - credential/api-tokens replaced with auto expiring/renewing certificate paths
1. in collaboration with younis and others: prioritise the application list for progression through maturity stages. including: 
   - devise a mechanism for prioritisation
   - apply prioritisation rankings to the list order
1. create a fast-track shortlist of applications for immediate attention based on highest prioritisation scores
1. create clickup tasks for each shortlisted fast-track application and subtasks representing the areas identified by the scoring workflow as requiring improvement
1. communicate to the contributors of the shortlisted applications that their application has been fast-tracked for score improvements and that their assistance and cooperation is required for improvement implementation
1. In collaboration with aamir: schedule workshops with contributors to assist with each stage of score improvement. these workshops will most likely overflow into january and beyond as we progress through and add applications to the working shortlist.
