On 08/11/2016 08:11 AM, Adam Culp wrote:
Thank you for that LOOOOOOONG explanation Larry, it did carry value
once I had time to read it. While the -interop approach you wrote
about was not something I was concerned with, the other portions were
useful. Thanks for the time spent.
In regards to:
That does of course presume that a project rep is bothering to
read the list and keep abreast of what's going on. If someone
doesn't even have the capacity to do that much, then the project
needs to pick a new rep. Waiting until a spec is done and
polished and just waiting on a final vote to make sure projects
know what is going on is completely and utterly backward.
I would caution that we are all busy, and switching a rep because FIG
is not our life with every breath may be extreme. In your description,
and others' posts, I'm hearing, "Members who can't keep up should go
away." To those who are able to keep up 100% I commend you, but I feel
that would be nobody. We all strive to fit FIG into our day-to-day the
best we can, because we want to contribute. Therefore I still have my
initial concern where things could progress without everybody knowing.
However, I'm not sure how we tackle that. I proposed a member project
vote because it was the easiest to implement and carry out.
I think we've already determined experimentally that asking 40 people to
read every message on the list is a losing battle. :-) Especially when
you layer on top of that the discussions that happen elsewhere than
here. That's part of the impetus for the CC/WG split.
Asking 40 people to at least read any email that is tagged "[Proposal]"
(or whatever) to indicate a possible new PSR is a much lower barrier,
and I think an achievable one. If they see that and go "Oh, they're
talking about a Queue PSR, I don't care about that *wanders off*",
that's fine. That's what people seem to be doing now anyway. I'm
suggesting we embrace that fact and not make their lack of time/interest
an impediment.
If someone can't keep up with at least those initial proposal threads to
know what's been proposed, then yes, that project needs a different
representative. But that's a much lower bar than we have today.
The CC I would expect to be reading everything and staying on top of it;
that's a higher expectation than project reps have, and that's OK.
That's what the CC is signing up for, and they know it.
--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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/php-fig/6d0117e8-4121-77f1-b4b4-b8d2cfcdf8ca%40garfieldtech.com.
For more options, visit https://groups.google.com/d/optout.
