Re: [PSR-11] Question about PSR-11

2016-10-04 Thread Woody Gilk 
Why should a class name contain information that is present in the class
namespace? If you don't like the class name, there is the option to apply a
"use ... as ..." alias.

--
Woody Gilk
http://about.me/shadowhand

On Tue, Oct 4, 2016 at 7:26 PM, Stefano Torresi  wrote:

> Il giorno mer 5 ott 2016 alle ore 01:13 Sara Golemon  ha
> scritto:
>
>> My $0.02USD is that it should have DI in the name (i.e. DIContainer)
>>
>
> 100% agree, but I guess this ship has sailed... ;-)
>
> It occurs to my mind that, while most of the development of
> container-interop happened outside this list - so FIG members and
> bystanders may have not been involved as much as they could - on the other
> hand the editors have had the care to post regular updates here, with links
> to github, so anybody potentially interested has been given the chance to
> chime in.
>
> --
> 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/CAFojS1u6WEqGRr4i91vTSd5ohyMfuieqFySA8GsvPpaKr6NkhA%40mail.
> gmail.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/CAGOJM6%2BUU7WE%2Btfxj-NptKrJ%2BiiEHV8jCDQ%2B7hsM%3DbF_GSLXuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PSR-11] Question about PSR-11

2016-10-04 Thread Stefano Torresi 
Il giorno mer 5 ott 2016 alle ore 01:13 Sara Golemon  ha
scritto:

> My $0.02USD is that it should have DI in the name (i.e. DIContainer)
>

100% agree, but I guess this ship has sailed... ;-)

It occurs to my mind that, while most of the development of
container-interop happened outside this list - so FIG members and
bystanders may have not been involved as much as they could - on the other
hand the editors have had the care to post regular updates here, with links
to github, so anybody potentially interested has been given the chance to
chime in.

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

Re: Output escaping PSR

2016-10-04 Thread Korvin Szanto 
Hi Chris,
Are you thinking like a text filter PSR or more of an output management
PSR? It sounds like a single interface with a single method to me:
`FilterInterface::filter($mixed): mixed;`.

Thanks,
Korvin

On Tue, Oct 4, 2016 at 7:39 AM Chris Riley  wrote:

> Hi,
>
> I think there could be quite some value in producing a spec and set of
> interfaces for consistent output escaping across frameworks. Security is an
> important consideration in every app and having a consistent API would make
> it much easier get it right.
>
> Would like to hear peoples opinions on this and collect volunteers to join
> a working group.
>
> ~C
>
> --
> 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/4c634f36-bd9c-43d2-a387-90a47f4dad84%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/CANeXGWVgL22eBfb4aQeA1p2k1c5z6iNqnNyg%2BTg5uFG6xiBTuw%40mail.gmail.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 Ryan Thompson 
PyroCMS remains!

On Sunday, October 2, 2016 at 6:44:02 PM UTC-5, 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.
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/e6d1b014-d3f5-4cbe-b940-a3372616a9c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PSR-11] Question about PSR-11

2016-10-04 Thread David Négrier 
Hey Sara,

Actually, the name of the interface was the first issue we discussed when 
starting container-interop (the test-bed for PSR-11).

You can have a look at the Github issue that explains why we ended up with 
ContainerInterface here: 
https://github.com/container-interop/container-interop/issues/1 (and the 
results of the vote here: 
https://github.com/container-interop/container-interop/wiki/%231-interface-name:-Vote)

> I think the impedance mismatch here is that PSR-11 isn't about generic 
Containers, but rather about a specialization of Containers aimed at 
dependency injection.

Interesting. I think it is the first time this issue is raised. We use the 
term "Container" as a diminutive for "Dependency Injection Container" 
(because PSR-11 is definitely about DI containers). I think in the PHP 
world, the term Container mostly refer to DI containers (rather than the 
more general datastructure), but I might be wrong. Well, naming is hard! If 
you have a better alternative for the name, please feel free to make a 
suggestion, but we have been a lot to discuss about it and so far, and 
"ContainerInterface" has the very large majority of supporting votes.

> Further, it strikes me as more useful to have that generic container 
implementation in place, then define a DI model based around it, since the 
containers presented here are obviously Map specializations.

Indeed, this is a specialization of a Map, but if we ever need an interface 
to describe a map, well... we could name it MapInterface, couldn't we?

-David

Le lundi 3 octobre 2016 23:06:06 UTC+2, Sara Golemon a écrit :
>
> On Monday, October 3, 2016 at 10:54:30 AM UTC-7, Pedro Cordeiro wrote:
>>
>> Anyway, how do I prepare my application to have interoperable containers, 
>> since they don't agree on how to add new services? I will have to write 
>> adapters for each specific implementation... doesn't that defeat the 
>> purpose of the PSR? Shouldn't "adding services" be in-scope, rather than 
>> 'let some implementations rely on autowiring, others have specific methods 
>> for registering'...?
>>
>>>
> I think the impedance mismatch here is that PSR-11 isn't about generic 
> Containers, but rather about a specialization of Containers aimed at 
> dependency injection.  From that point of view, I think the has/get 
> limitation makes more sense, but I personally would like to see the 
> interfaces named in a way which more precisely reflects that use case 
> scenario so that we leave the door more open to generic container 
> interfaces (e.g. Vector, Set, Map type containers).  Further, it strikes me 
> as more useful to have that generic container implementation in place, then 
> define a DI model based around it, since the containers presented here are 
> obviously Map specializations.
>
> -Sara
>

-- 
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/93db7065-67d8-4cb9-822c-32345bb6f87d%40googlegroups.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
> .
> 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/CAAqcDMhL7F2PGfKoASNUDAFuLe3LcRUYYOyp7T-UfqVdQWoFpA%40mail.gmail.com
> .
> 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: [Important] [Internals] All projects must declare intention to remain members

2016-10-04 Thread Jan Schneider 

 Horde remains.

Zitat von Michael Cullum :

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.

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/CAAqcDMhL7F2PGfKoASNUDAFuLe3LcRUYYOyp7T-UfqVdQWoFpA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

-
Jan Schneider
The Horde Project
http://www.horde.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/20161004072800.Horde.7ogUjtAaunO5y-XBjf2FWHx%40neo.wg.de.
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 Robert Hafner 
Stash is out.

Rob


> On Oct 2, 2016, at 4:43 PM, 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 
> .
> 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/CAAqcDMhL7F2PGfKoASNUDAFuLe3LcRUYYOyp7T-UfqVdQWoFpA%40mail.gmail.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/2C12CBFE-61D5-4E66-B3BC-086A45687922%40tedivm.com.
For more options, visit https://groups.google.com/d/optout.