Hoi,
It has always been very clear that the script conversion for Serbian and
Chinese is very important. Every time it has been stressed that it needs to
remain available. The fact that technically you have a challenge does not
take anything away from it.
I am quite confident that the Language
We could also try convincing the semi-decent shared hosts like Dreamhost
and Linode to run a service of their own for their customers.
That reminds me, I had an idea lying around somewhere about making it
possible for things like shared hosts to offer configuration hints to
the installer.
May someone help me?
I have read the short documentation of variables like:
$wgInternalServer
$wgServer
But I don't understand how combine them to get the Mediawiki accessible
internally with a local IP AND externally with a FQDN without broking the
absolute links of the CSS and javascripts.
So if all wikis on world would use this central parsoid, I wouldn't
like to see that huge outage when the parsoid server breaks :P
On Wed, Jan 28, 2015 at 8:40 AM, Federico Leva (Nemo)
nemow...@gmail.com wrote:
The only true precedent we have here is the public Collection server run by
On Jan 28, 2015 6:18 AM, Ilario Valdelli valde...@gmail.com wrote:
May someone help me?
I have read the short documentation of variables like:
$wgInternalServer
$wgServer
But I don't understand how combine them to get the Mediawiki accessible
internally with a local IP AND externally
Howdy all,
It was a pleasure chatting with you at this year's Developer Summit[1]
about how we might give SOA a shot in the arm by creating (and building
from) specifications.
The slides are available on the RESTBase project pages[2] and the session
notes are available on Etherpad[3].
I'm eager
I have to say: I think the presentations this year were better than ever, and
we definitely got a lot of important discussion done concerning the future of
SOA and MediaWiki.
--
Tyler Romeo
0x405D34A7C86B42DF
On January 28, 2015 at 09:16:00, Brion Vibber (bvib...@wikimedia.org) wrote:
Agreed
Hi.
There's been quite a bit of discussion about RESTBase lately. Is there a
request for comments on mediawiki.org about RESTBase? I looked at
https://www.mediawiki.org/wiki/Requests_for_comment and didn't see one.
From my limited understanding of what's being proposed, I'd personally be
a lot
MZMcBride,
the two RFCs that originally discussed RESTBase are:
- https://www.mediawiki.org/wiki/Requests_for_comment/Storage_service
- https://www.mediawiki.org/wiki/Requests_for_comment/Content_API
They were both originally discussed at the arch summit in January 2014.
We have since had two
Gabriel Wicke wrote:
the two RFCs that originally discussed RESTBase are:
- https://www.mediawiki.org/wiki/Requests_for_comment/Storage_service
- https://www.mediawiki.org/wiki/Requests_for_comment/Content_API
They were both originally discussed at the arch summit in January 2014.
We have since
On Wed, Jan 28, 2015 at 12:30 PM, James Douglas jdoug...@wikimedia.org
wrote:
Howdy all,
It was a pleasure chatting with you at this year's Developer Summit[1]
about how we might give SOA a shot in the arm by creating (and building
from) specifications.
The slides are available on the
JSON Schema is a recurring theme here which I'd like to encourage. I've
thought it was a promising idea and would like to explore it further, both
on the client and server side. If we can somehow keep data schema and API
specifications separate, it would be nice to develop both of these ideas in
MZMcBride wrote:
I updated the RESTBase page on mediawiki.org:
https://www.mediawiki.org/w/index.php?diff=1381405oldid=1283570.
I started a discussion on the talk page about the status of RESTBase. As
far as I can tell, it's simply proposed right now if both related RFCs
haven't been accepted,
On Tue, Jan 27, 2015 at 11:46 AM, Brion Vibber bvib...@wikimedia.org
wrote:
Another possibility is to shell out to nodejs-based services as an
alternative to running them as ongoing web services.
I have a hard time imagining a situation where you can install node and
everything else, but
Brad,
On Wed, Jan 28, 2015 at 10:08 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
If you're not on Debian or Ubuntu. Although yum install parsiod or
whatever might work on other Linux distros, what if you're on Windows or
something more exotic?
I think that we can help most users
Hi,
The report covering Wikimedia engineering activities in November 2014 is
now available:
https://www.mediawiki.org/wiki/Wikimedia_Engineering/Report/2014/November
--
Guillaume Paumier
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Wed, Jan 28, 2015 at 9:51 AM, Gabriel Wicke gwi...@wikimedia.org wrote:
I have a hard time imagining a situation where you can install node and
everything else, but would not just apt-get install parsoid
https://www.mediawiki.org/wiki/Parsoid/Setup or mathoid.
If you're not on Debian or
Gabriel and Wikimedia developers,
In what ways might you be anticipating developments with SemanticMediaWiki,
and in what ways not?
Scott
On Jan 28, 2015 9:52 AM, Gabriel Wicke gwi...@wikimedia.org wrote:
On Tue, Jan 27, 2015 at 11:46 AM, Brion Vibber bvib...@wikimedia.org
wrote:
Another
On Wed, Jan 28, 2015 at 9:51 AM, Gabriel Wicke gwi...@wikimedia.org wrote:
I believe we can make installing a fully-featured MediaWiki service system
as simple as copypasting 2-3 lines to a shell, or even executing a remote
installer script that runs those lines for you. Additionally, we can
Scott,
On Wed, Jan 28, 2015 at 9:55 AM, Scott MacLeod helia...@gmail.com wrote:
Gabriel and Wikimedia developers,
In what ways might you be anticipating developments with SemanticMediaWiki,
and in what ways not?
I definitely think that the mechanism needs to support the (optional)
Agreed - we had a great space and good support, the WiFi worked, power
strips everywhere, and there was always coffee. I can ask for little
more... ;)
Thanks also to our fellow attendees -- I had a lot of great conversations
and got a lot of data points to help set my work directions for the
On 28 January 2015 at 08:13, Daniel Friesen dan...@nadir-seen-fire.com wrote:
We could also try convincing the semi-decent shared hosts like Dreamhost
and Linode to run a service of their own for their customers.
Yes, reaching out to a shared hosting company or two is definitely
something to
While I agree that the most important cases should be *really* easy, I
worry about the implication that all other cases (including development of
core MediaWiki without using VMs) should necessarily be allowed to be
*really* complex.
If I'm no longer able to run MediaWiki from a XAMPP
On Wed, Jan 28, 2015 at 10:27 AM, Gabriel Wicke gwi...@wikimedia.org
wrote:
I think that we can help most users more if we identify the most important
use cases and focus on making those *really* easy. The installation in
exotic scenarios should still be supported, but I think it's okay if it
This is the Collaboration team update for 1/28.
We are in early stages of improving the user experience for enabling and
disabling Flow boards.
We enabled Flow on two pages on Portuguese Wikipedia, and are preparing
to finish enabling Flow for the Co-op
Gabriel,
Thanks ... yes, that's what I meant, and I wonder further if
SemanticMediaWiki will become very central five or ten years out (might it
even displace MediaWiki itself as we know it now)?
Scott
On Wed, Jan 28, 2015 at 10:06 AM, Gabriel Wicke gwi...@wikimedia.org
wrote:
Scott,
On
I think XAMPP-type setups are actually probably going to adapt well here --
since you have full system access you can install and run NodeJS-based
services as well. And an installer frontend can help manage setup so you
don't have to manually do much.
My biggest worry is the small installation on
since you have full system access you can install and run NodeJS-based
services as well. And an installer frontend can help manage setup so you
don't have to manually do much.
Well, that's the point from your perspective that might cause no
trouble because you know what to do but as a
28 matches
Mail list logo
