Calendar:Status Meetings:2008-07-02

<< previous meeting | index | next meeting >>

Meeting Details

• Wednesday, July 02nd, 18:00 CET
• Phone meeting

Telephone Info

• Toll free numbers
  • US/Canada: 866-692-3163
  • Netherlands: 0800-020-1392
  • Germany: 0800-000-3441
  • Switzerland: 0800-001-523
• Participant Passcode
  • 3182189
• Conference controls
  • Press *1 private help menu
  • Press *6 mute or un-mute individual line
• Each time you say something, please say your name first so people know who's speaking

Agenda Items

• Tracking 0.9
• Mercurial/Planning discussions, see this thread

Meeting Log

• Participants: simon, martin, berend, dmose
• We were discussing the current status of the project. Currently the major part of the implemenation work is done by the employees of Sun Microsystems and we were thinking how we could change this. Berend emphasized that nobody intends to keep information back and it was common agreement that this is not the case. Nevertheless Simon insisted that this is the impression that is partly shared by the community and proposed to also use other media for the communication. Berend promised to post regular blogs about his work to try to integrate the commnunity. On the other hand he also tried to ask for understanding that the project is currently driven by limited resources.
• Further explanation from Simon:
  • The project is currently lacking in outside communication, which gives the outside impression
    • we do not care about the community
    • we are not interested in community contributions
    • we have not much to say as not much is happening in our space
  • None of this is true and we need to counter these impressions. It was therefore decided that all of the core contributors (Andreas, Berend, Daniel, Martin, Philipp, Simon) should commit to blog about their work at least once a week and that those posts would all be posted to the calendar developer blog.
  • The topics for these blog posts would 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.
  • It is hoped that in the long run (6-12 months) this might pay off by raising the awareness of our project and attract more outside contributions.
• We discussed more active PR measures. Simon will contact a few people to get some press contacts in the hope to do some interviews to raise outside awareness of the Calendar project.