---
# System prepended metadata

title: FY22 Q1 Weekly Sync Meeting Notes

---

# FY22 Q1 Weekly Sync Meeting Notes

[Project board](https://github.com/github/connected-enterprise/projects/1)

(newest notes on top)

## Monday, Oct 10, 2021
**Work in Progress**

* S4
    * GH/GH endpoint has real data returned using `GitHub::Connect::S4`
    * UI Download buttons working
    * Development environments working with Codespaces
    * Getting tests for UI download and endpoint changes
    * Determining when to display UI element [ADR](https://github.com/github/connected-enterprise/pull/289)
    * Performance Batch work: Service availability, SL docs ... 
* EMU
    * No updates yet from the customer, new code pushed by @lildude 5 days ago. 

**New Work**
* Onboarding Refactor
    



## Monday, Oct 4, 2021
**Work in Progress**

* S4
    * UI work is now hooked up to hydro to track number of clicks
        * Tested on review-labs
        * Hooking up S4 gem to actually pull information. 
        * When should the button be visible?
    * Dotcom endpoint + Gem install
        * changes on s4 repo and gh/gh in parallel
* Dormancy Users
    * Shipped last week
    * Release dates are still on track 
* EMU Sev 2 Issue ([#264](https://github.com/github/connected-enterprise/issues/264))
    * Fix rolled out last Wednesday
    * some users have not deduped but might be a corner case  

**New Work**
* Onboarding Improvements for GitHub Connect(@kellyarwine Presentation)
    * [Presentation Deck](https://docs.google.com/presentation/d/1LHPcHiyihGciPB4JdSS3C9jHNQD9arytJT4JxVgPgBY/edit?usp=sharing)
    * 

## Monday, Sep 27, 2021
**Work in Progress**

* S4 (target date: Oct 22nd)
    * https://github.com/github/connected-enterprise/issues/215 Shipped 🎉 
    * https://github.com/github/connected-enterprise/issues/216 @tbehling @deleonjavier
    * https://github.com/github/connected-enterprise/issues/205 @tjl2
* EMU Sev 2 Issue
    * @lildude & @electroniko pairing on a solution 
    * Estimated ship date: Oct 4th. 
    * Will rejoin the epic after 
* Dormancy numbers Discussion
    * Needs to be added in order to give context to MEC
    * Dormancy interval setting must be passed 
    * Shooting for GHES 3.3 release [hydro schema, GHES code changes]


## Monday, Sep 20, 2021
**Work in Progress**

* S4 (target date: Oct 22nd)
    - 3-4 batches in parallel
    - lildude: new batch for instrumentation (instrumentation for consumer and API services; send them to Datadog; dashboard + alerting)
    - Tim: UI: Button is displaying in enterprise and orgs settings areas; dropdown selects JSON/CSV.  Might need call to S4 to determine if data is present?
        - followup question: how is the relationship calculated between a logged in admin user, with enterprise admin rights, and the list of reported GHES "server IDs" they should download the CSV data for?  Does this relationship get established by Connect "enterprise installations"?
            - "owner ID" field is in S4, with "b" "u" prepended, Business/User (which is org)
            - https://github.com/github/connected-enterprise/issues/228 helps explain
    - @deleonjavier: GitHub monolith endpoint: will ship today/tomorrow, also "how to create gem"; and how to use that client
    - "excluded field list": Kelly will talk through MEC in a meeting Wed to establish a decison on whether to release it
        - Can search "GTM" (go to market?) customer list in our issues
        - Field filtering capability will need to be in the scope of current work

* First Responder: Connect: severity 2 support escalation
    - de-duping situation that isn't happen; eats up customer's licenses (license sync)
    - customer email addresses have a "plus alias"; need to detect in the code that does license sync to match what's in file vs accounts in dotcom
        - potentially use alternative logic to pull other email address?
    - Kelly: EMUs have launched, customers are adopting, more customers coming. Prioritization should be high because a customer is blocked; offered a temporary license that customer didn't want to use; that customer is disabling Connect
        - Bryan: the needed fix should be on dotcom side only (the data file from GHES already contains the needed alternative email address for the user)
        - @lildude + @electroniko are tackling it



## Monday, Sep 13, 2021
**Work in Progress**

* S4 (target date: Oct 22nd)
  - Epic #2 started https://github.com/github/connected-enterprise/issues/204
      - https://github.com/github/connected-enterprise/issues/215 @rubiojr
          - Barebones API server and will build out
      - https://github.com/github/connected-enterprise/issues/216 @deleonjavier @sridharavinash 
          - adding an endpoint 
      - https://github.com/github/connected-enterprise/issues/205 @tjl2 @electroniko 
          - prior art research
      - https://github.com/github/connected-enterprise/issues/255 @tbehling
          - Prerendering CSVs in S4
  - Week of the 20th we'll potentially be onboarding customers onto S4. 
  - @tbehling will spike on CSV Caching 
* S4 on GHE.IO
    * Creating a looker dashboard to be a guinea pig for the larger set of onboarded customers.
* First Responder
  - Enterprise2 breakage fixed and it unblocked that team.


## Monday, Aug 30, 2021
**Work in Progress**
* S4
  - ADRs (optimization and migration strategies) https://github.com/github/connected-enterprise/issues/238
      - Sergio, and possibly Avinash
  - Refine Go Consumer https://github.com/github/connected-enterprise/issues/218
      - Model refactoring
      - Adding additional needed fields (owner_id, ghes_usage_metrics)
  - CosmosDB Subscription and Orchestration https://github.com/github/connected-enterprise/issues/236
      - Entitlements completed
      - Tim and Hugo working it (out Monday)
      - Might need some clarity on work (what is the reason this work needs to happen? disaster recovery? etc)
      - Do we need additional CosmosDB hardening? Track what Octoshift is doing
  - Target date moved to 9/8, because of the three new batches added in-flight (#238, #236, details in #210)
      - Date may be adjusted due to outcome of #238

* Admin UI Epic
  - Probably at least a week before starting

* Bounty
  - Deploy completed, scorecard is green

* GHES 3.2 QA
  - Follow up with Hugo on https://github.com/github/enterprise-releases/issues/2706
  - Update: waiting on next GM to test fix, backport merged.

* Flaky Tests 2.0
  - Need update from Colin
  - Is this priority over S4? Bryan to clarify
  - KK: yes it is

## Monday, Aug 23, 2021
**Work in Progress**
* S4
  - Create backing datastore
  - Need Azure resource access/unblocking
      - Same instance/different table with Octoshift? @jspawar or @amory
      - Azure-specific work to be rolled into new batch
  - Portion that would have blocked next epic now completed
* Refine Go Consumer
  - Schema definition, planning how to get data back "up"
* Bounty
  - Change completed last week, deployed today
  - Needs validation, then will close
* 3.2 Release QA
  - Hugo to begin after completing Bounty validation
* Open Source
  - One more flow chart needed, then will close the spike. New date is 8/23

## Monday, Aug 16, 2021
**Work in Progress**
* S4 https://github.com/github/connected-enterprise/issues/212
   - Moda Scaffolding completed
   - Local consumer development has a clear path forward
   - Consumer Boilerplate is near the finish line
* Bounty https://github.com/github/connected-enterprise/issues/180
   - Task Breakdown 
   - PR for fix is in Draft Form
* Open Source https://github.com/github/connected-enterprise/issues/217
* Backup-Utils https://github.com/github/connected-enterprise/issues/208
  - Disney affected and was asked what their ideal scenario would. 
  - Could be a result of a misuse or misunderstanding of a configuration flag. 
  - Needs prioritization.
  - Kelly wants to talk to Disney before proposing a solution.

**Product** 
- Kelly is adding a sendoff meeting for Wednesday at 9am PT

## Monday, Aug 09, 2021 
* **Work in progress**
    * Work breakdown reformatting for customer metrics access project was discussed
* **Product**
    * 

## Monday, Aug 02, 2021 

* **How we work**
    * vanessa to schedule another call to talk about this
* **Work in progress**
    * GHAE Portal extension currently on-hold, awaiting GHAE bundle fixes
    * Ted to wrap up the Actions re-enablement today
    * security issue 
        * speak with Brent tomorrow
        * Javier hands it off to Ted and Hugo
    * We can start the customer server metrics initiative this week 🎉🎉🎉
* **Product**
    * Need some investigative work and estimates for [Data improvement issue](https://github.com/github/connected-enterprise/issues/172)
        * Let's wait until there is a natural stop to prioritize that
    * Colin will make the link change in metrics copy
    * Kelly is working on onboarding journey
* Others
    * we should talk about on-call support for new service

## Monday, Jul 26, 2021 
* **Work in progress**
    * Telemetry access: #191
        * Javier has research shared about how to make it work
    * Reenabling connect Actions toggle for GHAE:
        * Ted is unblocking dev process with his Codespaces
    * GHAE Portal Extension Validation: #77
        * Tim: issue with failing to deploy GHAE account
    * Fundamentals
        * Colin: Flaky tests are fixed #182
        * Application Security Scorecard #180
    * Manual test for usage metrics:
        * Tim: ready to merge
    * Research on forking into GHES/GHAE
        * Bryan: enable a flow to enable contributions with a GHAE/GHES instance and have them contribute back to dotcom #190
        * "fork into an instance"
        * previous feature in dotcom: "read only mirrors"; could maybe leverage?
        * there is a possible feasibility path
        * need to find who to ask about certain broader questions
        * Currently working with git systems team; getting a contact on the PR side
    * This week focus on fundamentals, wrapping up azure portal stuff, and if there is free-time, take on some potato tasks.
* **Product**
    * Customer access to metrics 
        * Javier [broke down work and gave estimates](https://github.com/github/connected-enterprise/issues/191#issuecomment-885304241)
        * Not sure if we are doing it yet; currently surfacing our concerns up to product LT
        * Can we make metrics opt-in by default and just focus on adoption?
            * Worry about backlash and sales team shares the same concern
            * Will need to get Legal's thumbsup and change terms
            * We don't want to risk customers' trust
        * Delivering value to customers
            * Value add for this first iteration: time-series data and aggregation across different instances
            * Giving customers access to data transmitted is for transparency also
            * Admin stats is only first iteration just to finish the feature and have something to put in front of customers
                * Customers want usage data on Actions and Codespaces
                * Premium Health Check report is also desired
                * :point_up_2: these valuable data can be layered on in future iteration

## Monday, Jul 19, 2021 
* **Updates on work in progress**
    * Admin-stats (@tjl2):
        * hydro schema approved
        * doing testing now in dev env
        * trying to get stats uploaded
        * Tim can see the admin-stats being sent over
        * all pieces ready to go
        * just tweaking at this point, no extra hands needed
    * Documentation (Colin)
    * Flaky tests: PR just waiting for approval (Colin)
    * User journey:
        * Hugo picking this up
        * Per @vanessyuenn, this is the highest priority
    * Reliability:
        * Sergio is working on this
    * Re-enable GitHub Connect Actions toggle for GHAE #170
        * @tbehling is working on this
    * StatusPage:
        * Kelly is going to let Javier team know when to launch.
        * Javier will deploy to dotcom but we'll let some other actor update GHAE manifest.
    * Access to Server Telemetry Data epic:
        * Hoping to get a "yes"/"no" is this feasible
        * Requirements:  Do we want to do this work?  Can we do this work?  Can we do it by the dealine?
        * Colin's feedback is to add in a hard date and not to do what we did before—"target date is 3.2 release".
        * Ted's feedback:  not enough hard requirements as of now; two suggestions:
            * What are the requirements?  What's the date for those requirements?
            * What's the date?  How do we hit that date?
        * @vanessyuenn feedback:  let's get these answers by the end of the week; what's the breakdown of work and efforts and then can we limit the scope if not going to hit deadline
* **Updates from Product**
    * Three pieces of work for the quarter:
        * Access to enterprise data:  we're talking about that this week
        * GitHub Connect data improvements: let's talk about this and define the work needed
        * New onboarding journey:  Kelly is going to start working on this one asap so that we can figure out what engineering is needed