Alsee
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Saturday

  • Clear sailing ahead.

User Details

User Since
Feb 26 2015, 7:19 PM (116 w, 6 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
Alsee

Recent Activity

Mon, May 22

Alsee created T166058: Media Viewer cogwheel-preferences stopped working.
Mon, May 22, 2:01 PM · MediaWiki-extensions-MultimediaViewer
Alsee added a comment to T144571: Mobile Media Viewer violates user settings.

if JavaScript fails to load... going to the file page will happen

Thank you for clearing up why some of the testing gave random results. However that is not directly related to this issue.

Mon, May 22, 12:59 PM · Reading-Web-Backlog, Design, MobileFrontend

Sun, May 21

Alsee added a comment to T159032: Single Edit Tab global default change.

The WMF ran a controlled study on the effects of visual editor, showing that it provided zero benefit to new users and finding notable negative effects. Is there anyone here who honestly thinks that a majority of the general global editing community wants VE to be made the default?

Would love to see the study you mention, never heard of it.

Research:VisualEditor's_effect_on_newly_registered_editors/May_2015_study. Results: No change in how many new users made a first edit. No change in new user retention. No change in total contributions. Visual Editing was typically over 6.7 times slower, people were more likely to abandon edits without attempting to save, and attempted saves were less likely to be successful.

Sun, May 21, 3:26 PM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests

Sat, May 13

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

@Kipod, I strongly disagree.

Sat, May 13, 6:03 AM · Collaboration-Team-Triage, Notifications

Tue, May 9

Alsee added a comment to T135682: "Start editing" popup interferes with talk page usage.

This popup is a useless "click-to-continue" annoyance when it has only one option.

Tue, May 9, 8:14 PM · VisualEditor
Alsee merged task T154202: Don't show the welcome message unless it has a "switch to visual editing" button into T135682: "Start editing" popup interferes with talk page usage.
Tue, May 9, 8:12 PM · VisualEditor
Alsee merged T154202: Don't show the welcome message unless it has a "switch to visual editing" button into T135682: "Start editing" popup interferes with talk page usage.
Tue, May 9, 8:12 PM · VisualEditor

Apr 15 2017

Alsee added a comment to T159032: Single Edit Tab global default change.

If you really want to start a format consensus process, use the main BAR rooms, not the technical room used mostly for bug reporting.

Apr 15 2017, 10:54 PM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests
Alsee awarded T10681: Group changes across days in enhanced rc a Like token.
Apr 15 2017, 2:30 AM · MediaWiki-Watchlist, MediaWiki-Recent-changes

Apr 4 2017

Alsee added a comment to T153306: It would be nice to have Show preview and Review your changes more directly accessible in the New Wikitext Editor.
  • Burying PREVIEW in a menu behind the SAVE button leaves new users lost and scared when they actively avoid touching the dangerous SAVE button.
  • Burying the most used button in the editor is disruptive for experienced editors.

The most used button in the entire editor, and second most important button in the entire editor, absolutely warrants direct placement next to the SAVE button.

Apr 4 2017, 5:59 AM · Design, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor

Mar 28 2017

Alsee added a comment to T159032: Single Edit Tab global default change.

The discussion was unanimous when I posted it. Now one person has disagreed.

Mar 28 2017, 4:53 AM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests

Mar 27 2017

Alsee added a comment to T159032: Single Edit Tab global default change.

@Halibutt : While the comments were posted "last year", they are not over a year old. They were 3 months old when I opened this Phab, and now 4 months old. Your oppose and the new responses, it looks like 6-1. Would you like to open a more formal consensus-process to get a more formal result?

Mar 27 2017, 5:48 PM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests

Mar 25 2017

Alsee added a comment to T154844: New Wikitext Editor: Previews use the article-view rendering engine.

can you clarify?

Mar 25 2017, 10:52 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor

Mar 21 2017

Alsee added a comment to T154844: New Wikitext Editor: Previews use the article-view rendering engine.

I updated the task description to reflect the closure of the RFC on this issue. Also, my understanding is that blocker tasks inherit the priority of the parent task.

Mar 21 2017, 5:46 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee renamed T154844: New Wikitext Editor: Previews use the article-view rendering engine from New Wikitext Editor: Ensure that previews match article view as much as practical to New Wikitext Editor: Previews use the article-view rendering engine. (Consensus this is a blocker issue).
Mar 21 2017, 5:46 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee added a comment to T154843: New Wikitext Editor: Major improvement to load time to edit.

I updated the task description to reflect the closure of the RFC on this issue. Also, my understanding is that blocker tasks inherit the priority of the parent task.

Mar 21 2017, 5:46 PM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic
Alsee renamed T154843: New Wikitext Editor: Major improvement to load time to edit from New Wikitext Editor: Major improvement to load time to edit to New Wikitext Editor: Major improvement to load time to edit. (Consensus this is a blocker issue).
Mar 21 2017, 5:44 PM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic

Mar 18 2017

Pine awarded T154843: New Wikitext Editor: Major improvement to load time to edit a Manufacturing Defect? token.
Mar 18 2017, 8:13 PM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic

Mar 17 2017

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

Note that the Minor Planets page has been split. Anyone wanting to test that load time should use the link in Samwalton9's post above.

Mar 17 2017, 5:31 AM · Performance, VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor, VisualEditor-MediaWiki, Epic

Mar 16 2017

Alsee added a comment to T159032: Single Edit Tab global default change.

@Jdforrester-WMF, it's been almost three weeks since I opened this bug. Can I get an answer on this?
You said VE wouldn't be imposed as the SingleEditTab default without asking the community. You said it was a bug that SingleEditTab was deployed with a VE default. EnWiki was fixed to wikitext default, per discussion with the community. And now PolishWiki has a unanimous consensus asking for SingleEditTab to have a wikitext default.

Mar 16 2017, 9:23 AM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests

Mar 13 2017

Alsee added a comment to T114432: [RFC] Heredoc arguments for templates (aka "hygenic" or "long" arguments).

@jayvdb's suggestion looks like the best concepts here. I'd suggest a tweak:

Mar 13 2017, 10:09 PM · RfC, Parsing-Team, Wikimedia-Developer-Summit-2016, ArchCom-RfC

Mar 11 2017

Alsee added a comment to T153315: Pasting annotated wikitext results in double encoding and therefore <nowiki>s.

I'll add another voice to the chorus saying that CTRL-V needs to be a plain text paste. The formatted paste behavior is disruptive.

Mar 11 2017, 8:03 PM · VisualEditor-CopyPaste, MW-1.29-release (WMF-deploy-2017-01-03_(1.29.0-wmf.7)), VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor

Mar 9 2017

Alsee added a comment to T99924: Unable to click on links in templates.

If we let you interact with a template, we let you edit it.

Mar 9 2017, 6:45 AM · VisualEditor

Mar 8 2017

Alsee added a comment to T105498: Remove empty "See also"-section.
Mar 8 2017, 8:28 PM · WorkType-NewFunctionality, AutoWikiBrowser
Alsee added a comment to T105498: Remove empty "See also"-section.

I don't think it's a good idea to start singling out arbitrary section titles. Any empty section is almost never a desired permanent state. However it's not that unusual for sections to be empty while an article is being built, or when it's awaiting content, or when there is a debate in progress on what should/shouldn't be there.

Mar 8 2017, 8:27 PM · WorkType-NewFunctionality, AutoWikiBrowser
Alsee added a comment to T6715: Allow comments longer than 255 bytes.

I know next to squat about databases, so I apologize if this is incredibly dumb or obvious. Would it help to: Create the new comment table as write-only, fill it at leisure, and switch all reads&writes to the new table after it fully mirrors the existing data? Then increase the comment limit and clean up the old unused data at leisure.
That at least avoids the need to check both places during reads.

Mar 8 2017, 4:52 PM · Blocked-on-schema-change, Hindi-Sites, Malayalam-Sites, Community-Tech, User-notice, Schema-change, MediaWiki-Database

Mar 7 2017

Alsee added a comment to T159032: Single Edit Tab global default change.

The task is a four letter edit.

Mar 7 2017, 7:40 PM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests
Alsee added a comment to T159032: Single Edit Tab global default change.

Can you explain how this is different from T102398?

Mar 7 2017, 7:14 PM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests
Alsee added a comment to T159032: Single Edit Tab global default change.

Can someone please provide some sort of a response here?

Mar 7 2017, 7:00 PM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests
Alsee added projects to T159032: Single Edit Tab global default change: VisualEditor, VisualEditor-MediaWiki.
Mar 7 2017, 6:58 PM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests

Feb 26 2017

Liuxinyu970226 awarded T159032: Single Edit Tab global default change a Dislike token.
Feb 26 2017, 11:03 AM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests

Feb 25 2017

Alsee added a subtask for T102398: Migrate wikis to use a single edit tab which has both visual and wikitext modes and allows on-the-fly switching between them: T159032: Single Edit Tab global default change.
Feb 25 2017, 7:47 AM · User-notice, Epic, Design, VisualEditor-MediaWiki, VisualEditor
Alsee added a parent task for T159032: Single Edit Tab global default change: T102398: Migrate wikis to use a single edit tab which has both visual and wikitext modes and allows on-the-fly switching between them.
Feb 25 2017, 7:47 AM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests
Alsee created T159032: Single Edit Tab global default change.
Feb 25 2017, 7:45 AM · VisualEditor-MediaWiki, VisualEditor, Wikimedia-Site-requests

Feb 21 2017

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>

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

Feb 16 2017

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 :)

Feb 16 2017, 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?

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

Feb 14 2017

Alsee reopened T139370: Share results of Hovercard A/B Test on Hungarian Wikipedia as "Open".
Feb 14 2017, 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.
Feb 14 2017, 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.

Feb 14 2017, 5:14 PM · Community-Liaisons (Oct-Dec-2016), Page-Previews (2016-17-Q2-Goal), Reading-Web-Backlog
Alsee added a comment to T154202: Don't show the welcome message unless it has a "switch to visual editing" button.

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

Feb 14 2017, 3:34 PM · VisualEditor
Alsee updated the task description for T154202: Don't show the welcome message unless it has a "switch to visual editing" button.
Feb 14 2017, 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.
Feb 14 2017, 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.

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

Jan 31 2017

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

Jan 31 2017, 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.

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

Jan 30 2017

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.

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

Jan 28 2017

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.

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

Jan 26 2017

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.

Jan 26 2017, 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:

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

Jan 25 2017

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.

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

Jan 23 2017

Alsee raised the priority of T63729: Remove Flow from Meta-Wiki from Lowest to Needs Triage.
Jan 23 2017, 11:02 PM · User-notice-collaboration, 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)

Jan 23 2017, 11:01 PM · User-notice-collaboration, 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.

Jan 23 2017, 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 use the article-view rendering engine.

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 use the article-view rendering engine.

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 use the article-view rendering engine a Like token.
Jan 7 2017, 4:38 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee created T154844: New Wikitext Editor: Previews use the article-view rendering engine.
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: Don't show the welcome message unless it has a "switch to visual editing" button.

@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: Help communites replace page notices with collapsed templates as they're impossible for VE/NWE or mobile users.

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-MediaWiki-2017WikitextEditor, VisualEditor
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 (and self-links should be bold).

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-VisualDiffs, User-Ryasmeen, MW-1.29-release (WMF-deploy-2017-04-04_(1.29.0-wmf.19)), VisualEditor-MediaWiki-2017WikitextEditor, VisualEditor

Dec 30 2016

Alsee added a comment to T154202: Don't show the welcome message unless it has a "switch to visual editing" button.

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: Help communites replace page notices with collapsed templates as they're impossible for VE/NWE or mobile users.
Dec 27 2016, 9:16 PM · VisualEditor, VisualEditor-MediaWiki-2017WikitextEditor
Alsee created T154202: Don't show the welcome message unless it has a "switch to visual editing" button.
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 · Article-Reminder-Notifications, User-notice-collaboration, User-notice, Outreachy (Round-14), Google-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 · User-notice-collaboration, 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 (Apr-Jun 2017), User-Johan

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 · MediaWiki-Platform-Team, 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 · Flow, Collaboration-Team-Triage
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 · MediaWiki-Platform-Team, 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 · MediaWiki-Platform-Team, 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, MW-1.28-release (WMF-deploy-2016-09-13_(1.28.0-wmf.19)), MW-1.28-release-notes, MW-1.27-release-notes, MW-1.27-release (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 · MW-1.27-release (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 · MW-1.29-release (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