- 🇳🇿New Zealand quietone
checking in here to see if there is more to do. package manger was recently added but I wasn't involved in the process.
What, if anything is there still do here?
- 🇬🇧United Kingdom catch
package_manager has the same name as a contrib module, but because it came from the automatic_updates project, we didn't have to deal with identical project names, and that's the biggest complexity here.
e.g. automatic updates can create a new contrib branch without package_manager and both can exist at the same time on a site, and then the package manager contrib module will 'disappear' from the code base and the core one will take over.
But when the project name is the same, need to make it so that the contrib project disappears from packagist and that core provides it instead. I think this still needs manual intervention on Drupal.org but can't remember exactly what needs to happen.
- 🇳🇿New Zealand quietone
OK. So catch clarified the remaining problem is when the project name is the same. That point is covered in the related issue, #3188544: [policy discussion] Address Composer namespacing issues when extensions move between core and contrib → .
Therefor. closing this as a duplicate.