@Florian I'm not currently working on this. You may use this as a Gooogle-code-in task. :)

You are welcome to work on the task, since i am not working on it right now :)

@Gopavasanth the new tab which contains the newly generated video also have the download option in the player. Also, the file can be downloaded directly from the download button by right-clicking on it and choosing the save link as option. I couldn't find any way to resolve it through front end.

@Gopavasanth I think the problem in the link is the same as in this question https://stackoverflow.com/questions/50694881/how-to-download-file-in-react-js and thus can't be resolved by changing code in the front end, what do you think?

In T232296#5560234, @Gopavasanth wrote:

Hi @Nikitrain, did you reproduce the bug locally?

Hey @Gopavasanth need a little guidance here I am unable to figure out what's causing the button to misbehave can you maybe guide me where should I look

I would like to work on this.

hi! I would like to work on this task. Can you also post some screenshots of the problem or maybe some link where I can see the issue?

Since I haven't heard from anyone from release eng team. I am withdrawing this proposal.

@TerraCodes @Aklapper Can I add this as a Google Summer of Docs task. would love to complete this.

@srishakatux I have been waiting for @mmodell's feedback. Since he is in the release engineering team he can give expert feedback about the usefulness and timeline. I can add some more tasks after that.

@Aklapper waiting for your reply about the time the project will take, how much time do you think it should ideally take?

... While I think this would be nice to have, if I understand the scope correctly, I don't see how doing this would take three months...?

If we improve the documentation at mediawiki.org then we also need to change docs in HISTORY as well. As I can comprehend four pages and four Gerrit patch will take a week, so three months in total.

The release notes also do not follow the same template.

Why is that a problem? What is the actual underlying problem which would be solved by following the same template?

Documentation following a template is easy to navigate and use. It isn't a problem that they do not follow a template but I think it would be better if they did, following a well-structured template can help organise the information in a better way such that it is easily found. Also in my view, well-organised documentation is easy on the eyes.

There is also a repetition of release notes in the documentation of earlier versions.

Could you elaborate? Where can I see what kind of repetition?

You can see repitition in these release notes documentation for version 1.2 and version 1.1

Hey! @mmodell here's the first draft of my proposal, would love some feedback :)

Thanks for the info! I will keep that in mind for future tasks.

@ashley Bouquet doesn't contain any file named mediawiki.special.styles.css, although it does contain special.preferences.styles.css. Should I move special.preferences.styles.css to resources/skinStyles .

Thanks! for the detailed explanation, working with it :)
in skin Refreshed it contains refreshed/refreshed/extensions so I need to make a new folder for extension in Bouquet which will contain style file for AdvancedSearch

I have cloned the repo, I am working on it. As I gathered from the task description, this task is about adding https://wikibase-registry.wmflabs.org/wiki/Main_Page
in the "Projects Powered by Wikibase" sidebar on http://wikiba.se/. Correct me if I'm wrong

In T205177#5071807, @Aklapper wrote:

@Nikitrain: Please see the previous patch above and investigate.

@Aklapper I did see the previous patch. The previous patch is wrong that's what @ashley said in the comment. The patch is provided for the wrong file and now I can't figure out where to provide the new patch.

@ashley Sorry, I'm confused, if it isn't ideal to edit the CSS file of the skin then how am I supposed to fix this. I don't have any experience with resource loader, although I do have some experience with CSS. Where am I supposed to edit the CSS file? Can you please guide me a bit more? Thanks! :)

If this task is still unresolved then I would like to work on this. Can this be assigned to me?

when I see qqq.json it already has
"citoid-citefromiddialog-search-placeholder": "{{doc-important|Do not translate example.com as it is a domain name specifically reserved by IANA for examples.}}\n\nPlaceholder for the URL/DOI/PMCID/PMID/ISBN search field.",
Should I still edit the message.

In T218564#5069340, @Mvolz wrote:

In T218564#5069284, @Nikitrain wrote:

@Mvolz I have opened a pull request.
and include this note at the end of the qqq.json file
/*
Note for translators: Do not translate the search-placeholder domain name ("http://www.example.com").
http://www.example.com is a reserved domain intended to be used as a placeholder and should not be translated.
*/

Thanks for the feedback! on it ! is anything else needed to be done other than this?
It should go in the message in qqq, not as a comment. But the text is fine (although you don't need the note for translators bit as this is implied, since qqq is basically a file with notes for translators!)

@Mvolz I have opened a pull request.
and include this note at the end of the qqq.json file
/*
Note for translators: Do not translate the search-placeholder domain name ("http://www.example.com").
http://www.example.com is a reserved domain intended to be used as a placeholder and should not be translated.
*/

Seeing the jv.json file on git hub. I noticed that file contain
"citoid-citefromiddialog-search-placeholder": "conto http://www.example.com",
instead of
"citoid-citefromiddialog-search-placeholder": "http://www.example.com",
Is this how this is needed to be fixed?

I am interested in this task. One query, Where should the Note be included, in the beginning, end or someplace else?

All of the Release Notes for all of the versions have been completed in HISTORY by these patches.