Discuss here on how to adopt new technology standards w/ examples
View the Current Standards.
Depending on the impact of the technology on production or team productivity, we can have:
- small to no impact
- substantial impact
- try it, ideally on a small portion of the code base
- do a knowledge sharing to showcase the technology in the TES ecosystem
- create a new issue
- be sure to include the technology name clearly in the issue title
- follow the issue template as closely as is reasonable
- invite team members to discuss!
The purpose of this knowledge sharing is to showcase the technology and eventually get people on board
- no formal rules, but modest consensus for adoption is the goal
- close issue when consensus is reached
- label issue with
standard
orrejected
tag - if this replaces a previous technology, label the previous issue as
deprecated
If you adopt the new technology in your project, please link back the issue so others can see how the migration has been done.
The purpose of this knowledge sharing is to showcase the technology in the TES ecosystem
Aspirationally, viewing closed issues labelled standard
should give us a reasonably accurate view of our stack.
When there is no general consensus on a technology (e.g. request library), we will vote and, after 2 weeks, the technology will become a new standard
When a new standard is adopted a few actions should take place:
- 5-minute knowledge sharing on the new technology
- send an email to all project parents to let them know of the new standard
- add this information to the engineering git book
- add the technology to the standards document