[General] Re: Code dependent Preview deliverables update

[Ted Leung]

Just today Mimi put up

http://chandlerproject.org/Journal/CosmoImages

As far as I can see, there are two versions of the necessary artwork,  
one for server and one for hub.   Modifying the properties files  
accordingly should be a a small job.

What else needs to happen here?

Ted

On Jul 3, 2007, at 10:37 AM, Sheila Mooney wrote:

> Jared,
>
> Thanks for the lengthy response. If I understand correctly, it  
> looks as though the property file DOES NOT include what the  
> developers need in order to rebrand the application with the logo.  
> So all the tasks assigned to Travis for replacing the blue Cosmo  
> logo really should show the logo with Chandler Server not the Hub  
> version. Perhaps, Mimi already has all these files somewhere so I  
> am going to let her reply with any questions. It's probably easiest  
> if we simply attach what we need to every bug, even though it's  
> repetitive. I know Mimi has spoken to Matthew but we are going to  
> have Travis do this work so I want to make sure he has what he needs.
>
> Jared, I will assume for now that you will log all the associated  
> bugs/tasks for the Hub rebranding.
>
> All the URLs you suggested seem fine to me. I also found another  
> one that we need...
>
> + Link to the Getting Started Guide (I need to confirm with Pieter  
> that the signup instructions will go here)
>
> Sheila
>
> On Jul 3, 2007, at 10:18 AM, Jared Rhine wrote:
>
>> Sheila Mooney wrote:
>>> I reviewed all these items (for both desktop and server) with Mimi.
>>
>> Thanks!  Very helpful.
>>
>>> I think I need some help figuring out what next actions I should  
>>> be doing or even what additional tasks need to be logged.
>>
>> In general, what's going to happen is this:
>>
>> * Nothing that says "Chandler Hub" will get checked in to Cosmo's  
>> SVN. Things that are "Chandler Hub" rebranding are separate  
>> tickets, and in general not executed by Cosmo devs.
>>
>> * As service manager, I follow along with the rebranding changes  
>> being done for Chandler Server, and duplicate in some way,  
>> essentially each of those tasks
>>
>> * If there's a graphical asset produced for Chandler Server, a  
>> duplicate asset will be needed for Chandler Hub (though not  
>> handled by Cosmo devs).
>>
>> I have some of the Hub rebranding tasks tracked in bugzilla's  
>> "Sharing Service" product, but now I can take your easy list of  
>> Cosmo rebranding tasks and flesh out the Hub ones.
>>
>>> *Logo: There are 2 issues here....*
>>> + I think that I don't know what more you need from Mimi and I as  
>>> far as the logo is concerned. I spoke to Mimi and she said she  
>>> has provided the logo and all the text for Cosmo in a properties  
>>> file attached to https://bugzilla.osafoundation.org/show_bug.cgi? 
>>> id=9567.
>>
>> From what I saw of the attached property file in that bug, much  
>> (all) of the copy said "Chandler Hub".  What Cosmo devs need are  
>> files that say "Chandler Server"; the Hub files are useful to me,  
>> though the implementation for customizing the Hub might be a  
>> little different.
>>
>> For the logo specifically, (almost) anywhere there's a Chandler  
>> Server graphic created, we'll need a Chandler Hub logo.  For the  
>> "image grid", I'll need a whole new grid that I put into place for  
>> the Hub specifically.  If there's any stand-alone PNG logos added  
>> to Cosmo SVN, I'll need similiar files for the Hub (to go into the  
>> Hub SVN).
>>
>>> I am assuming this file is what you need to address all the logo  
>>> bugs.
>>
>> The properties file above I think are all copy-related marks  
>> (text). For graphical marks (ie, the logo), I think those are in  
>> different tickets.
>>
>> > As you
>>> talked about last Thursday, you wanted to front load the logo  
>>> work and I am not sure what else you need from us.
>>
>> For Hub, I need to see what changes are made for Chandler Server,  
>> and then duplicate that work for the Hub.  One of the reasons to  
>> do the logo work early is they are slightly trickier to duplicate  
>> for the Hub, so the sooner that the fixes are in Cosmo, the sooner  
>> I can start on the Hub patches.
>>
>>> We think we are done so if you need something else in a different  
>>> format, then you need to let us know in more detail.
>>
>> It's true that I won't know 100% until all the Chandler Server  
>> changes are applied to Cosmo SVN, but that will provide at least  
>> 90% of what I need right there.
>>
>> If the image grid changes again, both Chandler Hub and Chandler  
>> Server versions will need to be created.
>>
>>> + The second issue is - there is the whole class of bugs to  
>>> replace the existing Cosmo logo with the new one.
>>
>> It seemed like issue #1 above was mostly about the logo, so much  
>> of what I wrote above maybe belongs here instead :)
>>
>>> Aside from the proper logos in the properties file...
>>
>> I don't think logos go in the properties file.  Take a look; it's  
>> all text.  The graphical assets will generally involve updates to  
>> binary files.
>>
>> I'm probably not going to care about the admin UI rebranding for  
>> the Hub.  It's not user-visible (for the Hub), so of questionable  
>> worth to bother with sprucing that up.
>>
>>> These bugs are all currently assigned to Travis and I just wanted  
>>> to check that there wasn't some task you needed to do.
>>
>> As above, actually there's definitely a number of tasks I need to  
>> do to implement the Chandler Hub rebranding.  But it's almost all  
>> just following along behind the devs, reimplementing each change  
>> they make for Chandler Server, is the same way for Chandler Hub.
>>
>> Ideal is when I can change "Chandler Server" to "Chandler Hub" by  
>> changing some text in a config file (ala the *.properities) files.  
>> Images are more of a hassle, but not a large one.
>>
>>> *Specifying URLs for links*
>>> So, there is this big class of bugs on both the desktop and  
>>> server side where I just need to provide the developers with the  
>>> right link to use in the About Box or the Help menu. In order to  
>>> specify the links, I need to find out what all the final URLs are.
>>
>> We talked a bit about this on Friday.  I suggested that we should  
>> probably use "redirects" for all these hard-coded links.  We can  
>> then code in the "redirect URL" into the client, and then have  
>> flexibility to figure out or change the "final URL" later (before  
>> or even after Preview).
>>
>> So, with this list, let me review them, and try to propose a short  
>> redirect URL for each.  Then I'll need a task to implement all the  
>> redirect URLs.  We can code the redir URLs into clients at any  
>> time, once we agree on the redir URL to use.
>>
>>> The actual links we need are (I think this is it)
>>> + Landing page
>>> + FAQ page
>>> + How to log a bug page
>>> + Download page
>>
>> I'm thinking something like:
>>
>> 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
>>
>> There's also "signup", for which I think we have:
>>
>> http://hub.chandlerproject.org/signup
>>
>> (And for which no changes are needed)
>>
>> The above suggestion for redir URLs is just a strawman, let me  
>> review the lists of bugs you attached and see if any changes pop  
>> out at me.
>>
>> The "help" link in Cosmo's UI recently got updated from dot6 to  
>> dot7 though the destination page doesn't exist yet.  (It also uses  
>> a wiki.osafoundation.org URL, which I told Bobby not to fix until  
>> we figure out a final URL).  I think we should probably use redir  
>> pages in Cosmo's UI.
>>
>> -- Jared
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> 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