Links

• New DASL proposal? http://www.goland.org/Tech/dasl.html

Dev management plan du jour

Basic model: For high-level planning, we identify "projects", "features", or high level tasks to accomplish. Projects are assigned to an integration point. There are three integration points for 0.4 -- A, B and final. This is an initial proposal for integration points, to be adjusted if we see the need.

Low-level planning is more detailed and more decentralized. Each developer or the WG will break down a "project" into more detailed tasks, with a granularity down to the level of days possibly. There needs to be some centralized way of reporting completion of these granular tasks, but there doesn't need to be one centralized information page that contains every task for every project indefinitely out into the future.

• Plan integration point dates and put 0.4 high-level "projects" into these integration point buckets
  • Start by bucketing stuff for A, B and final for each WG separately
  • Schedule meeting with Mitch, Katie, Lisa, Chao and Andi to review plans & see dependencies
• Rip apart (obsolete) ZeroPointFourPlanning
  • Katie and Lisa do this in an ad-hoc manner, preserving tasks information but decentralizing
• Start public checkpoint milestone reporting - what tasks achieved by whom in this checkpoint
  • This is experimentation, we don't know if it's going to end up as email, wiki or other
  • Start with 0.3.16 milestone
  • Come up with plan for items due for 0.3.16 milestone, per project/person
  • Post plan for each WG, e.g. on WG page
  • Start with Services and Apps, with some coordination for similar format
  • Prepare to publish (email or wiki) 0.3.16 task completion report, with each WG section compiled by each WG coordinator
  • Consider putting task/checkpoint information in weekly WG meeting minutes on wiki

Calendar standard support reality

This page has a lot of products listed supporting calendaring standards. However, the descriptions of the standards are confused.

vCalendar/iCalendar as import/export format

It seems that vCalendar is pretty widely supported for importing and exporting calendar data into calendar application software, and for uploading to certain WebUI^?-based calendar servers. IMC said "vCard and vCalendar have been imbedded into so many products and services that the value of this list [of supporting vendors] has greatly diminished." Here's an explanation of how iCalendar relates to vCalendar. I use the term vCal more for the standard (even though the standard took vCal and made it iCalendar) now that iCal is the name for Apple's product.

• Apple's Mac OS X iCal can export, import and publish
• Outlook can email vCal files as attachments and import vCal files
• Open source projects like gnomecal generally seem to be vCal aware
• EventSherpa^? publishes compatibly with Apple iCal
• Kronolith
• MeetingMaker^?
• Evolution

iMIP/iTIP support for sending invitations

iMIP is a profile of iTIP. The iTIP "family" of standards (so far only including iMIP) are intended to formalize exchange of vCalendar/iCalendar data, such as invitations. See this blog post for a briefer survey. However it may just be that "iCalendar support" is used as a catch-all including iMIP/iTIP support.

• KOrganizer -- iTIP
• Kronolith -- iTIP
• ScheduleWorld^? -- will create and send iMIP messages to Outlook
• Outlook -- sends and receives iMIP messages
• iPlanet Calendar Server -- "limited" iMIP support
• Netscape Communicator can receive iMIP messages

-- LisaDusseault - 04 May 2004