change domain of mozillians.org to community.mozilla.org

RESOLVED INCOMPLETE

Status

P1
normal
RESOLVED INCOMPLETE
6 years ago
5 years ago

People

(Reporter: sancus, Unassigned)

Tracking

Details

(Whiteboard: [triaged 20121108])

(Reporter)

Description

6 years ago
We want to change the domain of mozillians.org to community.mozilla.org 

There's a patch that handles all the code changes ready to go in Pull Request on github, but I'm making this bug before merging since I'm not sure what order we need to do things in to get this changed.

I know there's probably three different environments to change on the IT side, plus database names and whatever DNS stuff needs to happen. So, if we can list out what needs to be done and then work on it in this bug that would be great.

Thanks!
Group: mozilla-corporation-confidential
Priority: -- → P1
Whiteboard: [triaged 20121108]
This is a significant change, adding some folks to ACK this change
(Reporter)

Comment 2

6 years ago
We definitely want to test this on dev first before we push it onwards -- the new URL should be community-dev.allizom.org
solarce: Acknowledge and approved

Comment 4

6 years ago
Hi all: Please hold on this.  We had a discussion in February about changing the URL.  Aakash had proposed connect.mozilla.org.  There was some discussion on why a change was needed (if at all) and what it would be.  community.mozilla.org was bandied around in the event if we had different access levels and other tools.  

There was no resolution and no immediate need identified to change the URL.

Please share the rationale.

Comment 5

6 years ago
Mary:

This change was put forward by Aakash here: 

https://bugzilla.mozilla.org/show_bug.cgi?id=790745

For now we will hold off until we get clarification. Please formally let me know if we should proceed or abandon.
(Reporter)

Updated

6 years ago
Blocks: 790745
Depends on: 810228
(In reply to Mary from comment #4)
> Hi all: Please hold on this.  We had a discussion in February about changing
> the URL.  Aakash had proposed connect.mozilla.org.  There was some
> discussion on why a change was needed (if at all) and what it would be. 
> community.mozilla.org was bandied around in the event if we had different
> access levels and other tools.  
> 
> There was no resolution and no immediate need identified to change the URL.
> 
> Please share the rationale.

Hey Mary,

The sign-off was given in the April/May Mozillians Roadmap/Branding meeting with Beard. The three of us agreed that a URL change made sense as we were planning to build out events.mozilla.org and tasks.mozilla.org. Here's the rationale:

* events.mozilla.org is on the roadmap as it fits needs with the org (we've designed a dev plan with approval on this with the Reps portal)
* We're supplying an API that only allows mozilla.org properties to use it. We want to alleviate any potential user perspective issue of offering an API of personally-identifiable data from a non mozilla.org property. 
* The design and dev team wants us to switch to the One Mozilla template and changing the url domain to mozilla.org is a part of those efforts.
* Many Reps and contributors have noted confusion about the url being off of mozilla.org [1]

I'll add on reasoning on why we chose mozillians.org as well:

* There wasn't a compelling name on mozilla.org, so mozillians.org was used
* We thought an exception might be justified in order to build up a
sense of identity among community members.  People had informally been
calling themselves Mozillians for a while and using it as the name of
the site where people created profiles seemed to fit.


This won't affect the branding; we want to continue to use Mozillians and, in fact, highlight that branding more with the One Mozilla re-design. Also, Beard gave verbal approval in the April/May meeting with this very decision.

http://mozillians.org will still be used via a re-direct. So, people can continue using it if they'd like.


[1] https://groups.google.com/forum/?fromgroups=#!searchin/mozilla.mozillians/aakash/mozilla.mozillians/O6eEc-YFHoc/CUmEB1HE_d0J
Mary: can we get approval here?

Comment 8

6 years ago
Bear with me.  Catching up on 3 days of email and getting ready for MozCamp :(

This actually was never approved in February - to be clear.  It was my suggested alternative to connect.mozilla.org.  

Not trying to be stop energy, but Chris and I were blindsided by this bug!  In order to proceed and there is very good reasoning to (thanks for the update it has been months since discussed), please circle back with everyone that was in that discussion.  It's only good hygiene and collaboration.  Those in the conversation were:

* Pete Scanlon (key for brand)
* John Slater (key for brand)
* Chris Beard (most interested in preserving brand around Mozillians - feared URL change would deprecate it)
* Our team

Once Chris is on board, please share out with the mozillians mailing list with reasoning.  This isn't to stop any progress, but share the rational.  We get very attached to our URLs :)

Comment 9

6 years ago
Mary:

OK on the above. 

For the time-being we will halt development on this and consider it out-of-scope for the API release next week.

We can decide how/when once a final decision is made on what the URL should be.

Best,
Ben
Group: mozilla-corporation-confidential

Comment 10

6 years ago
Marking this RESOLVED INCOMPLETE, pending further discussion that's outside the scope of WebOps. A new bug would probably be cleaner, if/when a final decision is reached. Thanks!
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE

Comment 11

6 years ago
Excellent point, will create a new bug for decision, this will remain the implementation bug.

Updated

6 years ago
No longer blocks: 790745

Updated

6 years ago
Depends on: 815835
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.