profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/joeyaiello/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Joey Aiello joeyaiello Microsoft Seattle, WA Program Manager and @PowerShell Committee Member working on PowerShell at @microsoft

azureautomation/vststasks 3

Visual Studio Team Services tasks for integrating with Azure Automation

joeyaiello/amazon_round 2

A simple piece of Javascript that rounds prices on Amazon to the nearest half-dollar

joeyaiello/2018 0

PowerShell Conference Europe 2018 Slides and Demo Scripts

joeyaiello/azure-content 0

Repository containing the Articles on azure.microsoft.com Documentation Center

joeyaiello/azure-pipelines-tasks 0

Tasks for Azure Pipelines

create barnchjoeyaiello/PowerShell-RFC

branch : Aug2021CommCall

created branch time in 19 days

MemberEvent
MemberEvent

fork joeyaiello/vue-app

📹 An example to use ffmpeg.wasm in Vue

https://ffmpegwasm.github.io/vue-app/

fork in a month

issue commentPowerShell/PowerShell

ConvertFrom-Yaml, ConvertTo-Yaml

@PowerShell/wg-powershell-cmdlets has been discussing this issue, and despite the extremely high demand (and my own personal desire to have strong, canonical YAML cmdlets), we're unfortunately going to have to close it (for now) as Won't Fix. The reasoning is two-fold:

  • While the PowerShell package is already fairly large, we're doing our best not to add new dependencies to the package so that we don't continue to grow our size unfettered, and because we believe that pulling modules from the PowerShell Gallery (or an internal trusted Gallery, having been vetted appropriately by an enterprise) should be a standard part of a PS7 workflow.
  • As a team, we simply don't have the capacity to build a .NET YAML parser from scratch, nor do we have the capacity to vet, support, and service a 3rd party library for which the security implications are high-stakes.

If .NET were to officially support a YAML library, we (as Microsoft) could potentially look into supporting a YAML module on the Gallery. But until that point, the existing community modules will have to suffice.

DarwinJS

comment created time in a month

issue openedPowerShell/PowerShell-RFC

Community Call Aug 19, 2021

As always, you can join the Community Call at https://aka.ms/JoinPSCall (9:30a PDT) with a Teams client or the browser web app.

Current agenda (TBD):

  • PowerShell 7 update
  • PowerShellGet 3.0 update
  • Microsoft/Windows Update for PS7
  • Code Coverage
  • Community demos
  • Q&A

Feel free to post your questions, comments, or any community demos (~5 mins) you'd like to present.

created time in a month

PullRequestReviewEvent

issue closedPowerShell/PowerShell-RFC

Create WG labels within RFC repo

Given that Working Groups (WGs) will be reviewing RFCs as area experts, it makes sense for us to add the equivalent WG-* labels here in the RFC repo in addition to PowerShell/PowerShell.

Leaving this here to remind me for later

closed time in a month

joeyaiello

issue commentPowerShell/PowerShell-RFC

Create WG labels within RFC repo

Closing as fixed

joeyaiello

comment created time in a month

issue openedPowerShell/PowerShell

Decide on which experimental features will remain in experimental in 7.2

Summary of the new feature / enhancement

In preparation for 7.2 RCs, @PowerShell/powershell-committee has reviewed our existing experimental features and decided that the following should be upgraded to stable, left as experimental, or removed altogether:

Supported / Non-Experimental

  • PSNotApplyErrorActionToStderr: We agree that stderr is used in many cases where there is no error behavior and therefore shouldn't trigger ErrorAction cases like Stop. Given that we've seen no issues with this experimental feature since it was checked into 7.1 previews, we're moving it to stable.
  • PSUnixFileStat: This has had sufficient time for users in preview builds to use the default behavior of showing Linux file stats (since early 7.1 previews), and no major issues have been reported.
  • PSAnsiProgress: This new minimal style of progress bar hasn't created any issues, and we see no reason not to make it stable. Furthermore, you can back to the old progress bar with $PSStyle.Progress.View = 'classic', or turn off progress altogether.
  • PSAnsiRendering: There were a few issues around the $PSStyle implementation that have been fixed. This points to some amount of usage from customers. Additionally, we've implemented features like PSAnsiProgress on top of this, and the interface has been stable and useful.
  • PSCultureInvariantReplaceOperator: As outlined in #10948, this issue should make the -replace string operator indifferent to the culture in an environment, such that it works the same as the -split operator. We haven't seen this cause any impact in the wild from the result of this Bucket 3 breaking change.
  • Microsoft.PowerShell.Utility.PSManageBreakpointsInRunspace: The -BreakAll switch added to Debug-Runspace is opt-in, and has been working well within the Azure Functions tooling for Visual Studio Code.
  • Microsoft.PowerShell.Utility.PSImportPSDataFileSkipLimitCheck: The -SkipLimitCheck switch added to Import-PowerShellDataFile is opt-in, and we haven't seen any issues with it in the wild.

