0001331: Ability to keep the history of calendars in a Version Control System - SOGo

ID	Project	Category	View Status	Date Submitted	Last Update

0001331	SOGo	Backend Calendar	public	2011-06-05 21:35	2011-06-15 20:21

Reporter	mossroy	Assigned To	ludovic
Priority	normal	Severity	feature	Reproducibility	always
Status	resolved	Resolution	won't fix
Product Version	nightly v2

Summary	0001331: Ability to keep the history of calendars in a Version Control System
Description	When your calendar is hosted on SOGo (or any other application), and can be modified by other applications through webdav/caldav/anything, there is a possibility that another application corrupts your calendar. In this case, it would be important to browse the history of this calendar, to see when the corruption happened, and to be able to rollback to a previous version.
Additional Information	I currently implement this kind of feature without SOGo, by simply hosting my .ics files on a Subversion server. It can be accessed through webdav : in this case every modification is considered as a new version of the file, and the history is kept. My Sunbird/Lightning clients see that as a simple webdav file. I'm thinking about hosting my calendars on SOGo, but I would lose this history and security. One solution would probably be to have a cron job that launches a wget on SOGo to export the .ics file, and commit it on a Subversion server (or any other VCS system) But maybe there is a better way?
Tags	No tags attached.

Date Modified	Username	Field	Change
2011-06-05 21:35	mossroy	New Issue
2011-06-15 20:21	ludovic	Note Added: 0002578
2011-06-15 20:21	ludovic	Status	new => resolved
2011-06-15 20:21	ludovic	Resolution	open => won't fix
2011-06-15 20:21	ludovic	Assigned To	=> ludovic

ludovic 2011-06-15 20:21 administrator ~0002578	Get the ICS version of your calendar from SOGo and handle the VCS yourself - this has little to do with SOGo.