@cassie The steps you mention are indeed separate from technical development, and I don’t see any problem in starting them.
However, the epic is paused for different reasons, some of them about capacity and priorities; see for instance some client epics that should be started first.
But this applies to Serenity/Bebop/Falcon and I don’t know whether it applies to Fixate’s work.
Other points and open tasks in this epic require more development work, to finish defining the new software architecture and workflows. For that we’ll need an epic owner, who needs to be core team, and that’s hard to find since core team members are overloaded.
But for the points you mention you just need reviewers, and I personally think anyone could take the reviews, even newcomers; that could be useful in case newcomers need tasks.
Maybe you (@cassie or @Ali) could become the epic owner of this epic, advance it through the design phase, then look for a next epic owner, when people in Serenity have more place for non-client work.
For simplicity, I think it’s better not to work on epics which are considered paused. If we resume work we must unpause them and allocate time.
It would also be best to wait until we have an epic owner, so that all future reviews can be done by the same person (the epic owner) instead of by many people.
@tikr you already mentioned some epics that Serenity needs to do before; that means this epic is still paused. When do you think we can increase the dedication a bit, to allow Fixate to progress with the design?
Note that the first message in this thread still applies: we still need a new epic owner (core team) from Serenity or another cell.