Yesterday we had a pretty interesting developer conference call, which was basically about the issue that only a very small team is currently developing on Lightning and Sunbird (basically just three people), that it is hard to reach community expectations with regards to bugfixes and feature work with so small a team and what would be necessary to attract more outside developers.

From my point of view one of our shortcomings in the past has been on the communication front. With that I don't mean the communication between different people on certain bug characteristics or code issues (that works great), but the communication between the calendar project and our community.

Currently our channels of communication are:

• This blog, which just gets a post every one to two weeks with a bug fix status update
• our developer and support newsgroups (mozilla.dev.apps.calendar and mozilla.support.calendar), which are not exactly buzzing with activity
• IRC, which not many people are watching

The result - at least as far as I see it - is that

• the core people from the project come across as a closed circle to which it is hard to get in to (the opposite is true)
• what's going on in the project is not exactly transparent. Instead I would call it opaque.

So what can we do to improve our situation, to make the project more transparent, to raise the interest in the project and by that to gain more outside contributors? A few things come to my mind:

• We need to talk more about what we are doing. Therefore every core contributor will try to commit himself to at least blog about various stuff at least once a week from now. These posts will probably range from developer-oriented topics (interesting or disgusting pieces of code, recent bugfixes, UI considerations, QA problems/successes/challenges) and project-related topics (PR issues, community relations, ...) to basically anything that the people find worthwhile to blog about.
  In my opinion a great example to follow here is the Firefox community. Where nearly everybody involved in the project (developers, build engineers, QA staff, PR and marketing people, management) tries to blog regularly about various Firefox stuff or other stuff that interests them. The outside image that this creates is the image of a beehive, where everybody is doing lots of stuff to improve Firefox and in my opinion stuff like this also attracts outside people, because everybody would like to contribute to a project that is alive and well instead of a project that is stalling or dead.
• We need to raise the awareness of the project in the outside world. I'll try to contact a few people to get some press contacts, in the hope to do some interviews with some people interested in open source. We hope that this will raise the awareness of Lightning and Sunbird and bring in outside contributors.

I want to make those of you, who are actively translating the calendar products (Lightning and Sunbird) aware, that our string freeze for our next release 0.9 is approaching. According to our release schedule we are aiming for a string freeze on July 14 2008, which is two and a half
weeks away from now.

After the string freeze we are currently planning for two additional weeks before we try to release our first release candidate on July 28. We would really appreciate it if you could have your locales already in shape for the first RC as this will broaden both the localization and application testing base.

That gives you about a month to get your localizations in shape if you start now or two weeks, if you decide to wait for the string freeze. From my point of view, it certainly makes sense to start working now, at least in a few areas. If you take a look at all the string changes since our 0.8 release and now, you'll notice that we've done a lot of cleanup work by removing unused and obsolete entities. This is definitely something that you can start working on now, while doing the remaining update work after the string freeze.

The 0.9 release will again come from the MOZILLA_1_8_BRANCH, but since we're keeping both the 1.8 branch and the cvs trunk in total sync, it makes sense for you to commit your changes to both at the same time.

I'll post some status updates in the coming weeks. If any of you will not be able to keep his locale updated for the 0.9 release, please let me know beforehand. As of now we are planning with all localizations that were included in the 0.8 release as well as with the new locales added since then (Norwegian (Nynorsk), Romanian and Traditional Chinese).

Please let me know if any of you wants to join us for 0.9.

If you have any questions, please do not hesitate to ask them in the corresponding discussion thread on the newsgroup mozilla.dev.l10n.