Alsee
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Friday

  • Clear sailing ahead.
User Since
Feb 26 2015, 7:19 PM (103 w, 5 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
Alsee

Recent Activity

Yesterday

Alsee added a comment to T63729: Remove Flow from Meta-Wiki.

<rant>Sometimes I would really want a more firm standpoint from WMF against people moving backwards… </rant>

Tue, Feb 21, 6:11 AM · Patch-For-Review, Community-Liaisons, Collaboration-Team-Triage, Flow, Wikimedia-Site-requests

Thu, Feb 16

Alsee updated subscribers of T87686: Categories are metadata.

@Jdlrobson: I definitely didn't assume any bad faith here, and I didn't mean to "blame" anyone in particular. Consider this my attempt to stir concepts into the idea sessions :)

Thu, Feb 16, 3:11 PM · Wikidata, Structured-Multimedia-Data
Alsee added a comment to T87686: Categories are metadata.

Why edit in the page when you can edit outside it?

Thu, Feb 16, 12:54 AM · Wikidata, Structured-Multimedia-Data

Tue, Feb 14

Alsee reopened T139370: Share results of Hovercard A/B Test on Hungarian Wikipedia as "Open".
Tue, Feb 14, 5:14 PM · Community-Liaisons (Oct-Dec-2016), Page-Previews (2016-17-Q2-Goal), Reading-Web-Backlog
Alsee reopened T139370: Share results of Hovercard A/B Test on Hungarian Wikipedia , a subtask of T146755: Inform community on changes/updates on hovercards functionality based on A/B test results, as "Open".
Tue, Feb 14, 5:14 PM · Community-Liaisons (Oct-Dec-2016), Reading-Community-Engagement
Alsee added a comment to T139370: Share results of Hovercard A/B Test on Hungarian Wikipedia .

I'm going to re-open this. Based on a Google Translate view. it looks like there wasn't really any opportunity for them to comment on enablement of Hovercards. All I saw were comments indicating they couldn't comment on it because (at that time) testing of Hovercards was disabled.

Tue, Feb 14, 5:14 PM · Community-Liaisons (Oct-Dec-2016), Page-Previews (2016-17-Q2-Goal), Reading-Web-Backlog
Alsee added a comment to T154202: Skip popup when it is pointless.

@Aklapper I expanded the task in the description, and I see that this still hasn't been triaged.

Tue, Feb 14, 3:34 PM · VisualEditor
Alsee edited the description of T154202: Skip popup when it is pointless.
Tue, Feb 14, 3:30 PM · VisualEditor
Alsee awarded T7004: Keep the pipe trick ([[Piped link|]]) syntax in wikitext instead of converting it at pre-save transform a Love token.
Tue, Feb 14, 2:27 PM · MediaWiki-Page-editing
Alsee added a comment to T7004: Keep the pipe trick ([[Piped link|]]) syntax in wikitext instead of converting it at pre-save transform.

I don't really agree with this request. I prefer to see what is about to be saved.

Tue, Feb 14, 2:26 PM · MediaWiki-Page-editing

Tue, Jan 31

Alsee added a comment to T154843: New Wikitext Editor: Major improvement to load time to edit.

Summary of load times reported at the RFC:
Alsee: United States 30 seconds. List of Planets 127 seconds.
Daß Wölf: List of planets 114 seconds. Village pump proposals 21 seconds.
Yodin: United States 35 seconds. List of planets 122 seconds.
Fram: Leuchtenberg Gallery 15 seconds. Exposition des primitifs flamands à Bruges 50 seconds.
Whatamidoing: United States 9 seconds. <--- One anomalous report

Tue, Jan 31, 6:40 PM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic
Alsee added a comment to T154843: New Wikitext Editor: Major improvement to load time to edit.

Alsee, are you running Windows?

Yes.

Tue, Jan 31, 6:18 PM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic

Mon, Jan 30

Alsee added a comment to T154843: New Wikitext Editor: Major improvement to load time to edit.

why your experience of performance is so different from other people's.

Mon, Jan 30, 2:20 PM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic

Sat, Jan 28

Alsee added a comment to T122806: Wikidata items for articles in the Draft namespace.

Holy crap. Wikidata should not be linking to our draft space at all. They definitely should not appear on other language wikis, as public links to a supposed English Language version of the article.

Sat, Jan 28, 1:04 AM · Wikimedia-Site-requests, Wikidata

Thu, Jan 26

Alsee added a comment to T144730: Publication of the Flow Satisfaction Survey results including an analysis and raw data.

Rather than "assumptions", I'd rather call it a concern. Ensuring a good initial publication is a lot better than (possibly) trying to rewrite history after publication.

Thu, Jan 26, 9:32 PM · Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017), Community-Liaisons (Jan-Mar 2017), User-notice-collaboration, Collaboration-Community-Engagement, Flow
Alsee added a comment to T144730: Publication of the Flow Satisfaction Survey results including an analysis and raw data.

I'll illustrate the problem:

Thu, Jan 26, 11:08 AM · Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017), Community-Liaisons (Jan-Mar 2017), User-notice-collaboration, Collaboration-Community-Engagement, Flow

Wed, Jan 25

Alsee added a comment to T144730: Publication of the Flow Satisfaction Survey results including an analysis and raw data.

@Trizek-WMF thanx for the reply, although I think I failed to properly identify my concern. I fear that you may be unaware of a potential incoming trainwreck.

