Skip to content

Commit 94c1ce5

Browse files
Added Sept notes/transcript to notes folder
1 parent 5f2623d commit 94c1ce5

File tree

2 files changed

+368
-0
lines changed

2 files changed

+368
-0
lines changed
Lines changed: 272 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,272 @@
1+
Joel Sallow
2+
hi joey <3
3+
4+
JB "AspenForester" Lewis
5+
hello! Good audio
6+
7+
Sydney Smith
8+
https://github.com/PowerShell/PowerShell-RFC/issues/260
9+
10+
Joel Sallow
11+
hi joey <3
12+
13+
JB "AspenForester" Lewis
14+
hello! Good audio
15+
16+
Jon J.
17+
Morning Folks
18+
19+
Jon J.
20+
Morning Folks
21+
22+
kvprasoon
23+
Hioo all...
24+
25+
Thomas Rayner
26+
The soothing, sultry tones of Joey.
27+
28+
kvprasoon
29+
Hioo all...
30+
31+
Thomas Rayner
32+
The soothing, sultry tones of Joey.
33+
34+
Justin Grote [MVP]
35+
Everyone's all about Scott Hanselman's ASMR voice but I think Joey has him beat.
36+
37+
Justin Grote [MVP]
38+
Everyone's all about Scott Hanselman's ASMR voice but I think Joey has him beat.
39+
40+
Tyler Leonhardt (POWERSHELL) (tyleonha@microsoft.com)
41+
lolol(Justin Grote [MVP] asked "Everyone's all about Scott Hanselman's ASMR voice but I think Joey has him beat.")
42+
43+
Anonymous
44+
I'm here! :)
45+
46+
kvprasoon
47+
is it similar to this ?https://github.com/ansible/community/wiki
48+
49+
Ansible has working groups
50+
51+
Jon J.
52+
How will these working groups be coordinated?
53+
54+
Jon J.
55+
How will these working groups be coordinated?
56+
57+
Steve Lee (POWERSHELL)
58+
Members of the WGs will self coordinate taking into consideration different timezones, etc...(Jon J. asked "How will these working groups be coordinated?")
59+
60+
kvprasoon
61+
is it similar to this ?https://github.com/ansible/community/wiki
62+
63+
Ansible has working groups
64+
65+
Steve Lee (POWERSHELL)
66+
WGs are not a new thing and we're leveraging existing concepts from different orgs as a best practice(kvprasoon asked "is it similar to this ?https://github.com/ansible/community/wiki
67+
68+
Ansible has working groups")
69+
70+
Anonymous
71+
I'm here! :)
72+
73+
MaxT
74+
Hi guys!
75+
76+
Anonymous
77+
Can these work group and committe meetings be recorded and published for increase visibility in how the decision was reached? Right now when the committe sends their decision there is not a lot of information on the background and alternate ideas.
78+
79+
Anonymous
80+
Can these work group and committe meetings be recorded and published for increase visibility in how the decision was reached? Right now when the committe sends their decision there is not a lot of information on the background and alternate ideas.
81+
82+
Steve Lee (POWERSHELL)
83+
We've discussed recording or a transcript of Committee meetings, but decided at this time not to pursue this as it limits the openness of our current conversations. We may revisit in the future. WGs will decide for themselves if they want a public record of their discussions.(Can these work group and committe meetings be recorded and published for increase visibility in how the decision was reached? Right now when the committe sends their decision there is not a lot of information on the background and alternate ideas.)
84+
85+
MaxT
86+
Hi guys!
87+
88+
Justin Grote [MVP]
89+
This is still just history right? Any further development based on the Predictive Intellisense issue you opened? I want vscode style property predictions if I don't already have a matching history.
90+
91+
Justin Grote [MVP]
92+
NM answered here(Justin Grote [MVP] asked "This is still just history right? Any further development based on the Predictive Intellisense issue you opened? I want vscode style property predictions if I don't already have a matching history.")
93+
94+
JoshCorr
95+
So is Predictive Readline essentially like hitting ctrl+r <typing>, but automatic?
96+
97+
JoshCorr
98+
So is Predictive Readline essentially like hitting ctrl+r <typing>, but automatic?
99+
100+
Steve Lee (POWERSHELL)
101+
ctrl+r is doing a search, the history prediction will rely on other algorithms for the prediction. So similar, but not the same. You can still use ctrl+r for reverse history search if that is your preference(JoshCorr asked "So is Predictive Readline essentially like hitting ctrl+r <typing>, but automatic? ")
102+
103+
Justin Grote [MVP]
104+
This is still just history right? Any further development based on the Predictive Intellisense issue you opened? I want vscode style property predictions if I don't already have a matching history.
105+
106+
Steve Lee (POWERSHELL)
107+
We're working with other teams on the actual ML aspect. Outside of AzPS, nothing to announce at this time.(Justin Grote [MVP] asked "This is still just history right? Any further development based on the Predictive Intellisense issue you opened? I want vscode style property predictions if I don't already have a matching history.")
108+
109+
Joel Sallow
110+
I like the idea, but I do think F2 is not a great default key for it tbh
111+
112+
Dongbo Wang
113+
Any suggestion for the default key? :)(Joel Sallow asked "I like the idea, but I do think F2 is not a great default key for it tbh")
114+
115+
Joel Sallow
116+
Ctrl+Space as Justin suggested or perhaps Ctrl+Alt+Space if it needs to be a different key at all. :)(Joel Sallow asked "I like the idea, but I do think F2 is not a great default key for it tbh")
117+
118+
Keith Hill
119+
Multiple predictors / list - very nice!
120+
121+
Thomas Rayner
122+
I can bind it to something other than F2, right?
123+
124+
Dongbo Wang
125+
Of course, it's a regular bindable function like others in PSReadLine(Thomas Rayner asked "I can bind it to something other than F2, right? ")
126+
127+
MaxT
128+
Jason ... That looks Awesome!
129+
130+
Jason Helmick (jahelmic@microsoft.com)
131+
Link to Predictive IntelliSense profile sample: https://www.powershellgallery.com/packages/PSReadLine/2.1.0-beta2/Content/SamplePSReadLineProfile.ps1
132+
133+
Thomas Rayner
134+
I can bind it to something other than F2, right?
135+
136+
Dongbo Wang
137+
my reply was lost after the question is moved here :)
138+
Yes, it's a regular bindable function just like others in PSReadLine(Thomas Rayner asked "I can bind it to something other than F2, right? ")
139+
140+
MaxT
141+
Jason ... That looks Awesome!
142+
143+
Keith Hill
144+
Multiple predictors / list - very nice!
145+
146+
Joel Sallow
147+
I like the idea, but I do think F2 is not a great default key for it tbh
148+
149+
Dongbo Wang
150+
Any suggestion for a better default key? :)(Joel Sallow asked "I like the idea, but I do think F2 is not a great default key for it tbh")
151+
152+
JB "AspenForester" Lewis
153+
The On-Demand sessions Joey mentioned don't seem to be currently listed in the Ignite catalog (yet).
154+
155+
kvprasoon
156+
Ctrl + F
157+
158+
JB "AspenForester" Lewis
159+
The On-Demand sessions Joey mentioned don't seem to be currently listed in the Ignite catalog (yet).
160+
161+
kvprasoon
162+
Ctrl + F
163+
164+
Ben Gelens
165+
Are psget v2 Issues still tracked? Or is it frozen?
166+
167+
Joel Bennett
168+
I want to strongly second the request to have PSGet3 in the base Windows install.
169+
170+
Especially as new functionality shows up in PSGet3 (like assembly dependencies), modules won't be installable by PSGet2, and we will (in Azure and other automated machine deployments) forever be using PSGet2 to install PSGet3 before we can install anything else!
171+
172+
Ben Gelens
173+
Are psget v2 Issues still tracked? Or is it frozen?
174+
175+
Steve Lee (POWERSHELL)
176+
Only critical issues in v2 are being looked at(Ben Gelens asked "Are psget v2 Issues still tracked? Or is it frozen?")
177+
178+
Joel Bennett
179+
I want to strongly second the request to have PSGet3 in the base Windows install.
180+
181+
Especially as new functionality shows up in PSGet3 (like assembly dependencies), modules won't be installable by PSGet2, and we will (in Azure and other automated machine deployments) forever be using PSGet2 to install PSGet3 before we can install anything else!
182+
183+
Justin Grote [MVP]
184+
On the F2 question: I think it should replace ctrl-Space *if and only if* the prediction is enabled. This puts it in parity with vscode etc where I want to see my available completions
185+
186+
Justin Grote [MVP]
187+
On the F2 question: I think it should replace ctrl-Space *if and only if* the prediction is enabled. This puts it in parity with vscode etc where I want to see my available completions
188+
189+
Steve Lee (POWERSHELL)
190+
Please open an issue(Justin Grote [MVP] asked "On the F2 question: I think it should replace ctrl-Space *if and only if* the prediction is enabled. This puts it in parity with vscode etc where I want to see my available completions")
191+
192+
Dongbo Wang
193+
As of today, predictive intellisense and tab completion are 2 separate code paths. Ctrl-Space is for tab completion, and should keep it that way.(Justin Grote [MVP] asked "On the F2 question: I think it should replace ctrl-Space *if and only if* the prediction is enabled. This puts it in parity with vscode etc where I want to see my available completions")
194+
195+
Dongbo Wang
196+
We are thinking about how to converge the tab completion and preditive intellisense in PSReadLine, the problem today is tab completion is comparatively too slow to have a smooth intellisense experience in the console environment.(Justin Grote [MVP] asked "On the F2 question: I think it should replace ctrl-Space *if and only if* the prediction is enabled. This puts it in parity with vscode etc where I want to see my available completions")
197+
198+
Dongbo Wang
199+
Just to clarify the functionality bound with F2 in the demo: it swtich the prediction view between the inline view and list view.(Justin Grote [MVP] asked "On the F2 question: I think it should replace ctrl-Space *if and only if* the prediction is enabled. This puts it in parity with vscode etc where I want to see my available completions")
200+
201+
Dongbo Wang
202+
You will be able to set the PredictionView via `Set-PSReadLineOption` as well.(Justin Grote [MVP] asked "On the F2 question: I think it should replace ctrl-Space *if and only if* the prediction is enabled. This puts it in parity with vscode etc where I want to see my available completions")
203+
204+
Sean Wheeler
205+
F7 - Displays the command history in the old console experience. Using F7 would provide a similar experience.(Justin Grote [MVP] asked "On the F2 question: I think it should replace ctrl-Space *if and only if* the prediction is enabled. This puts it in parity with vscode etc where I want to see my available completions")
206+
207+
Justin Grote [MVP]
208+
I currently zip-bootstrap in PSGetV3 in testing because PSGetV2 is so slow and inefficient
209+
210+
Justin Grote [MVP]
211+
I currently zip-bootstrap in PSGetV3 in testing because PSGetV2 is so slow and inefficient
212+
213+
Justin Grote [MVP]
214+
Q: Trevor, you said the predictive intellisense works in PS7.1 with PSReadline 2.1.0-beta2, I can't get "F2" to work and 2.1.0-beta2 has been out a while, did i mishear you?
215+
216+
Dongbo Wang
217+
Sorry if it was not clear, the list view and the feature that hooks up with the Prediction APIs shipped in 7.1.0-preview.7 are not in 2.1.0-beta2(Justin Grote [MVP] asked "Q: Trevor, you said the predictive intellisense works in PS7.1 with PSReadline 2.1.0-beta2, I can't get "F2" to work and 2.1.0-beta2 has been out a while, did i mishear you?")
218+
219+
Dongbo Wang
220+
Jason mentioned 2.1.0-beta2 for the history based inline view feature only(Justin Grote [MVP] asked "Q: Trevor, you said the predictive intellisense works in PS7.1 with PSReadline 2.1.0-beta2, I can't get "F2" to work and 2.1.0-beta2 has been out a while, did i mishear you?")
221+
222+
Dongbo Wang
223+
The new features will be in 2.2.0-beta1. We are going to GA 2.1 with the history based inline view only. This is because the prediction APIs shipped in 7.1 will remain experiemtal, and thus features built on top should not be in GA.(Justin Grote [MVP] asked "Q: Trevor, you said the predictive intellisense works in PS7.1 with PSReadline 2.1.0-beta2, I can't get "F2" to work and 2.1.0-beta2 has been out a while, did i mishear you?")
224+
225+
Justin Grote [MVP]
226+
THanks, I don't think these replies are in the "featured" section, just replying to me.(Justin Grote [MVP] asked "Q: Trevor, you said the predictive intellisense works in PS7.1 with PSReadline 2.1.0-beta2, I can't get "F2" to work and 2.1.0-beta2 has been out a while, did i mishear you?")
227+
228+
Dongbo Wang
229+
Oh, I will copy the replies there(Justin Grote [MVP] asked "Q: Trevor, you said the predictive intellisense works in PS7.1 with PSReadline 2.1.0-beta2, I can't get "F2" to work and 2.1.0-beta2 has been out a while, did i mishear you?")
230+
231+
Justin Grote [MVP]
232+
Specifically the "new" intellisense and list view
233+
234+
Justin Grote [MVP]
235+
Comment: I mean, [HashTable] and [Array] are still used as basic language constructs, I wouldn't expect system.text.json to happen anytime soon as native.
236+
237+
Justin Grote [MVP]
238+
Q: Trevor, you said the predictive intellisense works in PS7.1 with PSReadline 2.1.0-beta2, I can't get "F2" to work and 2.1.0-beta2 has been out a while, did i mishear you?
239+
240+
Dongbo Wang
241+
Justin, can you please copy my replies here? I cannot see them now(Justin Grote [MVP] asked "Q: Trevor, you said the predictive intellisense works in PS7.1 with PSReadline 2.1.0-beta2, I can't get "F2" to work and 2.1.0-beta2 has been out a while, did i mishear you?")
242+
243+
Joel Sallow
244+
braced variables have their uses, but requiring them for an operator is a bit silly in my opinion ;)
245+
246+
Joel Sallow
247+
braced variables have their uses, but requiring them for an operator is a bit silly in my opinion ;)
248+
249+
Justin Grote [MVP]
250+
Answer to New List View PSReadline: The new features will be in 2.2.0-beta1. We are going to GA 2.1 with the history based inline view only. This is because the prediction APIs shipped in 7.1 will remain experiemtal, and thus features built on top should not be in GA.
251+
252+
Justin Grote [MVP]
253+
Answer to New List View PSReadline: The new features will be in 2.2.0-beta1. We are going to GA 2.1 with the history based inline view only. This is because the prediction APIs shipped in 7.1 will remain experiemtal, and thus features built on top should not be in GA.
254+
255+
Justin Grote [MVP]
256+
dotnet restore already builds a local package repository, it should just place the additional packages there and reference them. It's what I do today to handle my Powerhsell Module net assembly dependencies.
257+
258+
Justin Grote [MVP]
259+
dotnet restore already builds a local package repository, it should just place the additional packages there and reference them. It's what I do today to handle my Powerhsell Module net assembly dependencies.
260+
261+
Joel Sallow
262+
@justin grote -- they mentioned you'll need to enable a PSReadline option to turn them on (set in your profile to turn it on persistently)
263+
264+
Joel Sallow
265+
@justin grote -- they mentioned you'll need to enable a PSReadline option to turn them on (set in your profile to turn it on persistently)
266+
267+
Justin Grote [MVP]
268+
Specifically the "new" intellisense and list view
269+
270+
Justin Grote [MVP]
271+
Comment: I mean, [HashTable] and [Array] are still used as basic language constructs, I wouldn't expect system.text.json to happen anytime soon as native.
272+
Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
# PowerShell Community Call - September 17, 2020
2+
3+
## Agenda
4+
5+
* PowerShell 7.1 preview 7
6+
* PowerShell 7.2 and working groups
7+
* PSReadline list view
8+
* Ignite 2020
9+
* Gallery statistics
10+
* PowerShellGet update
11+
* SecretManagement update
12+
* Notebooks
13+
* Q&A
14+
15+
## Notes
16+
17+
* Release of PS 7.1 preview 7
18+
* last preview before RCs start
19+
* made some calls on which experimental features will "graduate" to stable with some remaining experimental
20+
* RCs will be "go live", which means that they are supported in production
21+
* first RC this month, second RC in Oct, GA in Nov
22+
* last chance to give critical feedback before 7.2
23+
* PowerShell 7.2
24+
* strong desire to use the first half of the previews (6 months) to do feature work
25+
* second 6 months of release will be oriented more around stabilizing and bug fixes
26+
* LTS release
27+
* we want to look more at community contributions for feature inclusion in 7.2 than we have in the past
28+
* Working Groups
29+
* Think of this as subcommittees that specialize in specific areas of PowerShell
30+
* Working Groups will
31+
* foster initial discussions in issues
32+
* make decisions on feature/bugfix inclusion
33+
* advise the Committee on RFCs
34+
* Goal is to reduce bottlenecks within the Committee to providing feedback to feature proposals
35+
* Creates an opportunity to bring more community contributors on board
36+
* PSReadline list view
37+
* predictive IntelliSense shows matching lines from your PSReadline as you type
38+
* You can try this today with PSReadline 2.1.0-beta.2 and TODO link to profile example
39+
* New list view via F2 shows a list of predictions instead of just the one at your prompt
40+
* Can also incorporate other predictors, like one for Azure PowerShell that shows ML-generated examples
41+
* Ignite 2020
42+
* PowerShell 7 and PowerShell Unplugged sessions will be available on-demand
43+
* 2 Ask the Experts sessions with members of the team
44+
* "PowerShell and Linux in Azure"
45+
* 3 PowerShell Table Topics with community and PowerShell Team
46+
* PowerShell Gallery statistics
47+
* Gallery stats have been down for about a week now, still actively investigating
48+
* No ETA today, but we will try to provide one soon
49+
* Completely understand the frustration to package owners
50+
* Intermittent issues in Gallery were reported in the last week or two
51+
* We recently pushed an update that should fix these issues
52+
* Please let us know if you're still seeing problems
53+
* PowerShellGet updates
54+
* Original plan was to try and get PSGet 3.0 into the 7.1 preview releases
55+
* However, we decided to spend more time ensuring that 3.0 is stable and validated among customers before
56+
shipping into a stable release of PowerShell
57+
* Therefore, we will instead be shipping 3.0 for the first time in the first 7.2 preview
58+
* 7.2 GA will use 3.0 by default (with the 2.0 compatibility module to avoid breaking CI/CD scripts)
59+
* Major updates to the PowerShellGet repo for planning and milestone tracking
60+
* SecretManagement updates
61+
* Thanks to everyone for feedback
62+
* New preview release this week, blog post published on both [the release](https://devblogs.microsoft.com/powershell/secretmanagement-preview-3/)
63+
and the [design changes that impact extension developers](https://devblogs.microsoft.com/powershell/secretmanagement-module-preview-design-changes/)
64+
* Removed the built-in, default vault that was using CredMan on Windows
65+
* If you upgrade modules, you may need to go directly to Credential Manager to get your secrets
66+
* This preview introduces `Microsoft.PowerShell.SecretStore`, an optional .NET-based, cross-platform vault
67+
* You can still register this new `SecretStore` vault as your default
68+
* Notebooks
69+
* Notebooks provide the ability to mix rich text and executable code in a single, rendered file
70+
* In the VS Code PowerShell extension, we added the ability to run untitled, unsaved PowerShell notebooks
71+
* Files named like `*.Notebook.ps1` will now open directly into notebook mode in VS Code
72+
* All of this only available today in the PowerShell Preview extension with VS Code Insiders
73+
* Lots of blog posts available on the PowerShell Team blog
74+
* Make sure to turn on the Notebook UI feature flag in Settings
75+
* Q&A
76+
* Separating built-in PowerShell modules from the package and shipping them on the Gallery?
77+
* We have a strong desire to do this, but our catch 22 is around moving PowerShell forward and
78+
* Requirement of curly braces with null conditional member access
79+
* Folks in the community have analyzed the corpus and are arguing that question marks are highly unlikely
80+
in variable names
81+
* We can revisit and potentially remove the curly brace requirement in the future based on usage
82+
* .NET Maui
83+
* New cross-platform UI framework targeting .NET 6
84+
* Desire from our side is to work more with `gui.cs` for console GUIs (e.g. better for remoting)
85+
* Probably don't want to ship Maui in PowerShell itself due to the size
86+
* We've had a strong desire to do a "GAC lite" where module authors could take a dependency on Nuget
87+
assemblies that are shared between other modules that need them
88+
* Could updateable help be provided via the Gallery for other module authors
89+
* Something we *could* look at, but there's probably less utility there for Gallery-uploaded modules
90+
* How are we handling the "broken argument passing" in #1995
91+
* Softening on Start-Process argument list parameters
92+
* What to do about AssemblyLoadContext and side-by-side modules that are incompatible with each other
93+
* Module isolation RFC published a while back
94+
* We'll revisit the RFC with a more hybrid solution depending on PSGet 3.0 for dependency resolution
95+
* Will be looking at this in 7.2
96+
* No matter what we do, there will likely be breaking changes for us to move forward here

0 commit comments

Comments
 (0)