[Wikimedia-l] Wikimedians of Colorado User Group Annual Report 2019

2020-07-06 Thread Isarra Yos
Wikimedians of Colorado is proud to announce we've published our report 
for the past year. See it here:


https://meta.wikimedia.org/wiki/Wikimedians_of_Colorado_User_Group/Annual_Report_2019

I'd make a joke about it being the world's shortest report, but I'm sure 
we'll really outdo ourselves with the next one, the way this year is 
going, and probably have a fair bit of competition from some of the 
other regional groups as well. Nothing wrong with that, though. Lots of 
other ways for folks to keep involved in the meantime!


Thanks, y'all.

-Isarra


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Final report for the third round of WikiProject X

2019-09-29 Thread Isarra Yos
I've submitted my final report for the third grant-funded round of 
WikiProject X.


This round of the project was intended to see through finalising current 
development in order to fully deploy CollaborationKit, a MediaWiki 
extension intended to overhaul how users maintain and interact with 
WikiProjects, to the English Wikipedia. Unfortunately, this goal was not 
met, as the proposed scope exceeded the resources allocated, and I am 
not planning to resume work on it for the foreseeable future.


I feel that it is important that we honestly share what we have learned 
from this, however, as best to help others avoid making the same 
mistakes we did:


 * To view our final report:
   
https://meta.wikimedia.org/wiki/Grants:Project/WikiProject_X/CollaborationKit_MVP/Final
 * For more information about CollaborationKit itself, please see
   https://www.mediawiki.org/wiki/Help:Extension:CollaborationKit

Thanks,

-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] [Wikimania-l] Wikimania 2019 Early Bird Registration is Now Open!

2019-05-31 Thread Isarra Yos
Are there any plans to add ticket options that are more affordable, 
especially for volunteers?


Even with Early Bird discount, $270 is... a lot, frankly (and after 
today, $375). Prior to Montreal two years ago (Cape Town last year was 
also similarly expensive), the registration cost of Wikimanias for 
Wikimedia contributors was generally in the 30-50€ range for the whole 
event - even Esino Lario, where food and full accommodation were 
included in the default ticket, also had a 'simple' ticket option 
skipping this that was still in the usual price range. Is there any 
chance we could bring this practice back? Or... something?


This isn't even just that I can't afford this (which I can't - the 
registration costs more than the plane ticket would), /a lot of us/ 
probably aren't going to be able to. Wikimania isn't like most 
conferences, where attendees are being sent by their companies or 
organisation; many of us who would consider going are individuals. Not 
only do we not necessarily have any larger organisations to fund our 
attendance, we're largely not getting paid for any of this, either - 
we're donating our time to be a part of this movement, and now we're 
expected to pay hundreds of dollars, as community members, to attend an 
event that used to be specifically for the community?


This is especially going to be a major turnoff to any newcomers, as it 
precludes people just registering and checking it out, seeing what's up, 
unless they have a lot of money to throw around on things they're not 
sure about. And based on the conversations I've had with various 
newcomers over the years who have been drawn into such events (previous 
wikimanias, hackathons, other conferences) and been highly engaged and 
inspired by their experiences, this is apt to be a major loss.


I'll also note that while scholarships do resolve this issue for some 
people, the scholarship budget is limited, and also generally focussed 
on travel and accommodation costs for folks who would otherwise not be 
able to get there, not attendance costs for people who can get there 
just fine but would prefer to spend that 250€ on something else, like a 
couple of months of groceries. There wasn't a 'just cover the 
registration fee' option with the scholarship applications at all. Not 
that... there should be?


Basically, would it be possible to maybe get some more options here?

-I

On 24/05/2019 23:33, Isabel Cueva wrote:
Great News! The Wikimania discount registration 'early bird' price 
period has been extended to May 31st! Details: 
https://wikimania.wikimedia.org/wiki/2019:Registration


Also, don’t forget: If you want to make a presentation, run a 
workshop, or display a poster during Wikimania, the Call for 
Submissions is NOW OPEN 



On Fri, May 17, 2019 at 10:22 AM Isabel Cueva > wrote:


Attention Everyone (and please spread the word):


Early Bird Registration is now open for Wikimania 2019 on our
Eventbrite
page.


This discount pricing ends on May 24th so don’t delay!

Online registration will be open from today to July 30th, 2019.


For more information please visit:
https://wikimania.wikimedia.org/wiki/Registration


Wikimania 2019 will be held at Stockholm University
, Sweden
, from 14th to 18th August 2019.


The venue will host the majority of the conference, hackathon,
meetups, and pre-events.


We would like to encourage all speakers and attendees to register
early and book their flight and travel as soon as possible. If you
have questions about visas, please visit our wiki visa page
.


If you have any questions with regard to the conference, please
contact:

wikimania-i...@wikimedia.org 


Don’t forget: If you want to make a presentation, run a workshop,
or display a poster during Wikimania, the Call for Submissions is
NOW OPEN 



We hope you can join us in Stockholm this summer!



Isabel Cueva, WMF Event Program Manager

on behalf of the Wikimania ‘19 Organizing Team



-- 
	*Isabel Cueva*

Event Program Manager
Wikimedia Foundation 



--
*Isabel Cueva*
Event Program Manager
Wikimedia Foundation 


___
Wikimania-l mailing list
wikimani...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimania-l



___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 

Re: [Wikimedia-l] Thank you and farewell

2019-05-16 Thread Isarra Yos

On 16/05/2019 23:29, Joseph Fox wrote:

Maybe let's not turn this into a debate about what epistemology is.


Would this really be the Wikimedia we all know and love if we didn't?

Regardless, I'm glad Sati took the time to write this up. I thought it 
was an excellent description of just how truly terrible and wonderful 
things can be around here, and such poetry put to words only does us 
good, really. Now let's bikeshed!


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Annual report for Wikimedians of Colorado User Group for 2018

2019-04-03 Thread Isarra Yos

Hello from Colorado!

We're happy to present our annual report for the past year! Please see: 
https://meta.wikimedia.org/wiki/Wikimedians_of_Colorado_User_Group/Annual_Report_2018


We may be scattered across something like five totally different cities, 
but we do stuff.


Thanks, all! For the Wikimedians of Colorado, annual reportingly yours,

Isarra


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Suspensions of affiliates

2018-09-19 Thread Isarra Yos
Also apt to be useful information for other affiliates - oh, they did or 
didn't do blah and it added up to serious problems; we've been heading 
in that sort of direction too and should probably stop, or similar - 
often it's things we can all learn from, so if presented as such and 
handled consistently, there need not be shame in it.


On 19/09/2018 02:49, Pine W wrote:

I have several thoughts regarding this and related issues, but my main
feeling is that we should not hide news that would be in the public
interest to communicate, such as the suspension of an affiliate or an
investigation into an affiliate's use of trademarks, simply because it is
bad news or embarrassing news.

There are good reasons to keep certain information private, such as
preparations for pending litigation or personally identifying information
that has not been made public. The potential for negative publicity if
information is published, such as the suspension of an affiliate, isn't
sufficient justification for keeping information private.

Good governance is difficult to do if relevant information is kept private.
One of the benefits of having news regarding official actions be public is
that the public can evaluate the performance of the officials (in this
case, Affcom). Transparency is a useful deterrent against favoritism,
negligence, and other problems in public service organizations in general.
I generally want transparency regarding both the official actions of
affiliates and the official actions of Affcom. I would like Affcom to set
an example of being transparent by default, whether news is good or bad.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 





___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Wikimedians of Colorado User Group annual report 2017

2018-08-29 Thread Isarra Yos

Hey all,

The Wikimedians of Colorado User group has published our annual report 
for 2017, so please check it out here:

https://meta.wikimedia.org/wiki/Wikimedians_of_Colorado_User_Group/Annual_Report_2017

Thanks!

-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] C-team Statement on the Code of Conduct

2018-08-14 Thread Isarra Yos

Sorry, I apparently replied to the wrong mailing list.

On 14/08/18 18:19, Isarra Yos wrote:
As a total random, I'd also like to second this - as much as I think 
the CoC and the committee in particular have room to improve in how 
things are handled, this will never happen without proper support for 
the work they're doing in the first place.


While some of us have been somewhat flabbergasted by specific events, 
these are after all the people we need to be working with to actually 
resolve the issues at hand, and indeed the events (and handling 
thereof) themselves have also highlighted the need for more clearer 
standards moving forward. I'm glad to see some steps have already been 
taken. Let's continue in this vein.


Thank you!

-I

On 14/08/18 18:08, Amir Ladsgroup wrote:

Hey,
As a member of Code of conduct committee I just wanted to express how 
much

I appreciate your statement. The work we are doing is not fun, we are
dealing with frustrations, harassments, trolling, and all sorts of 
the dark

side of the Wikimedia movement but I genuinely believe that this type of
work is vital to keep the movement moving forward, to make us more
welcoming and foster a diverse environment.

All of the support I've received, private and public, online and 
offline is

overwhelming. Thank you, Thank you, Thank you.

Best
On Tue, Aug 14, 2018 at 7:46 PM Victoria Coleman 


wrote:


Hello everyone,

The executive leadership team, on behalf of the Foundation, would 
like to
issue a statement of unequivocal support for the Code of Conduct[1] 
and the
community-led Code of Conduct Committee. We believe that the 
development

and implementation of the Code are vital in ensuring the healthy
functioning of our technical communities and spaces. The Code of 
Conduct
was created to address obstacles and occasionally very problematic 
personal
communications that limit participation and cause real harm to 
community
members and staff. In engaging in this work we are setting the tone 
for the
ways we collaborate in tech. We are saying that treating others 
badly is
not welcome in our communities. And we are joining an important 
movement in

the tech industry to address these problems in a way that supports
self-governance consistent with our values.

This initiative is critical in continuing the amazing work of our 
projects
and ensuring that they continue to flourish in delivering on the 
critical

vision of being the essential infrastructure of free knowledge now and
forever.

Toby, Maggie, Eileen, Heather, Lisa, Katherine, Jaime, Joady, and 
Victoria



https://www.mediawiki.org/wiki/Code_of_Conduct <
https://www.mediawiki.org/wiki/Code_of_Conduct>




___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l

New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: 
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>






___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] C-team Statement on the Code of Conduct

2018-08-14 Thread Isarra Yos
As a total random, I'd also like to second this - as much as I think the 
CoC and the committee in particular have room to improve in how things 
are handled, this will never happen without proper support for the work 
they're doing in the first place.


While some of us have been somewhat flabbergasted by specific events, 
these are after all the people we need to be working with to actually 
resolve the issues at hand, and indeed the events (and handling thereof) 
themselves have also highlighted the need for more clearer standards 
moving forward. I'm glad to see some steps have already been taken. 
Let's continue in this vein.


Thank you!

-I

On 14/08/18 18:08, Amir Ladsgroup wrote:

Hey,
As a member of Code of conduct committee I just wanted to express how much
I appreciate your statement. The work we are doing is not fun, we are
dealing with frustrations, harassments, trolling, and all sorts of the dark
side of the Wikimedia movement but I genuinely believe that this type of
work is vital to keep the movement moving forward, to make us more
welcoming and foster a diverse environment.

All of the support I've received, private and public, online and offline is
overwhelming. Thank you, Thank you, Thank you.

Best
On Tue, Aug 14, 2018 at 7:46 PM Victoria Coleman 
wrote:


Hello everyone,

The executive leadership team, on behalf of the Foundation, would like to
issue a statement of unequivocal support for the Code of Conduct[1] and the
community-led Code of Conduct Committee. We believe that the development
and implementation of the Code are vital in ensuring the healthy
functioning of our technical communities and spaces. The Code of Conduct
was created to address obstacles and occasionally very problematic personal
communications that limit participation and cause real harm to community
members and staff. In engaging in this work we are setting the tone for the
ways we collaborate in tech. We are saying that treating others badly is
not welcome in our communities. And we are joining an important movement in
the tech industry to address these problems in a way that supports
self-governance consistent with our values.

This initiative is critical in continuing the amazing work of our projects
and ensuring that they continue to flourish in delivering on the critical
vision of being the essential infrastructure of free knowledge now and
forever.

Toby, Maggie, Eileen, Heather, Lisa, Katherine, Jaime, Joady, and Victoria


https://www.mediawiki.org/wiki/Code_of_Conduct <
https://www.mediawiki.org/wiki/Code_of_Conduct>




___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 





___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] New Wikimedia Foundation has soft launched!

2018-08-02 Thread Isarra Yos
Is there any way for us (others outside the team) to file bulk 
tasks/apply fixes to this? Is the source in gerrit/tasks tracked in 
phabricator, or is it somewhere else?


-I

On 02/08/18 01:51, Gregory Varnum wrote:

Hello,

After many months of work by over 100 individuals around the organization and 
movement, the Wikimedia Foundation's new website soft launched this week!

You can check it out for yourself here (you may need to clear your browser's 
cache):  https://wikimediafoundation.org/


So what comes next?

Throughout this week, the Communications department and core website team will 
be doing final tweaks and quality assurance testing in preparations for 
translations.

Over the coming weeks we will be working with affiliates and contributors 
around the world to make the site in available in Arabic, Chinese, French, 
German, Russian, and Spanish - in addition to the English version soft launched 
today. Once the translations are completed, we will be doing a more public 
announcement regarding the new website and begin more formally implementing 
usage of it.

Additionally, we will be holding office hours in the coming weeks.


What about the old website?

The old website (aka Foundation Wiki) will be given new life in the coming 
weeks as the Wikimedia Foundation Governance Wiki - where it will continue to 
house important documentation for the Wikimedia Foundation like policies, board 
resolutions and minutes, legal documents, etc. Additional information on the 
changes coming to that wiki and the plans for migrating archived content to 
Meta-Wiki will be available in the coming weeks.


What else should I know?

There is a lot of great things about this new website we are excited to share 
with all of you! More information about office hours will available in the 
coming weeks. Until then, we encourage you to take a look and contact me 
directly if you find any bugs, typos, or have any comments.


Thank you!

The Communications department greatly appreciates all of the discussions, work, 
and patience everyone has put into this gigantic undertaking. We are very close 
to the finish line, and today marks a significant step which was only possible 
with the help of the 100+ people involved.

On behalf of the Communications department and core website team (Heather, 
Zack, Katherine, Mel, and Greg),

-greg

---
Gregory Varnum
Communications Strategist
Wikimedia Foundation
gvar...@wikimedia.org
Pronouns: He/Him/His


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 





___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Timeless Newsletter

2018-07-20 Thread Isarra Yos

Hey all,

