Versions Compared

Old Version 3

changes.mady.by.user Matt Tuchfarber

Saved on

compared with

New Version Current

changes.mady.by.user David Joy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeItemWhoNotes
10 minStatusEveryone
30 minWhy FedX WorksEveryoneFolks across engineering frequently refer to FedX as an example of a group that functions really well – some other groups even seek to emulate us! Together, let's identify the things that make us work, both to share with the rest of the organization, and to help keep FedX going. I'd like all of us (that means you!) to present our findings at the eng all hands next Friday.
6 minsGatsbyJSAlasdair Swan (Deactivated)The Discovery project will be using GatsbyJS to deliver Isomorphic JS. I'm going to present on what I've learned so far.
5 minsJWT Cookies?Matt asking questions, other smarter people answering

It sounds like JWT Cookies are the future for edX. My question is what are they and will they be the solution for:

  • Determining user information in the client (probably?)
  • Determining is a user has a valid cookie to a backend (probably not?)

Notes

Should we use this Vue thing?

  • Team feels generally not wild about it
  • Historically edX hasn't been good at addressing tech debt
  • Educator team would be responsible for rewriting

GatsbyJS

  • https://github.com/edx/prospectus
  • RIP Drupal!!!!
  • Gatsby starter
  • Built with JS – but works without JS
  • For beta, data is in JSON, but in the future it will make api calls

JWT Cookies

  • Journals frontend needs to know whether a user is logged in, and who the user is
  • JWT cookies are the future
  • They will have user information in the cookie etc.
  • If we have the cookie, and its expiration date hasn't passed, then it is valid
  • But what if you've invalidated the cookie?
    • We need a roundtrip

Operating Principles

  • How do we track long-term progress?
  • Cross-functional communication
  • The stuff that used to be core isn't really owned anymore
  • Knowledge sharing/cross pollination
  • Do any actual problems get solved?
  • "Group therapy" for frontend
  • Is this a guild?
  • History:
    • 2015: Dennis, Andy, Alasdair: ux pattern library
    • Became more generic eventually
    • "FedX team" existed for a while (handling core-type upgrade stuff) got spun down by the last reorg
    • Modernization continued, oeps, etc.
    • Core FED existed starting fall 2017, spun down by reorg
  • "Help without meddling" – guidance
  • "Fix things on your own" – don't do it for people, help them learn on their
  • Being underresourced creates a sense of community
  • We are aligned around a problem that we don't think is being solved adequately
  • There is a clear vision for the future for the frontend – less clear for the backend
  • Treats, stickers, fun, events, etc – contribute to the sense of community
  • Celebrating success
  • Public office hours, casual, easy for anyone to show up
  • Easy to ramp up, welcoming, feel like you're contributing
  • Easy to make small contributions
  • Team really good at mentoring
  • Internal communication: alignment with autonomy
    • eslint config helps to build consistency