I am talking about kubernetes, yes. To quote @bd808, "the PORT env var should still be set". $PORT used to work few months ago, without me setting it. It seems to be unset recently.

@Majavah at the very top you would see "Open access". See the first screenshot.

Seems to be working now.

Thank you @Jdlrobson. I will have a look.

@Jdlrobson I was asking for en.wikinews.

Can anyone please share a before-and-after photos of what has changed? Thank you.

hq.eso.org is a sub-domain of ESO. The copyright notice page clearly states "Unless specifically noted, the images, videos, and music distributed on the public ESO website, along with the texts of press releases, announcements, pictures of the week, blog posts and captions, are licensed under a Creative Commons Attribution 4.0 International License"

@Trizek-WMF That dashboard helps knowing what kind of changes were made recently, knowing which articles needs expansion/peer review/protection … Since different projects implements these things in different way, I suggest to provide an option to set it uncollapsed by default … and as you have mentioned, one can choose what to do with it, and it will be saved, so just a simple by default uncollapse would solve the issue.

@Trizek-WMF: the “more compact design” makes it harder for newbies to contribute. It hides one of the most crucial templates which contains everything from links to project policies, RFA, RFP, DR and articles to review.

I assume this task changed the appearance of recent changes. However, on English Wikinews, there is an important template which is now collapsed by default and the label reads "Other review tools" even when the tasks mentioned in that template are not limited to reviewers. Admins, or even normal users can make use of it. However, if the label says review tools, it is less likely to be clicked, and hence, it is counter productive. The Tech News says users can opt-out for the new filters. Instead of opting-out, it should be not there by default and let the users opt-in for it. Else, it hide crucial links for everyone -- moreover, anonymous editors would not be able to opt-out.

In T172256#3510928, @Aklapper wrote:

Phab is the correct place for tracking and planning the actual performance of such a technical task.
Whether the task should be performed should be discussed and agreed on on-wiki, preferably before creating the task.

Phab isn't the best place for this task.

I would rather like a logo which won't make me wonder if it was UN's logo or Wikinews'. Just because it was not updated for years is not good enough to update adding shadows or complex gradients.

@Shizhao Because I do not agree to the terms and conditions. Besides, we do not know if that bot shares the logs publicly -- apparently WMF related channels do not allow public logging on public channels even though this is not their server.

@bd808 So, what should I do if I want to choose kubernetes. (By the way, if phabricator the correct place to discuss about project request?)

@bd808 I am already running the teleirc bot based on node.js locally on my machine.

@Piramidion It happens a) everytime VE is selected, and after it loads, cancelled by pressing Escape and clicking on Edit Source b) randomly when Edit Source is clicked.

@TheDJ, T165132 is due to the New Editor which I did not enable. I am facing this issue when I try to use the old editor.

@Piramidion, note that the task T165236 happens for the 2017 wikitext editor while I have not selected that feature and I am still experiencing this issue.

I can explain why Wiki Markup is something MediaWiki should not discard, its advantages and user convenience, but this is not the correct place to.
It is on the developers what they want to do.
There are so many important tools which should have been in existence years ago like semi-automated assistance to edit articles, but were never discussed.

@Dinoguy1000 Thanks for your comment, but was already discussed on IRC about it. I am aware of What You See Is What You Get - but in my project, I wanted to integrate the Wiki Markup but that should not be the only way to format the text.

Now here is the part: Using the Wiki Markup in the email is not entirely HTML email. And that is what I wanted to do - but then, instead of using the markup, I wanted to make things easier. Just like the Bold Italics and other formatting options available in the comment box, I wanted that for email. Preferably with keyboard shortcuts. HTML Email provides a greater degree of customisation something that will be too much instead of Wiki Markup when two users are communicating via email this user feature.

I had already discussed with a Wikimedian about why "RTF" was not the most suitable word. I had modified my proposal accordingly. Well, GSoC's selected participants were announced. So this discussion is for anyone who wants to know what they should focus on.

@zhuyifei1999, I need a project. I was told to create a project by another user who runs the bot for Chinese Wikiprojects. That user asked me to use Labs for login purpose only. I don't know what is the best practice. The code is ready, I need to host it.

In a nutshell: HTML email gives a lot of option and it can be easily misused to spam and annoy lot of Wikimedians.

@Aklapper
RTF is not an email format. But RTF offers features like underlined, bold, and italicised text. Other features like hyperlink, bullet list, numbering, text alignment, et cetera (<Screenshot>)

@Aklapper RTF is a proprietary file format, which has the features like bold, italics, underline and hyperlink. I did not say HTML formatting because an HTML email is a different concept, and that shifts the focus of the project.