Skip to content
This repository has been archived by the owner on Nov 15, 2019. It is now read-only.

ParSys Sprint G Goal #253

Closed
hmitsch opened this issue Mar 29, 2018 · 0 comments
Closed

ParSys Sprint G Goal #253

hmitsch opened this issue Mar 29, 2018 · 0 comments

Comments

@hmitsch
Copy link
Contributor

hmitsch commented Mar 29, 2018

Sprint Goal

Following the Sprint F Retrospective, we experiment with a more Kanban-oriented way of mapping out the next 2 weeks. This is the prioritization we landed on at the end of our Sprint Planning meeting.
image.png

Preparation for the planning meeting (aka former Sprint Goal)

Be a good Open Innovation citizen

  • (IAM) Common Voice: Integration support
  • (Infrastructure) Support SuMo Strategic Research: Hand off secure and redacted Kitsune DB for Tableau analysis
  • (OI Products) FOSS Heartbeat: Make devtools repo parseable (multi-file support) and clarify next steps
  • (OI Products) Explore SUMO Playstore tool: Can we build something quick, scrappy, non-sustainable with effort measured in days, not weeks/months?
  • (Contributor PRs) Keep the pipe clean, review & merge in a timely manner
  • (OI Products) Coral Meeting

(IAM) Firefox Accounts in Mozilla IAM

  • Prepare launch comms
  • enable fxa on mozillians staging for login and account verification
    • Mozillians shows "none" as login method: adding new IDPs is fairly easy, its a dictionary with security levels. let's tackle it in the next sprint

(IAM) OIDC Django Library

  • Support XHR requests in the Token Refresh middleware
  • Support extra_params like connection type in Authentication Request class

(OI Products) Blind Code Review Pilot

  • Submit Q2 project charter
  • tl;dr newsletter posting
  • Transition repo to a mozilla/parsys Github org

(CoSS) Launch a Pilot Event on Splash

(IAM) Stop starting, and start finishing / Operational improvements

(IAM) LDAP publisher / Auth0 publisher

  • (Staging-only) LDAP groups are exposed via the Person API
  • (Staging-only) auth0 creates new users in Mozilla IAM
    Info: this enables "staff data available in Mozillians"

(IAM) Change User Profile Schema (Design)

(IAM) Make Kubernetes Infrastructure real

  • Tech Alignment (or separate meeting): What's the CI/CD process and release process?
  • Moderator is migrated

[XL] (IAM) Mozillians.org Repositioning: UX Research

  • Plan
  • Acceptance criteria TBD

NLX.next

Upgrade Project Charters for April Operations Review

  • CoSS
  • Blind Code Reviews
  • IAM

Discourse

  • Do we need more test automation? Can we continue to "just press the PROD deploy button" whenever we feel like it? (Ask Viorela and Leo)

Backlogged

[L] (IAM) Resilient Operations: Tracing in the IAM Stack

  • Logs from Mozillians.org and CIS are in the same place

[L] (IAM) Individual group memberships expiry dates

  • UX design for setting the expiry date
  • As an access group curator, I can set an individual expiry date

(IAM) NLX Usertesting.com Analysis

  • Insights are captured in Github issues, estimated and prioritized

(IAM) NLX deployment automation

  • NLX can be deployed without manual intervention

GCP Reference Arch for Federated Access

  • Currently blocked: Credentials missing (GCP account creation)

  • Meeting with Google engineers next week

  • (Operations) Runbook: its complete for Mozillians.org, still requires copy & paste for the other ParSys properties

  • OSSN: Container hosting for GSoC

  • Discourse: As a Staff member I want to login using LDAP and get email notifications on a separate email address in order to separate inboxes for paid work and community work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant