[Tinyos-2-commits] CVS: tinyos-2.x/doc/html tep1.html, 1.8,
1.9 tep120.html, 1.8, 1.9
Phil Levis
scipio at users.sourceforge.net
Thu Jun 21 12:38:44 PDT 2007
Update of /cvsroot/tinyos/tinyos-2.x/doc/html
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv28880/html
Modified Files:
tep1.html tep120.html
Log Message:
Nits on TEP 1.
Incorporated alliance commments on TEP 120.
Index: tep1.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep1.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** tep1.html 29 May 2007 22:23:55 -0000 1.8
--- tep1.html 21 Jun 2007 19:38:42 -0000 1.9
***************
*** 304,310 ****
<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">18-Oct-2004</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.5</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2006-12-12</td>
</tr>
<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
--- 304,310 ----
<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">18-Oct-2004</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.6</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-05-29</td>
</tr>
<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
***************
*** 494,499 ****
entitled "Author's Address" or "Author's Addresses" MUST contain
detailed author contact information.</p>
! <p>A TEP MAY have appendices after its Author section. Unlike regular sections,
! appendices are lettered. Please refer to Appendix A for details.</p>
</div>
</div>
--- 494,500 ----
entitled "Author's Address" or "Author's Addresses" MUST contain
detailed author contact information.</p>
! <p>A TEP MAY have appendices after its numbered sections. Unlike
! numbered sections, appendices are lettered. Please refer to Appendix
! A for details.</p>
</div>
</div>
Index: tep120.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep120.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** tep120.html 15 May 2007 23:31:21 -0000 1.8
--- tep120.html 21 Jun 2007 19:38:42 -0000 1.9
***************
*** 378,383 ****
<li>FSF - Foundational software</li>
</ol>
! <p>We (the Alliance) draw most strongly upon the IETF, even though that
! organization was
focused around creating and standardizing protocols, rather than
developing a code base. Its emphasis on rough consensus AND
--- 378,385 ----
<li>FSF - Foundational software</li>
</ol>
! <p>Examining the structure and policies of these organizations helps
! determine what the Alliance can borrow from them, what it must
! do differently, and why. We (the Alliance) draw most strongly upon the
! IETF, even though that organization was
focused around creating and standardizing protocols, rather than
developing a code base. Its emphasis on rough consensus AND
***************
*** 395,402 ****
concept that proper behavior of participants and member companies is
most strongly shaped by code of ethics, captured in organization rules
! and social norms, rather than threats of legal reprocusions. The
broader marketplace is a more effective enforcement body than any
technical organization. Thus, we ask that participants declare
! relevant IP that they are aware of, rather than force a strict
accounting of potentially relevant IP. We encourage the development
of open solutions that are implemented without the need for particular
--- 397,405 ----
concept that proper behavior of participants and member companies is
most strongly shaped by code of ethics, captured in organization rules
! and social norms, rather than threats of legal repercussions. The
broader marketplace is a more effective enforcement body than any
technical organization. Thus, we ask that participants declare
! relevant intellectual proprt (IP) that they are aware of, rather than
! force a strict
accounting of potentially relevant IP. We encourage the development
of open solutions that are implemented without the need for particular
***************
*** 437,441 ****
from obtaining blocking IP. It does discourage contributions that
might pull IP into the pool. We prefer a process of declaration and
! multiple implementation.</p>
</div>
<div class="section">
--- 440,445 ----
from obtaining blocking IP. It does discourage contributions that
might pull IP into the pool. We prefer a process of declaration and
! multiple implementation. Section 7 goes deeper into how the Alliance
! manages the issues and complexities of IP in an open organization.</p>
</div>
<div class="section">
***************
*** 499,503 ****
supervising activities to resolve conflicting directions and moving
the process towards overall architectural coherence.</p>
! <p>The SC is also responsible for reviewing and approving all TEPs. WGs
submit TEPs to the SC for review. The SC should appoint one
contributing Alliance member not affiliated with the corresponding WG
--- 503,508 ----
supervising activities to resolve conflicting directions and moving
the process towards overall architectural coherence.</p>
! <p>The SC is also responsible for reviewing and approving all TinyOS
! Enhancement Proposals (TEPs) that working groups generate. WGs
submit TEPs to the SC for review. The SC should appoint one
contributing Alliance member not affiliated with the corresponding WG
***************
*** 580,584 ****
and production ecosystem around embedded network technology.</p>
<p>The organization will be able to accept direct financial and
! intellectual property contributions. The IP policy should encourage
corporate participation while preserving focus on soundness, merit,
and consensus building. Ultimately, we seek to promote a meritocracy
--- 585,590 ----
and production ecosystem around embedded network technology.</p>
<p>The organization will be able to accept direct financial and
! intellectual property contributions. The IP policy, described
! in Section 7, should encourage
corporate participation while preserving focus on soundness, merit,
and consensus building. Ultimately, we seek to promote a meritocracy
***************
*** 607,610 ****
--- 613,618 ----
<p>The typical output of a working group is technical documentation AND
working code, including interface definitions and standard proposals.
+ While this is the typical output, working groups are not constrained
+ to this model, and can have a variety of purposes and work products.
We seek to promote the development of standardized interfaces,
protocols, services, and tools with high quality, open reference
***************
*** 623,627 ****
open technology. We want to avoid having the advancement of embedded
networks getting trapped into proprietary IP. Accordingly, our IP
! policy builds heavily on the IETF mode. We also want to avoid a high
barrier to participation. Thus, we want to avoid demanding membership
requirements that require extensive legal analysis and assessing deep
--- 631,635 ----
open technology. We want to avoid having the advancement of embedded
networks getting trapped into proprietary IP. Accordingly, our IP
! policy builds heavily on the IETF model. We also want to avoid a high
barrier to participation. Thus, we want to avoid demanding membership
requirements that require extensive legal analysis and assessing deep
***************
*** 663,668 ****
Steering Committee to be able to approve the action.</p>
<p>Of course, Intellectual Property in the TinyOS alliance is closely
! tied to source licensing terms, as dicussed in greater detail in that
! section. As part of Alliance rules, members agree to only check in
code that conforms to Alliance source license policy. As part of
keeping barriers to participation low, GPL and code based on
--- 671,676 ----
Steering Committee to be able to approve the action.</p>
<p>Of course, Intellectual Property in the TinyOS alliance is closely
! tied to source licensing terms, as dicussed in greater detail in Section 8.
! As part of Alliance rules, members agree to only contribute
code that conforms to Alliance source license policy. As part of
keeping barriers to participation low, GPL and code based on
***************
*** 688,697 ****
as their own. This concern is partially addressed by GPL, where if
you build upon the work of others you are obliged to put it back in
! the open. Apache addresses this issue by requiring acreditation of
the Apache foundation. However, this is connected with a stiff
membership requirement of signing the copyright to Apache.
Participants make that sacrifice when they view the brand appeal
associated with the Apache meritocracy as of sufficient value to
! warrant the arrangement. Apache is also a losely affiliated
consortium of relatively localized projects, typically in very well
established technical areas. Our situation is different because we
--- 696,705 ----
as their own. This concern is partially addressed by GPL, where if
you build upon the work of others you are obliged to put it back in
! the open. Apache addresses this issue by requiring accreditation of
the Apache foundation. However, this is connected with a stiff
membership requirement of signing the copyright to Apache.
Participants make that sacrifice when they view the brand appeal
associated with the Apache meritocracy as of sufficient value to
! warrant the arrangement. Apache is also a loosely affiliated
consortium of relatively localized projects, typically in very well
established technical areas. Our situation is different because we
***************
*** 718,722 ****
after several years of proliferation.</p>
<p>To address these matters, the Alliance has a preferred source license
! based on the BSD framework and a small set of accepted licenses, some
of which have been gradfathered in with the existing code
base. Contributions can be made using one of those accepted licenses,
--- 726,731 ----
after several years of proliferation.</p>
<p>To address these matters, the Alliance has a preferred source license
! based on the BSD framework, (the "new" BSD license approved by the
! Open Source Initiative <a class="citation-reference" href="#bsd" id="id2" name="id2">[BSD]</a> ) and a small set of accepted licenses, some
of which have been gradfathered in with the existing code
base. Contributions can be made using one of those accepted licenses,
***************
*** 725,731 ****
Committee. In order to avoid the debate of what constitutes "open
source," the Steering Committee will generally only consider
! OSL-approved licenses for inclusion in the core. If a contributor
wishes to use a completely new license, it can submit the license to
! the OSL first.</p>
<p>We will not require that the Alliance hold copyright of submitted
source code, but that it conform to Alliance guidelines. These
--- 734,743 ----
Committee. In order to avoid the debate of what constitutes "open
source," the Steering Committee will generally only consider
! licenses approved by the Open Source Initiative (OSI) for inclusion in
! the core. However, being an
! OSI-approved license is not a sufficient condition for approval
! within the Alliance. If a contributor
wishes to use a completely new license, it can submit the license to
! the OSI first.</p>
<p>We will not require that the Alliance hold copyright of submitted
source code, but that it conform to Alliance guidelines. These
***************
*** 859,878 ****
</div>
<div class="section">
! <h1><a id="author-s-address" name="author-s-address">12. Author's Address</a></h1>
<div class="line-block">
! <div class="line">Philippe Bonnet <<a class="reference" href="mailto:bonnet.p@gmail.com">bonnet.p@gmail.com</a>></div>
<div class="line">David Culler <dculler at archrock.com></div>
! <div class="line">Deborah Estrin <<a class="reference" href="mailto:destrin@cs.ucla.edu">destrin@cs.ucla.edu</a>></div>
! <div class="line">Ramesh Govindan <<a class="reference" href="mailto:ramesh@usc.edu">ramesh@usc.edu</a>></div>
! <div class="line">Mike Horton <<a class="reference" href="mailto:mhorton@xbow.com">mhorton@xbow.com</a>></div>
! <div class="line">Jeonghoon Kang <<a class="reference" href="mailto:budge@keti.re.kr">budge@keti.re.kr</a>></div>
! <div class="line">Philip Levis <<a class="reference" href="mailto:pal@cs.stanford.edu">pal@cs.stanford.edu</a>></div>
! <div class="line">Lama Nachman <<a class="reference" href="mailto:lama.nachman@intel.com">lama.nachman@intel.com</a>></div>
! <div class="line">Jack Stankovic <<a class="reference" href="mailto:stankovic@cs.virginia.edu">stankovic@cs.virginia.edu</a>></div>
! <div class="line">Rob Szewczyk <<a class="reference" href="mailto:rob@moteiv.com">rob@moteiv.com</a>></div>
! <div class="line">Matt Welsh <<a class="reference" href="mailto:mdw@cs.harvard.edu">mdw@cs.harvard.edu</a>></div>
! <div class="line">Adam Wolisz <<a class="reference" href="mailto:awo@ieee.org">awo@ieee.org</a>></div>
</div>
</div>
</div>
</body>
--- 871,899 ----
</div>
<div class="section">
! <h1><a id="authors-address" name="authors-address">12. Authors' Address</a></h1>
<div class="line-block">
! <div class="line">Philippe Bonnet <bonnet.p at gmail.com></div>
<div class="line">David Culler <dculler at archrock.com></div>
! <div class="line">Deborah Estrin <destrin at cs.ucla.edu></div>
! <div class="line">Ramesh Govindan <ramesh at usc.edu></div>
! <div class="line">Mike Horton <mhorton at xbow.com></div>
! <div class="line">Jeonghoon Kang <budge at keti.re.kr></div>
! <div class="line">Philip Levis <pal at cs.stanford.edu></div>
! <div class="line">Lama Nachman <lama.nachman at intel.com></div>
! <div class="line">Jack Stankovic <stankovic at cs.virginia.edu></div>
! <div class="line">Rob Szewczyk <rob at moteiv.com></div>
! <div class="line">Matt Welsh <mdw at cs.harvard.edu></div>
! <div class="line">Adam Wolisz <awo at ieee.org></div>
</div>
</div>
+ <div class="section">
+ <h1><a id="citations" name="citations">13. Citations</a></h1>
+ <table class="docutils citation" frame="void" id="bsd" rules="none">
+ <colgroup><col class="label" /><col /></colgroup>
+ <tbody valign="top">
+ <tr><td class="label"><a class="fn-backref" href="#id2" name="bsd">[BSD]</a></td><td><a class="reference" href="http://www.opensource.org/licenses/bsd-license.php">http://www.opensource.org/licenses/bsd-license.php</a></td></tr>
+ </tbody>
+ </table>
+ </div>
</div>
</body>
More information about the Tinyos-2-commits
mailing list