For anyone not familiar, the Timeless skin has been available as an 
option on Wikimedia wikis since november or so, and development of the 
skin is now being funded by a Project Grant. If you're interested in 
receiving updates about this, I've created a newsletter which should be 
going out monthly.


You can sign up for the newsletter here: 
https://meta.wikimedia.org/wiki/Timeless/Newsletter
Or read the first issue: 
https://meta.wikimedia.org/wiki/Timeless/Newsletter/1


Timeless: https://www.mediawiki.org/wiki/Skin:Timeless?useskin=timeless
The grant now funding this: 
https://meta.wikimedia.org/wiki/Grants:Project/Isarra/Timeless:_Post-deployment_support


Thank you to everyone for your interest and support thus far, and making 
all of this possible!


-Isarra

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: Appropriation of the Wikimedia Blog by the WMF

2018-06-10 Thread Isarra Yos

On 10/06/18 05:01, Natacha Rault wrote:

Have a nice day, I have just bought myself a canoe kayak, which is the only way 
for me not to get entangled in contributing on a bright sunny day.
I cant bring my computer on the river!


Yes you can, if you have the money for it. They make waterproof computers.

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] WikiProject X followup grant to fund finalising CollaborationKit

2018-02-13 Thread Isarra Yos

Hey all,

I'm pleased to announce a proposed followup for WikiProject X, a project 
previously funded by an Individual Engagement Grant. I have now 
submitted a Project Grant, according to the new system, with which I 
intend to complete and fully assess the development of CollaborationKit, 
the extension James Hare, Brian Wolff, and I created in 2016 in the 
renewal round of the original grant to facilitate the creation, 
management, and usage of WikiProjects on the English Wikipedia.


While the CollaborationKit extension is largely complete as a 
functioning prototype, it has yet to be deployed to the target wiki, the 
English Wikipedia (while technically in production, at present it's only 
enabled on testwiki). Subsequent to that deployment, actual testing can 
begin, and only then will it be possible to iterate on the extension's 
layout and functionality to effectively address the needs and pitfalls 
that come up in practice. Only then, too, will we be able to effectively 
assess the overall project: how successful has WikiProject X, as both 
IEG and Project Grant, been at meeting the outcomes originally 
described? How effective is this kind of design and software project as 
a whole? What can we learn, and how can others learn from this approach?


I would like to invite anyone interested in the project to check out the 
new proposal, and to comment or ask any questions you might have: 
https://meta.wikimedia.org/wiki/Grants:Project/Isarra/WikiProject_X


For more information on the original grant: 
https://meta.wikimedia.org/wiki/Grants:IEG/WikiProject_X
WikiProject X on the English Wikipedia: 
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_X

CollaborationKit: https://www.mediawiki.org/wiki/Extension:CollaborationKit

Thanks!

Isarra

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Timeless grant resubmission

2018-02-12 Thread Isarra Yos

Hey all,

As many of you know, the Timeless skin was deployed for testing across 
all Wikimedia projects in late November last year. I submitted a Project 
Grant proposal at the time seeking funding to more actively support for 
this deployment as well as enable further development based on user 
feedback and the bugs that have been coming up in practice, but the 
proposal was ultimately vetoed in the late stages due to objections from 
WMF staff.


It is my understanding that these objections have since been withdrawn, 
and based on what happened, I have been recommended by relevant WMF 
staff to resubmit the proposal in the subsequent, now current, round of 
Project Grants. I have done this, and would like to invite anyone 
interested in this project to comment (again, even) on the current 
proposal, or ask any questions you might have on the talkpage. The 
current proposal can be found here: 
https://meta.wikimedia.org/wiki/Grants:Project/Isarra/Timeless:_Post-deployment_support


As for some general background:

If you don't know me, I'm Isarra, a volunteer MediaWiki developer and 
designer, and a previous WMF grantee on another project, WikiProject X. 
I originally created the Timeless skin itself as a volunteer project for 
a Wikimedia Tech Talk in 2015; after that the skin just sort of sat 
there being ignored for the better part of 2016, and then Paladox found 
it, filed a bug saying it should be deployed to Wikimedia, and it turned 
out a lot of people agreed with him and we spent most of 2017 pushing it 
through various processes, reviews, and fixes to be deployed 
(https://phabricator.wikimedia.org/T154371).


If you haven't and would like to try out Timeless, you can enable it in 
your preferences under Appearance > Skin, or just add ?useskin=timeless 
to the end of most page URLs to see what that page looks like in Timeless.


Thanks,

Isarra

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: [PRESS] Turkish authorities block Wikipedia

2017-04-30 Thread Isarra Yos
This is a great way for them to ensure the rest of the world sees those 
articles. Sort of. Bit inconveniencing to everyone actually IN Turkey...


-I

On 30/04/17 12:40, geni wrote:

FWIW the two articles the Turkish state is apparently complaining about are:

https://en.wikipedia.org/wiki/State-sponsored_terrorism#Turkey

https://en.wikipedia.org/wiki/Foreign_involvement_in_the_Syrian_Civil_War#Turkey





___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Timeless: a grant proposal

2017-04-01 Thread Isarra Yos
Isn't Wikidata mostly just used for language links on Wikimedia 
projects? That doesn't really affect the skin much.


-I

On 01/04/17 10:01, Szymon Grabarczuk wrote:

Gerard mentioned Wikidata, which collects interwiki and is a cross-wiki
database, so to me it's clear that by "multiple projects" he meant just
Wikimedia projects. This is specifically about focusing on cross-wiki
collaboration.

Well, an interesting point. That issue is one of main points of our
strategy consultations.

*Szymon Grabarczuk*

Free Knowledge Advocacy Group EU
Head of R Group, Wikimedia Polska
pl.wikimedia.org/wiki/User:Tar_Lócesilion
<http://pl.wikimedia.org/wiki/User:Tar_L%C3%B3cesilion>

On 1 April 2017 at 05:18, Isarra Yos <zhoris...@gmail.com> wrote:


I'm a bit confused what you're asking. My proposal should be covering
exactly what I aim to achieve. What, specifically, is unclear? Let me know
and I'll do what I can to improve it.

By 'other projects' do you mean third-party MediaWiki installs? I'm afraid
right now the scope of the grant really only covers usage on Wikimedia
projects, though wider applicability and adoption of Timeless is of course
something quite important to me personally, and I'm glad to see interest on
this list.

-I


On 29/03/17 07:02, Gerard Meijssen wrote:


Hoi,
What remains unclear is what it is that you aim to achieve. There are
great
possibilities possible but there has to be a focus.

One such focus would be that it helps us focus on the relations that an
article has with with other articles. They are all or should all be
related
in Wikidata anyway. With a skin that helps in determining this you have a
reason for another skin, a skin that will achieve greater quality for
multiple projects. The only question I have is how your skin would work
for
other projects.
Thanks,
   GerardM

On 29 March 2017 at 04:01, Isarra Yos <zhoris...@gmail.com> wrote:

Hi,

I'm Isarra, a volunteer MediaWiki developer, and I've submitted a grant
proposal to the WMF to support my work on a new responsive skin designed
for the Wikimedia projects, Timeless:

* Abstract: A new skin, Timeless, has been deployed to the Beta Cluster,
but to make it worth eventual deployment to all projects, we need proper
research into what's expected/needed from a better skin, and the ability
to
devote development resources to making it meet these expectations/needs.
This grant, as part of a larger series of vaguely planned grants intended
to work on many of the underlying issues with MediaWiki's user-facing
interfaces, will serve to address this need.
* https://meta.wikimedia.org/wiki/Grants:IdeaLab/Timeless

Timeless currently exists as fairly basic prototype, but I invite you to
take a look at the current version:

* Wiki specifically for Timeless: https://timeless-skin.wmflabs.
org/wiki/Main_Page
* To see what it might look/act like in production, there is a copy of
the
Simple English Wikipedia on the Beta Cluster, where Timeless has already
been deployed: https://simple.wikipedia.beta.wmflabs.org/wiki/Main_Page
-
you can create an account, set your skin to Timeless, and go through some
of the things you might do here, or simply append the string
?useskin=timeless to the end of any page url to see what it would look
like
in Timeless
* Skin documentation: https://www.mediawiki.org/wiki/Skin:Timeless

If this looks like a project you would be interested in seeing happen, I
would very much appreciate your feedback. This applies especially if you
have any specific concerns about the skin or the proposal itself, or have
faced particular problems on your own projects that you think this might
be
able to address, because the more of these are documented, the better
they
will be.

I look forward to working with all of you to redefine how we handle our
project interfaces.

Thanks,

Isarra


___
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wik
i/Mailing_lists/Guidelines
and https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>


___
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wik
i/Mailing_lists/Guidelines and https://meta.wikimedia.org/wik
i/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>




___
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wik
i/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ

Re: [Wikimedia-l] Timeless: a grant proposal

2017-03-31 Thread Isarra Yos
I'm a bit confused what you're asking. My proposal should be covering 
exactly what I aim to achieve. What, specifically, is unclear? Let me 
know and I'll do what I can to improve it.


By 'other projects' do you mean third-party MediaWiki installs? I'm 
afraid right now the scope of the grant really only covers usage on 
Wikimedia projects, though wider applicability and adoption of Timeless 
is of course something quite important to me personally, and I'm glad to 
see interest on this list.


-I

On 29/03/17 07:02, Gerard Meijssen wrote:

Hoi,
What remains unclear is what it is that you aim to achieve. There are great
possibilities possible but there has to be a focus.

One such focus would be that it helps us focus on the relations that an
article has with with other articles. They are all or should all be related
in Wikidata anyway. With a skin that helps in determining this you have a
reason for another skin, a skin that will achieve greater quality for
multiple projects. The only question I have is how your skin would work for
other projects.
Thanks,
  GerardM

On 29 March 2017 at 04:01, Isarra Yos <zhoris...@gmail.com> wrote:


Hi,

I'm Isarra, a volunteer MediaWiki developer, and I've submitted a grant
proposal to the WMF to support my work on a new responsive skin designed
for the Wikimedia projects, Timeless:

* Abstract: A new skin, Timeless, has been deployed to the Beta Cluster,
but to make it worth eventual deployment to all projects, we need proper
research into what's expected/needed from a better skin, and the ability to
devote development resources to making it meet these expectations/needs.
This grant, as part of a larger series of vaguely planned grants intended
to work on many of the underlying issues with MediaWiki's user-facing
interfaces, will serve to address this need.
* https://meta.wikimedia.org/wiki/Grants:IdeaLab/Timeless

Timeless currently exists as fairly basic prototype, but I invite you to
take a look at the current version:

* Wiki specifically for Timeless: https://timeless-skin.wmflabs.
org/wiki/Main_Page
* To see what it might look/act like in production, there is a copy of the
Simple English Wikipedia on the Beta Cluster, where Timeless has already
been deployed: https://simple.wikipedia.beta.wmflabs.org/wiki/Main_Page -
you can create an account, set your skin to Timeless, and go through some
of the things you might do here, or simply append the string
?useskin=timeless to the end of any page url to see what it would look like
in Timeless
* Skin documentation: https://www.mediawiki.org/wiki/Skin:Timeless

If this looks like a project you would be interested in seeing happen, I
would very much appreciate your feedback. This applies especially if you
have any specific concerns about the skin or the proposal itself, or have
faced particular problems on your own projects that you think this might be
able to address, because the more of these are documented, the better they
will be.

I look forward to working with all of you to redefine how we handle our
project interfaces.

Thanks,

Isarra


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
and https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>




___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Timeless: a grant proposal

2017-03-28 Thread Isarra Yos

Hi,

I'm Isarra, a volunteer MediaWiki developer, and I've submitted a grant 
proposal to the WMF to support my work on a new responsive skin designed 
for the Wikimedia projects, Timeless:


* Abstract: A new skin, Timeless, has been deployed to the Beta Cluster, 
but to make it worth eventual deployment to all projects, we need proper 
research into what's expected/needed from a better skin, and the ability 
to devote development resources to making it meet these 
expectations/needs. This grant, as part of a larger series of vaguely 
planned grants intended to work on many of the underlying issues with 
MediaWiki's user-facing interfaces, will serve to address this need.

* https://meta.wikimedia.org/wiki/Grants:IdeaLab/Timeless

Timeless currently exists as fairly basic prototype, but I invite you to 
take a look at the current version:


* Wiki specifically for Timeless: 
https://timeless-skin.wmflabs.org/wiki/Main_Page
* To see what it might look/act like in production, there is a copy of 
the Simple English Wikipedia on the Beta Cluster, where Timeless has 
already been deployed: 
https://simple.wikipedia.beta.wmflabs.org/wiki/Main_Page - you can 
create an account, set your skin to Timeless, and go through some of the 
things you might do here, or simply append the string ?useskin=timeless 
to the end of any page url to see what it would look like in Timeless

* Skin documentation: https://www.mediawiki.org/wiki/Skin:Timeless

If this looks like a project you would be interested in seeing happen, I 
would very much appreciate your feedback. This applies especially if you 
have any specific concerns about the skin or the proposal itself, or 
have faced particular problems on your own projects that you think this 
might be able to address, because the more of these are documented, the 
better they will be.


I look forward to working with all of you to redefine how we handle our 
project interfaces.


Thanks,

Isarra


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] What's making you happy this week? (Week of 19 March 2017)

2017-03-23 Thread Isarra Yos
Two things: VE has gotten really easy to install, as long as you don't 
need the full restbase server (not going into that, not going into that, 
not going into that). Which is really cool for third-party projects and 
such.


Also a pair of ladies with no prior experience or affiliation with 
Wikimedia, Kassondra Cloos of SNEWS and Abigail Wise of Adventure 
Projects, decided to host an editathon in Boulder, and the other day met 
with a few local more experienced Wikimedians (myself included, along 
with two others who actually know about Wikipedia, Todd Allen and Neal 
McBurnett) for planning and to sort out some details of how it's 
actually going to happen, and it looks like it's apt to be a very 
productive event. The thing's going to be on Sunday. Exciting stuff.


-I

On 22/03/17 20:37, Pine W wrote:

Borrowing an idea from Wikipedia Weekly, I think it would be nice to have a
thread about the good things that are happening around the Wikimedia
universe. If people enjoy this then it can be started (by anyone) on a
weekly basis.

My comment for this week: I enjoyed reading a post from the Wikimedia blog:
https://blog.wikimedia.org/2017/03/21/why-i-elements/: "Why I periodically
write about the elements on Wikipedia", by Mikhail Boldyrev.

Pine
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 





___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Status of the Code of Conduct for technical spaces

