[Savannah-cvs] [SCM] Savane-cleanup framework branch, master, updated. 8b70492b03e6d50fe296c225de33806876e962fc

[Sylvain Beucler]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Savane-cleanup framework".

The branch, master has been updated
       via  8b70492b03e6d50fe296c225de33806876e962fc (commit)
      from  dd789cf82fdc58a4cda42d66b6d38fd2121b11b7 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://git.savannah.gnu.org/cgit/savane-cleanup/framework.git/commit/?id=8b70492b03e6d50fe296c225de33806876e962fc

commit 8b70492b03e6d50fe296c225de33806876e962fc
Author: Sylvain Beucler <address@hidden>
Date:   Mon Aug 10 22:36:26 2009 +0200

    Write exhaustive roadmap for Savannah installation + doc fixes

diff --git a/TODO b/TODO
index 50f71d8..fa195e0 100644
--- a/TODO
+++ b/TODO
@@ -1,16 +1,129 @@
-- models
+Roadmap
+=======
 
-  - add DB indexes (db_model=True)
+The roadmap is based on the previous Savane incarnation.
 
-- now we need the screens for users to modify them
+However we can't guarantee we'll rewrite 100% of its features.  In
+addition, the goal is to get something we can install like at Savannah
+quickly, which means we may delay some features in a first step.
 
-- work on the web design
 
-- export to LDAP and reimplement .ssh replication and VCS creation
+[/] Implement web screens (higher priority)
 
-- implement mod_rewrite URL migration list
+    [/] User page
 
+    [/] Group page
 
-* Work on the web design
- - Maybe we can change the colors.
- - We needs to define a CSS class for buttons
+    [ ] Members list + GPG keyring
+
+    [/] Account conf ([X] e-mail, [X] password, [X] real name, [/] SSH
+        keys, [X] GPG key)
+
+    [/] My Groups
+
+    [ ] Group membership (manage members, manage permissions, request
+        inclusion)
+
+    [ ] Delete account (clean-up data but keep User+user_id if past
+        history)
+
+[ ] Implement web screens (lower priority)
+
+    [ ] Account conf 2 ([ ] profile, [ ] skills, [ ] timezone)
+
+    [ ] Bookmarks? Was considered for deletion at a point in Savane:
+        http://gna.org/task/?1412 - note that yeupou is a bit partial
+        towards trackers in that discussion
+
+[ ] News management (+ comments)
+
+[/] Work on the web design
+
+    [X] Do something different
+
+    [ ] Maybe we can change the colors.
+
+    [ ] We needs to define a CSS class for buttons
+
+[/] Rewrite backend (or have them work on a replicate that uses the
+    old DB schema)
+
+    [/] Link the system to the DB more directly (no cron'd
+        replication) - currently we use libnss-mysql-bg, it's in test
+        live at Savannah using the old DB schema.
+
+        TODO: adapt to new DB schema, and either fix libnss-mysql-bg
+        bugs or switch to libnss-pgsql - cf. doc/NSS-SQL
+
+    [/] homedirs and .ssh replication (done in savane-cleanup, and in
+        Python - just adapt the DB schema)
+
+    [ ] GPG keyrings
+
+    [ ] Group resources (Download, CVS, SVN, Arch, Git, Mercurial,
+        Bazaar)
+
+    [ ] CVS notifications (commit_prep+log_accum - Savannah-specific)
+
+    [ ] Mailing lists (Mailman)
+
+[/] Write migration scripts
+
+    [X] Users, groups, group types, memberships
+
+    [X] SSH keys (with new, separate table):
+        src/savane/backend/migrate_sshkeys.py
+
+    [ ] User preferences (table user_preferences)
+
+[ ] Implement mod_rewrite URL migration list
+
+[/] Separate the trackers in the old code so they can work
+    independently.  Some work was done in the 'split' branch.  TODO:
+    test more and add a new->old replication for users/groups so the
+    trackers can use it, until we rewrite them.  Possible do the same
+    for jobs and news.
+
+[ ] Add some tests
+
+=====
+
+Goal #1: use it live at Savannah :)
+
+=====
+
+Uncharted territories - and wild ideas.
+
+[ ] Optimize models - add DB indexes: db_index=True or unique=True
+    (with MySQL) or primary_key=True
+
+[/] Export users/groups to LDAP
+
+    [X] Populate a LDAP directory from the DB
+
+    [ ] Sync the LDAP directory when there are changes (e.g. password,
+        mail...)
+
+    [ ] Implement a Django backend that supports SSHA or CRYPT (CRYPT
+        may be better since all PAM modules would support it)
+
+[ ] Migration to PostgreSQL?
+
+[ ] Rewrite trackers in Django?
+
+[ ] Rewrite /people (request for contribution / jobs) in Django?
+
+[ ] Add more non-members<->groups and users<->users interactions (aka
+    "social features")
+
+[ ] List/retrieve more stats (namely commit stats)
+
+[ ] Create a timeline for projects with the latest project events
+    (commits, memberships, news, bugs...).  Possible for users too.
+
+[ ] Wikis
+
+[ ] Improve/suppress delays (e.g. ping a daemon that creates project
+    repositories and mailing lists, with a job queue system)
+
+[ ] Your Ideas Here
diff --git a/doc/NSS-MYSQL b/doc/NSS-SQL
similarity index 100%
rename from doc/NSS-MYSQL
rename to doc/NSS-SQL
diff --git a/src/savane/backend/migrate_sshkeys.py 
b/src/savane/backend/migrate_sshkeys.py
index 573825b..04f46f4 100644
--- a/src/savane/backend/migrate_sshkeys.py
+++ b/src/savane/backend/migrate_sshkeys.py
@@ -1,4 +1,4 @@
-# Replicate users and groups to an OpenLDAP directory
+# Migrate users' SSH keys from old Savane to new Savane
 # Copyright (C) 2009  Jonathan Gonzalez
 #
 # This file is part of Savane.

-----------------------------------------------------------------------

Summary of changes:
 TODO                                  |  131 ++++++++++++++++++++++++++++++--
 doc/{NSS-MYSQL => NSS-SQL}            |    0
 src/savane/backend/migrate_sshkeys.py |    2 +-
 3 files changed, 123 insertions(+), 10 deletions(-)
 rename doc/{NSS-MYSQL => NSS-SQL} (100%)


hooks/post-receive
-- 
Savane-cleanup framework