Bring plugin back online about wp-hypothesis

[acelaya]

I have already published a new version using the new automated GitHub workflow.

I requested a new review to the WordPress plugins team, and will follow-up with more details as soon as they come back to us.

[acelaya]

@SteelWagstaff you can find the plugin in packagist now with the package name hypothesis/wp-hypothesis https://packagist.org/packages/hypothesis/wp-hypothesis

[acelaya]

Steps to follow:

• Update project dependencies -> #41
• Migrate from travis to GitHub actions for CI and publishing -> #41
• Try to set-up a dev environment which provides a wordpress instance (maybe through docker compose?) -> #42
• Add a Makefile -> #45
• Test project on a WordPress 6.x instance and see if everything works -> It works! (#42)
• Automate plugin publishing -> #44

Nice to have:

• Add some tests
• Find an opinionated code formatting tool, like prettier in the JS world
• Add a static analysis tool like PHPStan

[SteelWagstaff]

Thanks for your work in reviving this @acelaya. We require the hypothesis WordPress plugin in our bedrocks at Pressbooks. Because the plugin was deactivated at WordPress at org, the mirror at wpackagist has been closed and it's not picking up your latest releases: https://wpackagist.org/search?q=hypothesis&type=any&search=

I'm hopeful that reactivating the plugin on WordPress.org will be enough to get the mirror back up and working.

In the meantime, however, would you have any interest in registering the plugin directly with packagist.org? The process is pretty simple and the GitHub repo already has the required composer.json file. See "Publishing Packages" instructions here: https://packagist.org/. That would allow us to simply run composer require hypothesis/hypothesis to manage the plugin as a dependency, indepedently of whether or not the wordpress.org listing is active and the wpackagist service is mirroring all tagged releases.

I could do this myself as it is a public repo, but it would then list me in packagist as a maintainer of the project, which is a bit misleading.

[acelaya]

In the meantime, however, would you have any interest in registering the plugin directly with packagist.org

This definitely makes sense. People managing their WordPress installations/deployments with composer would definitely benefit from it. I'll try to get it published there today.

Although, now that I look at the package name, it probably needs to be renamed to hypothesis/hypothesis-wp-plugin or something in those lines. The hypothesis/hypothesis name is too "top level", so to speak, and might be needed for other packages eventually.

[SteelWagstaff]

Amazing -- thanks!

[acelaya]

The plugin has been enabled again by the plugins team. I have also requested the previous owner to transfer ownership to us.

[acelaya]

Confirming wpackagist has started to pick up the new updates now that the plugin is listed again