[Cosmo-dev] [Sum] Nov 12-18

[Ted Leung]

Here's the summary of the activity on cosmo-dev for the week of   
November 12, 2006.

New threads:
-------

Mike Taylor (bear) posted an update on the Maven 2 upgrade
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001958.html>

Matthew Eernisse reposted a pointer to the Cosmo Javascript style guide
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001981.html>

Randy Letness proposed a set of changes to Cosmo's object model to  
support the new sharing format and stamping
+ Brian Moseley wanted to know more about namespaces, icalendar data  
not represented in a stamp, and stamps vs an items content
+ Randy Letness replied with some options on handling icalendar data,  
and saying that content items created via DAV would not be stamped
+ Brian Moseley responded by proposing to turn icalendar data into an  
ical4j object along with an order column.  He also said that DAV  
originated content items probably ought to have the EventStamp (not  
be unstamped)
+ Randy Letness pointed out some problems with the ical4j+order  
column approach and then proposed a partial solution.   He agreed  
with applying EventStamp to DAV originated events, but had concerns  
over things like .jpg files that might arrive via DAV
+ Brian Moseley agreed that we should stick to the blob/index  
approach that we are using for icalendar instead of the newer  
solution.   He also pointed out that things like .jpg files are not a  
problem and that Cosmo handles them just fine now.
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001968.html>

Morgen Sagen wanted to know about fixed point number support in EIM.
+ Randy Letness didn't see a problem with fixed point support, but  
wanted to know the use case
+ Morgen Sagen replied that the use case was a "timestamp"  
representing the last time triage status was changed in the dashboard
+ Bryan Stearns chimed in with additional clarification for the use  
case.
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001973.html>

Adam Christian wanted to know what to do about bug 7361 <https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=7361>:
+ consensus was to hold the fix for this until 0.6 - it is already in  
the 0.6 trunk
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001976.html>

Ted Leung reported that all task bugs for Cosmo 0.6 had been created  
and linked.  He had some questions about bugzilla structure
+ Brian Moseley responded with suggestions for new components and  
component ownership changes.
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001980.html>

Brian Moseley asked for some improvements to the CosmoZeroDotSix page  
<http://wiki.osafoundation.org/bin/view/Projects/CosmoZeroDotSix>:
+ Ted Leung asked for additional suggestions, and made the requested  
changes
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001987.html>

Bobby Rullo finished work on the Maven 2 JSAR plugin:
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001989.html>

Some of the design list discussion on login workflow ventured into  
code territory:
+ Matthew Eernisse clarified the state of Javascript timezone support  
in Cosmo and described his xDate library
   + Bobby Rullo wanted to make sure we weren't yanking CosmoDate
   + Matthew Eernisse replied that there was little overlap between  
CosmoDate and xDate and that gettting particular function was more  
important than the name of the class
   + Bobby Rullo pointed out that the whatever-Date objects still  
need a lightweight 0-arg constructor due to Cosmos way of creating  
objects from JSON
   + Bobby Rullo proposed a plan for how to incorporate the new  
timezone stuff and needed functionality from xDate into the existing  
date class
   + Matthew Eeenisse likes the plan
+ Jeremy Epstein wanted to clarify issues around setting a reasonable  
timezone default
   +  Matthew Eernisse pointed out that UTC offset didn't necessariy  
map to a unique timezone and proposed prompting the user
   +  A bunch of people voted in favor of prompting the user
+ Jeffrey Harris pointed out that knowing the timezone is very  
important and that UTC and offset are not enough.   The timezone is  
especially crucial for recurring events
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001996.html>

Travis Vachon discussed his plans to add an HTTP Logging filter to  
the trunk.  He got no replies
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002013.html>

Brian Moseley proposed that the model layer changes for 0.6 be done  
in a branch:
+ After discussion Randy Letness agreed that it would be good to branch.
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002024.html>

Travis Vachon reported that he finished the HTTP logging feature and  
the HTTP/HTTPS reverse proxy feature.  He plans to do account  
activation next and had questions about hibernate level changes that  
might be needed.
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002034.html>

Ted Leung started at thread to discuss minimizing the impact of  
dependencies.
+ After discussion there was agreement on a plan for a few features  
landing followed by a branch.
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002036.html>

