Closed Bug 1841816 Opened 3 years ago Closed 3 years ago

Add link to mastodon feed before twitter feed in nightly release notes

Categories

(www.mozilla.org :: L10N, enhancement)

Development/Staging
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: manuel, Assigned: CocoMo)

Details

Attachments

(1 file)

https://www.mozilla.org/en-US/firefox/117.0a1/whatsnew/?oldversion=116.0a1 links to a twitter feed. We should at least link to our mastodon feed before the twitter one https://mozilla.social/@FirefoxNightly. We could also replace the twitter link with our mastodon link ;).

Summary: Add link to mastadon feed before twitter feed in nightly release notes → Add link to mastodon feed before twitter feed in nightly release notes

This is not related to release notes, this is an in-product loaded regular page, changing component. I already added the mastodon account to our Nightly release notes https://www.mozilla.org/en-US/firefox/nightly/notes/

Agreed on this, I think we already have a bug filed somewhere about it.

I would not be in favor of removing the Twitter link, we have 26.5k followers on this account, we lost 500 maybe in the last year, these people report bugs and give valuable feedback that help our development. We have 375 followers on mastodon, most of them apparently mozilla employees.

The difficulty is of course not updating the page but updating the page in the 100 languages we support and updating other sections of this page while we are at it (we created this content in 2016 and tried to make it as future proof as possible :) ).

I am tentatively assigning myself to the bug for h2, I will unasssign if I see that I don't have time for it.

Component: Release notes → Pages & Content
Assignee: nobody → pascalc
Type: task → enhancement

The fix is merged to the main branch. After it is deployed, the English version of the page will have the additional mastodon link while localized versions will fallback to the current sentence. The updated string for localized versions will go to production gradually as localizers get to it.

Marking fixed!

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

Reopening and moving to the L10n sub-component.
Although we got many translations already on production, our top locales never got updated, it seems that for them the process is out of automation and managed manually with external agencies. Assigning to you Peying.

Thanks.

Assignee: pascalc → pmo
Status: RESOLVED → REOPENED
Component: Pages & Content → L10N
Flags: needinfo?(pmo)
Resolution: FIXED → ---

Translation request sent.

Flags: needinfo?(pmo)
Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: