Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Date
Attendees
Discussion items
Swimlanes
- Require/Webpack: likely through 06/2018
- Asset Pipeline: ditto
- Paragon as design system: 2 mo
- Bootstrap
- Tasks:
- Fix the uses_bootstrap mechanism
- Fix the wrapper template (header/footer and wrapper)
- Deliverables:
- Enumeration of all pages, how they're styled, how to prioritize conversion
- Kill pattern library
- Introduce new Bootstrap-only theming system
- Kill v1 sass
- Hawthorn theming docs
- TBD: enterprise logistration work
Process
- Greenfield vs. sandbox
- Both – we don't need to commit to a specific percentage split
- Planning stages of new stuff > work on old stuff. Stop the bleeding
- But we still need to work on the old stuff, to give us a clearer path to the new stuff
- Is our team's process working?
- Non-process process works day-to-day
- We need some way to regularly check in on the status of our long-running projects
- Is that what this meeting is? (We should make sure to check in about our projects)
- Core/feature team engagement model
- Predictable feature delivery
- Crucial to feature teams, but hard to guarantee for Core work
- If pulling in someone from Core, can a feature team commit to unpredictability for a while?
- Should feature teams absorb infra work at all?
- "Consulting" model maybe more effective
Action Items
- Dave Ormsbee: set up meeting with Enterprise to talk tech deliverables
- Bring this up at CELT