Closed Bug 688054 Opened 13 years ago Closed 12 years ago

Please set up mozilla.org/popcorn

Categories

(mozilla.org Graveyard :: Webdev, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ben, Unassigned)

References

Details

We're currently designing a Wordpress-powered site to live at mozilla.org/popcorn. This will be the public face of the Popcorn project, and will route to all popcorn resources in the known universe.

We've filed a bug to set up a staging area at popcorn.mozillalabs.com. We'll design and test the site there.

Please advise on steps we need to take in anticipation of deploying at /popcorn.

Will add updates as the site develops.

Many thanks,
Ben
Depends on: 688051
Depends on: 688059
Blocks: 688059
No longer depends on: 688059
CCing John Slater, who's shepherding the mozilla.org project. I am not sure how a subdirectory off the main mozilla.org domain fits into the bigger picture. Any reason why this shouldn't be popcorn.mozilla.org?
Here's a handy guide to help decide between popcorn.mozilla.org and mozilla.org/popcorn:
https://wiki.mozilla.org/Websites/Taskforce/Proposals/Domain_Name_Strategy#.22One_Mozilla.22_Strategy

Side question, but an important one: who's designing this site? Please do keep my team in the loop, and we can help if you need it.
Thanks, Fred.  To clarify this issue, I believe  Stephanie Schipper, our new VP of Web Stategy at the Foundation, met with John Slater.  It's my understanding that mozilla.org/popcorn is the proper implementation of the domain strategy - in many ways it is a "splash page" that guides users to the correct area of our project.  In the same way mozilla.org/firefox guides users to seperate channels, support, add ons etc - mozilla.org/popcorn will point users to our app, Popcorn Maker, our library popcorn.js and to our various events and outreach strategies. 

Hope that helps.
Mid air collision :)

Thanks for the task force document.  If I'm reading it correctly, we're on track.

We absolutely need help, John.  Maybe I'll drop you a line outside of this bug.
All right, if you need any help from the webdev side let us know. Looks like IT should be able to hook up your code as a subdirectory, without touching any of the existing mozilla.org infrastructure.

CCing cshields for a sanity check: Will we be able to run code in a subdirectory of mozilla.org that's completely unrelated to the PHP or bedrock code base? I am unfamiliar if Zeus can route requests based on path, or if we need to do this in Apache.
Corey also mentioned that because this would live underneath mozilla.org, it'd fall under the Bug Bounty and thus might have stricter security requirements. CCing mcoates from Infrasec: Can you please comment on comment 0 from infrasec's point of view?
We have technical issues with setting up separate sites as subdirectories under the mozilla.org domain.

From IT's perspective, if this is not going to be a part of the bedrock code it should live in popcorn.mozilla.org

We should probably meet with John and Stephanie sometime to explain the issues behind such a move to mozilla.org/popcorn  (not to mention that it would place a wordpress site within the security bug bounty program whereas popcorn.mozilla.org would not)
mozilla.org/anything won't work for a WP-powered site, so I am closing this for now. Please reopen when you want to move forward on this with a different URL.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.