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: CONTRIBUTING.md
+8-9
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Contributing to Platform for Situated Intelligence
2
2
3
-
We welcome contributions from the community in a variety of forms: from simply using it and filing issues and bugs, to writing and releasing your own new components, to creating pull requests for bug fixes or new features, etc. This document describes some of the things you need to know if you are going to contribute to the Platform for Situated Intelligence ecosystem. Please read it carefully before making source code changes.
3
+
We welcome contributions from the community in a variety of forms: from simply using it and filing issues and bugs, to writing and releasing your own new components, to creating pull requests for bug fixes or new features, etc. This document describes some of the things you need to know if you are going to contribute to the Platform for Situated Intelligence ecosystem.
4
4
5
5
## Code of conduct
6
6
@@ -60,12 +60,14 @@ Below is a description of the directory structure for the Platform for Situated
60
60
| Sources | Audio | Contains class libraries for audio components. |
61
61
| Sources | Calibration | Contains class libraries for calibrating cameras. |
62
62
| Sources | Common | Contains class libraries for common test support. |
63
-
| Sources | Extensions | Contains class libraries that extend the \psi runtime class libraries. |
63
+
| Sources | Data | Contains class libraries for creating and manipulating datasets. |
64
+
| Sources | Devices | Contains class libraries that support enumerating devices. |
64
65
| Sources | Imaging | Contains class libraries for \psi imaging, e.g. images, video capture, etc. |
65
66
| Sources | Integrations | Contains integrations - libraries that provide shims around 3rd party libraries. |
66
-
| Sources | Kinect | Contains class libraries for Kinect sensor components. |
67
+
| Sources | Kinect | Contains class libraries for Azure Kinect and Kinect V2 sensor components. |
67
68
| Sources | Language | Contains class libraries for natural language processing components. |
68
69
| Sources | Media | Contains class libraries for media components. |
70
+
| Sources | RealSense | Contains class libraries for RealSense sensor component. |
69
71
| Sources | Runtime | Contains class libraries for \psi runtime. |
70
72
| Sources | Speech | Contains class libraries for speech components. |
71
73
| Sources | Toolkits | Contains toolkits - e.g. Finite State Machine toolkit, etc. |
@@ -74,20 +76,17 @@ Below is a description of the directory structure for the Platform for Situated
74
76
75
77
### Coding Style
76
78
77
-
Platform for Situated Intelligence is an organically grown codebase. The consistency of style reflects this.
78
-
For the most part, the team follows these [coding conventions](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/inside-a-program/coding-conventions) along with these [design guidelines](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/). Pull requests that reformat the code will not be accepted.
79
+
For the most part, the Platform for Situated Intelligence codebase follows these [coding conventions](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/inside-a-program/coding-conventions) along with these [design guidelines](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/).
79
80
80
-
In case you would like to add a new project to the `Psi.sln` we require that the project is setup in a similar ways to the other projects to ensure a certain coding standard.
81
+
In case you would like to add a new project to the `Psi.sln` we require that the project is setup in a similar ways to the other projects to ensure consistency.
81
82
82
83
### Build and Test
83
84
84
85
To fully validate your changes, do a complete rebuild and test for both Debug and Release Configurations.
85
86
86
87
### Pull Requests
87
88
88
-
We accept __bug fix pull requests__. Please make sure there is a corresponding tracking issue for the bug. When you submit a PR for a bug, please link to the issue.
89
-
90
-
We also accept __new feature pull requests__. We are available to discuss new features. We recommend you open an issue if you plan to develop new features.
89
+
We accept __bug fix pull requests__ as well as __new feature pull requests__. For bug fixes, please open a corresponding issue for the bug and link to it, if one does not already exist. We also recommend you open an issue if you plan to develop new features, which will help facilitate community discussions about the design, implementation, etc.
Copy file name to clipboardexpand all lines: Directory.Build.props
+2-1
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
<Company>Microsoft Corporation</Company>
7
7
<Owners>microsoft,psi</Owners>
8
8
<Authors>Microsoft</Authors>
9
-
<AssemblyVersion>0.11.82.2</AssemblyVersion>
9
+
<AssemblyVersion>0.12.53.2</AssemblyVersion>
10
10
<FileVersion>$(AssemblyVersion)</FileVersion>
11
11
<Version>$(AssemblyVersion)-beta</Version>
12
12
<SignAssembly>false</SignAssembly>
@@ -21,6 +21,7 @@
21
21
<!-- Workaround for arbitrary value in AssemblyInformationalVersionAttribute until it is fixed in VS 16 https://github.com/Microsoft/visualfsharp/issues/4822 -->
22
22
<NoWarn>FS2003</NoWarn>
23
23
<LangVersion>latest</LangVersion>
24
+
<RunCodeAnalysis>false</RunCodeAnalysis>
24
25
</PropertyGroup>
25
26
26
27
<!-- Support for building in Visual Studio versions 15.9 and up -->
0 commit comments