Page Comparison

...

We also made some decisions around the shape of the radar and the next steps in the process.

Approaches

1. Combine

   1. Combine listing of tools into

   description of

   1. the single 'technique' that they support.

   2. Combine or exclude blips that only a small percentage of engineers need to know about. For example, engineers are consumers of all the coverage and linting tools. They don't need to know about each one we use and don't use. They can be listed within a description, if needed.

   3. Combine blips where one is an important subset of the other, or a sub-technology integral to the adoption of the other.

2. Remove

   1. Remove blips that are obvious and can be taken for granted. (eg Django).

   2. Remove blips that are not used in the platform at all right now. If the idea is a consideration for the future, have it first be prototyped with a provisional OEP. Exception: If it's a commonly asked question of our opinion on it and we've made a decision against it, consider including it.

3. Move

   1. Move blips that are abstracted away by cookie-cutters or Open edX APIs (since those choices are made for developers) to the 2nd tier Radar.

   2. Move blips that developers need not know about within their first 30 days to the 2nd tier Radar.

Decisions

• Tiers of Radars.

  • 1st tier includes information that we expect developers will want to know within 1st 30 days.

  • 2nd tier includes additional decisions to learn post-30 days.

  • 3rd tier includes edX.org-specific decisions.

• Rings. Align name of rings with status of OEPs. We want to update OEP-1 to remove the "Final" state and clarify the difference between Provisional and Accepted. We also want to add a description for the "Adopted" state we propose using in the Tech Radar.

• Tiers of Radars.

  • 1st tier includes information that we expect developers will want to know within 1st 30 days.

  • 2nd tier includes additional decisions to learn post-30 days.

  • 3rd tier includes edX.org-specific decisions.

• Descriptions Next. We'll write blip descriptions first, then use that additional context to determine what ring it belongs in.

• Quadrants. Our quadrants will differ from those used by Thoughtworks. One of our quadrants should be "Open edX Technologies" and include technologies specific to the Open edX ecosystem. The "Techniques" quadrant from Thoughtworks radar feels appropriate for ours, so we will use it. The remaining two quadrants are currently differentiate between "BackendFrontend" and "Frontend"specific technologies and “Technologies” in general, reflecting the natural divisions in our code-base.

...