Re: Resigning My Position ...

2016-09-13 Thread Korvin Szanto
Hi All, First of all, I want to apologize to everyone for the content of this email. My hope is that it won't seemtoo critical and instead will read how I intended. Here's a list of my positions: 1. This thread is depressing 2. People on every side need to take a step back and chill 3. PSR-8

Re: [Review][Discuss] FIG 3.0 Upcoming Vote

2016-09-13 Thread Gary Hockin
Paul, I hope I speak for many when I say that your constant nitpicking is becoming increasingly tiresome. I understand that you feel that the secretaries are working outside of the boundaries of the tasks and duties that they were voting in to fulfil. Other voting members on this list disagree

Re: [Review][Discuss] FIG 3.0 Upcoming Vote

2016-09-13 Thread Chris Tankersley
On Tue, Sep 13, 2016 at 10:38 AM, Paul Jones wrote: > > > On Sep 12, 2016, at 11:32, Pedro Cordeiro wrote: > > > > Paul, the role of a secretary is well described here, as I'm sure you > are aware:

Re: [Review][Discuss] FIG 3.0 Upcoming Vote

2016-09-13 Thread Tom Etzel
Paul keeps asking the same question over and over again. Why are you all so reluctant to just answer his question? Seriously... Just explicitly answer his question. The secretary is an "assistive/record-keeping" or the secretary is fill_in_the_blank. You want the guy to stop asking, but nobody

Re: [Review][Discuss] FIG 3.0 Upcoming Vote

2016-09-13 Thread Peter Huynh
A secretary is ... what defined in: http://www.php-fig.org/bylaws/membership/#fig-secretary. Asking again and again and again will not solve anything. Each person's point of view of the bylaw is subjective. It's not a matter of beating around the bush, it's a matter of giving a "correct

Re: [Review][Discuss] FIG 3.0 Upcoming Vote

2016-09-13 Thread Paul Jones
> On Sep 12, 2016, at 11:32, Pedro Cordeiro wrote: > > Paul, the role of a secretary is well described here, as I'm sure you are > aware: http://www.php-fig.org/bylaws/membership/#fig-secretary. Yes, it's *described* there, but nobody seems to be able to say what *kind*

Re: [REVIEW] PSR-13: Link definition interfaces

2016-09-13 Thread Larry Garfield
The standard example we've been using is a domain object of some sort that then is getting rendered to an HTTP Response. To wit: $article = load_article(...); // Article is a class in a domain model, but can generate links to other articles such as next/prev, up to the index of articles, etc.

Re: [REVIEW] PSR-13: Link definition interfaces

2016-09-13 Thread Matthew Weier O'Phinney
On Tue, Sep 13, 2016 at 8:18 AM, Josh Di Fabio wrote: > Quoting the meta doc. > >> Why is a LinkCollectionInterface needed? >> In many contexts, a set of links will be attached to some other object. >> Those objects may be used in situations where all that is relevant is

Re: [REVIEW] PSR-13: Link definition interfaces

2016-09-13 Thread Josh Di Fabio
Quoting the meta doc. > Why is a LinkCollectionInterface needed? > In many contexts, a set of links will be attached to some other object. Those objects may be used in situations where all that is relevant is their links, or some subset of their links. For example, various different value objects