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

Field changes for the "Mozilla Developer Network" product

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
Administration
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: openjck, Assigned: dkl)

Tracking

Details

(Reporter)

Description

5 years ago
Could you please update the following fields of the Mozilla Developer Network product?

Target Milestones
-----------------
None. Please remove all of the existing milestones.

Versions
--------
None. Please remove all of the existing versions.

Priority
--------
Not sure if this is possible, but it would be great to see only P1, P2, and P3. Don't worry about it unless it's an easy change.

Flags
-----
No plan to use this right now, but could you give a quick description of what this field is all about? Might want to take advantage of it in the future.

Components
----------
Please replace all existing components with the components in this list.

Component:   API
Description: The MDN API.

Component:   Collaboration
Description: Site collaboration. Following users, sending messages between users, etc.

Component:   Dashboards
Description: Dashboard features, types of dashboards, etc.

Component:   Demo Studio / Dev Derby
Description: The Demo Studio platform.

Component:   Design / user experience
Description: Visual design, user experience, usability, information architecture, etc.

Component:   Documentation
Description: Requests for major documentation additions, changes, and reorganizations. Remember that the MDN is a wiki -- you can edit it yourself!

Component:   Editing
Description: Anything that affects site editors. Using the WYSIWYG, moving pages, reverting revisions, etc.

Component:   File attachments
Description: File attachment tools. Requests for file attachments should go under "Documentation".

Component:   KumaScript
Description: The template language of the MDN.

Component:   Landing pages
Description: Anything related to landing pages, such as the homepage and the "Learning" page.

Component:   Localization
Description: Anything that affects localizers. Localization tools, localization workflow, etc.

Component:   Login
Description: Persona integration, authentication workflow, etc.

Component:   Other
Description: Anything else.

Component:   Performance
Description: Anything related to how quickly resources load.

Component:   Security
Description: Features that would enhance security, reports about vulnerabilities, etc. Use the "Security" checkbox if this is a problem that others could harm others.

Component:   SEO
Description: Search engine optimization. Anything related to how well we rank.

Component:   Site search
Description: In-site search. The search algorithm, organizing search results, etc.

Component:   Tags / flags
Description: Adding and removing tags, types of flags, etc.

Component:   User management
Description: Banning users, managing permissions, etc.

Component:   User profiles
Description: Editing profiles, profile features, etc.
(Reporter)

Comment 1

5 years ago
Noticed a couple of typos. The corrected versions are below.

> Component:   File attachments
> Description: File attachment tools. Requests for file attachment uploads should go
> under "Documentation".

> Component:   Security
> Description: Features that would enhance security, reports about
> vulnerabilities, etc. Use the "Security" checkbox if this is a problem that
> could harm others.
(Assignee)

Comment 2

5 years ago
This is not a simple undertaking. The current Mozilla Developer Network has 3179 bugs currently against it. We cannot simply drop all of the components and start with a fresh set as the bugs would have to be reassigned from the old component to the relevant new one. Same with versions. Milestones, the old bugs would just get assigned to the the default milestone all products have, '---'. 

Here is the current component list:

Administration: Requests related to administration of the MDN website (f.e.: user privileges, configuration changes).

Deki Infrastructure: Development or integration of enhancements to any MDN infrastructure based on MindTouch Deki (f.e: extensions, upgrades, or patches).

Demos: For anything related to demos

Docs Platform: For issues related to the MDN Docs section of developer.mozilla.org

Documentation Requests: Requests for major documentation additions or reorganizations. Please do not use bugs for small corrections or additions; edit the wiki instead. No special privileges are required!

Engagement: For anything related to developer engagement activities (f.e.: programs, marketing campaigns, meetups).

Evangelism: For anything related to technology evangelism and community education.

Forums: For issues related to the MDN Forums section of developer.mozilla.org.

Localization: For l10n issues and requests related to the MDN website or programs.

Upload Requests: Use this component to request that files (such as examples and screenshots) be uploaded to MDN.

Website: For issues with features or content on developer.mozilla.org (i.e.: broken links, website copy)

----

Our options are: 

1) create mappings from old component to new related component name and have IT run scripts to migrate bugs for the old component to the new component. 

2) Simply rename the old components name to the new name which keeps the internal ID mapping intact in the Bugzilla database. Problem is that the current bugs may have nothing to do with the new component name and it's interpretation.

3) Keep the old component names intact and create the new ones along side for people to file new bugs into. And then slowly phase out the old component names as their bugs can be moved over to one of the new components. This may cause confusion if one or more of the old component names is too similar to one or more of the new ones. Then we could just do selective renaming similar to option 2).