2017-03-11 Thread Isarra Yos

On 09/03/17 20:36, Antoine Musso wrote:

The RfC has been going on for almost two years already. Given the flood
of announces on a wide range of mailing lists, I don't see how one could
have missed it. 


The flood might be exactly how. Keep being inundated with notices, many 
people are likely to just start ignoring all of the notices. This is a 
problem for a lot of things, though.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Draft Code of Conduct for Technical Spaces

2017-02-26 Thread Isarra Yos

On 26/02/17 18:21, MZMcBride wrote:

Then you and others should have no problem providing specific examples.
I'd like to see links to Gerrit changesets and Phabricator tasks where
this new policy and its committee would help. If you want to make claims
of serious unacknowledged problems, substantiate them with evidence. This
is exactly the same burden of proof you would expect from anyone else.

MZMcBride


I've asked for this before, but got nothing but hypotheticals. It's hard 
to weigh in on a document that does not cite specific examples, with 
context, of what it seeks to address. When designing anything - 
processes, software, architecture - you need to know your use cases in 
order to properly address them. We spent months researching what the 
users were actually doing, and the problems they were running into, 
before we started making anything for WikiProject X. For every decision 
we made, we can point to examples on-wiki of the trends that led us to 
this; or the software limitations; or the fact that it actually was kind 
of arbitrary, and that if any actual reasons to change it are provided, 
this can totally be done.


And this Code of Conduct is much bigger, in both scope and likely 
impact, than WikiProject X.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Invitation to review: Design Statement of Purpose

2016-11-16 Thread Isarra Yos
Okay, so you want to clarify... something, and build trust. What needs 
clarifying? What has been unclear? For whom, and building trust with 
whom? Are these even the right questions?


A problem here, from what you're saying, seems to be that things with 
Design have been historically overly complicated/confused, and there 
hasn't been good communication with other teams, with the community, 
even within Design itself. Though a step in the right direction, this 
seems to me like a continuation of that pattern, frankly. The more big 
words you use, the more passive voice, the more overarching 'themes' and 
less direct problem statements, the more you distance yourselves from 
what you're doing and who you're working with, and I would if anything 
strongly recommend the opposite. Keep it simple.


Your general purpose should be to make things... better. But what that 
means depends on what your problems are, so your problems are what you 
need to do work to sort out. That way you can address the problems, and 
move forward.


So what are the problems? How will you address them? And in order to 
define these problems, for that matter, what's your scope?


-I

On 10/11/16 20:36, Arthur Richards wrote:

Hi Isarra, thanks for the excellent questions. Here's my attempt to answer
them:

The purpose of the statement of purpose is to gain clarity and build trust
within the design group and with their principle stakeholders. With the
statement itself, we seek to gain clarity and shared understanding about
what design at the WMF is here for and trying to achieve (at a big-picture
level). Through the process of defining the statement of purpose, we hope
to build trust amongst the design group and with their principle
stakeholders. So, the primary audience for this document is the design
group itself, with the stakeholders of design being a secondary audience.

Moving forward, that is once the statement of purpose is done, design can
take a close look at where it is now relative to where it wants to be as
defined by the statement of purpose. Design can then use that difference to
help make decisions about how we get from here to there (for instance to
help in making decisions about staffing, structure, involvement in product
teams, how to approach design problems, and so on).

Long story short, the statement of purpose is intended to be an organizing
tool - to create clarity through everyone understanding the purpose, and
trust by going through a collaborative process of definition amongst design
and their stakeholders - so that they can execute better and with decreased
friction.

A little more background and history:
As the Foundation has evolved over the years, there have been many
challenges and pain points around figuring out how design should function
and how it should be integrated into the various facets of the organization
(from product development to communications). Through all of the attempts
to address those challenges and pain points over the years, it's become
clear that the role and purpose of design is not well understood - at least
not in a shared and consistent way, which makes it nearly impossible to
find the right and lasting solutions. A few months ago, the Team Practices
Group was asked to help identify and resolve the major pain points - after
doing research, we agreed in conjunction with the design group that we
should pursue clarifying the purpose of design and validate it with their
stakeholders.

Does this answer your questions?

On Thu, Nov 10, 2016 at 12:24 PM Isarra Yos <zhoris...@gmail.com> wrote:


I'm going to ask this here since the talkpage on-wiki is a flow board
and I find those very difficult to use, but I'm a bit unclear what the
purpose of this is. All the things listed sound good in theory, but the
language is ambiguous and very high level, to the point where it's hard
to see how it applies in practice. Essentially, who is this for? What
are the problems they are trying to address? What are they planning to
do, and what will this mean in practice moving forward?

Thanks.

-I

On 10/11/16 18:40, Keegan Peterzell wrote:

Hello all,

Over the past few months the Design team members at the Wikimedia
Foundation (user experience [UX] designers, design researchers, user
experience engineers, and communications) have been working with Arthur
Richards from the Team Practices Group to identify the high-level themes
that motivate design at the WMF. These themes have been turned into a

brief

statement of purpose, whose intent is to articulate the vision and

purpose

behind design at the WMF. This statement will influence the future
direction of design work.

At this point the stakeholders are ready for a review of the draft
statement. The purpose of this review is to gather a common understanding
of its purpose, and to identify any key themes that may be missing from

the

high-level discussion. On the wiki page for the statement, you'll find
these themes and what they enc

Re: [Wikimedia-l] Invitation to review: Design Statement of Purpose

2016-11-10 Thread Isarra Yos
I'm going to ask this here since the talkpage on-wiki is a flow board 
and I find those very difficult to use, but I'm a bit unclear what the 
purpose of this is. All the things listed sound good in theory, but the 
language is ambiguous and very high level, to the point where it's hard 
to see how it applies in practice. Essentially, who is this for? What 
are the problems they are trying to address? What are they planning to 
do, and what will this mean in practice moving forward?


Thanks.

-I

On 10/11/16 18:40, Keegan Peterzell wrote:

Hello all,

Over the past few months the Design team members at the Wikimedia
Foundation (user experience [UX] designers, design researchers, user
experience engineers, and communications) have been working with Arthur
Richards from the Team Practices Group to identify the high-level themes
that motivate design at the WMF. These themes have been turned into a brief
statement of purpose, whose intent is to articulate the vision and purpose
behind design at the WMF. This statement will influence the future
direction of design work.

At this point the stakeholders are ready for a review of the draft
statement. The purpose of this review is to gather a common understanding
of its purpose, and to identify any key themes that may be missing from the
high-level discussion. On the wiki page for the statement, you'll find
these themes and what they encompass in the "Background" section. If you
have an observation, comment, or concern about what is listed there, please
bring it up on the talk page. If it is relevant to the review and
understanding of the statement, it will be looked at for future drafts. If
there are comments about design and the design process in general, we'll
hold on to those until a time when they can be addressed for the broader
discussion of design in general.

All that said, here are the links:
* 
* 

We look forward to seeing you on the wiki.




___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: [WikimediaMobile] Mobile site is now lazy loading images

2016-09-01 Thread Isarra Yos
On a slow desktop connection, lazy-loading is generally the opposite of 
what you want - unlike mobile, there's usually no data limit, it just 
takes awhile getting the data. A common pattern is thus to start a large 
page loading and then do something else, or just wait for it to finish 
then. It's like buffering video, so that way you have it all there when 
you actually go to it, and when it finishes, it's done. Lazy loading 
prevents such an uninterrupted experience by forcing the user to instead 
sit through every slow-loading image/section, with no way to avoid it.


For mobile, though, where you need to worry about running out of data 
but generally have much faster speeds, lazy loading makes a lot more 
sense. It's great that we have it here!


-I

On 26/08/16 16:47, Jane Darnell wrote:

Interesting to see the drop in bytes sent to the Japan article and this
makes me think we should "fold up" article sections on desktop too for very
long articles, such as the Japan article. The benefits for mobile are
obvious, but this may be beneficial for slow desktop connections as well.

-- Forwarded message --
From: Jon Robson 
Date: Tue, Aug 23, 2016 at 5:20 PM
Subject: [WikimediaMobile] Mobile site is now lazy loading images
To: mobile-l , Wikimedia developers <
wikitec...@lists.wikimedia.org>


FYI after much experimentation, research and testing the mobile site has
been lazy loading images [1] since Thursday 18th August. This means if you
do not see an image you will not download it. We have taken care to ensure
users without JavaScript can still view images and that most users will
barely notice the difference.

We are currently crunching the data this change has made and we plan to
write a blog post to reporting the results.

In our experiments on Japanese Wikipedia we saw a drop in image bytes per
page view by 54% On the Japanese Japan article bytes shipped to users
dropped from 1.443 MB to 142 kB.

This is pretty huge since bytes equate to money [3] and we expect this to
be significant on wikis where mobile data is more expensive. In a nutshell
Wikipedia mobile is cheaper.

As I said blog post to follow once we have more information, but please
report any bugs you are seeing with the implementation (we have already
found a few thanks to our community of editors).

~Jon

[1] https://www.mediawiki.org/wiki/Reading/Web/Projects/
Performance/Lazy_loading_images
[2] https://www.mediawiki.org/wiki/Reading/Web/Lazy_loading_
of_images_on_Japanese_Wikipedia
[3] https://whatdoesmysitecost.com/



___
Mobile-l mailing list
mobil...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 





___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Crisis of Confidence

2016-05-04 Thread Isarra Yos
He isn't asking Dariusz to leave the board, but the position of chair of 
a particular committee on it. While I have no idea if this is called for 
either, it seems an important distinction.


-I

On 03/05/16 04:23, Anthony Cole wrote:

Fae, I can see no reason for Dariusz to leave the board. He seems to be
decent and intelligent. The Arnnon thing was an error but it was clearly
part of a broader problem. Yes, they all need training but that seems to be
in the works. I hope he stays, and is re-elected if he chooses to run next
time.

Anthony Cole


On Tue, May 3, 2016 at 7:09 AM, Nick Wilson (Quiddity) <
nwil...@wikimedia.org> wrote:


On Mon, May 2, 2016 at 2:21 AM, Fæ  wrote:


[...]

With regard to "[the WMF board] delivering services that are of a high

quality", all the metrics that the WMF report show the opposite. The
WMF consistently fail to meet the performance targets they set for
themselves, as you can see from the most recent quarterly report, they
"missed", i.e. "failed", 35% of all their objectives.[3] In the Retail
& Telecoms businesses I have worked in, a pattern of poor performance
like this would see speedy major investment in change and improvement,
including major changes at the board level.
[...]
3.


https://meta.wikimedia.org/w/index.php?title=File:Wikimedia_Foundation_Quarterly_Report,_FY_2015-16_Q2_(October-December).pdf=5



The explanation for this, is at the top of

https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews
: "NB: In a mature 90-day goalsetting process, the “sweet spot” is for
about 75% of goals to be a success. Organizations that are meeting 100% of
their goals are not typically setting aggressive goals."
Note that partial successes are not also represented, if one just checks
the overview result; it's a simple binary system. See the textual notes for
details about partial successes within individual goals.
Plus, not reaching that 75% target of completely-successful goals, is
perhaps also attributable to the intense and widespread stress of that time
period...
Hope that helps.
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,



___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 




___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Recognition of Wikimedians of Colorado User Group

2016-03-08 Thread Isarra Yos

Oh, so we should actually start doing stuff? Oh dear.

I mean, we do stuff. Of course we do stuff.

And thanks everyone!

On 07/03/16 03:18, Alex Wang wrote:

Congrats! Excited to learn more about your activities.

Cheers,

Alex

On Sun, Mar 6, 2016 at 4:15 PM, Sydney Poore  wrote:


Congratulations!! Look forward to hearing more about your projects.

Warm regards,
Sydney
On Mar 6, 2016 4:57 PM, "Carlos M. Colina"  wrote:


Dear all,

On behalf of the Afffiliations Committee, I am glad to announce the
recognition of a new Wikimedia User Group in the United States:

Wikimedians

of Colorado User Group [1]

Among their objectives are organizing meetups of wikimedians in Colorado,
plus organizing events to promote our projects in the state, especially

in

educational institutions and libraries.

Let's give our colleagues a warm welcome! :-)

1: https://meta.wikimedia.org/wiki/Wikimedians_of_Colorado_User_Group
--
"*Jülüjain wane mmakat* ein kapülain tü alijunakalirua jee wayuukanairua
junain ekerolaa alümüin supüshuwayale etijaanaka. Ayatashi waya junain."
Carlos M. Colina
Socio, A.C. Wikimedia Venezuela | RIF J-40129321-2 |

www.wikimedia.org.ve


Member, Wikimedia Foundation Affiliations Committee
Phone: +972-52-4869915
Twitter: @maor_x
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,








___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Outcomes from the Consultation on Wikimedia movement conferences/Wikimania

2016-02-09 Thread Isarra Yos
Interestingly, having them every other year would make it potentially 
viable for an entirely new community group to start putting on their own 
wikimanias, essentially forking the process.


On 09/02/16 07:01, Gerard Meijssen wrote:

Hoi,
I positively HATE the notion that Wikimania will be once every other year.
It is easy enough to get in contact with local heroes. What Wikimania does
is bring people from the whole world together. Without Wikimania our
community is parochial. This is where our projects are weak in having a
global view.

I resent this conclusion forcefully.
Thanks,
   GerardM

On 8 February 2016 at 23:53, Ellie Young  wrote:


The Community Resources team at the WMF recently held a consultation

on articulating the value of Wikimedia movement conferences overall, the
unique value of Wikimania, and what new form Wikimania could take to better
serve the movement going forward.   We have completed analysis of these
results and have prepared this report:


https://meta.wikimedia.org/wiki/Grants:IdeaLab/Towards_a_New_Wikimania/Outcomes

I will be working with the community, organizers, committees, and WMF in
2017 to begin set up and planning for an experimental model for Wikimedia
movement conferences, including Wikimania, starting in 2018.

Feedback and comments are welcome at the discussion page
<
https://meta.wikimedia.org/wiki/Grants_talk:IdeaLab/Towards_a_New_Wikimania/Outcomes
Thanks to all who participated!

Ellie

--
Ellie Young
Events Manager
Wikimedia Foundation
eyo...@wikimedia.org
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 




___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Profile of Magnus Manske

2016-01-21 Thread Isarra Yos
You just don't get it, do you? Even from the start this was all about 
social issues with rollouts, and still you are contributing to the very 
same social problems you so blindly condemned.


-I

On 20/01/16 14:16, Magnus Manske wrote:

On Wed, Jan 20, 2016 at 12:58 AM Todd Allen  wrote:


