-
Notifications
You must be signed in to change notification settings - Fork 32
Utility & Configuration Management
merichar edited this page Sep 13, 2010
·
6 revisions
- Consistent design for all external event organizer views
- Consistent design for all internal management stuff
- From [email protected]
- To Organizer
- Contains submitted event information
- Contains unique base64 url to share with other people (obfuscated, not acled)
- Includes “Please reply to this e-mail for information regarding this event”
The future of [email protected]
- Reserved for non-event use
- We should work out profiles/email so that you can check it like another inbox (e.g. [email protected])
- Seen as “From: <”tech member name-via-tracker" [email protected]> or <“tech member name-via-tracker” [email protected]> which goes to events@.
- Parse based on subject with event id or maybe plus addressing? [email protected] => GS 2010
- All e-mail except for notification of submitted event receipt should be triggered by some techie
- Some more general e-mail interface should be available for sending mail
- Anyone who gets an email outside of the tracker infrastructure is responsible for forwarding it back to events (or suffer pain of death)
- Solicit interest/confirm attendance
- List available positions
- Consistent view for all actions requiring an html calendar
- Agenda, Day, Week, and Month views
- We like the current color scheme
- Ability to export an arbitrary calendar (probably can’t do auth’ed export, maybe base64 obfuscated links/export)
Generate reports in html and pdf containing
- Most commonly used equipment and rooms
- Financial statistics
- How many man-hours put towards something
Sufficient flexibility to add future reported elements without affecting previous reports