Convert Events recipe-adjacent projects to general projects

+1 for this. These recipes aren't usable (at least, not without adding them as VCS repos to composer.json) until they're general projects.

If it could be possible for our Packagist integration to work properly for recipes within module projects (which would in itself resolve the need to convert the projects in this issue), it would save time and effort down the road.

Composer does not support the concept of projects within projects. Every installable repository has only one composer.json at the root level. We are not doing any special Drupal-specific Packagist integration for recipes.

https://www.drupal.org/project/locations → looks like it used to be a module. I believe the moved project will still be installable as a module at that version, via Packagist.org, assuming the composer.json is complete, and not relying on Packages.Drupal.org to detect any .info.yml dependencies or other metadata. I think this should be okay in this case, but something to keep in mind for anything else that had a release as a module; we avoid disrupting older releases.

(Also a good reason to potentially move everything to one single project type, with conditional fields for module/recipe-specific metadata. So projects can switch type in a release, without manual intervention.)

Thanks @drumm. I can confirm that the 1.0 branch for Locations does indeed have a complete composer.json, so hopefully that bodes well for it still being installable as a module. It's definitely more important for it to be installable as a recipe, however.

Some pre-work had to be done in 📌 Handle release/project deletion Active to make sure we can cleanly remove metadata from packages.drupal.org, so it doesn’t override Packagist.org. That is now done.

Done, and the three projects with releases will be available at Packagist.org in a few minutes.

Automatically closed - issue fixed for 2 weeks with no activity.