This wiki has undergone a migration to Confluence found Here
GForge Site Administration
Jump to navigation
Jump to search
Rules, practices and principles for site administrators (not project administrators but the whole GForge site administration)
We have two tiers of site administrators; HL7 staff who understand their roles, and the supplemental administrators as reps from Publishing and Tooling to ensure there is coverage during publishing cycles when they’re working at the last minute on a weekend and staff is not available
- Who should be the site administrators for GForge? In addition to HL7 staff support (Josh, Lynn, Don and Mike), the logical candidates are at least one representative from each of the Tooling and Publishing Work Group cochairs
- Woody Beeler
- Lloyd McKenzie
- Non-staff site administrators should limit activities to user rights on individual projects rather than setting up new projects.
- Is there a way to monitor what has been done by the site administrators or should we email one another to notify of changes?
- There is an audit log available to admins, but major site administrative changes can be emailed to the other admins as a courtesy
