In reply to Scott Bowler.

That's not strictly true. In fact I read the discussions within Slack. The migration plugin was declined because it was produced before ClassicPress was even in a shippable 'alpha state'. All the plugin did was disable the Gutenberg callout.

So, it's not for the same reason. I imagine that if it was submitted again, you'd have a better chance at being approved (potentially).

I do agree though that the plugin repository rules are tightened and relaxed whenever it's deemed necessary. The fact that this plugin would help promote Gutenberg is probably one reason why it was let through.