If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Add Mozilla NYC to the /contacts/spaces page

RESOLVED INVALID

Status

www.mozilla.org
Pages & Content
RESOLVED INVALID
3 years ago
3 years ago

People

(Reporter: mruttley, Assigned: retornam)

Tracking

Production
Other
All

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [kb=1408057] )

(Reporter)

Description

3 years ago
http://www.mozilla.org/en-US/contact/spaces/

should also include:

115 East 23rd Street
Floor 5
NYC, NY 10010

Since we have a new office!~

Updated

3 years ago
Component: Other → Pages & Content
Product: Websites → www.mozilla.org
Version: unspecified → Production

Updated

3 years ago
Whiteboard: [kb=1408057]
(Assignee)

Updated

3 years ago
Assignee: nobody → mozbugs.retornam
I'm just adding Lisa and Lori to this bug to confirm that we should be publicly listing an NYC office.

Lisa and Lori - Please advise.  Should we list the NYC office on East 23rd on the Spaces page?

http://www.mozilla.org/en-US/contact/spaces/
Flags: needinfo?(ljashinsky)
Flags: needinfo?(lgray)

Comment 2

3 years ago
Adding Rob Middleton for guidance, here.
Flags: needinfo?(ljashinsky)

Comment 3

3 years ago
I really don't think we should add the NY office to the MozSpaces page as this is not a MozSpace and is specific to Content Services and Darren's Team.  What I mean by not a MozSpace is it does not have the following:  Global badging system for access, WPR support, a true community space for drop in's, no receptionist and no hoteling desks.  If we publish the address then this office will have MANY people wanting to work out of it for extended periods of time which I honestly don't think this office is set up to support.

Added Darren to the bug as well to make sure I am not misspeaking.

Rob
Thanks everyone.  I'm closing this bug for now.  We can re-open if needed.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(lgray)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.