Fantastic work! :) VisualEditor is becoming really zippy -- which had been
one of the top concerns in user feedback in the past. Congratulations to
everyone involved.
Erik
--
Erik Möller
VP of Product Strategy, Wikimedia Foundation
___
Wikitech-l
On Mon, Mar 16, 2015 at 11:21 PM, Kevin Wayne Williams
kwwilli...@kwwilliams.com wrote:
There doesn't seem to be any particular user demand to adopt Flow,
so there's no reason to believe it will gain any more traction than LQT ever
did.
There was significant community interest and momentum
On Tue, Mar 10, 2015 at 3:29 PM, James Forrester
jforres...@wikimedia.org wrote:
Congratulations, Services team, and all those who've helped you get to this
point.
This is a huge milestone and I'm so happy we've reached it. It'll be
hugely valuable for Mobile Web, Mobile Apps, VisualEditor
Thanks for all _your_ work seeing this through the finish line as well,
Kunal. This is a great first step towards better user profile support, and
brings all Wikimedia wikis closer together.
--
Erik Möller
VP of Product Strategy, Wikimedia Foundation
Hi folks,
MediaWiki emits the hreflang attribute on language links, but only as part
of the links in the body, and not in the head as recommended by Google
[1]. The result of this is that Google (and possibly other search engines)
doesn't interpret the hreflang attribute for purposes of
On Thu, Feb 5, 2015 at 7:50 PM, MZMcBride z...@mzmcbride.com wrote:
Perhaps if Titan/Wikidata Query Service development is on hold, Nik could
investigate this?
Not really on hold - just looking at alternatives to Titan. But this
is a pretty critical issue for all our dev workflows, so really
On Wed, Feb 4, 2015 at 8:41 AM, Gabriel Wicke gwi...@wikimedia.org wrote:
Regarding general-purpose APIs vs. mobile: I think mobile is in some ways a
special case as their content transformation needs are closely coupled with
the way the apps are presenting the content. Additionally, at least
On Tue, Feb 3, 2015 at 5:46 PM, Dan Garry dga...@wikimedia.org wrote:
To address these challenges, we are considering performing some or all of
these tasks in a service developed by the Mobile Apps Team with help from
Services. This service will hit the APIs we currently hit on the client,
Just a quick note that I really appreciated everyone's help making the
summit come together. As always, we'll be doing lots of second-guessing of
everything we did and didn't do, and how we want to use future time
together. Before we go into that, I'd like to thank the event team and
_everyone_
Hooray! :-) You'll do great things, as always. Look forward to your
focused leadership in this area.
Erik
--
Erik Möller
VP of Product Strategy, Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Fri, Jan 16, 2015 at 1:14 PM, Ryan Lane rlan...@gmail.com wrote:
On Fri, Jan 16, 2015 at 12:27 PM, Ryan Lane rlan...@gmail.com wrote:
What you're forgetting is that WMF abandoned MediaWiki as an Open Source
project quite a while ago (at least 2 years ago).
{{citation needed}}
On Thu, Jan 15, 2015 at 10:57 PM, Tim Starling tstarl...@wikimedia.org wrote:
Sorry to labour the point, but the way to go about this at present is pretty
straightforward,
and it doesn't involve the architecture committee. You just convince the
management (Damon,
Erik, etc.) that it is a
On Thu, Jan 15, 2015 at 9:31 PM, Ori Livneh o...@wikimedia.org wrote:
On the leadership front, let me throw out a hypothetical: should we
have MediaWiki 2.0, where we start with an empty repository and build
up? If so, who makes that decision? If not, what is our alternative
vision? Who
This is fantastic -- kudos to everyone for pushing to get this through the
finish line. Making editing faster (and improving general site
responsiveness) is one of the most obvious things we can do that serves
every single contributor to our projects. We've still got lots more that we
can do in
As noted in the server admin log [1], Phabricator is currently down due to
a network outage impacting one of our racks in the Ashburn data-center.
We're investigating and will aim to restore service ASAP.
Erik
[1] https://wikitech.wikimedia.org/wiki/Server_Admin_Log
--
Erik Möller
VP of
On Wed, Nov 5, 2014 at 11:21 AM, Gabriel Wicke gwi...@wikimedia.org wrote:
What are the indexing requirements for this metadata? If fast access by
specific properties is needed
Most typically, I'm guessing you'd do stuff on a per-revision basis to
show quality indicators and such on page
Hi folks,
there are many projects which have an interest in generating and
querying metadata for specific revisions:
- community efforts to annotate quality of specific articles
- researchers analyzing revision contents (e.g. to derive quality
heuristics, perform citation analysis, etc.)
-
On Wed, Oct 22, 2014 at 11:56 PM, Pine W wiki.p...@gmail.com wrote:
It's been awhile since I've noticed a status update from the Growth that
team through the EE list or this list. The Meta page implies that the
Growth team disbanded on October 3. Is that true, and if so, does WMF still
have a
On Tue, Sep 30, 2014 at 2:33 PM, Federico Leva (Nemo)
nemow...@gmail.com wrote:
There must be a way that we can allow users to work from Tor.
RESOLVED FIXED http://meta.wikimedia.org/wiki/NOP
Not quite; if your _only_ means of access is Tor and you have no prior
editing history to point to
Ori and ...
Aaron Schulz, Alexandros Kosiaris, Brad Jorsch, Brandon Black, Brett
Simmers, Bryan Davis, Chad Horohoe, Chris Steipp, Erik Bernhardson,
Faidon Liambotis, Filippo Giunchedi, Giuseppe Lavagetto, Greg
Grossmeier, Jack McBarn, Katie Filbert, Kunal Mehta, Mark Bergsma, Max
Semenik,
On Sat, Aug 23, 2014 at 11:22 AM, Erik Moeller e...@wikimedia.org wrote:
The IE6 disable patch is in prod now. I've tested on a few wikis and
have not noticed any issues - if anything, IE6 actually feels usable
now when before it kept throwing errors or was just slowing to a
crawl
On Wed, Aug 6, 2014 at 11:52 AM, Erik Moeller e...@wikimedia.org wrote:
== Microsoft Internet Explorer 7.x ==
Last release in series: April 2009
- Browsing: Most pages work fine (some styling issues), but pages with
audio files cause JavaScript errors (problem in TMH).
- Editing: Throws JS
Hi folks,
Admins are currently given broad leeway to customize the user
experience for all users, including addition of site-wide JS, CSS,
etc. These are important capabilities of the wiki that have been used
for many clearly beneficial purposes. In the long run, we will want to
apply a code
This is fantastic progress, and really promising data. Huge kudos, guys :)
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Wed, Aug 6, 2014 at 10:15 PM, James Forrester jdforres...@gmail.com wrote:
Yes, this is sensible. Let's certainly not call it the MediaWiki API
given how many are planned.
Core seems a reasonable qualifier, though, no? Seems like the
content API and a lot of other proposed interfaces are by
On Mon, Aug 4, 2014 at 5:36 PM, Derric Atzrott
datzr...@alizeepathology.com wrote:
I would like to make a case for moving more browsers into the grade C
category.
Yes please. As a project that must live the test of time I think we should
be focusing our energy on building for future browsers.
Following up on disabling JavaScript support for IE6 [1], here is some
additional research on other browsers. I'd appreciate if people with
experience testing/developing for/with these browsers would jump in
with additional observations. I think we should wait with adding other
browsers to the
On Sun, Jul 27, 2014 at 2:25 AM, Krinkle krinklem...@gmail.com wrote:
Since Grade B never ended up being recognised in any way by the software,
I've kept that out. And the previously undocumented Grade C represents
browsers we are interested in supporting due to their traffic but only via
the
On Fri, Jul 11, 2014 at 8:45 AM, Luca Martinelli
martinellil...@gmail.com wrote:
so the Book Creator will still be active, maybe under another name,
maybe with another engine, but still active?
Same name and functionality, just the Order a printed book feature
will disappear.
Erik
--
Erik
Since 2008, we've offered a small feature to download printed books
from Wikipedia article. This is done in partnership with a company
called PediaPress.
They've sold about 15K books over that time period, not enough to
break even, and the support/maintenance burden for the service is no
longer
On Thu, Jul 3, 2014 at 9:09 AM, Jon Robson jrob...@wikimedia.org wrote:
== The future ==
Mantle is only a short term measure. The hope is that all the code
that goes here will eventually go into core. We hold the code here to
exactly the same high standards that we hold core to, we are just
As an update on the goals process for WMF engineering, we've begun
fleshing out out the top priorities for the first quarter. Going
forward, we'll aim to call out the top priorities for each quarter as
we approach it, to create more shared visibility into the most urgent
and high-impact projects
As a reminder, this is in 65 minutes.
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Raw logs here:
https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-06-25-17.30.log.html
Next steps:
1) Trevor, Roan, Timo, Kaldari and others will refine the proposal at
https://www.mediawiki.org/wiki/Requests_for_comment/Redo_skin_framework as
a concrete step to
Hi folks,
We're hosting a conversation about standardization and continued
development of front-end libraries in MW core on 6/25, 5:30 PM UTC,
#wikimedia-office.
This is driven by a recognized need for teams at WMF to work more
effectively on user-facing features and reduce duplication of
On Fri, Jun 13, 2014 at 6:06 PM, Pine W wiki.p...@gmail.com wrote:
Voodoo? Secret account in the Caymans set up by Fundraising Tech?
Wikishares?
If you want in on the Wikishares, it would be a nice test case for
Matt Walker's new PDF generator. :)
--
Erik Möller
VP of Engineering and Product
On Mon, Jun 9, 2014 at 11:14 PM, Pine W wiki.p...@gmail.com wrote:
FWIW, for me as a power user who watches many discussions simultaneously on
multiple wikis, a unified watchlist and more refined tools for watchlist
management are among the features at the top of my development wish list.
On Tue, Jun 10, 2014 at 1:09 AM, Thomas Gries m...@tgries.de wrote:
Watchlist and (fine-granular definable) E-Mail-Notifications are very
important - for my daily work.
LiquidThreads and Echo (if you opt-in to mail) offer that (using the
MediaWiki UserMailer functions).
Does Flow also
Hi all,
We've got the first DRAFT (sorry for shouting, but can't hurt to
emphasize :)) of the annual goals for the engineering/product
department up on mediawiki.org. We're now mid-point in the process,
and will finalize through June.
On Mon, Jun 9, 2014 at 12:12 PM, Risker risker...@gmail.com wrote:
This. Nobody, but nobody, asked the WMF to create this sort of system, and
it is a rather quixotic goal given that each project has its own set
of workflows.
Hey Anne,
We're of course pretty familiar with many of the highly
Dear Anne,
Thank you for the thoughtful critique.
There were four problems with talk/discussion pages that users across
multiple communities over multiple years have identified:
- Automatic signatures for posts/edits
- More efficient method for indenting that is not dependent on
It's being investigated, see #wikimedia-operations on irc.freenode.net.
Erik
On Thu, May 29, 2014 at 1:34 PM, ENWP Pine deyntest...@hotmail.com wrote:
Hi, I'm getting some 404 errors consistently when trying to load some
English Wikipedia articles. Other pages load ok. Did something break?
On Thu, May 15, 2014 at 8:06 AM, Jon Robson jdlrob...@gmail.com wrote:
Visual: ?
The mild conflict VisualEditor: conflict aside, that seems reasonable.
View: might also work if it's not used for something else. Either way,
it's going to be a bit tricky to translate.
It might be good to design
As a reminder, this is happening tomorrow at 12 PM PDT / 19:00 UTC
tomorrow (Tuesday):
https://plus.google.com/events/cae6ng1m9o4mhdbpo10u5v05bvg
We're going to talk about various strategies for automated testing and
improvements to our continuous integration infrastructure. Antoine
'hashar'
On Tue, Apr 15, 2014 at 8:47 AM, Nathan nawr...@gmail.com wrote:
In the comment thread at the bottom someone gave him a heads up about the
fonts controversy, hopefully he doesn't get totally discouraged from
MediaWiki design studies after reading it ;)
I actually think it's interesting that he
3
Thank you Erwin for always moving things forward. Much appreciated. :)
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Thu, Apr 10, 2014 at 7:39 AM, Derk-Jan Hartman
d.j.hartman+wmf...@gmail.com wrote:
So for me, the question is not how can we apply pretty serif fonts to
headers, the question is what can we do short term and long term to
make that happen.
It would be good if we could focus the conversation
On Tue, Apr 8, 2014 at 10:59 AM, Martijn Hoekstra
martijnhoeks...@gmail.com wrote:
So, the font stack changes with regards to the status quo now change
nothing for Windows users, changes Helvetica - Helvetica neue for Mac
users and changes Arial, DejaVu Sans or Arimo for possibly something
Just a note that Brandon just commented on the patchset:
We discussed this patch today during our weekly design team meeting
and how to move forward. At this point in time we are leaning towards
+2'ing this but we want to have a bit of discussion internally before
doing so.
We'll have something
On Tue, Apr 1, 2014 at 9:22 PM, Jon Robson jdlrob...@gmail.com wrote:
This is epic. Thanks a bunch Siebrand!
Agreed - really exciting to see this come to fruition! :) Kudos to
Siebrand everyone involved. I'm sure there will be bumps along the
road but it's clearly a bit architectural step
FYI.
-- Forwarded message --
From: Erik Moeller e...@wikimedia.org
Date: Fri, Feb 21, 2014 at 2:35 PM
Subject: Language Engineering team changes
To: All Wikimedia Foundation Staff
Hi folks.
After some internal conversations, we've implemented the following
changes
FYI.
-- Forwarded message --
From: Erik Moeller e...@wikimedia.org
Date: Fri, Feb 21, 2014 at 2:40 PM
Subject: Update on WMF Director of TechOps
To: All Wikimedia Foundation Staff
Hi folks,
in consultation with Faidon and Mark, we've decided not to immediately
post
We've been in discussions with Top Level Design, both to look into
potentially appropriate uses (e.g. URL shorteners) and to prevent
squatting of WMF trademarks.
James points out that now there's .foundation there's some additional
potential for mischief :P. Damn TLDs sprouting like mushrooms ..
On Mon, Feb 17, 2014 at 4:42 PM, Rob Lanphier ro...@wikimedia.org wrote:
tl;dr: His stack still lists HelveticaNeue as the first font, but proposes
Arimo as a web font which may well look better on MS Windows. Arimo ships
with ChromeOS.
So, what would be the downside of listing a font like
On Mon, Feb 17, 2014 at 7:19 PM, Steven Walling swall...@wikimedia.org wrote:
We basically tried the equivalent of this (placing relatively free fonts
unknown on most platforms first) which Kaldari talked about previously.
Ultimately that kind of declaration is useless for the vast majority of
Tim, this is great - thanks so much for getting it spun up, should be
very helpful for office hours and such.
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
___
Wikitech-l mailing list
Hi all,
I'm sorry to update you that Ken will be leaving WMF. He's agreed to
provide transitional support through February and March, and Mark
Bergsma will be Acting Director of TechOps starting today, sharing
some of the work with Faidon. Thanks to both of them for stepping up.
We'll be
On Mon, Jan 13, 2014 at 9:10 AM, Chris Steipp cste...@wikimedia.org wrote:
To satisfy Applebaum's request, there needs to be a mechanism whereby
someone can edit even if *all of their communications with Wikipedia,
including the initial contact* are coming over Tor or equivalent.
Blinded,
Hi all,
We had a fibre cut of our connection to our Tampa DC this morning. ETA
of a fix is still pending, but the cuts have been located and crews
are being dispatched. Meanwhile public traffic is being rerouted via
the public Internet, so most services should be reachable. Tampa is
our secondary
On Fri, Jan 17, 2014 at 11:08 AM, Marc A. Pelletier m...@uberbox.org wrote:
The problem isn't straight up vandalism (IPBE is no help there -- the
account'd get swiftly blocked) but socking. POV warriors know how to
misuse proxies and anonymity to multiply their consensus, and having
IPBE and
On Fri, Jan 17, 2014 at 1:38 PM, Risker risker...@gmail.com wrote:
End of the day, though, absent blocking problematic IP addresses and ranges
(which really can't be done unless the person blocking actually knows the
IP address or range), the socks and spammers just keep coming. This
problem
Thanks, Matt, for the detailed update, as well as for your leadership
throughout the project, and thanks to everyone who's helped with the
effort so far. :-)
As Matt outlined, we're going to keep moving on critical path issues
til January and will do a second sprint then to get things ready for
We were dealing with cascading site issues due to excessive database
queries, and are still investigating the root cause, but site should
be recovered by now.
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
___
Hi folks,
for a long time we've relied on the mwlib libraries by PediaPress to
generate PDFs on Wikimedia sites. These have served us well (we
generate 200K PDFs/day), but they architecturally pre-date a lot of
important developments in MediaWiki, and actually re-implement the
MediaWiki parser
On Fri, Nov 8, 2013 at 9:00 AM, Bryan Davis bd...@wikimedia.org wrote:
I think that picking the title Senior Software Engineer II may be
underselling the value of this highest tier to the outside world. In
my recent job search I saw a bit of the tech ladder side of the org
chart for several
On Thu, Nov 7, 2013 at 1:15 AM, Faidon Liambotis fai...@wikimedia.org wrote:
Faidon,
great questions.
The architect title, besides the job description that you described, is
also a seniority level within the WMF's engineering department. Other
organizations do e.g. sr./staff/sr. staff
On Wed, Nov 6, 2013 at 7:13 AM, Brion Vibber bvib...@wikimedia.org wrote:
* It makes sense to have a handful of folks as a core review planning
group.
* However, I would consider avoiding using the term Architect for its
members as it's easily conflated with existing WMF job titles. I think
tl;dr: I’d appreciate thoughts from the Wikimedia technical community
at large whether the designation of individual technical contributors
as architects should be meaningful, and if so, how to expand it
beyond the original triumvirate (Brion, Tim Mark), e.g. by
transitioning to a
On Tue, Nov 5, 2013 at 6:21 PM, Chad innocentkil...@gmail.com wrote:
I think I can respond to pretty much the whole idea here. I
think titles are pretty much a WMF-thing and shouldn't have
any bearing on MediaWiki :\
Just to be clear on how they currently do, in the relatively recently
This was due to a broken deployment of Parsoid, the new MediaWiki
parser used by VisualEditor. A new library dependency defaulted to
iso8859-1 instead of utf-8, which caused character munging to occur.
Gabriel is working on a postmortem and we'll share this shortly with
recommendations on how to
On Mon, Oct 28, 2013 at 7:12 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
Where I come from, beta does mean this is the direction we're
intending to go in, subject to testing and feedback before it's made
an official release.
That's right. There are two questions here:
- Do these
Hi folks,
after speaking to a few folks, I'd like to check in on the WMF deployment
train schedule overall, and see if there are ways to optimize it.
(Note: In the below I refer to test wikis vs. production wikis,
generously including mediawiki.org as a test wiki. I realize that our test
wikis,
Welcome on board, Gergő -- really looking forward to making images,
video and other media in our projects .. sparkle. ;-)
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
___
Wikitech-l mailing list
On Fri, Oct 4, 2013 at 9:34 AM, Brion Vibber bvib...@wikimedia.org wrote:
Can someone summarize this thread? As far as I can tell someone has invented
a requirement that all features be blessed by the WMF Features team, and I'm
pretty sure that can't be right. Can it?
Of course not. I think
On Thu, Oct 3, 2013 at 6:50 PM, Terry Chay tc...@wikimedia.org wrote:
We still eventually want to reach the point where the criteria is not the
amalgam of rules above
but a simpler one based on intent, expertise-sharing and consensus-building:
If any engineering department or community
On Sat, Sep 7, 2013 at 2:01 PM, Steven Walling swall...@wikimedia.org wrote:
Weekly deployment plans/notes
This monthly roadmap spreadsheet/wiki page
Quarterly plans, as represented in
https://www.mediawiki.org/wiki/Wikimedia_Engineering/2013-14_Goals and other
places
Yearly/annual plans
On Wed, Aug 28, 2013 at 3:19 PM, Tyler Romeo tylerro...@gmail.com wrote:
After many months of struggle, WMF takes one big step towards a more secure
Wikipedia. Good job everybody!
Agreed - fantastic to see this out the door :-). Thanks to everyone
who made it happen.
Erik
--
Erik Möller
VP
On Tue, Aug 20, 2013 at 12:46 PM, George William Herbert
george.herb...@gmail.com wrote:
The change must be delayed until people geographically / nationally denied
HTTPS can log in again.
Tim's working on a patch that should make this possible:
https://gerrit.wikimedia.org/r/#/c/80166/
The
On Tue, Aug 20, 2013 at 9:20 PM, Risker risker...@gmail.com wrote:
The mandatory use of HTTPS outside of a limited number of countries where
we know the editors will be blocked is not what I am talking about.
No, but the point is that there's no apolitical choice here. Actively
suppressing a
On Mon, Jul 22, 2013 at 8:44 PM, Tim Starling tstarl...@wikimedia.org wrote:
Newcomers with the VisualEditor were ~43% less likely to save a
single edit than editors with the wikitext editor (x^2=279.4,
p0.001), meaning that Visual Editor presented nearly a 2:1 increase
in editing difficulty.
On Mon, Jul 22, 2013 at 6:35 PM, James Forrester
jforres...@wikimedia.org wrote:
It would imply that Wikimedia thinks preference bloat is an appropriate way
forward for expenditure of donor funds. This would be a lie. Each added
preference adds to the complexity of our software - so increasing
On Tue, Jul 23, 2013 at 12:05 AM, Tim Starling tstarl...@wikimedia.org wrote:
I tried editing [[Argentina]] on my laptop just now, it took 45
seconds of CPU time and 51 seconds of wall clock time before the
percentage CPU usage began to drop. It's pretty slow.
Yes, that's why I said
On Mon, Jul 22, 2013 at 9:51 AM, Tyler Romeo tylerro...@gmail.com wrote:
Seriously, though, I understand why the VE team might want to force
everybody to use VE
That's a misrepresentation of the facts. We're not talking about
forcing people to use VE. We're talking about whether there should
be
On Mon, Jul 22, 2013 at 8:44 PM, Tim Starling tstarl...@wikimedia.org wrote:
and the results from Aaron Halfaker's study [2]
As noted at the top of the page, the analysis is still in progress.
Importantly, there were many confounding variables in the test, some
of which are already documented.
Scott -
I'm really glad that you've joined WMF engineering! The work on
Parsoid is groundbreaking. It will open the door to collaboration at a
scale not seen before. And it will require contributors of your level
of experience to pull it off.
Thanks for coming on board -- I look forward to
Hello all,
I’m delighted to announce that Ken Snider is joining the Wikimedia
operations team. He will start as an international contractor working
remotely from Toronto, Canada on June 10, and will be visiting SF in
the week of June 17. We’re currently in the process of seeking work
-- Forwarded message --
From: Erik Moeller e...@wikimedia.org
Date: Mon, Jun 3, 2013 at 3:56 PM
Subject: Engineering/Product Goals for 2013-14
To: WMF Engineering/Product
Dear all,
as those of you who’ve worked on individual goals have seen, we’re
only looking for focus areas
Yes, better support for display of images through a modal viewer would
be great. I'm not sure a modal parameter that has to be explicitly
set for files is the best approach - I would recommend optimizing the
default experience when a user clicks an image or video. It's not
clear that the current
FYI
-- Forwarded message --
From: Erik Moeller e...@wikimedia.org
Date: Mon, May 6, 2013 at 9:44 AM
Subject: Jared Zimmerman joins Wikimedia Foundation as Director of UX
To: wikimediaannounc...@lists.wikimedia.org
Hi folks,
It’s my great pleasure to announce that today, Jared
On Mon, May 6, 2013 at 7:20 PM, MZMcBride z...@mzmcbride.com wrote:
The reason I ask about a distinction is that there have been a lot of
changes to Wikimedia wikis lately and likely more to come, as the
Wikimedia Foundation has gotten larger and has more dedicated tech
resources. Overall,
On Tue, Apr 23, 2013 at 9:08 PM, Brian Wolff bawo...@gmail.com wrote:
Hi Brian,
We already have the page lang support.
What do you mean by that? AFAICT there's no existing designated place
in the schema for associating a content language with a specific page.
Thanks,
Erik
On Tue, Apr 23, 2013 at 10:00 PM, MZMcBride z...@mzmcbride.com wrote:
I'm not sure I'd call what you're proposing a major architectural
undertaking, though perhaps I'm defining a much narrower problem scope.
Yeah. A lot depends on whether or not we want language to be a first
class citizen at
Hi folks,
I'd like to start a broader conversation about language support in MW
core, and the potential need to re-think some pretty fundamental
design decisions in MediaWiki if we want to move past the point of
diminishing returns in some language-related improvements.
In a nutshell, is it time
On Wed, Apr 3, 2013 at 3:06 PM, Steven Walling steven.wall...@gmail.com wrote:
The best way to approach a
project like this is not to propose an up-front migration of an entire wiki
to a new piece of software, just to prototype a few new features.
I think the potential migration of content to
On Mon, Mar 18, 2013 at 10:29 AM, Tomasz Finc tf...@wikimedia.org wrote:
I'm pleased to announce that the mobile department has two new staff
members. Yuri Astrakhan Adam Baso join as sr. software developers on
the mobile partner team.
Welcome on board, guys. Really looking forward to the
On Thu, Mar 14, 2013 at 7:46 PM, Juliusz Gonera jgon...@wikimedia.org wrote:
I wouldn't be that optimistic, maybe it would slightly increase. Having an
account is one of the factors but I wouldn't underestimate user
friendliness. The first time I tried to find the URL to clone a repo in
On Mon, Mar 4, 2013 at 8:07 PM, Ori Livneh o...@wikimedia.org wrote:
Today I sprinted to pick up QUnit testing in Jenkins and get it
stabilised and deployed.
This is fantastic. Thanks, Timo.
Indeed - this is a great milestone. Thanks for all your work getting
this out the door, Timo! :-)
On Sun, Mar 3, 2013 at 6:06 PM, Brian Wolff bawo...@gmail.com wrote:
Personally I prefer it in the first line. Second to a good one line summary
of what was done, the bug number is the next most important thing. It
allows one to see the context the commit was made in. Having it in the
first
On Fri, Mar 1, 2013 at 2:20 PM, Jon Robson jdlrob...@gmail.com wrote:
I actually prefer bug numbers in the header.
+1, also useful for release notes. Could the footer line be
auto-generated for indexing purposes?
Yay for bikeshed topics ;-)
--
Erik Möller
VP of Engineering and Product
On Tue, Jan 15, 2013 at 12:08 PM, Rob Lanphier ro...@wikimedia.org wrote:
started yesterday as a Senior Software Engineer in our Platform
Engineering group (MediaWiki Core, specifically).
Welcome on-board, Ram :-). Look forward to your efforts on search,
which is in desperate need of love and
1 - 100 of 300 matches
Mail list logo
