You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/building/windows-core.md
+12-12
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
Build PowerShell on Windows for .NET Core
2
2
=========================================
3
3
4
-
This guide will walk you through building PowerShell on Windows, targeting .NET Core.
4
+
This guide will walk you through building PowerShell on Windows, targeting .NET Core.
5
5
We'll start by showing how to set up your environment from scratch.
6
6
7
7
You can also [build PowerShell for Full .NET framework](windows-full.md) on Windows.
@@ -24,14 +24,14 @@ This guide assumes that you have recursively cloned the PowerShell repository an
24
24
Visual Studio
25
25
----------------
26
26
27
-
You will need to install an edition of Visual Studio 2015 (Community, Enterprise, or Professional) with the optional feature 'Common Tools for Visual C++' installed.
27
+
You will need to install an edition of Visual Studio 2015 (Community, Enterprise, or Professional) with the optional feature 'Common Tools for Visual C++' installed.
28
28
The free Community edition of Visual Studio 2015 can be downloaded [here](https://www.visualstudio.com/visual-studio-community-vs/).
29
29
30
30
.NET CLI
31
31
--------
32
32
33
33
We use the [.NET Command Line Interface][dotnet-cli] (`dotnet`) to build PowerShell.
34
-
The version we are currently using is `1.0.1`.
34
+
The version we are currently using is `1.0.1`.
35
35
The `Start-PSBootstrap` function will automatically install it and add it to your path:
36
36
37
37
```powershell
@@ -69,17 +69,17 @@ Start-PSBuild
69
69
70
70
Congratulations! If everything went right, PowerShell is now built and executable as `./src/powershell-win-core/bin/Debug/netcoreapp1.1/win10-x64/powershell`.
71
71
72
-
This location is of the form `./[project]/bin/[configuration]/[framework]/[rid]/[binary name]`,
73
-
and our project is `powershell`, configuration is `Debug` by default,
74
-
framework is `netcoreapp1.1`, runtime identifier is **probably**`win10-x64`
75
-
(but will depend on your operating system;
76
-
don't worry, `dotnet --info` will tell you what it was), and binary name is `powershell`.
77
-
The function `Get-PSOutput` will return the path to the executable;
72
+
This location is of the form `./[project]/bin/[configuration]/[framework]/[rid]/[binary name]`,
73
+
and our project is `powershell`, configuration is `Debug` by default,
74
+
framework is `netcoreapp1.1`, runtime identifier is **probably**`win10-x64`
75
+
(but will depend on your operating system;
76
+
don't worry, `dotnet --info` will tell you what it was), and binary name is `powershell`.
77
+
The function `Get-PSOutput` will return the path to the executable;
78
78
thus you can execute the development copy via `& (Get-PSOutput)`.
79
79
80
-
The `powershell` project is the .NET Core PowerShell host.
81
-
It is the top level project, so `dotnet build` transitively builds all its dependencies,
82
-
and emits a `powershell` executable.
80
+
The `powershell` project is the .NET Core PowerShell host.
81
+
It is the top level project, so `dotnet build` transitively builds all its dependencies,
82
+
and emits a `powershell` executable.
83
83
The cross-platform host has built-in documentation via `--help`.
84
84
85
85
You can run our cross-platform Pester tests with `Start-PSPester`.
Copy file name to clipboardExpand all lines: docs/community/governance.md
+20-20
Original file line number
Diff line number
Diff line change
@@ -2,20 +2,20 @@
2
2
3
3
## Terms
4
4
5
-
*[**PowerShell Committee**](#powershell-committee): A committee of project owners who are responsible for design decisions, approving [RFCs][RFC-repo], and approving new maintainers/committee members
5
+
*[**PowerShell Committee**](#powershell-committee): A committee of project owners who are responsible for design decisions, approving [RFCs][RFC-repo], and approving new maintainers/committee members
6
6
***Project Leads**: Project Leads support the PowerShell Committee, engineering teams, and community by working across Microsoft teams and leadership, and working through industry issues with other companies.
7
7
They also have optional votes on the PowerShell Committee when they choose to invoke them. The initial Project Leads for PowerShell are Angel Calvo ([AngelCalvo](https://github.com/AngelCalvo)) and Kenneth Hansen ([khansen00](https://github.com/khansen00)).
8
8
*[**Repository maintainer**](#repository-maintainers): An individual responsible for merging pull requests (PRs) into `master` when all requirements are met (code review, tests, docs, and RFC approval as applicable).
9
9
Repository Maintainers are the only people with write permissions into `master`.
10
-
*[**Area experts**](#area-experts): People who are experts for specific components (e.g. PSReadline, the parser) or technologies (e.g. security, performance).
11
-
Area experts are responsible for code reviews, issue triage, and providing their expertise to others.
10
+
*[**Area experts**](#area-experts): People who are experts for specific components (e.g. PSReadline, the parser) or technologies (e.g. security, performance).
11
+
Area experts are responsible for code reviews, issue triage, and providing their expertise to others.
12
12
***Corporation**: The Corporation owns the PowerShell repository and, under extreme circumstances, reserves the right to dissolve or reform the PowerShell Committee, the Project Leads, and the Corporate Maintainer.
13
13
The Corporation for PowerShell is Microsoft.
14
14
***Corporate Maintainer**: The Corporate Maintainer is an entity, person or set of persons, with the ability to veto decisions made by the PowerShell Committee or any other collaborators on the PowerShell project.
15
-
This veto power will be used with restraint since it is intended that the community drive the project.
15
+
This veto power will be used with restraint since it is intended that the community drive the project.
16
16
The Corporate Maintainer is determined by the Corporation both initially and in continuation.
17
17
The initial Corporate Maintainer for PowerShell is Jeffrey Snover ([jpsnover](https://github.com/jpsnover)).
18
-
*[**RFC process**][RFC-repo]: The "review-for-comment" (RFC) process whereby design decisions get made.
18
+
*[**RFC process**][RFC-repo]: The "review-for-comment" (RFC) process whereby design decisions get made.
19
19
20
20
## PowerShell Committee
21
21
@@ -31,7 +31,7 @@ The PowerShell Committee and its members (aka Committee Members) are the primary
31
31
32
32
### Committee Member Responsibilities
33
33
34
-
Committee Members are responsible for reviewing and approving [PowerShell RFCs][RFC-repo] proposing new features or design changes.
34
+
Committee Members are responsible for reviewing and approving [PowerShell RFCs][RFC-repo] proposing new features or design changes.
35
35
36
36
#### Changes that require an [RFC][RFC-repo]
37
37
@@ -45,14 +45,14 @@ The following types of decisions require a written RFC and ample time for the co
45
45
46
46
#### Changes that don't require an RFC
47
47
48
-
In some cases, a new feature or behavior may be deemed small enough to forgo the RFC process
48
+
In some cases, a new feature or behavior may be deemed small enough to forgo the RFC process
49
49
(e.g. changing the default PSReadline `EditMode` to `Emacs` on Mac/Linux).
50
-
In these cases, [issues marked as `1 - Planning`][issue-process] require only a simple majority of Committee Members to sign off.
50
+
In these cases, [issues marked as `1 - Planning`][issue-process] require only a simple majority of Committee Members to sign off.
51
51
After that, a Repository Maintainer should relabel the issue as `2 - Ready` so that a contributor can begin working on it.
52
52
53
-
If any Committee Members feels like this behavior is large enough to warrant an RFC, they can add the label `RFC-required` and the issue owner is expected to follow the RFC process.
53
+
If any Committee Members feels like this behavior is large enough to warrant an RFC, they can add the label `RFC-required` and the issue owner is expected to follow the RFC process.
54
54
55
-
#### Committee Member DOs and DON'Ts
55
+
#### Committee Member DOs and DON'Ts
56
56
57
57
As a PowerShell Committee Member:
58
58
@@ -73,23 +73,23 @@ Members are encouraged to share their opinions, but they should be presented as
73
73
### PowerShell Committee Membership
74
74
75
75
The initial PowerShell Committee consists of Microsoft employees.
76
-
It is expected that over time, PowerShell experts in the community will be made Committee Members.
77
-
Membership is heavily dependent on the level of contribution and expertise: individuals who contribute in meaningful ways to the project will be recognized accordingly.
76
+
It is expected that over time, PowerShell experts in the community will be made Committee Members.
77
+
Membership is heavily dependent on the level of contribution and expertise: individuals who contribute in meaningful ways to the project will be recognized accordingly.
78
78
79
-
At any point in time, a Committee Member can nominate a strong community member to join the Committee.
79
+
At any point in time, a Committee Member can nominate a strong community member to join the Committee.
80
80
Nominations should be submitted in the form of [RFCs][RFC-repo] detailing why that individual is qualified and how they will contribute.
81
-
After the RFC has been discussed, a unanimous vote will be required for the new Committee Member to be confirmed.
81
+
After the RFC has been discussed, a unanimous vote will be required for the new Committee Member to be confirmed.
82
82
83
83
## Repository Maintainers
84
84
85
-
Repository Maintainers are trusted stewards of the PowerShell repository responsible for maintaining consistency and quality of PowerShell code.
85
+
Repository Maintainers are trusted stewards of the PowerShell repository responsible for maintaining consistency and quality of PowerShell code.
86
86
One of their primary responsibilities is merging pull requests after all requirements have been fulfilled.
87
87
88
88
For more information on Repository Maintainers--their responsibilities, who they are, and how one becomes a Maintainer--see the [README for Repository Maintainers][maintainers].
89
89
90
90
## Area Experts
91
91
92
-
Area Experts are people with knowledge of specific components or technologies in the PowerShell domain. They are responsible for code reviews, issue triage, and providing their expertise to others.
92
+
Area Experts are people with knowledge of specific components or technologies in the PowerShell domain. They are responsible for code reviews, issue triage, and providing their expertise to others.
93
93
94
94
They have [write access](https://help.github.com/articles/permission-levels-for-an-organization-repository/) to the PowerShell repository which gives them the power to:
95
95
@@ -99,14 +99,14 @@ They have [write access](https://help.github.com/articles/permission-levels-for-
99
99
100
100
### Area Expert Responsibilities
101
101
102
-
If you are an Area Expert, you are expected to be actively involved in any development, design, or contributions in your area of expertise.
102
+
If you are an Area Expert, you are expected to be actively involved in any development, design, or contributions in your area of expertise.
103
103
104
104
If you are an Area Expert:
105
105
106
106
1.**DO** assign the [correct labels][issue-process]
107
107
1.**DO** assign yourself to issues labeled with your area of expertise
108
108
1.**DO** code reviews for issues where you're assigned or in your areas of expertise.
109
-
1.**DO** reply to new issues and pull requests that are related to your area of expertise
109
+
1.**DO** reply to new issues and pull requests that are related to your area of expertise
110
110
(while reviewing PRs, leave your comment even if everything looks good - a simple "Looks good to me" or "LGTM" will suffice, so that we know someone has already taken a look at it).
111
111
1.**DO** make sure contributors are following the [contributor guidelines](../../.github/CONTRIBUTING.md).
112
112
1.**DO** ask people to resend a pull request, if it [doesn't target `master`](../../.github/CONTRIBUTING.md#lifecycle-of-a-pull-request).
@@ -122,12 +122,12 @@ If you are an Area Expert:
122
122
123
123
See our [Issue Management Process][issue-process]
124
124
125
-
## Pull Request Process
125
+
## Pull Request Process
126
126
127
127
See our [Pull Request Process][pull-request-process]
0 commit comments