Once the VisualEditor was fit for purpose and a good deployment strategy
had been developed, the English Wikipedia community overwhelmingly
supported rolling it out. (

https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)/Archive_125#Gradually_enabling_VisualEditor_for_new_accounts
)


That is for new accounts only. Without an account, still no VE for you,
even if you are probably the one needing it most.


It's not Luddism, it's not "resistance to change", it's not "power users"
grumpy about newbies having an easier time, it's not anything like that.
It's that in the state it was initially released in, the thing did not
work.


No one said "Luddism", except to defend against its use. Odd.



So yes, by all means, let's try new things. But try:

1: Asking us what we actually want, before coding something up and feeling
obligated to push it out. People are a lot more receptive to something they
asked for than something being forced upon them. That's been an issue with
Flow. It's not that it doesn't work well (though it doesn't), it's that it
wasn't wanted to start with. So instead of "Here's the new discussion
system", ask "What can we do to make our system of discussion better?"


Listening to what editors want is important. ONLY listening to wad editors
want is bad. People often don't know what they want or need, until they see
it. Compare the famous (possibly misattributed) Henry Ford quote:
“If I had asked people what they wanted, they would have said faster
horses.”

Also, veteran editors do not represent the readers or casual/newbie
editors; their needs are often quite different.



2: Make sure it works. Have an opt-in beta phase. Doesn't have to be
perfect, but certainly make sure it's not breaking page formatting all over
the place. You'll notice, for example, that there wasn't really any
resistance to HHVM. It worked well, it was desirable, it was clearly fit
for purpose. So no, there isn't just a reflexive change aversion. Though
the previous missteps and hamfisted followups have, rather ironically,
created a lot of the reflexive change aversion that people said was there.


Wrong example. The HHMV switch was a back-end change that should have had
no visible effect. As long as the servers are fast, people don't really
care what's going on there. Did e.g. English Wikipedia actually vote on
HHMV?


3: Be nice (but NOT condescending or patronizing) if an issue comes up.
"Superprotect" alienated people right quickly, and turned what could have
been a productive (if tense) conversation into a war. Same with refusal to
budge on VE and the arrogant tone several people took. Yes, some people
might be rude about objecting to the change. Don't sink to their level. If
they call the new software a steaming pile, ask "Could you offer more
concrete feedback?"


Superprotect was used to revert an admin action on de.wikipedia, an action
that might actually fall under U.S. or German computer sabotage laws. This
was hailed as some heroic action by that vocal group I keep mentioning,
when it can easily be seen as someone abusing the privileges given by the
Foundation (as owners of the servers) to deactivate functionality put in
place by the Foundation.
The creation and subsequent use of superprotect was not exactly the most
wise decision ever undertaken, but neither was the original sabotage
(literally so; using access to a machine to stop it from working, just not
using a wooden shoe).
And while it is always good to ask for more concrete feedback, it is even
better to offer it to begin with.



4: Don't surprise people. Not everyone follows the Village Pumps or what
have you. If a major new feature is set to roll out, do banners, do
watchlist notices, do whatever it takes, but make sure people know. When
Mediaviewer was rolled out, all of a sudden, I was just having images act
completely different. I had no idea what was going on. People are more
amenable to change if you brace them for it. Even better, do that to
develop a rollout strategy in advance with the community. (You already know
they want it; they asked for it. Right?)


The Foundation appears to be doing this already. I even saw a mail about it
today.



5: If at all feasible, offer an easy opt-out. People are actually more
likely to give something a decent try if they know they can switch back if
they don't like it.


IIRC, both VE and MediaViewer offered opt-out from the beginning; the MV
opt-out just was "below the fold" or something.



6: Show willingness to budge. "No, we won't do ACTRIAL, period." "You get
VE, like it or not." "You're getting Mediaviewer even if we have to develop
a new protection level to cram it down your 

Re: [Wikimedia-l] Announcement about changes to the Board

2015-12-29 Thread Isarra Yos

On 29/12/15 07:37, MZMcBride wrote:

Right, that part isn't surprising. But discounting the unsurprising vote,
it was a nearly unanimous decision (8 to 1). I have a good deal of respect
for many of the current Board of Trustees members and I have no doubt that
all of them understand and appreciate the gravity of removing a colleague.
This wasn't a close vote and to me that says quite a bit.


It says a lot, but just what that is depends entirely on the context. 
And for community members who voted for him, that context could mean we 
should also no longer have confidence in him elsewhere in the projects, 
or in the board, or have no bearing on either thing whatsoever. Not 
knowing just means there's no indication what to trust.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] [Wikimedia Announcements] FDC recommendations for 2015-2016 Round 1 APG grant requests

2015-11-24 Thread Isarra Yos

On 24/11/15 09:47, Asaf Bartov wrote:

On Tue, Nov 24, 2015 at 1:37 AM, Fæ  wrote:


Brandon's description of this looking like a 'kiss off', i.e. a spin
to make this disappear for another year, seems to meet the facts of
what can be observed and measured in a non-subjective way.


Yes.  I encourage everyone to judge WMF by its actions.  Talk is cheap.

A.


Certainly, but asking someone to reword a thing doesn't help with the 
actions either.


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] [Wikimedia Announcements] FDC recommendations for 2015-2016 Round 1 APG grant requests

2015-11-23 Thread Isarra Yos

I had a go at simplifying:

> We know spending less time on this is a problem, but we're going to 
try to do better. In order to help with this, we'll also be looking at 
what's happened in previous years in order to see where things fell 
short then, comparing that to what the FDC standards say should be 
happening. See also link.


That's how I read it, anyway. Maybe I'm wrong. I don't actually know 
anything about this stuff.


On 24/11/15 04:30, Brandon Harris wrote:

Could you answer this question in plain language, please, as this answer feels 
like a "kiss off".



On Nov 23, 2015, at 8:27 PM, Lila Tretikov  wrote:

We fully acknowledge the issue with the shortened AP review this year and
are committed to the 30 day review going forward. Since the overall issue
has been noted since as far back as 2012 we are doing a review of our
process in comparison to the FDC standards to build best practices going
forward. You can add you comments here to help guide the conversation:
https://meta.wikimedia.org/wiki/User_talk:LilaTretikov_(WMF)#Annual_Plan

Lila



On Mon, Nov 23, 2015 at 8:09 PM, Craig Franklin 
wrote:


I likewise appreciate the strong language on the situation with the WMF;
the general opacity and vagueness of public budget plans (especially
considering the requirements for affiliate organisations in this area) is
something that has been widely noted on this list and elsewhere, and to my
mind not answered in a satisfactory way.  It is good to see a fearless FDC
that is prepared to "tell it as it is", and make sure that this problem is
receiving continued attention.

It is my hope that the Foundation will address the issues raised here in a
constructive and transparent manner, rather than ignoring them or trying to
spin them away.

Cheers,
Craig

On 24 November 2015 at 12:04, Pine W  wrote:


Thank you FDC.

Many of the small and midsized APG requests fared well in this round.

That

is nice to see.

I find it concerning that the larger the organization, the more problems
the FDC  seemed to find with the org's budget and performance management
practices. One would expect the larger organizations to have mature and
robust practices in these areas. Regarding WMF in particular, my concerns
about its budget practices are well documented and I appreciate that the
FDC is also taking note of the persistence of the problems. I hope that

WMF

will get serious about its financial transpatency.

A couple of questions about Wikidata:

I'm confused about the funding for Wikidata. In one place the FDC says

that

"Nonetheless, the FDC is exasperated by the inability of WMDE to to
disaggregate the costs of Wikidata from other projects." and in another
place the FDC says that "We have recommended a reduced amount for WMDE in
this round with the expectation that WMDE will not cut Wikidata or their
other tech development work, but will instead find cost savings elsewhere
in its annual plan." If the FDC wants a disaggregated budget (which is
understandable) then why is the FDC expecting WMDE to dip into its other
funds and/or make cuts elsewhere in order to cover the work in this
proposal that the FDC is declining to fund in this proposal? This
expectation seems to be a bit of a contradiction.

I'm also wondering how WMDE is able to submit a dedicated request for
restricted funding for Wikidata if the Wikidata project is so integrated
into WMDE's other budgets that the FDC finds the integration to be
problematic. Can the FDC or our colleagues at WMDE explain this?

Wikidata is a high profile project with a good reputation, and I hope

that

the issues can be resolved soon.

Thanks,

Pine
On Nov 23, 2015 14:09, "matanya moses"  wrote:


Hello Wikimedians,

tl;dr: The FDC’s recommendations for this round of the APG grant

requests

have now been published at:


https://meta.wikimedia.org/wiki/Grants:APG/FDC_portal/FDC_recommendations/2015-2016_round1

The Funds Dissemination Committee (FDC) meets twice a year to help make
decisions about how to effectively allocate movement funds to achieve

the

Wikimedia movement's mission, vision, and strategy. [1] We met for four
days last week in San Francisco to review 11 proposals submitted for

this

round of funding. [2]

The committee has now posted our Round 1 2015-2016 recommendations on

the

annual plan grants (APG) to the Wikimedia Foundation Board of Trustees.

[3]

The WMF Board representatives to the FDC (Denny Vrandecic, Jan-Bart de
Vreede and Dariusz Jemielniak) will lead the Board in its review of

these

recommendations. The WMF Board will review the recommendations and then
make their decision on them before 1 January 2016.

This round, the eleven proposals came from ten chapters and one

thematic

organisation, totaling requests of approximately $3.8 million USD. Ten
affiliates were returning to the APG program, and one was a new

applicant.

This round, one 

Re: [Wikimedia-l] Celebrating Parisian culture and libertarianism

2015-11-16 Thread Isarra Yos
Isaac David makes good points, and writing it off as racist and 
discrimination is ridiculous. The people who did these things may indeed 
be bloodlusty assholes, but what led them to this is important too, and 
denying that will only ensure that it is not understood, not addressed. 
I don't care if this is the way to tolerance, either - tolerance by 
itself is meaningless; all you need to do is ignore, and not question, 
and you can perhaps tolerate anything. What is more difficult is 
understanding and love, because for these you have to learn, but these 
are also what actually connect people and allow them to help each other, 
and to help prevent tragedies like these.


But if you really don't wish to see this discussed, then simply do not 
discuss it. Don't tell people to shut the fuck up, simply let this 
aspect of the thread die on its own.


We work on these projects to help people learn, and to learn ourselves. 
Fae's proposal was not a bad one to this end, and Gnangarra brings up 
related topics that are also of relevance. These should not be at odds, 
as these are all important, and all worth working on, covering, building 
upon.


On 16/11/15 07:14, Pierre-Selim wrote:

Just +1 on the stfu.
Le 16 nov. 2015 7:53 AM, "Christophe Henner" 
a écrit :


I'm sorry but just shut the fuck up about "religion".

They're bloodlusty assholes that wanted to kill and divide. Nothing more.

It's not a religious thing (Paris isn't à holy city) or a cultural thing.
It's hate. Simple and plain hate.

They'd like us to say it's about religion and culture. Because that jump
starts the next sentence, it's us versus them where us has a better
culture. And then to start discriminating in our own country.

Because us vs them is the basis of any racist speech.

So please stop making it about culture and religion. Or if you want to make
it about culture, make it about the real culture they attacked : tolerance,
understanding, love.

That would the best answer we could make.

Thanks

PS: sorry for this email I don't usually send those but hey after that
week-end I couldn't restrain myself
Le 16 nov. 2015 7:24 AM, "Isaac David"  a
écrit :


Le dim. 15 nov. 2015 à 23:06, Gerard Meijssen 

[Wikimedia-l] 'Design team' in Wikimedia contexts

2015-11-10 Thread Isarra Yos
From time to time I see references to the 'design team' on lists and on 
phabricator. But what does this really mean now? As I understood it, the 
previous monolithic Design Team was essentially disbanded toward the 
beginning of the year, with the designers themselves distributed amongst 
the other WMF teams in order to more directly integrate their services 
into the development workflow (which sounds like a pretty good idea to 
me, at least, since design is such an integral part of most 
development). Did this happen? According to 
https://wikimediafoundation.org/wiki/Staff_and_contractors, there seem 
to still be two teams now with the word 'design' in their names, Reading 
Design and Design Research, though these both seem to have somewhat more 
specialised functions than just general design, namely Reading (sounds 
like front-end non-interactive mw stuff, the visuals perhaps?) and Research.


So what is the 'design team'? Is it one of these, though the teams only 
have 5 and 4 people on them, respectively? Is it just WMF designers in 
general?


As much as this is also just a plea to please be more specific, if you 
have an actual answer, or if you have been saying this, please, speak 
up, share your experience and where you're coming from. As confusing as 
it is, I suspect a discussion of what and why this has been going on 
could also clear up quite a bit.


Thanks.

-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] [Design] 'Design team' in Wikimedia contexts

2015-11-10 Thread Isarra Yos
According to the Staff and Contractors page, May is a 'Visual Experience 
Designer', which sounds like exactly what you're describing when it 
comes to the overlap between interaction and visual design. Is it just 
that you lack the visual design resources currently (one visual designer 
who isn't even just visual design does seem a bit insufficient for such 
a huge task!) to not overlap your roles?


Also, very cool to see how the roles interact laid out like this.

You're a UX engineer too, right? Does this mean you're often one of the 
ones interacting with other engineers/developers?


Sorry if I'm getting a bit off track here - design has always been one 
of the more opaque areas of the Foundation, at least from a volunteer 
perspective, and it's really nice to get a view of what's going on in 
such an integral part of the organisation.


On 10/11/15 22:50, Sherah Smith wrote:
>>Why do you make the distinction that UX designers also do visual when you stated already that you 
also have specifically visual designers?


Because interaction design and visual design are separate things. 
Visual designers are hired to design visual components, while UX 
designers are hired to design user experiences. Sometimes building 
experiences involves visual design, but not always - for example, in 
cases where we are innovating new ideas that do not yet have standards.


>>Are the visual designers the ones doing the UI standardisation?

May, who is a Visual Designer, is indeed working on UI 
Standardization, along with Volker, who is a UX Engineer.


>>How does Design Research relate to the rest of this?

Roughly:
Design Researchers conduct user research ---> UX Engineers build 
interactive prototypes working with Design Research and Designers ---> 
Designers polish and iterate the prototypes with the prototypers ---> 
Engineers build the designs



As for the difference between UX Designer and UX Engineer, the main 
difference is that the UX Engineer has an engineering background and 
applies that to the building (coding) of interactive prototypes.


