Skip to content

Commit 7bb301d

Browse files
richlandermairaw
andauthored
Fix linter errors (#10119)
* Fix linter errors * Update Documentation/security-group/dotnet-security-group-agreement.md Co-authored-by: Maira Wenzel <[email protected]> --------- Co-authored-by: Maira Wenzel <[email protected]>
1 parent 17b2c26 commit 7bb301d

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

Documentation/security-group/dotnet-security-group-agreement.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Microsoft Corporation (“Microsoft”) is pleased to work with Company Ltd. (
88

99
3. **Collaboration with Other Parties**. Microsoft intends to engage with a group of interested and known industry parties (who have also entered into an agreement substantially the same as this Agreement) in a similar way as Microsoft and Collaborator are collaborating under this Agreement. Each party agrees to use commercially reasonable efforts to collaborate in good faith with all other such parties to the program. Within the group, parties may share information relating to their respective products, builds, schedules, processes, dependencies, etc. Collaborator agrees to keep confidential all information received from other parties while participating in the group.
1010

11-
4. **Proprietary Rights**. With the exception of information shared under Section 1, neither party grants the other (by implication, estoppel or otherwise) any right, title, interest, or license, in any patents, patent applications, trade secrets, copyrights, mask work rights, trademarks or other intellectual property. Collaborator grants Microsoft a license to use, publish, and commercialize information shared under Section 1.
11+
4. **Proprietary Rights**. With the exception of information shared under Section 1, neither party grants the other (by implication, estoppel or otherwise) any right, title, interest, or license, in any patents, patent applications, trade secrets, copyrights, mask work rights, trademarks or other intellectual property. Collaborator grants Microsoft a license to use, publish, and commercialize information shared under Section 1.
1212

1313
5. **Data**. Collaborator and Microsoft will not provide each other with any customer data, personal data, or personally identifiable information in connection with this Agreement.
1414

@@ -20,7 +20,7 @@ Microsoft Corporation (“Microsoft”) is pleased to work with Company Ltd. (
2020

2121
9. **Limitation of liability**. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE PARTIES LIMIT THEIR LIABILITY FOR ANY CLAIMS UNDER THIS AGREEMENT TO $500 USD AND IN NO EVENT WILL EITHER PARTY (INCLUDING THEIR DIRECTORS, OFFICERS AND AFFILIATES) BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE, SPECIAL, OR EXEMPLARY DAMAGES ARISING OUT OF THIS AGREEMENT. THESE EXCLUSIONS APPLY REGARDLESS OF WHETHER APPLICATION OF THESE EXCLUSIONS CAUSES ANY REMEDY TO FAIL OF ITS ESSENTIAL PURPOSE. THIS SECTION 9 WILL NOT APPLY TO LIABILITY ARISING OUT OF EITHER PARTY’S LIABILITY FOR (i) VIOLATION OF ITS CONFIDENTIALITY OBLIGATIONS OR (ii) WILLFUL MISCONDUCT.
2222

23-
10. **Governing Law**. The terms of this Agreement will be governed and construed in accordance with the laws of the state of New York of the United States of America, U.S.A.
23+
10. **Governing Law**. The terms of this Agreement will be governed and construed in accordance with the laws of the state of New York of the United States of America, U.S.A.
2424

2525
11. **Entire agreement; assignment**. This Agreement is the entire agreement between the parties regarding its limited subject matter and merges and replaces all prior and contemporaneous agreements, communications, and representations between the parties regarding its subject matter. Collaborator may not assign or transfer this Agreement to a third party without Microsoft’s prior written consent.
2626

Documentation/security-group/dotnet-security-group.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,18 +14,18 @@ Membership in the Group is limited to companies that distribute or support .NET
1414

1515
Members:
1616

17-
- Canonical
18-
- IBM
19-
- Microsoft
20-
- Red Hat
17+
- Canonical
18+
- IBM
19+
- Microsoft
20+
- Red Hat
2121

2222
## Responsibilities
2323

2424
The group is modelled on common open source practices. It is oriented on source as the shared artifact and securing supply chains that rely on supported .NET versions. There is no affordance for sharing source patches for unsupported .NET versions or binaries. Binary sharing establishes a high level of business continuity, which is outside the scope of a program oriented around an open source project.
2525

2626
Members must publish builds for supported .NET versions. They can additionally patch end-of-life .NET versions, however, that activity is outside the scope of the Group. Members who exclusively use early-access source patches to update end-of-life versions may be removed from the program.
2727

28-
Members are expected to be active in `main` or other active branches as an investment in the .NET ecosystem. Doing that demonstrates a strong commitment to the ecosystem and earned community credibility.
28+
Members are expected to be active in `main` or other active branches as an investment in the .NET ecosystem. Doing that demonstrates a strong commitment to the ecosystem and earned community credibility.
2929

3030
## Vulnerability publishing process
3131

@@ -48,4 +48,4 @@ This process applies to [supported .NET releases](https://github.com/dotnet/core
4848

4949
Vulnerability reports should be sent through the [security reporting process](https://github.com/dotnet/runtime/blob/main/README.md#reporting-security-issues-and-security-bugs).
5050

51-
Inquiries about the Group can be sent to [[email protected]](mailto:[email protected]).
51+
Inquiries about the Group can be sent to [[email protected]](mailto:[email protected]).

0 commit comments

Comments
 (0)