Added missing credits

wycats · Feb 16, 2011 · 9afb749 · 9afb749
1 parent f9e1f14
commit 9afb749
Show file tree

Hide file tree

Showing 10 changed files with 49 additions and 2 deletions.
diff --git a/guides.yml b/guides.yml
@@ -15,9 +15,24 @@ authors:
       nick: jz
       description: Jason Zimdars is an experienced creative director and web designer who has lead UI and UX design for numerous websites and web applications. You can see more of his design and writing at <a href="http://www.thinkcage.com/">Thinkcage.com</a> or follow him on <a href="http://twitter.com/JZ">Twitter</a>
   Contributors:
+    - name: Alex Iskander
+      nick: ialexi
+      description: Member of the SproutCore core team.
+    - name: Florian Kugler
+      nick: fkugler
+      description: ""
     - name: Shawn Morel
       nick: shawnmorel
       description: Shawn Morel is a software generalist with lots of experience building user interfaces in Cocoa, Flex, and bare-bones HTML.
+    - name: Scott Smith
+      nick: ssmith
+      description: ""
+    - name: Devin Torres
+      nick: dtorres
+      description: ""
+    - name: 'Vibul "Veebs" Imtarnasan'
+      nick: veebs
+      description: ""
 
 index:
   Start Here:

diff --git a/source/adding_unit_test.textile b/source/adding_unit_test.textile
@@ -164,3 +164,7 @@ Once you've added a unit test file, now you need to write some unit test code.
 Learn more by writing your first unit test.
 
 On to "Writing Unit Test Cases »":/writing_unit_tests.html
+
+h3. Changelog
+
+* February 15, 2011: initial version by "Scott Smith":credits.html#ssmith and "Vibul &quot;Veebs&quot; Imtarnasan":credits.html#veebs
diff --git a/source/chance.textile b/source/chance.textile
@@ -382,3 +382,7 @@ To avoid needlessly including the same data twice, skip the middle slice:
 You can supply a space-separated list of slices to skip. The possible slice
 names are +top-left+, +top+, +top-right+, +left+, +middle+, +right+,
 +bottom-left+, +bottom+, and +bottom-right+.
+
+h3. Changelog
+
+* January 20, 2011: initial version by "Alex Iskander":credits.html#ialexi
diff --git a/source/running_unit_tests.textile b/source/running_unit_tests.textile
@@ -106,4 +106,7 @@ This concludes the main programming guide for working with Unit Tests in SproutC
 
 On to the "SproutCore Testing Guidelines »":/testing_guidelines.html
 
+h3. Changelog
 
+* February 15, 2011: initial version by "Scott Smith":credits.html#ssmith and "Vibul &quot;Veebs&quot; Imtarnasan":credits.html#veebs
+* February 15, 2011: minor revisions by "Peter Wagenet":credits.html#pwagenet
diff --git a/source/test_driven_development.textile b/source/test_driven_development.textile
@@ -18,3 +18,7 @@ h3. Test-drive SproutCore Method Implementation
 h3. Test-drive Observer Implementation
 
 h3. Test-drive Bindings Implementation
+
+h3. Changelog
+
+* February 15, 2011: initial placeholder by "Scott Smith":credits.html#ssmith and "Vibul &quot;Veebs&quot; Imtarnasan":credits.html#veebs
diff --git a/source/testing_guidelines.textile b/source/testing_guidelines.textile
@@ -23,4 +23,8 @@ h3. Next
 
 Let's reinvent the *todos* project using TDD techniques.
 
-On to "SproutCore Development Using TDD »":/todos_tdd.html
+On to "SproutCore Development Using TDD »":/todos_tdd.html
+
+h3. Changelog
+
+* February 15, 2011: initial placeholder by "Scott Smith":credits.html#ssmith and "Vibul &quot;Veebs&quot; Imtarnasan":credits.html#veebs
diff --git a/source/theming_app.textile b/source/theming_app.textile
@@ -467,3 +467,6 @@ have to add it to your theme's +theme.js+ and remove it from your app's:
 MyTheme.Error = MyTheme.subtheme('error');
 </javascript>
 
+h3. Changelog
+
+* January 17, 2011: initial version by "Alex Iskander":credits.html#ialexi
diff --git a/source/todos_tdd.textile b/source/todos_tdd.textile
@@ -351,4 +351,8 @@ Todos.mainPage = SC.Page.design({
 });
 </javascript>
 
-Generally, since I tend to think of the binding to the description and the value as functionality, I think I would want an integration test which checks both of those values. However for the sake of brevity (this post is already quite long), I'll leave out those tests.
+Generally, since I tend to think of the binding to the description and the value as functionality, I think I would want an integration test which checks both of those values. However for the sake of brevity (this post is already quite long), I'll leave out those tests.
+
+h3. Changelog
+
+* February 15, 2011: initial version by "Scott Smith":credits.html#ssmith and "Vibul &quot;Veebs&quot; Imtarnasan":credits.html#veebs
diff --git a/source/unit_test_framework.textile b/source/unit_test_framework.textile
@@ -107,3 +107,7 @@ Now that you know the basics of how to use unit tests,
 it's time to start adding unit tests to your project.
 
 See "Adding Unit Test Files »":/adding_unit_test.html
+
+h3. Changelog
+
+* February 15, 2011: initial version by "Scott Smith":credits.html#ssmith and "Vibul &quot;Veebs&quot; Imtarnasan":credits.html#veebs
diff --git a/source/writing_unit_tests.textile b/source/writing_unit_tests.textile
@@ -228,4 +228,6 @@ Now that you have written a unit test case or two, it's time to run them.  The n
 
 On to "Running Unit Tests »":/running_unit_tests.html
 
+h3. Changelog
 
+* February 15, 2011: initial version by "Scott Smith":credits.html#ssmith and "Vibul &quot;Veebs&quot; Imtarnasan":credits.html#veebs