Closed mindplay-dk closed 10 months ago
Completely +1 on removing Puli. Service discovery is something important IMHO if we want to have something friendly for the end user.
But indeed, we can discuss that later, or in another PSR / project. So I have no strong objection to remove it at this stage 👍
Yeah, I think we need to narrow the scope - glad you agree. 🙂
For the record, the PSR meta document draft now reads:
5. Service Discovery
Integration with projects like Puli was explored, for automatic discovery and binding of service providers.
Puli is EOL by now, but served as proof of concept with regards to the potential for service discovery, whether this be framework-specific, or via a future standard.
Service discovery (as a feature of the standard) is outside the scope of this PSR.
I'd like to go ahead and remove
puli.json
and documentation references, as Puli is long dead and gone.I would likely remove any mentions of service discovery, as it is not relevant or required for interoperability - and since it can be added later.
If you think it's worth mentioning, I could add something to the PSR meta document explaining how this was considered and why it is not required for this PSR?
Any objections?