On Tue, Nov 10, 2015 at 2:32 PM, Isarra Yos <zhoris...@gmail.com 
<mailto:zhoris...@gmail.com>> wrote:


Er, forgot to cc the main list, since I did cross-post in the
first place.

Sorry about that!


On 10/11/15 22:25, Isarra Yos wrote:

Hi, thank you for your response. This does clarify a lot.

Why do you make the distinction that UX designers also do visual
when you stated already that you also have specifically visual
designers? Are the visual designers the ones doing the UI
standardisation?

How does Design Research relate to the rest of this? You state
that they are not designers, but their work is an integral part
of the user experience design process.

Also, in the future, could you please use a darker colour (or
even just leave it as the default) for your emails? That grey is
really hard to read and I misread a few things the first time
that made it look a little... different from what you obviously
meant.

Thanks!

On 10/11/15 22:04, Sherah Smith wrote:

Hi Isarra,

>> what is the 'design team'?

Even though the design team (as it used to be) is now split out
under different managers with no centralized Director, we still
consider ourselves a "team" in that we still work together
across teams to maintain consistency and provide feedback,
collaborate, and review one another's work where needed. We have
a weekly meeting and regularly talk and brainstorm in person
across teams to support one another in our work.

Design Research is the team that conducts research that informs
the design of products we build on all other teams. The
employees on this team are not designers.

Reading Design is a sub-team under Reading, and it designs
reading experiences, mostly for mobile platforms. Where you see
"Visual Designer" as a title, that person works on visual
designs. "UX Designer" works on combinations of visual and user
experience design, mostly the latter, and "UX Engineer" builds
interactive prototypes and interaction design.

The reorganization that you reference happened in late April
this year and was not a decision the design team itself made.
Rather, it came from upper management. We do now work within the
teams you see listed on the staff page, on experiences for those
teams specifically. So for example, you will not see a designer
on the Search & Discovery team working on experiences for the
Editing team.

Is there a particular concern you have about this organization
that you feel like we should be discussing, or does this answer
your questions?

Thank you,


On Tue, Nov 10, 2015 at 1:21 PM, Isarra Yos <zhoris...@gmail.com
<mailto:zhoris...@gmail.com>> wrote:

Re: [Wikimedia-l] [Design] 'Design team' in Wikimedia contexts

2015-11-10 Thread Isarra Yos

Er, forgot to cc the main list, since I did cross-post in the first place.

Sorry about that!

On 10/11/15 22:25, Isarra Yos wrote:

Hi, thank you for your response. This does clarify a lot.

Why do you make the distinction that UX designers also do visual when 
you stated already that you also have specifically visual designers? 
Are the visual designers the ones doing the UI standardisation?


How does Design Research relate to the rest of this? You state that 
they are not designers, but their work is an integral part of the user 
experience design process.


Also, in the future, could you please use a darker colour (or even 
just leave it as the default) for your emails? That grey is really 
hard to read and I misread a few things the first time that made it 
look a little... different from what you obviously meant.


Thanks!

On 10/11/15 22:04, Sherah Smith wrote:

Hi Isarra,

>> what is the 'design team'?

Even though the design team (as it used to be) is now split out under 
different managers with no centralized Director, we still consider 
ourselves a "team" in that we still work together across teams to 
maintain consistency and provide feedback, collaborate, and review 
one another's work where needed. We have a weekly meeting and 
regularly talk and brainstorm in person across teams to support one 
another in our work.


Design Research is the team that conducts research that informs the 
design of products we build on all other teams. The employees on this 
team are not designers.


Reading Design is a sub-team under Reading, and it designs reading 
experiences, mostly for mobile platforms. Where you see "Visual 
Designer" as a title, that person works on visual designs. "UX 
Designer" works on combinations of visual and user experience design, 
mostly the latter, and "UX Engineer" builds interactive prototypes 
and interaction design.


The reorganization that you reference happened in late April this 
year and was not a decision the design team itself made. Rather, it 
came from upper management. We do now work within the teams you see 
listed on the staff page, on experiences for those teams 
specifically. So for example, you will not see a designer on the 
Search & Discovery team working on experiences for the Editing team.


Is there a particular concern you have about this organization that 
you feel like we should be discussing, or does this answer your 
questions?


Thank you,


On Tue, Nov 10, 2015 at 1:21 PM, Isarra Yos <zhoris...@gmail.com 
<mailto:zhoris...@gmail.com>> wrote:


From time to time I see references to the 'design team' on lists
and on phabricator. But what does this really mean now? As I
understood it, the previous monolithic Design Team was
essentially disbanded toward the beginning of the year, with the
designers themselves distributed amongst the other WMF teams in
order to more directly integrate their services into the
development workflow (which sounds like a pretty good idea to me,
at least, since design is such an integral part of most
development). Did this happen? According to
https://wikimediafoundation.org/wiki/Staff_and_contractors, there
seem to still be two teams now with the word 'design' in their
names, Reading Design and Design Research, though these both seem
to have somewhat more specialised functions than just general
design, namely Reading (sounds like front-end non-interactive mw
stuff, the visuals perhaps?) and Research.

So what is the 'design team'? Is it one of these, though the
teams only have 5 and 4 people on them, respectively? Is it just
WMF designers in general?

As much as this is also just a plea to please be more specific,
if you have an actual answer, or if you have been saying this,
please, speak up, share your experience and where you're coming
from. As confusing as it is, I suspect a discussion of what and
why this has been going on could also clear up quite a bit.

Thanks.

-I

___
Design mailing list
des...@lists.wikimedia.org <mailto:des...@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/design




--
*Sherah Smith*
UX Engineer
Wikimedia Foundation
206-660-6585
sherahsmith.com <http://sherahsmith.com>
donate.wikipedia.org <http://donate.wikipedia.org>


___
Design mailing list
des...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/design




___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Introducing WikiProject X

2015-01-15 Thread Isarra Yos

On 14/01/15 04:01, Keegan Peterzell wrote:

On Tue, Jan 13, 2015 at 5:40 PM, Ricordisamoa ricordisa...@openmailbox.org
wrote:




  Sounds like just another enwiki-specific thing.



​That's a reasonable assumption. I'm only guessing, but I think the project
is based on the English Wikipedia because that's the area where the
grantee(s) are most familiar. I wouldn't want them to go mucking around on
projects they are not familiar with first.

I'm going to assume that while this is initially en.wp focused, the
grantees are willing to learn from and share what they learn with the other
projects. One would think they would appreciate the outreach from other
communities, learning from each other is always a Good Thing™.​


This. For our project, things enwp users would never even think of may 
prove to be the most useful, but as always, we do want this to be able 
to scale. Such will probably show up more in any tool implementations 
that show up later, but the less hard-coded those things are, the more 
flexibility they can have later, which means they will be more useful 
for everyone down the line - english wikipedians and whoever else as well.


A lack of flexibility has happened with a lot of other tools before and 
it's not something we want to repeat. We'll see what happens, though.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Why WMF should reconsider the 3-month gender gap

2015-01-10 Thread Isarra Yos

These are important points, and well said. Thank you.

-I

On 10/01/15 07:41, Gerard Meijssen wrote:

Hoi,
I do not care one whit who you are or why you think you are provoked.  What
I care about is arguments that are put cleanly without much fanfare. When
you think that you have permission to be rude threatening or abusive under
any circumstances, you are wrong. It degrades any point you have and it
abuses the other people on the list.

You may not think much of our list administrator. Your choice as long as it
is private, you are entitled to that opinion.

When you choose to be abusive, it makes you unpalatable and I do not really
care for your point of view because it got tainted. So make up your mind
what is important, your ego or your argument.
Thanks,
GerardM

On 8 January 2015 at 22:59, mcc99 mc...@hotmail.com wrote:


Well Austin Hair,

You display a profound lack of understanding of ME, it seems.  I am polite
until others are rude, become threatening, even a thinly veiled way, so
allow me to tell you first that I do not care a whit what YOU think of me
or my opinion on this or any other topic.  And if others object to my
opinion on a topic, sensitive or not, they can make their case and it will
stand or not on its merits.

But if you think you or anyone else can intimidate me into staying quiet
when I see something fundamentally wrong happening, guess again.

Now to put it politely, at least to start with:

Go climb a tree.

 Original message 
From: wikimedia-l-requ...@lists.wikimedia.org
Date:01/08/2015  11:30 AM  (GMT-05:00)
To: wikimedia-l@lists.wikimedia.org
Cc:
Subject: Wikimedia-l Digest, Vol 130, Issue 29

Message: 1
Date: Thu, 8 Jan 2015 17:01:08 +0100
From: Austin Hair adh...@gmail.com
To: Wikimedia Mailing List wikimedia-l@lists.wikimedia.org
Subject: Re: [Wikimedia-l] Why WMF should reconsider the 3-month
 gender gap
Message-ID:
 
ca+bw_fvvbcn6bm6dutawbj884a1wmfbumctbnqojvubk5r0...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8

On Thu, Jan 8, 2015 at 4:30 PM, mcc99 mc...@hotmail.com wrote:

But in future, I think I'll sign in more often, esp. now that half the

WikiGods have my uid on an alert trigger now. :)

I think the question is only being asked because you're displaying a
profound lack of understanding of how Wikipedia and Wikimedia work,
not only in your recent proposal, but in commenting on this sensitive
topic.

You're entitled to your opinion, of course, and you've been polite in
expressing it—that goes a long way, at least with me. So please don't
think that it's a matter of demanding a certain number of WikiCred
points before the WikiGods will let you sit at the WikiGrownups table,
or anything like that. Just understand that this issue has a lot of
people on edge, and at this rate it won't be long before politely
ignored becomes less ignored and less polite.

Austin

___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe



___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Why WMF should reconsider the 3-month gender gap project-related decision

2015-01-08 Thread Isarra Yos
I'm just going to preface this by pointing out that I didn't actually 
read all of the OP due to a philosophical opposition to giant walls of 
text, but I think you've kind of missed the point in a few places.


Also please don't call people names. That's not nice.


On 08/01/15 10:52, geni wrote:

On 8 January 2015 at 07:07, mcc99 mc...@hotmail.com wrote:


If you ask any RN the names of the greatest contributors to the nursing
profession, you'll get a stream of women's names.  To suggest that nursing
needs more men or else it won't be able to achieve its greatest potential
would be a crass and inaccurate insult to the many thousands of women who
have made modern nursing what it is.  Of course there have been and will be
male nurses who stand out as contributors, but only a very small
percentage, probably in keeping with the ratio of men to women in nursing.
And yet, despite the high salaries RNs command, are there any
gov't-sponsored initiatives to get men into nursing?


In fact nurses get paid less than the male national average wage. This is
clearly some definition of high salaries I wasn't previously familiar with


Are male nurses paid more than female ones? Otherwise that's not really 
relevant.



If so, it'd be news to me and many others.  But I ask, if men by and
large, for whatever reasons, aren't interested in becoming nurses, why make
a big deal about it?


Reducing the recruitment pool is less than ideal. However the number of men
training to be nurses has been increasing so it is probably felt the
problem will solve itself.



Are there gov't-sponsored campaigns to get more women into the relatively
lucrative job of refuse collection?


Ah you can tell the piece you are recycling from is dated. Post
privatisation refuse collection has ceased to be a particularly lucrative
job.


I think that was supposed to be a joke. Gender disparities exist across 
the field in both low-paying and high-paying fields, but generally the 
focus is only to get more women into higher-paying ones, especially ones 
involving technology.


In a way it does seem to be a bit of a tangent here, where contributors 
aren't necessarily paid in the first place, but research into how we as 
a movement fit into the overall pattern of field-based gender 
disparities might show a solid connection. It'd certainly be 
interesting, if nothing else, especially if folks were to compare both 
regionally and globally.



  (Think professional STEM fields.)

I'm a chemist you insensitive clod. Depending on what you are doing it can
be dirty or dangerous.


I get that you disagree, but that's not helping anything.

-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Why WMF should reconsider the 3-month gender gap project-related decision

2015-01-08 Thread Isarra Yos

On 08/01/15 20:04, Austin Hair wrote:

On Thu, Jan 8, 2015 at 1:41 PM, Risker risker...@gmail.com wrote:

Frankly, there's not a single thing I've read, or a single objection I've
seen raised, that wasn't about how unnecessary it is to focus on women.  I
don't think we've ever heard that about the global south, or non-European
languages, or a lot of other areas where there are acknowledged biases.

Maybe you're only talking about this specific fork of the thread, but
I was happy to see that the previous discussion managed to stay
on-topic and largely avoid the specific social issue. I saw a lot of
people with specific criticism of the decision, completely separate
from the cause. (I appreciate that Leigh was still clinging to that
idea while the thread was being dragged into the abyss, only to be
insulted in the process.)

Having addressed that, I want to say to everybody that Wikimedia-l is
a lot of things, not all good, but the previous conversation was at
least on-topic. Does anyone seriously think that this one is? Please,
please don't make me start content filtering based on words like
feminazi or misogynist.

Austin


As far as I can tell, this is the first time either of those words have 
shown up in the discussion. It's true that the bulk of this thread is 
only about the particular topic chosen for the 3-month focus, whereas 
the previous thread was about the nature of having 3-month focuses in 
the first place and particularly the chosen implementation, but so long 
as people remain civil, why can both not be valid topics of discussion?


It doesn't even matter what the topic is, really. It ought to be worth 
discussing if only to clarify what it means to different folks, but even 
and in doing so, how better to generate possible ideas for projects?


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Wikimedia Conference 2015

2014-09-11 Thread Isarra Yos

On 11/09/14 18:42, Ilario Valdelli wrote:

On 11.09.2014 20:06, James Forrester wrote:

On 11 September 2014 10:52, Ilario Valdelli valde...@gmail.com wrote:


Against the funds of WMF.

A second conference open to the public would be a second yearly 
Wikimania,

and to open it means to have a budget more or less equal to Wikimania.


Indeed, which is why we keep asking for the name to stop being a lie.

J.


Considering it a lie is an extreme evaluation in my opinion.

In Wikimedia conference there are chapters (~40) and user groups 
(~15). At the start it was called chapters conference, now it's 
called Wikimedia Conference because it's more open.


In my opinion it's not a problem to call it again chapters conference.

To participate it's sufficient to be representative of a group, not 
only of himself.


Considering the principle of delegation, it may be considered a 
Wikimedia Conference.


Regards



I'm part of the Wikimedia movement, but there are no chapters nearby, 
nor are there any user groups that I know of relevant to my interests as 
yet. Thus there is nobody to represent me but myself.


If this is Wikimedia, why can't I go to a Wikimedia conference?