Experimental (for now)

  • PSAnsiRenderingFileInfo: This came in very late, and we'd like to give it some more bake time for folks to give feedback. For example, we should continue to discuss the colors themselves, which file extensions should be colorized, how we might be able to support LS_COLOR, whether we need theme support, as well as how 3rd parties might be able to extend existing formatters (more context in #15746). To that end, we're leaving it as experimental.
  • PSCommandNotFoundSuggestion: The suggestion framework still has significant issues (e.g. writes only to the console host rather than an output stream). This is still something we'd like to leverage in the future for suggesting modules for download from PowerShellGet.
  • PSNativePSPathResolution: Today, this resolution of PSPaths in native commands is overly aggressive because single- and double-quotes are not differentiated in the native command binder. This means you can't indicate a PSPath as literal. Until we solve this issue (which is non-trivial), we're leaving this as experimental.
  • PSLoadAssemblyFromNativeCode: As we discussed in #14641, we are leaving this as experimental until we decide whether or not we want to implement a full native hosting API for wrapping PowerShell from native code.
  • PSSubsystemPluginModel: Subsystems are still a WIP as we work through the right way to decouple certain functionality from the core PowerShell engine.

Needs to be removed

  • PSImplicitRemotingBatching: This has not fulfilled the original goal of optimizing implicit remoting calls, and has not seen significant usage from folks in the wild. To that end, we plan to revert and remove this code before 7.2 GAs.

Deferred

  • PSDesiredStateConfiguration.InvokeDscResource: Given that this is part of the PSDesiredStateConfiguration module, we are deferring to the module owner to make a final decision on whether this should remain experimental.

Proposed technical implementation details (optional)

No response

created time in a month

pull request commentPowerShell/PowerShell-RFC

`TimeSpan` Literals and support for `TimeSpan` objects in Cmdlets such as Start-Sleep

@schuelermine : thanks for the updates! The way our current process works, this would remain open until the final code is merged as non-experimental (which should only happen after the feature exists as an experimental feature in preview builds for some length of time).

So it's currently "experimentally approved" for you to start code work (or anyone else that wants to pick it up).

schuelermine

comment created time in 2 months

delete branch joeyaiello/PowerShell-RFC

delete branch : RFCProcess

delete time in 2 months

push eventPowerShell/PowerShell-RFC

Joey Aiello

commit sha 5bd5e0a8104136921620083ee67258083e8fc9e5

