Operations Group Meeting 9 Feb 2007

Attending: Katie, Mitch, Sheila, Philippe, Jared, Ted, Aparna, Heikki

Balance

Ted observed that we're very focused on delivering Preview (a good thing), but that we might want to take a moment to make sure we're not losing our good practices of working in an open way.

• Make sure conversations happen on list, meetings and irc conversations summarized on lists, etc. (Process)
• Important to not hide plugin capability from end-user desktop download (Product)
• Ted has a concern about domain name, and losing connection between "chandler product/project" and "osafoundation" (Pr)

Branding/Pr

Follow up on conversation about sites/domains on pr list.

• Agreement that we don't want to hide the role of the foundation (some presence on landing page, wiki -- be it domain or some other thing)
• Agreement that the url that gets passed around as "landing" site is www.chandlerproject.org (or equivalent, something cleaner than osafoundation)
• Agreement that we don't really want the user docs/user area to be silo'd from the developer area
• Open question: do we want the webapp to have its own unique domain? (ops team: no -- more complicated to have more domains, better to focus the brand in one place)
• Open question: what domain do we want the wiki to live at?
  • general agreement to leave mailing lists, email addresses at osafoundation.org for practical reasons
  • general agreement to have a general audience blog at blog.chandlerproject.org
  • developer blog?

Privacy/Terms of Service

• We have probono legal advice to help with ToS^?
• Jared has the next action to come up with first draft, including "tenets" of the ToS^?, to start off the conversation
• We've followed up about concerns about migration practices

CalDAV and Preview

• Are we losing sight of CalDAV requirements for Preview? How do we frame the priorities crisply?
• Strategically important for Cosmo to be CalDAV server and Chandler to be CalDAV client.
• Proposal: frame priorities using "interop with apple" as the Preview goal, for both Cosmo and Chandler

Build support for Cosmo and Service

Ted brought up the issue of making sure Cosmo and Service requirements/tasks get noted and prioritized by build team -- do we have the right processes in place?

• Heikki to attend Cosmo meetings
• Heikki to hang out on #cosmo