Re: [Wikimedia-l] Foundation and affiliates disclosing salaries on job ads & the effect of this on workplace equity

2020-09-12 Thread Dan Garry (Deskana)
On Fri, 11 Sep 2020 at 22:23, Michael Peel  wrote:

> This seems to be a restriction against employers asking for someone’s
> salary history, not against including the expected salary range in a job
> advert.


Yes. Apologies, the "undoubtedly not doing this" written in my earlier
email was a bit unclear. Thanks for the clarity.

Dan
___
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] Foundation and affiliates disclosing salaries on job ads & the effect of this on workplace equity

2020-09-12 Thread Dan Garry (Deskana)
On Fri, 11 Sep 2020 at 12:39, Nathan  wrote:

> Shouldn't two candidates for the same position for the same company get
> roughly the same salary, regardless of where they live?
>

I don't know. Maybe.

Within the US, there are markets where decent, experienced software
engineers earn half of what a software engineer in San Francisco would
earn, and they would also probably have a comparable quality of life.
Outside the US, there are markets out there where the going rate
for decent, experienced software engineers is 15 times less than the going
rate for a software engineer in San Francisco. Due to the relative decrease
in purchasing power, the salary that's 15 times lower gives these people a
good quality of life comparable to (or possibly even better than) life in
San Francisco. Is it exploiting them to pay them 15 times less given that
their quality of life is the same, or even higher, than people in San
Francisco? Would it be fair to people in San Francisco, or other locations,
to do this? Should the Wikimedia Foundation pay people in this market 15
times more than they would earn at another company? As Gergő said, would
that be a responsible use of donor funds?

I don't have the answer to these questions. They are very hard questions
where there is no obviously correct answer.

Dan
___
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] Foundation and affiliates disclosing salaries on job ads & the effect of this on workplace equity

2020-09-11 Thread Dan Garry (Deskana)
Asking candidates for their current salary is prohibited in San Francisco
as of July 2018 [1] which means that, as a San Francisco based
organisation, the Foundation will undoubtedly not be doing this. To my
knowledge, this wasn't done by the Foundation before either, but we can
confidently state that it won't be done now.

There are some complexities in disclosing salary ranges for the Foundation.
One practice that can be used for encouraging diversity in candidate
applications is to specify that a position is open to candidates with a
wide range of experience and in all locations in the world, in which case
the salary range posted will be so large that it will basically be
meaningless. On the other hand, another good practice for encouraging
diversity is to source internally for senior positions, which opens up more
junior roles that can be sourced externally, in which case a salary range
can be more meaningful and helpful. It's hard to figure out what the right
balance is.

Regardless, more public transparency in salary banding would be good to see.

Dan

[1]:
https://www.shrm.org/resourcesandtools/legal-and-compliance/state-and-local-updates/pages/san-francisco-bans-salary-history-questions.aspx

On Fri, 11 Sep 2020 at 10:44, Chris Keating 
wrote:

> Good morning everyone!
>
> There's a campaign(1) for nonprofits to disclose the salaries, or at least
> salary ranges, on job ads.
>
> An increasing body of evidence(2) shows that practices like not disclosing
> expected pay, and requiring applicants to disclose their current salary, is
> harmful to equity in the workplace.
>
> Not disclosing salaries affects pay levels within the organisation -
> because white men are usually relatively confident in negotiating their
> salaries upwards, so tend to end up with a better deal.
>
> It can also affect the diversity of candidates who apply. Candidates who
> have stronger networks within the industry they're moving into (again, more
> commonly white men with privileged social and educational backgrounds) also
> have clear expectations because they are 'in the know' about industry
> norms, while people who don't, find the lack of salary information a
> barrier to application. (After all, why take the time and effort to apply
> for a job when you have no idea how the likely pay compares to your current
> employment?)
>
> I know practices vary within the movement - I believe the WMF never
> mentions salaries on ads, and I don't know whether the range is disclosed
> to applicants or not - some chapters I know do advertise a salary. However,
> I'd urge all entities within the movement that hire staff to disclose the
> expected salary ranges for posts they are advertising, as part of their
> commitment to equality, diversity and inclusion.
>
> Thanks for reading,
>
> Chris
>
>
>
> (1): https://showthesalary.com/
> (2): e.g. at https://showthesalary.com/resources/
> ___
> 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] Institutional memory @ WMF

2020-08-26 Thread Dan Garry (Deskana)
On Wed, 26 Aug 2020 at 12:16, Strainu  wrote:

