Evaluate current code organization in src/mongo/s/ against team ownership patterns

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We currently use owners.yml with pattern matching to assign ownership for the top-level files in src/mongo/s/. A recent code review suggested reorganizing them into component-based subfolders to improve team ownership clarity.

      Goal:
      Evaluate whether our current ownership system via owners.yml patterns is sufficient, or if folder-based organization would provide additional benefits. If the folder-based organization is better, reorganize the top-level files into folders.

            Assignee:
            Unassigned
            Reporter:
            Lucy Wu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: