+1 looks much better, thanks Mimi.
Cheers,
Katie
[EMAIL PROTECTED] wrote:
I've done another pass at the page with Katie and Ted's framing in mind.
It's now a short list of apps with instructions...and then notes about
bugs and issues if there are any.
I've gotten rid of the apps that didn't have instructions and expanded on
the note at the top inviting people to add their own troubleshooting
advice.
I propose we rename this page ChandlerDesktopImportExport since I imagine
we will continue to maintain / expand it after Preview.
Mimi
http://chandlerproject.org/Projects/PreviewDesktopImportExport
I'm in agreement that the page is for end users (not primarily a
planning page). I do think that a little bit of information on related
bugs is interesting/useful for users -- they could want to know if/when
we plan on fixing a bug or adding support for something.
My main complaint with the current page is that the "description" column
is all scrunched and unreadable. I'd rather have a list of products and
link to detailed instructions than try and read that as is.
Cheers,
Katie
Mimi Yin wrote:
Ah, ic. I think there is value in calling out issues in the same place,
but you're right, the emphasis should be more about instructions and
less about bugs. I will take another pass at this page with this in
mind...
On Aug 13, 2007, at 5:53 PM, Ted Leung wrote:
Last week we had some discussion about the desktop import/export wiki
page:
<http://chandlerproject.org/Projects/PreviewDesktopImportExport>. I
volunteered to drive a revision of this page.
I see that Mimi has already removed some of the stuff that I found
most objectionable: use of the wiki for bugzilla like tasks. This
is an end user page. If we want to plan to rectify deficiencies in
our Import/Export support, I think we should do that on a separate
page (or move this content to a separate page).
I think that this page should just be a list of products, and
instructions for how to import/export data between that product and
Chandler desktop. If we don't currently have solutions but feel
that a product is important, we should have an entry that says
something like: "We don't have an import/export recipe for XXX yet,
if you use XXX and have a recipe, feel free to add it here. If you
want hep debugging the Chandler end of a recipe that you are working
on, you can drop a note onto the chandler-users mailing list."
Thoughts?
Ted
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
