Re: [CC][Nomination Request] Sam Minnée

[Guy Marriott]

I have met Sam before within the Wellington NZ PHP community and also vouch
for him. Unfortunately I am also not a voting member

On Wed, Dec 7, 2016 at 5:16 AM, Christopher Pitt  wrote:

> Hi folks,
>
> I'd like to nominate Sam, but I'm not a voting member. Would anyone else
> like to? Sam is the original author, and a current core committer of the
> SilverStripe framework and CMS. He's a talented developer, an insightful
> project leader, and a wonderful human. Here's a bit of history, of the
> project and the company I'm proud to be a part of:
> https://www.silverstripe.com/who-we-are/history
>
> Kind regards
> Chris
>
> --
> 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/7a32f472-0a70-4bde-92c0-5651ce8e314f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAKD%3DPH%2Bi83_B7y6mAF2eNuourgR%3DGOiZR4OtV6%3D6hQe44_4U3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [CC] [Nomination Request] Beau Simensen

[Michael Cullum]

Great. Thanks both.

http://bit.ly/cc-election-candidates

--
M

On Tuesday, 6 December 2016 19:00:30 UTC+1, Chris Tankersley wrote:
>
> I hereby nominate Beau Simensen for the FIG CC. Beau has worked on many 
> different PSRs and has been an active community member in the past, 
> previously serving as the voting representative for Sculpin. He's been 
> involved in many different projects through the years and I think would be 
> a great addition to the core committee.
>
> -- 
> 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.
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/762cf857-84d4-4b13-b67b-bfceefd9ca25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [CC] [Nomination Request] Tobias Nyholm

[Michael Cullum]

Awesome. Thanks both.

http://bit.ly/cc-election-candidates

--
M

On Tuesday, 6 December 2016 18:55:28 UTC+1, Chris Tankersley wrote:
>
> I hereby nominate Tobias Nyholm for the FIG CC. He is the creator of 
> PHP-cache and co-creator of HTTPlug. His involvement in these projects show 
> his desire and commitment to work toward framework interoperability.
>
> https://github.com/Nyholm
> https://twitter.com/TobiasNyholm
>
> -- 
> 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.
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/56f4f442-05b8-42a7-a2ce-a500353e4736%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PSR-12]

[Rudolph Gottesheim]

I agree 100%.

In my opinion, the one-liner is far *more* obvious since we're so used to 
the short 
> Well for having worked on a few projects with strict types everywhere, I 
> am not sure. Yes in those projects I tend to ignore it, but that's mostly 
> because I know it's there anyway. The bottom line is it doesn't matter a 
> whole lot visually speaking I suppose. If you open a file and don't know if 
> it has strict types or not, the two following things are probably equally 
> obvious.
>
> [image: Inline images 1]
>
> vs 
>
> [image: Inline images 2]
>
> Same same, except we lose two lines for (I'd argue) nothing.. And IMO it 
> belongs with  how it changes the language.
>
> Anyway I guess it's too late and I won't change the outcome of this, but 
> for the record I have to say it: the day I open a class file and I can't 
> even see the `class` token, I shall weep.
>
> Cheers
> Jordi
>
> On 5 December 2016 at 20:54, Woody Gilk > 
> wrote:
>
>>
>> On Mon, Dec 5, 2016 at 12:30 PM, Larry Garfield > > wrote:
>>
>>> I'd say the opposite: My brain is already trained to ignore the >> line as noise, so anything added to that line WOULD be missed.
>>>
>>
>> Exactly this.
>>
>> --
>> Woody Gilk
>> http://about.me/shadowhand
>>
>> -- 
>> 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+u...@googlegroups.com .
>> To post to this group, send email to php...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/php-fig/CAGOJM6%2B_i-VXu1jtu_kj8pO2TonyKKdGmddXCA-U8-n-7FG75g%40mail.gmail.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Jordi Boggiano
> @seldaek - http://nelm.io/jordi
>

-- 
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/10e51ef8-dc11-4d59-96ee-60fbaae04454%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PSR-11] Review of the delegate lookup requirement level

[Matthieu Napoli]

Hi,

This is a good point. However there's a discussion about removing the 
delegate lookup entirely from PSR-11 
here: https://groups.google.com/forum/#!topic/php-fig/9YAFG4Xw2zo That 
would remove that issue I think.

Cheers
Matthieu

