WordPress plugin adoption

[B-Interactive]

I wasn't previously aware of this option.

WordPress - Take Over an Existing Plugin

It's by no means a guaranteed process, and there are some benefits to a break from legacy. There are still hundreds of active installations however, that could benefit.

[davidmpurdy]

My impression from our correspondence with the individual from Cloudflare was that their preference was a separate fork they would point to, rather than add us to their plugin (which I think is the process if you're working with the original developer as we are).

However, I don't think we ever brought up anything specific. I can see pros and cons either way. If you'd like to follow up on that thread and suggest that, I'm all for it!

[B-Interactive]

I wouldn't want to act against Cloudflare and I'd look to respect their wishes with respect to the original plugin. The 2nd option in that link is something I'd only pursue with their go-ahead.

[rmens]

You should take it over. Cloudflare is being very negligent with their WordPress plug-ins. They probably just don't care.

[JakubJeziorski]

Any update on that?

[rmens]

I opened a support ticket with Cloudflare asking why their stream plug-in breaks with PHP 8.1 and they basically told me 'tough luck there's nobody minding the store'.

If this plug-in is taking over, I guess it will trigger an update for all the installs of the existing CF Stream plug-in and ensure sites don't break when these PHP versions get updated. So this seems to be the responsible thing to do @B-Interactive.

[B-Interactive]

Our discussions with Cloudflare have taken the approach that this will be treated as a separate plugin to the current (outdated) official one, but they were happy for this fork to then be directed to as the (new) official plugin, once it was officially listed on the WordPress Plugins repository.

The thing currently holding back submission to the WordPress repository, is the Block which still needs some work to be considered healthy and functional. Releasing it otherwise, I expect, will result in submission rejection, or very poor public reception. Whilst the shortcodes are working well, WordPress is quite Block centric now, and the two work in fundamentally different ways.

[JakubJeziorski]

Aren't we able to place shortcodes in blocks anyway? So even if they prefer to use it in Gutenberg, they can.

…

On Thu, Jun 15, 2023, 05:06 David Armstrong ***@***.***> wrote: Our discussions with Cloudflare have taken the approach that this will be treated as a separate plugin to the current (outdated) official one, but they were happy for this fork to then be directed to as the (new) official plugin, once it was officially listed on the WordPress Plugins repository. The thing currently holding back submission to the WordPress repository, is the Block which still needs some work to be considered healthy and functional. Releasing it otherwise, I expect, will result in submission rejection, or very poor public reception. Whilst the shortcodes are working well, WordPress is quite Block centric now, and the two work in fundamentally different ways. — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHXT3NAPYA7JK4IOCDM5VBTXLJ33DANCNFSM6AAAAAARJXA24Y> . You are receiving this because you commented.Message ID: ***@***.*** com>