Hi Quim,
If it's possible to have a remote unconference session about this topic as
a part of the WDS, I'd be game for that.
I'm very interested in having a much better system for communication about
UX changes than seems to exist today, but I need to be cautious about
taking on this topic as a
On Tue, Dec 20, 2016 at 5:01 AM, Pine W wrote:
> Hi Quim,
>
> Would it be possible to set up a 60-minute Hangouts or Zoom meeting to
> discuss this set of issues (UX change communications, possibly aided by the
> newsletter extension and/or a wiki page with some kind of UX
Hi Quim,
Would it be possible to set up a 60-minute Hangouts or Zoom meeting to
discuss this set of issues (UX change communications, possibly aided by the
newsletter extension and/or a wiki page with some kind of UX checkpoint)?
If so, perhaps you and I could have an off-list discussion to find
On Sat, Dec 17, 2016 at 4:38 AM, Pine W wrote:
> The Newsletter extension could be useful in all kind of ways, and I
> was glad to see that it's apparently still in active development.
>
Oh yes, check https://phabricator.wikimedia.org/project/profile/888/
It would be
Quim,
I like your line of thought here.
The Newsletter extension could be useful in all kind of ways, and I
was glad to see that it's apparently still in active development.
It would be helpful for me to have proposals shown in the newsletter
divided by approximate time horizon (next week, next
On Fri, Dec 16, 2016 at 2:16 PM, Quim Gil wrote:
> Imagine the same approach for new projects/features, security reviews, new
> betas, release plans... This is a good way to scale communications without
> drowning central spaces like Tech News, wikitech-ambassadors or your
>
On Fri, Dec 16, 2016 at 12:51 AM, Pine W wrote:
> The issue which I am attempting to address is not a UI change itself
> (good or bad) but rather communication about proposed and upcoming UI
> changes.
Communication of proposals and changes is a problem indeed. Not just
On Fri, 16 Dec 2016, at 04:18 PM, Gergo Tisza wrote:
> * write a detailed list of everything you intend to do in March
> * in that month, avoid doing anything that you did not think to put on
> that list
> I think you will gain some insights about the cost of trying to organize
> things far ahead
On Thu, Dec 15, 2016 at 3:51 PM, Pine W wrote:
> My proposal would be that proposed UI changes which affect large
> proportions of the user base should be announced 3 months in advance.
>
So here is a fun experiment:
* choose an activity you do a lot (say, editing Wikipedia
On Fri, Dec 16, 2016 at 6:50 AM, Tyler Romeo wrote:
> On Thu, Dec 15, 2016 at 6:51 PM, Pine W wrote:
>
> > My proposal would be that proposed UI changes which affect large
> > proportions of the user base should be announced 3 months in advance.
> >
On Thu, Dec 15, 2016 at 6:51 PM, Pine W wrote:
> My proposal would be that proposed UI changes which affect large
> proportions of the user base should be announced 3 months in advance.
> This would provide plenty of opportunity for discussion,
> synchronization, and testing
(Now forking this from the "Changes in colors of user interface" thread.)
Hi Adam,
Thanks for your email.
I don't think that our interface evolves particularly rapidly, our
interface makes me feel like it's 2003 again. I'd like to have our
interface's usability and our workflows be much easier
quote name=Brian Wolff date=2014-02-16 time=18:00:29 -0400
On Feb 16, 2014 2:04 PM, Jon Robson jdlrob...@gmail.com wrote:
Brad since you work for the for the foundation and seem to have a lot of
expertise in this area and seem to have been one of the more vocal
supporters of free fonts
On Sun, Feb 16, 2014 at 6:36 PM, Greg Grossmeier g...@wikimedia.org wrote:
See also: The general rule among many engineering departments at WMF is
If it didn't happen on the list (or somewhere similarly public and
indexable) it didn't happen.
The team I most recently heard champion that rule
On Sun, Feb 16, 2014 at 3:36 PM, Greg Grossmeier g...@wikimedia.org wrote:
See also: The general rule among many engineering departments at WMF is
If it didn't happen on the list (or somewhere similarly public and
indexable) it didn't happen.
Wikitech is great for discussing things with a
Firstly apologies if my mail was read as public discussions = bad. That was
not my intention. The fact I am on a vacation and writing emails on a phone
with a heavily bandaged hand (which hurts when i type) surely shows I care
a lot about this matter (and the fact that I am doing so on a phone
On Feb 16, 2014 4:01 PM, Steven Walling steven.wall...@gmail.com wrote:
On Sun, Feb 16, 2014 at 3:36 PM, Greg Grossmeier g...@wikimedia.org
wrote:
See also: The general rule among many engineering departments at WMF is
If it didn't happen on the list (or somewhere similarly public and
On Sun, Feb 16, 2014 at 4:00 PM, Steven Walling steven.wall...@gmail.comwrote:
Wikitech is great for discussing things with a wider audience especially
where we need to seek opinions of developers outside the staff.
Which is basically almost always :)
No one is suggesting that we should
Following my my previous mail Attention developers in which I made wrong
assumptions. Let's do some discussion first.
So, before I go further I'm trying to get a sense of what is currently
going on. And hopefully the problems and gaps will uncover themselves as we
go.
I wrote a page on mw.org
19 matches
Mail list logo