Wed, Jan 25, 6:05 PM · Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017), Community-Liaisons (Jan-Mar 2017), User-notice-collaboration, Collaboration-Community-Engagement, Flow

Mon, Jan 23

Alsee raised the priority of T63729: Remove Flow from Meta-Wiki from "Lowest" to "Needs Triage".
Mon, Jan 23, 11:02 PM · Patch-For-Review, Community-Liaisons, Collaboration-Team-Triage, Flow, Wikimedia-Site-requests
Alsee added a comment to T63729: Remove Flow from Meta-Wiki.

The RFC on Meta has closed with a clear consensus to remove Flow. Note that this was not an RFC to reduce active Flow pages to zero, this was an RFC for the extension be uninstalled as was done on Enwiki. (T148611)

Mon, Jan 23, 11:01 PM · Patch-For-Review, Community-Liaisons, Collaboration-Team-Triage, Flow, Wikimedia-Site-requests
Alsee added a comment to T144730: Publication of the Flow Satisfaction Survey results including an analysis and raw data.

Four months ago I commented here: The analysis needs to clearly note that invitation and participation were heavily biased towards Flow enthusiasts. (Invitations were selectively posted on the user_talk pages of the small minority who converted their user_talk to Flow.) This should be particularly noted in relation to the question comparing wikitext to Flow.

Mon, Jan 23, 10:32 PM · Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017), Community-Liaisons (Jan-Mar 2017), User-notice-collaboration, Collaboration-Community-Engagement, Flow

Jan 9 2017

Alsee added a comment to T154843: New Wikitext Editor: Major improvement to load time to edit.

@Aklapper if you can get the this new editor load time to be comparable to current editor load times, then sure. That will get this Phab listing closed, and terminate the entire discussion here.

Jan 9 2017, 12:31 PM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic

Jan 8 2017

Alsee added a comment to T154844: New Wikitext Editor: previews should match article view (use PHP parser).

The issue was first raised by me 14 weeks ago half way down this thread on Talk:Wikimedia_Product. That was before any project page or documentation even existed yet. "Whatamidoing, can you please please please go to the head of the New Wikitext Editor project and tell them that a new "Wikitext editor" that doesn't have genuine wikitext support is a deal breaker? It has the same Parasoid-based fake wikitext that Flow has. I suspect there would be a consensus against even having it in Beta-features until that "bug" is fixed. I've already saved a screenshot showing the New Editor botching the preview in nine different ways at once, and it's not hard to show lots more. A new wikitext editor that can't give accurate previews is a non-starter."

Jan 8 2017, 5:12 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee added a comment to T154844: New Wikitext Editor: previews should match article view (use PHP parser).

To avoid a split discussion, see my Technical Collaboration Guideline comment at T154843#2926550.

Jan 8 2017, 3:16 AM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee added a comment to T154843: New Wikitext Editor: Major improvement to load time to edit.

P.S. I forgot to mention the Technical Collaboration Guideline. As an individual, I am proposing this as an Actionable Blocker. I would be more than happy to see the WMF close this as cantfix/wontfix, so long as it will be reopened as a blocker if/when the community formally resubmits it as a consensus blocker issue.

Jan 8 2017, 3:14 AM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic
Alsee added a comment to T130470: Conduct a Gather extension postmortem.

What I mean is that the community wasn't quibbling about the exact quantity of work. If you could wave a magic wand and reduce the labor by 90%, it wouldn't have made a difference. People who opposed it still would have opposed it.

Jan 8 2017, 2:19 AM · Community-Liaisons, Technical-Collaboration-Guidance, Reading-Web-Backlog

Jan 7 2017

Pppery awarded T154844: New Wikitext Editor: previews should match article view (use PHP parser) a Like token.
Jan 7 2017, 4:38 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee created T154844: New Wikitext Editor: previews should match article view (use PHP parser).
Jan 7 2017, 11:49 AM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee created T154843: New Wikitext Editor: Major improvement to load time to edit.
Jan 7 2017, 11:48 AM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic
Alsee added a comment to T154202: Skip popup when it is pointless.

@Aklapper I just had it happen again. I was able to get a screenshot this time:

Jan 7 2017, 5:40 AM · VisualEditor
Alsee added a comment to T130470: Conduct a Gather extension postmortem.

