Updated with some insight on seeding locally vs remotely.

diff --git a/GSoC2010DataSeeder.wiki b/GSoC2010DataSeeder.wiki
index 061789e..3a0e564 100644
--- a/GSoC2010DataSeeder.wiki
+++ b/GSoC2010DataSeeder.wiki

@@ -130,6 +130,26 @@
 Python fixtures are used to easily set up and tear down a database for test purposes. The fixture module supports easy addition of static predefined data to the datastore and it's very well integrated with unit tests. The data seeder's main purpose however is to load arbitrary random data.
 
 A local script could be used to generate a fixture dataset file from a configuration sheet which will then be used for unit testing. This will make it easy to provide lots of generated data to tests, and in the same time ensure that the data used for tests will not change because of randomness.
+
+== Remote vs local ==
+
+While it is necessary to use the GAE Task Queue API for seeding a live instance, it's too much of an overhead for seeding locally, especially for automated tests.
+
+Therefore, I find the need for two scripts that will handle local data generation and seeding, by using a configuration sheet, provided by the web interface. The scripts should be minimal, reusing most of the implementation provided in the SoC data seeder module implementation.
+
+  # *Python fixture generator*
+{{{
+This script generates Python fixture datasets for use with unit tests, based on a data seeder JSON configuration file.
+
+Usage: ./gen_fixture.py [-o output.py] <configuration.json>
+}}}
+  # *Local data seeder*
+{{{
+This script seeds the local datastore based on a data seeder JSON configuration file.
+
+Usage: ./data_seeder.py <configraution.json>
+}}}
+
 = Meetings and Agendas =
 
 == Wednesday May 12, 2010 8:00 in UTC ==