HepForge tracker

This is the issue tracker for HepForge development.

• HepForgeToDo?

Rewriting the admin system

After the Jan 2007 upgrade, the admin scripts are very out of date. We could try to re-point the paths etc., but it would be error prone and anyway the shell-based admin has, IMO, run its course. The new plan is to provide common HF admin functions as Python library routines, bundle up all "forge" Python as a Python system package and use the resulting library for all forge functionality (shared between admin scripts, CGI etc.). The admin frontend will be rewritten as a forge-admin script, cf. trac-admin.

• ForgePython
• ForgeAdmin

To write the new system, we need to make careful notes on how users and projects are now administered with the new layout. We should try to be as independent as possible from hard-coding paths, esp. /hepforge.

• ManualMkUser
• ManualMkProject
• ManualAddUsersToProject
• ManualMkMailingList

Server setup

There are some specific issues with the server setup which need to be borne in mind when re-installing:

• Default umask should be set to 002, since group-writeability is important

Old HepForge admin guide (out of date)

These descriptions are out of date - particularly regarding the admin shell scripts, which are now defunct (but have yet to be replaced).

• HepForgeAdmin

In more detail…

• HepForgeScripts (very out of date)
• HepForgeWebConfig (quite out of date)
• HepForgeMailConfig (now have mailing lists)
• HepForgeSvn?
• HepForgeDependencies