The Mozillians team has been thinking about the things we'd like to do with Engagement Tools and how Mozillians.org mesh over time. Currently, the plan is to build out things like a TaskBoard and an Events Manager (each as platforms from the onset) over the next year, while also laying groundwork to better integrate the Community Directory app with a Web Service API and a means to parse for aggregated Contributor Metrics (i.e. moving it to become a platform) [1].
These apps are expected to be lightly tied to each other and resemble more of a collection of tools, but its likely that they become much more closely tied than they should be if they are all built on Mozillians.org. People will believe it to be a single app and treat it as such. Further, any of these apps could become large depending on needs and popularity; we'll need enough space for them to grow on their own freely.
The sanest approach here is to emulate this type of product development not only within the codebase, but also within our URL scheme.
So, what does that mean? Well, its the following:
1. Host the Phonebook app on connect.mozilla.org instead of mozillians.org and re-direct from the latter until it is not necessary. 2. Host the TaskBoard on tasks.mozilla.org and the Events Manager on events.mozilla.org. Any new tools will have their own sub-domain on mozilla.org as seen fit.
This proposal works with another tool in the Engagement Toolkit, input.mozilla.org. We've had universal approval by pretty much everyone asked on #mozillians and on the Contributor Engagement team, but that doesn't mean much until it's gone through this mailing list. So, here's a call out to ask for opinions on if this matches everyone's expectations of the roadmap.
I agree 100% with the reasoning for changing the app's URL from mozillians.org.
To me, I think phonebook.mozilla.org would make more sense since we already refer to mozillians.org as the Phonebook. There is a separate Phonebook app for staff already at phonebook.mozilla.org, which is less relevant now that we have a better Phonebook app for everyone to use.
We could move the staff app to an intranet or different URL and then have the Phonebook app live at phonebook.mozillians.org. This would allow us to have a similar naming convention for tools (eg: phonebook, tasks, events, badges) that are all nouns. On the other hand, "connect" is a verb and doesn't follow the convention for the other tool names.
This requires a bit more IT work than the sanest approach you proposed, but I think it would benefit users more.
> The Mozillians team has been thinking about the things we'd like to do with Engagement Tools and how Mozillians.org mesh over time. Currently, the plan is to build out things like a TaskBoard and an Events Manager (each as platforms from the onset) over the next year, while also laying groundwork to better integrate the Community Directory app with a Web Service API and a means to parse for aggregated Contributor Metrics (i.e. moving it to become a platform) [1].
> These apps are expected to be lightly tied to each other and resemble more of a collection of tools, but its likely that they become much more closely tied than they should be if they are all built on Mozillians.org. People will believe it to be a single app and treat it as such. Further, any of these apps could become large depending on needs and popularity; we'll need enough space for them to grow on their own freely.
> The sanest approach here is to emulate this type of product development not only within the codebase, but also within our URL scheme.
> So, what does that mean? Well, its the following:
> 1. Host the Phonebook app on connect.mozilla.org instead of mozillians.org and re-direct from the latter until it is not necessary.
> 2. Host the TaskBoard on tasks.mozilla.org and the Events Manager on events.mozilla.org. Any new tools will have their own sub-domain on mozilla.org as seen fit.
> This proposal works with another tool in the Engagement Toolkit, input.mozilla.org. We've had universal approval by pretty much everyone asked on #mozillians and on the Contributor Engagement team, but that doesn't mean much until it's gone through this mailing list. So, here's a call out to ask for opinions on if this matches everyone's expectations of the roadmap.
> To me, I think phonebook.mozilla.org would make more sense since we
> already refer to mozillians.org as the Phonebook. There is a separate
> Phonebook app for staff already at phonebook.mozilla.org, which is less
> relevant now that we have a better Phonebook app for everyone to use.
I think this should at least be looked into. Easier to fix the URLs than people's perceptions of what the product is called :-)
i.e. one sub-domain, consisting as many apps as required - would be more
meaningful. It will also save the sub-domain jungle - but hey, that's my
personal opinion.
Like for "projects" (M.O/projects/firefox, M.O/projects/thunderbird), it
can also be like M.O/connect/mozillians et. al.
Just a suggestion from my understanding - please don't court-martial me! :-/
> 1. Host the Phonebook app on connect.mozilla.org instead of mozillians.org and re-direct from the latter until it is not necessary.
I'm fine with this.
For background, earlier this year we chose to consciously make an
exception to the One Mozilla domain name policy and go with
mozillians.org for a couple of reasons:
* There weren't any suggestions for a compelling mozilla.org domain
name. We really wanted to go with people.mozilla.org but that was
taken. It seems like connect.mozilla.org is a good alternative.
* 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. That having
been said, we can keep some wording about people being Mozillians on
the site without it being used as the domain name.
On the side note of using the word Mozillians, I like it as a word
describing the community as a whole. I recently took advantage of it
to call my Toronto facebook group "Mozillians Toronto" to avoid
confusion with the office or the corp if I used "Mozilla Toronto." So
I like that not using it as the domain frees it back up as an open
word, and not one referring to a specific project!
>> 1. Host the Phonebook app on connect.mozilla.org instead of mozillians.org and re-direct from the latter until it is not necessary.
> I'm fine with this.
> For background, earlier this year we chose to consciously make an
> exception to the One Mozilla domain name policy and go with
> mozillians.org for a couple of reasons:
> * There weren't any suggestions for a compelling mozilla.org domain
> name. We really wanted to go with people.mozilla.org but that was
> taken. It seems like connect.mozilla.org is a good alternative.
> * 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. That having
> been said, we can keep some wording about people being Mozillians on
> the site without it being used as the domain name.
> > 1. Host the Phonebook app on connect.mozilla.org instead of mozillians.org and re-direct from the latter until it is not necessary.
> I'm fine with this.
> For background, earlier this year we chose to consciously make an
> exception to the One Mozilla domain name policy and go with
> mozillians.org for a couple of reasons:
> * There weren't any suggestions for a compelling mozilla.org domain
> name. We really wanted to go with people.mozilla.org but that was
> taken. It seems like connect.mozilla.org is a good alternative.
> * 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. That having
> been said, we can keep some wording about people being Mozillians on
> the site without it being used as the domain name.
> David
Joining in a bit late, but really glad this is happening. I wanted to
outline a potential conflict for Mozillians to use
connect.mozilla.org.
In just a few weeks we will be bring the BrowserID/Persona product to
market, which is in many ways a Mozilla connect product. Content-wise,
there's a lot of connecting going on and that's just in the copy :-)
Right or wrong in the perception of the BrowserID/Persona product, a
number of journalists and bloggers have written about it as a
Facebook, Twitter, and OpenID "connect killer."
From an seo/sem, general search traffic, and content strategy
perspective, I recommend strongly against any product that is not
BrowserID/Persona using the word connect in their URL.
There are a number of high volume search queries around Mozilla's
*connect* authentication product, and it's likely that we'll be
working towards optimizing the BrowserID/Persona product to compete
against other connect products on the web.
Additionally, it could be a confusing experience when users arrive at
connect.mozilla.org looking for the BrowserID/Persona *connect*
product, they might mistake Mozillians as our identity product.
What are your thoughts? If I can be helpful
Here are a few links that offer the context of BrowserID/Persona as a
Mozilla connect product (again, right or wrong, it's an established
perception):
Please let me know if I can be helpful in your efforts, moving over to
mozilla.org and fitting smoothly into the information architecture,
search and content strategy.
> On Dec 1 2011, 8:44 am, davidwboswell<davidweldonbosw...@gmail.com>
> wrote:
>>> These apps are expected to be lightly tied to each other and resemble more of a collection of tools
>> I definitely like this approach of having a connected set of tools
>> instead of adding everything onto one site.
>> It also fits the domain name policy better with each separate service
>> being hosted on it's own sub-domain. For reference see:
>>> 1. Host the Phonebook app on connect.mozilla.org instead of mozillians.org and re-direct from the latter until it is not necessary.
>> I'm fine with this.
>> For background, earlier this year we chose to consciously make an
>> exception to the One Mozilla domain name policy and go with
>> mozillians.org for a couple of reasons:
>> * There weren't any suggestions for a compelling mozilla.org domain
>> name. We really wanted to go with people.mozilla.org but that was
>> taken. It seems like connect.mozilla.org is a good alternative.
>> * 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. That having
>> been said, we can keep some wording about people being Mozillians on
>> the site without it being used as the domain name.
>> David
> Joining in a bit late, but really glad this is happening. I wanted to
> outline a potential conflict for Mozillians to use
> connect.mozilla.org.
> In just a few weeks we will be bring the BrowserID/Persona product to
> market, which is in many ways a Mozilla connect product. Content-wise,
> there's a lot of connecting going on and that's just in the copy :-)
> Right or wrong in the perception of the BrowserID/Persona product, a
> number of journalists and bloggers have written about it as a
> Facebook, Twitter, and OpenID "connect killer."
> From an seo/sem, general search traffic, and content strategy
> perspective, I recommend strongly against any product that is not
> BrowserID/Persona using the word connect in their URL.
> There are a number of high volume search queries around Mozilla's
> *connect* authentication product, and it's likely that we'll be
> working towards optimizing the BrowserID/Persona product to compete
> against other connect products on the web.
> Additionally, it could be a confusing experience when users arrive at
> connect.mozilla.org looking for the BrowserID/Persona *connect*
> product, they might mistake Mozillians as our identity product.
> What are your thoughts? If I can be helpful
> Here are a few links that offer the context of BrowserID/Persona as a
> Mozilla connect product (again, right or wrong, it's an established
> perception):
> Please let me know if I can be helpful in your efforts, moving over to
> mozilla.org and fitting smoothly into the information architecture,
> search and content strategy.
Is there anything we can still do about "persona" as a name for browserid at this point? It's just really not a good product name for any latin-based language, sadly.
Yes, considering Mozilla spent a long time promoting "Personas" I
think the same reasoning applies here (are those being renamed or
dropped?). Just change it to "connect?" 2 birds one stone?
>>>> 1. Host the Phonebook app on connect.mozilla.org instead of
>>>> mozillians.org and re-direct from the latter until it is not necessary.
>>> I'm fine with this.
>>> For background, earlier this year we chose to consciously make an
>>> exception to the One Mozilla domain name policy and go with
>>> mozillians.org for a couple of reasons:
>>> * There weren't any suggestions for a compelling mozilla.org domain
>>> name. We really wanted to go with people.mozilla.org but that was
>>> taken. It seems like connect.mozilla.org is a good alternative.
>>> * 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. That having
>>> been said, we can keep some wording about people being Mozillians on
>>> the site without it being used as the domain name.
>>> David
>> Joining in a bit late, but really glad this is happening. I wanted to
>> outline a potential conflict for Mozillians to use
>> connect.mozilla.org.
>> In just a few weeks we will be bring the BrowserID/Persona product to
>> market, which is in many ways a Mozilla connect product. Content-wise,
>> there's a lot of connecting going on and that's just in the copy :-)
>> Right or wrong in the perception of the BrowserID/Persona product, a
>> number of journalists and bloggers have written about it as a
>> Facebook, Twitter, and OpenID "connect killer."
>> From an seo/sem, general search traffic, and content strategy
>> perspective, I recommend strongly against any product that is not
>> BrowserID/Persona using the word connect in their URL.
>> There are a number of high volume search queries around Mozilla's
>> *connect* authentication product, and it's likely that we'll be
>> working towards optimizing the BrowserID/Persona product to compete
>> against other connect products on the web.
>> Additionally, it could be a confusing experience when users arrive at
>> connect.mozilla.org looking for the BrowserID/Persona *connect*
>> product, they might mistake Mozillians as our identity product.
>> What are your thoughts? If I can be helpful
>> Here are a few links that offer the context of BrowserID/Persona as a
>> Mozilla connect product (again, right or wrong, it's an established
>> perception):
>> Please let me know if I can be helpful in your efforts, moving over to
>> mozilla.org and fitting smoothly into the information architecture,
>> search and content strategy.
> Is there anything we can still do about "persona" as a name for browserid at
> this point? It's just really not a good product name for any latin-based
> language, sadly.
> Yes, considering Mozilla spent a long time promoting "Personas" I
> think the same reasoning applies here (are those being renamed or
> dropped?). Just change it to "connect?" 2 birds one stone?
> On Sat, Jan 28, 2012 at 12:27 PM, Axel Hecht<l...@mozilla.com> wrote:
>> On 28.01.12 06:19, Chrissie Brodigan wrote:
>>> On Dec 1 2011, 8:44 am, davidwboswell<davidweldonbosw...@gmail.com>
>>> wrote:
>>>>> These apps are expected to be lightly tied to each other and resemble
>>>>> more of a collection of tools
>>>> I definitely like this approach of having a connected set of tools
>>>> instead of adding everything onto one site.
>>>> It also fits the domain name policy better with each separate service
>>>> being hosted on it's own sub-domain. For reference see:
>>>>> 1. Host the Phonebook app on connect.mozilla.org instead of
>>>>> mozillians.org and re-direct from the latter until it is not necessary.
>>>> I'm fine with this.
>>>> For background, earlier this year we chose to consciously make an
>>>> exception to the One Mozilla domain name policy and go with
>>>> mozillians.org for a couple of reasons:
>>>> * There weren't any suggestions for a compelling mozilla.org domain
>>>> name. We really wanted to go with people.mozilla.org but that was
>>>> taken. It seems like connect.mozilla.org is a good alternative.
>>>> * 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. That having
>>>> been said, we can keep some wording about people being Mozillians on
>>>> the site without it being used as the domain name.
>>>> David
>>> Joining in a bit late, but really glad this is happening. I wanted to
>>> outline a potential conflict for Mozillians to use
>>> connect.mozilla.org.
>>> In just a few weeks we will be bring the BrowserID/Persona product to
>>> market, which is in many ways a Mozilla connect product. Content-wise,
>>> there's a lot of connecting going on and that's just in the copy :-)
>>> Right or wrong in the perception of the BrowserID/Persona product, a
>>> number of journalists and bloggers have written about it as a
>>> Facebook, Twitter, and OpenID "connect killer."
>>> From an seo/sem, general search traffic, and content strategy
>>> perspective, I recommend strongly against any product that is not
>>> BrowserID/Persona using the word connect in their URL.
>>> There are a number of high volume search queries around Mozilla's
>>> *connect* authentication product, and it's likely that we'll be
>>> working towards optimizing the BrowserID/Persona product to compete
>>> against other connect products on the web.
>>> Additionally, it could be a confusing experience when users arrive at
>>> connect.mozilla.org looking for the BrowserID/Persona *connect*
>>> product, they might mistake Mozillians as our identity product.
>>> What are your thoughts? If I can be helpful
>>> Here are a few links that offer the context of BrowserID/Persona as a
>>> Mozilla connect product (again, right or wrong, it's an established
>>> perception):
>>> Please let me know if I can be helpful in your efforts, moving over to
>>> mozilla.org and fitting smoothly into the information architecture,
>>> search and content strategy.
>> Is there anything we can still do about "persona" as a name for browserid at
>> this point? It's just really not a good product name for any latin-based
>> language, sadly.
Thanks for the thoughts, Chrissie. That's some interesting stuff to mull over, but I think its manage-able to use the name and brand of "Mozilla Connect" since it's really just connecting new/potential contributors to folks in the Mozilla Project and its web properties. We're not building a SSO; we're building a directory app with web services.
Also, Personas is an identity solution for users across the web. The branding choice there resonates something much deeper and personal than something like "Mozilla Connect". Basically, we just need to be careful in where we link this to and how its framed in copy as well as design. That's something I'd expect our fantastic Creative team to be able to easily figure out!
----- Original Message -----
From: "Chrissie Brodigan" <christine.brodi...@gmail.com>
To: mozilli...@lists.mozilla.org
Sent: Friday, January 27, 2012 9:19:20 PM
Subject: Re: [mozillians] Changing the Phonebook app's URL from "mozillians.org" to "connect.mozilla.org"
On Dec 1 2011, 8:44 am, davidwboswell <davidweldonbosw...@gmail.com>
wrote:
> > These apps are expected to be lightly tied to each other and resemble more of a collection of tools
> I definitely like this approach of having a connected set of tools
> instead of adding everything onto one site.
> It also fits the domain name policy better with each separate service
> being hosted on it's own sub-domain. For reference see:
> > 1. Host the Phonebook app on connect.mozilla.org instead of mozillians.org and re-direct from the latter until it is not necessary.
> I'm fine with this.
> For background, earlier this year we chose to consciously make an
> exception to the One Mozilla domain name policy and go with
> mozillians.org for a couple of reasons:
> * There weren't any suggestions for a compelling mozilla.org domain
> name. We really wanted to go with people.mozilla.org but that was
> taken. It seems like connect.mozilla.org is a good alternative.
> * 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. That having
> been said, we can keep some wording about people being Mozillians on
> the site without it being used as the domain name.
> David
Joining in a bit late, but really glad this is happening. I wanted to
outline a potential conflict for Mozillians to use
connect.mozilla.org.
In just a few weeks we will be bring the BrowserID/Persona product to
market, which is in many ways a Mozilla connect product. Content-wise,
there's a lot of connecting going on and that's just in the copy :-)
Right or wrong in the perception of the BrowserID/Persona product, a
number of journalists and bloggers have written about it as a
Facebook, Twitter, and OpenID "connect killer."
>From an seo/sem, general search traffic, and content strategy
perspective, I recommend strongly against any product that is not
BrowserID/Persona using the word connect in their URL.
There are a number of high volume search queries around Mozilla's
*connect* authentication product, and it's likely that we'll be
working towards optimizing the BrowserID/Persona product to compete
against other connect products on the web.
Additionally, it could be a confusing experience when users arrive at
connect.mozilla.org looking for the BrowserID/Persona *connect*
product, they might mistake Mozillians as our identity product.
What are your thoughts? If I can be helpful
Here are a few links that offer the context of BrowserID/Persona as a
Mozilla connect product (again, right or wrong, it's an established
perception):
Please let me know if I can be helpful in your efforts, moving over to
mozilla.org and fitting smoothly into the information architecture,
search and content strategy.
_______________________________________________
mozillians mailing list
mozilli...@lists.mozilla.org
https://lists.mozilla.org/listinfo/mozillians
There were plans at one point, as i recall, to give all Mozillians an
@mozillians.org email address -- something that isn't possible with
@mozilla.org. The purpose of that, I believe, was to enable an
Mozillians-wide Yammer instance.
I don't think it will change much. mrz and I have talked at length on how to get contributors up on Yammer and that should be possible once we develop the Moz Connect Web Services mentioned here:
----- Original Message -----
From: "Deb Richardson" <d...@dria.org>
To: "Aakash Desai" <ade...@mozilla.com>
Cc: "Chrissie Brodigan" <christine.brodi...@gmail.com>, mozilli...@lists.mozilla.org
Sent: Saturday, January 28, 2012 1:32:59 PM
Subject: Re: [mozillians] Changing the Phonebook app's URL from "mozillians.org" to "connect.mozilla.org"
There were plans at one point, as i recall, to give all Mozillians an
@mozillians.org email address -- something that isn't possible with
@mozilla.org. The purpose of that, I believe, was to enable an
Mozillians-wide Yammer instance.
Thanks for the feedback. I wanted to take a minute to address the
question/comments about BrowserID being named Persona.
Yes, BrowserID will be named Mozilla Persona. The name will be coupled
with a tagline and visual identity to make sure it is clear what the
Mozilla Persona product is. During the process we did solicit feedback
from the community and specifically emailed both the marketing list
and the world ready list in Dec. We did hear some concerns from the
community about Persona meaning "person" in many other languages but
after talking through this further with the community and doing some
additional research we were able to alleviate this concern as the
consensus was that we could easily address the confusion between
"Persona" and person through a tagline, key messages and visual
identity.
We also asked the community about renaming the current "Personas"
product in Add-ons and the feedback was also that we could probably
find a more descriptive name for that product such as backgrounds or
wallpaper (those name(s) are not confirmed). We will be working with
the community to confirm the new name for the current Persona's
product. More to come around the renaming of Persona's.
Thanks,
Kristin
On Jan 30, 10:13 am, Robert Kaiser <ka...@kairo.at> wrote:
I follow the marketing list and I don't have such an email thread. Be
careful when you say you approached "the community" because it is very
large and unless you made sure to post on many mailing lists, and in
the newsletter you probably didn't reach "the community."
It's my understanding that "Persona" will not be just browserID but
one component of it, and maybe the current personas will be part of
your mozilla persona. If this is the case it would be a lot easier to
use the current marketing around "Personas" to start introducing the
idea that it will be a collection of customizations, and refer to the
themes by the new name.
But certainly there are a lot of other words that wouldn't have the
same problem as "Persona" does. Perhaps you could link to something
that explains what else you considered and why it wouldn't work. That
would make it a lot easier for people to agree with the decision.
On Mon, Jan 30, 2012 at 8:25 PM, Kristin Baird <kristinjcon...@gmail.com> wrote:
> Hi,
> Thanks for the feedback. I wanted to take a minute to address the
> question/comments about BrowserID being named Persona.
> Yes, BrowserID will be named Mozilla Persona. The name will be coupled
> with a tagline and visual identity to make sure it is clear what the
> Mozilla Persona product is. During the process we did solicit feedback
> from the community and specifically emailed both the marketing list
> and the world ready list in Dec. We did hear some concerns from the
> community about Persona meaning "person" in many other languages but
> after talking through this further with the community and doing some
> additional research we were able to alleviate this concern as the
> consensus was that we could easily address the confusion between
> "Persona" and person through a tagline, key messages and visual
> identity.
> We also asked the community about renaming the current "Personas"
> product in Add-ons and the feedback was also that we could probably
> find a more descriptive name for that product such as backgrounds or
> wallpaper (those name(s) are not confirmed). We will be working with
> the community to confirm the new name for the current Persona's
> product. More to come around the renaming of Persona's.
> Thanks,
> Kristin
> On Jan 30, 10:13 am, Robert Kaiser <ka...@kairo.at> wrote:
>> ChrissieBrodigan schrieb:
>> > In just a few weeks we will be bring the BrowserID/Persona product to
>> > market, which is in many ways a Mozilla connect product.
>> Eww... "persona"? Really? Once again using that word that has no meaning
>> at all or even confusing meaning to non-US people? :(
Sorry if this doesn't thread correctly in your clients - I just joined the list so I can't reply and get all the headers right..
Anyway, just wanted to chime in on the two identity points on this thread:
* On "connect": our identity platform/roadmap includes several components related to connecting--to a site, or between people. I do talk about connect, and it's also in one of the taglines we are considering. So I do have some amount of concern about using that term. However- we are not actually planning to use it in a domain, or in a top-level brand, so there wouldn't be a straight-up conflict, just risk of confusion or SEO issues.
I'm not sure how to evaluate the risks on this, so I defer that to the branding and SEO experts in marketing--should we be concerned? can we mitigate the risks?
* On the "persona" name:
Our identity product is not just BrowserID, that is just one component. Our aim is to create a platform for defining "you" on the Web. For example, we want the identity product to include user profiles, links to your data, your contacts/friends, and even payment methods. Your profile should include your favorite/current Firefox skins, btw.
So after a lengthy search, we think that Persona is actually a great match. It is deeply connected to identity (whether viewed as "character", "personality", or "personhood"), and allows us to grow our product under that umbrella to cover all of the fun stuff we want to do. We did hear some concerns about localization, and I do think we will need some help in making the roll-out smooth--particularly since we already have Personas, which makes the transition more difficult.
I am a native Spanish (es_VE) speaker, FWIW, and also speak some Italian. I think we can make it work, we just need to think it through!
Thanks Dan. That sums it up really well. As we continue to make
progress on Persona we will update everyone with the roll out plan.
As we mentioned we did reach out to both the marketing list and the
world ready list on/around 12/20 and received quite a great deal of
valuable feedback that we are incorporating into the roll out plan for
the Persona name.
Please let us know if there are any additional questions.
Thanks,
Kristin
On Jan 30, 9:20 pm, Dan Mills <thun...@mozilla.com> wrote:
> Sorry if this doesn't thread correctly in your clients - I just joined the list so I can't reply and get all the headers right..
> Anyway, just wanted to chime in on the two identity points on this thread:
> * On "connect": our identity platform/roadmap includes several components related to connecting--to a site, or between people. I do talk about connect, and it's also in one of the taglines we are considering. So I do have some amount of concern about using that term. However- we are not actually planning to use it in a domain, or in a top-level brand, so there wouldn't be a straight-up conflict, just risk of confusion or SEO issues.
> I'm not sure how to evaluate the risks on this, so I defer that to the branding and SEO experts in marketing--should we be concerned? can we mitigate the risks?
> * On the "persona" name:
> Our identity product is not just BrowserID, that is just one component. Our aim is to create a platform for defining "you" on the Web. For example, we want the identity product to include user profiles, links to your data, your contacts/friends, and even payment methods. Your profile should include your favorite/current Firefox skins, btw.
> So after a lengthy search, we think thatPersonais actually a great match. It is deeply connected to identity (whether viewed as "character", "personality", or "personhood"), and allows us to grow our product under that umbrella to cover all of the fun stuff we want to do. We did hear some concerns about localization, and I do think we will need some help in making the roll-out smooth--particularly since we already have Personas, which makes the transition more difficult.
> I am a native Spanish (es_VE) speaker, FWIW, and also speak some Italian. I think we can make it work, we just need to think it through!
IMHO and based in no research from my "own small world within pt-BR angle (
Brazil )" I see no problem if Mozilla is coming up with the name *persona*
and willing to position it as a product/brand. The fact personas is there
is a lovely confusion for me and I like to think that Personas brand could
go away in the long term future.
One thing to pay attention, community check needed, is the check if in any
country the word persona has a meaning or association with product or
system that is not aligned with Mozilla style ( like if means something
really bad ) or largely in use.
The part that is concerns me is the long term vision, or ambition, about
these potential products vs names vs platform vs open standards vs moz
mission. And I am not following other discussions so my apologies as I may
be totally lost. I think that a very clear and in dept documentation (
high level, not technical ) on how Mozilla see identity vs roadmap of
investments vs potential products/platform/open standards is key for
Mozilla as identity touches ( or demands involvement of ) constituents
deeply. I also took a couple minutes now to look browserId from google
search door and noticed I was taken to a mozilla labs page with the
statement " a better way to sign in " and when looked for more info it took
me to a sumo page :
https://support.mozilla.org/en-US/kb/what-browserid-and-how-does-it-w... seems to lack connection with mozilla's ambition/mission/views. So
then I wonder what is the current amount of users online that are being
aware of this word/term/site/service browser ID and if it is perhaps time
to associate mozilla's high level documentation/response/answer at these
pages.
On Tue, Jan 31, 2012 at 3:20 AM, Dan Mills <thun...@mozilla.com> wrote:
> Hi guys,
> Sorry if this doesn't thread correctly in your clients - I just joined the
> list so I can't reply and get all the headers right..
> Anyway, just wanted to chime in on the two identity points on this thread:
> * On "connect": our identity platform/roadmap includes several components
> related to connecting--to a site, or between people. I do talk about
> connect, and it's also in one of the taglines we are considering. So I do
> have some amount of concern about using that term. However- we are not
> actually planning to use it in a domain, or in a top-level brand, so there
> wouldn't be a straight-up conflict, just risk of confusion or SEO issues.
> I'm not sure how to evaluate the risks on this, so I defer that to the
> branding and SEO experts in marketing--should we be concerned? can we
> mitigate the risks?
> * On the "persona" name:
> Our identity product is not just BrowserID, that is just one component.
> Our aim is to create a platform for defining "you" on the Web. For example,
> we want the identity product to include user profiles, links to your data,
> your contacts/friends, and even payment methods. Your profile should
> include your favorite/current Firefox skins, btw.
> So after a lengthy search, we think that Persona is actually a great
> match. It is deeply connected to identity (whether viewed as "character",
> "personality", or "personhood"), and allows us to grow our product under
> that umbrella to cover all of the fun stuff we want to do. We did hear some
> concerns about localization, and I do think we will need some help in
> making the roll-out smooth--particularly since we already have Personas,
> which makes the transition more difficult.
> I am a native Spanish (es_VE) speaker, FWIW, and also speak some Italian.
> I think we can make it work, we just need to think it through!
*frown*
But then, a decision is a decision, I guess. Will be hard to market that in the German market as even "Personas" was already confusing as hell to people here, but then, I'm not the marketing team, so I don't have to do the marketing. Even "BrowserID" is a way clearer message to people from where I stand, but my POV might be completely wrong.
> During the process we did solicit feedback
> from the community and specifically emailed both the marketing list
> and the world ready list in Dec.
Interesting. I've been considering myself a part of "the community" for 12 years and this is the first I heard of this. Maybe I'm not in the community you are talking of. Also, I would have thought that people paid by Mozilla would at least get an early warning about it, but I first heard it yesterday on IRC when people working for us were just as confused as myself. Seems like we still have some way to go in improving communications among contributors. Also, I'm on mozilla.marketing / markt...@lists.m.o and haven't seen it there, but maybe there's different "marketing lists".
I guess the thing to remember is that while it doesn't resonate now,
neither did a bunch of other terms we're used to now. That said
though, in theory we could also make up a catchier term if we have to
do a lot of leg work towards expressing the meaning.
I definitely see how Persona fits, especially if we're expecting users
to use multiple personas. ie one set of settings for online
transactions, another for work, another for social networking.
On Tue, Jan 31, 2012 at 6:41 AM, Marcio Galli <mga...@mgalli.com> wrote:
> IMHO and based in no research from my "own small world within pt-BR angle (
> Brazil )" I see no problem if Mozilla is coming up with the name *persona*
> and willing to position it as a product/brand. The fact personas is there
> is a lovely confusion for me and I like to think that Personas brand could
> go away in the long term future.
> One thing to pay attention, community check needed, is the check if in any
> country the word persona has a meaning or association with product or
> system that is not aligned with Mozilla style ( like if means something
> really bad ) or largely in use.
> The part that is concerns me is the long term vision, or ambition, about
> these potential products vs names vs platform vs open standards vs moz
> mission. And I am not following other discussions so my apologies as I may
> be totally lost. I think that a very clear and in dept documentation (
> high level, not technical ) on how Mozilla see identity vs roadmap of
> investments vs potential products/platform/open standards is key for
> Mozilla as identity touches ( or demands involvement of ) constituents
> deeply. I also took a couple minutes now to look browserId from google
> search door and noticed I was taken to a mozilla labs page with the
> statement " a better way to sign in " and when looked for more info it took
> me to a sumo page :
> https://support.mozilla.org/en-US/kb/what-browserid-and-how-does-it-w... > seems to lack connection with mozilla's ambition/mission/views. So
> then I wonder what is the current amount of users online that are being
> aware of this word/term/site/service browser ID and if it is perhaps time
> to associate mozilla's high level documentation/response/answer at these
> pages.
> m
> On Tue, Jan 31, 2012 at 3:20 AM, Dan Mills <thun...@mozilla.com> wrote:
>> Hi guys,
>> Sorry if this doesn't thread correctly in your clients - I just joined the
>> list so I can't reply and get all the headers right..
>> Anyway, just wanted to chime in on the two identity points on this thread:
>> * On "connect": our identity platform/roadmap includes several components
>> related to connecting--to a site, or between people. I do talk about
>> connect, and it's also in one of the taglines we are considering. So I do
>> have some amount of concern about using that term. However- we are not
>> actually planning to use it in a domain, or in a top-level brand, so there
>> wouldn't be a straight-up conflict, just risk of confusion or SEO issues.
>> I'm not sure how to evaluate the risks on this, so I defer that to the
>> branding and SEO experts in marketing--should we be concerned? can we
>> mitigate the risks?
>> * On the "persona" name:
>> Our identity product is not just BrowserID, that is just one component.
>> Our aim is to create a platform for defining "you" on the Web. For example,
>> we want the identity product to include user profiles, links to your data,
>> your contacts/friends, and even payment methods. Your profile should
>> include your favorite/current Firefox skins, btw.
>> So after a lengthy search, we think that Persona is actually a great
>> match. It is deeply connected to identity (whether viewed as "character",
>> "personality", or "personhood"), and allows us to grow our product under
>> that umbrella to cover all of the fun stuff we want to do. We did hear some
>> concerns about localization, and I do think we will need some help in
>> making the roll-out smooth--particularly since we already have Personas,
>> which makes the transition more difficult.
>> I am a native Spanish (es_VE) speaker, FWIW, and also speak some Italian.
>> I think we can make it work, we just need to think it through!
> Kristin Baird schrieb:
>> Yes, BrowserID will be named Mozilla Persona.
> *frown*
> But then, a decision is a decision, I guess. Will be hard to market that
> in the German market as even "Personas" was already confusing as hell to
> people here, but then, I'm not the marketing team, so I don't have to do
> the marketing. Even "BrowserID" is a way clearer message to people from
> where I stand, but my POV might be completely wrong.
>> During the process we did solicit feedback
>> from the community and specifically emailed both the marketing list
>> and the world ready list in Dec.
> Interesting. I've been considering myself a part of "the community" for
> 12 years and this is the first I heard of this. Maybe I'm not in the
> community you are talking of. Also, I would have thought that people
> paid by Mozilla would at least get an early warning about it, but I
> first heard it yesterday on IRC when people working for us were just as
> confused as myself. Seems like we still have some way to go in improving
> communications among contributors. Also, I'm on mozilla.marketing /
> markt...@lists.m.o and haven't seen it there, but maybe there's
> different "marketing lists".
> Robert Kaiser
Robert, if you want to get an invite to world-ready, feel free to give stas a poke. moco is rather underrepresented there ;-)
On Tue, Jan 31, 2012 at 4:32 PM, Axel Hecht <l...@mozilla.com> wrote:
> On 31.01.12 19:32, Robert Kaiser wrote:
>> Kristin Baird schrieb:
>>> Yes, BrowserID will be named Mozilla Persona.
>> *frown*
>> But then, a decision is a decision, I guess. Will be hard to market that
>> in the German market as even "Personas" was already confusing as hell to
>> people here, but then, I'm not the marketing team, so I don't have to do
>> the marketing. Even "BrowserID" is a way clearer message to people from
>> where I stand, but my POV might be completely wrong.
>>> During the process we did solicit feedback
>>> from the community and specifically emailed both the marketing list
>>> and the world ready list in Dec.
>> Interesting. I've been considering myself a part of "the community" for
>> 12 years and this is the first I heard of this. Maybe I'm not in the
>> community you are talking of. Also, I would have thought that people
>> paid by Mozilla would at least get an early warning about it, but I
>> first heard it yesterday on IRC when people working for us were just as
>> confused as myself. Seems like we still have some way to go in improving
>> communications among contributors. Also, I'm on mozilla.marketing /
>> markt...@lists.m.o and haven't seen it there, but maybe there's
>> different "marketing lists".
>> Robert Kaiser
> Robert, if you want to get an invite to world-ready, feel free to give stas
> a poke. moco is rather underrepresented there ;-)