-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Wikimedia Conference 2015

2014-09-11 Thread Isarra Yos

On 11/09/14 22:06, Pete Forsyth wrote:

On Thu, Sep 11, 2014 at 1:47 PM, Alice Wiegand me.ly...@gmail.com wrote:


Is this really a discussion about the name of a conference or is it more a
discussion about inclusion and exclusion with the underlying question if
this conference, which once was set up as a meeting for the organizations
within the Wikimedia movement, should be open for non-organized Wikimedians
as well. Which would probably be a different conference.


I think this discussion is both. But the immediate, acute, and solvable
problem (the inaccurate name of the conference) should not be ignored, just
because there *might* be a larger, hazier problem that will not be solved
today or tomorrow. Some progress is better than no progress.

Personally, I have no problem with the existence of the conference, but I
find its name alienating. Not everyone agrees with that assessment, but
clearly some others in this thread do.

Pete
[[User:Peteforsyth]]



What Pete said.

We could go into issues with the exclusionary nature itself, such as 
that it would exclude representatives of groups who ran into trouble 
becoming official - despite such a conference likely being one of the 
best venues for them to bring up and discuss with relevant others how to 
actually address or resolve that trouble that excluded them in the first 
place...


...but that sort of thing is much harder to resolve/address. The name, 
at least, is simple, and should also make a lot of the other problems 
less glaring in the process.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Next steps regarding WMF-community disputes about deployments

2014-09-06 Thread Isarra Yos

On 06/09/14 06:13, Erik Moeller wrote:

On Fri, Sep 5, 2014 at 10:42 PM, Risker risker...@gmail.com wrote:

The major deficiencies that have long been identified in the current
discussion system (and that can be addressed by technology) are all able to
be addressed in MediaWiki software or by extensions. Automatic signatures
have been done by bots for years; indenting could be added to the editing
function gadget and moved to an extension; much work has already been done
on graceful resolution of edit conflicts.  The ability to watchlist an
individual thread or section of a page is more challenging but, I have been
told, still possible.

Let's just acknowledge that the limitations of what can reasonably be
layered onto wikitext-based representation of comments have not been
fully explored, rather than jumping to conclusions about what's easy
to address and what's hard. As noted separately, I agree it may be
worth pushing the boundaries a bit more on this, if only to know
exactly where they are, and to achieve short term improvements.


But many of these things have been explored and experimented with. 
That's just it. We have extensions to create a whole new discussion 
system already which get some things right and others no so much, like 
LQT and Comments, and various bots and gadgets that do smaller tasks 
(auto-signing, indentation, cleanup, etc).


Have the successes and failures of the existing approaches and tools 
been considered? Are things LQT got right present in Flow?



Automatic signature (something that is currently
functional on Flow, but is not customizable) turns out to be more of a
challenge when users are widely known by a signature line that doesn't
match their username,

I've not talked to them about it explicitly, but I'd guess that the PM
and the UX folks have a negative aversion against custom signatures
because of their free-form nature (including sometimes
layout-exploding ones). Perhaps a middle-ground can be found here,
with some more sanitization applied to prevent some of the
sigs-from-hell occasionally found. Other than that I can't see a good
reason to not just show them when they're set, and it's certainly
technically trivial to do so.


Signatures that break the page are currently dealt with by yelling at 
the user to fix their sig and then blocking them if need be. I dunno how 
a structured talkpage would necessarily change that, though having the 
signatures automatically tidied might be useful in general, as it should 
at least help prevent unclosed tags. Beyond that what they allow really 
depends on the project, but any structured formatting with sensible 
padding should work fine no matter what they do (I mean, I've never seen 
any issues with that with LQT).



and there is no method by which users can add an
explanatory note to their signature such as formerly known as
User:Whatever.

 From the point forward that Flow is in wide use, a user rename would
be automatically reflected in old comments if desired, much as it is
reflected in old edits. But if signatures were supported, as above,
you could still use them for these types of indicators, as well.


The more efficient indenting has reduced possible
indents to three levels, without exception;

This seems to be the most religious topic when it comes to Flow. The
database stores all threading information. It'd be trivial to expand
the threading level if that's more popular and usable.


How is this religious? Something is needed to show progression, and 
lacking anything else, threading has already been proven to work. Just 
chopping it off has been shown time and again not to (you see it 
particularly often on blog and news comments).



I've heard the argument that this doesn't work on mobile, but we could
just set a different threading level on mobile.

I think it's worth experimenting with flat pages (with quoting) for
certain purposes, and Danny wants to, but it strikes me as most
reasonable to start with something that more closely resembles talk
pages as they are now (which is why we did that with LQT originally).


Formatting the pages as flat with just ids and links to what the things 
are replying to could be an interesting option experiment with, 
especially when you don't have a lot of space. Like boards. Be like 
4chan! Everyone loves 4chan.





Rigid predictable technical
restrictions on who can edit what has resulted in inability to remove
posts that are obviously unsuitable (there's no undo or revert
function), replaced with a hide function that can only be applied by
certain users that's practically a red flag for people to look-see what the
problem edit is.

The team has pretty strong arguments why they don't want posts to be
editable (the gist is, they fear that no other discussion system does
this, and it will freak people out -- they see the introduction of a
new system as a good opportunity to reset expectations). I personaly
am not religious about it; when we built LQT we made posts 

Re: [Wikimedia-l] Next steps regarding WMF-community disputes about deployments

2014-09-06 Thread Isarra Yos

On 06/09/14 07:41, Erik Moeller wrote:

On Sat, Sep 6, 2014 at 12:23 AM, Isarra Yos zhoris...@gmail.com wrote:


Why in the world would posts not be editable? I've never used a platform
where discussion was important in which users couldn't at least edit their
own posts (along with mods) where the lack of such wasn't often complained
about (for instance bugzilla and gerrit don't allow it; moodle and tumblr
do).

Sorry, I should have been clearer. By default, Flow lets you edit your
own comments, and lets admins edit all comments, just like typical
forum conventions. It just doesn't let everyone edit everything.


But that's not how wikis work. On other platforms that do support such 
editing at all, users edit their own articles, and their own comments, 
with only moderators trusted to change them. But on wikis, the users are 
also the moderators. This applies to content and comments, and admins 
are only required where things can become sensitive (where concerns of 
privacy, site stability, or simply dangerous tools in terms of vandalism 
come into play). Why the sudden divergence that only admins can be mods 
here? Discussions aren't sensitive.


This sort of thing is a large part of why some of us are so skeptical of 
Flow currently - if the designers do not even understand the basic 
principles behind a wiki, how can what is developed possibly suit our 
needs? The thing is, they - you - need to start really listening, and 
not just arguing (or not responding at all), because otherwise things 
are just going to get messier and messier.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] editor retention initiatives

2014-09-03 Thread Isarra Yos

On 02/09/14 10:56, Ricordisamoa wrote:

Il 26/08/2014 12:18, Craig Franklin ha scritto:
The editor retention problem will not be solved with technological 
gizmos

and doodads, nor with top-down solutions imposed from above.  It will be
solved with positive human contact and creating a collaborative 
community
that people actually want to be a part of, rather than one that they 
put up

with.
This makes my first RFBOT on the Italian Wikipedia 
https://it.wikipedia.org/wiki/Wikipedia:Bot/Autorizzazioni/Archivio/2013#SamoaBot 
come to my mind.
I was much less experienced than now, and ended up flooding Recent 
Changes. A bureaucrat threatened 
https://it.wikipedia.org/w/index.php?diff=56154161oldid=5615 to 
block me, and I even retired 
https://it.wikipedia.org/w/index.php?diff=56157910 for a day.

But I was already 'addicted' to Wikipedia and came back soon after.

Thanks to that episode, I gradually became a quite experienced 
operator. But... how many users would have given up in my place?


If someone has already gone to the trouble of making a bot, it seems 
unlikely that they would give up after a single incident. I've seen it 
happen after a protracted series of such incidents/screwups, but that's 
perhaps better for everyone involved anyway at that point.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] The reader, who doesn't exist

2014-08-21 Thread Isarra Yos

On 21/08/14 13:24, Risker wrote:

On 21 August 2014 09:18, Yaroslav M. Blanter pute...@mccme.ru wrote:



For me the conclusion would be not that we should drop them altogether in
the mobile version (most of them are useful navigation means after all) but
that the mobile version should be improved to parse them and to present
them as a piece of plain text, not as a template.



Many of these templates have over 100 links in them; a surprisingly large
number have subtemplates built into them.  I'm having a hard time seeing
how adding all those links at the bottom of an article is actually going to
help that much. Unless we have some evidence to confirm this information is
actually useful to readers -seriously, this is a community-designed feature
targeted at readers as opposed to editors - it's probably time to rethink
what indirectly related information on our article pages is made routinely
available.  We want people to use our information, not give up because it
takes too long to load.

Risker/Anne


Man, I forgot how over the top some projects get with their navigation 
templates. But what Yaroslav said might actually provide a good 
guideline - if they CAN be reasonably simplified, then the templates 
themselves are probably reasonable. If not, they need to be fixed.


Just hiding them isn't the solution - the templates themselves need to 
be made more realistic, because while they may be a bit overwhelming on 
the desktop (I mean, I looked at [[red]] and was overwhelmed by the 
bottom of the page), the issues they present on mobile devices should be 
a real incentive. But if you just hide them, that removes the incentive 
to fix them up. That doesn't make much sense to me.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] [Wikitech-l] Superprotect user right, Comming to a wiki near you

2014-08-14 Thread Isarra Yos

On 14/08/14 16:07, Yaroslav M. Blanter wrote:
This is actually not correct. Take pending changes on the English 
Wikipedia as an example - people used to complain a lot on how RfC's 
were closed, but this is the business of the community. I have never 
heard anybody complaining that the trial sucked, or that PC itself 
does not work properly. There was a discussion, there was a trial, 
everything was properly announced, and everything from the 
developers's side was done perfectly or close to perfectly.


Take Phase I Wikidata - this is smth I was actively participating in 
and watched it from the close distance. Everything went smoothly, with 
the Hungarian Wikipedia trial starting first, the Italian Wikipedia a 
bit later, when feedback was taken into account, and then other 
Wikipedias followed. Again, no problem with the developers whatsoever.


Now compare this with VE, AFT, Mediaviewer, and Flow will be probably 
the next disaster of a comprable scale - despite the fact that WMF is 
pretty open about Flow, and there are many people answering questions 
basically in real time.


Cheers
Yaroslav


It may be that specific teams, not just legal and whatnot but also 
including within engineering itself, are better at handling this sort of 
thing than others. Have there been any patterns with how well things go 
depending on who is involved? If so, perhaps the others could learn from 
them...


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] [Wikitech-l] slow death of anyone can edit concept

2014-08-09 Thread Isarra Yos

I got a 404 too.

On 09/08/14 14:57, Alex Monk wrote:

Not for me...


On 9 August 2014 15:27, svetlana svetl...@fastmail.com.au wrote:


On Sat, 9 Aug 2014, at 23:11, James Forrester wrote:

[..]
https://imgur.com/a/JFN9y​

404




___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Comment on the content, not the contributor - with staff?

2014-07-15 Thread Isarra Yos

On 14/07/14 15:11, Quim Gil wrote:

On Thursday, July 3, 2014, Isarra Yos zhoris...@gmail.com wrote:


What can we, as volunteers, do when we believe staff have gone too far
(besides create drama on a mailing list)?


It depends on the area and the problem, but there are enough WMF employees
with public exposure and community background to choose from. The
Engineering Community team should be able to help technical volunteers
having problems with WMF employees. The community liaisons (now Community
Engagement team) are also good points of contact.

Of course, each of us employees has a manager and a HR contact, and if the
problem is exceptional they could be the ultimate points of contact within
the WMF.

Does this answer your question?


Aye, thank you. I think you and Pine covered it, or enough that I feel 
like I have a pretty good idea of what to expect. I'm not exactly 
convinced there'd be any point bothering at this stage, rather like with 
gerrit where it's just sort of like dropping things into a dark 
unknowable hole, but should something come up again I'll definitely try 
what you said.


Also I like the lack of drama. Yay, lack of drama.

-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Proposal: List administration policy

2014-07-12 Thread Isarra Yos
I don't really have anything to add, but I think Fae makes some good 
points here.


On 12/07/14 08:04, Fæ wrote:

On 12/07/2014, Russavia russavia.wikipe...@gmail.com wrote:
...

the door completely with their backdoor continued accusations which are
made without a shred of proof.

Referring to Richard's post, the general list guidelines apply[1] and
there is an explanation of the admin role[2]. However neither of these
documents sets a policy for whether administrators on this list have a
duty to reply to emails from a participant when they ask why they have
been moderated or blocked, nor whether they have to give an
explanation when action is taken so that the person being moderated or
blocked can have the opportunity to understand the issue, change their
behaviour and have a path to get unblocked or unmoderated.

As with Russavia's case above, there may be people who are thought to
be problematic due to a history on Wikimedia projects, perhaps they
will always be unwelcome on this list, however the vast majority of
bans or moderated accounts ought to be based solely on evidence of
posts to this list. However, there is no downside to letting people
ask the question why was I moderated? or go on to appeal moderation
or a ban if they wish, preferably as a public process so that others
affected are free to comment with evidence. It may be beneficial to
consider adding a project whereby moderation or banning can be
requested publicly, rather than by closed emails.

I still hold the view that a policy beyond the standard general
nuts-and-bolts guidelines which ensures a greater level of
transparency compared to the de facto closeted and apparently
sometimes silent process we have settled for, would be of benefit to
all contributors of this list.

Links
1. https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
2. https://meta.wikimedia.org/wiki/Mailing_lists/Administration

Fae


I guess the way I see it, there will always be exceptions, but anyone 
worth letting (back) on the list in the first place probably deserves at 
least some sort of transparency.


The overhead required to actually do that could prove problematic, 
though. I don't know.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Community RfCs about MediaViewer

2014-07-10 Thread Isarra Yos

On 10/07/14 15:53, Brion Vibber wrote:

Perhaps it's time to stop calling self-selected surveys of a tiny subset of
our user base community consensus.

The vast majority of our user base never logs in, never edits, and never
even hears about these RfC pages. Those are the people we're making an
encyclopedia for.

-- brion


And those who do log in, edit, and comment on RfCs generally do so with 
the understanding, on some level, that everything they do, that the 
entire encyclopedia, is for the readers, because without an audience 
there would be nothing. They know their audience, they interact directly 
with this audience on the talkpages and in email, and indeed they often 
use the site exactly as this audience would, simply taking things a step 
further to edit as well.


