PowerShell
Update Community Call README.md
Update to indicate 30 min time slot for community call and process for requesting a demo slot.
When and why did the call get shortened to 30 minutes? The short time doesn't allow for much community feedback and discussion especially when there are a lot of announcements.
Thanks @ThomasNieto, we have been experimenting with a 30 minute call the past few months (since June), given that we were finding there was unstructured time on the call and we really value everyone's time. We always pause and ask for any questions/topics at the end of the call-- If there are particular topics that do spark constructive discussion we can often stay on/make a space to continue that discussion.
I will also say if we find 30 minutes isnt working, we can always switch back-- nothing is set in stone
I think that we should continue with an upto 1 hour call and perhaps move this to being split into the following format
1st 20 min- PS Team Driven Updates (like we currently have) 20-40min - Community Demo/s from then to 1hour - Community led topic conversations like user groups/conferences etc & any Issue triaging needs or general chat time
the last one would be useful to allow for community members to discuss together around any issues across not only the PowerShell owned repos but any PowerShell topics in general & perhaps add more clarity/context into issues like https://github.com/PowerShell/PowerShell/issues/15552 and https://github.com/PowerShell/PSResourceGet/issues/1494 where there are many moving parts to the bigger issue at play & also be a place where outside partners from wider Microsoft or community can post key updates in their modules (Graph/SharePoint/Exchange/Windows etc)
The 2nd would allow PS Team members to drop off the call if needed but stay if they wanted and catch up on post recording.
I'd been thinking about this sorta thing all year tbh & would be happy for all of 2025 to commit to hosting and managing that latter section if that would be agreeable @SydneyhSmith
Appreciate all the feedback-- sparking conversation about how we should think about the call etc. just as an fyi I am out most of the week for personal stuff so probably will not get back to you until sometime next week
Just chiming in here - we really value the PowerShell user group meetups that happen locally/regionally, which is the best place for demos and sharing to happen. If we do too much in the community call we could accidently reduce the value of those local events and we don't want that to be the case. The last handful of years has been really tough on user groups.
And of course - the team is always happy to virtually participate in the user group meetups!
