On Sat, Sep 15, 2012 at 1:47 PM, Oliver Keyes <okeyes(a)wikimedia.org>wrote;wrote: No, it's not an E3 thing. Mz just filed a bug bringing up the fact that it was derelict and potentially useful. -- Steven Walling https://wikimediafoundation.org/

Is this on WMF labs for testing purposes? From a brief read of the extension info page I see that a user would be able to save their drafts and access them - but thinking from a helping new users perspective, is there a way for other users (admins?) to access these drafts to help newbies who wonder where their drafts are when they navigate away from the page? This is going to need a lot of documentation, help page information etc as the idea of drafts is a new concept. New terminology may need to be introduced now - we currently 'save' a page, but you would 'publish' a draft. To add to Oliver's comments below, what would the proposed workflow for editing be? Edit page -> Save draft -> Publish draft Edit page -> Save page What about when someone wants to 'unpublish' a draft? I imagine there could be instances when users would accidentally publish their drafts and then wouldn't want the old drafts to be publicly viewable. Excuse me if all of these discussions have already happened, if they have I appear to have missed them! Thehelpfulone Sent from my iPhone On 15 Sep 2012, at 22:10, Oliver Keyes <okeyes(a)wikimedia.org> wrote: Gotcha. I'm going to reply there, but to duplicate my comments for the sake of people not following the bugzilla thread: TL;DR, I really oppose turning this on with the way it's formatted now and using the process that's being discussed. *For more detail on each point; this is not, as MzMcBride claims, "just a change to core functionality". It introduces a completely new workflow, alters existing ones and sticks a big button on the (already overfilled) page that we know all editors are going to see. There is no way this can be turned on without a community discussion unless you want a raging storm of anger hurled in the direction of whoever hits the big red button. *The UI elements clash with current thinking about the direction that we're going in. The Micro Designs Improvement project is currently working on the edit window as we speak, and plans to do a couple more iterations given the opportunity. I'd rather not throw two competing philosophies of design into the mix - that works if they're from the same team, but I worry we'd end up with (at best) an inconsistent UI. *This really doesn't seem an efficient way to do things. What's the use case here, exactly? If it's "people would like to save a draft in case they lose their work", save the draft automatically after [number] of minutes or seconds rather than requiring them to actually make a decision, and then just void any drafts after [other number] of minutes or seconds. If it's "we want to sort how confusing the existing setup is by offering functions found on other sites", integrate that into the existing workflows to avoid button bloat. At https://www.mediawiki.org/wiki/Extension:Drafts I'm seeing edge cases discussed and the workflow discussed...but not how this in any way can be integrated into how Wikipedia currently works, or how we'd like it to work, or what exactly the use case is for this software. If there is a use case, it needs to be communicated. If there isn't, we shouldn't be turning it on. On 15 September 2012 21:56, Steven Walling <swalling(a)wikimedia.org> wrote: -- Oliver Keyes Community Liaison, Product Development Wikimedia Foundation _______________________________________________ Design mailing list Design(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design

On Sep 16, 2012, at 7:52 PM, Sumana Harihareswara <sumanah(a)wikimedia.org> wrote: Exactly this. --- Brandon Harris, Senior Designer, Wikimedia Foundation Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate _______________________________________________ Design mailing list Design(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design