Skip to content

Commit 8033b77

Browse files
SteveL-MSFTSteveL-MSFT
authored
Merge pull request #231 from joeyaiello/SeptOctCommCall
Add Sept and Oct 2019 community calls
2 parents ec6a6f7 + 375a989 commit 8033b77

File tree

5 files changed

+617
-0
lines changed

5 files changed

+617
-0
lines changed

‎CommunityCall/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ recurring event on your calendar.
1212

1313
## Notes
1414

15+
* [October 17, 2019](./notes/20191017_Notes.md) ([YouTube recording](https://youtu.be/yL0FXyZQdmQ) and [transcript](./notes/20191017_ChatTranscript.txt))
16+
* [September 19, 2019](./notes/20190919_Notes.md) ([YouTube recording](https://youtu.be/T2D8FxvoS1g) and [transcript](./notes/20190919_ChatTranscript.txt))
1517
* [August 15, 2019](./notes/20190815_Notes.md) ([YouTube recording](https://youtu.be/cK1xenkF9zs) and [transcript](./notes/20190815_ChatTranscript.txt))
1618
* [July 18, 2019](./notes/20190718_Notes.md) ([YouTube recording](https://youtu.be/qwbbUqimtXA) and [transcript](./notes/20190718_ChatTranscript.txt))
1719
* [June 20, 2019](./notes/20190620_Notes.md) ([YouTube recording](https://youtu.be/yJF-O9tH89Q) and [transcript](./notes/20190620_ChatTranscript.txt))

‎CommunityCall/notes/20190919_ChatTranscript.txt

Lines changed: 230 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,230 @@
1+
Steve Lee (POWERSHELL)
2+
We are starting
3+
4+
Anonymous
5+
Hello :)
6+
7+
JB Lewis
8+
Hey folks!
9+
10+
JB Lewis
11+
Hey folks!
12+
13+
Roberth
14+
Timezones, ey?
15+
16+
Keith Hill
17+
Do you think && || will still make the cut for PS7?
18+
19+
Anonymous
20+
Hi @all
21+
22+
Michael B.
23+
is dispose{} in there?
24+
25+
Roberth
26+
Timezones, ey?
27+
28+
Keith Hill
29+
Do you think && || will still make the cut for PS7?
30+
31+
Michael B.
32+
is dispose{} in there?
33+
34+
Ayan
35+
Is the PowerShell Conference Asia 2019 being streamed online?
36+
37+
Adam
38+
When does support for 6.2 end?
39+
40+
Ayan
41+
Is the PowerShell Conference Asia 2019 being streamed online?
42+
43+
Adam
44+
When does support for 6.2 end?
45+
46+
Sergey Vasin
47+
Are we recording?
48+
49+
Christoph Bergmeister
50+
What about splatting using the @@ syntax for PS7?
51+
52+
Sergey Vasin
53+
Are we recording?
54+
55+
Joel Sallow
56+
Dispose isn't in 4. I'm waiting for approval on the RFC so I can finish the code work. It's basically done though.
57+
58+
Christoph Bergmeister
59+
What about splatting using the @@ syntax for PS7?
60+
61+
Christoph Bergmeister
62+
I have opened a PR for it
63+
64+
Keith Hill
65+
Literal splatting?
66+
67+
Joel Sallow
68+
Dispose isn't in 4. I'm waiting for approval on the RFC so I can finish the code work. It's basically done though.
69+
70+
Christoph Bergmeister
71+
https://github.com/PowerShell/PowerShell/pull/10073
72+
73+
Christoph Bergmeister
74+
I have opened a PR for it
75+
76+
Keith Hill
77+
Literal splatting?
78+
79+
Christoph Bergmeister
80+
https://github.com/PowerShell/PowerShell/pull/10073
81+
82+
Christoph Bergmeister
83+
But someone in the community has a concern about whether the RFC design nees to be re-reviewed. I'd like to get feedback and sign off on the implementation in the PR
84+
85+
Missy
86+
re: live stream for PSConfAsia, possibly here:
87+
https://livestream.com/gaelcolas/events/8824779
88+
89+
Christoph Bergmeister
90+
https://github.com/PowerShell/PowerShell/pull/10073#issuecomment-526969790
91+
92+
kvprasoon
93+
PSConfAsia - Mostly livestreamed from tmrw
94+
https://livestream.com/gaelcolas/events/8824779
95+
96+
Thomas Nieto
97+
What is the decision on the breaking change to remove support for variable names ending in "?" since analysis found only 70 unique variable names using that convention.
98+
99+
https://github.com/PowerShell/PowerShell/issues/3240
100+
101+
Missy
102+
re: live stream for PSConfAsia, possibly here: https://livestream.com/gaelcolas/events/8824779
103+
104+
kvprasoon
105+
PSConfAsia - Mostly livestreamed from tmrw
106+
https://livestream.com/gaelcolas/events/8824779
107+
108+
Missy
109+
re: live stream for PSConfAsia, possibly here: https://livestream.com/gaelcolas/events/8824779
110+
111+
Missy
112+
re: live stream for PSConfAsia, possibly here:
113+
https://livestream.com/gaelcolas/events/8824779
114+
115+
Christoph Bergmeister
116+
But someone in the community has a concern about whether the RFC design nees to be re-reviewed. I'd like to get feedback and sign off on the implementation in the PR
117+
118+
Christoph Bergmeister
119+
https://github.com/PowerShell/PowerShell/pull/10073#issuecomment-526969790
120+
121+
Joel Sallow
122+
I mean I'm pretty sure a fair few folks were saying that the generalized splatting RFC probably needed a rework well before it was accepted, but I don't think there was -- again -- a real consensus on what would be a better way to implement.
123+
124+
Michael B.
125+
could we get a twitter handle to follow where all RFCs get called linked? or is that too much duplication of effort?
126+
127+
Joel Sallow
128+
I mean I'm pretty sure a fair few folks were saying that the generalized splatting RFC probably needed a rework well before it was accepted, but I don't think there was -- again -- a real consensus on what would be a better way to implement.
129+
130+
Anonymous
131+
@Joey, do you want to talk about my blogpost? I am working from home so I can speak.
132+
133+
Sean Wheeler
134+
@Joey, do you want to talk about my blogpost? I am working from home so I can speak.
135+
136+
Thomas Nieto
137+
What is the decision on the breaking change to remove support for variable names ending in "?" since analysis found only 70 unique variable names using that convention.
138+
139+
https://github.com/PowerShell/PowerShell/issues/3240
140+
141+
Keith Hill
142+
Case in point on future behaviors, collection unrolling, while handy, can cause unexpected behavior. In retrospect, probably should have used an explicit operator for collection unrolling e.g. $process.Id.
143+
144+
Keith Hill
145+
er $processes.*Id
146+
147+
Michael B.
148+
could we get a twitter handle to follow where all RFCs get called linked? or is that too much duplication of effort?
149+
150+
Sean Wheeler
151+
@Joey, do you want to talk about my blogpost? I am working from home so I can speak.
152+
153+
Michael B.
154+
yes when they get posted
155+
156+
Joel Sallow
157+
Ehhh, people can still name variables whatever they want with ${var?} whether or not we change the default charset available. But yeah, ultimately changing that may not be worth it since it flatly doesn't affect anything if you use any whitespace; $var? ? $ifTrue : $ifFalse is valid regardless, really, so the only truly affected scenarios are probably largely code-golf.
158+
159+
Keith Hill
160+
Case in point on future behaviors, collection unrolling, while handy, can cause unexpected behavior. In retrospect, probably should have used an explicit operator for collection unrolling e.g. $process.Id.
161+
162+
Keith Hill
163+
er $processes.*Id
164+
165+
Michael B.
166+
speaking as an admin scripter, not a dev, github confuses the hell out of me. sorry.
167+
168+
Michael B.
169+
yes when they get posted
170+
171+
Joel Sallow
172+
Ehhh, people can still name variables whatever they want with ${var?} whether or not we change the default charset available. But yeah, ultimately changing that may not be worth it since it flatly doesn't affect anything if you use any whitespace; $var? ? $ifTrue : $ifFalse is valid regardless, really, so the only truly affected scenarios are probably largely code-golf.
173+
174+
Michael B.
175+
speaking as an admin scripter, not a dev, github confuses the hell out of me. sorry.
176+
177+
Anonymous
178+
The generalized splatting feature was a question if the multi-line continuence RFC with enclosures would work better because it doesn't allow changing parameters into hash tables when switching to multi-line
179+
180+
Joel Sallow
181+
Right, but if you're looking to be whitespace agnostic you'd be changing the variable name requirements. Currently if a variable is named $Var you cannot use a ternary operator without whitespace?
182+
183+
Joel Sallow
184+
Not saying it's wrong one way or the other, just clarifying! <3(Joel Sallow asked "Right, but if you're looking to be whitespace agnostic you'd be changing the variable name requirements. Currently if a variable is named $Var you cannot use a ternary operator without whitespace?")
185+
186+
Anonymous
187+
The generalized splatting feature was a question if the multi-line continuence RFC with enclosures would work better because it doesn't allow changing parameters into hash tables when switching to multi-line
188+
189+
Joel Sallow
190+
Right, but if you're looking to be whitespace agnostic you'd be changing the variable name requirements. Currently if a variable is named $Var you cannot use a ternary operator without whitespace?
191+
192+
Darwin
193+
Can we alias get-ciminstance and the relevant params?
194+
195+
Darwin
196+
Can we alias get-ciminstance and the relevant params?
197+
198+
Christoph Bergmeister
199+
Something that should be called out as well is that PowerShell 6.1 gets out of supporrt next week (yeah) and therefore PSSA 1.18.3 already dropped support for it
200+
201+
Michael B.
202+
but they are slow!!! (CIM) so very slow...
203+
204+
Christoph Bergmeister
205+
Something that should be called out as well is that PowerShell 6.1 gets out of supporrt next week (yeah) and therefore PSSA 1.18.3 already dropped support for it
206+
207+
Michael B.
208+
but they are slow!!! (CIM) so very slow...
209+
210+
Edward
211+
With the foreach in parallel function, what is the behavior during an exception?
212+
213+
Edward
214+
With the foreach in parallel function, what is the behavior during an exception?
215+
216+
Joey Aiello
217+
Non-terminating PSTask exception, or with -AsJob it's handled in the job object(Edward asked "With the foreach in parallel function, what is the behavior during an exception?")
218+
219+
kvprasoon
220+
Thank you all
221+
222+
Keith Hill
223+
thanks! bye
224+
225+
Jonas Sommer Nielsen
226+
Awsome stuff. Have a nice day :)
227+
228+
Joel Sallow
229+
Thank you all! <3
230+

‎CommunityCall/notes/20190919_Notes.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
## Notes
2+
3+
* Releases
4+
* 7.0.0-preview.4 out later today, blogpost to come with GIFs on features
5+
* Working towards ~December Release Candidate, ~January General Availability
6+
* Bound to .NET Core 3.1 and their dates
7+
* Will get LTS support for 7.0 and .NET Core 3.1
8+
* PowerShell Script Analyzer 1.18.3 released with a critical bugfix (get it from the Gallery!)
9+
* RFCs
10+
* Going through an exercise of rewriting our processes and principles around PowerShell and RFCs
11+
* Want to provide more transparency and dependability, but also the Committee is an executive body that sometimes has to make unpopular decisions
12+
* "We want to be sure we don't preclude behavior when we add behavior." - Jim
13+
* PowerShellGet 3.0
14+
* We want to make sure that new modules are well-tested and used in production
15+
before they ship into PowerShell
16+
* PSGet 3.0 will be in preview in 7.0 GA, and will not make it's way into PS until 7.x
17+
* Some PS Team owned cmdlets are missing in PS Core vs. Windows PS
18+
* We cannot legally use private/undocumented Windows APIs from PowerShell as it ships outside of Windows*
19+
* Some "work just fine" when sideloading inbox Windows modules (like `Microsoft.PowerShell.LocalAccounts`),
20+
but others cannot be imported because they have the same name as existing PS Core modules
21+
* For these, use the `WindowsCompatibility` module to call into them via Windows PowerShell
22+
* DSC
23+
* `Invoke-DscResource` being made available cross-platform in 7.0
24+
* Not calling through a Local Configuration Manager (LCM),
25+
but invoking directly in user context via PowerShell
26+
* `Configuration` blocks now compile correctly on macOS as well
27+
* Still some bugs/kinks that need to be documented, but it's a good start
28+
* 3.0, 4.0, and 5.1 documentation is being maintained on `PowerShell-Docs` and `windows-powershell-docs` repos,
29+
but hasn't been finding it's way into updateable help
30+
* Sean has a blog post on platyPS and using the Markdown source in the docs repo
31+
to manually update your console help on downlevel versions
32+
* Currently in the process of archiving (read-only) the 3.0, 4.0, and 5.0 help
33+
(5.1 will continue to be maintained)
34+
* PS Conference Asia
35+
* Demos
36+
* `ForEach-Object -Parallel` is awesome, check out the demo and Paul's blog post
37+
* Go through GitHub Issues
38+
* Q&A
39+
* Conditional chain operator (`&&` and `||`) going to make it in time for PS7?
40+
* Would like to make this into 7.0-preview.5 as experimental
41+
* Is PS Conf Asia being streamed online?
42+
* We don't believe so, but there will likely be recordings
43+
* When does 6.2 support end?
44+
* 6 months after 7.0 GAs, roughly July of next year
45+
* Is this being recorded?
46+
* Yes, we record all Community Calls and put them on YouTube,
47+
easy to find at https://aka.ms/PSCommunityCall
48+
* `@@` "generalized splatting" will likely not make it for PS 7.0,
49+
no one from our team is working on that
50+
* Is Dispose() work being done?
51+
* Joel Sallow needs us to finish his RFC before he can finish code

0 commit comments

Comments
 (0)