New Threads:
Heikki posted a note On encrypting passwords.
http://lists.osafoundation.org/pipermail/design/2007-February/
006436.html
+ He is proposing that we provide some level of encryption support
for passwords in Preview ie: people can submit their repositories for
debugging without exposing their passwords.
+ He had some questions about how this should work in the UI.
+ Nobody replied to this thread (at least on the design list). PPD
will follow-up on what design related response is required.
Mimi started a new thread about PPC vs Intel Mac.
http://lists.osafoundation.org/pipermail/design/2007-February/
006442.html
+ She was questioning whether or not users would understand the
terminology PPC vs Intel when they go to download the app and wanted
to know if there were alternatives to the terminology.
+ John noted that we could ship universal binaries and avoid this
problem.
+ After exploring this further is seems as though the download would
be considerably bigger and it's unaccounted for build system work.
+ It's probably ok for Preview to stick with what we have.
Mimi summarized an issue that came up in another thread - Editable
Email versus Editable Attachments
http://lists.osafoundation.org/pipermail/design/2007-February/
006456.html
+ Mimi explained that for Preview we don't explicitly provide an
option for the user to send plain email messages that can't be part
of the edit/update workflows.
+ Users can certainly choose not to edit messages but for Preview we
will always attach a special Chandler attachment (EIML format) that
gets included with every message sent.
+ Through usage and dogfood feedback we will determine how users
respond to these workflows.
Based on all the list discussions Mimi has done another update of the
email spec - Updated Email Spec...Take Two
http://lists.osafoundation.org/pipermail/design/2007-February/
006459.html
+ Ironed out wrinkles around Configuring Chandler IMAP folders on the
server.
+ Clarified that all Chandler message items go out with EIML
attachments.
+ Clarified that BCC and the Appears in label are not fields that go
out in the EIML attachment ;o)
+ Not doing the funky combo-EIML attachment for forwards anymore.
Forwards are just regular message items like any other Chandler
message item.
+ Clarified behavior for what appears in the byline (sent to the list
to discuss more there).
+ Clarified that we're *not* sharing BCC right now, so BCC is *not* a
factor when calculating what message items are going into the IN
Collection.
In updating the email spec, Mimi came across another issue - Replying
to and Forwarding Recurring Events
http://lists.osafoundation.org/pipermail/design/2007-February/
006461.html
+ She clarified that when a user selects in instance of a recurring
event, we do not give them the option to reply/fwd this instance,
this and future or the entire event series.
+ We simply take the title, location, date/time and notes field data
for the selected occurrence and use that in the reply/fwd. This
behavior is the same and reply/fwd for any chandler item.
+ The Send, Update action and changes to the address fields will
always apply to the ENTIRE event series.
Sheila a proposal from the dev list for Cutting freebusy for preview.
http://lists.osafoundation.org/pipermail/design/2007-February/
006465.html
+ Sheila seconded Jeffrey's proposal that we defer fixing the free-
busy bugs for Preview and disable this feature from the menus and
dialogs.
BKirsch sent out some Comments on Email 0.7 spec.
http://lists.osafoundation.org/pipermail/design/2007-February/
006467.html
+ He had several questions related to stamping and forwarding
messages and the EIML info that gets attached.
+ Mimi responded...
+ For items stamped just as mails, we don't put anything extra in
the message body.
+ That if an original message is stamped as an event and forwarded
we package the event info as an .ics attachment. If the forward gets
stamped it should behave exactly the same like all other message
items that are forwarded. We don't need to worry about packaging up
the original forward info.
Mimi came across an issue with Dump and Reload from PPC to Intel Mac
http://lists.osafoundation.org/pipermail/design/2007-February/
006443.html
+ If users upgrade from PPC to Intel Mac, how do we make it obvious
that they need to install a new version THEN they need to upgrade
their repository as well. What happens if the old PPC data is gone.
Continued Discussions:
Davor replied to Jeffrey clarification on Any time/all day change. We
now default to creating an anytime event when you double click in the
all day area.
http://lists.osafoundation.org/pipermail/design/2007-February/
006425.html
+ Although he had seen references to all-day events, Davor didn't
know there was a difference or how to create this distinction.
Bkirsch responded to Mimi's email proposal for Forwarding Chandler
Items around. He has concerns that some of the requirements are too
complex for Preview.
http://lists.osafoundation.org/pipermail/design/2007-February/
006427.html
+ Some of Brian's concerns center around forwarded stamped items and
notes changes in the EIML attachment.
+ Mimi replied that we could simplify this for Preview and just
package up any event and task information into a .ics attachement.
+ There is some weirdness around forwarding items and how they might
up as 2 copies (depending on the sequence of events).
+ Mimi and Brian got into discussing some weird edge cases but we can
keep it simple for Preview and make some generalized assumptions.
BKirsch replied to a thread selecting smtp account for an imap account
http://lists.osafoundation.org/pipermail/design/2007-February/
006439.html
+ The first account in the list is the default outgoing account.
Users ran into a bug where they created a new one and didn't fill in
the default account we create.
+ Using the default or first filled out account is really the easiest
way to keep this consistent since we don't always know which account
the user intends on using.
+ Mimi and Brian decided to use the first filled out account as the
default.
Other Stuff:
Sheila sent out the notes from the Preview Meeting - Friday Feb 16th.
http://lists.osafoundation.org/pipermail/design/2007-February/
006438.html_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