Le samedi 3 décembre 2016 18:10:16 UTC+1, Michael Mayer a écrit :
>
> The current version is very confusing:
>
>> 1.4 Additional feature: Delegate lookup
>> This section describes an additional feature that *MAY* be added to a 
>> container.
>> …
>> Implementation of this feature is therefore *RECOMMENDED*.
>
>
> From RFC 2119 :
>
>> 3. *SHOULD*   This word, or the adjective "*RECOMMENDED*", mean that 
>> there
>>may exist valid reasons in particular circumstances to ignore a
>>particular item, but the full implications must be understood and
>>carefully weighed before choosing a different course.
>> …
>> 5. *MAY*   This word, or the adjective "*OPTIONAL*", mean that an item is
>>truly optional.  One vendor may choose to include the item because a
>>particular marketplace requires it or because the vendor feels that
>>it enhances the product while another vendor may omit the same item.
>>An implementation which does not include a particular option MUST be
>>prepared to interoperate with another implementation which does
>>include the option, though perhaps with reduced functionality. In the
>>same vein an implementation which does include a particular option
>>MUST be prepared to interoperate with another implementation which
>>does not include the option (except, of course, for the feature the
>>option provides.)
>
>
>
> Thus, as an implementer, *MAY* or *SHOULD* I implement the delegate 
> lookup feature?
>
> Regards,
> Michael
>

-- 
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/9ca3fee6-614f-4912-92fe-906ddf71daf7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[CC] [Nomination Request] Chris Tankersley

[Chris Tankersley]

Like a few people before me, I'd like to request a nomination to the Core
Committee for FIG 3.0.

For those of you that don't know me, I've been an active member of the PHP
community for many years, speaking at conferences, blogging, etc on many
different topics for both programming and devops. I've been involved in a
few different projects, most notably Sculpin (of which I'm the current
project representative for FIG), and the PHP Mentoring Project, where I am
the lead developer for the website.

So, while I am a project representative, I am looking to the other
representatives to help sponsor my nomination.

Thank you all!

-- 
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.
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/CAL9n4XNN9s0C0FWKszK71961R1i1XpBZPWZvrD%2BjpfJuJ8fifA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [REVIEW] PSR-16 Simple Cache

[Matthew Weier O'Phinney]

On Tue, Dec 6, 2016 at 8:39 AM, Rasmus Schultz  wrote:
> Personally, I don't use a null-cache, ever.
>
> The problem with a null-cache, is that it's not actually a cache - it
> satisfies the interface, but doesn't behave like a cache, so it's not even
> useful for testing.
>
> I wrote this for testing where I have PSR-16 dependencies:
>
> https://github.com/kodus/mock-cache
>
> I've never had a use-case, test or otherwise, where a null-cache actually
> satisfied the requirement. I would never add caching to something that
> doesn't require caching, and if it requires caching, a null-cache isn't even
> a meaningful default. I honestly don't understand they're for, but maybe
> that's just me ;-)

It's a matter of architecture. In many systems I've used and studied,
classes may require a cache to the constructor. However, in
development mode, you may want to ensure the cache is never hit —
perhaps you do not have access to the appropriate cache server, or do
not want to worry about trampling the work other developers are doing,
etc. Alternately, you may want to ensure the business logic _must_ be
hit, instead of the cached results, so that you can trace code
execution. As such, having the ability to have a null cache injected
instead of a version backed by a data store can be quite useful.

> On Monday, December 5, 2016 at 7:02:42 PM UTC+1, Larry Garfield wrote:
>>
>> We've decided since PSR-3 that such "stock implementations" do not belong
>> in the spec, but can live in -util libraries.  A NullCache implementation of
>> PSR-6 / PSR-16 would be very welcome for cache-util.
>>
>> On 12/05/2016 11:47 AM, Alexander Ustimenko wrote:
>>
>> Another issue that we have now in current cache and cache-util is complete
>> missing of null-object.
>>
>> In Psr/Log we have NullLogger, why we can't have NullCache?
>>
>> There are situations, when we dont' know 100%, that there or here we need
>> cache. Or we know, that we need cache there, but for some time we can live
>> without it.
>>
>> Cache could be an optional dependency. It's a bitter thought, but it's a
>> truth. So I suggest to add to Psr/Simple cache default NullCache as just
>> /dev/null or BlackWhole implementation.
>>
>> Examples:
>>
>> https://github.com/symfony/cache/blob/master/Adapter/NullAdapter.php
>>
>> https://github.com/tedious/Stash/blob/master/src/Stash/Driver/BlackHole.php
>>
>> Same as https://github.com/php-fig/log/blob/master/Psr/Log/NullLogger.php
>>
>>
>> Use case
>>
>> Cache as an optional injectable dependency. When class user not provides
>> it -- we take ready NullCache and use it.
>>
>>
>> среда, 16 ноября 2016 г., 21:22:20 UTC+7 пользователь Jordi Boggiano
>> написал:
>>>
>>> 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
>>>
>>> --
>>> Jordi Boggiano
>>> @seldaek - http://seld.be
>>
>> --
>> 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+u...@googlegroups.com.
>> To post to this group, send email to php...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/php-fig/b67406ac-5227-456d-a7c3-f65523bf527d%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
> --
> 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/ddb02530-5460-4d90-95fa-53a7afc286f6%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Matthew Weier O'Phinney
mweierophin...@gmail.com
https://mwop.net/

-- 
You received this message because you are subsc

[CC] [Nomination Request] Tobias Nyholm

[Tobias Nyholm]

I'm happy to accept the nomination. 
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.
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/93c048a9-7074-4f70-9bef-b078406c2fce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PSR-12]

[Michael Sheakoski]

I have enjoyed reading everyone's viewpoints on this subject. In the end, 
it has reinforced that at least for my personal standard, https://groups.google.com/d/msgid/php-fig/8bc0a7de-86b1-41af-9137-68c422b11e60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [CC] [Nomination Request] Beau Simensen

[Beau Simensen]

On Tuesday, December 6, 2016 at 12:00:30 PM UTC-6, Chris Tankersley wrote:
>
> I hereby nominate Beau Simensen for the FIG CC. Beau has worked on many 
> different PSRs and has been an active community member in the past, 
> previously serving as the voting representative for Sculpin. He's been 
> involved in many different projects through the years and I think would be 
> a great addition to the core committee.
>

I accept. 

-- 
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/fc49d28d-550f-4470-9db5-8fa470f0a5f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[CC] [Nomination Request] Beau Simensen

[Chris Tankersley]

I hereby nominate Beau Simensen for the FIG CC. Beau has worked on many
different PSRs and has been an active community member in the past,
previously serving as the voting representative for Sculpin. He's been
involved in many different projects through the years and I think would be
a great addition to the core committee.

-- 
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.
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/CAL9n4XNqVafD2hd0BnL79g%3D76-ofQsW60rk5OpnYyfExNRMrSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Internals] Change to FIG 3.0 term lengths

[Lukas Kahwe Smith]

fine for me.

though I have no preference for or against this.

> On 06 Dec 2016, at 16:24, Michael Cullum  wrote:
> 
> Hi all,
> 
> It was noted by a few individuals that the way the bylaws stand about 
> fulfilling the initial 12 Core Committee roles as if there is a 12-member 
> vacancy this leads to a rather inefficient situation where some people would 
> have their terms expire in April/May of this year which I'm sure you all 
> agree is non-ideal as (1) they won't have time to settle in (2) CC elections 
> take time and focus away from working on specifications and two in such a 
> short period is relatively unhelpful.
> 
> However, a small change could help resolve this issue so I'm just asking if 
> anyone objects to us doing it slightly differently**
> 
> The old system would have involved the following three terms:
> Top four candidates term expires in: August 2018
> Next four candidates term expires in: January 2018
> Last four candidates terms expire in:  April 2017
> 
> My suggestion is to change it so they receive the following (slightly 
> extended terms so the minimum term is ~1 year and maximum is just over 2 
> years):
> Top four candidates term expires in: April 2019
> Next four candidates term expires in: August 2018
> Last four candidates terms expire in:  January 2018
> 
> Essentially, we just skip the first normal CC election and extend everyone's 
> term by a few months so that we stay on the defined calendar for future 
> elections.
> 
> --
> Many thanks
> FIG Secretaries
> 
> ** If there are more than a couple of objections from voting members then I 
> guess it will just be dropped as an entire vote to decide if we should do 
> this doesn't really help with the aim of reducing bureaucracy in this instance
> 
> --
> 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/CAAqcDMgEO2UdVnJyDvf1hT7rc3o4L3AX1oY99xJsGG8C%3D-FghQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

regards,
Lukas Kahwe Smith
sm...@pooteeweet.org



-- 
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/B8FED62F-AF83-405B-AE52-BBD6A109D7DE%40pooteeweet.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

[CC] [Nomination Request] Tobias Nyholm

[Chris Tankersley]

I hereby nominate Tobias Nyholm for the FIG CC. He is the creator of
PHP-cache and co-creator of HTTPlug. His involvement in these projects show
his desire and commitment to work toward framework interoperability.

https://github.com/Nyholm
https://twitter.com/TobiasNyholm

-- 
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.
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/CAL9n4XOPqtnxrZ9Ojv4FX1TQ6JbV%2BM68cbMiv666sMf0o-bK-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[CC][Nomination Request] Sam Minnée

[Christopher Pitt]

Hi folks,

I'd like to nominate Sam, but I'm not a voting member. Would anyone else 
like to? Sam is the original author, and a current core committer of the 
SilverStripe framework and CMS. He's a talented developer, an insightful 
project leader, and a wonderful human. Here's a bit of history, of the 
project and the company I'm proud to be a part of: 
https://www.silverstripe.com/who-we-are/history

Kind regards
Chris

-- 
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/7a32f472-0a70-4bde-92c0-5651ce8e314f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Internals] Change to FIG 3.0 term lengths

[Larry Garfield]

This sounds reasonable to me.  Thanks, Secretaries.

--Larry Garfield

On 12/06/2016 09:24 AM, Michael Cullum wrote:

Hi all,

It was noted by a few individuals that the way the bylaws stand about 
fulfilling the initial 12 Core Committee roles as if there is a 
12-member vacancy this leads to a rather inefficient situation where 
some people would have their terms expire in April/May of this year 
which I'm sure you all agree is non-ideal as (1) they won't have time 
to settle in (2) CC elections take time and focus away from working on 
specifications and two in such a short period is relatively unhelpful.


However, a small change could help resolve this issue so I'm just 
asking if anyone objects to us doing it slightly differently**


The old system would have involved the following three terms:
Top four candidates term expires in: August 2018
Next four candidates term expires in: January 2018
Last four candidates terms expire in:  April 2017

My suggestion is to change it so they receive the following (slightly 
extended terms so the minimum term is ~1 year and maximum is just over 
2 years):

Top four candidates term expires in: April 2019
Next four candidates term expires in: August 2018
Last four candidates terms expire in:  January 2018

Essentially, we just skip the first normal CC election and extend 
everyone's term by a few months so that we stay on the defined 
calendar for future elections.


--
Many thanks
FIG Secretaries

** If there are more than a couple of objections from voting members 
then I guess it will just be dropped as an entire vote to decide if we 
should do this doesn't really help with the aim of reducing 
bureaucracy in this instance

--


--
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/8d511fde-7a58-388b-7d3c-8e407b88326d%40garfieldtech.com.
For more options, visit https://groups.google.com/d/optout.

[Internals] Change to FIG 3.0 term lengths

[Michael Cullum]

Hi all,

It was noted by a few individuals that the way the bylaws stand about
fulfilling the initial 12 Core Committee roles as if there is a 12-member
vacancy this leads to a rather inefficient situation where some people
would have their terms expire in April/May of this year which I'm sure you
all agree is non-ideal as (1) they won't have time to settle in (2) CC
elections take time and focus away from working on specifications and two
in such a short period is relatively unhelpful.

However, a small change could help resolve this issue so I'm just asking if
anyone objects to us doing it slightly differently**

The old system would have involved the following three terms:
Top four candidates term expires in: August 2018
Next four candidates term expires in: January 2018
Last four candidates terms expire in:  April 2017

My suggestion is to change it so they receive the following (slightly
extended terms so the minimum term is ~1 year and maximum is just over 2
years):
Top four candidates term expires in: April 2019
Next four candidates term expires in: August 2018
Last four candidates terms expire in:  January 2018

Essentially, we just skip the first normal CC election and extend
everyone's term by a few months so that we stay on the defined calendar for
future elections.

--
Many thanks
FIG Secretaries

** If there are more than a couple of objections from voting members then I
guess it will just be dropped as an entire vote to decide if we should do
this doesn't really help with the aim of reducing bureaucracy in this
instance

-- 
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/CAAqcDMgEO2UdVnJyDvf1hT7rc3o4L3AX1oY99xJsGG8C%3D-FghQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [REVIEW] PSR-16 Simple Cache

[Rasmus Schultz]

Personally, I don't use a null-cache, ever.

The problem with a null-cache, is that it's not actually a cache - it 
satisfies the interface, but doesn't behave like a cache, so it's not even 
useful for testing.

I wrote this for testing where I have PSR-16 dependencies:

https://github.com/kodus/mock-cache

I've never had a use-case, test or otherwise, where a null-cache actually 
satisfied the requirement. I would never add caching to something that 
doesn't require caching, and if it requires caching, a null-cache isn't 
even a meaningful default. I honestly don't understand they're for, but 
maybe that's just me ;-)


On Monday, December 5, 2016 at 7:02:42 PM UTC+1, Larry Garfield wrote:
>
> We've decided since PSR-3 that such "stock implementations" do not belong 
> in the spec, but can live in -util libraries.  A NullCache implementation 
> of PSR-6 / PSR-16 would be very welcome for cache-util.
>
> On 12/05/2016 11:47 AM, Alexander Ustimenko wrote:
>
> Another issue that we have now in current cache and cache-util is complete 
> missing of null-object. 
>
> In Psr/Log we have NullLogger, why we can't have NullCache?
>
> There are situations, when we dont' know 100%, that there or here we need 
> cache. Or we know, that we need cache there, but for some time we can live 
> without it.
>
> Cache could be an optional dependency. It's a bitter thought, but it's a 
> truth. So I suggest to add to Psr/Simple cache default NullCache as just 
> /dev/null or BlackWhole implementation.
>
> Examples:
>
>- https://github.com/symfony/cache/blob/master/Adapter/NullAdapter.php 
>- 
>
> https://github.com/tedious/Stash/blob/master/src/Stash/Driver/BlackHole.php 
>
> Same as https://github.com/php-fig/log/blob/master/Psr/Log/NullLogger.php
>
> Use case 
>
> Cache as an optional injectable dependency. When class user not provides 
> it -- we take ready NullCache and use it.
>
> среда, 16 ноября 2016 г., 21:22:20 UTC+7 пользователь Jordi Boggiano 
> написал: 
>>
>> 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 
>>
>> -- 
>> Jordi Boggiano 
>> @seldaek - http://seld.be 
>>
> -- 
> 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+u...@googlegroups.com .
> To post to this group, send email to php...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/php-fig/b67406ac-5227-456d-a7c3-f65523bf527d%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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/ddb02530-5460-4d90-95fa-53a7afc286f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[CC Nomination Request] Marc Alexander

[Marc Alexander]

To all FIG representatives:

I hereby kindly request a nomination for the election to the FIG 3.0 Core 
Committee.

Let me tell you a few things about me:
I'm currently the project representative for phpBB and the phpBB lead 
developer. During my time at phpBB I've worked on various features from 
back-end features like password hashing to front-end features employing JS, 
jQuery, as well as employing commonly used libraries such as Symfony. I do also 
have a few smaller side projects that are for example used in phpBB like my 
fast-image-size library [1].
As day job I'm a software engineer at a small startup. During this time a 
mostly work on C++, Qt, and similar in order to write a robot simulation 
software which involves working on fast algorithmic solvers and visualization 
toolkits.

I did previously sponsor the now accepted PSR 13 and would like to contribute 
more to the FIG through the core committee. 

Thank you


[1] - https://github.com/marc1706/fast-image-size

-- 
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/222c3a40-39ea-435a-8982-e55fabfcc185%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [CC][Nomination] Michael Heap

[Michael Cullum]

Great. Thanks folks

https://gist.github.com/michaelcullum/9f5fd32efce27fb5517dd43bf814f16f

--
Michael C

On 6 December 2016 at 11:10, Michael Heap  wrote:

> Thanks Michiel, I accept the nomination
>
> On Tuesday, 6 December 2016 08:33:49 UTC, Michiel Rook wrote:
>>
>> I hereby nominate Michael Heap for the CC.
>>
>> regards,
>>
>> Michiel
>>
> --
> 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/89bd7664-ebf8-42d0-944e-0661fa1beaed%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAAqcDMhbDLuMyktATzsGnFj4ATzC%3DuAPo1%3DQ5j-goOfvAAAScA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [CC][Nomination] Michael Heap

[Michael Heap]

Thanks Michiel, I accept the nomination

On Tuesday, 6 December 2016 08:33:49 UTC, Michiel Rook wrote:
>
> I hereby nominate Michael Heap for the CC.
>
> regards,
>
> Michiel
>

-- 
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/89bd7664-ebf8-42d0-944e-0661fa1beaed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[CC][Nomination] Michael Heap

[Michiel Rook]

I hereby nominate Michael Heap for the CC.

regards,

Michiel

--
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/e99e8deb-f40f-bf0d-5866-45ae688191f5%40gmail.com.
For more options, visit https://groups.google.com/d/optout.