Hi all,
Some months ago we started to define a statement of purpose for design at
Wikimedia. We shared our initial iteration and got useful feedback. Based
on that feedback, we have updated a new version:
https://www.mediawiki.org/wiki/Design/Statement_of_purpose
Please, feel free to check the up
Thank you Pau, and to all of the folks involved in the process. In addition
to the UX designers, design researchers, UX engineers, and brand folks in
communications, the Team Practices Group and Community Liaisons were
intimately involved. Internal stakeholders and folks from the broader
community
(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 f
Thank you for this e-mail. It was informative.
Stas Malyshev wrote:
>No, and there are tricky parts there. Consider
>https://www.wikidata.org/wiki/Q735712. Yes, Lex Luthor held the office
>of the President of the USA. In a fictional universe, of course. But the
>naive query - every Wikidata item w
Hi everyone,
The Community Tech team is happy to announce the top 10 wishes from the
2016 Community Wishlist Survey!
More than 1,100 people participated in the survey this year -- proposing,
discussing and voting on 265 ideas. There was a two-week period in November
to submit and discuss proposal
Hi!
> Sure, but I'm not really worried about potential false positives. I'm
> worried that we're building a giant write-only data store.
Fortunately, we are not doing that.
>> Unless you're talking about pulling a small set of values, in which case
>> Lua/templates are probably the best venue.
>
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 of proposed changes.
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.
> > This would provide plenty of opportunity for d
TL;DR: The ONLY practical solution today it to use Lua.
This sucks,but it works and scale well [in WP sense] - hewiki uses it
heavily in infoboxs - to show list of actors in movies, or musical band
members etc.
Long version:
Actually, specifically for list of presidents you don't need bot.
Here is
Hi!
> Actually, specifically for list of presidents you don't need bot.
Yeah, you are right, I was thinking about going through query route, but
if your list is contained in one property (like Q30/P6) then using Lua
is just fine. It's not always the case (e.g. "list of all movies where
Brad Pitt
Forwarding Katherine's email because this may also be of interest to
technical audiences and Wikimedia affiliates who don't subscribe to
Wikimedia-l. Also including Research-l because the strategy process
will likely be influenced by existing research, and may involve new
research initiatives.
Pin
On Wed, Dec 14, 2016 at 11:06 AM, Grace Gellerman
wrote:
> * Eileen published our first real CiviCRM extension to
> https://civicrm.org/extensions/unsubscribe-email-data-entry-screen
> ** existing extensions are all actually Drupal modules, not publicized
> except in gerrit
> ** hope more of our
12 matches
Mail list logo