> Thanks for the response Dan!
>
> A rigorous study is IMHO impossible, since we're lacking a rigorous
> definition of the limits between WMF and community.
>

Absolutely agreed.


> OK, but how is this done precisely? Are there written docs? Mentors?
> Is cross-team help common? Or is this kept at the anecdotal level ("oh
> yeah, you should also keep in mind..." )?
>

In my experience, all of the above. What is done exactly depends on the
situation, but all of those things you've listed can and do happen,
depending on the nature and size of the project, the people involved, and
so on. People keep their eye out, through both formal and informal
mechanisms, and help out if they think they can.

I don't want to go into specific details, as I'm doing it purely from
memory and might misremember things, and things might've changed since I
left the WMF two years ago. To be clear, I'm not under any kind of
non-disclosure agreement, I just don't want to be inaccurate.

Dan
___
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] Institutional memory @ WMF

2020-08-26 Thread Dan Garry (Deskana)
On Tue, 25 Aug 2020 at 22:26, Strainu  wrote:

> The pattern I'm seeing is: team gets a big project (in this case UCoC)
> -> team hires -> newbie makes good faith edits that are known to cause
> offense to some members of the community.


This is basically always going to happen when new people are onboarded, or,
indeed, as people make mistakes. By my observations, this happens a lot
less nowadays than it used to. This is anecdotal on my part, but in the
absence of any rigorous study of the frequency with which this occurs, this
thread as a whole is anecdotal. That's not to say it's not valuable to
discuss it, but it's worth bearing that in mind.


> This pattern can be broken
> only if the organization has a process to teach newcomers things that
> seem obvious to old timers ("don't go over community decisions if you
> can avoid it", "don't change content", "try to talk to people before
> doing a major change", "not everyone speaks English", "affiliates are
> not the community" etc.)
>
> My question is: does the WMF has such a process?
>

When people are onboarded a lot of this is explained to them, and people
are encouraged to reach out to those more experienced with the communities.
That people get it wrong occasionally is expected.

Dan
___
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] Universal Code of Conduct Drafting Committee - Call for participation

2020-07-31 Thread Dan Garry (Deskana)
On Fri, 31 Jul 2020 at 15:29, Todd Allen  wrote:

> That was a firm "No" on any Universal Code of Conduct. There shouldn't be a
> "drafting committee" for it, it was disapproved.
>

It's not clear to me what you're referring to here. What is the "that" that
was a "firm no"?

Dan
___
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] Paid API?

2020-07-09 Thread Dan Garry (Deskana)
On Thu, 9 Jul 2020 at 21:15, Dan Garry (Deskana)  wrote:

> ECR and GKE.
>

Correction: I meant GCR, not GKE.

Dan
___
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] Paid API?

2020-07-09 Thread Dan Garry (Deskana)
On Thu, 9 Jul 2020 at 18:20, Amir Sarabadani  wrote:

> * I find it ethically wrong to use AWS, even if you can't host it in WMF
> for legal reasons, why not another cloud provider.


Which cloud provider would you recommend? Popular alternatives to AWS
include GCP (by Google, who unscrupulously harvest user data and sell it
for profit) and Azure (by Microsoft who arguably owe their position in the
market due to numerous anti-competitive practices for which they have
fought, and lost, numerous lawsuits). In addition to that, there are
numerous other factors to consider, such as cost (we should be responsible
with donor money), and environmental impact of the hosting choice in
question. My point is, there is no objectively correct ethical choice.

There's also numerous other factors to take into account in addition to
ethics. There are different feature sets that each cloud provider offers;
as an example, I recently did a competitive analysis of different
cloud-hosted container registry providers, and was surprised at the large
number of feature differences in each provider, even for something as
relatively straightforward as a container registry, even between ECR and
GKE. Engineering productivity is an important factor too.

From a project management perspective, it seems to me that the most prudent
thing to do is to choose a solution for prototyping rather than spending an
excessive amount of time analysing it. After all, time is money. I would be
concerned by the choice of AWS if this were in any way a permanent choice,
but the docs specifically mention that AWS is being used for ease of
prototyping, and that the long-term solution is presently undetermined.

Dan
___
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] Status of APG and FDC?

2020-03-10 Thread Dan Garry (Deskana)
Hi all,

Does anyone know what the status of the APG process and the FDC is? The
documentation on-wiki seems to be out of date:

   - The APG info page [1] says new applications are not being accepted,
   and there's a bunch of errors in the table.
   - The APG page [2] doesn't make reference to the above statement about
   new applications not being accepted.
   - The FDC page [3] says the terms of all of the members expired in
   either 2018 or 2019, and doesn't make any reference to the above either.

