Closed Bug 775224 Opened 12 years ago Closed 12 years ago

[ia] populate the new products table

Categories

(support.mozilla.org :: Knowledge Base Software, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED
2012.14

People

(Reporter: willkg, Assigned: willkg)

References

Details

(Whiteboard: u=user c=wiki p=2)

+++ This bug was initially created as a clone of Bug #768226 +++

Chunk 2:

* populate the new Products table
I think this is a 2 pointer.

The data is based on the wiki Document tags. Some of those tags are product and those products need to be in the new Products table.

We should also add a default image for each product we add.

I don't know offhand how we pre-populate data in tables.

Ricky, James: How do we do this? Fixtures? Migration? Make people type it all out (which is problematic because we need to do a migration from tags to products)?
Whiteboard: u=user c=wiki p=2
The list of all wiki Document tags is as follows:

[u'profile',
 u'cookies',
 u'privacy and security',
 u'firefox',
 u'add-ons',
 u'migrate',
 u'accessibility',
 u'recovery key',
 u'general',
 u'sync',
 u'persona',
 u'error messages',
 u'profiles',
 u'download',
 u'latest firefox',
 u'bookmarks',
 u'crashing',
 u'malware',
 u'flash',
 u'controls',
 u'desktop',
 u'tabs',
 u'tips',
 u'FxHome',
 u'marketplace',
 u'getting started',
 u'browserID',
 u'passwords',
 u'customize',
 u'dignostics',
 u'privacy & security',
 u'Firefox 1.0',
 u'ios',
 u'diagnostic',
 u'Firefox 6.0.2',
 u'Firefox 5.0',
 u'download and install',
 u'hanging and slowness',
 u'android',
 u'search',
 u'settings',
 u'mobile',
 u'versions',
 u'security and privacy',
 u'websites',
 u'slowness or hanging',
 u'diagnostics',
 u'slowness and hanging',
 u'addons',
 u'history']


The following are probably products:

* firefox
* sync
* persona (though this may actually refer to firefox personas)
* desktop
* FxHome
* marketplace
* browserID
* Firefox 1.0
* Firefox 6.0.2
* Firefox 5.0
* android
* mobile


What do we want the final list to look like?
Ccing a bunch of people. I don't know if this is the full stake-holders list.

Please see previous comment. What do we want the final list to look like?
Also, to answer the question in the description, we'll populate the data in a migration.
Assignee: nobody → willkg
Scratch that... I should just start with the products listed in the form:

* Desktop
* Mobile
* Sync
* Home
* Marketplace

Is that ok?
(In reply to Will Kahn-Greene [:willkg] from comment #5)
> Scratch that... I should just start with the products listed in the form:
> 
> * Desktop
> * Mobile
> * Sync
> * Home
> * Marketplace

Let’s add one more, which is BrowserID / Persona?

I also saw several duplicate entries on comment 2:

hanging and slowness
slowness and hanging
slowness or hanging

privacy and security
security and privacy

Is there something we can do about this? Maybe this is a question for Matt and Verdi, who are tagging articles.
(In reply to Bram Pitoyo [:bram] from comment #6)
> 
> Let’s add one more, which is BrowserID / Persona?

If we have documents for that product, I'm game for adding it now. Otherwise, we should add it later when we need it.


> I also saw several duplicate entries on comment 2:
> 
> hanging and slowness
> slowness and hanging
> slowness or hanging
> 
> privacy and security
> security and privacy
> 
> Is there something we can do about this? Maybe this is a question for Matt
> and Verdi, who are tagging articles.

Someone could spend the time to fix this now. It'll probably get fixed when we switch from tags to topics in the next few weeks. I don't know offhand what this affects, so I don't know if it's worth spending the time on it now.
I need help filling in the product data.

Verdi, Kadir: What should the values for these be?

Desktop:

* Slug: 'desktop'
* Display name: 'Firefox Desktop'
* Description:
* Display order: 

Mobile:

* Slug: 'mobile'
* Display name: 'Firefox Mobile'
* Description:
* Display order: 

Sync:

* Slug: 'sync'
* Display name: 'Sync'
* Description:
* Display order: 

Home:

* Slug: 'home'
* Display name: 'Home'
* Description:
* Display order: 

Marketplace:

* Slug: 'marketplace'
* Display name: 'Marketplace'
* Description:
* Display order:
(In reply to Will Kahn-Greene [:willkg] from comment #7)
> > Let’s add one more, which is BrowserID / Persona?
> 
> If we have documents for that product, I'm game for adding it now.
> Otherwise, we should add it later when we need it.

There are only two articles about BrowserID:
* https://support.mozilla.org/en-US/kb/what-browserid-and-how-does-it-work
* https://support.mozilla.org/en-US/kb/how-do-i-manage-my-browserid-account

Is it worth it to add now? It might not. I want feedback from Verdi for adding this as a product.


Taking a stab at the description and display order. Feel free to correct if I’m wrong.

Desktop:

* Slug: 'desktop'
* Display name: 'Firefox Desktop'
* Description: Web browser for Windows, Mac and Linux
* Display order: 1

Mobile:

* Slug: 'mobile'
* Display name: 'Firefox Mobile' (is it correct to call it ‘Firefox for Android’?)
* Description: Web browser for Android smartphones and tablets
* Display order: 2

Sync:

* Slug: 'sync'
* Display name: 'Sync'
* Description: 'Take your tabs and bookmarks with you across devices'
* Display order: 3

Home:

* Slug: 'home'
* Display name: 'Home' (Firefox Home for iPhone)
* Description: 'Take your tabs and bookmarks to your iPhone'
* Display order: 4

Marketplace:

* Slug: 'marketplace'
* Display name: 'Marketplace'
* Description: 'Download and buy web applications'
* Display order: 5
Bram: That looks fine to me. If you want to give me the details for BrowserID product, that'd be fine, too.

Everyone else: Are the details in comment #9 ok? If not, speak now.
(In reply to Bram Pitoyo [:bram] from comment #9)
> 
> Taking a stab at the description and display order. Feel free to correct if
> I’m wrong.
> 
> Desktop:
> 
> * Slug: 'desktop'
> * Display name: 'Firefox Desktop'
> * Description: Web browser for Windows, Mac and Linux
> * Display order: 1
> 

Shouldn't this be Firefox?
*Slug: firefox
*Display name: Firefox
*Description: Web browser for Windows, Mac and Linux
*Display order: 1

> Mobile:
> 
> * Slug: 'mobile'
> * Display name: 'Firefox Mobile' (is it correct to call it ‘Firefox for
> Android’?)
> * Description: Web browser for Android smartphones and tablets
> * Display order: 2
> 

I believe we can call this "Firefox for mobile" or "Firefox for Android" but not Mobile Firefox, Firefox mobile, etc.

*Slug: mobile
*Display name: Firefox for mobile
*Description: Web browser for Android smartphones and tablets
*Display order: 2


> Sync:
> 
> * Slug: 'sync'
> * Display name: 'Sync'
> * Description: 'Take your tabs and bookmarks with you across devices'
> * Display order: 3
> 

I thought we were going to treat this like a feature not a product? It's also technically switched to be a feature instead of a service internally.


> Home:
> 
> * Slug: 'home'
> * Display name: 'Home' (Firefox Home for iPhone)
> * Description: 'Take your tabs and bookmarks to your iPhone'
> * Display order: 4

Firefox Home is EOL. Should we still include it? If so, how can we name it "Home"? Isn't that a major problem?

*Slug: firefox-home
*Display name: Firefox Home for iPhone
*Description: Access your tabs and bookmarks on your iPhone
*Display order: 3


> 
> Marketplace:
> 
> * Slug: 'marketplace'
> * Display name: 'Marketplace'
> * Description: 'Download and buy web applications'
> * Display order: 5

Won't this be more than just web applications? Also it's not shipping until Q4. We should be prepared to have it in the IA but probably won't be ready at launch.

What about Thunderbird? It looks somewhat unlikely that we'll combine the Thunderbird site with SUMO but should we still list it and link to the Thunderbird site?
Let me clarify something before we get too far off track....

I need to populate the products table with products that currently have kb articles or are getting kb articles in the very near future--let's say in the next month. We can add products at any time after this--we don't have to add all future products now.

We have no kb articles for Thunderbird--so we should add that later.

The current list was pulled from the kb/new page. My assumption is that if the product isn't listed there, we don't have kb articles for it.
(In reply to Will Kahn-Greene [:willkg] from comment #7)
> (In reply to Bram Pitoyo [:bram] from comment #6)
> > 
> > Let’s add one more, which is BrowserID / Persona?
> 
> If we have documents for that product, I'm game for adding it now.
> Otherwise, we should add it later when we need it.
> 
> 

We actually have two documents for this (2000 visits/month total) but it seems hardly worth making this a product yet. It still needs to complete it's name change and nearly nobody (outside of mozilla) uses it.
(In reply to Will Kahn-Greene [:willkg] from comment #12)
> Let me clarify something before we get too far off track....
> 
> I need to populate the products table with products that currently have kb
> articles or are getting kb articles in the very near future--let's say in
> the next month. We can add products at any time after this--we don't have to
> add all future products now.
> 
> We have no kb articles for Thunderbird--so we should add that later.
> 
> The current list was pulled from the kb/new page. My assumption is that if
> the product isn't listed there, we don't have kb articles for it.

the products listed in kb/new are not based on the new IA.

One major problem with the old IA was the lack of Thunderbird documents. We've been talking about moving those over to SUMO but that may not happen given our change of focus (no more paid staff working on TB). Regardless, we'll have to do something about Thunderbird.
Two things:

1. We're not implementing the new IA in one big step. We're implementing pieces and transitioning the existing site piece-by-piece and will end up with the new IA at some glorious point in the future.

2. Sounds like the sumo team needs to come to a consensus on products. Whatever your consensus is, it needs to meet the following two requirements I have:

2.1. I need to be able to map the current set of products in kb/new to whatever the new system is for all the documents in the existing kb.

2.2. I need it soon because this blocks other products-reimplementation bugs in our current sprint.
Ok I talked to Bram, Michelle and Ibai.

(In reply to Will Kahn-Greene [:willkg] from comment #15)
> it needs to meet the following two requirements
> I have:
> 
> 2.1. I need to be able to map the current set of products in kb/new to
> whatever the new system is for all the documents in the existing kb.

Desktop => Firefox
*Slug: firefox
*Display name: Firefox
*Description: Web browser for Windows, Mac and Linux
*Display order: 1

Mobile => Firefox for mobile
*Slug: mobile
*Display name: Firefox for mobile
*Description: Web browser for Android smartphones and tablets
*Display order: 2

All articles "relevant to" Sync and Home should go into both the Firefox and the Firefox for mobile products. We won't have Sync or Home as products anymore.

There are no Marketplace documents at this time.

We will need to start documenting both Firefox OS and Mozilla Marketplace this quarter though.
Pretty sure Ricky pushed this to production earlier today.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.