Working Group Member Request #24168
Labels
WG-Engine
core PowerShell engine, interpreter, and runtime
WG-NeedsReview
Needs a review by the labeled Working Group
Comments
|
Hi Darren, |
|
📣 Hey @dkattan, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Name of Working Group you are requesting to join?
Engine
Can you provide at least 1 hour per week to the Working Group? Note that time commitments will vary per Working Group and decided by its members.
Yes
Why do you want to join this working group?
Application for PowerShell Working Group
I am the creator of ImmyBot, an application utilized by over 700 Microsoft partners that deeply integrates with PowerShell. As the leader of a team of 12 full-time developers, I am eager to contribute to resolving backlogged issues within the PowerShell project.
Potential Contributions
Expertise in Large-Scale PowerShell Usage: Our extensive use of PowerShell allows us to easily reproduce and address concurrency-related problems that may not be apparent in typical usage scenarios.
Resource for Issue Resolution: We can offer support in tackling issues that may not be high priority for the average user but significantly impact large-scale operations. For example, the slow module loading when opening multiple runspaces concurrently (Features to improve performance of concurrent Runspaces #7524) is a critical issue for our operations.
Collaborative Approach: I understand the caution needed when accepting code submissions, especially for core PowerShell areas. A closer relationship with the working group could reduce friction in implementing necessary changes and foster mutual benefits.
Shared Problem-Solving: There may be issues the PowerShell team is working on that affect our operations without our knowledge. Our involvement could help identify these shared challenges and potentially alleviate some of the workload for the core team.
Commitment
I am committed to contributing positively to the PowerShell community and working collaboratively with the team to enhance PowerShell's functionality and performance, particularly in scenarios involving large-scale and concurrent operations.
Thank you for considering my application. I look forward to the opportunity to contribute to the PowerShell working group.
What skills do you bring to this working group?
I've been writing C# since 2007. I'm intimately familiar with the PowerShell source, specifically the parameter binder, module loading, PSProviders, input completion, constrained runspaces, constrained language mode, PSSerializer, PSScriptAnalyzer, PowerShellEditorServices, PSReadLine and the PowerShell VS Code extension.
Additionally, having built our browser based PowerShell editor I am familiar with the Language Server Protocol and Debug Adapter Protocol, TypeScript, Monaco and Vue.js.
Public links to articles, code, or other resources that demonstrate your skills.
While my primary application is not open-source, I am happy to share it privately if it helps establish credibility.
I have contributed in at least a minimal capacity to PowerShell, PowerShellEditorServices, and PSScriptAnalyzer with mixed success:
PowerShellEditorServices
PowerShell/PowerShellEditorServices#2122
PowerShell/PowerShellEditorServices#2115
PowerShell/PowerShellEditorServices#1641
PowerShell/PowerShellEditorServices#1640
PowerShell/PowerShellEditorServices#1537
PowerShell/PowerShellEditorServices#1510
PowerShell/PowerShellEditorServices#1507
PowerShell/PowerShellEditorServices#1504
PSScriptAnalyzer
PowerShell/PSScriptAnalyzer#1953
PowerShell
#20527
#20069
#19464
#17460
PowerShell RFC
PowerShell/PowerShell-RFC#361
PowerShell Docs
MicrosoftDocs/PowerShell-Docs#10547
Members of my team like @colinblaise have also contributed
PowerShell/PowerShellEditorServices#1694
The text was updated successfully, but these errors were encountered: