Mimi Yin wrote:
Does the list of re-branding bugs essentially = the list you need?
So far as I currently know and I'll flag as soon as I find anything's
that so far been missed.
One additional thing: the Account Activated page has 2 versions, 1 for
Chandler Server and 1 for Chandler Hub. For more details:
https://bugzilla.osafoundation.org/show_bug.cgi?id=8623
Thanks.
Not every Hub-related piece of copy, in particular the TOS links in
signup and PIM pages, have a Server equivalent. I'll be turning on the
feature via a properties file, then adding some Hub-related string.
But these are small and need no additional files or a dedicated ticket.
Landing page: http://chandlerproject.org/
FAQ page: http://chandlerproject.org/faq
Log a bug page: http://chandlerproject.org/logbug
Download page: http://chandlerproject.org/download
Log a bug is actually: Report a bug.
All of these pages, except for the landing page will live on the wiki.
So should it be:
+ wiki.chandlerproject.org/faq
+ wiki.chandlerproject.org/reportabug
+ wiki.chandlerproject.org/download
Minor correction, there's not really a "wiki.chandlerproject.org" right
now, just chandlerproject.org.
These URLs:
http://chandlerproject.org/faq
http://chandlerproject.org/reportabug
http://chandlerproject.org/download
are now live, should be considered "canonical links", and can be safely
encoded into Chandler Desktop and Chandler Server as needed.
Remaining are:
+ Landing page: http://chandlerproject.org/ (in place and works, but
need to get it static and have it not redirect)
+ UpgradeDialog.py migration instructions
(chandlerproject.org/migrate-desktop?)
I think we decided to handle Help issues in the product faq? I'm not
aware that anyone owns writing a help page.
The help links in Cosmo currently do not point to the product faq.
-- Jared
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