Updated governance and process: Working Groups (WGs) (#274) * first draft of Working Group process * Update RFC0000-RFC-Process.md * Update RFC0000-RFC-Process.md Co-authored-by: Robert Holt <rjmholt@gmail.com> * Apply suggestions from code review Co-authored-by: Robert Holt <rjmholt@gmail.com>

view details

push time in 2 months

PR merged PowerShell/PowerShell-RFC

Updated governance and process: Working Groups (WGs)

<!--

All new RFCs must:

  • have examples of the proposed behavior, preferably in the form of a script (or scripts) which shows the proposed behavior with comments and annotations

All new RFCs should:

  • Not have a number - maintainers will assign the number
  • Be placed in the Draft folder

Maintainers will sometimes need to make small edits (for example, set the RFC number). To make this easier, we suggest giving maintainers permission to push to your fork, see https://github.com/blog/2247-improving-collaboration-with-forks.

Also be sure to read https://github.com/PowerShell/PowerShell-RFC/blob/master/RFC0000-RFC-Process.md

-->

This PR reworks the RFC process to conform to the updated governance of Working Groups (WGs).

For more context, see PowerShell/PowerShell#14603 and this blog post.

+59 -31

1 comment

1 changed file

joeyaiello

pr closed time in 2 months

pull request commentPowerShell/PowerShell-RFC

Updated governance and process: Working Groups (WGs)

If there are any other changes on this that need to be addressed, please file as a bug fix.

joeyaiello

comment created time in 2 months

pull request commentPowerShell/PowerShell-RFC

Native Command Error Handling

@rkeithhill agreement that, especially given what's in the docs today for ApplicationFailedException ("Defines the exception that is thrown if a native command fails", it might make sense to rename NativeCommandException to something else.

@SteveL-MSFT is suggesting NativeCommandExitException, but we're open to other possibilities.

We're also referring this RFC to the Engine WG for review.

theJasonHelmick

comment created time in 2 months

issue openedPowerShell/PowerShell-RFC

Create WG labels within RFC repo

Given that Working Groups (WGs) will be reviewing RFCs as area experts, it makes sense for us to add the equivalent WG-* labels here in the RFC repo in addition to PowerShell/PowerShell.

Leaving this here to remind me for later

created time in 2 months

pull request commentPowerShell/PowerShell-RFC

Native Command Error Handling

@rkeithhill even as an opt-in feature, it still needs to be marked as an experimental feature to denote that the design may change in the future.

Ideally, it should be code-fenced such that the opt-in isn't possible without the experimental feature turned on, but if the Maintainers agree with you that it's prohibitively difficult to do that, it should still have a placeholder experimental feature (where turning it off would do nothing) to denote the potential instability of the interface.

theJasonHelmick

comment created time in 2 months

push eventPowerShell/PowerShell-RFC

Jason Helmick

commit sha bf1dcb1df9780f581bdba1bfc0c3e4888ee60827

Added notes/readme PSCommcall20210715 (#296)

view details

push time in 2 months

PR merged PowerShell/PowerShell-RFC

Added notes/readme for PSCommCall-20210715

@SteveL-MSFT, can you review and merge.

+61 -0

0 comment

2 changed files

theJasonHelmick

pr closed time in 2 months

PullRequestReviewEvent

push eventPowerShell/PowerShell-RFC

Dongbo Wang

commit sha ac5e376c457c84b407e9ecdf198c8909e22ccaa6

Move the media folder to Final (#295)

view details

push time in 2 months

PR merged PowerShell/PowerShell-RFC

Move the media folder to Final because `RFC0062-PredIctive-IntelliSense.md` is moved to Final folder

The media folder was not moved to Final when RFC0062-PredIctive-IntelliSense.md was moved. /cc @theJasonHelmick

+0 -0

1 comment

9 changed files

daxian-dbw

pr closed time in 2 months

pull request commentPowerShell/PowerShell-RFC

Move the media folder to Final because `RFC0062-PredIctive-IntelliSense.md` is moved to Final folder

Thanks, @daxian-dbw! Just saw this when we logged on to meet today, you made it easy :)

daxian-dbw

comment created time in 2 months

push eventPowerShell/PowerShell-RFC

Jason Helmick

commit sha 87476a5a153776d4402abd711da5cb64e95b27c3

Final: RFC0062 - Predictive IntelliSense (#289) * updated pr predictive intellisense * Update 1-Draft/RFC00XX-PredIctive-IntelliSense.md Co-authored-by: James Truher [MSFT] <jimtru@microsoft.com> * updated pr predictive intellisense * updated pr predictive intellisense * removed reference to plugin as PSRL option * changed providers to plugins and cleanup * Corrections * Merge RFC0062 - Predictive IntelliSense as Final Co-authored-by: James Truher [MSFT] <jimtru@microsoft.com> Co-authored-by: Joey Aiello <joeyaiello@users.noreply.github.com>

view details

push time in 2 months

PR merged PowerShell/PowerShell-RFC

Predictive IntelliSense

Link to original pr: #262 https://github.com/PowerShell/PowerShell-RFC/pull/262/files

+353 -0

0 comment

10 changed files

theJasonHelmick

pr closed time in 2 months

push eventtheJasonHelmick/PowerShell-RFC

Joey Aiello

commit sha 0c594a78db02c9ebdbbc7e6c2a8e165aeee2adbe

Merge RFC0062 - Predictive IntelliSense as Final

view details

push time in 2 months

PullRequestReviewEvent

PR opened PowerShell/PowerShell-RFC

Remove empty 2-Draft-Accepted

Forgot to remove this empty folder in #290

+0 -1

0 comment

1 changed file

pr created time in 2 months

push eventjoeyaiello/PowerShell-RFC

joeyaiello

commit sha 71a8ed7886fdfbd9b9c273952d571511ec545246

remove empty 2-Draft-Accepted

view details

push time in 2 months