So when they speak for the users who never log in, never edit, and never 
comment, do not discount them. No more than you discount yourself when 
you try to speak for the users who never log in, never edit, and never 
comment.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

[Wikimedia-l] Comment on the content, not the contributor - with staff?

2014-07-03 Thread Isarra Yos

Hey, all. Bit of a question, here.

Basically, how does comment on the content, not the contributor apply 
to staff and contractors? What can we, as volunteers, do when we believe 
staff have gone too far (besides create drama on a mailing list)?



In many of our communities, we have a saying: comment on the content, 
not the contributor. When working with others, this is quite useful, 
and something we definitely want to remember, because it reminds us to 
cooperate and find use for whatever content is good, and it also helps 
us to avoid making personal attacks and other generally unhelpful 
comments about the people involved that tend not to be relevant to the 
situation.


Of course, this depends a great deal on the situation itself - this 
applies to an edit dispute or a bug report or an RfC about content or 
features or what have you, but what about when the contributor IS a 
relevant topic? In volunteer circles it generally boils down to a 
question - is the contributor causing more trouble than they're worth? 
If so, an appropriate committee or whatever can do something sanctiony, 
and the situation will be resolved for the time being.


But what if it's not a volunteer? What if it's a staff developer who is 
consistently ignoring project consensus and needs, or a team that 
refuses to justify their decisions even in light of scrutiny, or a 
contractor hired to do something specific and community-facing who won't 
actually do it, and on top of that won't let volunteers do the needful 
either? With a volunteer, it's often a pretty simple matter to simply 
remove an individual or group from a topic or project, but with staff, 
the situation is a lot more complicated - not just because they're paid, 
but also because they have specific obligations and requirements, as 
well as the power and authority the position grants. Volunteers come and 
go, and answer to other volunteers. Staff are supposed to do things, and 
paid to be doing things, and answer to staff (and also the board and 
crap, but at the level I'm talking about it's basically just other staff).


There's a very real disconnect here, and though community liaisons are 
supposed to be bridging that gap, this works far better on content 
projects than in development, where developers and designers and whatnot 
need to communicate with each other, no matter who they are, in order to 
get things done. And indeed, most staff here are pretty great about this 
and you can totally go right up to them and talk about their work and 
collaborate and what have you, but sometimes they aren't. And that's a 
problem.


So what can we, as volunteers, do in such cases? What are our channels 
for bringing up issues with staff, so that we don't just wind up 
bringing it up somewhere completely inappropriate, where we really 
should be commenting on the content itself?


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Comment on the content, not the contributor - with staff?

2014-07-03 Thread Isarra Yos

On 03/07/14 18:16, Pine W wrote:

In the past, this mailing list has been used for discussions of staff
conduct, which I am not sure is the best idea when identifiable people are
involved. I suggest that a first line of approach would be to discuss the
matter civilly with the people directly involved including the employee and
other volunteers, and if that doesn't get results, then go to the
employees' supervisor.

WMF HR has told me in the past that they can also step in with situations
like this.

Pine


The problem is, in my experience the main problem has usually been that 
the people involved won't talk at all, at least in the case of the 
employees. And what are you supposed to say? Somehow I don't think Hi, 
please remember that consensus is something you're supposed to follow 
or Hi, could you please do your job? would help matters any.


Would tracking down their supervisors and hoping they know any more than 
the other folks do really be the best option? Personally I wouldn't even 
know where to start, and even then there's no guarantee they would 
listen. Email shows up from someone they've never heard of calling into 
question their people. Or better yet, email shows up from someone they 
understand that their people widely regard to be a troll. Might be 
difficult to keep an open mind at that point. (I've had this happen.)


Perhaps HR is the only way to go at that point? But even then, how do 
you bring that up?


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] The Signpost is (sort of) published

2014-06-03 Thread Isarra Yos

On 02/06/14 20:14, Andy Mabbett wrote:

On 2 June 2014 19:39, Ed Erhart the.e...@gmail.com wrote:


There is one person in charge of making the final calls of every issue—me.

This is troubling, Wikipedia is supposed to be an open,
community-driven initiative.

We've seen problems in the past with single-person gatekeepers; at
TFA, for instance.

Not that I'm casting aspersions, but you may be indisposed, and a
future keyholder may turn out to be rogue.


It was an unfortunate error that I did not give the password to
other trusted Signposters, but as Pine says, that is no longer the case.

That, at least, is reassuring.





Wikipedia is exactly that, an open, community-driven initiative. This is 
why when something needs doing, in many cases any random bloke can come 
in and do it - the {{sofixit}} narrative. Of course, as a result, things 
are also often not necessarily as well-organised as they perhaps could 
be, and there may only be a single person involved, but why should this 
be a problem when such is only the beginning?


Most nothing will be well-organised at first, but as time goes on, as a 
project matures and others join in, problems come to light and are 
fixed. If an initial lack of organisation or a potentiality for issues 
down the road were considered a barrier to doing stuff, nothing would 
ever get done. We certainly wouldn't have a Wikipedia.


I'd say that what has happened here has if anything been a good example 
of that the process really does work, and I'd like to thank those 
involved for taking the initiative to keep things running smoothly. This 
is what keeps all the projects running, when you get right down to it.


-I

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Affiliation in username

2014-04-20 Thread Isarra Yos

On 20/04/14 11:50, Liangent wrote:

On Sun, Apr 20, 2014 at 4:05 PM, Federico Leva (Nemo) nemow...@gmail.comwrote:


Amir E. Aharoni, 20/04/2014 08:39:

  Silly technical remark: Everybody, please stop doing this with

parentheses.
It breaks in right to left languages. Gary-WMF is just as readable, and
doesn't have this problem. Thanks for the attention.


Your suggestion works against the built-in assumptions of MediaWiki for
disambiguations.
https://meta.wikimedia.org/wiki/Help:Pipe_trick


Then Gary, WMF?



Nemo


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe


Removing the affiliation from the name itself and adding it as a group 
would allow the mediawiki to format the name and group in a way that 
makes sense for the given language. Keep to the parentheses for english 
and such, do other things for ones where that doesn't work or wouldn't 
be the norm.


-I

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] the big red notice on the top of http://strategy.wikimedia.org - done

2014-03-10 Thread Isarra Yos
Why not? People know what the words 'read' and 'only' mean. Putting them 
together should be pretty self explanatory: It can only be read.


On 10/03/14 22:32, Michael Peel wrote:

Probably not. How about 'archived'?

Thanks,
Mike

On 10 Mar 2014, at 22:22, User Mono userm...@outlook.com wrote:


Closed isn't the best word, but do most people know what 'read only' means?


From: peter.southw...@telkomsa.net
To: wikimedia-l@lists.wikimedia.org
Date: Sun, 9 Mar 2014 12:32:56 +0200
Subject: Re: [Wikimedia-l] the big red notice on the top of 
http://strategy.wikimedia.org - done

Makes sense to me too.
Peter
- Original Message -
From: James Alexander jameso...@gmail.com
To: Wikimedia Mailing List wikimedia-l@lists.wikimedia.org
Sent: Sunday, March 09, 2014 12:12 PM
Subject: Re: [Wikimedia-l] the big red notice on the top of
http://strategy.wikimedia.org - done



On Sun, Mar 9, 2014 at 1:49 AM, Bohdan Melnychuk bas...@yandex.ru wrote:


But we close wiki. We not set wiki read only. Why should we use another
therm than the procedure is called?


Because what we DO (no matter what we call it) is set it as Read Only, it
is still 100% accessible you just can't edit it. I think it does make
sense
that 'read-only' is more understandable then 'close' which sounds like we
completely shut it off and you can't read it either.

James
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe



___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Statement for the police about the fundraising?

2014-02-07 Thread Isarra Yos

Who exactly would the webmaster of fi.wikipedia.org even be?

On 08/02/14 00:24, Kevin Gorman wrote:

My Finnish is hardly perfect, but the letter essentially outlines the
Finnish law regarding what is and what isn't money collection activities,
and then compares what goes on with fi.wikipedia.org with the relevant
Finnish statutes, concluding that the fundraising campaign is in fact a
money collection activity and thus needs a permit from the Finnish police.
They request that the webmaster of fi.wikipedia.org explains the purpose of
the fundraising text, and also furnishes the Finnish National Police Board
with information regarding the total sum of money that has been raised
through the text, at a date no later than the 21st of February.  They also
say that additional details may be required.  They indicate that it is
currently an administrative issue, but that the Police Board has the
authority to initiate investigations of criminal wrongdoing if the answers
of the webmaster of fi.wikipedia.org are unsatisfactory.

Best,
Kevin Gorman


On Fri, Feb 7, 2014 at 2:54 PM, Federico Leva (Nemo) nemow...@gmail.comwrote:


http://www.finlex.fi/fi/laki/ajantasa/1889/18890039001#L17P16b

Nemo


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe



___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Thanking anonymous users

2014-01-13 Thread Isarra Yos

On 13/01/14 20:37, Risker wrote:

m...@uberbox.orgOf course there already exists a way to thank IP
editors.  It is to go to their talk page and leave them a message that says
Thanks for your edit here [link to diff].  It is far more personal, far
more likely to encourage the user to edit further (and maybe create an
account?) based on research on the effects of template versus personalized
talk page messages to new editors, and doesn't require anyone to write any
code whatsoever.

I'm not entirely certain it's a good idea to technologize such very basic
user interactions.  It takes as much work to thank someone using
notifications as it does to leave them a talk page message.

Risker/Anne
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
I can see it now - a thank link that goes to the user's talkpage and 
opens a new section edit window, maybe with the header prefilled... but 
that would force a real interaction, and encourage real discussion...


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Thanking anonymous users

2014-01-10 Thread Isarra Yos

On 10/01/14 19:21, Ryan Kaldari wrote:

These are two reason we don't have Thanks for anonymous editors:
1. Anonymous editors don't get notifications
2. Multiple editors often share the same IP address
Problem #2 isn't as prominent as it use to be, but there are still many
large companies and schools that connect to the internet through a single
IP. I imagine that once IPv6 is widely in use, this problem will go away
and we'll be able to turn on all notifications (including Thanks) for
anonymous editors.

Ryan Kaldari
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe


1. Why not?
2. A time limit might help resolve that with ipv4 addresses. 
Alternately, thanks could potentially be nice even if they didn't make 
the edit themselves, since it's the general feeling and such, so just 
letting that through for ipv4 addresses might be an option.


Mind I'm mostly just echoing something someone else said on IRC just 
now, but they seem like interesting points to me.


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Fundraising banner obscuring site interface

2013-12-10 Thread Isarra Yos

On 10/12/13 14:57, David Gerard wrote:

True. However, do read the blog post on the need for caution in
answering such concerns with metrics.


- d.

And it's an excellent point to bring up. While I'm sure the fundraising 
team tries to keep in mind the balance between analytics results and and 
less measurable effects, reminders like this can be quite useful for 
everyone. It's like, /don't go overboard! In the meantime it works, but 
be careful./


Yes.

-L
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Office hours for VisualEditor

2013-10-30 Thread Isarra Yos

On 30/10/13 16:32, Bjoern Hoehrmann wrote:

* Risker wrote:

Just to clarify, since  UTC is a confusing time for most of us...is
that the minute after 2359 UTC on November 2 (i.e., 7 hours after the first
session), or is it the minute after 2359 UTC on November 3?

I've seen it used both ways so I just want to be clear.

Could you elaborate on this confusion and where you think it is common?
The 24 hour clock divides a day into 24 hours from 0 to 23 starting at
midnight. 23:59 is 23 hours and 59 minutes after 00:00 on the same day.

   2013-11-03T00:00Z --+
   2013-11-03T00:01Z   |
   ... |
   2013-11-03T00:59Z   |-- November 3rd
   2013-11-03T01:00Z   |
   ... |
   2013-11-03T23:59Z --+
   2013-11-04T00:00Z
   ...

The minute after 2013-11-03T23:59Z is on November 4th. I do understand
that when setting a deadline you are better off giving the end of a day
as deadline so the time is up when the day is over, otherwise people see
a contradiction and get confused, but beyond that I've not encountered
this particular confusion.
It's probably more common in places where people use 12-hour time for 
more things. Because many 12-hour conventions make absolutely no sense, 
folks can learn to expect time standards to make no sense and then don't 
know whether or not to expect 24-hour time to make sense because the 
precedent they're used to says it may not either.


So while 24-hour time does follow fairly logical conventions, if we're 
less used to using it we won't necessarily know to expect that, which 
might explain some of the confusion.


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Go away, community (from WMF wiki at least)

2013-05-13 Thread Isarra Yos
Employees have a separate wiki specifically for employee things. The 
foundationwiki is different from that, serving as a forefront to the 
movement itself, something which we are all a part of - and that admin 
access should be reflecting people's specific type of association with 
the movement doesn't seem to be a decided fact.


On 13/05/13 07:59, Jane Darnell wrote:

I can sympathize with the issue, namely, that it would be nice if only
Foundation employees could be allowed admin access on their own wiki.
I recall a similar issue (which was not so widely blown up) for our
WMNL board wiki in the Netherlands (and yes Phoebe, that is a very
boring wiki). I find it interesting to read Gayle's reaction, but I
don't think she should have apologized.

The way the community interacts with newbies is unforgiveable, period.
This is a perfect example of the reason that many women will go away
after their first few edits, or they grow some sort of special magic
Wikipedia filter. Even if she was just the messenger and it was
Philippe's idea, as far as the reactions to Gayle go, I agree with
Philippe's it's often damn hard to wade into these waters..., but I
would rather conclude with Staff members are Wikipedians too.

And don't get me started on the concept of higher standards!!

2013/5/13, phoebe ayers phoebe.w...@gmail.com:

On Sun, May 12, 2013 at 10:32 PM, Federico Leva (Nemo)
nemow...@gmail.comwrote:


Casey Brown, 13/05/2013 07:05:


[...] [Note that I'm speaking generally -- I personally think Gayle can

handle criticism and she seems very nice. She also probably had no
idea this would create dramz. My comment is directed towards the
general omg think of the staff member! response to criticism that is
systemic in our movement.]


Still, omg think of the staff member! seems to be the point Gayle and
Philippe make on this thread. If history teaches something, I guess the
board will soon approve a resolution to request the development of a
Personal Communitymember Filter to AT LAST hide all that offensive content
in our community. MediaWiki-mailman integration offers some challenges,
but
our commitment to openness will swiftly help, shutting down more mailing
lists in favour of wiki discussions.

Nemo