I believe I have avoided a "blame" tone in my list below, but I welcome any attempt to improve tone or clarity.

  • Pre-development input: This is an old lesson. Early community input has previously been identified as a key factor in the success or failure of a project. For some reason it is still hard to put this lesson into practice. The Gather project was effectively invisible to the community, up to the point it was announced for deployment. Community input during the concept and design phase could have identified significant issues in advance. The idea could have been re-thought, or cheaply canceled.
  • Moderation tools: The community has fairly high expectations that any user-generated content is tracked in contribution history, that all of the usual functionality be available for cleaning it up, and that cleanup actions be logged for accountability. Integrating any new non-wikipage user content into our existing systems is a significant undertaking. It should not be done lightly. The community may (uncomfortably) accept bugs or limitations in theses systems in a limited beta-test. However a project team must be prepared to either roll back the product, or to take responsibility for implementing full tracking&moderation functionality if content is left live for an extended period. This issue was addressed by Risker's checklist for content-creation extensions and T126952: Integrate Risker's checklist for content-creation extensions to the WMF product development process.
  • Was the maintenance burden underestimated? (Suggested in comment by @JEumerus.) I think it is important to note that this was NOT a significant focus in community discussions. Yes, there would be a lot to review, and yes AFD style keep/delete debates would be ugly, but the critical community concerns were not the what the WMF expected.
  • Nature of the content and nature of the work: The content goes against many community policies, and against the very reason that we volunteer. Editors volunteer their unpaid labor to generate publicly-owned content, as a public service to the world. Even user space pages are considered community owned, they are (loosely) expected to serve our global-good mission. Gather content is viewed as essentially "privately owned" social-network style random junk. Any labor greater than zero is like being an unpaid employee policing Facebook content. The community isn't a free labor force to police John Doe's personal junk, for John Doe's personal benefit. The work might seem similar, but community sees a significant difference.
  • Terminating a project must be explicitly in-scope for discussion: This issue lead to communication-breakdown and collaboration-breakdown on multiple levels. There were multiple requests from the community to the WMF for a collaborative process to resolve the issue. These requests were made to the liaison, to the project manager, and even to the executive director. All of those requests received evasive non-responses. (Is there some internal WMF policy or culture against responding to those requests?) Multiple requests were made for the WMF acknowledge that ending the project was in-scope for discussion. All of those requests received evasive non-responses. (Is there some internal WMF policy or culture against responding to those requests?) This issue eroded community trust that the WMF was willing or able to participate in good-faith collaborative resolution. It's hard to discuss fixing a project when the WMF can't acknowledge that ending the project might end up being the most appropriate outcome.
  • "Community doesn't like/want a product" needs to be considered valid and important feedback. If the community reasons are unclear or confusing, the actionable-response is to investigate and engage. The WMF shouldn't have missed the huge red flag when the Administrator's Noticeboard announcement turned into outright revolt. The community may have communicated its position poorly. The community tends to cite policy-jargon in its reasons. And in this case the community discussion took an odd turn... the community didn't want to engage in an uphill battle arguing against the project. The community basically said "You can keep your project but you'll have to pay staff to do 100% of the labor". This was basically a sarcastic position. The community did not expect the WMF to pay staff to police the content. The WMF was expected to realize that the project was non-viable without community&admin support. In any case, the WMF should have taken the situation seriously.
  • Avoid telling the community not to run an RFC. A number of editors wanted to pursue collaborative-resolution with the WMF. Morale for a collaborative process broke down for a number of reasons. Telling the community not to run an RFC is a sore point. This was a "last straw" that caused the final crumble in morale. At that point the community started the RFC, rather than wait for the WMF to announce its internal decision on Gather.
Jan 7 2017, 1:44 AM · Community-Liaisons, Technical-Collaboration-Guidance, Reading-Web-Backlog

Jan 4 2017

Alsee added a comment to T64270: Support video and audio content.

T154387 was just closed as a dupe of this because the general issue is being dealt with here, however T154387 is a much more specific bug with much more specific requirements.

Jan 4 2017, 2:04 PM · Patch-For-Review, Parsoid

Jan 2 2017

Alsee added a comment to T154204: New Wikitext Editor: Page notice with collapsed template is broken.

If the broken ANRFC toolbox is a WontFix, can you please update the 2017 wikitext editor page to remove the claim that deploying New Wikitext Editor won't break anything? We'll give users as good an experience as we can, without breaking anything.

Jan 2 2017, 8:25 AM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor

Dec 31 2016

Alsee created T154387: New Wikitext Editor: Preview is broken for OGG element (and probably other media).
Dec 31 2016, 11:56 PM · Parsoid, VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee created T154385: Low framerate while vertical scrolling lots of content in an OOUI window in Chrome..
Dec 31 2016, 11:05 PM · OOjs-UI (OOjs-UI-0.18.3), Browser-Support-Google-Chrome
Alsee added a comment to T153535: NWE: Links to missing pages should be red in preview.

Not just redlinks. External links need to show as external links, and a page that links to itself needs to be a black (non-)link. Same as the normal wikitext editor preview.

Dec 31 2016, 9:39 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor

Dec 30 2016

Alsee added a comment to T154202: Skip popup when it is pointless.

When I log out it is still remembering not to give me any popup, even when I clear cookies.

Dec 30 2016, 12:54 AM · VisualEditor

Dec 27 2016

Alsee created T154204: New Wikitext Editor: Page notice with collapsed template is broken.
Dec 27 2016, 9:16 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee created T154202: Skip popup when it is pointless.
Dec 27 2016, 8:48 PM · VisualEditor

Dec 16 2016

Alsee created T153453: Parser: span fails to close inside bold-italics.
Dec 16 2016, 1:36 PM · MediaWiki-Parser
Alsee awarded T153306: It would be nice to have Show preview and Review your changes more directly accessible in the New Wikitext Editor a Like token.
Dec 16 2016, 9:05 AM · Design, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor

Nov 15 2016

Alsee added a comment to T119595: Provide a reply to Letter to Wikimedia Foundation: Superprotect and Media Viewer.

The letter referred to "permit local projects (...) to determine the default status of the Media Viewer"

I believe this answers the point of the letter, and this is why I think it is correct to resolve this task.

Nov 15 2016, 6:44 AM · Technical-Collaboration-Guidance, Community-Liaisons (Oct-Dec-2016), Liaisons-March-2016, Liaisons-February-2016, DevRel-January-2016, DevRel-December-2015

