Louis Laugesen

@paulopmt1, @allilevine suggested to drop the sprint goal flag from this as it's not likely we can ship this in the time we have and it's distracting from the plans...

Planning post here pdh6GB-25m-p2 - domain eligibility was in the backlog but not a focus. Moving to slack. p1664155028405089-slack-C03FE3T479R

Broke this down into separate issues see [sprint 31](https://github.com/orgs/Automattic/projects/290/views/20?filterQuery=team%3AExplorers+sprint%3A%22Sprint+31%22).

https://github.com/composer/composer/pull/5293

Need some new ones for: - SEO - CRM & Livechat (Replaced customer service) - Events Calendar - Social - Email (newsletter marketing) But lets start with what we have.

Going by slack I think we can ship this with what we have and ignore the rest for now. (There is a follow up design change that can catch the...

From same thread: Wondering if these planned changes have an impact on this as it will mess with the way plugins get installed / activated and the timing of it....

Might be able to avoid the workaround but need more time to investigate. Linking the debug issue https://github.com/Automattic/wp-calypso/issues/23565#issuecomment-1198952641 And the 20% time p2 pb5gDS-1Vj-p2 about D85060-code and D85066-code

> For Jetpack sites, we show the [empty-list-view](https://github.com/Automattic/wp-calypso/blob/trunk/client/my-sites/subscribers/components/empty-list-view/empty-list-view.tsx) component. Can we do the same for Atomic sites on jetpack cloud? Leaving the launchpad behavior in dotcom default sites only?

What are the next steps to closing this issue? Should we hide this block on simple sites in the meantime? > I took a look at the issue. /wpcom/v2/sites/\/blog-stats is...