4) Create an entirely new product from scratch with the new component list and encourage people to use the new product instead. We can disable the old product for new bugs and move it to the Graveyard classification. Downside is that there are probably plenty of bugs in the old product that people may still care about. I imagine they could move those over to the new product if they desire but that may be irritating.

* Flags are used for marking bugs in such a way to be helpful for a release process or to mark a bug as needing some action to be taken such as an approval or code review.

dkl
(Reporter)

Comment 3

5 years ago
Thanks for the detailed response.

Versions: Moving everything into "--" is fine. Practically all open bugs use the "Kuma" version, which is now essentially just our codename for the product. Any bugs using other versions are either closed or will be closed soon.

Milestones: If the existing milestones are going to be lost, I would prefer that we just leave Milestones field untouched. It might confuse some users, but it's worth it to keep old search results intact.

Components: Option 2 sounds good. We need to sort through all of our open bugs anyway (hence the new organization) so it will be fine if some bugs are a slightly the wrong component. See my rename mapping below.

Administration => User management
Deki Infrastructure => Other
Demos => Demo Studio / Dev Derby
Docs Platform => Editing
Documentation Requests => Documentation
Engagement => Other
Evangelism => Other
Forums => Other
Localization => Localization (with new description)
Upload Requests => Documentation
Website => Landing pages
(Assignee)

Comment 4