Jared Rhine opened a bugzilla ticket <http:// 
bugzilla.osafoundation.org/show_bug.cgi?id=7433> for compressing  
Javascript to reduce bandwidth usage
+ Matthew Eernisse posted some references on how to solve this problem
+ Ted Leung replied with pointers to UI research on reasonable  
response times, and reminded people of the need to keep an eye on  
performance
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002045.html>

Ted Leung reposted the Cosmo 0.6 planning page URL <http:// 
wiki.osafoundation.org/bin/view/Projects/CosmoZeroDotSix>:
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002048.html>
Bobby Rullo went ahead and added JSUnit testing to the build, but had  
a list of TODO's left:
+ Matthew Eernisse suggested not porting the date tests as they went  
into Dojo 0.4
+ Ted Leung volunteered to pick up the rest of the tasks
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002054.html>

Jared Rhine pointed out Linux Weekly News is picking up the Cosmo  
announcements:
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002056.html>

A new version of the MySQL JDBC driver has been released
+ We will probably upgrade to it.
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002076.html>

Jared Rhine posted some feature request for console users which  
spawned some good discussion.  On notable item was a search box for  
users as opposed to paging.
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002075.html>

Travis Vachon asked for a sanity check on the data persistence part  
of account activation.
+ There was some discussion on how various aspects of the feature  
ought to work.	Of note were leaked activations (accounts requested  
but not activated), unactivated vs locked accounts
+ Randy Letness proposed storing an activation hash in the user  
record - lots of people liked this idea
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002058.html>

Matthew Eernisse was having trouble unifying the account signup boxes  
between Cosmo and Snarf
+ Brian Moseley suggested removing account signup from Snarf altogether.
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002061.html>

Ted Leung posed about DebugBar a JavaScript tool ala FireBug but for IE
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002085.html>

Ted Leung wanted to know what a reasonable Data Migration feature for  
Cosmo 0.6 looked like:
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
002086.html>

Continuing Conversations:
-------

The discussion on Free/Busy display continued:
+ Priscilla Chung was concerned that the work to do this would  
detract from Preview features
+ Brian Moseley pointed out that the UI needed to handle free/busy  
tickets gracefully
+ Priscilla Chung proposed a simple dialog
+ Several people wondered why we would cut a feature that looks to be  
doable in the alotted time
+ Ted Leung pointed out that free/busy was outside the CC workflow,  
that folks working on free/busy are not on the critical path for 0.6  
and that time spent on free/busy could be spent fixing non-feature  
0.6 bugs.   He proposed implementing Priscilla's dialog, looking at  
the interop needs with respect to free/busy and holding the time  
allocated for free/busy free, to either work on free busy or bugs,  
once the situtation was clearer.
+ People agreed with Ted Leung's proposal.

The discussion on the Morse Code spec continues:
+ Randy Letness asked about deletion, distributed locking(!), and  
interleaved syncs/updates from multiple clients
+ Brian Moseley will update the docs when there is a plan for  
deletion, and wanted to leave the locking discussion for a separate  
thread
+ Ted Leung liked the spec and asked if it could be linked from the  
Projects.CosmoZeroDotSix page on the wiki
+ Vinu Gopal asked about merging in the case of conflicts
+ Brian Moseley pointed out the conflicts don't happen because of  
locking
+ Morgen Sagen wanted to know how a client can figure out which  
permissions it has for a given ticket
+ Brian Moseley pointed out that the client can propfind for  
ticket:ticketdiscovery
+ Morgen Sagen wanted clarification about which records and which  
parts of record the client and server were required to send - He  
didn't get an answer
+ Morgen Sagen also wanted to know what happens if another client  
does a post in between a client's GET/POST sync operation - he  
proposed that each client provide a sync token in it's POST request,  
and that the server reject mismatched sync tokens.
+ Randy Letness said that he and Brian Moseley discussed the same  
idea as Morgen Sagen, and that was the plan
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001960.html>

Brian Moseley supplied some more information on the space usage  
reports feature
<http://lists.osafoundation.org/pipermail/cosmo-dev/2006-November/ 
001963.html>