Update about page

about.html

@@ -15,31 +15,31 @@ <h1>Goals</h1>
 
 <br/><br/>
 
-The Tau Labs software is released under the GPL and will be treated in that spirit.  Porting the software to new boards is encouraged and fun.  The project will also maintain a set of reference platforms which the code will be more frequently tested against and will be expected to perform optimally.  As it was put, these will receive “A+ development support.”  As Lilvinz put it, with open source you can only give and create and we want to continue doing that.
+The Tau Labs software is released under the GPL and will be treated in that spirit.  Porting the software to new boards is encouraged and fun.  The project will also maintain a set of reference platforms which the code will be more frequently tested against and will be expected to perform optimally. A complete list of supported targets can be found <a href="http://wiki.taulabs.org">here</a>. 
 
 
 <h1>Reference Platforms and Inclusion into project</h1>
-The current reference platforms are the Quanton for higher end applications and the ST F3Discovery board as an easily accessible platform.  The Freedom has been designed by the project and features a gumstix Overo header as well as a full complement of sensors.  The F3discovery board is manufactured by ST and costs less than 25$.
+The current reference platforms are the Quanton for higher end applications and the ST F3Discovery board as an easily accessible platform. SThe F3discovery board is manufactured by ST and costs less than 25$, which makes it a great target for students wanting a flexible board. Sparky is also available as a small F3 based board. 
 
 <br/><br/>
 
-A second tier of reference platforms that would be ideal are reference applications - a complete flying setup including board and airframe for certain applications.  This is ideal for supporting researchers and students who might want to focus goals beyond just getting in the air.
+As described in our goals, porting the software to other boards is encouraged.  We liken this to the Android model where Google produces a reference platform and encourages a rich ecosystem of extensions and modifications.  Other targets are eligible to be merged to next provided they are supported by a maintainer and the hardware design is published with an open source license. People can also maintain their own forks to support other targets that to not meet these crtieria.
 
 <br/><br/>
 
-As described in our goals, porting the software to other boards is encouraged.  We liken this to the Android model where Google produces a reference platform and encourages a rich ecosystem of extensions and modifications.  The conclusion of the meeting was to only maintain the reference platforms in the core source tree and allow other targets to live in their own forks so that the appropriate maintainers can ensure compatibility with any changes applied to the reference platform.  Subsequent discussion implied we might allow targets in whose maintainers are active and responsive. Those targets will be considered as ‘contributions’, our reference platforms remaining the main focus for development and especially testing.
-<br/><br/>
 We will welcome patches back into the core architecture (e.g. PiOS) to support other targets if they are implemented cleanly and improve the code base.  Also new drivers will be welcomed as this will improve the power of PiOS for everyone.
+
 <br/>
+
 <h1>Financing and Infastructure</h1>
 The first goal is to keep running costs low.  That means using free hosting services when possible.  We will use the GitHub wiki and become proficient in it to see if that is really a limitation.  There have been some offers to donate server bandwidth and Gussy and PT_Dreamer will follow up on that to see about setting up a forum. Edouard volunteered to provide backup storage.
 
 <br/><br/>
 
-The second goal is to avoid situations where people acquire debt which affects the project decisions.  What finances the project does have to deal with will be run through the non-profit that Gussy and CheBuzz have already established.  In addition we will try and merge that board of directors and the various committees into the project decision making process.  We discussed if the project needs funds that all of the developers who would like to can contribute to a fund managed by the non-profit.  Hardware provided to the developers should not be given away which creates implied obligations, but should be sold at cost.
+The second goal is to avoid situations where people acquire debt which affects the project decisions. What finances the project does have to deal with will be run through the OmniLoco Foundation, which is the foundation behind Tau Labs. If the project needs funds then anyone who would like to can contribute to a fund managed by the non-profit. Hardware provided to the developers should not be given away which creates implied obligations, but should be sold at cost.
 
 <h1>Hardware manufacturing</h1>
-The project will not be responsible for making hardware directly.  The reference platforms might already be available (e.g. F3 discovery) or will be release CC-BY-SA.  We also won’t stigmatize any businesses that makes the design and sells it - keeping in mind the reference platform cannot be expected to perform in a specific way that is suited to a particular application.  Anyone manufacturing can contribute profits back to the non-profit and this will be transparently documented in order to say “supports the Project”. By definition, the non-profit organization will publish regular accounts on its use of funds.
+The project will not be responsible for making hardware directly.  The reference platforms might already be available (e.g. F3 discovery) or will be release CC-BY-SA.  We also won’t stigmatize any businesses that makes the design and sells it - keeping in mind the reference platform cannot be expected to perform in a specific way that is suited to a particular application. Anyone manufacturing can contribute profits back to the non-profit and this will be transparently documented in order to say “supports the Project”. By definition, the non-profit organization will publish regular accounts on its use of funds.
 
 <br/><br/>