On Thu, Aug 12, 2021, at 10:42 AM, Matthew Weier O'Phinney wrote: > My main question is why the Util libraries would move to the PER process. > > Currently, these have been developed to provide features complementary > to a given standard: > > - cache-util and simplecache-util provides boilerplate that will be > used in most implementations, as well as default "in memory" > implementations. > - http-util provides constants used for request methods and response > status codes > > In each case, I'd argue they're less "evolving standards" as they are > libraries tracking common usage or tracking non-FIG standards to > provide commonly used artifacts. In other words, they are _libraries_, > not _recommendations_. > > Otherwise, the rest of this looks fantastic! Thanks for putting this together!
Mainly because right now we have no process for util libraries; their ownership and management is entirely undefined (as witnessed by the simpelcache-util library being entirely empty and abandoned for no particular reason). I figure if we establish a process for them it would probably look an awful lot like the PER process, so I tossed them in together. If we wanted to keep them separate, what would that look like? --Larry Garfield -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/0a7fec5a-864d-4b44-b24b-717d9e7e3343%40www.fastmail.com.