Thanks!

Dan

[1]: https://meta.wikimedia.org/wiki/Grants:APG/Information
[2]: https://meta.wikimedia.org/wiki/Grants:APG
[3]:
https://meta.wikimedia.org/wiki/Grants:APG/Funds_Dissemination_Committee
___
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] Movement Strategy: Recommendations and community conversations launching next week

2020-02-03 Thread Dan Garry (Deskana)
On Sat, 25 Jan 2020 at 23:49, Pine W  wrote:

> Here are a couple of arguments from WMF in favor of SuperProtect, which was
> implemented to prevent local users from removing MediaViewer.


Superprotect is now over five years old. Superprotect's removal is now over
four years old. It was a mistake, and it was explicitly acknowledged as
such: the then-ED of the WMF said it had "set up a precedent of
mistrust". Almost all of the people involved in it are no longer affiliated
with the Wikimedia Foundation, and in fact, plenty of the staff members at
the Wikimedia Foundation were hired *after* superprotect was removed.

I don't think bringing up superprotect in this discussion is especially
relevant or helpful.

Dan

Source for most of the above: https://meta.wikimedia.org/wiki/Superprotect
___
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] Ombuds Commission now accepting nominations for 2020

2019-10-11 Thread Dan Garry (Deskana)
On Fri, 11 Oct 2019 at 08:52, Henry Wood  wrote:

> So the Ombudsman Commission is managed by a department that they are
> likely to want to report on?
>

No. The Ombudsman Commission oversees volunteer actions only. Complaints
about staff should be sent directly to the Wikimedia Foundation.

I should note that the Ombudsman Commission page on Meta
 does not explicitly
state what I have said above; I am basing my comment on my past experience
when I was on the Ombudsman Commission.

Dan
___
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] [Wikitech-l] Community Tech: New Format for 2020 Wishlist Survey

2019-10-07 Thread Dan Garry (Deskana)
On Sun, 6 Oct 2019 at 05:50, Gerard Meijssen 
wrote:

> The disappointing you show and the grotesque conclusions are imho based
> in a sense of entitlement.


I don't think calling Yuri's conclusions grotesque or saying he is entitled
are particularly productive comments. Let's keep this list discussion calm,
please?

Dan
___
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] Introducing Wikimedia Space: A space for movement news and conversations

2019-06-26 Thread Dan Garry (Deskana)
On Wed 26 Jun 2019 at 00:58, Amir Sarabadani  wrote:

> I have no comment on Wikimedia Space. IMHO it's too soon to criticize it
> but I want to point out to a pattern that I have been seeing in the past
> couple of months by several people in this very mailing list.
>
> You have been repeating the word "WMF" (four time, for four different
> purposes) and treating it as a big monolith which is far from truth, WMF
> consists of different teams with different focuses, priorities, goals, and
> processes.
>
> This type of comments also increases the tension by promoting concept of
> "volunteer vs. WMF". It's not a war, we have the same mission. Stop
> criticizing a huge organization devoted to support volunteers (which you
> can't deny all of its good deeds, like keeping servers the world-class
> website running while being horribly understaffed, we have only 1% of
> Google's staff) because you disagree with this project or that program.
>
> Criticize projects, criticize actions (which can be valid), but don't be
> like "here we go again, WMF".


Largest possible +1 to this. Thanks Amir.

Dan
___
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] WMF commitment for a Wikimedia projects archive

2019-05-07 Thread Dan Garry (Deskana)
On Tue 7 May 2019 at 11:04, Fæ  wrote:

> I am sure this Wikimedia wide community run list is a perfectly good place
> to check whether the WMF has any commitment to long term public archives,
> or not.
>
> Thanks for your advice as to where to go, but the strategy process groups
> are undoubtedly a worse place to ask this question and expect a verifiable
> answer.


I see! Then I will defer to your clear expertise in getting definitive
answers. I look forward to seeing the outcome!

Dan
___
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] WMF commitment for a Wikimedia projects archive

2019-05-07 Thread Dan Garry (Deskana)
I think the correct venue to ask for such a large, cross-cutting, strategic
commitment would be with the strategy process working groups, and not this
mailing list. Did you try engaging with them?

Dan

On Tue, 7 May 2019 at 09:35, Fæ  wrote:

