Mozilla Calendar Project Lead Mike Potter Retires, Mostafa Hosseini Named as New Head
Friday July 4th, 2003
Yesterday, Mike Potter retired as the lead of the Mozilla Calendar project. Mostafa Hosseini has now taken over Mike's duties, which include reviewing patches, checking in code, creating new builds and updating the project website. Like Mike, Mostafa works for OEone (the company that launched the Calendar project) and has already written substantial portions of the component's code.
The current plan is to work towards making Calendar into a standalone application, along the lines of Mozilla Firebird and Mozilla Thunderbird. Though the team did discuss moving Calendar to mozdev, they have decided to remain a part of the Mozilla project for now. Encouragingly, there has been interest in Calendar from companies such as Sun Microsystems and Lindows.com.
#3 Re: Why the obsession about standalone apps?
Saturday July 5th, 2003 6:45 AM
You are replying to this message
That sounds like an excellent idea, but somewhat tangential to the issue of seperate applications.
If I understand what you are suggesting correctly, the system you are looking for would be able to construct arbitary assosiations between different resources. For example, you might set up relationships saying these webpages are related to this email which is part of this project, or that this document needs to be edited in the next five days, before this scheduled meeting using information in these three other documents, this folder of email and the sections that I annotated on this web page. Correct? If so, the Mozilla framework is probably an excellent place to implement such an application, since (as far as I can tell), it would be an ideal use of RDF which is well supported inside Mozilla. The application could create it's own RDF file contatining relationships between pieces of data and whatever metadata is required, whilst the data itself would be held in the files belonging to whatever external application created them.
As far as I can tell, quite a lot of the framework for this already exists within Mozilla. Some of the links from <http://www.mozilla.org/rdf/doc/> describe quite similar ideas.
The neat thing about having this in a setting where everything is componentised is the extra flexibility that is avaliable. For example, it is probably true that a web browser can be totally seperate from such a proposed information managment application. On the other hand, it might be beneficial to integrate some email functionality directly into the application - the ability to retreive new mail and apply the adaptive or keyword filters that are avaliable in thunderbird. Composing a message on the other hand will always need a new window and so it doesn't matter if that is part of a seperate application. It's a similar situation with calendar (or any other scheduling app that integrates with the application) - if the calendar window itself is a seperate application, it doesn't matter, so long as the data from calendar is avaliable for use. It also means that people who don't need this functionality (like most home users, public internet access points, etc.)aren't burdened with an interface desigened around it.
As an aside, if anyone knows of a really good resource for learning about RDF, I'd really like to know about it.