Fennic: Thanks for the encouragement. I'm glad you're seeing value in it!

Rob: We'll see if this thread ends up in the final script, haha. "And this
week's human interest story: some dink named Len is asking everyone for
their social media handles"

On Tue, Jul 21, 2026 at 7:58 AM fennic log <[email protected]> wrote:

> Hi Len,
>
> First off, Great work, I appreciate your effort to glean more
> visibility into the goings on in the internals of PHP and you have a nice
> presentation style for your videos and a soothing voice.
>
> Secondly, anything you read from me, simply refer to as [fennic](
> https://en.wikipedia.org/wiki/Fennec_fox).
>
>
> On Tue, 21 Jul 2026 at 01:27, Rob Landers <[email protected]> wrote:
>
>>
>>
>> On Mon, Jul 20, 2026, at 23:43, Len Woodward wrote:
>>
>> Hi contributors,
>>
>> For the last 6 weeks or so, in an effort to make the PHP internals more
>> accessible and visible to a wider audience, I've been summarizing the
>> week's discussions into a ~10-15 minute weekly video, then breaking that
>> out into written content where it's supported, and threaded content for
>> other micro-blogging platforms.
>>
>> *I have two things to discuss:*
>>
>> 1. I'm trying to ensure that contributors are properly
>> tagged/attributed/[at]mentioned on all these platforms, but I just don't
>> have a well built-out list of all of your social handles. I've collected
>> some of these from the internals Discord and through web searches, but it's
>> not enough. To collect these handles for platforms like LinkedIn, Reddit,
>> Twitter, Bsky, Threads, Mastodon, etc, would it make more sense for you all
>> to *reply in this thread with all of your handles*, or should I create a
>> simple *Google Form* and link *that* instead?
>>
>> 2. To maintain accuracy, I want to include publishing the video link here
>> to the internals list as part of my publishing workflow each week. I hope
>> this provides an easy path for anyone who feels I've misunderstood or
>> misrepresented their messages to correct me, allowing me to include a
>> 'corrections and errata' segment in the videos. If we find that we're
>> having to do multiple corections each week, then I'll probably post the
>> first draft to the list and allow comments and corrections during an ~8hr
>> window *before* filming.
>>
>> ---
>>
>> The data cutoff is weekly at 10pm Vancouver time (UTC-7) each Tuesday
>> evening. First draft of the script is usually ready by 11:30 PM, and
>> filming generally starts at 9:30am the subsequent Wednesday morning.
>> Publishing is usually finished around ~5pm that same Wednesday. I'm working
>> hard to speed this up, but it's an iterative process.
>>
>> I'm going to include the link to last week's video here so that we can
>> address any necessary corrections, and I'll also a list of the platforms
>> where I posted it. If anyone has ideas for other platforms where this
>> visibility work might be appreciated, I'd love to know them. I've also been
>> submitting to laravel-news, and the phpweekly newsletter.
>>
>> youtube     https://youtu.be/cGNa33qGqEg
>> r/php
>> https://www.reddit.com/r/PHP/comments/1uxnmsp/this_week_in_php_internals_july_15_2026/
>> r/symfony
>> https://www.reddit.com/r/symfony/comments/1uxnuq0/this_week_in_php_internals_july_15_2026/
>> r/laravel
>> https://www.reddit.com/r/laravel/comments/1uxntqb/this_week_in_php_internals_july_15_2026/
>> dev.to
>> https://dev.to/projektgopher/this-week-in-php-internals-july-15-2026-4nhb
>> mastodon    https://phpc.social/@ProjektGopher/116926982520569384
>> threads     https://www.threads.com/@projektgopher/post/Da1bNf_lL-r
>> bsky        https://bsky.app/profile/projektgopher.com/post/3mqq27xvmac2s
>> twitter     https://x.com/ProjektGopher/status/2077559023998816461
>> linkedin
>> https://www.linkedin.com/feed/update/urn:li:share:7483325450434400256/
>>
>> Thanks everyone for your help and support (especially on Discord), and
>> I'm eager to keep this thing going.
>>
>> Cheers,
>> Len
>>
>>
>> You are going to include this email discussion in your video? right? :)
>>
>> — Rob
>>
>

Reply via email to