5 years ago
(In reply to John Karahalis [:openjck] from comment #3)
> Thanks for the detailed response.
> 
> Versions: Moving everything into "--" is fine. Practically all open bugs use
> the "Kuma" version, which is now essentially just our codename for the
> product. Any bugs using other versions are either closed or will be closed
> soon.

Ok. So I will then renamed 'Kuma' to unspecified and move whatever is left over to that version. Deleting the rest.

> Milestones: If the existing milestones are going to be lost, I would prefer
> that we just leave Milestones field untouched. It might confuse some users,
> but it's worth it to keep old search results intact.

I will leave milestones alone then.
 
> Components: Option 2 sounds good. We need to sort through all of our open
> bugs anyway (hence the new organization) so it will be fine if some bugs are
> a slightly the wrong component. See my rename mapping below.
>
> Administration => User management
> Deki Infrastructure => Other
> Demos => Demo Studio / Dev Derby
> Docs Platform => Editing
> Documentation Requests => Documentation
> Engagement => Other
> Evangelism => Other
> Forums => Other
> Localization => Localization (with new description)
> Upload Requests => Documentation
> Website => Landing pages

Since some of them are going to end up in the same new component (Documentation, Other),
I will still need to get IT to move some bugs for me using special scripts on the server.
This is because I can't technically rename more than one component to the same new name. 
So we will pick the one with the most bugs, rename it and move the others appropriately.

To be clear you want this to take effect immediately or should time be taken to notify others of the coming change?

dkl
(Reporter)

Comment 5

5 years ago
> This is because I can't technically rename more than one component to the
> same new name.

Yep. Hadn't thought of that.

> So we will pick the one with the most bugs, rename it and move the others
> appropriately.

Sounds good.

> To be clear you want this to take effect immediately or should time be taken
> to notify others of the coming change?

Immediately is fine.
(Reporter)

Comment 6

5 years ago
Just a friendly ping. Any status on this?
(Assignee)

Comment 7

5 years ago
Sorry for any delay this has caused. I am working on this today and had to write a script to do the moving of bug versions as we do not want to necessarily spam everyone for a version change. The script is done and once it tests ok, I will get the IT staff to run the script on the production systems hopefully today. I will create a full list of scripts to run on this bug and move it over to the server ops product.

Thanks
dkl
(Reporter)

Comment 8

5 years ago
Sounds great!
(Assignee)

Comment 9

5 years ago
glob, can you do a quick look over of the new version of moveversion.pl. It works in my testing but always better to have a second set of eyes on it.

http://bzr.mozilla.org/bmo/4.0/annotate/head:/contrib/reorg-tools/moveversion.pl

Thanks
dkl
(Assignee)

Comment 10

5 years ago
Adding in the steps that need to be taken here for when I move over to IT:

Stage 1: (Me)

1. Create new components: 
   Other
   Documentation
   User management
   Demo Studio / Dev Derby
   Editing
   Landing pages 

Stage 2: (Admins)

1. # perl contrib/reorg-tools/moveversion.pl "Mozilla Developer Network" Deki unspecified doit
2. # perl contrib/reorg-tools/moveversion.pl "Mozilla Developer Network" Kuma unspecified doit
3. # perl contrib/reorg-tools/moveversion.pl "Mozilla Developer Network" MDN unspecified doit

4. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Deki Infrastructure" "Mozilla Developer Network" "Other" 
5. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Documentation Requests" "Mozilla Developer Network" "Documentation" 
6. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Administration" "Mozilla Developer Network" "User management"
7. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Demos" "Mozilla Developer Network" "Demo Studio / Dev Derby"
8. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Platform" "Mozilla Developer Network" "Editing"
9. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Website" "Mozilla Developer Network" "Landing pages"

Stage 3: (Me)

1. Delete versions Deki, Kuma, and MDN.

2. Manually move bugs with Engagement => Other
3. Manually move bugs with Evangelism => Other
4. Manually move bugs with Forums => Other
5. Delete Deki Infrastructure, Engagement, Evangelism, and Forums

6. Manually move bugs with Upload Requests => Documentation
7. Delete Documentation Requests and Upload Requests

8. Change description of Localization => Localization (with new description)

Thinks to be aware of:

1. This all will possibly invalidate a lot of stored queries that users will need to update.
2. The new component names will have new watch users so people will need to update component watching.

dkl
(Assignee)

Comment 11

5 years ago
(In reply to David Lawrence [:dkl] from comment #10)
> Adding in the steps that need to be taken here for when I move over to IT:
> 
> Stage 1: (Me)
> 
> 1. Create new components: 
>    Other
>    Documentation
>    User management
>    Demo Studio / Dev Derby
>    Editing
>    Landing pages 

I have create all of the components needed (plus the extras from comment 0 not mentioned above).

Moving now to the administrative product so the Admins can perform the tasks below

> Stage 2: (Admins)
> 
> 1. # perl contrib/reorg-tools/moveversion.pl "Mozilla Developer Network"
> Deki unspecified doit
> 2. # perl contrib/reorg-tools/moveversion.pl "Mozilla Developer Network"
> Kuma unspecified doit
> 3. # perl contrib/reorg-tools/moveversion.pl "Mozilla Developer Network" MDN
> unspecified doit
> 
> 4. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Deki
> Infrastructure" "Mozilla Developer Network" "Other" 
> 5. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network"
> "Documentation Requests" "Mozilla Developer Network" "Documentation" 
> 6. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network"
> "Administration" "Mozilla Developer Network" "User management"
> 7. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network"
> "Demos" "Mozilla Developer Network" "Demo Studio / Dev Derby"
> 8. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network"
> "Platform" "Mozilla Developer Network" "Editing"
> 9. # perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network"
> "Website" "Mozilla Developer Network" "Landing pages"

Admin, once the above is complete, please move the bug back to "bugzilla.mozilla.org/Administration" so we can complete the remainder below.

> Stage 3: (Me)
> 
> 1. Delete versions Deki, Kuma, and MDN.
> 
> 2. Manually move bugs with Engagement => Other
> 3. Manually move bugs with Evangelism => Other
> 4. Manually move bugs with Forums => Other
> 5. Delete Deki Infrastructure, Engagement, Evangelism, and Forums
> 
> 6. Manually move bugs with Upload Requests => Documentation
> 7. Delete Documentation Requests and Upload Requests
> 
> 8. Change description of Localization => Localization (with new description)

Note: Went ahead and did this too ^^^
 
dkl
Assignee: nobody → server-ops-devservices
Component: Administration → Server Operations: Developer Services
Product: bugzilla.mozilla.org → mozilla.org
QA Contact: shyam
Version: Production → other
Had a fail on 8. The rest were fine. Do you want me to re-run 8 as something else? 

[root@pp-app-bugs02 bugzilla.mozilla.org]# perl /contrib/reorg-tools/moveversion.pl "Mozilla Developer Network" Deki unspecified doit
Can't open perl script "/contrib/reorg-tools/moveversion.pl": No such file or directory
[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/moveversion.pl "Mozilla Developer Network" Deki unspecified doit
About to move the version from 
From 'Mozilla Developer Network / Deki'
To 'Mozilla Developer Network / unspecified'
for 116 bugs ...

Press <Ctrl-C> to stop or <Enter> to continue...

Moving version from 'Mozilla Developer Network / Deki to 'Mozilla Developer Network / unspecified' ...

[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/moveversion.pl "Mozilla Developer Network" Kuma unspecified doit
About to move the version from 
From 'Mozilla Developer Network / Kuma'
To 'Mozilla Developer Network / unspecified'
for 1149 bugs ...

Press <Ctrl-C> to stop or <Enter> to continue...

Moving version from 'Mozilla Developer Network / Kuma to 'Mozilla Developer Network / unspecified' ...

[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/moveversion.pl "Mozilla Developer Network" MDN unspecified doit
About to move the version from 
From 'Mozilla Developer Network / MDN'
To 'Mozilla Developer Network / unspecified'
for 666 bugs ...

Press <Ctrl-C> to stop or <Enter> to continue...

Moving version from 'Mozilla Developer Network / MDN to 'Mozilla Developer Network / unspecified' ...

[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Deki Infrastructure" "Mozilla Developer Network" "Other"
About to move 370 bugs
From 'Mozilla Developer Network' : 'Deki Infrastructure'
To 'Mozilla Developer Network' : 'Other'

Press <Ctrl-C> to stop or <Enter> to continue...

Moving 370 bugs from Mozilla Developer Network:Deki Infrastructure to Mozilla Developer Network:Other
[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Documentation Requests" "Mozilla Developer Network" "Documentation"
About to move 642 bugs
From 'Mozilla Developer Network' : 'Documentation Requests'
To 'Mozilla Developer Network' : 'Documentation'

Press <Ctrl-C> to stop or <Enter> to continue...

Moving 642 bugs from Mozilla Developer Network:Documentation Requests to Mozilla Developer Network:Documentation
[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Administration" "Mozilla Developer Network" "User management"
About to move 80 bugs
From 'Mozilla Developer Network' : 'Administration'
To 'Mozilla Developer Network' : 'User management'

Press <Ctrl-C> to stop or <Enter> to continue...

Moving 80 bugs from Mozilla Developer Network:Administration to Mozilla Developer Network:User management
[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Demos" "Mozilla Developer Network" "Demo Studio / Dev Derby"
About to move 116 bugs
From 'Mozilla Developer Network' : 'Demos'
To 'Mozilla Developer Network' : 'Demo Studio / Dev Derby'

Press <Ctrl-C> to stop or <Enter> to continue...

Moving 116 bugs from Mozilla Developer Network:Demos to Mozilla Developer Network:Demo Studio / Dev Derby
[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Platform" "Mozilla Developer Network" "Editing"
Can't find component ID for 'Platform'.
[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Website" "Mozilla Developer Network" "Landing pages"
About to move 1401 bugs
From 'Mozilla Developer Network' : 'Website'
To 'Mozilla Developer Network' : 'Landing pages'

Press <Ctrl-C> to stop or <Enter> to continue...

Moving 1401 bugs from Mozilla Developer Network:Website to Mozilla Developer Network:Landing pages
Assignee: server-ops-devservices → shyam
Failed :

[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Platform" "Mozilla Developer Network" "Editing"
Can't find component ID for 'Platform'.

Updated

5 years ago
Assignee: shyam → nobody
Component: Server Operations: Developer Services → Administration
Product: mozilla.org → bugzilla.mozilla.org
QA Contact: shyam
it should be "Docs Platform":

perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Docs Platform" "Mozilla Developer Network" "Editing"
(In reply to Byron Jones ‹:glob› from comment #14)
> it should be "Docs Platform":
> 
> perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Docs
> Platform" "Mozilla Developer Network" "Editing"

Done.

[root@pp-app-bugs02 bugzilla.mozilla.org]# perl contrib/reorg-tools/movebugs.pl "Mozilla Developer Network" "Docs Platform" "Mozilla Developer Network" "Editing"
About to move 512 bugs
From 'Mozilla Developer Network' : 'Docs Platform'
To 'Mozilla Developer Network' : 'Editing'

Press <Ctrl-C> to stop or <Enter> to continue...

Moving 512 bugs from Mozilla Developer Network:Docs Platform to Mozilla Developer Network:Editing
> 1. Delete versions Deki, Kuma, and MDN.
deleted.

> 2. Manually move bugs with Engagement => Other
moved.

> 3. Manually move bugs with Evangelism => Other
moved.

> 4. Manually move bugs with Forums => Other
moved.

> 5. Delete Deki Infrastructure, Engagement, Evangelism, and Forums
deleted.

> 6. Manually move bugs with Upload Requests => Documentation
moved.

> 7. Delete Documentation Requests and Upload Requests
deleted.
Assignee: nobody → dkl
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Reporter)

Comment 17

5 years ago
Thanks for all the hard work on this. Everything looks great.
You need to log in before you can comment on or make changes to this bug.