Hi folks,
does anyone have experiences with integrating a MediaWiki installation into
Small Business Server 2008 environment? The task is to install a wiki and
authenticate logged-in users automatically. Preferably with real name
instead of username.
Is there a manual for this somewhere?
I would like a company install for handbooks and howtos, but I have to
persuade our sysop.
--
Bináris
On Tue, Feb 5, 2013 at 2:43 PM, Gabriel Wicke <gwicke(a)wikimedia.org> wrote:
>> It would also mean that MediaWiki would be making uncontrolled API
>> calls *during the page parse*.
>
> To me it is not clear why a Wikidata web API would be less controlled
> than a Wikidata Lua API with direct access to the DB.
Oh. Earlier you were talking about general API access.
>> That would probably not work out too
>> well; I know on my local test wiki it's a pain just having to wait for
>> the ForeignAPIRepo calls for images.
>
> Slow operations will be slow, no matter how you call them. With a web
> API you at least get to parallelize and distribute the execution, so
> that you don't have to wait for a sequence of slow operations.
OTOH, with an API in Lua/PHP that accesses the database directly you
don't have to worry about establishing a TCP connection, sending
headers, waiting for a response, etc.
--
Brad Jorsch
Software Engineer
Wikimedia Foundation
Hi,
just wanted to inform you about new feature some of you might find useful.
In case you are looking for someone and you want to be notified when they
become online, you can use wm-bot for that (though it's in some wikimedia
channels only, but all general dev channels are already being occupied by
it), for example if I was waiting for hashar, I could just send a private
message
@notify hashar
to wm-bot and he send me a private message when hashar appear somewhere, or
talk and such. It works even on users who are already online but idle (so
it ping you when the user stop being idle)
I know similar features are available in some irc clients, but some of us
have to use webchat and similar clients sometimes, and using a bot this
feature is available to anyone.
Let me know in case you had any feedback for this
Hello,
I guess this can be answered by Tim or Victor, but I'm grateful for any pointers that can help me with a rather specific problem with Scribunto.
I'm currently working on the Wikidata project to include Lua functions for templates that access Wikidata entities.
I've toyed around a bit and extended LuaCommon.php with a getEntities function and a wikibase table to hold that function. Now I wonder if there are any plans for Lua extensions outside the mw.* namespace.
I've added a wikibase.lua file and a wikibase.* namespace in Lua. However, the way PHP and Lua play together and how Scribunto can be extended looks a bit like black magic (which is to be expected, given that Scribunto is far from finished).
Here are my questions:
1. Is there an easy way to add your own Lua functions (that call PHP Api functions) to Scribunto other than writing them into LuaCommon.php?
2. Is using your own namespace the way to go?
3. Are there some kind of examples how to wrap PHP functions into the Lua environment (using the frame etc)?
4. Is there any way to introspect or debug such wrapped functions?
Thanks for any suggestions!
Cheers,
Jens
--
Jens Ohlig
Software developer Wikidata project
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
+correct content-type this time ;) Note this has already been merged,
but still worth mention for visibility.
On 2/1/13 12:10 PM, Michael Dale wrote:
> We are about to merge in support for audio derivatives to Timed Media
> Handler (TMH). The big value here, I think is encoding to AAC or MP3
> and adding a /listen to this article/ feature to the mobile app.
> https://gerrit.wikimedia.org/r/#/c/39363/
>
> This can really help with improving accessibility of Wiktionary
> pronunciation media files as well.
>
> Also AAC / m4v ingestion, could make audio recordings a lot easier to
> import into the site, i.e a "record a reading of this article" mobile
> app feature #2 ;)
>
> There are already thousands of spoken articles, with some promotion
> their could probably be a lot be more:
> http://en.wikipedia.org/wiki/Category:Spoken_articles
>
> The software patent situation for mp3 is sad, considering how long the
> mp3 format has been around:
> http://www.tunequest.org/a-big-list-of-mp3-patents/20070226/
>
> I think AAC is a similar situation, encoder wise:
> http://en.wikipedia.org/wiki/Advanced_Audio_Coding#Licensing_and_patents
>
> But fundamentally Wikimedia is not "distributing" these encoders and
> there are no royalties for media distribution. Likewise we are not
> shipping decoders ( the decoders are in browser or the mobile OS )
>
> I don't know why Wikimedia's commitment to being accessible in royalty
> free formats, somehow also precludes making content accessible for
> folks on platforms that ~don't~ decode royalty free formats. But
> hopefully we can change that over time.
>
> Not sure if this is the right forum for this, but I hope we could come
> out of this thread with rough consensus to enable these formats to
> help increase the reach of audio works.
>
> peace,
> --michael
All,
The Fundraising and Mobile teams have been scheming about how we can start
to use the capabilities of the Varnish cache in our respective extensions.
Mobile already does use ESI, but this would be extensions to it.
As I know multiple other parties have been thinking along the same lines,
I've taken the liberty of creating an RfC [1] to discuss the subject /
develop requirements / wishlists / gotchas. Ideally this will serve as a
method to start retiring Squid, moving the site to Varnish, and then being
able to separate the site chrome from site content. *evil laugh*
[1]
https://www.mediawiki.org/wiki/Requests_for_comment/Caching_HTML_Fragments_…
--
~Matt Walker
Your system does not seem to support OGG audio format. Downloading this
file without ogg support may need a significant amount of space and
bandwith. Downloading article.wav ... 20%
Hi everyone,
I've setup a new repository called "sandbox." The purpose of this
repository is simple--it's meant to be a home for one-liners, quick
patches, and other things that don't have a proper home.
I've made pushing & review permissions super liberal on it (as in,
granted to all registered gerrit users), so anyone should be able
to do anything on it they want (direct pushing, make branches,
tag something, review, submit, etc).
As always, please let me know if you have any problems.
-Chad
Just wanted to note that volunteer Alex Monk (Krenair) now has +2 rights
in MediaWiki core and all extensions.
https://www.mediawiki.org/w/index.php?title=Git%2FGerrit_project_ownership&…
Alex joined our community as a developer about a year ago and has
consistently been helpful, especially in fixing bugs and reviewing
others' patches. Alex, thanks for your work.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation