That actually makes my comments more relevant. There is a closed room that has no archive?!
--
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/53887094-9b3d-4e6c-9dc1-8e75d9dddeb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAGOJM6J0Y4cgsc6Hg_UGbpwRs8SJ0Ma_xQD-yojr9ELiBwpFeg%40mail.gmail.com.
the actual channel on freenode is #phpfig and it is public
--
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/CAFojS1v2ZtFhywy_UUoBp-MUhdim8RYmxUkn3WHAtgLRfANqvg%40mail.gmail.com.
May 29, 2016 at 4:55 AM
That actually makes my comments more relevant. There is a closed room that has no archive?!
----
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/CAGOJM6J0Y4cgsc6Hg_UGbpwRs8SJ0Ma_xQD-yojr9ELiBwpFeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
May 28, 2016 at 10:17 PM
out of interest, the #php-fig channel on freenode is invite only.--
On Saturday, May 28, 2016 at 12:41:23 PM UTC-4, Woody Gilk wrote:
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/53887094-9b3d-4e6c-9dc1-8e75d9dddeb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
May 29, 2016 at 6:45 AM
Hi Jason.
It's a chat. There usually isn't a reason for a log. If the participants
in a chat think that their recent contributions are so important that it
should be preserved for future reference, the relevant part of the chat
is usually copied and preserved somewhere else.
Technicaly it is no problem to start logging a chat right away, but the
main question for me still is: Why do you think that it might as well
not exist if there are no logs?
Cheers
Andreas
May 29, 2016 at 6:31 AM
If there are no logs, it might as well not exist.
May 29, 2016 at 5:15 AM
the actual channel on freenode is #phpfig and it is public
--
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/CAFojS1v2ZtFhywy_UUoBp-MUhdim8RYmxUkn3WHAtgLRfANqvg%40mail.gmail.com.
If people want we (the secretaries) will be happy to look into implementing some kind of irc logging solution (suggestions welcome) but the general unwritten rule is that discussions on irc should be summarised elsewhere afterwards if they are important.
--
Michael
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/b32e715e-3b3b-05eb-f7c4-a472f900ce53%40beccati.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAAqcDMhf%2BFTmzPryPTVz6Q-oSpioYd%2B0jMWFqdRgKKGu08W56g%40mail.gmail.com.
Yes, some people who have gotten involved in FIG more recently are going to GitHub. We direct them back here.
PSA: If you're doing major discussion in a GitHub PR, you're doing it wrong. The secretaries have been and will continue to lock GitHub threads to prevent that, because we do not want to have the conversation split.
For example, until this thread I had NFI where any of the container work
was happening, just that there's occasionally a blog post about stuff
that's happened that I have no visibility into at all. There's no
discoverability for those who want to get involved. That's why we have
said, repeatedly, that such discussions belong here, on the list. If we
get too much technical activity (it would be a blessing), then we should
spin up dedicated lists for each WG that we can also advertise. (A few
topics had these in the past.)