Skip to content

Commit 96c7077

Browse files
committed
Add .NET to nF mentions
1 parent 21a86bf commit 96c7077

File tree

6 files changed

+45
-45
lines changed

6 files changed

+45
-45
lines changed

CONTRIBUTORS.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
## **nanoFramework** Contributors
1+
## .NET **nanoFramework** Contributors
22

3-
The following is a list of contributors to the **nanoFramework** project (all repositories), in alphabetical order.
3+
The following is a list of contributors to the .NET **nanoFramework** project (all repositories), in alphabetical order.
44

55
<table>
66
<tr>

README.md

+14-14
Original file line numberDiff line numberDiff line change
@@ -6,31 +6,31 @@
66
-----
77
Document Language: [English](README.md) | [简体中文](README.zh-cn.md)
88

9-
# **nanoFramework** Home
9+
# .NET **nanoFramework** Home
1010

11-
This _Home_ repository is the starting point for developers that want to learn about **nanoFramework**, contribute to it or opening issues.
12-
It contains links to the various GitHub repositories used by **nanoFramework**.
11+
This _Home_ repository is the starting point for developers that want to learn about .NET **nanoFramework**, contribute to it or opening issues.
12+
It contains links to the various GitHub repositories used by .NET **nanoFramework**.
1313

14-
**nanoFramework** goal is to be a platform that enables the writing of managed code applications for constrained embedded devices.
14+
.NET **nanoFramework** goal is to be a platform that enables the writing of managed code applications for constrained embedded devices.
1515
Developers can harness the familiar IDE Visual Studio and their .NET (C#) knowledge to quickly write applications without having to worry about the low level hardware intricacies of a micro-controller.
1616

1717
Being a developer you'll probably will fit in one (or maybe both :wink:) of the following _profiles_:
1818

1919
- Developer: if your goal is to develop C# applications for micro-controllers.
2020
- Contributor: if you are interested in actively contributing by coding (native, managed, C, C++, CMake), writing documentation or participating in the overall project organization.
2121

22-
# Sponsoring **nanoFramework**
22+
# Sponsoring .NET **nanoFramework**
2323

24-
Most of the core team members and contributors are embedded systems enthusiasts, passionate about coding and people that like challenges. The work on **nanoFramework** is done mostly on their free time. Some of the core members happen to work on companies that sponsor heavily **nanoFramework** and offer their work hours to the project. If you use **nanoFramework** for serious work or want to support it, please donate. This allow for paying the infrastructure cost and more time to be invested on the project. Besides monetary contributions, there are several other ways to contribute. Please read the documentation about this [here](http://docs.nanoframework.net/content/contributing/index.html).
24+
Most of the core team members and contributors are embedded systems enthusiasts, passionate about coding and people that like challenges. The work on .NET **nanoFramework** is done mostly on their free time. Some of the core members happen to work on companies that sponsor heavily **nanoFramework** and offer their work hours to the project. If you use .NET **nanoFramework** for serious work or want to support it, please donate. This allow for paying the infrastructure cost and more time to be invested on the project. Besides monetary contributions, there are several other ways to contribute. Please read the documentation about this [here](http://docs.nanoframework.net/content/contributing/index.html).
2525

2626
This is how we use the donations:
2727

2828
- Pay for infrastructure costs.
2929
- Develop public relation actions to get the project known.
3030
- Support maintainers and contributors that invest a large amount of time in the project.
31-
- Support projects that **nanoFramework** depends on.
32-
- Produce documentation, tutorials and other content to support developers using **nanoFramework**.
33-
- Organize events to demo **nanoFramework**.
31+
- Support projects that .NET **nanoFramework** depends on.
32+
- Produce documentation, tutorials and other content to support developers using .NET **nanoFramework**.
33+
- Organize events to demo .NET **nanoFramework**.
3434

3535
## Sponsors
3636

@@ -51,7 +51,7 @@ Backers are individuals who contribute with money to help support nanoFramework.
5151

5252
## Other backers and sponsors
5353

54-
There are other people and organizations that have contributed to **nanoFramework** along the time in several ways: sponsoring the coding of a feature that was missing or needed improvement, paying for an expense, coding a feature or... We would like to acknowledge these sponsors.
54+
There are other people and organizations that have contributed to .NET **nanoFramework** along the time in several ways: sponsoring the coding of a feature that was missing or needed improvement, paying for an expense, coding a feature or... We would like to acknowledge these sponsors.
5555

5656
<table>
5757
<tr>
@@ -127,13 +127,13 @@ See some of our guides for more details:
127127

128128
### [Docs](https://docs.nanoframework.net)
129129

130-
The project documentation is a great place to find information about **nanoFramework**, no matter if you are newcomer or a veteran. It's organized in the following categories:
130+
The project documentation is a great place to find information about .NET **nanoFramework**, no matter if you are newcomer or a veteran. It's organized in the following categories:
131131

132132
- [API reference](http://docs.nanoframework.net/api) documentation for the various class libraries.
133-
- [Developing C# applications](https://docs.nanoframework.net/content/getting-started-guides/getting-started-managed.html#coding-a-hello-world-application) using **nanoFramework**.
133+
- [Developing C# applications](https://docs.nanoframework.net/content/getting-started-guides/getting-started-managed.html#coding-a-hello-world-application) using .NET **nanoFramework**.
134134
- [Building an image](https://docs.nanoframework.net/content/building/index.html) to load on a target board.
135-
- [**nanoFramework** architecture](https://docs.nanoframework.net/content/architecture/index.html) and how the different pieces fit together.
136-
- [Contributing to **nanoFramework**](https://docs.nanoframework.net/content/contributing/index.html) includes an overview on how you can contribute to the project.
135+
- [.NET **nanoFramework** architecture](https://docs.nanoframework.net/content/architecture/index.html) and how the different pieces fit together.
136+
- [Contributing to .NET **nanoFramework**](https://docs.nanoframework.net/content/contributing/index.html) includes an overview on how you can contribute to the project.
137137

138138
### [Blog](https://www.nanoframework.net/blog)
139139

README.zh-cn.md

+14-14
Original file line numberDiff line numberDiff line change
@@ -6,29 +6,29 @@
66
-----
77
文档语言: [English](README.md) | [简体中文](README.zh-cn.md)
88

9-
# **nanoFramework** 首页
9+
# .NET **nanoFramework** 首页
1010

11-
本库是开发者了解 **nanoFramework** 的起点,也可以贡献或提问。它包含了 **nanoFramework** 所使用到的各个GitHub库链接。
11+
本库是开发者了解 .NET **nanoFramework** 的起点,也可以贡献或提问。它包含了 .NET **nanoFramework** 所使用到的各个GitHub库链接。
1212

13-
**nanoFramework** 的目标是在受限嵌入式设备上使用托管代码编写应用。开发者可以利用熟悉的IDE(Visual Studio)和 .NET(C#)知识快速编写应用程序,而无需担心微控制器的低级硬件复杂性。
13+
.NET **nanoFramework** 的目标是在受限嵌入式设备上使用托管代码编写应用。开发者可以利用熟悉的IDE(Visual Studio)和 .NET(C#)知识快速编写应用程序,而无需担心微控制器的低级硬件复杂性。
1414

1515
作为一名开发者,你可以选择以下一种(或两种)角色:
1616

1717
- 开发者:如果你的目标是为微控制器开发C#应用。
1818
- 贡献者:如果你有兴趣通过编码(原生,托管,C/C++,CMake)积极贡献,包括编写文档或者参与整个项目组织。
1919

20-
# 赞助 **nanoFramework**
20+
# 赞助 .NET **nanoFramework**
2121

22-
大多数核心团队成员和贡献者都是嵌入式系统爱好者,热衷于编码和喜欢挑战的人。**nanoFramework** 工作都是他们在工作之余完成。一些核心成员恰好工作于那些大力赞助 **nanoFramework** 并为其提供工作时间的公司。如果你想把 **nanoFramework** 用于正式工作并支持它,请捐赠。这样可以支付基础设施成本,并为项目投入更多的时间。除了货币捐助,还有其它几种捐助方式,请参考 [这里](http://docs.nanoframework.net/content/contributing/index.html).
22+
大多数核心团队成员和贡献者都是嵌入式系统爱好者,热衷于编码和喜欢挑战的人。.NET **nanoFramework** 工作都是他们在工作之余完成。一些核心成员恰好工作于那些大力赞助 .NET **nanoFramework** 并为其提供工作时间的公司。如果你想把 .NET **nanoFramework** 用于正式工作并支持它,请捐赠。这样可以支付基础设施成本,并为项目投入更多的时间。除了货币捐助,还有其它几种捐助方式,请参考 [这里](http://docs.nanoframework.net/content/contributing/index.html).
2323

2424
我们如何使用捐赠:
2525

2626
- 支付基础设施成本。
2727
- 宣传推广项目。
2828
- 支持在项目中投入大量时间的维护人员和贡献者。
29-
- 支持 **nanoFramework** 所依赖的项目。
30-
- 制作产品文档、教程以及其它内容,以支持使用 **nanoFramework** 的其他开发人员。
31-
- 组织活动演示 **nanoFramework**
29+
- 支持 .NET **nanoFramework** 所依赖的项目。
30+
- 制作产品文档、教程以及其它内容,以支持使用 .NET **nanoFramework** 的其他开发人员。
31+
- 组织活动演示 .NET **nanoFramework**
3232

3333
## 赞助商
3434

@@ -38,13 +38,13 @@
3838

3939
## 支持者
4040

41-
支持者是那些用金钱帮助支持 **nanoFramework** 的人。每一点点的帮助,我们都很感激所有的贡献,即使是最小的贡献。
41+
支持者是那些用金钱帮助支持 .NET **nanoFramework** 的人。每一点点的帮助,我们都很感激所有的贡献,即使是最小的贡献。
4242

4343
<a href="https://opencollective.com/nanoframework#support"><img src="https://opencollective.com/nanoframework/tiers/backer.svg?avatarHeight=80"></a>
4444

4545
## 其他支持者和赞助商
4646

47-
还有其他人和组织一直以多种方式为**NanoFramework**做出贡献:赞助对缺失或需要改进的功能进行编码、支付费用、对功能进行编码或……我们要感谢这些赞助商。
47+
还有其他人和组织一直以多种方式为.NET **NanoFramework**做出贡献:赞助对缺失或需要改进的功能进行编码、支付费用、对功能进行编码或……我们要感谢这些赞助商。
4848

4949
<table>
5050
<tr>
@@ -119,13 +119,13 @@
119119

120120
### [文档](https://docs.nanoframework.net/content/index.html)
121121

122-
无论您是新手还是老手,项目文档都是查找有关**NanoFramework**信息的好地方。它按以下类别组织:
122+
无论您是新手还是老手,项目文档都是查找有关.NET **nanoFramework**信息的好地方。它按以下类别组织:
123123

124124
- [API手册](http://docs.nanoframework.net/api) 各种类库的文档。
125-
- [开发C#应用](https://docs.nanoframework.net/content/getting-started-guides/getting-started-managed.html#coding-a-hello-world-application) 使用 **nanoFramework**.
125+
- [开发C#应用](https://docs.nanoframework.net/content/getting-started-guides/getting-started-managed.html#coding-a-hello-world-application) 使用 .NET **nanoFramework**.
126126
- [编译镜像](https://docs.nanoframework.net/content/building/index.html) 加载到目标板上。
127-
- [**nanoFramework**架构](https://docs.nanoframework.net/content/architecture/index.html) 不同的部分是如何组合在一起的。
128-
- [贡献**nanoFramework**](https://docs.nanoframework.net/content/contributing/index.html) 包括如何为项目做出贡献的概述。
127+
- [.NET **nanoFramework**架构](https://docs.nanoframework.net/content/architecture/index.html) 不同的部分是如何组合在一起的。
128+
- [贡献.NET **nanoFramework**](https://docs.nanoframework.net/content/contributing/index.html) 包括如何为项目做出贡献的概述。
129129

130130
### [博客](https://www.nanoframework.net/blog)
131131

THIRD-PARTY-NOTICES.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
## Third party licensing and copyright notices
22

3-
**nanoFramework** components use third-party libraries and other resources that may be distributed under licenses different than the one with our repositories.
3+
.NET **nanoFramework** components use third-party libraries and other resources that may be distributed under licenses different than the one with our repositories.
44

55
Attributions and license notices for test cases originally authored by third parties can be found in the respective test directories.
66

7-
In the event that we accidentally failed to list a required notice, please bring it to our attention by raising an issue, or reaching out in the Discor community.
7+
In the event that we accidentally failed to list a required notice, please bring it to our attention by raising an issue, or reaching out in the Discord community.
88

99
_The attached notices are provided for information only._
1010

docs/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# **nanoFramework** Documentation
1+
# .NET **nanoFramework** Documentation
22

33
Documentation is available [here](http://docs.nanoframework.net/content/introduction/what-is-nanoframework.html).
44

docs/organization/README.md

+12-12
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
1-
# **nanoFramework** GitHub organization
1+
# .NET **nanoFramework** GitHub organization
22

33
Our GitHub organization holds the various repositories for firmware, class libraries, documentation and tools.
4-
Follows a list and description of the repositories under **nanoFramework** organization.
4+
Follows a list and description of the repositories under .NET **nanoFramework** organization.
55

66
## Repositories
77

8-
- [Samples](https://github.com/nanoframework/Samples) - this repo contains sample applications illustrating **nanoFramework** APIs and common use cases.
8+
- [Samples](https://github.com/nanoframework/Samples) - this repo contains sample applications illustrating .NET **nanoFramework** APIs and common use cases.
99

10-
- [nf-interpreter](https://github.com/nanoframework/nf-interpreter) - this repo contains the **nanoFramework** CLR, interpreter, target boards configuration and the build system. This is where everything required to build an image to be flashed into a device lives.
10+
- [nf-interpreter](https://github.com/nanoframework/nf-interpreter) - this repo contains the .NET **nanoFramework** CLR, interpreter, target boards configuration and the build system. This is where everything required to build an image to be flashed into a device lives.
1111

1212
- [nf-Community-Targets](https://github.com/nanoframework/nf-Community-Targets) - this repo contains target boards that are contributed by community members. You might find here _inspiration_ for your next board.
1313

@@ -47,17 +47,15 @@ Follows a list and description of the repositories under **nanoFramework** organ
4747

4848
- [lib-Windows.Storage.Streams](https://github.com/nanoframework/lib-Windows.Storage.Streams) - this repo contains the Windows.Storage.Streams library that is used in developing C# applications.
4949

50-
- [lib-System.Net](https://github.com/nanoframework/lib-System.Net) - this repo contains the System.Net library that is the foundation for networking in **nanoFramework**.
50+
- [lib-System.Net](https://github.com/nanoframework/lib-System.Net) - this repo contains the System.Net library that is the foundation for networking in .NET **nanoFramework**.
5151

5252
- [lib-nanoFramework.Hardware.ESP32](https://github.com/nanoframework/nanoFramework.Hardware.ESP32) - this repo contains the nanoFramework.Hardware.ESP32 class library that exposes hardware features specific of ESP32 targets.
5353

54-
- [nf-Visual-Studio-extension](https://github.com/nanoframework/nf-Visual-Studio-extension) - this repo contains the Visual Studio extension and all the associated tools required to compile and build a **nanoFramework** managed application ready to deploy to a target device.
54+
- [nf-Visual-Studio-extension](https://github.com/nanoframework/nf-Visual-Studio-extension) - this repo contains the Visual Studio extension and all the associated tools required to compile and build a .NET **nanoFramework** managed application ready to deploy to a target device.
5555

5656
- [nf-debugger](https://github.com/nanoframework/nf-debugger) - this repo contains the debugger library (in several technologies) allowing reuse of the low lower library by third party applications.
5757

58-
- [nf-ANT](https://github.com/nanoframework/nf-ANT) - this repo contains an UWP application that connects to a **nanoFramework** target and can provide basic information about it along with some basic management operations. The development of this tool has been put on a halt because its features and capabilities are now available in Visual Studio through the Device Manager window.
59-
60-
- [nf-tools](https://github.com/nanoframework/nf-tools) - this repo contains various tools that are required in **nanoFramework** development, usage or repository management.
58+
- [nf-tools](https://github.com/nanoframework/nf-tools) - this repo contains various tools that are required in .NET **nanoFramework** development, usage or repository management.
6159

6260
- [metadata-processor](https://github.com/nanoframework/metadata-processor) - this repo contains the Meta Data Processor that is used when building C# nanoFramework applications. It's main function is to parse the outputs from Roslyn and build proprietary PE files that will be loaded into the nanoFramework target devices.
6361

@@ -67,8 +65,10 @@ Follows a list and description of the repositories under **nanoFramework** organ
6765

6866
- [esp32-firmware-flasher](https://github.com/nanoframework/esp32-firmware-flasher) - this repo contains the ESP32 firmware flasher tool that is used to update the firmware on ESP32 nanoFramework target devices. It's been superseded by nanoFramework Firmware Flasher.
6967

70-
- [nanoframework.github.io](https://github.com/nanoframework/nanoframework.github.io) - this repo contains the sources and configuration files to generate the **nanoFramework** documentation web site. Any static content, such as articles, guides, how-to's and such is to be checked-in here.
68+
- [nanoframework.github.io](https://github.com/nanoframework/nanoframework.github.io) - this repo contains the sources and configuration files to generate the .NET **nanoFramework** documentation web site. Any static content, such as articles, guides, how-to's and such is to be checked-in here.
69+
70+
- [ChibiOS](https://github.com/nanoframework/ChibiOS) - this repo contains a mirror of the official ChibiOS SVN repository. It's used as the default source for building .NET **nanoFramework** images.
7171

72-
- [ChibiOS](https://github.com/nanoframework/ChibiOS) - this repo contains a mirror of the official ChibiOS SVN repository. It's used as the default source for building **nanoFramework** images.
72+
- [mbedtls](https://github.com/nanoframework/mbedtls) - this repo contains a mirror of the official mbedtls repository. It's used as the default source for building .NET **nanoFramework** images implementing TLS for networking.
7373

74-
- [mbedtls](https://github.com/nanoframework/mbedtls) - this repo contains a mirror of the official mbedtls repository. It's used as the default source for building **nanoFramework** images implementing TLS for networking.
74+
- [nf-ANT](https://github.com/nanoframework/nf-ANT) - this repo contains an UWP application that connects to a .NET **nanoFramework** target and can provide basic information about it along with some basic management operations. The development of this tool has been put on a halt because its features and capabilities are now available in Visual Studio through the Device Manager window.

0 commit comments

Comments
 (0)