In my post about google products, I had shown my wish to have a desktop application for calendar which should sync it’s data with an online server so that I will not have to open browser to see calendar, and I will be able to see calendar even if I do not have my laptop with me.

Now, in software engineering course, we are asked to make a software using different software engineering techniques. And I could persuade my project partners to work on this dream calendar. Mainly the calendar will have following properties :

1. API for making desktop application and web application. First release will have API for perl only. (will serve both desktop and web application )
2. All normal calendar things
3. The software will be under GPL.
4. Others will be able to change your calendar, if you have given them permission.
5. others will be able to send you a request to add an entry in your schedule, like your friend may want you to attend a meeting, (s)he can put an entry for that in your calendar, but you have to accept that request so it finally appear in your schedule.
6. We are trying to understand how iCal works, once we understand that, we will try to include iCal as well, so that you could use current softwares which supports iCal. (iCal is RFC standard for calendars, that means I can freely use it. right?)
7. As of now, if iCal doesn’t make sense, we will have our own thing, for now we are calling it oCal.
8. I will run this server on my web server, so if you others wouldn’t have a server to sync their data, they should be able to do that.
9. We are thinking of including some plugin system as well, so users could modify the calendar functionalities, though we are looking at how different plugin systems works
10. Current status of the project can be seen at http://rohitj.net/dokuwiki/doku.php?id=software_engineering_project

If you think you want a particular feature in the calendar, let me know. We want to know what users want.