> With all of the strategy discussions still on-going, it would be good
> to know where the long term public archive of our Wikimedia projects
> sits within it.
>
> As has been mentioned on this list previously, when volunteers donate
> to the Internet Archive, there is some comfort that their efforts in
> helping preserve public domain media will be accessible and archived
> for 100 years.
>
> I have been unable to work out what the Wikimedia Foundations
> commitment is to maintaining a publicly accessible project archive. I
> may be wrong and would love to have someone post a link that puts me
> right, but based on past discussions, I suspect that if a project gets
> closed or mothballed, there is no specific commitment to fund public
> access to any archives. The WMF may be unable to match the 100 year
> commitment that the Internet Archive plans for, but it would be jolly
> nice to have a commitment to something and have that promoted in the
> long term strategy.
>
> The best example I can think of is Wikimedia Commons as this is a
> significant size, so committing to maintaining a 10 or 20 year archive
> (not just an operational backup) is not an insignificant thing to find
> publicly accessible server space for or earmark a specific budget for.
>
> Thanks,
> Fae
> --
> fae...@gmail.com https://commons.wikimedia.org/wiki/User:Fae
>
> ___
> 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] Supporting Wikinews [was: Reviewing our brand system for our 2030 goals]

2019-04-17 Thread Dan Garry (Deskana)
On Wed, 17 Apr 2019 at 15:41, Yaroslav Blanter  wrote:

> Indeed, I am not a fan of Wikinews and I do not particularly see the
> project as in any way successful. However, if the project is shut down
> against the will of the community (I now mean the Wikinews community, or
> perhaps even specifically the English Wikinews community), I will ask
> myself  whether Wikivoyage (I am active in the Russian Wikivoyage, where we
> have a couple of dozen active users) could also be shut down one day
> against the will of the community, just because we are not successful
> competing with the brands like Lonely Planet, DK, or Michelin, for example.
>

I've not seen any proposals involving shutting down projects without
community involvement, so hopefully you shouldn't need to worry about this.

Dan
___
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] Supporting Wikinews [was: Reviewing our brand system for our 2030 goals]

2019-04-16 Thread Dan Garry (Deskana)
Splitting off the Wikinews discussion from the branding discussion...

On Tue, 16 Apr 2019 at 07:52, Jennifer Pryor-Summers <
jennifer.pryorsumm...@gmail.com> wrote:

> Compared to Wikitribune it is!  But more importantly, if Wikinews is not
> thriving, then why not?  Does it lack resources?  What could or should the
> WMF do to revive it?


In my opinion, nothing. Wikinews was a nice idea, but it didn't work out,
and I don't think the Wikimedia Foundation investing resources into trying
to bring it back to life is really worth it. In fact, I think the Wikimedia
Foundation isn't the right group to try to breathe new life into the
project anyway—we, as a volunteer community, could invest our time in
bringing new content into it. That doesn't happen though. Why is that? For
me, I'm voting with my actions rather than my words—it's because it just
isn't important enough compared to other things. It's okay to think that.

Also, I'd prefer to see the Wikimedia Foundation trying to do fewer things
but do them better rather than taking more on; I think the annual plan
reflects that it is trying to do so.


> Perhaps some of the money spent on rebranding would
> be better spent on the  projects that are not doing so well as the big
> Wikipedias -- or perhaps the WMF should cut its losses and close them down,
> on the principle of reinforcing success instead.
>

I suspect that significantly less money is being spent on this rebranding
effort than people might think. A short engagement with an external
consultant, and some staff time to think about it and publish some pages to
solicit comment, is a relatively small investment compared to what it might
take to bootstrap improvements to breathe life into a mostly dead project.
I don't think it's really helpful to guess about the cost of things... yes,
I broke my own rule right at the start of this paragraph. ;-)

Dan
___
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] branding is bikeshedding, how about CTO criteria or working group lists instead?

2019-04-16 Thread Dan Garry (Deskana)
On Mon, 15 Apr 2019 at 21:09, James Salsman  wrote:

> I withdraw any opinions and suggestions about the branding discussion,
> and don't intend to continue participating in it. Instead, I would
> like to have a more substantive discussion:
>
> (1) I ask that the CTO search team please publish their search and
> requirement criteria, including the CTO job description and any and
> all goals for the CTO position whether in current planning documents
> or unpublished drafts of planning materials.
>

Much of this is contained the job description
,
which is posted publicly on the Wikimedia Foundation website
.

Is there something specific you think is missing?

Dan
___
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] branding is bikeshedding, how about CTO criteria or working group lists instead?

2019-04-16 Thread Dan Garry (Deskana)
On Tue, 16 Apr 2019 at 10:14, Gerard Meijssen 
wrote:

