DISCUSS: Organization of EE-specific code

@meks wrote:

Is there a parent issue that is tracking this overall effort? I ended up looking at this epic gitlab-org&27 (closed) and was wondering if this is still being used to track. It seems like we have done 18/24 MRs in the epic.

  • Are there still work that hasn't been scoped out by the team? Are we anticipating more MRs to finish this
  • I noticed we are helping out the BE (backend team) with migrating spinach to Rspec is this work related as well?

[...]

This is important, I would recommend we take a step back and scout all the areas that are unfinished. Its perfectly spending a day diving into the codebase and taking notes down to an issue. #slowdowntospeedup

[...]

Before embarking on this effort, let's answer these questions first:

  1. Do we know all the remaining areas are left to migrate? (rough idea, we can spend some more time this week to do more investigation)
  2. Do we know our current progress ? (rough % no. is fine)
  3. Do all the engineering teams know that all new EE content should be put in the ee/ top-level folder going forward?
  • If not it means that we will have new stuff to migrate coming in all the time. :(
  • I have also added a MR checklist item to the EE repo - [ ] EE specific content should be in the top level /ee Let me know if I should add this to CE as well. https://gitlab.com/gitlab-org/gitlab-ee/edit
  1. It sounds like we may need a team discussion forum on this EE organization, can we do this in #qa, I would assume we may need other dev teams to chime in as well.

Previous work:

Previous discussions:

The idea is to set up a plan of action.

/cc @godfat @rspeicher

Edited by Mek Stittri