(no commit message)

[homepage.git] / wiki / ocamlcore.mdwn

diff --git a/wiki/ocamlcore.mdwn b/wiki/ocamlcore.mdwn
index 37a4b4c..ac5c623 100644 (file)
--- a/wiki/ocamlcore.mdwn
+++ b/wiki/ocamlcore.mdwn
@@ -1,23 +1,51 @@
+[[draft_forge_announcement]]
+[[draft_forge_public_announcement]]
+----
+

 todo list to be completed before announcing the public availability of <http://www.ocamlcore.org>
 
 * having a working forge service, in turn this means:
 
   - test the creation of a project with all the corresponding services
 
 todo list to be completed before announcing the public availability of <http://www.ocamlcore.org>
 
 * having a working forge service, in turn this means:
 
   - test the creation of a project with all the corresponding services
 

-      * vcs (svn at the very minimum)
-      * mailing list
-      * upload/download
-      * tracker
+      * vcs (svn at the very minimum) (2008/02/06 -> OK)
+      * forge mailing list (2008/02/27 -> OK)
+      * upload/download (2008/02/27 -> OK)
+      * tracker (2008/02/06 -> OK)
+      * avoid creating forum (newly created project should follow template project)

       * ...
 
       * ...
 

-  - maybe having a specific theme? or this can be postponed?
+Note: This have not been tested 'in-a-row'. Still needs to be checked against a fresh project..
+  
+  - <span class="strike">do some clean up in mailing list/forge project (don't want to have a test-cvs-1 and bl
+abla project when we released)</span>
+    * removed blabla-2etez, blabla-commits, test-cvs-1-commits (using /var/lib/mailman/bin/rmlist -a)
+    * removed test-cvs-1 and blabla from the forge
+
+  - <span class="strike">fix mailing list admin moderation... (doesn't work since SSL enablement)</span>
+
+  - have a specific theme (it could be simple, but we need one, inspired from INRIA/Caml one)
+
+  - <span class="strike">check that feature requests via the forge interface do work</span> (done through the link below, a feature request for the forge itself)
+
+  - <span class="strike">move the gforge data under /srv</span>

 
 

-  - check that feature requests via the forge interface do work
+  - <span class="strike">backup the postgresql database using pg_dump daily instead of relying on the backup of `/var/lib/postgres/...`</span> (see incr_backup/full_backup, note that it doesn't dump "LARGE OBJECT", so i keep the backup of `/var/lib/postgres/...` for now)

 
 

-  - move the gforge data under /srv
+* <span class="strike">write the terms of services for ocamlcore.org</span>

 
 

-  - backup the postgresql database using pg_dump daily instead of relying on the backup of `/var/lib/postgres/...`
+* <span class="strike">install a planet (planet.ocamlcore.org)</span>

 
 

-* write the terms of services for ocamlcore.org
+* <span class="strike">get SSL certificat from cacert (S. Le Gall)</span>
+
+* create at least hosting for darcs/git/hg(.ocamlcore.org) even if it is not integrated with the forge
+
+* Web redirections:
+
+ -> <span class="strike">HTTPS only once logged into the forge (connection with SSL), no need to overload the server when doing non authenticated navigation</span>

 
 * what else?
 
 * what else?

+
+* things that should be done on the long term (i.e. after the public annoucement) should be registered using [forge tracker](http://forge.ocamlcore.org/tracker/index.php?group_id=1&atid=102)
+
+* Well done zack ! openid auth actually works !