(Now continuing this discussion on Wikimedia-l also, since we are
discussing grant policies.)
For what it's worth, I repeatedly advocated for allowing IEG to support a
broader range of tech projects when I was on IEGCom. I had the impression
that there was a lot of concern about limited code review staff time, but
it serms to me that WMF has more than enough funds to to pay for staffing
for code review if that is the bottleneck for tech-focused IEGs (as well as
other code changes).
I also think that the grant scope policies in general seem too conservative
with regard to small grants (roughly $30k and under). WMF has millions of
dollars in reserves, there is plenty of mission-aligned work to be done,
and WMF itself frequently hires contractors to perform technical,
administrative, communications, legal and organizing work. It seems to me
that the scope of allowed funding for grants should be similar to the scope
of allowed work for contractors, and it would serve the purposes that
donors have in mind when they donate to WMF if the scope of allowed
purposes for grants is expanded, particularly given WMF's and the
community's increasing skills with designing and measuring projects for
In the past I think there were probably some wasteful uses of grant
funding, and the response at the time might have been to prohibit or refuse
to fund entire categories of expenses. Now that everyone has more planning
and evaluation capacity, it seems to me that this is a good time to rethink
the categorical prohibitions and replace at least some of them with
appropriate expectations for impact that would better serve our overall
mission of creating and sharing knowledge.
On Feb 21, 2015 12:05 PM, "Brian Wolff" <bawolff(a)gmail.com> wrote:
> On 2/21/15, Pine W <wiki.pine(a)gmail.com> wrote:
> > In general WMF has a conservative grant policy (with the exception of
> > grant funding seems to be getting more conservative every year, and some
> > mission-aligned projects can't get funding because they don't fit into
> > current molds of the grants programs). Spontaneous cash awards for
> > work are unlikely. However, if there is an existing project that could
> > some developer time, it may be possible to get grant funding for future
> > work.
> I find this kind of doubtful when IEG's (which for an individual
> developer doing a "small" project is really the type of funding that
> applies) have been traditionally denied for anything that even
> remotely touches WMF infrastructure. (Arguably the original question
> was about toollabs things, which is far enough away from WMF
> infrastructure to be allowed as an IEG grant, but I won't let that
> stop my rant...). Furthermore, it appears that IEGs now seem to be
> focusing primarily on gender gap grants.
> I find it odd, that we have grants through GSOC and OPW to people who
> are largely "newbies" (although there are exceptions), and probably
> not in a position to do anything "major". IEG provides grants as long
> as they are far enough away from the main site to not actually change
> much. But we do not provide grants to normal contributors who want to
> improve the technology of our websites, in big or important ways.
> Ostensibly this is done in the name of:
> >Any technical components must be standalone or completed on-wiki.
> Projects are
> >completed without assistance or review from WMF engineering, so MediaWiki
> >Extensions or software features requiring code review and integration
> cannot be
> >funded. On-wiki tech work (templates, user scripts, gadgets) and
> >standalone applications without a hosting dependency are allowed.
> Which on one hand is understandable. WMF-tech has its own priorities,
> and can't spend all its time babysitting whatever random ideas get
> funded. So I understand the fear that brought this about. On the other
> hand it is silly, since a grant to existing tech contributors is going
> to have much less review burden than gsoc/opw, and many projects might
> have minimal review burden, especially because most review could
> perhaps be done by non-wmf employees with +2, requiring only a final
> security/performance sign off. In fact, we do already provide very
> limited review to whatever randoms submit code to us over the internet
> (regardless of how they are funded, or lack thereof). If IEG grants
> were allowed in this area, it would be something that the grantee
> would have to plan and account for, with the understanding that nobody
> is going to provide a team of WMF developers to make someone else's
> grant happen. We should be providing the same amount of support to IEG
> grantees that we would to anyone who submitted code to us. That is,
> not much, but perhaps a little, and the amount dependent on how good
> their ideas are, and how clean their code is.
> [End rant]
> Politically, I think its dangerous how WMF seems to more and more
> become the only stakeholder in MediaWiki development (Not that there
> is anything wrong with the WMF, I just don't like there being only 1
> stakeholder). One way for there to be a more diverse group of
> interests is to allow grants to groups with goals consistent with
> Wikimedia's. While not exactly super diverse (all groups have similar
> goals), at least there would then be more groups, and hopefully result
> in more interesting and radical projects.
> Wikitech-l mailing list
could we by any chance return to the conservative Netiquette way of
creating subjets, or the New Era of inadequate subjects has just begun, and
we trend to soil the list with these marketing-based whatnots? Shall I go
to the details or are we all informatics-minded people here?
Hi, this is a status update for my WikiHiero rewrite! 
I've made a first pass on comparison, based on all hieroglyphic texts on
English Wikipedia: 
You can see the difference yourselves, in my opinion the general quality is
considerably better, and far more hieroglyphs are supported. However, a few
problems were identified, mostly related to WikiHiero accidentally allowing
invalid syntax in the past. I'm working on either fixing them in tokenizer,
e.g. converting "ra::" to something like "ra:.:." or making a fallback to
the old HTML renderer and adding a tracking category for future fixage by
editors. Some of the known problems are listed at . Unfortunately, this
also includes some cases where WikiHiero's hieroglyphs deviated from what
was said in standards, resulting in a mess that needs manual conversion
during a transitional period. These will also fall back on the old renderer
and be tracked.
The code is still being worked on, it can be seen in  (Hierator) and 
Max Semenik ([[User:MaxSem]])
In I562e437e, clickable anchors for section headers were added to the
parser's output, which is causing many extensions' tests to fail .
I will try to update some of the extensions' tests, but I'm hoping the
extension maintainers will update their tests to reflect this change since
I don't think I'll be able to update them all as of now.
Sincere apologies for the late notification.
Today Google Summer of Code 2015 and Outreachy (was FOSS Outreach Program
for Women, now open to other groups) have announced their call for
organizations. Wikimedia will apply to both programs. The deadlines are
February 20 and 17, respectively. THIS IS 7-10 DAYS FROM NOW!
We need to update the ideas page, but this time we will do it differently:
all project ideas need to be presented as a Phabricator task only (no
excerpt in wiki page page is needed). We will use a workboard to track the
readiness of project ideas.
If you are interested in participating as intern or mentor, follow
If you are interested in proposing a project idea, associate your task to
(work-in-progress drafts and other proposals subject to discussion are
I'm looking for a co-organizer to drive this round. We have a process that
works, a motivated pool of mentors, and room for creativity and
improvement. Between two people, the job is actually simple, and the
rewards are literally priceless (including the possibility to attend the
Mentors Summit). Nemo was a great co-organizer of Google Code-in, setting a
precedent that we want to consolidate. If you are interested, contact me.
Engineering Community Manager @ Wikimedia Foundation
Yesterday we opened the travel request process for Wikimedia Foundation
employees in Engineering and Product willing to participate at the
Wikimedia Hackathon or Wikimania. There is no public link, but you can
follow this task at https://phabricator.wikimedia.org/T89355
In this process, we are asking WMF employees to find a hackathon buddy with
the sole requirement of not being another WMF employee. In fact, in the
registration for the hackathons we will request the same to all
This means that non-WMF contributors might receive a request from a WMF
employee to be hackathon buddies. This also means that if you are planning
to participate in any of these events (and especially if you plan to
request travel sponsorship to Lyon) you will be encouraged to find a buddy
It's going to be fun. :) And no worries, we will help making connections
to whoever needs that help.
Engineering Community Manager @ Wikimedia Foundation