We've renamed the product landing in Firefox as "Firefox Screenshots" We'd like to do a bit of cleanup to our existing Discourse channels: - https://discourse.mozilla-community.org/c/test-pilot/page-shot-dev - https://discourse.mozilla-community.org/c/test-pilot/page-shot Questions - Can we just rename the categories and save the data? If so, would it create an alias so the old name will link to the new name? - If we wanted to, could we move these into their own community? e.g. firefox-screenshots/dev and firefox-screenshots/product-discussions /cc ian/jared/john/wil for any more input
(In reply to Cory Price [:ckprice] from comment #0) > - Can we just rename the categories and save the data? If so, would it > create an alias so the old name will link to the new name? Yep, topics don't have a category-specific url, and we can set up a redirect from /c/test-pilot/page-shot(-dev) to wherever we want. > - If we wanted to, could we move these into their own community? e.g. > firefox-screenshots/dev and firefox-screenshots/product-discussions Yeah, although I would rather we moved page-shot to firefox-screenshots, and page-shot-dev to firefox-screenshots/dev.
> … we can set up a redirect … If I recall correctly (from recent administration of Discourse for Open Source Design): when a category's slug is changed, there's no need to set up a redirect; redirection occurs automatically. I _assume_ that things are similarly automated if you move a subcategory from one category to another.
> I _assume_ that things are similarly automated if you move a subcategory from one category to another. Last time I did a move like this, they weren't automated - don't know if that's changed now. But setting up the redirects manually is very easy. > - If we wanted to, could we move these into their own community? > Yeah, although I would rather we moved page-shot to firefox-screenshots, and page-shot-dev to firefox-screenshots/dev. Revisiting this, I'm not sure we necessarily want to do this - putting Firefox Screenshots in a top level category - on our end. That's not to say we don't, I just have a few more questions: cory/ian/jared/john/wil: how do you see the discussion around Page Shot changing as it turns into Firefox Screenshots? Is it still going to exist as an independent project within Firefox, under your stewardship, or will it get passed onto another team? Will it release independently of Firefox? Will discussion of it still shape its development, or is it considered "done"? And is the same going to be roughly true of all experiments graduating Test Pilot?
Flags: needinfo?(cbkprice) → needinfo?(wclouser)
It's currently remaining under the Test Pilot umbrella with no concrete plans to move to another team, although the discussions are there. If it helps, consider that we are still in the "Graduation" phase of the project -- we're in Firefox, and analyzing usage data, and ensuring it's bringing value to GA Firefox users. Up to this point it has only had an opt-in audience. I don't consider it done. We don't have a one-size-fits-all solution to experiments graduating. It will have to be something we figure out for each experiment, or at least enough that we have a similar previous project. I don't expect projects which graduate into Firefox to veer widely from this path though.
Thanks for those answers. Would you be happy with a rename and redirection, while keeping the two categories under the Test Pilot parent category, then? So, something like this: "Firefox Screenshots": /c/test-pilot/firefox-screenshots "Firefox Screenshots Dev": /c/test-pilot/firefox-screenshots-dev We can also make them Firefox Orange, and everything.
I think that's fine. Kind of seems like we could just drop the -dev category. Ian: do we need -dev?
Flags: needinfo?(wclouser) → needinfo?(ianb)
Let's remove the -dev group
Righto, done: https://discourse.mozilla.org/c/test-pilot/firefox-screenshots https://discourse.mozilla.org/c/archives/test-pilot-page-shot-dev
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.