VPN Android - Early Access (Phase 0) Release.
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: nfurlan, Assigned: ffloare)
Details
Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]
**Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content **
IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.
Content access restriction: Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]
Note: If yes, ensure ‘Advanced Fields’ are visible by selecting ‘Show Advanced Field’ at the top right, then scroll to ‘Security’ and check ‘Confidential Mozilla Employee Bug (non-security)’.
NO
Attention: Any content not marked as confidential will be accessible to both NDAd and non-NDAd contributors with a Bugzilla account. Drafts for non-confidential content will also follow the same access policy, being open to comments for anyone with the link. Non-confidential Bugzillas can benefit from contributions by community contributors, while confidential Bugzillas will be handled exclusively by staff.
Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)
Choose one below and delete others. [REQUIRED]
Firefox for Android
Select the type of request.
Choose one or more below and delete others. [REQUIRED]
New content
Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED]
- We are launching a new VPN integration inside Firefox Android (This is an early access version that will require FX accounts login)
##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]
**Note: Specify if the user-facing changes mentioned above are final, experimental, or in beta. This information is crucial for determining the appropriate support and documentation level needed. Please note that SUMO KB articles only support the production version for Firefox.
- Rollout via Nimbus in Fx 151.
Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]
**Note: Please confirm if these features or changes are limited to specific geographic regions and if they will be implemented gradually. Knowing this helps us tailor our documentation and support resources appropriately.
- US, France, Germany and UK.
Please indicate if this is an on- or off-train release [REQUIRED]
**Note: If applicable, add the product version number to the end of the Summary field using the format: Summary [Product V123]. If this is an off-train release, please use the format: Summary [Product off-train].
- On Train
What is the anticipated release date? [REQUIRED]
Note: Content is typically published at, or within, 48 hours of the release.
- Fx 151 release date.
Does the content need to be published prior to the release date? If so, when? [REQUIRED]
Note: If you don’t let us know if this date changes, it will be published on this date
- No need.
Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]
Note: A minimum of 10 days is required for translation requests.
- In the other countries where the VPN will be available.
Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]
https://mozilla-hub.atlassian.net/browse/FXDROID-6776
Please include links to any design assets, visuals, figma files, etc. [REQUIRED]
Note: Ensure to submit only final visual assets relevant to the Production release, excluding Nightly or Beta images, and favor 'Light mode' UI screenshots over 'Dark mode'
https://www.figma.com/design/kfvRkMYIRGNu075LN14aW5/VPN-for-Android?node-id=2-2162&t=bgNvvNoREaG7B0pn-0
Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]
https://docs.google.com/document/d/1aACkw6GA5XnJQ5kky4dnCzAoFsoHl3iYcN-GvIFz7BU/edit?tab=t.0 (See Phase 0)
Does the content need approval before publishing? If yes, identify the one approver responsible for this task.
Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]
Updated•4 months ago
|
Comment 1•4 months ago
|
||
Joe, do we have an Asana ticket for this already?
Asana Link: https://app.asana.com/1/90589597529/project/1203460865189761/task/1214066484474672?focus=true
| Assignee | ||
Comment 3•4 months ago
|
||
| Assignee | ||
Comment 4•3 months ago
|
||
| Assignee | ||
Updated•3 months ago
|
| Assignee | ||
Comment 5•1 month ago
|
||
| Assignee | ||
Updated•1 month ago
|
In this article, the tags and the summary seem to have been swapped.
Comment 7•1 month ago
•
|
||
(In reply to Mozinet from comment #6)
In this article, the tags and the summary seem to have been swapped.
By "tags" I think you meant "keywords". I submitted a revision that's pending review, to fix the summary and to remove all of the unneeded keywords (ref.: https://support.mozilla.org/en-US/kb/when-and-how-to-use-keywords). See https://support.mozilla.org/en-US/kb/mobile-android-vpn/history
Comment 8•5 days ago
•
|
||
(In reply to Flavius Floare from comment #5)
Live here: https://support.mozilla.org/en-US/kb/mobile-android-vpn
The KB URL https://support.mozilla.org/en-US/kb/mobile-android-vpn (which has the title Use built-in VPN in Firefox for Android based on a Google search) is now a Page Not Found for me. Is the article now restricted? Should this bug be reopened or resolved as WONTFIX or INACTIVE?
P.S. See https://support.mozilla.org/en-US/kb/article-maintenance/discuss/15385 for more information and a request for documentation when access to existing KB articles is restricted.
| Assignee | ||
Comment 9•4 days ago
|
||
(In reply to Alice Wyman from comment #8)
(In reply to Flavius Floare from comment #5)
Live here: https://support.mozilla.org/en-US/kb/mobile-android-vpn
The KB URL https://support.mozilla.org/en-US/kb/mobile-android-vpn (which has the title Use built-in VPN in Firefox for Android based on a Google search) is now a Page Not Found for me. Is the article now restricted? Should this bug be reopened or resolved as WONTFIX or INACTIVE?
P.S. See https://support.mozilla.org/en-US/kb/article-maintenance/discuss/15385 for more information and a request for documentation when access to existing KB articles is restricted.
Yes, the article has been restricted for now. I don't think we should reopen the bug, as its main goal - that of creating and publishing the article - has been accomplished.
Comment 10•4 days ago
|
||
(In reply to Flavius Floare from comment #9)
(In reply to Alice Wyman from comment #8)
(In reply to Flavius Floare from comment #5)
Live here: https://support.mozilla.org/en-US/kb/mobile-android-vpn
The KB URL https://support.mozilla.org/en-US/kb/mobile-android-vpn (which has the title Use built-in VPN in Firefox for Android based on a Google search) is now a Page Not Found for me. Is the article now restricted? Should this bug be reopened or resolved as WONTFIX or INACTIVE?
P.S. See https://support.mozilla.org/en-US/kb/article-maintenance/discuss/15385 for more information and a request for documentation when access to existing KB articles is restricted.
Yes, the article has been restricted for now. I don't think we should reopen the bug, as its main goal - that of creating and publishing the article - has been accomplished.
Can you at least let contributors know why the article has been restricted and for how long you think it will be inaccessible to the public? See https://support.mozilla.org/en-US/kb/article-maintenance/discuss/15385 ... Links to the article have been included in a number of support forum threads and are now a "Page Not Found".
| Assignee | ||
Comment 11•4 days ago
|
||
(In reply to Alice Wyman from comment #10)
(In reply to Flavius Floare from comment #9)
(In reply to Alice Wyman from comment #8)
(In reply to Flavius Floare from comment #5)
Live here: https://support.mozilla.org/en-US/kb/mobile-android-vpn
The KB URL https://support.mozilla.org/en-US/kb/mobile-android-vpn (which has the title Use built-in VPN in Firefox for Android based on a Google search) is now a Page Not Found for me. Is the article now restricted? Should this bug be reopened or resolved as WONTFIX or INACTIVE?
P.S. See https://support.mozilla.org/en-US/kb/article-maintenance/discuss/15385 for more information and a request for documentation when access to existing KB articles is restricted.
Yes, the article has been restricted for now. I don't think we should reopen the bug, as its main goal - that of creating and publishing the article - has been accomplished.
Can you at least let contributors know why the article has been restricted and for how long you think it will be inaccessible to the public? See https://support.mozilla.org/en-US/kb/article-maintenance/discuss/15385 ... Links to the article have been included in a number of support forum threads and are now a "Page Not Found".
Thanks for flagging this and for looking into it.
The visibility of the VPN article was restricted following a request from the product team responsible for the feature. This wasn't a decision I made independently, and I don't want to speculate about the product or release considerations behind the request since I may not have the full context.
Regarding whether changes to article visibility should always be documented in the contributor forum, I think that's a broader process question that would benefit from input from the rest of the SUMO team and community rather than something I should decide on my own. I'm happy to help clarify what happened with this particular article, but I'd prefer to leave any changes to the overall process open for discussion.
Thanks for raising the concern.
Comment 12•4 days ago
|
||
Thanks, Flavius. I'll leave it up to the SUMO team and/or another community member to start a discussion about why this particular article is no longer accessible ("Page Not Found") and whether staff should document (in some way) when access to any published article is removed.
I also set up a Needs change entry in the Content maintenance and management article that covers restricting visibility to Add a documentation requirement when an existing KB article's visibility is restricted.
Comment 13•3 days ago
|
||
(In reply to Alice Wyman from comment #12)
I also set up a Needs change entry in the Content maintenance and management article that covers restricting visibility to Add a documentation requirement when an existing KB article's visibility is restricted.
Just closing the loop here. Alice, let's continue discussion about this in the article discussion thread.
Description
•