Hi, as one of WMF developers who work on MobileFrontend[1], I'd love to
know how third parties use this extension. How does your caching
works? How are you detecting mobile devices? Do you have any problems
with running it? Finally, just tell us if you tried it at all:)
----
[1] https://www.mediawiki.org/wiki/Extension:MobileFrontend
--
Best regards,
Max Semenik ([[User:MaxSem]])
Greetings
My name is Yevheniy Vlasenko and I am a student of Master’s Program at
Chernihiv State Technological University(Ukraine), Department of Computer
Science. I would like to present an idea «Improvement of glossary tools»
(Semantic MediaWiki).
Currently there are two ways for handling glossaries in MediaWiki:
Lingo and Semantic Glossary. The idea aims to improve both extensions and
introduce new features. The most interesting innovations are: «support for
term multiple definition», context support», «integration of
FlaggedRevs/ApprovedRevs».
This project will significantly improve an efficiency of both
extensions. If will be useful for all wikis that use terms (science, art,
jurisprudence, etc.) as well as for third party users of MediaWiki.
Potentially it can be used in Wikidictionary and other Wikimedia projects.
The idea would be mentored by Stephan Gambke and Yury Katkov.
Full proposal can be found at my page
http://www.mediawiki.org/wiki/User:Zhenya.
Would be glad to receive any feedback either on idea or proposal.
---
Best Regards,
Yevheniy Vlasenko
Hi!
I am Siddha Ganju, a Computer Science and Engineering student from National
Institute of Technology, Hamirpur, Himachal Pradesh,India.
I have submitted a proposal[1] on jQuery.IME - the next big improvements.
All suggestions are welcome!
Thanks!
[1] https://www.mediawiki.org/wiki/User:SiddhaGanju/GSoC_2013_Application
--
Siddha Ganju
2nd Year Undergraduate Student
Computer Science and Engineering Department
National Institute of Technology, Hamirpur - 177005
E-mail Id : siddhaganju(a)gmail.com
At the risk of starting another huge bikeshed like [1] I feel like we need
some good guidance on just how in the heck we are required to license
extensions/images/source code files. With the help of Marktraceur we now
have
http://www.mediawiki.org/wiki/Manual:Coding_conventions#Source_File_Headers
which
is somewhat specific to PHP but could be generalized to JS, CSS, and SQL.
[1] http://lists.wikimedia.org/pipermail/wikitech-l/2013-March/067217.html
But I have some additional questions... breaking this up into bits; my
current thought matrix is that:
== Extensions ==
* Must have a LICENSE file in the root with the full text of the license
for the extension, and appended any additional licenses for
libraries/resources they've pulled in
** How do we specify what license goes to what included component?
== PHP Files ==
* For generic files, include a statement like
http://www.mediawiki.org/wiki/Manual:Coding_conventions#Source_File_Headers
* If it's the Extension.php file $wgExtensionCredits array should have the
following items
** author
** version
** url
** license?
** If we include additional libraries, so we add another entry to the
wgExtensionCredits array?
== JS/CSS Files ==
This gets a bit confusing because apparently we're supposed to have a
license in every bit of content pushed to the user; did we ever settle that
huge thread in any meaninful way? E.g. how to push minimized but licensed
files?
== Image Files ==
Really shouldn't be licensed under GPLv2; but right now they implicitly
are. Is there a way to explicitly identify image/binary content as being CC
licensed? Do we just add a line to the license file about this?
== And... go! ==
______
< moo. >
------
\ ^__^
\ ($$)\_______
(__)\ )\/\
U ||----w |
|| ||
~Matt Walker
Wikimedia Foundation
Fundraising Technology Team
Hi,
The deadline for submissions to the FOSS Outreach Program for Women is
*** 19:00pm UTC on May 1, 2013 ***
You must send your application to opw-list{}gnome.org before the
deadline. No exceptions!
https://live.gnome.org/OutreachProgramForWomen#Send_in_an_Application
You can keep improving your proposal in your project wiki page after the
deadline. It is ok if you haven't completed your mandatory contribution
yet. It is also ok if you don't have two co-mentors confirmed yet.
Also remember:
http://lists.wikimedia.org/pipermail/wikitech-l/2013-April/068842.html
If you hesitate, just apply. You will have more days to ask questions
and improve your proposal.
After applying you can add yourself to
https://www.mediawiki.org/wiki/Outreach_Program_for_Women#Candidates
What happens after submitting your OPW proposal:
* If you are also applying to GSoC then focus on GSoC. The first
evaluation will be done in that context following the GSoC process and
without any gender specific considerations.
* If your proposal is strictly for OPW then we will start evaluating it
and we might come back to you with questions.
The official announcement of accepted interns will be done by the OPW
program on May 27:
https://live.gnome.org/OutreachProgramForWomen/2013/JuneSeptember#Schedule
However, we might confirm some or all the Wikimedia interns by May 10.
It will partially depend on the GSoC selection process.
Good luck to everybody!
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi,
how can I figure out in a tag extension callback e.g.
function wfSampleRender( $input, array $args, Parser $parser, PPFrame $frame )
if the parser is inside a block mode or not?
With block mode I mean something like
:<mytag></mytag>
or
#<mytag></mytag>
or
<mytag></mytag>
but not
blindtext <mytag></mytag> more text
If there is an extension that uses ways to dermine the "block" a link
would help a lot.
Best regards
physikerwelt
On 18 April 2013 17:32, James Forrester <jforrester(a)wikimedia.org> wrote:
> TL;DR: VisualEditor will be deployed on 14 new Wikipedias next week as an
> opt-in alpha. Your assitance is requested to inform your wikis about this
> and help get the software translated.
This is now done (for de, nl, fr, it, ru, es, sv, pl, ja, ar, he, hi,
ko, and zh). Grateful for feedback, bug reports and suggestions of how
we can improve the VisualEditor for you.
Yours,
--
James D. Forrester
Product Manager, VisualEditor
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester