Re: PSR-17 Explicit Nullable

2024-04-15 Thread Matteo Beccati
Hi Vincent,Il 15/04/2024 15:28, Vincent de Lau ha scritto:> I would not 
mind a small rationale in the errata why it is `?string` and

not `string|null`.


That would mean raising the required version to 8.0, when union types 
were introduced.



Cheers
--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/723dba4f-ab7f-4dab-a63d-73951da3798d%40beccati.com.


Re: PSR-17 Explicit Nullable

2024-04-15 Thread Matteo Beccati
+1


thanks for the quick follow up!

On Mon, Apr 15, 2024 at 2:12 PM Woody Gilk  wrote:

> As editor of PSR-17, I hereby call a vote to:
>
>1. Change the minimum required version of PHP to 7.1 for PSR-17.
>2. Add explicit nullable types to PSR-17 interfaces.
>3. Tag a new release v1.1.0 of psr/http-factory with changes (1) and
>(2).
>
> The relevant PRs are:
>
> https://github.com/php-fig/fig-standards/pull/1321
> https://github.com/php-fig/http-factory/pull/17
>
> Thank you,
>
> --
> Woody Gilk (he/him)
> https://www.shadowhand.com
>
> --
> 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/CAGOJM6JNuwYA9Twh-0FJZ7sgQ_kaLCdBUSHMTRLXgb95TSox4Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CAGOJM6JNuwYA9Twh-0FJZ7sgQ_kaLCdBUSHMTRLXgb95TSox4Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/CAFE4j_D%2B2bm1DVAFQmJ5vVpLoazEcWmvb4w2863Pc%3DSfjdka5w%40mail.gmail.com.


Re: [Internals][ELECTIONS] Request for Nominations

2024-02-21 Thread Matteo Beccati

Hi Mark,

thanks for the nomination. Accepted!


Cheers

Il 21/02/2024 16:19, Mark Niebergall ha scritto:
I nominate Matteo Beccati for a Core Committee Member. Matteo is a 
current Project Representative, and has previously served as a CC Member.


On Friday, February 16, 2024 at 1:17:45 PM UTC-7 Mark Niebergall wrote:

Hello All,

On Thursday, February 8, 2024 at 5:19:21 PM UTC-7 Mark Niebergall wrote:

Hello Everyone,

It is a little late, but it is election time again. To make up
for some time, we are immediately opening the nominations.

The following 4 Core Committee seats are up for election: Chris
Tankersley, Korvin Szanto, Enrico Zimuel, and Ken Guest.

There is also 1 Secretary position up for election: Steve Winter.

Those with seats expiring may express their intention to run
again for election. Anyone else is also welcome to seek a
nomination to be included in the election.

Nominations will be open until 2024-02-16 00:00 UTC, at which
time the election will start. Elections will run for two weeks,
ending 2024-03-01 00:00 UTC.


The nomination period was scheduled to end at 2024-02-16 00:00:00
UTC, but there are insufficient Core Committee (CC) and Secretary
nominations. The period will be extended 1 week to 2024-02-23
00:00:00 UTC to allow for 1 more publicly accepted CC nomination and
1 Secretary. Voting (if necessary) will end instead 2024-03-07
00:00:00 UTC.

Current nominations for CC are:
- Steve McDougall (accepted nomination from Chris Tankersly)
- Ken Guest (pending acceptance of nomination from Chuck Burgess)
- Korvin Szanto (accepted nomination from Alexander Makarov)

Who else is willing to help the PHP-FIG group as a CC or Secretary?
Please consider seeking a nomination from any Project Representative
or Secretary listed for PHP-FIG https://www.php-fig.org/personnel/
<https://www.php-fig.org/personnel/>.


Feel free to reach out to the other two secretaries (Alessandro
and Mark), or any other sitting PHP-FIG member, to ask for a
nomination or for further information.

*FAQ:*
*
*Q: Who can be nominated?
A: Anyone! The secretaries of the PHP-FIG are basically
administrative clerks and community handlers. For more details,
see
https://www.php-fig.org/bylaws/mission-and-structure/#secretaries 
<https://www.php-fig.org/bylaws/mission-and-structure/#secretaries>
The CC members of the PHP-FIG are basically the technical
steering committee; citing the bylaw:
https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee 
<https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee>

Q: Who can nominate?
A: Citing the bylaw: "Candidates for Secretary or the Core
Committee must be nominated/proposed by an existing Project
Representative or FIG Secretary to be considered, and must
publicly accept their nomination in order to be valid.
Prospective candidates may seek nominations in any way they see
fit."

For full election bylaws, please see the PHP-FIG bylaws:
https://www.php-fig.org/bylaws/elections-and-vacancies/
<https://www.php-fig.org/bylaws/elections-and-vacancies/>


Thanks,

Mark Niebergall
PHP-FIG Secretary

--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/f00bfde9-4f6f-4aeb-9673-48ffd08ea962n%40googlegroups.com <https://groups.google.com/d/msgid/php-fig/f00bfde9-4f6f-4aeb-9673-48ffd08ea962n%40googlegroups.com?utm_medium=email_source=footer>.


--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/4b5a5e44-d5c2-474d-8945-a648876ce13e%40beccati.com.


Re: [VOTE][Projects] Expulsion Vote for Stormpath PHP SDK

2023-10-06 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

+1 from Revive Adserver

Il 05/10/2023 16:52, Buster Neece ha scritto:

+1 from AzuraCast

On Thursday, October 5, 2023 at 9:39:01 AM UTC-5 Vincent de Lau wrote:

This thread is to collect Member Project votes on the Stormpath PHP
SDK Expulsion vote.

The proposal is to expel Stormpath PHP SDK as a Member Project.

There have been various efforts to prevent this drastic measure,
without any result. The final discussion thread with the background
leading to this proposal can be found here:
https://groups.google.com/g/php-fig/c/zYvUOTH-y3I
<https://groups.google.com/g/php-fig/c/zYvUOTH-y3I>

Voting ends by 2023-10-19 17:00 UTC

Voting options: For (+1), Against (-1), or Abstain (+0)
Quorum: none
Majority: 50%
https://www.php-fig.org/bylaws/voting-protocol/#expulsion-vote
<https://www.php-fig.org/bylaws/voting-protocol/#expulsion-vote>

ONLY PROJECT REPRESENTATIVES CAN VOTE HERE, see current list:
https://www.php-fig.org/personnel/#member-projects
<https://www.php-fig.org/personnel/#member-projects>

--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/301f8393-bf9f-40e9-ae8e-738a922b8da1n%40googlegroups.com <https://groups.google.com/d/msgid/php-fig/301f8393-bf9f-40e9-ae8e-738a922b8da1n%40googlegroups.com?utm_medium=email_source=footer>.


--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/4446115f-2c97-b23a-db9b-491da7486017%40beccati.com.


Re: [VOTE][Projects] Expulsion Vote for eZ Systems

2023-10-06 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

+1 from Revive Adserver

Il 05/10/2023 16:52, Buster Neece ha scritto:

+1 from AzuraCast

On Thursday, October 5, 2023 at 9:38:00 AM UTC-5 Vincent de Lau wrote:

This thread is to collect Member Project votes on the eZ Systems
Expulsion vote.

The proposal is to expel eZ Systems as a Member Project.

There have been various efforts to prevent this drastic measure,
without any result. The final discussion thread with the background
leading to this proposal can be found here:
https://groups.google.com/g/php-fig/c/zYvUOTH-y3I
<https://groups.google.com/g/php-fig/c/zYvUOTH-y3I>

Voting ends by 2023-10-19 17:00 UTC

Voting options: For (+1), Against (-1), or Abstain (+0)
Quorum: none
Majority: 50%
https://www.php-fig.org/bylaws/voting-protocol/#expulsion-vote
<https://www.php-fig.org/bylaws/voting-protocol/#expulsion-vote>

ONLY PROJECT REPRESENTATIVES CAN VOTE HERE, see current list:
https://www.php-fig.org/personnel/#member-projects
<https://www.php-fig.org/personnel/#member-projects>

--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/61b71431-2d2d-4575-a7d0-7d7f5a71c52en%40googlegroups.com <https://groups.google.com/d/msgid/php-fig/61b71431-2d2d-4575-a7d0-7d7f5a71c52en%40googlegroups.com?utm_medium=email_source=footer>.


--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/eaf3a9f1-0bc6-fb17-b8e2-c56358367003%40beccati.com.


Re: [VOTE][Projects] Hyperf Membership vote

2023-07-24 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

Hi,

+1 from Revive Adserver


Il 24/07/2023 11:13, Vincent de Lau ha scritto:
This thread is to collect Member Project votes on the Hyperf Membership 
vote.


The proposal is to accept Hyperf as a Member Project. Hyperf will be 
represented by Leo Cavalcante. The membership application is being 
sponsored by Vincent de Lau as a Core Committee member.


The membership application and discussion thread can be found here: 
https://groups.google.com/g/php-fig/c/zwsMt9E6wzw


Voting ends by 2023-08-07 10:00 UTC

Voting options: For (+1), Against (-1), or Abstain (+0)
Quorum: none
Majority: 50%
https://www.php-fig.org/bylaws/voting-protocol/#membership-vote

ONLY PROJECT REPRESENTATIVES CAN VOTE HERE, see current list: 
https://www.php-fig.org/personnel/#member-projects


--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/62ec442f-4c7f-4367-809f-e6dd7e7364dbn%40googlegroups.com <https://groups.google.com/d/msgid/php-fig/62ec442f-4c7f-4367-809f-e6dd7e7364dbn%40googlegroups.com?utm_medium=email_source=footer>.


--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/5a61b7f8-bf77-d87a-7059-56d378e5986b%40beccati.com.


Re: [VOTE] Core Committee Election January 2022

2022-01-16 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

Voting for Revive Adserver:

1. Enrico Zimuel
2. Florian Engelhardt
3. Ken Guest
4. Chris Tankersley
5. Korvin Szanto
6. Navarr Barnier


Cheers

On 15/01/2022 17:51, Vincent de Lau wrote:

Hello everyone,

Yesterday the nomination period ended, and we got 7 nominations in 
total, which is great!
For the secretary seat, we have one uncontested nomination. For the Core 
Committee, we have 6 nominations against 4 available seats, so this 
means that we will be holding a proper election, starting now! The 
nominees are (in temporal order of nomination):


  * Korvin Szanto - https://groups.google.com/g/php-fig/c/Rv43KRFOt_A
  * Navarr Barnier - https://groups.google.com/g/php-fig/c/kAOTuIFB7Eg
  * Chris Tankersley - https://groups.google.com/g/php-fig/c/xtrwd7o6SOQ
  * Ken Guest - https://groups.google.com/g/php-fig/c/QtKqPOYZ2HA
  * Florian Engelhardt - https://groups.google.com/g/php-fig/c/wjxZf1VMzDA
  * Enrico Zimuel - https://groups.google.com/g/php-fig/c/vA-dFT8lXbM 

You can find information about the nominees inside the linked nomination 
thread. Full information about the Core Committee vote and role is 
visible in the bylaws here: 
https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee 
*Who can vote?* As specified in the bylaws, the vote for CC members is 
open to Project Representatives and individuals from the community. To 
be eligible to vote as an individual, the bylaw established the 
following threshold:: /"Any individual that has posted a non-trivial 
message in the official FIG venue (mailing list, forum, etc.) at least 
five (5) times within the past calendar year as of the start of 
nominations [...] is eligible to vote on Core Committee candidates."/ We 
will obviously consider Discord in this account; feel free to reach to 
me or any other secretary to check on the matter. *When can you vote?* 
Voting will be open in this thread until January 29th 17:00 UTC.

*How to vote*
Votes are cast by replying in this thread on the list. For individuals 
that have not used the mailing list before, please be sure to identify 
yourself, for instance by including your Discord or Github handle.
The voting system used is STV[1][2], so basically, there is no tactical 
voting possible (like with FPTP); vote for who you want, even if they 
are a less popular candidates as your vote will move down to a different 
candidate if you back an unpopular candidate who doesn't have enough 
votes; if a candidate is elected, their surplus votes are also 
re-allocated so you are not punished for backing popular candidates 
either. There is no quorum, you are of course entitled to not vote and 
it will not count as a missed vote on the voting sheet. Rank all the 
candidates in order of preference for example: 1. Luke 2. Leia 3. Anakin 
4. Rey 5. Padmé 6. Finn At the end of the voting phase, secretaries will 
be announcing the results, and all the newly elected (both CC members 
and secretary). Thanks, and happy voting! Alessandro Lai and Vincent de 
Lau PHP-FIG Secretary [1]: STV User-friendly Explanation 
https://www.youtube.com/watch?v=l8XOZJkozfI [2]: 
https://en.wikipedia.org/wiki/Single_transferable_vote


--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/22dd11d5-8d4a-46d7-ab77-e291b4e03f49n%40googlegroups.com <https://groups.google.com/d/msgid/php-fig/22dd11d5-8d4a-46d7-ab77-e291b4e03f49n%40googlegroups.com?utm_medium=email_source=footer>.


--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/c656e886-20a4-debb-f142-812d86a096df%40beccati.com.


Re: [VOTE] Core Committee Election

2021-06-11 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

Hi,

1) Alessandro Chitolina
2) Michelle Sanver
3) Larry Garfield
4) Matthew Weier O'Phinney
5) Woody Gilk


Cheers
--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/a3c1cbcd-8e79-d8a6-c228-2ccfd2c31041%40beccati.com.


Re: [Internal][ELECTIONS] Request for nominations

2021-06-10 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

Hi Alessandro,

thanks for the nomination. I've been pondering what to do in the past 
couple of days and I think I made up my mind now.


Since we now have already 5 CC members running in the election, I've 
decided to *not* accept the nomination in order to have mathematical 
certainty that the new candidates will have their slot in the CC.


There will still be an election for term length, but I love the idea of 
having fresh blood in the CC. Good luck everybody!



Cheers

On 08/06/2021 17:06, Alessandro Lai wrote:

I'm nominating Matteo Beccati for re-election as CC member.

Il giorno venerdì 4 giugno 2021 alle 11:26:25 UTC+2 alek...@gmail.com ha 
scritto:


Hi everyone,
I accept the nomination. Thank you very much Alessandro!

All the best,
Alessandro

Il giorno venerdì 4 giugno 2021 alle 11:03:59 UTC+2
alessand...@gmail.com ha scritto:

Hello everyone!
I would like to nominate another CC: Alessandro Chitolina:
https://github.com/alekitto <https://github.com/alekitto>

For those who don't know him, he's a freelance Web Solution
Architect, working with Decathlon, Switcho and many other
companies. He's a PHP developer since 2009, and he does a lot of
Open Source work:
  * Solido, a toolbox to build REST APIs in PHP:
https://solid-o.github.io/docs/ <https://solid-o.github.io/docs/>
  * messenger-extra, DBAL & MongoDB transports for Symfony
Messenger: https://github.com/alekitto/messenger-extra
<https://github.com/alekitto/messenger-extra>
  * class-finder, a class-discovery utility inspired by Symfony
finder: https://alekitto.github.io/class-finder/
<https://alekitto.github.io/class-finder/>

I would also add that I forgot to put a deadline on the
nominations. Normally they would span for two weeks, so up until
yesterday, but since we still have to gather enough names to
fill the spots, I will let them run for an additional week, so
up until the 10th.
Il giorno venerdì 4 giugno 2021 alle 03:49:49 UTC+2 Michelle
Sanver ha scritto:

Hi everyone,

Guess I’m jumping out of lurker mode! 

Thanks a lot for the nomination Benni. I accept.

With gratitude,
Michelle Sanver
On 1 Jun 2021, 22:09 +0200, Benjamin Mack
, wrote:

Hey everybody,

I nominate Michelle Sanver as Core Committee member.

All the best,
Benni from TYPO3.


On 20. May 2021, at 21:55, Alessandro Lai
 wrote:

Hello everyone,
and sorry for the delay. This is the month where we
should be holding a new cycle of elections, but instead
I'm a little late, so I'll try to kickstart the process now.

We have those positions to fill which will be expired by
the end of the month:
 - 1 secretary position, currently owned by Asmir Mustafic
 - 4 CC Larry Garfield, Matthew Weier O'Phinney, Woody
Gilk, Matteo Beccati
 - 1 CC position, which was left vacant by Beau Simensen
last year

Every one of the five which have an expiring term can
express their intention to run again for election, as
anyone else is welcome to throw their hat in the ring and
help us out!

As always,
*FAQ:*
Q: Who can be nominated?
A: Anyone! The secretaries of the PHP-FIG are basically
administrative clerks and community handlers. For more
details, see
https://www.php-fig.org/bylaws/mission-and-structure/#secretaries
<https://www.php-fig.org/bylaws/mission-and-structure/#secretaries>
The CC members of the PHP-FIG are basically the technical
steering committee; citing the bylaw:

https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee

<https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee>

Q: Who can nominate?
A: Citing the bylaw: "Candidates for Secretary or the
Core Committee must be nominated/proposed by an existing
Project Representative or FIG Secretary to be considered,
and must publicly accept their nomination in order to be
valid. Prospective candidates may seek nominations in any
way they see fit."

Feel free to reach out to me, the other two secretaries
(Asmir & Buster) or any other sitting PHP-FIG member to
ask for a nomination or for further informations.

--
You received this message because you are subscribed to
the Google Groups "PHP Framework Interopera

Re: [Internal][ELECTIONS] Request for nominations

2021-05-24 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

Hi everybody,

I nominate for CC:

- Larry  Garfield

- Matthew Weier O'Phinney


Cheers

On 20/05/2021 21:55, Alessandro Lai wrote:

Hello everyone,
and sorry for the delay. This is the month where we should be holding a 
new cycle of elections, but instead I'm a little late, so I'll try to 
kickstart the process now.


We have those positions to fill which will be expired by the end of the 
month:

  - 1 secretary position, currently owned by Asmir Mustafic
  - 4 CC Larry Garfield, Matthew Weier O'Phinney, Woody Gilk, Matteo Beccati
  - 1 CC position, which was left vacant by Beau Simensen last year

Every one of the five which have an expiring term can express their 
intention to run again for election, as anyone else is welcome to throw 
their hat in the ring and help us out!


As always,
*FAQ:*
Q: Who can be nominated?
A: Anyone! The secretaries of the PHP-FIG are basically administrative 
clerks and community handlers. For more details, see 
https://www.php-fig.org/bylaws/mission-and-structure/#secretaries 
<https://www.php-fig.org/bylaws/mission-and-structure/#secretaries>
The CC members of the PHP-FIG are basically the technical steering 
committee; citing the bylaw: 
https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee 
<https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee>


Q: Who can nominate?
A: Citing the bylaw: "Candidates for Secretary or the Core Committee 
must be nominated/proposed by an existing Project Representative or FIG 
Secretary to be considered, and must publicly accept their nomination in 
order to be valid. Prospective candidates may seek nominations in any 
way they see fit."


Feel free to reach out to me, the other two secretaries (Asmir & Buster) 
or any other sitting PHP-FIG member to ask for a nomination or for 
further informations.


--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/dce97b4a-2d1a-47ce-8e97-a3a7273d4789n%40googlegroups.com 
<https://groups.google.com/d/msgid/php-fig/dce97b4a-2d1a-47ce-8e97-a3a7273d4789n%40googlegroups.com?utm_medium=email_source=footer>.



--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/6445e0cf-a1fc-190c-1486-fd864a7c63f1%40beccati.com.


Re: [VOTE][CC] Bylaw CS update

2021-03-31 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

+1

On 31/03/2021 09:15, Alessandro Lai wrote:


Hello everyone,
this my seem a small formality, but we need a vote for a small bylaw 
amendment: https://github.com/php-fig/fig-standards/pull/1203


Basically, we need to update the guidelines to follow PSR-12, since it 
deprecated PSR-2.


As per our voting protocol: https://www.php-fig.org/bylaws/voting-protocol/

This is a vote for the Core Committee only.
Quorum is 50%.
A 2/3 majority is required for passage.
Voting ends in two weeks, at midnight UTC between 14th & 15th of April.

I'll be opening a separate thread for project representative.

--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/0f947e00-2141-4ca6-910c-03b416878dcbn%40googlegroups.com 
<https://groups.google.com/d/msgid/php-fig/0f947e00-2141-4ca6-910c-03b416878dcbn%40googlegroups.com?utm_medium=email_source=footer>.



--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/398318a5-d424-3b55-13f9-d2995e645311%40beccati.com.


Re: [Internal] Sunset Slack workspace?

2021-03-24 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

Hi,

Yes please. As a matter of fact, I've removed the workspace from my 
client already ;-)



Cheers

On 24/03/2021 13:24, Alessandro Lai wrote:

Hello everyone,
I'm happy to see that the Discord experiment is going well: over 200 
users have joined, the newly formed WG for PSR-20 has found a home 
there, and we've now migrated the Twitter and site deploy integration too.


So, my question is: should we close/retire the Slack workspace? It's 
basically silent, noone is using it, and our collective RAMs would 
surely be happier with one less workspace to be kept open.


WDYT?

--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/9b86ef3a-e7bd-4577-9d32-37a201bf7dabn%40googlegroups.com 
<https://groups.google.com/d/msgid/php-fig/9b86ef3a-e7bd-4577-9d32-37a201bf7dabn%40googlegroups.com?utm_medium=email_source=footer>.



--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/c4fd5308-34aa-7929-25ff-fc80938c5afd%40beccati.com.


Re: [ENTRANCE] [VOTE] [CC] Clock Interface PSR

2021-03-16 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

+1

On 16/03/2021 00:35, Chuck Burgess wrote:

As the Sponsor for this new candidate PSR, I hereby call the Entrance Vote.


Proposal PR: https://github.com/php-fig/fig-standards/pull/1224 
<https://github.com/php-fig/fig-standards/pull/1224>



Editor: Chris Seufert
Sponsor:  Chuck Burgess - PHP-FIG
Working Group:
- Jérôme Gamez (kreait/clock)
- Andreas Möller (ergebnis/clock)
- Luís Cobucci (lcobucci/clock)
- Pol Dellaiera
- Ben Edmunds
- Andreas Heigl (ergebnis/clock)


Please do not reply to this topic if you are not a CC member.
--

--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/CANsgjnsAk9%2BmEEgM2od81rs5JttLHV%3DDuYpkaMF9qtuFx%3DwEGQ%40mail.gmail.com 
<https://groups.google.com/d/msgid/php-fig/CANsgjnsAk9%2BmEEgM2od81rs5JttLHV%3DDuYpkaMF9qtuFx%3DwEGQ%40mail.gmail.com?utm_medium=email_source=footer>.



--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/8c22c5ec-7a56-0803-8365-aad376e1d68f%40beccati.com.


Re: [Vote] PSR-13 Link Errata

2021-03-05 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

+1

On 24/02/2021 22:50, Larry Garfield wrote:

Since there seems to be no dissension, no sense waiting any longer.

I am hereby calling an Errata vote on the following Link fixes, including the 
linked (no pun intended) PRs.

https://github.com/php-fig/fig-standards/pull/1222

This is a CC Vote, requiring 2/3 to pass.  Voting will remain open until 10 
March, unless all 11 CC members vote before then.  (Hint hint, folks. :-) )




--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/c7930ff3-7b1a-73c9-7655-1ad75aa92700%40beccati.com.


Re: [VOTE][PSR-11] Type Updates

2021-03-03 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

+1

sorry for the delay


On 19/02/2021 15:30, Matthew Weier O'Phinney wrote:

Hi, everyone!

On 2021-01-25, I opened the discussion period around updating PSR-11 per 
the PSR Evolution bylaw (https://www.php-fig.org/bylaws/psr-evolution/ 
<https://www.php-fig.org/bylaws/psr-evolution/>). The discussion centers 
around three related proposals:


- https://github.com/php-fig/fig-standards/pull/1215 
<https://github.com/php-fig/fig-standards/pull/1215> (the errata for the 
specification)
- https://github.com/php-fig/container/pull/20 
<https://github.com/php-fig/container/pull/20> (the first step of the 
evolution, adding argument typehints, and modifying defined exception 
interfaces to extend Throwable)
- https://github.com/php-fig/container/pull/28 
<https://github.com/php-fig/container/pull/28> (the second step of the 
evolution, adding return typehints where reasonable)


Since opening the discussion period, the main question was whether the 
second step should have the specification target PHP 8 in order to pick 
up the "mixed" type. Consensus is that we should target PHP 7 releases 
at this time, as this will allow libraries to adopt the changes faster. 
(As an example, we're only just now getting around to having 
laminas-servicemanager typehint explicitly against PSR-11 and not 
container-interop; we'll be able to jump to the latest versions of the 
spec immediately as a result.)


As the discussion period has passed the two-week minimum threshold, I 
now hereby open the vote.


+1 to merge the patches and create the new releases
-1 to leave things as-is
+0 to abstain

Thanks in advance, everyone!

--
Matthew Weier O'Phinney
mweierophin...@gmail.com <mailto:mweierophin...@gmail.com>
https://mwop.net/ <https://mwop.net/>
he/him

--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/CAJp_myVHMjmrQmk5LP_5rvdLYzbTPquQJSX%2BDE%2B2KS4UzbsJ2A%40mail.gmail.com 
<https://groups.google.com/d/msgid/php-fig/CAJp_myVHMjmrQmk5LP_5rvdLYzbTPquQJSX%2BDE%2B2KS4UzbsJ2A%40mail.gmail.com?utm_medium=email_source=footer>.



--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/2aa8f3b0-fe36-6f5c-8828-9aa4908d2215%40beccati.com.


Re: [VOTE][PSR-11] Type Updates

2021-02-22 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

Hi,

+1


On 19/02/2021 15:30, Matthew Weier O'Phinney wrote:

Hi, everyone!

On 2021-01-25, I opened the discussion period around updating PSR-11 per 
the PSR Evolution bylaw (https://www.php-fig.org/bylaws/psr-evolution/ 
<https://www.php-fig.org/bylaws/psr-evolution/>). The discussion centers 
around three related proposals:


- https://github.com/php-fig/fig-standards/pull/1215 
<https://github.com/php-fig/fig-standards/pull/1215> (the errata for the 
specification)
- https://github.com/php-fig/container/pull/20 
<https://github.com/php-fig/container/pull/20> (the first step of the 
evolution, adding argument typehints, and modifying defined exception 
interfaces to extend Throwable)
- https://github.com/php-fig/container/pull/28 
<https://github.com/php-fig/container/pull/28> (the second step of the 
evolution, adding return typehints where reasonable)


Since opening the discussion period, the main question was whether the 
second step should have the specification target PHP 8 in order to pick 
up the "mixed" type. Consensus is that we should target PHP 7 releases 
at this time, as this will allow libraries to adopt the changes faster. 
(As an example, we're only just now getting around to having 
laminas-servicemanager typehint explicitly against PSR-11 and not 
container-interop; we'll be able to jump to the latest versions of the 
spec immediately as a result.)


As the discussion period has passed the two-week minimum threshold, I 
now hereby open the vote.


+1 to merge the patches and create the new releases
-1 to leave things as-is
+0 to abstain

Thanks in advance, everyone!

--
Matthew Weier O'Phinney
mweierophin...@gmail.com <mailto:mweierophin...@gmail.com>
https://mwop.net/ <https://mwop.net/>
he/him

--
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 
<mailto:php-fig+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/CAJp_myVHMjmrQmk5LP_5rvdLYzbTPquQJSX%2BDE%2B2KS4UzbsJ2A%40mail.gmail.com 
<https://groups.google.com/d/msgid/php-fig/CAJp_myVHMjmrQmk5LP_5rvdLYzbTPquQJSX%2BDE%2B2KS4UzbsJ2A%40mail.gmail.com?utm_medium=email_source=footer>.



--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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/ac445d18-548c-f4d8-8901-2c8a9d59c55e%40beccati.com.


Re: [Vote] [PSR-13] updates

2021-01-22 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
+1

On 16/01/2021 18:06, Larry Garfield wrote:
> I hereby call a vote of the Core Committee to approve the following PRs to 
> update PSR-13 to use modern PHP typing capabilities, as previously discussed.
> 
> This is a Core Committee vote requiring a 50% quorum and 2/3 majority, with 
> voting ending on 30 January.
> 
> CC members, please cast your votes.
> 
> Step 1: https://github.com/php-fig/link/pull/6
> Step 2: https://github.com/php-fig/link/pull/7
> Spec: https://github.com/php-fig/fig-standards/pull/1199
> 


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/8b3d2561-c7f9-a875-89f7-baff6c42507f%40beccati.com.


Re: [Vote] [PSR-6] Type updates

2021-01-22 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
+1

On 16/01/2021 18:08, Larry Garfield wrote:
> I hereby call a vote of the Core Committee to approve the following PRs to 
> update PSR-6 to use modern PHP typing capabilities, as previously discussed.
> 
> This is a Core Committee vote requiring a 50% quorum and 2/3 majority, with 
> voting ending on 30 January.
> 
> CC members, please cast your votes.
> 
> Spec: https://github.com/php-fig/fig-standards/pull/1220
> Step 1: https://github.com/php-fig/cache/pull/23
> Step 2: https://github.com/php-fig/cache/pull/24
> 


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/d6ff5127-8705-954f-8237-60382030b67b%40beccati.com.


Re: Separate repository on GitHub for discussions, voting, politics?

2020-08-11 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
Hi,

On 11/08/2020 17:18, daniel...@gmail.com wrote:
> btw, IRC chat is almost dead. There are some people online (16), but
> nobody talks even when you asks about very PHP-FIG-related things. 

IRC could be (almost) dead, but some people are still hanging out in it.

You just can't expect a quick reply as if it was a channel with hundreds
of active people at any given time.

However on sunday at 19:17 CEST someone joined the channel. At 20:07,
they asked a question. Between 20:15 and 20:17 they pinged a few channel
members typing their nicknames. They waited a whole 12 minutes and left
the channel.

I have randomly noticed at 21:06 that xchat was blinking, which was too
late... but I would have happily answered that the mailing list was the
place to discuss that.

I normally don't pass sunday evenings waiting if someone pops in on IRC
for a whole 20 minutes, asking php-fig questions. If I should, just
please let me know! ;-)


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/69f5aca0-17e7-c99e-1f7e-ada66b1e7095%40beccati.com.


Re: [VOTE][CC] Errata bylaw update

2020-07-10 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
+1


Cheers

On 09/07/2020 10:46, Alessandro Lai wrote:
> Since the mandatory two weeks are passed on the discussion
> (https://groups.google.com/g/php-fig/c/CObJmc5jDcE), I'm hereby calling
> a CC vote for this bylaw change.
> 
> As always, quorum is 50%, majority 2/3.
> Vote will end July 23rd, 23:59:59 UTC.
> 
> THIS THREAD IS FOR CORE COMMITTEE VOTES ONLY
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/718c7275-04ae-4e60-a4ec-6330cd893ed0n%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/718c7275-04ae-4e60-a4ec-6330cd893ed0n%40googlegroups.com?utm_medium=email_source=footer>.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/26b62f91-fdb6-92b0-5928-c71471dac87a%40beccati.com.


Re: [VOTE][CC] TYPO3 Membership vote

2020-07-03 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
Hi,

I've sponsored the vote, so here's my +1.


Cheers

On 03/07/2020 09:16, Alessandro Lai wrote:
> This thread is to collect votes on the TYPO3 Membership vote.
> 
> Details:
>  - membership request:
> https://groups.google.com/d/topic/php-fig/qDOyOuLuoKc/discussion
>  - proposed project representative: Benni Mack, which is project lead
>  - request sponsored by Matteo Beccati 2 weeks ago:
> https://groups.google.com/d/msg/php-fig/qDOyOuLuoKc/HtwMXZ_jBgAJ
> 
> 
> Quorum: 50%
> Majority: 50%
> https://www.php-fig.org/bylaws/voting-protocol/#membership-vote
> 
> ONLY CORE COMMITTEE MEMBERS CAN VOTE HERE
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/cf05addb-2600-483c-ae7c-8766cf6f27c2o%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/cf05addb-2600-483c-ae7c-8766cf6f27c2o%40googlegroups.com?utm_medium=email_source=footer>.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/a51b83ce-94aa-6b16-d765-e8487903e0f0%40beccati.com.


Re: Membership Request: Benni Mack (TYPO3)

2020-06-19 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
Hi Larry,

On 18/06/2020 22:21, Larry Garfield wrote:
> On Thu, Jun 18, 2020, at 3:16 PM, Benni Mack wrote:
>> I don't know exactly if I should start a vote or if this is done by a 
>> CC member or Secretary.
>> https://www.php-fig.org/bylaws/voting-protocol/#membership-vote
> 
> Technically, as written an existing project rep from another project needs to 
> call the vote, and all votes should have a 2 week discussion period prior.  I 
> guess this email starts off that 2 week timer.
> 
> I fully support and endorse TYPO3's membership.  They meet all of the 
> requirements and they're leveraging several PSRs already.  I'm not a project 
> rep, though, so I cannot call a vote in 2 weeks. :-)  Someone who is, please 
> do so.

I guess I can, so that is what I'm going to do: I call a vote in 2 weeks :-)


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/5841f693-96bc-48b6-fa1c-48a5c6f06151%40beccati.com.


Re: [DISCUSS] Disallowing trailing comma in function and method definitions

2020-04-29 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
Hi,

so, we just voted the feature in (58 vs 1), but you'd like to disallow
it in PSR-12. I don't think that is a good move, as much as you hate the
feature yourself.

On 29/04/2020 11:20, tag Knife wrote:
> Since the RFC to allow this behavour in PHP 8 has been accepted, I wish
> to start talks on if we should amend PSR-12 to allow or disallow
> trailing commas in function and method names.
> 
> There is general confusion within the community why this RFC has been
> firstly proposed and mostly accepted. With others welcoming the change
> as they apparently do this error all the time.
> 
> Personally I have never had a problem with accedently trailing a comma
> in parameter lists and against this RFC, I think it promotes learned bad
> habits instead of allowing people to learn from mistakes.
> I am for disallowing trailing commas in parameter lists in either PSR-12
> or any future code style.
> 
> Discuss.
> 
> RFC: https://wiki.php.net/rfc/trailing_comma_in_parameter_list


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/f956015c-0552-3960-77ba-6434e0c1ea89%40beccati.com.


Re: [VOTE] Core Committee Election

2020-01-13 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
>From Revive Adserver:

1. Enrico Zimuel
2. Korvin Szanto
3. Chris Tankersley
4. Massimiliano Arione
5. Ben Edmunds


Cheers

On 10/01/2020 09:42, Alessandro Lai wrote:
> Hello everyone,
> as specified in the previous thread
> (https://groups.google.com/d/topic/php-fig/te-IAmuZte0/discussion),
> yesterday at midnight UTC the nominations ended, and since today it's
> possible to vote for the renewal of the terms that are up for this
> elections.
> 
> We have *4 spots on the Core Committee* up for reelection; we also have
> one full-term spot for secretary but, since we have only one unopposed
> nomination for the secretary election, we will need to vote for the Core
> Committee positions only, for which we have five nominations (listed in
> chronological order of nomination):
> 
>  - Enrico Zimuel:
> https://groups.google.com/d/topic/php-fig/G9O263am5Bs/discussion
>  - Massimiliano Arione:
> https://groups.google.com/d/topic/php-fig/CXS_djlzI6E/discussion
>  - Korvin Szanto:
> https://groups.google.com/d/topic/php-fig/suq1VFu3N8Y/discussion
>  - Chris Tankersley:
> https://groups.google.com/d/topic/php-fig/O-qPhtb3li4/discussion
>  - Ben Edmunds:
> https://groups.google.com/d/topic/php-fig/xk6cHWzOr6s/discussion
> 
> Full information about the Core Committee vote and role is visible in
> the bylaws here:
> https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee
> <https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee>
> 
> *Who can vote?*
> As specified in the bylaws, any Project Representative or any
> participant in the PHP-FIG ML can vote on the CC elections. A ML
> participant is defined in the bylaws as follows:
> "Any individual that has posted a non-trivial message in the official
> PHP-FIG venue (mailing list, forum, etc.) at least five (5) times within
> the past calendar year as of the start of nominations [...] is eligible
> to vote on Core Committee candidates."
>  
> *When can you vote?*
> Voting will be open in this thread until January 23rd 23:59:59 UTC.
> 
> *How to vote*
> The voting system used is STV[1][2], so basically, there is no tactical
> voting possible (like with FPTP); vote for who you want, even if they
> are a less popular candidates as your vote will move down to a different
> candidate if you back an unpopular candidate who doesn't have enough
> votes; if a candidate is elected, their surplus votes are also
> re-allocated so you are not punished for backing popular candidates
> either. There is no quorum, you are of course entitled to not vote and
> it will not count as a missed vote on the voting sheet. Rank the
> candidates in order of preference for example:
> 
> 1. Luke
> 2. Leia
> 3. Anakin
> 4. Rey
> 5. Padmé
> 6. Finn
> 
> At the end of the voting phase I will be announcing the results, and all
> the newly elected (both CC members and secretary), as announced before.
> Thanks!
> 
> Alessandro Lai
> PHP-FIG Secretary
> 
> [1]: STV User-friendly Explanation
> https://www.youtube.com/watch?v=l8XOZJkozfI
> <https://www.youtube.com/watch?v=l8XOZJkozfI>
> [2]: https://en.wikipedia.org/wiki/Single_transferable_vote
> <https://en.wikipedia.org/wiki/Single_transferable_vote>
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/c9f56a7f-adf7-4b31-b5a9-65635560d104%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/c9f56a7f-adf7-4b31-b5a9-65635560d104%40googlegroups.com?utm_medium=email_source=footer>.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/fba15307-e7d9-59b5-8306-88bbda2a6a08%40beccati.com.


Re: [VOTE][CC][BYLAW] PSR evolution

2019-11-13 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
+1

thanks Alessandro!


On 11/11/2019 10:48, Alessandro Lai wrote:
> Hello everyone,
> after a long review phase of my PR and multiple fixes and amendments, I
> think it's now ready:
> 
> https://github.com/php-fig/fig-standards/pull/1195
> 
> The PR adds a new document that addresses the issue of upgrading the
> code of a PSR to leverage new language features. I started working on
> this draft after a long discussion here on the ML
> (https://groups.google.com/d/topic/php-fig/OyC3plRYhqg/discussion),
> after that the issue surfaced many times on our communication channels.
> 
> The PR has been reviewed by multiple parties, and I consider it now
> ready to be put to a vote. So I hereby call a bylaw vote, following our
> Voting Protocol:
> 
> https://www.php-fig.org/bylaws/voting-protocol/
> 
> THIS THREAD IS FOR VOTES OF THE CORE COMMITTEE ONLY; there will be
> another thread for Project Representative; any other message or "vote"
> will be ignored. As always, you can vote with a +1, +0 or -1, you will
> have a period of two weeks to cast your vote, so this will be closed
> after 23:59:59 UTC of Monday 25th.
> 
> There is a 50% quorum for this vote, and a 2/3 majority is required for
> it to pass.
> 
> Thank you.
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/c2879540-00c4-4dcd-b4d9-6c4fba50c8fc%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/c2879540-00c4-4dcd-b4d9-6c4fba50c8fc%40googlegroups.com?utm_medium=email_source=footer>.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/7987a403-abea-b29c-b8d2-4146d2987466%40beccati.com.


Re: [VOTE][PROJECTS][BYLAW] PSR evolution

2019-11-13 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
+1 from Revive Adserver

On 11/11/2019 10:49, Alessandro Lai wrote:
> Hello everyone,
> after a long review phase of my PR and multiple fixes and amendments, I
> think it's now ready:
> 
> https://github.com/php-fig/fig-standards/pull/1195
> 
> The PR adds a new document that addresses the issue of upgrading the
> code of a PSR to leverage new language features. I started working on
> this draft after a long discussion here on the ML
> (https://groups.google.com/d/topic/php-fig/OyC3plRYhqg/discussion),
> after that the issue surfaced many times on our communication channels.
> 
> The PR has been reviewed by multiple parties, and I consider it now
> ready to be put to a vote. So I hereby call a bylaw vote, following
> following our Voting Protocol:
> 
> https://www.php-fig.org/bylaws/voting-protocol/
> 
> THIS THREAD IS FOR VOTES OF PROJECT REPRESENTATIVES ONLY; any other
> message or "vote" will be ignored. As always, you can vote with a +1, +0
> or -1, you will have a period of two weeks to cast your vote, so this
> will be closed after 23:59:59 UTC of Monday 25th.
> 
> There is no quorum for this vote, and a 2/3 majority is required for it
> to pass.
> 
> Thank you.
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/fc771d51-13e8-411f-8b0e-eae400f92897%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/fc771d51-13e8-411f-8b0e-eae400f92897%40googlegroups.com?utm_medium=email_source=footer>.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/93916bc2-f394-06f0-70b5-97e65509724b%40beccati.com.


Re: [VOTE] [Accept] PSR-12 Extended Coding Style Guide

2019-08-06 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
+1

On 26/07/2019 18:10, Chris Tankersley wrote:
> Finally, after a very long review period and much discussion and
> tweaking, I think we are finally ready for the acceptance vote for PSR-12.
> 
> The specification can be found here:
> https://github.com/php-fig/fig-standards/blob/master/proposed/extended-coding-style-guide.md
> 
> And the meta document here:
> https://github.com/php-fig/fig-standards/blob/master/proposed/extended-coding-style-guide-meta.md
> 
> Thank you to everyone involved!
> 
> -- 
> Chris Tankersley
> http://ctankersley.com
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/CAL9n4XNXae2wfGbwERNEF-68M8cxrvxgeu%2BjKSdvb2HravQ%3D7w%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CAL9n4XNXae2wfGbwERNEF-68M8cxrvxgeu%2BjKSdvb2HravQ%3D7w%40mail.gmail.com?utm_medium=email_source=footer>.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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/738d6d1f-6728-3aec-7241-0bc2a461f063%40beccati.com.


Re: [VOTE] Core Committee Election

2019-05-14 Thread 'Matteo Beccati' via PHP Framework Interoperability Group

Hi everyone,

Revive Adserver votes:

1. Matteo Beccati
2. Larry Garfield
3. Beau Simensen
4. Matthew Weier O'Phinney
5. Woody Gilk
6. Adam Englander
7. Benni Mack


Cheers
--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/10196df7-a10e-4c40-74fc-617892b8d867%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [CC][NOMINATION] Matteo Beccati

2019-05-02 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
Hi Alessandro,

thanks for the nomination. Accepted!


Cheers

On 02/05/2019 17:04, Alessandro Lai wrote:
> I would like to nominate Matteo Beccati (@mbeccati) for the upcoming CC
> elections.
> 
> Matteo is a longstanding project representative in PHP-FIG for Revive
> Adserver, and he is constantly giving to the community through Grusp,
> the italian association that is behind all the italian PHP user groups
> and the PHPDay conference.
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To post to this group, send email to php-fig@googlegroups.com
> <mailto:php-fig@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/d2b01d08-74c0-427a-a53f-6783c1f4667d%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/d2b01d08-74c0-427a-a53f-6783c1f4667d%40googlegroups.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/a4878abf-f5e6-c722-7eeb-d9b5b927916e%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: PSR-9/10

2018-05-28 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
On 26/05/2018 18:17, Michael Cullum wrote:
> If you think you might be able to contribute and fit with one of the
> above categories then please get in touch through this thread or if
> you want to chat first, a private email or tweeting me
> (@michaelcullumuk) is also fine!

Please count me in. I've been personally dealing with the security
issues in Revive Adserver through its various names and iterations since
15+ yrs.


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/cc80f2c9-110c-1331-ba91-8afee1e686c8%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: PSR status update

2018-03-19 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
-fig/A5mZYTn5Jm8/8nqDCh5TBgAJ
> 
> <https://groups.google.com/forum/?fromgroups#!searchin/php-fig/PSR-17%7Csort:date/php-fig/A5mZYTn5Jm8/8nqDCh5TBgAJ>).
> 
> 
> The new PSR working group is:
> 
> - Editor: Woody Gilk
> 
> - Sponsor: Matthew Weier O’Phinney
> 
> - Members: Stefano Torresi, Matthieu Napoli, Korvin Szanto, Glenn
> Eggleton, Oscar Otero, and Tobias Nyholm.
> 
> The working group is currently looking at proposal and hope to have
> it ready to share for general review in the next two weeks.
> 
> 
>   PSR-18 (HTTP client)
> 
> Status: Draft
> 
> The working group is currently deciding on an upgrade path from
> HTTPlug. They have a proposal that they think will work which is
> being reviewed by a small group and once they’re happy with it that
> will be posted to the PHP-FIG for comments.
> 
> 
>   PSR-19? (Streams / Async)
> 
> Status: Pre-Draft
> 
> Currently on hold until Sara can make time in her schedule.
> 
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To post to this group, send email to php-fig@googlegroups.com
> <mailto:php-fig@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/5b4bac43-6d33-4064-9be5-2bdafd9bfaa1%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/5b4bac43-6d33-4064-9be5-2bdafd9bfaa1%40googlegroups.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/60c149d6-5a8c-ba13-ea9c-8d1f1e70800b%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE][Internals] Secretary election

2018-01-16 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
Mark Railton


on behalf of Revive Adserver


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/255a8c3d-1428-533b-65c6-7f0e244d9fea%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE] Secretary Election

2017-10-21 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
Hi,

1. Alessandro Lai
2. Margret Staples
3. Mark Railton


On 19/10/2017 23:17, Michael Cullum wrote:
> Hi all,
> 
> We've been attempting to get more nominations so this has been delayed a
> few times but we now have three candidates so we're rolling with it.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/9b60720c-4a4a-6a9a-b290-0815c35f22bf%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


[Secretary nomitation] Alessandro Lai

2017-09-25 Thread 'Matteo Beccati' via PHP Framework Interoperability Group
Hi everyone,

I hereby nominate Alessandro Lai (alessandro.la...@gmail.com) for the
position of FIG Secretary.

Alessandro is one of the coordinators of the Milan PHP user group. He's
trying to help the PSR-12 WG and would like do lend a hand with the
secretary role.


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/9be07895-4807-3b4e-d7ba-56164f1432f1%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Vote] [Member Projects] Membership Application: Phergie

2017-02-21 Thread Matteo Beccati
+0 from Revive Adserver

On 06/02/2017 16:57, Chris Tankersley wrote:
> It's been well past 2 weeks while having a discussion period on allowing
> Phergie as a member project, and here is the voting thread for Member
> Projects.
> 
> Please vote with a -1/0/+1, like normal.
> 
> Discussion
> Thread: 
> https://groups.google.com/forum/?!topic%2Fphp-fig%2Fbz9sr8q8yHI#!topic/php-fig/bz9sr8q8yHI
> 
> I'll be creating a separate thread for the Core Committee vote. 
> 
> -- 
> Chris Tankersley
> http://ctankersley.com
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To post to this group, send email to php-fig@googlegroups.com
> <mailto:php-fig@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/CAL9n4XPvga9mrSc5R8-EqkfNfyqqaDAG_U6D_7kyx1A%2Bn-Ff%2BA%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CAL9n4XPvga9mrSc5R8-EqkfNfyqqaDAG_U6D_7kyx1A%2Bn-Ff%2BA%40mail.gmail.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/e85bf649-99ac-57a7-2771-f0d13f5dbabb%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE][Accept] PSR-16: Simple Cache

2016-12-29 Thread Matteo Beccati
+1 from Revive Adserver

On 18/12/2016 16:25, Jordi Boggiano wrote:
> After a fruitful month of review and final tweaks (thanks to all
> involved), I think we are ready for a vote here at the PSR-16 headquarters.
> 
> Please find the specification here:
> 
> -
> https://github.com/php-fig/fig-standards/blob/1d4f586d0bbe7e30cf8972268be8cef9d321fdcc/proposed/simplecache.md
> 
> 
> And the meta document:
> 
> -
> https://github.com/php-fig/fig-standards/blob/1d4f586d0bbe7e30cf8972268be8cef9d321fdcc/proposed/simplecache-meta.md
> 
> 
> There are currently 37 voting member projects, which means we must
> have 13 votes to pass quorum, with half or more of all votes cast in
> favor, in order to approve acceptance of PSR-16.
> 
> Voting starts now (Dec 18th 15:25 UTC) and will therefore run until
> January 1st, 15:25 UTC - so we can hopefully start the year on a good
> note ;)
> 
> Best Regards and Merry Christmas while I am at it,
> Jordi
> 


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/b44d2b4c-010d-c52b-98ac-31d7ff961bca%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE] First Core Committee Elections

2016-12-12 Thread Matteo Beccati
Hi,

here are my votes:

Sara Golemon
Lukas Kahwe Smith
Matthew Weier O’Phinney
David Négrier
Beau Simensen
Stefano Torresi
Gary Hockin
Korvin Szanto
Graham Daniels
Samantha Quiñones
Michael Heap
Larry Garfield
Jeremy Coates
Jason Coward
Marc Alexander
Chris Tankersley
Cees-Jan Kiewiet
Steve Winter
Tobias Nyholm
Same Minée


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/08ee2b1b-aa78-7f35-4df2-c2f731c46ab2%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [REVIEW] PSR-16 Simple Cache

2016-11-23 Thread Matteo Beccati
Hi Jordi (et al.),

nice job!

Tbh I was a bit surprised as I haven't seen any discussion about it at
all after the entrance vote and I wasn't aware of it being worked on
anywhere outside this ML. My fault, as I've probably missed that
communication and didn't check or ask around.

That said, below are my major gripes with it, inherited from PSR-6.

I understand where "MUST treat an item as expired once its Expiration
Time is reached" comes from, and I would agree, but for a cache it makes
little sense to be so strict and adamant about it. An entry that has a
TTL of 30 seconds is probably going to be fine at 31s too, especially if
expiration can't be expressed as a point in time.

Relaxing that would allow implementations to conform to the PSR-6
interface and adding stampede protection the same way apc(u) / squid do,
i.e. returning a slightly stale item while a single process is updating
the cache.

Not a deal-breaker, but "SHOULD treat an item as expired" can be
implemented as "always treat..." if anyone so desires, whereas the
opposite is not possible.

Other than that, I also am not very fond of null meaning either never or
some unspecified default value. A library would be forced to pick one as
there's no way to set an item to never expire if a default is available.
I personally like being able to specify a default TTL, but I would trade
that in exchange for something cleaner and clearer.

Alternatively, I'd suggest adding something like
CacheInterface::setDefaultTTL() and CacheInterface::TTL_NEVER = -1, with
support for the latter being subject to the actual storage capabilities.


Cheers


On 16/11/2016 15:22, Jordi Boggiano wrote:
> Heya,
> 
> We believe PSR-16, Simple Cache, is now ready for final review. As
> coordinator, I hereby open the mandatory review period prior to a formal
> acceptance vote; voting will begin no earlier than December 1st, 2016.
> 
> Here are links to the most current version and its meta document:
> 
> https://github.com/php-fig/fig-standards/blob/1cf169c66747640c6bc7fb5097d84fbafcd00a0c/proposed/simplecache.md
> 
> 
> https://github.com/php-fig/fig-standards/blob/1cf169c66747640c6bc7fb5097d84fbafcd00a0c/proposed/simplecache-meta.md
> 
> 
> 
> The package containing the interfaces is there:
> 
> https://github.com/php-fig/simplecache
> 
> 
> The latest important changes to the interfaces can be found at:
> 
> https://github.com/php-fig/simplecache/releases/tag/0.2.0
> 
> 
> And FWIW, Scrapbook already provides a PSR-16 implementation in its
> upcoming release:
> https://github.com/matthiasmullie/scrapbook/blob/master/src/Psr16/SimpleCache.php
> 
> 
> 
> Thanks for your time reviewing!
> 
> Cheers
> 


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/5ed473d6-0d38-6da9-4b0a-7fe1bcbe0641%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


[CC][Nomination] Stefano Torresi

2016-11-15 Thread Matteo Beccati
Hi,

I hereby nominate Stefano Torresi for the FIG CC. He has proved to be
very passionate about FIG, both on the ML and in person, and I think he
would make a good CC member.

A few words of introduction from him:

> I thought there was no room for a low-profile peer like me, I'm aware
> I'm not a well known face in the PHP community, but so far I did what
> I could as an observer, and given that I lurk the list pretty
> consistently and that we're short of candidates, I figured I could
> try and have more of a impact on the FIG initiative. Regarding my
> credentials, I have an academic CS background and I've been working
> as a full-stack web developer for more than ten years. I also
> co-founded my local PHP User Group in my hometown, Catania, with the
> patronage of the GrUSP (the italian association of PHP user groups). 
> I am not really affiliated with any particular project (although Zend
> Framework is probably the most notable among the projects I
> contribute to), so perhaps I could give a broader point of view,
> closer to the generic end user rather than to the framework
> developer.


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/5b3a14d4-dd43-66af-2f1a-0a519d148b1b%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Internals][FIG 3.0] Extending Nomination Period & Delaying FIG 3.0 Transition

2016-11-10 Thread Matteo Beccati
+1 from Revive Adserver


On 09/11/2016 18:08, Michael Cullum wrote:
> Hi all,
> 
> Does anyone have any objections to extending the Core Committee
> nomination period one month and pushing the FIG 3.0 implementation
> timetable back a month (so the new implementation date will be 1st
> February)?
> 
> There are still a number of people looking to be nominated or
> considering standing; meanwhile right now we only have 7 candidates when
> 15-20 would be a much more appropriate number for a fair election and we
> think at least 12 at a minimum is still achievable if given a little
> more time.
> 
> --
> FIG Secretaries
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To post to this group, send email to php-fig@googlegroups.com
> <mailto:php-fig@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/CAAqcDMhSgM3qMZAnV9674xuLuLF3YQtx_otOv53ANJHsk%2Bq%2B7Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CAAqcDMhSgM3qMZAnV9674xuLuLF3YQtx_otOv53ANJHsk%2Bq%2B7Q%40mail.gmail.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/00b3fc3a-0262-f1b1-110c-48dbb449f90a%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE][Accept] PSR-13: Link Definition Interfaces

2016-11-07 Thread Matteo Beccati
+1 from Revive Adserver

On 31/10/2016 22:15, Matthew Weier O'Phinney wrote:
> Per the by-laws, the required review period has passed for the
> proposed standard PSR-13 (Link Definition Interfaces). No changes have
> been made in the past two weeks since re-opening the review period.
> 
> The specification is here:
> 
> - 
> https://github.com/php-fig/fig-standards/blob/a47c644f9d0f914bb0a9777eeaec157f2d51dbff/proposed/links.md
> 
> And the meta document is here:
> 
> - 
> https://github.com/php-fig/fig-standards/blob/a47c644f9d0f914bb0a9777eeaec157f2d51dbff/proposed/links-meta.md
> 
> As coordinator, as of 21:20 UTC, I hereby open voting to accept the
> proposed standard.
> 
> There are currently 37 voting member projects, which means we must
> have 13 votes to pass quorum, with half or more of all votes cast in
> favor, in order to approve acceptance of PSR-13.
> 


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/bb103307-6f4a-79b6-ec79-ed12b96be5f7%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: Output escaping PSR

2016-10-06 Thread Matteo Beccati
Hi,

On 06/10/2016 09:53, Alessandro Lai wrote:
> Maybe the aim of this PSR should be a test suite (or at least a data
> provider of common and edge cases for tests) instead of an interface: if
> your escaper pass all the tests, it's PSR-x compliant. 
> 
> This could be a really good standard, which any implementer can look up
> to to see if its implementation is up to the task.

Still, I don't think it's a suitable goal for a PSR. We'd be defining
the output of an implementation, which is more or less like providing
one. What would be the benefit?


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/72db76f6-f790-fa4e-3b09-f901221f7027%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Important] [Internals] All projects must declare intention to remain members

2016-10-04 Thread Matteo Beccati
Revive Adserver remains.


On 03/10/2016 01:43, Michael Cullum wrote:
> As per the FIG 3.0 bylaws, all member projects must, between the 1st
> October and 31st October, declare they wish to remain a member project
> of the FIG. If you don't wish to remain, then it would be useful for you
> to also state this so we don't chase you up on it. Project reps, simply
> reply to this topic if you wish to remain.
> 
> I'd note that with FIG 3.0; there is much less of a burden/requirement
> for project reps to put time into FIG efforts, but of course remaining
> ensures you can still have a main seat at the table in deciding who
> steers the FIG and assurance to be involved in any PSRs that are
> relevant to your project and you can of course continue to be as
> actively involved (or more so) than presently too.
> 
> Should any old member projects who have previously left wish to re-join
> the FIG due to the new lower requirement on activity, I imagine in
> January there will be a combined vote for new member projects.
> 
> Many thanks,
> The Secretaries
> 
> -- 
> 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
> <mailto:php-fig+unsubscr...@googlegroups.com>.
> To post to this group, send email to php-fig@googlegroups.com
> <mailto:php-fig@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/CAAqcDMhL7F2PGfKoASNUDAFuLe3LcRUYYOyp7T-UfqVdQWoFpA%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CAAqcDMhL7F2PGfKoASNUDAFuLe3LcRUYYOyp7T-UfqVdQWoFpA%40mail.gmail.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout.


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/b6445654-f7bb-bc4c-e03a-0cedbe2674b6%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE] "FIG 3.0" Bylaw amendments (Take 2)

2016-09-28 Thread Matteo Beccati

Hi,

+1 from Revive Adserver


On 17/09/2016 01:14, Larry Garfield wrote:

I hereby open a vote for the following bylaw changes, colloquially known
as "FIG 3.0".  I'm fairly certain anything that needs to be said has
been said by now by all parties.

https://github.com/php-fig/fig-standards/pull/752

The vote will be open for 2 weeks, closing on 30 September 2016.

As usual, the vote is open to voting representatives only and is a
simple +1/-1 vote.

--Larry Garfield




--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/7aa59a03-ca9b-8e35-0d03-e56259e3c155%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE] PSR-6 Errata

2016-09-07 Thread Matteo Beccati

On 05/09/2016 17:39, Larry Garfield wrote:

Hm.  Well, I had been planning to offer an alternate vote on using
InvalidArgumentException should the first one fail, as that was the most
likely objection.  However, if the vote didn't even meet quorum then I
don't know if it's even worth doing that.


I'll add my voice to the count. Let's offer the alternate vote, please.



Hopefully should FIG 3 pass the Core Committee can take up this question
more effectively, but I don't know that there's a reason to bother if
we're not even going to make quorum.


TBH, I find this a bit scary. In fact if FIG 3's Core Committee was 
already in place, there's a chance the Errata would have passed in the 
current form. :-|



Cheers
--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/8fa21eae-055a-75b4-cef3-52c693abfe6a%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE] [Bylaw Amendment] Do not require interface suffix on future PSR Interfaces

2016-09-05 Thread Matteo Beccati

Hi,

-1 from Revive Adserver



On 04/09/2016 18:26, Michael Cullum wrote:

Hi all,

The PSR-11 Editors have requested we open this vote for them as they are
unable to do so not being voting members.

*Status Quo:* The bylaw states that all interfaces in PSRs published by
the PHP FIG must have the interface name suffix of 'Interface' e.g.
`LoggerInterface`
*Change:* The proposed change is that we no longer require that
interfaces are suffixed by 'Interface' so `ContainerInterface` would
become `Container`

Arguments for/against and [two
week] *discussion*: http://bit.ly/interface-suffix-discussion
*Pull request for bylaw change*: http://bit.ly/interface-suffix-pr

Note: This will only affect future PSR production (of PSRs in draft or
not yet through an entrance vote) so will not break or change any
current PSRs. It is also not a standard or recommendation for the PHP
community or member projects, but an internal bylaw on how we name
interfaces in our own interfaces in PSRs.

Voting will close in two weeks on the 18th September at 23:59 UTC.
Voting is available to voting members and may be cast as +1 (For), -1
(Against) or 0 (Abstain).

--
Many thanks,
Michael Cullum

--
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
<mailto:php-fig+unsubscr...@googlegroups.com>.
To post to this group, send email to php-fig@googlegroups.com
<mailto:php-fig@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/php-fig/CAAqcDMh4JSN1Opsiam8GgjXc1vsTfSuFJ7fEJvtoRoxBxRv_xQ%40mail.gmail.com
<https://groups.google.com/d/msgid/php-fig/CAAqcDMh4JSN1Opsiam8GgjXc1vsTfSuFJ7fEJvtoRoxBxRv_xQ%40mail.gmail.com?utm_medium=email_source=footer>.
For more options, visit https://groups.google.com/d/optout.



--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/84338df0-19df-cb1b-2d49-f27b7d4fc8f8%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE] PSR-6 Errata

2016-08-21 Thread Matteo Beccati

-1 from Revive Adserver.