Au contraire, I feel we should all earn some kind of barnstar just for
participating in this discussion/situation. You know, it's kind of the
ultimate Wikimedian tempest: arguing over who gets to add users and delete
pages on what is quite possibly the world's most boring wiki[1]...

It's also a quintessentially Wikimedian debate because there's all this
subtext -- assumed but not articulated -- that isn't minor at all: about
community ownership versus corporate control, about who has authority to
make decisions in what sphere, about the role volunteers play in the
organization, over what personal reputation means on the projects, over
what admin rights mean, what kind of work environment the staff have, etc..
I'm gonna take a stab in the dark here and guess that Gayle wasn't
intending to start a debate on all these big important topics, or even
perhaps to comment on them at all. I'm also gonna say from experience that
it's often damn hard to wade into these waters and take an action *without*
touching off a debate on all these subjects. As someone said upthread, the
golden rule does help, as does practice working with the wiki way, and
knowing all the personal ins and outs of Wikimedia and our arcane culture.
But *even that* doesn't always save someone from making an unpopular
decision, or from screwing up or not thinking through all the ways they
might be wading into a minefield -- and that goes for all of us, staff,
board,  community alike. Hey, ask me how I know.

Sheesh, being part of the world's biggest collaborative project is hard
sometimes.

-- phoebe


1. I exempt, of course, the internal wiki at my workplace, which has won
the crown many years running.
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l



--
-— Isarra


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l


Re: [Wikimedia-l] [Wikimedia Announcements] Jared Zimmerman joins Wikimedia Foundation as Director of UX

2013-05-07 Thread Isarra Yos

Woot!

On 06/05/13 17:44, Erik Moeller wrote:

Hi folks,

It’s my great pleasure to announce that today, Jared Zimmerman will
start as Wikimedia Foundation’s Director of User Experience. As UX
Director, Jared will lead the design team and have a hands-on role on
the team, contributing his own design work. It’s still a small team
(Brandon, Vibha, May, and Pau), but we expect to hire an additional
3-4 designers in the coming 12-18 months.

Prior to Wikimedia, Jared was Principal Interaction Designer at
Autodesk, where he worked with engineers, visual artists, and user
experience researchers to create new software solutions for
architecture and design professionals with an emphasis on AutoCAD for
Mac and soon to be released online design collaboration tools. Jared
has led cross-disciplinary design teams in his roles at Autodesk,
Ammunition Group, and iconmobile, including creative direction.

At Autodesk, he was part of the transition to agile development and
helped his design teams apply those principles to their work. During
his time there he worked with design management to establish designers
as product owners in the scrum process, to further integrate them into
the development process from start to finish, as well as teaching his
team best practices for use of agile design tools.

Jared has degrees in Graphic Design (BGD) and Fine Art Photography
(BFA) from the Rhode Island School of Design. His photography has been
in featured in publications such as Travel + Leisure Magazine,
ZonaRetiro, and Huffington Post.

In addition to starting in his new job, Jared is also planning his
wedding in July to his fiancée Shannon. [1] In his spare time Jared is
wrapping up a remodel to their home, working on his first iPhone app,
experimental cooking, photographing the bay area  abroad [2], and
answering questions on Quora. [3]

I look forward to Jared’s leadership in helping elevate a delightful,
consistent and efficient User Experience to becoming a key measure of
success for our work.

Please join me in welcoming Jared! :-)

Erik

[1] http://shannonbadiee.com/
[2] http://www.flickr.com/photos/spoinknet/
[3] https://www.quora.com/Jared-Zimmerman/answers

--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation

___
Please note: all replies sent to this mailing list will be immediately directed 
to Wikimedia-l, the public mailing list of the Wikimedia community. For more 
information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
___
WikimediaAnnounce-l mailing list
wikimediaannounc...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l



--
-— Isarra


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l


Re: [Wikimedia-l] Introducing Ellie Young as Conference Coordinator

2013-03-29 Thread Isarra Yos
One needn't stick around to establish and maintain a working framework 
for such - continuity and knowledge-transfer sounds rather like 
consistency and maintainability of code, where if it is well set up and 
documented anyone can reasonably pick up where someone else left off.


So to ensure that there is continuity between events from year to year, 
the important thing would be the framework and that what was done gets 
written down - and in an organised and consistent fashion. That way 
never mind who it is in this position, the future organisers should 
still be able to find stuff from previous events as well, pick up where 
others left off, and continue from there.


On 29/03/13 02:06, Everton Zanella Alvarenga wrote:

Good point, Florence.

Is it like if we hired someone for a education position to work during
one school term for only 6 months.

Tom

On Thu, Mar 28, 2013 at 10:37 PM, Florence Devouard anthe...@yahoo.com wrote:

Welcome again Ellie

A question came to my mind when I read the description of the job.

- making sure there is good continuity and knowledge-transfer as the
conference moves to new hosts year-over-year.

Yet, she is taking on the role as an annual contract.

Is there not a contradiction here ?

Flo






--
-— Isarra


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l


Re: [Wikimedia-l] [Wikimedia Announcements] Announcement *please read*

2013-03-28 Thread Isarra Yos
It's odd, but I think I'm glad - not so much that you're leaving, but 
where you're going, what you intend to do... somehow I find that 
comforting...


On 27/03/13 22:00, Sue Gardner wrote:

Hello Wikimedia community members,

This is not an easy e-mail to write, and it’s been a very hard
decision to make. But I’m writing to tell you that I’m planning to
leave my position as the Executive Director of the Wikimedia
Foundation.

My departure isn’t imminent -- the Board and I anticipate it’ll take
at least six months to recruit my successor, and I’ll be fully engaged
as Executive Director all through the recruitment process and until we
have a new person in place. We’re expecting that’ll take about six
months or so, and so this note is not goodbye -- not yet.

Making the decision to leave hasn’t been easy, but it comes down to two things.

First, the movement and the Wikimedia Foundation are in a strong place
now. When I joined, the Foundation was tiny and not yet able to
reliably support the projects. Today it's healthy, thriving, and a
competent partner to the global network of Wikimedia volunteers. If
that wasn’t the case, I wouldn’t feel okay to leave. In that sense, my
leaving is a vote of confidence in our Board and executive team and
staff --- I know they will ably steer the Foundation through the years
ahead, and I’m confident the Board will appoint a strong successor to
me.

And I feel that although we’re in good shape, with a promising future,
the same isn’t true for the internet itself. (This is thing number
two.) Increasingly, I’m finding myself uncomfortable about how the
internet’s developing, who’s influencing its development, and who is
not. Last year we at Wikimedia raised an alarm about SOPA/PIPA, and
now CISPA is back. Wikipedia has experienced censorship at the hands
of industry groups and governments, and we’re --increasingly, I
think-- seeing important decisions made by unaccountable
non-transparent corporate players, a shift from the open web to mobile
walled gardens, and a shift from the production-based internet to one
that’s consumption-based. There are many organizations and individuals
advocating for the public interest online -- what’s good for ordinary
people -- but other interests are more numerous and powerful than they
are. I want that to change. And that’s what I want to do next.

I’ve always aimed to make the biggest contribution I can to the
general public good. Today, this is pulling me towards a new and
different role, one very much aligned with Wikimedia values and
informed by my experiences here, and with the purpose of amplifying
the voices of people advocating for the free and open internet. I
don’t know exactly what this will look like -- I might write a book,
or start a non-profit, or work in partnership with something that
already exists. Either way, I feel strongly that this is what I need
to do.

I feel an increasing sense of urgency around this. That said, I also
feel a strong sense of responsibility (and love!) for the Wikimedia
movement, and so I’ve agreed with the Board that I’ll stay on as
Executive Director until we have my successor in place. That’ll take
some time -- likely, at least six months.

Until then, nothing changes. The Wikimedia Foundation has lots of work
to do, and you can expect me to focus fully on it until we have a new
Executive Director in place.

I have many people to thank, but I’m not going to do it now --
there’ll be time for that later. For now, I’ll just say I love working
with you all, I’m proud of everything the Wikimedia movement is
accomplishing, and I’m looking forward to our next six months
together.

Jan-Bart’s going to write a note in a couple of minutes with
information about the transition process. We’ll be hosting office
hours this weekend as well, so anybody with questions can ask them
here or turn up to talk with us on IRC.

Thanks,
Sue



--
Sue Gardner
Executive Director
Wikimedia Foundation

415 839 6885 office
415 816 9967 cell

Imagine a world in which every single human being can freely share in
the sum of all knowledge.  Help us make it a reality!

https://donate.wikimedia.org/

___
Please note: all replies sent to this mailing list will be immediately directed 
to Wikimedia-l, the public mailing list of the Wikimedia community. For more 
information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
___
WikimediaAnnounce-l mailing list
wikimediaannounc...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l



--
-— Isarra


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Office hour inside out (program evaluation)

2013-03-23 Thread Isarra Yos

On 23/03/13 21:49, Everton Zanella Alvarenga wrote:

The India Education Program was really useful for my learnings before
I started coordinating the education program in Brazil. Without them,
I could have made similar mistakes. And this is one really important
thing about the nature of Wikimedia projects, they are not predictable
as a simple physics problem, and we have to value much more the
learnings from our mistakes.

At the same time, when you don't value these learnings to improve next
projects and have in your mind that trials must be succeed by success,
people can be afraid of sharing possible errors.

Without trials, things will continue progressing slowly. And
innovation will continue mediocre.

Tom

On Fri, Mar 22, 2013 at 9:41 AM, WereSpielChequers
werespielchequ...@gmail.com wrote:

We shouldn't criticise people for coming up with programs such as IEP and
AFT, but we should look at how long it took to stop them after serious
opposition arose and major flaws were pointed out. As a movement we need to
get much better at switching our efforts from blind alleys to things that
we can get consensus for.


Well said, mon. Well said.

--
-— Isarra


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l


Re: [Wikimedia-l] [Wikitech-l] open positions at WMF

2013-03-20 Thread Isarra Yos
On the other hand, how hard could it be to just write an extension to 
integrate a wordpress database and interface into a mediawiki? Call it a 
new namespace on the mediawiki end, and... uh... horrible things on the 
wordpress end...


I was going to say that if I had enough spare time I could probably pull 
that off, but putting this down in text it now occurs to me how utterly 
insane that is, especially considering how hard a time I had just making 
my own wordpress and mediawiki installs look the same.


Even so, it definitely could be done, and it'd probably be easier to 
maintain and update than making something from scratch. I mean, they're 
both php, with somewhat similar structures...


On 20/03/13 18:57, David Gerard wrote:

On 20 March 2013 02:06, K. Peachey p858sn...@gmail.com wrote:

On Wed, Mar 20, 2013 at 9:20 AM, Jay Walsh jwa...@wikimedia.org wrote:

We're really interested in wiki-fying the blog at some point too, or
at least marrying more of the technologies. I'd love to us to use a
wiki-based system, but that's a bit further down the pipeline. I'd
like to see us incorporate SUL so Wikimedia project usernames could be
used for comments and posting. I think that will be a question of
using our very limited resources, but I'm super interested in that.

MediaWiki + LQT (or the likes) for the comments and you are basically
there. In addition you have less to worry about in regards to the
WordpRess exploits (as pointed out by Daniel) and you open up to a
whole new ecocycle of developers we already have.


Cobbling together blog software is a one-man project; having a
versatile, well-maintained and mature blog engine with ubiquitous
third-party support is another matter. You could turn WordPress into
an encyclopedia CMS too, but it would be well below optimum.

WordPress has all manner of problems (I am painfully aware of this, I
have to hit it with a hammer in my day job) but it is basically the
best available for the job. MediaWiki has all manner of problems (you
are painfully aware of this, I'm certain) but, similarly, there's
nothing better for the job.

It's possible we could do better with something adapted, but not from
MediaWiki. For one thing, WordPress's visual editor works ...


- d.


- d.

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l



--
-— Isarra


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l


Re: [Wikimedia-l] [Wikitech-l] open positions at WMF

2013-03-20 Thread Isarra Yos

On 20/03/13 21:09, James Alexander wrote:

On Wed, Mar 20, 2013 at 1:54 PM, Isarra Yos zhoris...@gmail.com wrote:


On the other hand, how hard could it be to just write an extension to
integrate a wordpress database and interface into a mediawiki? Call it a
new namespace on the mediawiki end, and... uh... horrible things on the
wordpress end...

I was going to say that if I had enough spare time I could probably pull
that off, but putting this down in text it now occurs to me how utterly
insane that is, especially considering how hard a time I had just making my
own wordpress and mediawiki installs look the same.

Even so, it definitely could be done, and it'd probably be easier to
maintain and update than making something from scratch. I mean, they're
both php, with somewhat similar structures...




I actually don't think it would be. Mediawiki is an awesome tool for many
things but we really shouldn't be using it for things it isn't good
for/meant for. Wordpress is a very good, modular, option for bogs in
particular and is, in my opinion, a perfectly acceptable thing to use for
that. In order to have any good design setup for the blog on mediawiki we
would have to be using a fair bit of rawhtml (something that mediawiki
allows but was never really meant for) and very complicated templates. We
would also need to have a much more understandable comment system then
mediawiki has right now. Liquid threads isn't meant for this type of
conversation, mediawiki itself sucks horribly for a comment type system and
while flow type stuff may be helpful it is down the road and not really in
scope currently from my understanding.

In order to make it flexible enough for those running the blog on the front
end (Staff / Volunteers etc) we  would have to make it relatively easy to
understand that rawhtml/template system at least at some level which is, in
my opinion, too much to ask of them. They should be focused on what they
are writing and other work, not trying to work around the page itself. Our
current visual editor is also unlikely to be workable with
that complicated of a template system in any near future. It would create
an enormous amount of complication for something that doesn't need it.
Dogfooding our product is great but shouldnt' be done just because it
should be done where the product makes sense for the task.

James


James Alexander
Manager, Merchandise
Wikimedia Foundation
(415) 839-6885 x6716 @jamesofur
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l


MediaWiki is good for revision control and some forms of categorisation 
and has all our users. Wordpress works for blog displaying and 
organising pages and tagging stuff and generally throwing it at the 
readers. What I am suggesting would take both of those, stuff the -admin 
interface and editing and revisions into mediawiki, but have wordpress 
handle the content and displaying it to readers (just dealing with the 
current revisions on that end)... in a mediawiki skin, even, and then... 
well, explode, probably.


I dunno, if it didn't explode I know plenty of folks who would use this, 
but it probably wouldn't actually help Wikimedia that much, considering 
what they're apparently looking for specifically.


--
-— Isarra


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l