Nov 12 2016

Alsee updated subscribers of T119595: Provide a reply to Letter to Wikimedia Foundation: Superprotect and Media Viewer.

@WhatamIdoing it's not clear at all.

Nov 12 2016, 1:42 PM · Technical-Collaboration-Guidance, Community-Liaisons (Oct-Dec-2016), Liaisons-March-2016, Liaisons-February-2016, DevRel-January-2016, DevRel-December-2015
Alsee added a comment to T119595: Provide a reply to Letter to Wikimedia Foundation: Superprotect and Media Viewer.

@Qgil this is either "Open" or "Declined". The purpose here was to get some sort of clarity. We definitely do not have that here. I for one have absolutely no clue what would happen if one or more communities were to again alter the the default status of the Media Viewer.

Nov 12 2016, 1:33 AM · Technical-Collaboration-Guidance, Community-Liaisons (Oct-Dec-2016), Liaisons-March-2016, Liaisons-February-2016, DevRel-January-2016, DevRel-December-2015
Alsee reopened T119595: Provide a reply to Letter to Wikimedia Foundation: Superprotect and Media Viewer as "Open".
Nov 12 2016, 1:33 AM · Technical-Collaboration-Guidance, Community-Liaisons (Oct-Dec-2016), Liaisons-March-2016, Liaisons-February-2016, DevRel-January-2016, DevRel-December-2015

Nov 3 2016

Alsee awarded T117990: Enable the Flow personal talk opt-in Beta Feature on some wikis a Dislike token.
Nov 3 2016, 5:42 PM · Goal, Community-Liaisons, Collaboration-Team-Triage, Wikimedia-Site-requests, Flow

Oct 30 2016

Alsee added a comment to T146727: Create a lockdown configuration for Flow on Enwiki to prevent anyone at all from creating new Flow boards.

T148611 is uninstalling the Flow extension on EnWiki.

Oct 30 2016, 11:49 PM · Collaboration-Team-Triage (Collab-Team-Q2-Oct-Dec-2016), Flow
Alsee added a comment to T2582: Remind me of this article in X days.

Is it really a good idea to add an interface element and one-off code for this micro-feature? It seems like this functionality would be trivially inherent if a workflow system is created.

Oct 30 2016, 8:02 PM · Rails-Girls-Summer-of-Code (2017), Outreach-Programs-Projects, Reading-Web-Planning, Collaboration-Team-Triage, Notifications, WorkType-NewFunctionality, MediaWiki-General-or-Unknown
Alsee added a comment to T63729: Remove Flow from Meta-Wiki.

Flow is to be uninstalled on EnWiki T148611, can we just roll the two tasks into one?

Oct 30 2016, 7:37 PM · Patch-For-Review, Community-Liaisons, Collaboration-Team-Triage, Flow, Wikimedia-Site-requests

Oct 20 2016

Alsee added a comment to T104479: Provide a modern wikitext editor .

@Alsee: Can you provide the Wikitext that you were previewing?

Oct 20 2016, 10:49 PM · VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Design, Epic

Oct 16 2016

Alsee added a comment to T120219: PageAssessments deployment to WMF wikis.

Remember that someone could put "JohnDoe(555)555-1234" in there, or even "JohnDoeIsAPedophile".

Oct 16 2016, 12:11 PM · Patch-For-Review, MediaWiki-extensions-PageAssessments, Community-Tech-fixes, Tracking, Community-Tech

Oct 7 2016

Alsee added a comment to T147655: [<!--Hidden HTML comments-->[ should not be processed the same as [[.

[<!--Hidden HTML comments-->[Link]] turns into [[Link]] is of course the wanted result. Comments are obviously ignored.

Oct 7 2016, 8:22 PM · Parsing-Team, MediaWiki-Parser

Oct 6 2016

Alsee added a comment to T104479: Provide a modern wikitext editor .

@Alsee are you using Mathoid? The error is likely related to the fact that you use Parsoid (and RESTBase too?) but not Mathoid.

Oct 6 2016, 7:02 AM · VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Design, Epic

Oct 5 2016

Alsee added a comment to T104479: Provide a modern wikitext editor .

MUST-FIX: Don't use Parasoid. It results in assorted preview errors. I briefly tested the New Editor, and tossed together this screenshot with a random assortment of problems. The left side is the New Editor preview, the right side is the current wikitext editor preview, and both are previewing the same wikitext. Hint: The right side render is correct.

Oct 5 2016, 8:06 PM · VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Design, Epic

Oct 1 2016

Alsee added a comment to T146899: Keep Tech News easy to read.

For what it's worth, people who think it's a fun hobby to write an encyclopedia are typically going to have have above average reading comprehension :)

Oct 1 2016, 10:57 AM · Community-Liaisons (Jan-Mar 2017), User-Johan, Goal

Sep 29 2016

Alsee added a comment to T107595: [RFC] Multi-Content Revisions.

Did anyone consider that it might be a bad idea to start building a radical change to the editing environment without investigating whether the editing community wants this?

Each of the use cases have had quite a bit of discussion, and has had quite a bit of investigation by the people proposing it.

Sep 29 2016, 10:02 PM · User-Daniel, Wikidata-Sprint, ArchCom-Has-shepherd, RfC, Wikidata-Sprint-2015-11-17, Wikidata-Sprint-2015-11-03, Wikidata-Sprint-2015-10-13, Wikidata-Sprint-2015-09-29, Wikimedia-Developer-Summit-2016, Wikidata, Wikidata-Sprint-2015-09-15, ArchCom-RfC

Sep 28 2016

Alsee added a comment to T108407: Compare selected revisions for Flow history.

Highlighting new posts only works for the narrow use case.

Sep 28 2016, 8:02 PM · Collaboration-Team-Triage, Flow
Alsee added a comment to T146727: Create a lockdown configuration for Flow on Enwiki to prevent anyone at all from creating new Flow boards.

What is the point of re-opening this task? It was created based on a miscommunication. As far as I'm aware, there is no one at the WMF or in the community who wants this.

Sep 28 2016, 11:57 AM · Collaboration-Team-Triage (Collab-Team-Q2-Oct-Dec-2016), Flow

Sep 27 2016

Alsee closed T146727: Create a lockdown configuration for Flow on Enwiki to prevent anyone at all from creating new Flow boards as "Invalid".
Sep 27 2016, 2:01 PM · Collaboration-Team-Triage (Collab-Team-Q2-Oct-Dec-2016), Flow

Sep 26 2016

Alsee added a comment to T107595: [RFC] Multi-Content Revisions.

My apologies, my intent wasn't to try to prove a case against MCR here. (Although I do understand why replies focused in that direction). Perhaps it would help if I shortened my previous comment:

Sep 26 2016, 4:05 AM · User-Daniel, Wikidata-Sprint, ArchCom-Has-shepherd, RfC, Wikidata-Sprint-2015-11-17, Wikidata-Sprint-2015-11-03, Wikidata-Sprint-2015-10-13, Wikidata-Sprint-2015-09-29, Wikimedia-Developer-Summit-2016, Wikidata, Wikidata-Sprint-2015-09-15, ArchCom-RfC

Sep 24 2016

Alsee added a comment to T144730: Publication of the Flow Satisfaction Survey results including an analysis and raw data.

The analysis needs to clearly note that invitation and participation were heavily biased towards Flow enthusiasts. (Invitations were selectively posted on the user_talk pages of the small minority who converted their user_talk to Flow.)

Sep 24 2016, 6:32 PM · Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017), Community-Liaisons (Jan-Mar 2017), User-notice-collaboration, Collaboration-Community-Engagement, Flow
Alsee added a comment to T107595: [RFC] Multi-Content Revisions.

Did anyone consider that it might be a bad idea to start building a radical change to the editing environment without investigating whether the editing community wants this? Ripping categories and templates and other stuff entirely out of the page?

Sep 24 2016, 1:08 PM · User-Daniel, Wikidata-Sprint, ArchCom-Has-shepherd, RfC, Wikidata-Sprint-2015-11-17, Wikidata-Sprint-2015-11-03, Wikidata-Sprint-2015-10-13, Wikidata-Sprint-2015-09-29, Wikimedia-Developer-Summit-2016, Wikidata, Wikidata-Sprint-2015-09-15, ArchCom-RfC

Sep 17 2016

Alsee added a comment to T144571: Mobile Media Viewer violates user settings.

I just did some casual testing, loading the mobile site (en.m.wikipedia.org) using desktop, with preference Media Viewer off. Clicking images give unpredictable results. I get one of the following two types of result:
https://en.m.wikipedia.org/wiki/File:The_Matrix_Poster.jpg
https://en.m.wikipedia.org/wiki/The_Matrix#/media/File%3AThe_Matrix_Poster.jpg

Sep 17 2016, 12:53 AM · Reading-Web-Backlog, Design, MobileFrontend

Sep 9 2016

Alsee added a comment to T85847: Grant editcontentmodel right to all logged in users.

This task should be declined. It is just pointless disruption to let zero-rights-users screw with the content model of random pages. Utilizing massmessage requires advanced permissions to send out the messages anyway. Obviously someone with advanced permissions can handle the rare and trivial creation of the page in the first place.

Sep 9 2016, 9:45 AM · Community-consensus-needed, WMF-deploy-2016-09-13_(1.28.0-wmf.19), MW-1.28-release-notes, MW-1.27-release-notes, WMF-deploy-2016-03-01_(1.27.0-wmf.15), Patch-For-Review, MediaWiki-ContentHandler

Sep 5 2016

Alsee added a comment to T124225: PageImages should never return non-free images.

@Voidronl:
Official WMF Resolution:Licensing policy opens with the following notice:

This policy is approved by the Wikimedia Foundation Board of Trustees.
It may not be circumvented, eroded, or ignored by Wikimedia Foundation officers or staff nor local policies of any Wikimedia project.

Please do not ignore, erode, or attempt to circumvent the limitations on use of non-free content. The fact that some wikis permit non-free content at all is itself conditional upon those limitations.

Sep 5 2016, 3:34 AM · WMF-deploy-2016-03-08_(1.27.0-wmf.16), Reading-Web-Sprint-68-"Java and JavaScript are basically the same", Reading-Admin, Reading-Community-Engagement, Wikipedia-iOS-App-Backlog, Wikipedia-Android-App-Backlog, Patch-For-Review, WMF-Legal, PageImages
Alsee added a comment to T95026: PageImages should be able to pick Wikidata's P18 as chosen image.

Taking control of this off of local wiki would be bad. In the few cases I checked this would have either been no help, or made things worse. It's hard to imagine many cases where Wikidata would have a suitable image that couldn't/shouldn't be in the article itself. Any rare case like that would be best dealt with using {{#pageimage:Image}} or {{#pageimage:{{#property:p18}}}}.

Sep 5 2016, 12:38 AM · Reading-Web-Backlog, Wikidata, PageImages
Alsee added a comment to T87336: PageImages shouldn't return images that are not in the lead section.

Wikidata was zero help. Jylland had no image, Fabia Drake returned the SAME wrong image, and Sexual Assault returned an offensively bad carton image. I removed the two bad images from Wikidata.

Sep 5 2016, 12:26 AM · WMF-deploy-2016-12-13_(1.29.0-wmf.6), Reading-Web-Sprint-87-♨️😭, Reading-Web-Sprint-86-🔪🦃, Reading-Web-Backlog, Wikipedia-iOS-App-Backlog, Wikipedia-Android-App-Backlog, PageImages

Sep 3 2016

Alsee raised the priority of T87336: PageImages shouldn't return images that are not in the lead section from "Low" to "Normal".
Sep 3 2016, 5:06 PM · WMF-deploy-2016-12-13_(1.29.0-wmf.6), Reading-Web-Sprint-87-♨️😭, Reading-Web-Sprint-86-🔪🦃, Reading-Web-Backlog, Wikipedia-iOS-App-Backlog, Wikipedia-Android-App-Backlog, PageImages
Alsee added a comment to T87336: PageImages shouldn't return images that are not in the lead section.

Sexual assault returns a seriously bad selection. The image is a living young woman which, when used as PageImage paired with the page title, looks BADLY like she was just Sexually Assaulted moments ago.
Jyllands-Posten Muhammad cartoons controversy reaches all the way down to the 15th article section, for the 4th article image, tangentially related, from 700 years ago
Fabia Drake returns an image of Tallulah Bankhead
I don't have a link handy, but there was a biography that not only returned the wrong person, it returned the opposite gender.

Sep 3 2016, 5:06 PM · WMF-deploy-2016-12-13_(1.29.0-wmf.6), Reading-Web-Sprint-87-♨️😭, Reading-Web-Sprint-86-🔪🦃, Reading-Web-Backlog, Wikipedia-iOS-App-Backlog, Wikipedia-Android-App-Backlog, PageImages

Sep 2 2016

Alsee created T144571: Mobile Media Viewer violates user settings.
Sep 2 2016, 2:17 AM · Reading-Web-Backlog, Design, MobileFrontend

Aug 26 2016

Alsee added a comment to T143422: Indicate when text chunks have been moved, but not changed otherwise.

I've been thinking about it. I'm not sure it makes sense to solve the simpler design problem for unchanged-moves first. Showing moves-with-changes presumably also needs to be solved, and that solution will probably define what the solution should/must be for the no-change case. Hopefully the ideas here can be a good starting point.

Aug 26 2016, 8:02 PM · TCB-September Tasks, TCB-Team-Sprint-2016-08-29, WMDE-Design, TCB-Team-Sprint-2016-08-11, TCB-Team, MediaWiki-History-or-Diffs, Design

Aug 25 2016

Alsee added a comment to T68078: When mentioning other users, indicate mention notifications in the "your edit was saved" message.

Based on comments elsewhere, it appears that the mention information isn't available until about 1/3 of a second after the "your edit was saved" message is sent. Could we send the "saved" message, leave the connection open, and send the mention results when they become available? This should visibly update the screen even if there are zero mentions.

Aug 25 2016, 9:31 AM · Collaboration-Team-Triage, Notifications

Aug 24 2016

Alsee added a comment to T143422: Indicate when text chunks have been moved, but not changed otherwise.

I just made a mock-up with =/= and using black. I think it works.
Edit: I changed my mock-up to treat blank lines as a -/+ change. That will make much more sense in general, unless we can group the blank lines in the same box with the moved text.

Aug 24 2016, 11:59 PM · TCB-September Tasks, TCB-Team-Sprint-2016-08-29, WMDE-Design, TCB-Team-Sprint-2016-08-11, TCB-Team, MediaWiki-History-or-Diffs, Design
Alsee added a comment to T143422: Indicate when text chunks have been moved, but not changed otherwise.

''Would it make sense to you to keep the highlighting like it is now so a moved text (former position) is yellow and a moved text in its future position is blue?''

Aug 24 2016, 10:55 PM · TCB-September Tasks, TCB-Team-Sprint-2016-08-29, WMDE-Design, TCB-Team-Sprint-2016-08-11, TCB-Team, MediaWiki-History-or-Diffs, Design
Alsee added a comment to T125632: Plan, write and submit a satisfaction survey concerning Flow to communities.

@Trizek-WMF, the goal is to get unbiased feedback, right? The current survey invitation plans will inadvertently bias the results as hard as possible:

Aug 24 2016, 3:56 AM · Community-Liaisons (Jul-Sep-2016), Collab-Team-Q1-July-Sep-2016, Liaisons-April-2016, Liaisons-March-2016, Surveys, Collaboration-Community-Engagement, Liaisons-February-2016, Flow

Aug 23 2016

Alsee added a comment to T143422: Indicate when text chunks have been moved, but not changed otherwise.

Wow, the example image was so extremely confusing that it actually wound up being fascinating. Chuckle. For quite a while I couldn't find any moved text at all. Grey paired with grey says "don't waste looking at this, don't waste time thinking about this". We are actively blind to grey text paired with grey text.

Aug 23 2016, 9:17 PM · TCB-September Tasks, TCB-Team-Sprint-2016-08-29, WMDE-Design, TCB-Team-Sprint-2016-08-11, TCB-Team, MediaWiki-History-or-Diffs, Design
Alsee added a comment to T139962: When saving, be informed about mentions you sent (#9).

I hope Notifications isn't considered a substitute for T68078 (indicating mentions when the page is saved).

Aug 23 2016, 6:02 PM · TCB-Team (Oct2016-March2017), German-Community-Wishlist-Main-Wishes

Aug 12 2016

Alsee added a comment to T131132: Re-label the "Save" button to be "Publish", to better indicate to users the outcomes of their action.

Have you considered the confusion for new editors when many editors habitually keep calling it the "save button"? That will keep happening for years, and it could persist indefinitely given the human habit for shorter terms.

Aug 12 2016, 7:15 AM · MW-1.28-release-notes, WMF-deploy-2016-08-30_(1.28.0-wmf.17), Community-Liaisons, WMF-deploy-2016-05-03_(1.27.0-wmf.23), MW-1.27-release-notes, Patch-For-Review, WikiEditor, VisualEditor, Editing-Department, MediaWiki-Internationalization, MediaWiki-Page-editing, User-notice

Jul 30 2016

Alsee added a comment to T141576: Please disable CX until drafts aren't completely private.

I don't think anyone believed it was *illegal* to store sever-side drafts. There are strong concerns that it's a very bad idea and extremely undesirable. Current user-private data very limited, very low visibility, and very impractical/implausible to use. Private server drafts is an obvious and practically unlimited text store. It is trivially usable for modest size binary files, with only minor inconvenience. Large binary storage is possible but implausibly impractical.

Jul 30 2016, 11:57 AM · Language-Engineering July-September 2016, WMF-Legal, ContentTranslation-Release10

Jul 23 2016

Alsee added a comment to T119595: Provide a reply to Letter to Wikimedia Foundation: Superprotect and Media Viewer.

It's been over 700 days since the letter, and just under 4 weeks to the two-year mark. Maybe someone can make it a goal not to cross the two year mark?

Jul 23 2016, 8:00 PM · Technical-Collaboration-Guidance, Community-Liaisons (Oct-Dec-2016), Liaisons-March-2016, Liaisons-February-2016, DevRel-January-2016, DevRel-December-2015

May 8 2016

Alsee reopened T76749: data-ve-clipboard-key span inserted in page as "Open".
May 8 2016, 10:26 AM · VisualEditor pre-2015 work, WMF-deploy-2014-12-10_(1.25wmf12), WMF-deploy-2014-11-26-(1.25wmf10), WMF-deploy-2014-12-03-(1.25wmf11), VisualEditor-ContentEditable, VisualEditor

Apr 26 2016

Alsee added a comment to T132806: Enwiki is a wikitext-primary site, and the visual editor is the primary editor for new logged-in editors.

Note: With the Wikitext editor loading first as primary/default, the popup for Continue_Editing/Switch_Editors will need a text-tweak to "Switch to Visual Editor".

Apr 26 2016, 3:16 PM · Patch-For-Review, VisualEditor, VisualEditor-MediaWiki

Apr 21 2016

Alsee added a comment to T119595: Provide a reply to Letter to Wikimedia Foundation: Superprotect and Media Viewer.

@Whatamidoing-WMF you might want to consider striking your comment calling my comment "inaccurate"..... unless someone at the WMF addresses the problem in the next 7 hours. It's been a week since Elitre made that comment, and James has been ignoring the issue on Phab and on his talk page for 9 days. So far no one at the WMF has been willing to discuss the faulty deployment. ("Faulty deployment" is the only good-faith option here.)

Apr 21 2016, 1:41 PM · Technical-Collaboration-Guidance, Community-Liaisons (Oct-Dec-2016), Liaisons-March-2016, Liaisons-February-2016, DevRel-January-2016, DevRel-December-2015

Apr 15 2016

Alsee added a comment to T119595: Provide a reply to Letter to Wikimedia Foundation: Superprotect and Media Viewer.

@Qgil is there any chance you can immediately post the "generic Opt-out process"? That may be preferable to the chaotic events that are currently unfolding.

Apr 15 2016, 1:34 AM · Technical-Collaboration-Guidance, Community-Liaisons (Oct-Dec-2016), Liaisons-March-2016, Liaisons-February-2016, DevRel-January-2016, DevRel-December-2015

Apr 13 2016

Alsee added a project to T132556: Faulty "You have switched editors" popup makes it difficult for new users to return to primary editor: VisualEditor.
Apr 13 2016, 9:42 AM · VisualEditor
Alsee created T132556: Faulty "You have switched editors" popup makes it difficult for new users to return to primary editor.
Apr 13 2016, 9:23 AM · VisualEditor

Apr 12 2016

Alsee added a comment to T128478: Enable single edit tab on enwiki.

Please REVERT or FIX immediately.

Apr 12 2016, 8:30 PM · WMF-deploy-2016-04-05_(1.27.0-wmf.20), Wikimedia-Site-requests, VisualEditor-MediaWiki, VisualEditor
Alsee edited the description of T128478: Enable single edit tab on enwiki.
Apr 12 2016, 8:26 PM · WMF-deploy-2016-04-05_(1.27.0-wmf.20), Wikimedia-Site-requests, VisualEditor-MediaWiki, VisualEditor
Alsee edited the description of T128478: Enable single edit tab on enwiki.
Apr 12 2016, 8:21 PM · WMF-deploy-2016-04-05_(1.27.0-wmf.20), Wikimedia-Site-requests, VisualEditor-MediaWiki, VisualEditor
Alsee reopened T128478: Enable single edit tab on enwiki as "Open".
Apr 12 2016, 8:17 PM · WMF-deploy-2016-04-05_(1.27.0-wmf.20), Wikimedia-Site-requests, VisualEditor-MediaWiki, VisualEditor
Alsee reopened T128478: Enable single edit tab on enwiki, a subtask of T102398: Migrate wikis to use a single edit tab which has both visual and wikitext modes and allows on-the-fly switching between them, as "Open".
Apr 12 2016, 8:17 PM · User-notice, Epic, Design, VisualEditor-MediaWiki, VisualEditor
Alsee reopened T128478: Enable single edit tab on enwiki, a subtask of T119269: Run experiment defaulting anonymous editors to the visual editor on the English Wikipedia, as "Open".
Apr 12 2016, 8:17 PM · Category, VisualEditor-MediaWiki, VisualEditor, Editing-Analysis

Apr 3 2016

Alsee added a comment to T102398: Migrate wikis to use a single edit tab which has both visual and wikitext modes and allows on-the-fly switching between them.

@Jdforrester-WMF
I earlier asked if the WMF was going to try to push a VE-default as part of the single-edit-tab deployment. You said you wouldn't do that without talking to the wikis first.

Apr 3 2016, 5:07 PM · User-notice, Epic, Design, VisualEditor-MediaWiki, VisualEditor

Mar 16 2016

Alsee added a comment to T91683: Allow editors control of the page image.

@Jdlrobson thanx. It's currently grabbing the next available image.

Mar 16 2016, 10:30 PM · Reading-Web-Backlog, PageImages

Mar 15 2016

Alsee added a comment to T91683: Allow editors control of the page image.

Any magicword needs to accept "none" as the image. This will override any automatic image selection treat it like an article with no images. This is needed in circumstances where none of the images in the article are remotely appropriate for representing the topic. A biography article may not have any available image of the person, but may contain an image of their spouse, or even something they fought against. (Someone opposed to pornography shouldn't be represented by a movie they tried to get banned, and a politician who lost an election shouldn't be represented by the politician who won.)

Mar 15 2016, 11:10 PM · Reading-Web-Backlog, PageImages

Feb 29 2016

Alsee added a comment to T68078: When mentioning other users, indicate mention notifications in the "your edit was saved" message.

+1 for this being a significant and persistent issue. The fact that you can't add a ping to an existing chunk of text is a very easy constraint to miss.
+1 for previews indicating whether the save will trigger pings. It vastly reduces the risk of trying to ping and not realizing you failed, and if a ping attempt is failing you very much want to fix it during the preview phase. Adding a new edit to send a ping after ping-fail can get a little messy.

Feb 29 2016, 4:10 AM · Collaboration-Team-Triage, Notifications

Feb 20 2016

Alsee added a comment to T122961: Remove Flow from Wikipedia talk:WikiProject Breakfast on enwp.

My description of the bug was inaccurate because the bugs here themselves created confusion, and because Quiddity said in his earlier comment that the WMF was not going to be applying protection to the page.

Feb 20 2016, 7:59 PM · Collaboration-Team-Archive-2015-2016, Wikimedia-Site-requests, Flow

Feb 18 2016

Alsee added a comment to T122961: Remove Flow from Wikipedia talk:WikiProject Breakfast on enwp.

@Quiddity
Bug report: The Edit Description link disappeared from at https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Breakfast/Flow_archive

Feb 18 2016, 8:46 AM · Collaboration-Team-Archive-2015-2016, Wikimedia-Site-requests, Flow

Jan 25 2016

Alsee added a comment to T124003: Automatically congratulate users for reaching certain edit count milestones.

I understand the intention is good here, to encourage more participation. However we want editors with intrinsic altruistic motivations. There is a Community Ethos opposed to people chasing after some sort of achievement list. There is a not-uncommon meme that "Wikipedia is not an MMORPG", it is explicit policy that Wikipedia is not a social network, and there is a related very negative view on hat collecting.

Jan 25 2016, 7:51 PM · WMF-deploy-2016-03-01_(1.27.0-wmf.15), User-notice, Collaboration-Team-Archive-2015-2016, Editing-Department, Notifications
Alsee awarded T124003: Automatically congratulate users for reaching certain edit count milestones a Dislike token.
Jan 25 2016, 6:31 PM · WMF-deploy-2016-03-01_(1.27.0-wmf.15), User-notice, Collaboration-Team-Archive-2015-2016, Editing-Department, Notifications

Jan 17 2016

Alsee added a comment to T122961: Remove Flow from Wikipedia talk:WikiProject Breakfast on enwp.

@Quiddity, could you clarify the "detailed attribution" issue?

Jan 17 2016, 7:44 AM · Collaboration-Team-Archive-2015-2016, Wikimedia-Site-requests, Flow