Changes between Version 9 and Version 10 of SummerOfCode2007

Timestamp:

Mar 13, 2007, 3:37:23 PM (18 years ago)

Author:

Jacob

Comment:

--

SummerOfCode2007

@@ -28 +28 @@
 Try to scope ideas/proposals to the 4-month timeline -- simply proposing to fix a ticket or two will probably result in your proposal being rejected in favor of a more ambitious one.  The SOC '''does not cover activities other than coding''', so certain ideas ("Write a more detailed tutorial" or "Create demonstration screencasts" or "Add a pony") are not suitable for inclusion here.
 
+On the other side, though, be sure to be concrete in your proposal. We'll want to know what your goals are, and how you plan to accomplish them.
+
 In no particular order:
+
+ * Build a public repository for reusable Django applications.  This probably includes:
+   * a standard way of packaging Django apps for distribution
+   * infrastructure for automatically downloading and installing packaged Django apps.
 
  * Add optional object-level caching for objects in the cache backend
@@ -36 +42 @@
    * Coherency could be maintained by invalidating/replacing the cached copy when an object is saved
    * It should be possible to force the retrieval to pull the record from the database if the programmer knows it is necessary (DB-level coherency is required)
- * Finalize TextIndexingAbstractionLayer and get it merged into trunk
- * Finalize FullHistory and get it merged into trunk
- * Finalize SchemaEvolution and get it merged into trunk
- * Finalize RowLevelPermissions and get it merged into trunk
+
+ * Create a set of generic RESTful API views (like wsgicollection).
+
+ * Finalize one of the open branches: TextIndexingAbstractionLayer, FullHistory, SchemaEvolution, RowLevelPermissions.
+
+ * Some idea from [http://code.djangoproject.com/wiki/SummerOfCode2006 last year] that didn't get tried.
+  
  * Placeholder - add your ideas here.