@Dereckson: Is this still a valid task, now that GSoC 2017 and Outreachy 14 are over? Or has this happened? (And if not, should this be moved to Outreachy 15?)

I assume this task has served its purpose, hence closing.

New developers arriving to our community need to be aware that they can use https://discourse-mediawiki.wmflabs.org/ to ask all their questions.

Please move "me too" / "UI bad" / "UI good" / "I don't like XYZ" / "+1!"s on Gerrit or Phabricator to the talk page on-wiki instead of posting them here. Thanks.

In T184442#3886988, @Baloch007 wrote:

What we need to add anything else? Aklapper:)

Adding Bug: T184504 as the last line in the commit message would be welcome :)

In T173537#3886549, @Paladox wrote:

I think this issue may be affecting @Zoranzoki21 who reported this on irc.

Not only, also in T183980. (Which might turn out to be a duplicate?)

@awight: Maybe patch-welcome as that has a more vague definition?

Would this be fixed by fixing T158572: Explore how to make a category search that includes sub-categories. ? If so I'd mark this as a duplicate...

Please do. Any code changes should be proposed and discussed in Gerrit... :)

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description and your own comment in T169843#3410396 I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current task description with its huge unclear scope only listing "potential views" I am removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description (no idea what is "a 600 orphan", for example) I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

In T97159#3101902, @amritsreekumar wrote:

as this bug had already disappeared due to a regression.

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current short task description I'm removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@awight: good first task tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. As per the last comments and due to the short task description which does not define what is the problem and what is wanted instead I am removing the good first task tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

@N0rthway: Which change? Please link to a proposed change in Gerrit. Thanks!

Nothing secret here as far as I can tell, hence removing Security and task access restrictions

@Dheerajmalisetty: If you have specific questions about MediaWiki architecture or specific code places (which ones?) of the MediaWiki parser code base, feel free to ask them. This task is not an good first task task to fix, and to know more you'll have to investigate the code base.

@Dheerajmalisetty: You have been asked several times to please ask specific questions in tasks. "Can I get more info?" questions are neither specific nor useful.
See the task description and previous comments in this task for more information. If that is not enough information then you need to be specific and clear why not.

@Dheerajmalisetty: That's still a vague question and does not explain which specific issues are unclear and why. The task description feels pretty clear to me.
Maybe this task is not (yet) for you - please consider finding an easier one first.

Done.

We cannot help if you do not have specific questions and do not explain what you don't understand and why. :-/

Hi @Dheerajmalisetty! Please see and read https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker#Feedback.2C_questions_and_support - thanks!

In T184499#3885705, @Wiki13 wrote:

I am not someone from ops

Nobody knows what this is about, hence closing as invalid.

@Atsme: Removing you as assignee as I don't think that you plan to fix this task. Please correct me if I'm wrong.
Also, it is unclear where exactly (URL) and why you are unable to pull up any English Wikipedia stats. Please see https://mediawiki.org/wiki/How_to_report_a_bug - thanks.

SRE I guess

See https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Policy/Access_To_Security_Issues :)

Thanks! Whoops! 2017, not 2016. My copy and paste skills are improvable, it seems. :P

Please use the one attached

There is no attached one.

Is this about Cloud-Services ? Or something else?

I assume this is the same request as T184438 ? Not sure what this is about. Closing as duplicate and resetting priority.

I assume this is the same request as T184438 ? Not sure what this is about. Closing as a duplicate.

Resetting assignee. Feel free to reassign to yourself if you plan to work on fixing this task yourself. :)

Well, no reply by @Eisenhaus335, unfortunately.

@Kaganer: Sarcasm is not welcome.

In T152261#3881773, @mwjames wrote:

We don't close bugs just because they are inactive.

As the author of this issue, I came to the conclusion that it seems unreasonable to expect any changes.

@mwjames: You are free to, but that is unrelated to any activity or not. Please do not close tasks just because (wo)manpower is limited.

@Pine: https://meta.wikimedia.org/wiki/Legal#Wikimedia_Foundation_Email_Contacts explains how you can contact WMF's Legal team.
Legal is free to reopen T42006. Currently the situation is as in T42006.

The ping should not go to me but to WMF-Fundraising

Has this ever happened? Or is this still to be enabled again, 2½ months later?

@Sumitsurai: Any news, following https://wikitech.wikimedia.org/wiki/Reporting_a_connectivity_issue ? Is this still a problem?

In T100444#3878985, @Pamputt wrote:

Is there any news about this?

In T151172#3881399, @Pamputt wrote:

Is there any update on this request?

Ah, thanks for the explanation! Got it! :)

@Framawiki: FYI, I'm planning to remove the "Doing" column from the workboard, as I don't see any advantage in having it (see previous comments).

Unfortunately closing this report as no further information has been provided.
@Gustmd7410: After you have provided the information asked for and if this still happens, please set the status of this report back to "Open" via the Add Action... → Change Status dropdown. Thanks!

No reply by @Rantemario. Hence unfortunately closing.

@brihadeeshrk: Phabricator is not a place to play with. Your account has been disabled.

@brihadeeshrk: Phabricator is not a place to play with. Your account has been disabled.

I'd hope that https://en.wikipedia.org/wiki/Wikipedia:Purge provides more info :)

Duplicate of T127008?

Thanks! Published as https://codein.withgoogle.com/tasks/6625790378639360/

Thanks! Published as https://codein.withgoogle.com/tasks/6040999845429248/

Not a beginner task. :) Published as https://codein.withgoogle.com/tasks/6013397499904000/

I don't see a good reason to create subtasks here...

I don't see a good reason to create subtasks here...