On 8/10/07, Mimi Yin <[EMAIL PROTECTED]> wrote: > > Phew, made it through all the drafts... > > > http://chandlerproject.org/pub/Product/GetStartedGuide/4 > -SharingCollection.html > > > 1. Again, I'm wondering if we need to have intro paragraphs explaining > sharing. There's already a lot of verbiage on the landing page about sharing > and collaboration. >
I've been trying to structure this as a self-sufficient, stand-alone document, so a bit of redundancy with the ChandlerProject landing page or other wiki pages in setting the stage was part of my design for the GsG. *2. Publishing a collection* > * > * > > Select what information you want to share. Chandler organizes information > items into collections (@@@ link to Glossary). When you first run Chandler > there are some sample collections and items that are created to help you > begin to use Chandler. Below you can see in addition to the Dashboard and > email collections there are three other collections (Work, Home, and Fun), > each containing several items. An important concept in Chandler is that an > item (calendar event, to do task, email message, or note) can exist > simultaneously in any number of collections > > > > I'm wondering if we're wandering into 'explain the chandler model' > territory, which is covered in the vision document and feature list etc. For > the guide, we should just plunge straight into instructions? > My thoughts are that the two core differentiators for Chandler are Triage and Sharing and therefore these two chapters need a bit more introduction than Setting Up Accounts for example. The Windows screenshot also feels out of place and is potentially confusing > because you use Mac / Windows to differentiate between publisher and > subscriber. Here, the Windows screenshot appears before the Mac publisher > has published the share. > > > 1. Select the collection you wish to share from the sidebar. > 2. Go to the Share>>Publish... menu > I hadn't planned for the Windows user to be the subscriber and Mac to be the Publisher, it just sort of evolved into that. I can go back and make that initial Publish screenshot from the Mac *<ADD>* > We should explain that if you change the default sharing filters, > subscribers won't actually share alarms, BCC: or Needs reply status unless > they go and change the filters as well on their end? In other words, you > might be sharing, but they're not seeing your changes unless they decide to > share those attributes as well. > +1 Also clarify that Read/Unread status is not something you can share in > Preview. > +1 *<ADD>* > Explain what it means to Keep out of Dashboard? and why that's there? > > > The Dashboard collection provides a view of your data across all of your > collections. However, if you're subscribing to somebody else's calendar or > task list, the 'Keep out of Dashboard' option allows you to keep their data > out of your Dashboard. > +1 (this is great feedback BTW - just the kind of specific information that would make a great Bugzilla bug...) *<ADD>* > Show/explain the error icon in both the Sidebar and the Triage Table. > +1 Is the last section 'from Philippe's Release Notes' still in progress? > leaving that stuff there until I have time to go through it and make sure I've covered everything important in Philippe's list Pieter Mimi >
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "General" mailing list http://lists.osafoundation.org/mailman/listinfo/general