> Hoi,
> Thank you for your sense of superiority..


It's not helpful to sarcastically "thank" someone like this. I don't find
Chris to have had a sense of superiority in his email, but even if he had,
this is not the correct way to address it.

Dan
___
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] Wikimedia has been accepted as a mentor organization in GSoC 2019!

2019-02-28 Thread Dan Garry (Deskana)
As Srishti says, community wishlist items tend to be very under-defined,
with open-ended and ambiguous deliverables, and exist in complex spaces.
These things are okay because the people handling them are professionals
who are trained specifically to distill open-ended projects into specific
deliverables, and because the contract with community wishlist items is
specifically *not* that the items will be done, but that the items will be
evaluated and responded to.

On the other hand, projects like GSoC are aimed at training and mentoring
people new to software development on best practices, coding paradigms, and
so on. The students need very well-defined, specific projects in order to
succeed, and wishlist items tend not to have these characteristics. Simply
funnelling wishlist items directly into GSoC would set up the participants
for failure.

So, some kind of refinement of the wishlist items is needed. Now, it
*is* possible
to distill certain wishlist items down into small, byte-sized, well-defined
GSoC projects, for sure. But that will take time, user research,
resourcing, etc. I think that's worth doing, but it is a resourcing
question, and we need to ask the question of what other work the product
folks will drop in order to make that happen.

Dan

On Wed, 27 Feb 2019 at 03:01, James Heilman  wrote:

> We have a lot of amazing potential projects that just missed the selection
> criteria for the community wish list in 2019
>
> https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Results
>
> Would some of these quality as projects?
>
> James
>
> On Tue, Feb 26, 2019 at 2:11 PM Srishti Sethi 
> wrote:
>
> > Hello everyone,
> >
> > Wikimedia has been accepted as a mentor organization in the Google Summer
> > of Code 2019 with 207 open source projects
> > 
> > :)
> > And, application period for Outreachy Round 18 started last week.
> >
> > We have listed a few ideas for projects for both programs on MediaWiki
> and
> > we are looking for more. Unlike Google Summer of Code, Outreachy is open
> to
> > non-students and non-coders and projects could be around documentation,
> > design, translation research, outreach, etc. View current list of ideas:
> >
> > https://www.mediawiki.org/wiki/Google_Summer_of_Code/2019
> >
> > https://www.mediawiki.org/wiki/Outreachy/Round_18
> >
> > Both these programs have a similar timeline for the summer round.
> Accepted
> > candidates will work with mentors from May to August 2019. If you are
> > interested in mentoring a project, create a task on Phabricator and tag
> it
> > with #outreach-programs-projects and #Google-Summer-of-Code (2019) or
> > #Outreachy (Round 18). You can also choose to mentor for projects already
> > on outreach-programs-projects
> > 
> > workboard. Remember, every project must have two mentors.
> >
> > Some helpful resources for you:
> > * Learn more about the roles and responsibilities of a mentor:
> > https://www.mediawiki.org/wiki/Google_Summer_of_Code/Mentors
> > https://www.mediawiki.org/wiki/Outreachy/Mentors
> >
> > * View full program timeline:
> > https://developers.google.com/open-source/gsoc/timeline
> > https://www.outreachy.org/apply/project-selection/
> >
> > Looking forward to your participation! :)
> >
> > Cheers,
> >
> > Srishti, Derick and Pratyush (Wikimedia org admins)
> >
> >
> > *Srishti Sethi*
> > Developer Advocate
> > Wikimedia Foundation 
> > ___
> > 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,
> > 
>
>
>
> --
> James Heilman
> MD, CCFP-EM, Wikipedian
> ___
> 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] Strategic planning for conferences

2019-01-31 Thread Dan Garry (Deskana)
It may be helpful if you repeat the specific question you're asking. Right
now from your email I don't know what your question is other than asking
what the "strategy for conferences" is, which is so open and vague as to be
basically unanswerable. I think you have perhaps made your question clearer
in the past, but staff are quite frequently buried in so many emails that
more difficult to answer emails tend to languish. The easier you make it to
get an answer, the more likely you are to get one.

Dan

On Wed, 30 Jan 2019 at 23:37, Pine W  wrote:

