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.
#2 Why the obsession about standalone apps?
Saturday July 5th, 2003 1:12 AM
You are replying to this message
This is really beyond me. I think splitting up the different parts of Mozilla technically is a good idea, but it is NOT a good idea from a design and usability POV. We already have loads of standalone apps that each one does their thing - one for browsing the web, one for doing email, one for PIM, one for ... but what most users who do serious work on a computer face every day is: you have to do everything several times - you have to think about how to organize bookmarks, email folders, document folders according to your tasks in different programs etc. And you cannot do what you want: you cannot mark a message as "todo until ...", you cannot associate a bunch of URLs to an email, and so on. I have said it before and I repeat it: providing standalone apps like FB, TB, Cal just adds another program to a long list of existing similar programs, but is not innovative from a usability POV. To give users what they need for their work, analyze how the different kinds of information - email, web, todos, etc. - are used and integrate this into an app that finally lets users do what they want, and not, what was easy to program. Users don't care how you implement that technically - if splitting up into modules is reasonable, fine. But users DO care about how easy it is to manage to overwhelming amount of information they are confronted with. Users doing real work dont care about theming that much, but they would love to have more flexible ways to organize their 5000 emails, for example ...