I feel that failing with an E_USER_ERROR that can't be caught is an even 
bigger API change. Almost evil, I would say.



On 19/08/2016 20:43, Larry Garfield wrote:

I hereby open a vote for the following Errata for PSR-6:

https://github.com/php-fig/fig-standards/pull/787

Basically, it's a vote to merge that PR.

The vote will be open for 2 weeks, closing on 2 September 2016 @ 23:59 UTC.

As usual, the vote is open to voting representatives only and is a
simple +1/-1 vote.

I definitely appreciate the point that an InvalidArgumentException would
have been better, and had this issue been brought up during the Review
phase I'd probably have gone that direction.  However, adding an
exception does count as an API change, albeit a small one, so I am not
comfortable with that direction in an Errata. (Obviously if you feel
that this is a bad decision, vote -1.)

--Larry Garfield




--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/bbb4657b-be65-84ac-1a0a-284548bb5bbf%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE] Secretary Election August 2016

2016-08-16 Thread Matteo Beccati
ion on the web visit
https://groups.google.com/d/msgid/php-fig/CAAqcDMgTF_AX2-znS%2BMu9-Bk8aCcq1xfqYnr9-EN03q1YQXjnQ%40mail.gmail.com
<https://groups.google.com/d/msgid/php-fig/CAAqcDMgTF_AX2-znS%2BMu9-Bk8aCcq1xfqYnr9-EN03q1YQXjnQ%40mail.gmail.com?utm_medium=email_source=footer>.
For more options, visit https://groups.google.com/d/optout.



--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/ea47d3c4-3fc7-cc04-bf0f-257a06fac05b%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: A message from the Zend Framework CR team

2016-08-02 Thread Matteo Beccati

Hi Gary,

On 01/08/2016 17:50, GeeH wrote:

It was agreed as a group, that voting +1 for the replacement of Paul was
inherently pointless, as removing Paul as the voting representative is a
moot action resulting in no perceptible change to the situation. As
Matthew was one of the public complainants, it should be obvious that as
a team we still feel that there was a problem with Paul's behaviour. In
effect, we disagree with Paul's expulsion as a voting representative,
but still feel there is a problematic situation on the mailing list. We
also believe that expelling someone should be a last resort when
mediation has failed and that while mediation was attempted, it was not
done in a meaningful way with clear goals.


I was planning to write an email to explain the reasons behind my vote, 
but I couldn't have found better words to express my own feelings about it.



Cheers
--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/aa9e2dad-149f-a228-b0a2-b9b974bfa891%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Cache] Errata regarding \DateTimeInterface

2016-08-01 Thread Matteo Beccati

Hi Larry,

On 31/07/2016 20:29, Larry Garfield wrote:


I have pushed another commit to the PR that updates the recommended
handling per Bret's suggestion.

If no one objects by mid-week or so, I will call a vote on this errata.



I still haven't seen any replies to my objection re: null input. I don't 
think the PR is ready for voting just yet.



Cheers
--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/9b23bb78-3707-9fe0-0cd4-2594f18e5e1a%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Vote] Require Aura project to replace its representative

2016-07-29 Thread Matteo Beccati

Hi,

-1 from Revive Adserver


On 29/07/2016 01:56, Samantha Quiñones wrote:

All,

The discussion period having concluded, I am now opening a vote on the matter 
of the proposal to require the Aura project to name a new voting representative.

The discussion thread is available here: 
https://groups.google.com/d/msg/php-fig/w38tCU4mdgU/R1oyiIMuAAAJ

To summarize, I am opening this vote at the request of a number of voting 
representatives who have asked that this matter be taken up under the Voting 
Representatives section of the Membership Bylaw, the full text of which is 
located here: http://www.php-fig.org/bylaws/membership/#voting-representatives. 
The relevant section of the bylaw is as follows:

"If, in the judgement of PHP-FIG, a Voting Representative is acting inappropriately 
and to the detriment of PHP-FIG's ability to meet its objectives, a vote may be taken to 
request a replacement Voting Representative in accordance with the Voting Protocol bylaw 
or to expel the Member Project where replacing a Voting Representative is not 
possible."

A vote of +1 is a vote for requiring the Aura project to name a new voting 
representative.

A vote of -1 is a vote against requiring the Aura project to name a new voting 
representative.

If the motion passes, the current voting representative (Paul M. Jones) will be 
removed as the listed voting representative for the Aura project. The Aura 
project may then name a new representative in the usual fashion. If the project 
fails to name a new representative, it is subject to expulsion under the bylaws.

If the motion fails, the Aura project will not be required to name a new 
representative.

This vote will proceed according the Voting Protocol and will close on 
11-August-2011 at 23:59 UTC.

To further clarify, this vote is not a vote to ban Paul M. Jones from 
participation in the FIG, only to request the Aura project to name a new voting 
representative. Further, this vote is not about whether you like or dislike 
Paul, but if you believe that he has acted in a way detrimental to the FIG.

I want to make it explicitly and unequivocally clear that the purpose of this 
thread is for qualified voting members to vote on the matter at hand. This is a 
very sensitive issue and I will not tolerate discussion or flaming in this 
thread. I ask that all participants please respect Paul's dignity, as well as 
the dignity of the FIG, and refrain from personal attacks or other disruptive 
or divisive behavior. There are human beings involved in absolutely every step 
of this process and I further ask you to give one another the benefit of the 
doubt and operate from the assumption that others are working as hard for the 
success and advancement of the FIG as you are.

If you have any questions about this vote, please direct them to info [at] 
php-fig.org.

Thank you for your participation,
Samantha Quiñones, Secretary




--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/dd617360-cf0b-eb9c-9442-a769c090f26b%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [PSR-17] Any help needed? When do we move forward?

2016-07-29 Thread Matteo Beccati

Hi Woody,

On 28/07/2016 17:22, Woody Gilk wrote:

On Thu, Jul 28, 2016 at 10:19 AM, Paul Jones <pmjone...@gmail.com
<mailto:pmjone...@gmail.com>> wrote:
To be clear, this is at the editor's discretion; nothing else
impedes "progress."

That's an interesting way to put it Paul, since you know full well why
progress has stalled and what could be done to allow it to continue.


I hope you don't mind me asking. How is the current sponsor actively 
impeding technical progress?



Cheers
--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

--
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/249b7a37-a9df-ea21-bf2a-7cd9eac95365%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Cache] Errata regarding \DateTimeInterface

2016-07-27 Thread Matteo Beccati
Hi,

On 26/07/2016 23:36, Brent Shaffer wrote:
> assert issues a warning or exception based on your "assert"
> configuration. If the goal is to mimic a type check, we could *actually*
> mimic a type check and use E_RECOVERABLE_ERROR in PHP 5 and throw
> TypeError in PHP 7. But we aren't doing this, so using "assert" does not
> mimic a type check. Since the PHP documentation says to not use
> "assert", and it essentially issues a warning anyway, why not just issue
> a WARNING without assert?

I agree that using assert() is a fairly weird and I would vote against it.

Also I would expect to be able to pass a null value in order to reset
the expiration to (never|the default). That's in fact supported:

"If null is passed explicitly, a default value MAY be used..."


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/49abda91-fb26-20a5-9827-0b6380d6dec2%40beccati.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE] Membership Application: pimcore

2016-07-19 Thread Matteo Beccati
Hi,

+1 from Revive Adserver.



On 18/07/2016 16:00, Lukas Kahwe Smith wrote:
> Aloha,
> 
> So given that there didn’t see to be any opposition (then again also no 
> support by-side me) for the adoption of pimcore in the original thread 
> requesting for addition to the member list, I am not calling for a formal 
> vote on the matter. The intended representative is Bernhard Rusch who is part 
> of the core team.
> 
> Voting members only, just +1/-1/abstain please.
> 
> For reference here is the link to said original thread:
> https://groups.google.com/d/msg/php-fig/7qcqblUe2hk/Gtl_0gG1EgAJ
> 
> regards,
> Lukas Kahwe Smith
> sm...@pooteeweet.org
> 
> PS: Here for quick reference the initial email:
> 
> Hi,
> 
> I would like to submit my application for membership on behalf of Pimcore.
> Pimcore is an open source CMF for building highly customized websites and 
> applications.
> 
> Link: http://pimcore.org/
> On Github: https://github.com/pimcore/pimcore
> 
> A little bit about myself: My name is Bernhard Rusch, I'm working with PHP 
> since 14 years and worked with many different products and frameworks during 
> that time, mainly in the area of content management and ecommerce.
> We started pimcore 6 years ago with the mission to make enterprise web 
> content management easier for developers and editors.
> 
> Thank you for your consideration.
> 
> Bernhard Rusch
> https://github.com/brusch
> 
> 
> 


-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/

-- 
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 post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/a6b98732-6cf1-4efc-4021-5435acb930af%40beccati.com.
For more options, visit https://groups.google.com/d/optout.