> Hi Alex,
>
> I hope that you are doing well. I originally started this email thread on
> Wikimedia-l near the end of September 2018, and four months have passed. I
> am still hoping to hear an update about WMF's strategy for conferences. I
> am trying to be patient and considerate, but I think that you may
> understand that I have difficulty with the length of the delay here. It
> seems to me that questions like this should not take WMF four months to
> answer, and that no one should need to send repeated requests for
> information like this. Once in awhile someone might be on vacation or an
> email might get stuck in a draft folder so one additional reminder or
> request might be necessary, but I think that the situation with this email
> thread should not ever happen. In addition to my original questions
> regarding conference strategy, I would like to know what has caused the
> lengthy delay and the lack of responsiveness from WMF. I am trying to be
> patient, but there is a problem here.
>
> Thanks,
>
> 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, 


Re: [Wikimedia-l] Survey about the Foundation's Mission

2019-01-16 Thread Dan Garry (Deskana)
James,

As is fairly typical with your proposals, most of the proposals in the
survey (free healthcare, universal basic income, etc.) have very little to
do with the Foundation's mission. If you're going to do a survey, I suggest
actually connecting it to the Foundation's mission, although sadly it seems
that suggestions like this fall on deaf ears.

Dan

On Wed, 16 Jan 2019 at 02:21, James Salsman  wrote:

> Happy 18th birthday to Wikipedia!
>
> What does it mean for the Wikimedia Foundation to empower
> contributors? Please share your opinion of what the Wikimedia
> Foundation's mission statement means when it describes empowering
> people to collect and develop educational content:
>
> http://bit.ly/wikimission
>
> The survey results are summarized after form submission.
>
> Best regards,
> Jim Salsman
>
> ___
> 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] Update and feedback results from the Wikimedia's chairpersons retreat

2019-01-03 Thread Dan Garry (Deskana)
On Sun, 30 Dec 2018 at 03:39, Pine W  wrote:

> I am wondering whether, for the purposes of (1) increasing the cost
> effectiveness of travel expenses, (2) reducing the negative environmental
> effects from travel, and (3) increasing the number of chairpersons who
> participate, if future meetings could be scheduled immediately before or
> after Wikimania or the Wikimedia (WMF + Affiliates) Summit.


This is already being done to a large extent. For example, lots of team
offsites are scheduled to run either before or after the annual all staff
meeting, hackathons, Wikimania, etc, which wasn't really the case a few
years back. The effects of this policy can be seen in the annual financial
statements—in FY2013/14 and FY2017/8 the amount spent on travel and
conferences was almost exactly the same [1] in spite of the Foundation
having grown by around 100 staff [2].

As to whether more bundling of meetings with other meetings should be done,
I find it to be a mixed bag. On the one hand, travel spending is reduced,
and it's more likely that people can attend meetings due to bundling things
together. On the other hand, the effectiveness of the meetings is reduced;
conferences like Wikimania are exhausting enough without having to do
important meetings that require a lot of concentration either before or
afterwards. Whether that trade-off is worth it or not depends on the
situation. It's certainly not as clear cut as you make it out to be here.

With regards to environmental impact, I always recommend the "green stuff"
thread
.

Dan

[1]: Source: Wikimedia Foundation financial reports
. In FY2013/14
there was a total of $1,965,854 spent on travel and conferences, and in
FY2017/18 the same spending was $1,954,772. Travel spending fluctuated up
by around 17% in the years between these, but it went back down afterwards.
Travel spending has remained basically the same despite significant growth
of the organisation, demonstrating the effectiveness of policy changes on
decreasing travel spending.

[2]: Source: my memory. An exact figure could probably be figured out by
looking at the history of the staff and contractors page on
foundation.wikimedia.org.
___
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] Mobile fundraising ads

2018-12-10 Thread Dan Garry (Deskana)
On Wed, 5 Dec 2018 at 11:44, vermont--- via Wikimedia-l <
wikimedia-l@lists.wikimedia.org> wrote:

> Entering Wikipedia while not logged in, from both a PC and mobile device,
> lead to an insane amount of large, bright red banners asking for donations.
> Statistics may show that this sort of advertising gains the most clicks
> and donations. That should not be the only metric by which donation
> requests are decided.
>
> We are losing readers because of this.
>

Whilst there are certainly anecdotes to this effect, there's no evidence at
present that we're losing any more readers than normal. For example, page
views to the Simple English Wikipedia

(I chose this wiki because you linked to it in your email) are relatively
stable. Now, eyeballing page view graphs like I did is not really
scientific, but it gives a better indication than relying on isolated
comments.

Criticism of the fundraising banners (and there is plenty of it) will be
better received by the Fundraising team if we all stick to the facts, and
avoid extrapolation and hyperbole.

Dan
___
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,