Fix some typos

George Oikonomou
2013-11-20 15:16:29 -08:00
parent eca4d3329f
commit 5f4f81fa42

@@ -180,16 +180,16 @@ term, people who maintain a reasonable level of commitment and who demonstrate
that they know what they're doing may be invited to become repo collaborators.
* The hardware must be commercially available and of interest to a wide audience.
In other words, ports for bespoke hardware built for e.g. a specific project /
a single customer / niche markets are more suitable for a Contiki fork
a single customer / niche markets are more suitable for a Contiki fork.
* The code must strictly adhere to the Contiki code style, as discussed above.
* The new files must have a clear copyright notice and license header. Contiki's
preferred software license is the
[3-clause BSD](http://opensource.org/licenses/BSD-3-Clause).
Other licenses may also be considered
as long as they are compatible with the 3-clause BSD (e.g. the Apache 2.0 license).
Conversely, code distribute under GPL cannot be considered. The same applies to
bespoke licenses, such as those allowing redistribution only together with certain
kinds of hardware.
Conversely, code distributed under GPL cannot be considered. The same applies to
bespoke licenses, such as those allowing use or redistribution only together with
certain kinds of hardware.
* The port must demonstrate a certain degree of completeness and maturity. Common sense
applies here.
* The port must be accompanied by examples demonstrating basic functionality. This could
@@ -214,7 +214,7 @@ However, we will insist on the existence of a free alternative for everything.
After the port has been accepted, things meant to work off the shelf should keep working off the shelf as Contiki moves forward.
We appreciate that for many people, contributing to Contiki is a spare time activity
We appreciate that, for many people, contributing to Contiki is a spare time activity
and our expectations from port maintainers take this into consideration. All we ask
from maintainers is to comment on and address relevant pull requests at a reasonable
frequency and to make sure travis keeps passing. In other words, we just want platforms