Welcome back to Wikimedia Foundaion, Yuvi! :-)
-Sumana
-------- Original Message --------
Subject: Yuvi Panda returns to the Mobile Team
Date: Sun, 13 Jan 2013 17:33:38 -0800
From: Tomasz Finc <tfinc(a)wikimedia.org>
I'm very happy to announce that Yuvi Panda has rejoined the mobile
department as a software developer. He'll be working directly with Brion
Vibber within the newly created apps team. More info about the team will
go out in the next weeks.
For those of you that have not worked with Yuvi before he's been
responsible in some part for:
* Wiki Loves Monuments Android App
* Signpost Android App
* Wikipedia iOS/Android App
* Multiple language tools
* Numerous self run hackathons
* ... and so much more
For the next six months Yuvi will be working with us remotely from India
while he finishes up his degree. Upon completion of his studies and his
visa being accepted he will move and work with us full time in SF.
The team is very excited to be working with him again.
Pleases join me in re-welcoming Yuvi to the mobile team!
--tomasz
Hello everyone!
We have developed a Code Editor for Mediawiki CSS and JavaScript pages as part
of IIT Hackathon which was mentored by Yuvi Panda.
Basic description about the project along with snapshots can be found in this
page: https://github.com/psibi/wikiCodeEditor#readme
Any suggestions/improvements are welcome :)
Regards,
Sibi
The more I look at ContentHandler, the more it seems like a major new
feature for MW.
Are there any examples of this in use on Labs?
Is there more information on how to use and extend it for things like
WorkingWiki?
There is some talk of how the Gadgets extension may be changed by the
use of ContentHandler. Has any work been done on that yet? Do gadget
authors on-wiki need to know about these changes?
I like what I'm seeing in ContentHandler, but I'm a little afraid that
this will be like the introduction of ResourceLoader -- there is a lot
of promise here and new capability, but it sounds very disruptive to
current Gadget users (to give one example).
How can we begin to prepare third party users of MW for these changes now?
--
http://hexmode.com/
Language will always shift from day to day. It is the wind blowing
through our mouths. -- http://hexm.de/np
> From: "Mark A. Hershberger"<mah(a)everybody.org>
> To: Wikimedia developers<wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Release Notes and ContentHandler
> Message-ID:<50F16DC2.70007(a)everybody.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 01/12/2013 08:00 AM, Lee Worden wrote:
>> >Do you know that the WorkingWiki extension pretty much already does this?
> I was not aware of this extension.
>
> If I am understanding the example at
> http://lalashan.mcmaster.ca/theobio/projects/index.php/Greenhouse_paper
> correctly, it looks like it uses the <source-file> tag to make it so
> that parts of the page are handled by LaTeXML.
Yes, that's what's happening there. On other pages we store R source
code, makefiles, and whatever else people want to store.
> Just from looking overhttps://www.mediawiki.org/wiki/ContentHandler
> there seems to be a lot of cross over between what the WorkingWiki
> extension does and what ContentHandler enables. Having ContentHandler
> in core may mean that you can reduce the amount of code in the
> WorkingWiki extension.
Yes, I think ContentHandler does some of what WW does, and I'll be happy
to integrate with it. I don't think we'll want to abandon the
source-file tag, though, because on pages like
http://lalashan.mcmaster.ca/theobio/math/index.php/Nomogram and
http://lalashan.mcmaster.ca/theobio/worden/index.php/Selection_Gradients/Ma…,
it's good to be able to intertwine source code with the rest of the
page's wikitext.
Also, in a multi-file project, for instance a simple LaTeX project with
a .tex file and a .bib file, it's useful to put the files on a single
page so you can edit and preview them for a while before saving.
LW
From: Ori Livneh <ori(a)wikimedia.org>
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Subject: Re: [Wikitech-l] ContentHandler examples?
> After working with the API for a while I had a head-explodes moment when I realized
>that MediaWiki is now a generic framework for collaboratively fashioning
and editing
>content objects, and that it provides a generic implementation of a
creative workflow
>based on the concepts of versioning, diffing, etc. I think it's a
fucking amazing
>model for the web and I hope MediaWiki's code and community is nimble
enough to fully
>realize it.
I agree. Wikis can do lots more than create documents, and we've only
started down that road. ContentHandler is a step in this direction, and
our project is as well. I'd love to have conversations about all this.
I'm based in the Bay Area, by the way, even though our project is
based in Canada.
Lee Worden
As you may have guessed, I've been working on the release notes for
1.21. Please look over them and improve them if you can.
In the process, I came across the ContentHandler blurb. I don't recall
this being discussed on-list, but, from looking at the documentation for
it, it looks pretty awesome. I've used some of my editorial powers to
say, in the release notes:
Extension developers are expected to create additional types in the
future. These might support LaTeX or other forms of markup.
Is this correct? It sounds like a really big thing, if it is.
--
http://hexmode.com/
Language will always shift from day to day. It is the wind blowing
through our mouths. -- http://hexm.de/np
Hi Mark,
Do you know that the WorkingWiki extension pretty much already does this?
http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki
I haven't looked into the ContentHandler features in any detail, but I
don't imagine it'll be hard to handle source files stored on pages with
special content types along with the other ways of storing source files
that we already support. And yes, I'm sure I'll do it at some point.
Lee Worden
> Date: Fri, 11 Jan 2013 20:19:57 -0500
> From: "Mark A. Hershberger"<mah(a)everybody.org>
> To: Wikimedia developers<wikitech-l(a)lists.wikimedia.org>
> Subject: [Wikitech-l] Release Notes and ContentHandler
> Message-ID:<50F0BA3D.6060102(a)everybody.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> As you may have guessed, I've been working on the release notes for
> 1.21. Please look over them and improve them if you can.
>
> In the process, I came across the ContentHandler blurb. I don't recall
> this being discussed on-list, but, from looking at the documentation for
> it, it looks pretty awesome. I've used some of my editorial powers to
> say, in the release notes:
>
> Extension developers are expected to create additional types in the
> future. These might support LaTeX or other forms of markup.
>
> Is this correct? It sounds like a really big thing, if it is.
>
> -- http://hexmode.com/ Language will always shift from day to day. It is
> the wind blowing through our mouths. -- http://hexm.de/np
Hi,
Am 08.01.2013 17:59, schrieb Calvin W.F. Siu:
> As discussion with Manuel tonight about the whole wikimania system,
> he addressed that getting our domain (registration.wikimedia.hk and
> scholarship.wikimedia.hk) to use in every year's wikimania system
> because wikimania team in every year need to buy the SSL certificate for
> the systems, this action can cost effectively for every wikimania team to
> reduce the cost to buy SSL certificate and avoid the error from browser. Of
> course, we can claim the cost of buying certificate from WMCH/foundation.
> Is it possible to do that?
my suggestion was that we get a subdomain like "ssl.wikimania.org"
pointing to 195.114.98.120 (server of WMCH where the Wikimania Tools are
available hosted since 2010).
We could then implement the registration and scholarship portals on
* https://ssl.wikimania.org/registration
and
* https://ssl.wikimania.org/scholarship
We would need a certificate for ssl.wikimania.org, though, which needs
to be issued by the WMF as they are the owner of "wikimania.org".
Otherwise we would be able to register a new domain for this purpose
which is owned by WMCH, so we can do the same as above but buy the SSL
certificates by ourselves.
Someone from Wikitch-L who can help us with that?
Thanks,
Manuel
--
Wikimedia CH - Verein zur Förderung Freien Wissens
Lausanne, +41 (21) 34066-22 - www.wikimedia.ch