orta
commented
6 years ago Team nav is basically one of my side projects at Artsy, so there's not really much process and definitely no product roadmap 🍡
That said, we have monthly meetings with the workspace team called the people tech working group (which is tomorrow, and I can put you on) where they ask about things that they need and I see if I can find time that month to add/amend them.
The v3 section is so that I can enjoy working in team nav, because it's a bit of a chore without typescript or relay, or JSX in v2. I moved over the settings from Peril's site and re-created the process in there. If I need to make more ad-hoc pages for Artsy, I expect to build more in there.
Personally though, I'm not into re-writes - it's clunky but it works right now. That said, I think team-nav is a place where we can explore the omakase stack tooling once it's ready ( /cc @damassi ) and I'd be open to re-implementing it then so that we can test it from another angle
dblandin
We have the beginning of a V3 version for Team Navigator: https://github.com/artsy/team-navigator/pull/119. We recently used that V3 space for a Buy Now artworks dashboard: https://github.com/artsy/team-navigator/pull/123.
It's a bit unclear whether new development towards Team Navigator should continue in the existing codebase or if there is a roadmap for migrating towards a V3 version.
Is there an incremental approach to take? If some goals are to use create-react-app and TypeScript, maybe we can convert the existing codebase over incrementally and/or or tackle each migration separately?
What's the best way to discuss and decide on a product roadmap?