[General] Re: URLs for Preview Release

[Mimi Yin]

Hi Jared, See in-line. Ted, there are some questions for you as well.  
There are a number of Cosmo-specific issues to be ironed out.

On Jul 6, 2007, at 4:39 PM, Jared Rhine wrote:

> Mimi Yin wrote:
>> + Landing page: chandlerproject.org
>
> Yes.  Full version is "http://chandlerproject.org/", same thing.
>
>> + Download Desktop: http://chandlerproject.org/ 
>> downloadchandlerdesktop or /downloaddesktop or just /download?
>
> http://chandlerproject.org/download is already in place.  In  
> general, for these redirection links, more detail is better than  
> less.  We could do '/download-desktop' if we want to be more  
> precise and it can point to the same downloads.osafoundation.org  
> location it does now.

Oh man, we have too many options. I sent a proposal to the list to  
have it point to an end-user focused downloads page: http:// 
lists.osafoundation.org/pipermail/general/2007-July/000644.html

>
>> + Sign up for a Chandler Hub account: hub.chandlerproject.org
>
> Current best is http://hub.chandlerproject.org/signup

Ok

>
> That's what's in Chandler Desktop right now.
>
>> + Getting Started Guide: chandlerproject.org/gettingstarted*??*
>
> TBD.  "/guide" I proposed in another email.

That shorter, so better :)

>
>> + Vision: chandlerproject.org/vision*??*
>> + Features: chandlerproject.org/features*??*
>
> If you want these shortcuts for these, sure; those two sound  
> perfect. Are they needed?  (See below)
>
>> + FAQ: chandlerproject.org/faq
>> - Help
>> - Desktop migration instructions
>> - How to publish to Chandler Server
>
> I think we might want a migration-specific link, even if it points  
> the FAQ for now.
>
>> + Blog: wp.osafoundation.org
>
> No no no.
>
> ;)
>
> blog.chandlerproject.org

Ok

>
> > + Report a Bug: chandlerproject.org/reportabug
>
> Yes, that one's implemented and let's lock on it.
>
> > + Known Issues: chandlerproject.org/knownissues*??*
>
> Ok, I'll implement this one, so let's say locked.  Where should it  
> point for now?

I think Sheila is still pulling together a known issues page. I think  
it makes the most sense to have 1 for both projects since users won't  
necessarily know where any given problem is coming from. (Sometimes  
we can't even figure it out ;)

>
> > + Project Wiki: *?? I imagine that whatever we decide for this will
> > impact the other links listed here.*
>
> Not sure what you mean.  The "project wiki" URL is  
> chandlerproject.org and I thought that was completely locked for  
> Preview and for the foreseeable future.  I can point to lots of  
> emails on the subject :)

How do we distinguish between the landing page and the wiki?

>
> > + Mailing Lists: chandlerproject.org/mailinglists*??*
>
> That's what I'd favor, as just "/lists" is probably ambigious.
>
> > + Chat on IRC: chandlerproject.org/irc*??*
> > + Get Involved / Community: chandlerproject.org/getinvolved*??*
>
> Ok, reasonable.  But where are these linked from?  The "redirect"  
> pattern we're using is nicely applied when something's going to get  
> hardcoded and shipped somewhere in an unchangeable form.  Are the  
> above in a client somewhere?

They're linked from the landing page and wiki sidebars. Ted proposed  
linking to Get Involved from the Welcome Notes.

>
>> + About OSAF: osafoundation.org
>
> I think www.osafoundation.org is better in this case.

Sure. I was being lazy and omitting www

>
>> + Download Server:  http://chandlerproject.org/downloadserver
>> -* Q* Should we just combine downloadserver and getting the source  
>> (http://chandlerproject.org/Projects/ChandlerServerSource) onto 1  
>> page with 2 sections?
>
> The homepage of downloads.osafoundation.org should be of general  
> utility and suitable for collapsing into chandlerproject.org/ 
> download for now.

I think we need to separate developer-downloads from end-user downloads.

>
>> + Cosmo Project Page:  chandlerproject.org/DeveloperArea*??*
>
> I really don't know here.  For Preview, anything expident I'd  
> think, probably a redirect would be best, ala "chandlerproject.org/ 
> cosmo".

What's the difference between the Cosmo Team page, the Cosmo portion  
of the Developer Area page and the current Cosmo Home page? It feels  
like there are too many views into the same content.

http://chandlerproject.org/Projects/EngineeringArea
http://chandlerproject.org/Projects/CosmoTeam
http://chandlerproject.org/Projects/CosmoHome

I think CosmoHome should probably be split up between the Developer  
Area and Cosmo Team pages and deprecated. I've logged a bug against  
Ted to keep track of this issue: https://bugzilla.osafoundation.org/ 
show_bug.cgi?id=9820

As for the About Chandler Hub... in particular, where we point people  
depends on whether we think they'll be end-users or developers. If  
it's an end-user link, then we should probably just point them to the  
landing page. Ted, do you have any thoughts on this?

>
> It's possible that after Preview\ we'll find that not have product- 
> specific homepage/landing pages even on the wiki is kinda weird and  
> we'll want to create some.  At that point, the /cosmo link could be  
> redirected.
>
>> + Cosmo Help: chandlerproject.org/faq*??*
>
> Best practice is to ship release-specific documentation with a  
> product itself.  Our use of wiki pages is something of a shortcut,  
> based on cosmo-dev list discussions.  Long term, I think it's very  
> possible we'll want to switch to going to product-specific help links.
>
> For Cosmo, the current plan of record is to create a page on the  
> wiki for each release and code that into the software.  That page  
> can then be made to be release-specific or just include the  
> contents of a more general page for now.

Okay, who owns that?

>
> We're not getting a whole lot of value out of the "page per  
> release" strategy right now but I'd guess the Cosmo team might want  
> to maintain it.
>
> I think it'd be helpful to maintain this list; if you're up for  
> another round of updating your list and reposting, it's a good  
> thing for polish up and have a definitive list.

Yes when we iron out all the issues, I will create a wiki page with  
all these URLs.

Thx!

Mimi


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/general/attachments/20070707/0826749a/attachment.html