Hi all,
I am an undergraduate student, currently pursuing my Integrated degree(
Msc. Chemistry and B.Tech Electronics& Instrumentation) from Bits
Pilani(India). I am looking forward to apply for GSOC this year under
Mediawiki. So from the list of projects/ideas stated on the Mediawiki gsoc
page I wish to work on the idea of developing a convention extension which
could be plugged into a wiki running the Mediawiki software.The current
requirement states to have an extension which would help convert any wiki
into a suitable website for conference ,such as Wikimania
Wikimania currently offers these many features :-
- a separate main page is dedicated for listing the conference details
- and features like registration, submission and talk (voting) are
present
- event management features
- speaker descriptions
-session details
-schedule info
-ticketing feature(payment gateway)
Wikimania is a site which is hand tailored for this purpose, so to get a
better understanding of how such conference management software works i
looked into a couple more available out there on the web such as
OpenConferenceWare(Ruby on Rails)[1] and wisconDB(perl)[2].
So after having looked into the above listed packages and Wikimania I have
come up with a list of tasks that should be performed by this extension :-
1. integration of new set of preferences in the preferences menu (
specially dedicated for the setting up of conference like features or even
a separate menu page just to avoid the clutter)
2. creation of template pages for registration, submission and voting just
like we already have in Wikimania but instead of creating them by hand this
extension would create them for the admin. (this feature would work once
the conference feature is enabled in the first step stated above)
3. creation of separate database tables which would solely handle this
added functionality(just like wisconDB [2])
4. creation of new templates(magic words) , that one could use in other
pages as well (just to show some relevant information regarding the
conference or event organized by the admin user)
-an example of such a template already exists on Wikimania [3]
Also had a discussion with ^demon on IRC regarding the approach that one
should take for building such an extension, he threw me some more ideas
that he had thought about this project and suggested me some more features
such as :-
5. creation of special badges
6. export feature for all the user information which could be available in
CSV or some other format
I just wanted to provide an introduction to this project , that?s why may
not have provided a detailed description of each point written above. So
further information can be looked under this page
https://meta.wikimedia.org/wiki/ConventionExtension<
https://meta.wikimedia.org/wiki/Books>
which i will be using for further development and plans on this project.
Any sort of feedback would be appreciated.
Extra Info :
[1] https://github.com/igal/openconferenceware
[2] https://code.google.com/p/wiscondb/
[3] https://wikimania2012.wikimedia.org/wiki/Main_Page
Thanks,
Akshay Chugh
On Fri, Feb 24, 2012 at 3:11 AM, <wikitech-l-request(a)lists.wikimedia.org>wrote:
> Send Wikitech-l mailing list submissions to
> wikitech-l(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> or, via email, send a message with subject or body 'help' to
> wikitech-l-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> wikitech-l-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikitech-l digest..."
>
>
> Today's Topics:
>
> 1. Re: Bump of minimum required PHP version to 5.3 for MediaWiki
> 1.20 (Antoine Musso)
> 2. Re: Bump of minimum required PHP version to 5.3 for MediaWiki
> 1.20 (Trevor Parscal)
> 3. Re: Bump of minimum required PHP version to 5.3 for MediaWiki
> 1.20 (Arthur Richards)
> 4. Re: Please Welcome Christian Aistleitner to Technical
> Operations (Ben Hartshorne)
> 5. Re: Bump of minimum required PHP version to 5.3 for MediaWiki
> 1.20 (Chad)
> 6. Re: Please Welcome Christian Aistleitner to Technical
> Operations (Manuel Schneider)
> 7. Re: Bump of minimum required PHP version to 5.3 for MediaWiki
> 1.20 (Patrick Reilly)
> 8. Re: Bump of minimum required PHP version to 5.3 for MediaWiki
> 1.20 (Chad)
> 9. Re: Caching of pages with time sensitive magic words (Platonides)
> 10. Re: Git + Gerrit is a toughy (Antoine Musso)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 23 Feb 2012 21:56:29 +0100
> From: Antoine Musso <hashar+wmf(a)free.fr>
> To: wikitech-l(a)lists.wikimedia.org
> Subject: Re: [Wikitech-l] Bump of minimum required PHP version to 5.3
> for MediaWiki 1.20
> Message-ID: <ji695p$dc8$1(a)dough.gmane.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Le 21/02/12 16:08, Domas Mituzas wrote:
> > If MediaWiki is better on newer PHP, we should use newer PHP.
>
> I have read that:
> > If MediaWiki is better on JS, we should use JS.
>
> Go figure.
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 23 Feb 2012 13:02:07 -0800
> From: Trevor Parscal <tparscal(a)wikimedia.org>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Bump of minimum required PHP version to 5.3
> for MediaWiki 1.20
> Message-ID:
> <CANKkVPpeT0CBmAgpxk+uzX3YXDyDnDhYR=Hhyqr3a=dEw4q77A(a)mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> Me too.
>
> - Trevor
>
> On Thu, Feb 23, 2012 at 12:56 PM, Antoine Musso <hashar+wmf(a)free.fr>
> wrote:
>
> > Le 21/02/12 16:08, Domas Mituzas wrote:
> >
> >> If MediaWiki is better on newer PHP, we should use newer PHP.
> >>
> >
> > I have read that:
> > > If MediaWiki is better on JS, we should use JS.
> >
> > Go figure.
> >
> >
> >
> >
> > ______________________________**_________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/**mailman/listinfo/wikitech-l<
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l>
> >
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 23 Feb 2012 13:05:37 -0800
> From: Arthur Richards <arichards(a)wikimedia.org>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Bump of minimum required PHP version to 5.3
> for MediaWiki 1.20
> Message-ID:
> <CAG5YvhLu-9Yzwf6d+y7dKNvpo0ay33A2iX2PM7K-X6jHbiG6bw(a)mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> >
> > The correct answer is "I'm sorry this is inconvenient, ask your hosting
> > provider or find a better one."
>
>
> I completely agree.
>
> Being able to use features like namespaces and late static binding would be
> a huge win. I'm definitely in favor of bumping the minimum PHP version to
> 5.3.x.
>
> --
> Arthur Richards
> Software Engineer, Mobile
> [[User:Awjrichards]]
> IRC: awjr
> +1-415-839-6885 x6687
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 23 Feb 2012 13:06:36 -0800
> From: Ben Hartshorne <bhartshorne(a)wikimedia.org>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Cc: wmfall(a)lists.wikimedia.org
> Subject: Re: [Wikitech-l] Please Welcome Christian Aistleitner to
> Technical Operations
> Message-ID:
> <CAF9NrhUO8-1TTjtU2d8G7aM+MEmOnh-3N+08-7iS6pdu=S5tJA(a)mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Thu, Feb 23, 2012 at 9:56 AM, Ct Woo <ctwoo(a)wikimedia.org> wrote:
>
> > Hi All,
> >
> > TechOps is happy to announce Christian Aistleitner has joined us as a
> > consultant/contractor.
> > Christian, who is based in Linz, Austria, will work towards hardening the
> > XML dump infrastructure.
> >
> > Though he just completed his PhD in 2011, he has been doing programming
> > since his teenage years., and started working in 2001. His career
> revolves
> > around free software integration, making software maintainable, and
> > tracking down and fixing the ever hiding bugs.
> >
> > He is a self-confessed code reading junkie, feeding on twisted,
>
>
> I look forward to seeing some event-driven python programing! ;)
>
> welcome.
>
> -ben
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 23 Feb 2012 16:11:25 -0500
> From: Chad <innocentkiller(a)gmail.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Bump of minimum required PHP version to 5.3
> for MediaWiki 1.20
> Message-ID:
> <CADn73rMOijzT-eYEkiNQHmRxm-0KAJK2EssvXYDtLBiod-qPnw(a)mail.gmail.com
> >
> Content-Type: text/plain; charset=UTF-8
>
> On Thu, Feb 23, 2012 at 4:05 PM, Arthur Richards
> <arichards(a)wikimedia.org> wrote:
> >>
> >> The correct answer is "I'm sorry this is inconvenient, ask your hosting
> >> provider or find a better one."
> >
> >
> > I completely agree.
> >
> > Being able to use features like namespaces and late static binding would
> be
> > a huge win. I'm definitely in favor of bumping the minimum PHP version to
> > 5.3.x.
> >
>
> Namespaces are moderately useful. They would've been much nicer
> if PHP hadn't decided on completely batshit notation for them.
>
> I'd also like to take a quick moment to put myself on the record as
> saying that I think LSB is a hack. It can has its uses, but the vast
> majority of examples I've seen in the wild so far are hacks to work
> around poor initial design decisions.
>
> Please use features intelligently, not just because they're the shiny
> new tool in the drawer.
>
> -Chad
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 23 Feb 2012 22:17:53 +0100
> From: Manuel Schneider <manuel.schneider(a)wikimedia.ch>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Cc: wmfall(a)lists.wikimedia.org, Wikimedia ?sterreich
> <vorstand(a)wikimedia.at>
> Subject: Re: [Wikitech-l] Please Welcome Christian Aistleitner to
> Technical Operations
> Message-ID: <4F46AD01.6040303(a)wikimedia.ch>
> Content-Type: text/plain; charset=iso-8859-1
>
> Bonan tagon,
>
> this time I may also chime in the "hello thread". Someone from Austria,
> great!
>
> Is Christian already familiar with his favourite chapter, Wikimedia
> ?sterreich? I'd be happy to hear more from him...
>
>
> /Manuel
> --
> Regards
> Manuel Schneider
>
> Wikimedia CH - Verein zur F?rderung Freien Wissens
> Wikimedia CH - Association for the advancement of free knowledge
> www.wikimedia.ch
>
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 23 Feb 2012 21:19:03 +0000
> From: Patrick Reilly <preilly(a)wikimedia.org>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Bump of minimum required PHP version to 5.3
> for MediaWiki 1.20
> Message-ID:
> <CAN211xnA-=Yg6K11DCDXRHLZHUmWwOTfY2gnQTz-+nG_vF9yxw(a)mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> The key features of PHP 5.3.0 include:
>
> Support for namespaces
> Late static binding
> Lambda Functions and Closures
>
> Syntax additions:
> NOWDOC,
> ternary short cut "?:"
> and jump label (limited goto), __callStatic()
> Under the hood performance improvements
> Optional garbage collection for cyclic references
>
> More consistent float rounding...
>
> Deprecation notices are now handled via E_DEPRECATED (part of E_ALL)
> instead of the E_STRICT error level
>
> Several enhancements to enable more flexiblity in php.ini (and ini parsing
> in general)
>
> On Feb 24, 2012 2:35 AM, "Arthur Richards" <arichards(a)wikimedia.org>
> wrote:
> >
> > >
> > > The correct answer is "I'm sorry this is inconvenient, ask your hosting
> > > provider or find a better one."
> >
> >
> > I completely agree.
> >
> > Being able to use features like namespaces and late static binding would
> be
> > a huge win. I'm definitely in favor of bumping the minimum PHP version to
> > 5.3.x.
> >
> > --
> > Arthur Richards
> > Software Engineer, Mobile
> > [[User:Awjrichards]]
> > IRC: awjr
> > +1-415-839-6885 x6687
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
> ------------------------------
>
> Message: 8
> Date: Thu, 23 Feb 2012 16:23:38 -0500
> From: Chad <innocentkiller(a)gmail.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Bump of minimum required PHP version to 5.3
> for MediaWiki 1.20
> Message-ID:
> <CADn73rOFOycx4sSmdDvOos70rEh8F07ipyaQpKCYMkSMeC4g6g(a)mail.gmail.com
> >
> Content-Type: text/plain; charset=UTF-8
>
> On Thu, Feb 23, 2012 at 4:19 PM, Patrick Reilly <preilly(a)wikimedia.org>
> wrote:
> > Syntax additions:
> > NOWDOC,
>
> This is actually very useful.
>
> > ternary short cut "?:"
>
> I don't think this syntax is all that intuitive. People are
> lazy though, so I guess it'll get used.
>
> > and jump label (limited goto), __callStatic()
>
> If anyone uses jump I'm going to whack them over the
> head with a revert stick. I see zero reason why this
> should ever be needed.
>
> > Under the hood performance improvements
> > Optional garbage collection for cyclic references
> >
>
> This is my favorite part of 5.3 <3
>
> -Chad
>
>
>
> ------------------------------
>
> Message: 9
> Date: Thu, 23 Feb 2012 22:38:12 +0100
> From: Platonides <Platonides(a)gmail.com>
> To: wikitech-l(a)lists.wikimedia.org
> Subject: Re: [Wikitech-l] Caching of pages with time sensitive magic
> words
> Message-ID: <ji6bav$vqg$1(a)dough.gmane.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 23/02/12 17:55, Sezgin Sucu wrote:
> > Hi I am curious as to how mediawiki sites are dealing with caching of
> > pages that contain time sensitive magic words that change from time to
> > time.
> > e.g. CURRENTTIME.
> >
> > Does mediawiki software send a different expiration time for such pages?
> > I have tested myself and haven't seen a difference.
> >
> > Thanks
>
> The parser cache expires much earlier in that case. Although we don't
> reduce it to lower than one hour due to the presence of such words.
>
>
> http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/includes/MagicWord.p…
>
>
>
>
>
>
> ------------------------------
>
> Message: 10
> Date: Thu, 23 Feb 2012 22:43:41 +0100
> From: Antoine Musso <hashar+wmf(a)free.fr>
> To: wikitech-l(a)lists.wikimedia.org
> Subject: Re: [Wikitech-l] Git + Gerrit is a toughy
> Message-ID: <ji6bua$4t3$1(a)dough.gmane.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Le 21/02/12 18:44, Andrew Otto a ?crit :
> > [~/Projects/wm/analytics/reportcard] (master)[29c6b47]$ git-review
> > You have more than one commit that you are about to submit.
> > The outstanding commits are:
> >
> > 29c6b47 (HEAD, master) observation.py - comments
> > 14a771a test commit for git branch push
> > 73dd606 Buncha mini changes + hackiness to parse a few things. This
> really needs more work
> > 2d37c13 pipeline/user_agent.py - adding comment that this file should
> not be used
> > 5892eb8 Adding loader.py - first hacky loader, just so we can get some
> data into mysql to work with.
> > e3fb30b Renaming the concept of variables to 'traits'. Allowing
> trait_sets to be specified so that we don't record HUGE amounts of data.
> > d0de74b base.py - adding schema in comments. Got lots of work to do to
> make this prettier
> > 328e55d Trying my darndest to clean things up here! I've cloned a new
> repo, and am checking in my non-committed (an non-approved?) changes into
> this new branch. Hopefully gerrit will be happier with me.
> >
> > This smells of me doing something really wrong.
>
> It seems to be a git-review safe guard to prevents someone from sending
> several commits. Each of them would make Gerrit generates several
> changes. To those wondering why one would have multiple commits, three
> use cases come to mind.
>
> I will give you the solution at the end of this post.
>
>
> 1) high frequency tradin^H^H^H^H^H^H committing
>
> Some people, me for example, do local commits very often, then squashes
> them before submitting the final patch. Git squashing means regrouping
> multiples commits in just one. Imagine I have made 4 commits locally,
> possibly using my mother tongue (french), in such case, using git-review
> will have me submitting a commit list like:
>
> abcde1 oh mygod
> d30909 variable fun
> f39004 je ne sais plus ce que c'est
> 439090 before lunch
>
> f39004 is some French meaning "I don't remember what was that" which
> does not describe the commit change (hint: using French will be
> perfectly valid once we start migrating from English).
>
> Anyway, git-review would generates 4 changes out of the 4 commits above.
> Not that helpful is it?
>
> Instead I would have wanted to regroup them and write a nice commit
> description. For example:
>
> 30490 (bug 1234) fix issue in feature foobar
>
>
> 2) newbie spamming gerrit
>
> This happen when you first play with Gerrit.
>
> In subversion world, whenever you submit a new patch (svn commit) it is
> going to be written down in the central repository. You will not be able
> to change it, hence any subsequent submission based on it are guaranteed
> it is not going to change.
>
> In git world, as I understand it, each commit as a parent commit. The
> reference is a sha1 based on the content of the commit. Whenever you
> change a commit, every children, grand-children .. will have their sha1
> recomputed.
>
> Enter in Gerrit world, when we send a commit in a queue, there is no
> guarantee that commit will end up in the reference repo. It might be
> amended or simply rejected. So your list of commit will be recomputed
> and all child / grand children will need to be resubmitted.
>
> Guess that? That will update of all those Gerrit changes, making mass
> email spam / jenkins rebuild etc.
>
>
> 3) mixing features
>
> You could well be mixing two different changes. Maybe you have made a
> commit to fix bug 1234 and two days later a fix for bug 6789. Those
> should really be two different changes.
>
>
>
> In conclusion, it is best to use a local branch for any bug / feature
> you might be working on actually. Branches are cheap in git, they are
> just a pointer. Once you are happy with your small branch, squash the
> commits and submit the end result. Less changes, less spam.
>
> If you really want to *spam* force git-review to do it with a yes card:
>
> $ git-review --yes
>
> But you probably want to use branch / squash instead.
>
>
> :-)
>
> --
> Antoine "hashar" Musso
> Migration to French is not scheduled yet
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
> End of Wikitech-l Digest, Vol 103, Issue 62
> *******************************************
>
Hi I am curious as to how mediawiki sites are dealing with caching of
pages that contain time sensitive magic words that change from time to
time.
e.g. CURRENTTIME.
Does mediawiki software send a different expiration time for such pages?
I have tested myself and haven't seen a difference.
Thanks
Cross posting to reach a larger audience.
We've gotten word from the Global Development group that a lot of our
partners are asking for an official Symbian S40 J2ME app for
Wikipedia. Before talking to any potential development houses I wanted
to reach out to both of these lists to see if anyone has a lead on any
open source developers who would want to contract for a project like
this and/or volunteer with us.
The feature set would be fairly basic including but not limited to
* Reading articles
* Bookmarks
* History
* Interwiki links
Now developing for J2ME is a beast unto itself as Derk-Jan
https://bugzilla.wikimedia.org/show_bug.cgi?id=32700#c1 points out but
the potential install base of these phones is still fairly large
making it a good strategic goal. We'd love to do this in PhoneGap but
its support starts at S60 and not S40.
I see two Symbian based apps here
http://en.wikipedia.org/wiki/Help:Mobile_access#Symbian_applications
but their both just for offline reading
Curious to hear peoples thought/experiences.
--tomasz
I have a case where I need to determine whether or not a request is coming
from a trusted proxy, so I'm passing the IP address wfIsTrustedProxy(). In
order to get the correct IP address to check, I need to pull the IP address
from the remote_addr header. WebRequest::getRawIP() already does this, but
it's a protected method, so I've gone ahead and duplicated the
functionality for myself, but that always makes me feel weird. Is there any
reason not to make it a public method instead? I imagine there are other
cases where this would also be useful.
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
There are currently three test failures in the MobileFrontend test suite -
all coming from MobileFormatterTest.php (see http://pastie.org/3439629).
Can whoever broke these or someone familiar with MobileFormatter either fix
the code or fix the tests?
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Hi all,
I am an undergraduate student, currently pursuing my Integrated degree(
Msc. Chemistry and B.Tech Electronics& Instrumentation) from Bits
Pilani(India). I am looking forward to apply for GSOC this year under
Mediawiki. So from the list of projects/ideas stated on the Mediawiki gsoc
page I wish to work on the idea of developing a convention extension which
could be plugged into a wiki running the Mediawiki software.The current
requirement states to have an extension which would help convert any wiki
into a suitable website for conference ,such as Wikimania
Wikimania currently offers these many features :-
- a separate main page is dedicated for listing the conference details
- and features like registration, submission and talk (voting) are
present
- event management features
- speaker descriptions
-session details
-schedule info
-ticketing feature(payment gateway)
Wikimania is a site which is hand tailored for this purpose, so to get a
better understanding of how such conference management software works i
looked into a couple more available out there on the web such as
OpenConferenceWare(Ruby on Rails)[1] and wisconDB(perl)[2].
So after having looked into the above listed packages and Wikimania I have
come up with a list of tasks that should be performed by this extension :-
1. integration of new set of preferences in the preferences menu (
specially dedicated for the setting up of conference like features or even
a separate menu page just to avoid the clutter)
2. creation of template pages for registration, submission and voting just
like we already have in Wikimania but instead of creating them by hand this
extension would create them for the admin. (this feature would work once
the conference feature is enabled in the first step stated above)
3. creation of separate database tables which would solely handle this
added functionality(just like wisconDB [2])
4. creation of new templates(magic words) , that one could use in other
pages as well (just to show some relevant information regarding the
conference or event organized by the admin user)
-an example of such a template already exists on Wikimania [3]
Also had a discussion with ^demon on IRC regarding the approach that one
should take for building such an extension, he threw me some more ideas
that he had thought about this project and suggested me some more features
such as :-
5. creation of special badges
6. export feature for all the user information which could be available in
CSV or some other format
I just wanted to provide an introduction to this project , that’s why may
not have provided a detailed description of each point written above. So
further information can be looked under this page
https://meta.wikimedia.org/wiki/ConventionExtension<https://meta.wikimedia.org/wiki/Books>
which i will be using for further development and plans on this project.
Any sort of feedback would be appreciated.
Extra Info :
[1] https://github.com/igal/openconferenceware
[2] https://code.google.com/p/wiscondb/
[3] https://wikimania2012.wikimedia.org/wiki/Main_Page
Thanks,
Akshay Chugh
On Thu, Feb 23, 2012 at 5:30 PM, <wikitech-l-request(a)lists.wikimedia.org>wrote:
> Send Wikitech-l mailing list submissions to
> wikitech-l(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> or, via email, send a message with subject or body 'help' to
> wikitech-l-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> wikitech-l-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikitech-l digest..."
>
>
> Today's Topics:
>
> 1. Re: 1.19 deploy to commons rescheduled for Wednesday, Feb 22
> 18:00-22:00 UTC (Rob Lanphier)
> 2. Re: Patch submitted: authentication on Wikipedia via
> user_name OR user_email (phoebe ayers)
> 3. Git, Gerrit, and You! or, Gerrit training available starting
> Monday 27 February (Sumana Harihareswara)
> 4. Reminder: MW Workshop: MediaWiki's ResourceLoader - 2/23/2012
> at 21:00 UTC on #wikimedia-dev (Gregory Varnum)
> 5. [ANN] MediaWiki Short URL Builder configuration tool
> (Daniel Friesen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 22 Feb 2012 15:46:03 -0800
> From: Rob Lanphier <robla(a)wikimedia.org>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] 1.19 deploy to commons rescheduled for
> Wednesday, Feb 22 18:00-22:00 UTC
> Message-ID:
> <CAPzpXh5VXEWhWUuj9EPAavs2uy22pjq3T6uTT1z0jRqsFp_4vA(a)mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi everyone,
>
> This deployment of 1.19 to commons finally happened about an hour or
> so ago. We're keeping an eye on possible issues. We haven't seen
> anything that would cause us to roll back, but we are seeing a few
> issues.
>
> Please report bugs in Bugzilla, or if you're feeling too lazy for
> that, at least drop a note on this talk page:
> https://meta.wikimedia.org/wiki/Talk:Wikimedia_maintenance_notice
>
> Thanks!
> Rob
>
> On Tue, Feb 21, 2012 at 8:49 PM, Rob Lanphier <robla(a)wikimedia.org> wrote:
> > Hi all,
> >
> > The 1.19 deploy to commons didn't go the way we hoped. ?We're planning
> > to try again tomorrow, after we have some time to debug some of the
> > problems we hit. ?Roan and Aaron are discussing some thumb generation
> > issues now, and there are also some Javascript issues that we'll need
> > to resolve tomorrow.
> >
> > A new deployment window is planned for Wednesday, Feb 22 18:00-22:00 UTC
> >
> > Rob
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 22 Feb 2012 17:01:54 -0800
> From: phoebe ayers <phoebe.wiki(a)gmail.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Patch submitted: authentication on Wikipedia
> via user_name OR user_email
> Message-ID:
> <CAAi3vqHNZYoLR7=bzfXc7xHYAuODA9GrCYGF3Oan0VPrVH_J=w(a)mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Wed, Feb 22, 2012 at 4:24 AM, Nicolas Brouard <brouard(a)ined.fr> wrote:
> >
>
> >
> > Thank you for your support. I just submitted a complete patch entitled
> "Can't authenticate using my mother language username (UNICODE) when I only
> have (a public) access to Wikipedia with an ASCII (english) keyboard" in
> about 20 languages on
> > https://bugzilla.wikimedia.org/show_bug.cgi?id=34590
> >
> > People supporting this idea, please for it.
>
> Cool!
>
> See also: https://bugzilla.wikimedia.org/show_bug.cgi?id=28085, a bug
> I submitted ages ago based on feedback I've gotten talking to users
> who only occasionally edited. The idea is that that remembering a
> username can be a barrier to casual editing (a few tries to remember a
> username that you don't use much and you might just give up) -- and
> being able to log in with an email address might help make things
> smoother.
>
> -- phoebe
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 22 Feb 2012 20:53:05 -0500
> From: Sumana Harihareswara <sumanah(a)wikimedia.org>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: [Wikitech-l] Git, Gerrit, and You! or, Gerrit training
> available starting Monday 27 February
> Message-ID: <4F459C01.1020704(a)wikimedia.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Before the March 3rd migration of MediaWiki core + WMF-deployed
> extensions to git, we want all MediaWiki developers to feel comfortable
> with Git, git-review, and Gerrit. So I'm scheduling the first in some
> one-hour interactive training sessions where you can learn the new
> MediaWiki development workflow.
>
> I can lead a couple of these on Monday and Tuesday, 27 and 28 February.
> If you're interested, please mark down times that you're available in
> this poll:
>
> http://www.doodle.com/9r5nb33u8cu4ap6y
>
> I intend on running these sessions via Google+ Hangout (you don't have
> to enable your webcam or audio) so you'll see my screen as I show you
> the steps. If you prefer not to use G+, then please let me know and I'll
> separately schedule some IRC trainings, or find another screensharing
> solution.
>
> While it's nice if you can come to a training, I aim to also make sure
> comprehensive documentation is at
>
> https://www.mediawiki.org/wiki/Git/Workflow
>
> by sometime this Friday. And then, after I've gotten the ball rolling,
> I hope other new experts will take the lead and start teaching.
>
> --
> Sumana Harihareswara
> Volunteer Development Coordinator
> Wikimedia Foundation
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 23 Feb 2012 03:02:07 -0500
> From: Gregory Varnum <gregory.varnum(a)gmail.com>
> To: wikitech-l(a)lists.wikimedia.org
> Subject: [Wikitech-l] Reminder: MW Workshop: MediaWiki's
> ResourceLoader - 2/23/2012 at 21:00 UTC on #wikimedia-dev
> Message-ID: <0F00371B-BFDA-4DE6-9CEE-1FDCBE9FA95B(a)gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
> "MediaWiki's ResourceLoader" will be held on 23 February, 2012 at 21:00
> UTC in IRC (#wikimedia-dev).
>
> This IRC workshop will be an opportunity to learn more about utilizing
> MediaWiki's ResourceLoader. Also an opportunity to ask questions about
> developing MediaWiki extensions.
>
> Everyone is invited to attend. Developers interested in serving as
> "extensions" or "ResourceLoader" experts are encouraged to signup as
> participants at:
> https://www.mediawiki.org/wiki/Project:WikiProject_Extensions/Workshops#Med…
>
> MediaWiki Workshops typically last one hour, and happen no more than twice
> a month to present trainings, hold discussions and collaborate on community
> or WikiProject Extensions projects. Facilitators host the session to
> introduce any presenters, determine the order of questions, and generally
> helps to keep things going. Time of day will vary in order to offer people
> in different parts of the world the opportunity to participate.
>
> More information:
> https://www.mediawiki.org/wiki/Project:WikiProject_Extensions/MediaWiki_Wor…
>
> -greg aka varnent
>
>
> -------
> Gregory Varnum
> Lead Administrator, WikiQueer
> Lead, Aequalitas Project
> @GregVarnum
> fb.com/GregVarnum
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 23 Feb 2012 03:48:10 -0800
> From: "Daniel Friesen" <lists(a)nadir-seen-fire.com>
> To: "wikitech-l(a)lists.wikimedia.org" <wikitech-l(a)lists.wikimedia.org>
> Subject: [Wikitech-l] [ANN] MediaWiki Short URL Builder configuration
> tool
> Message-ID: <op.v94q2kxdjuwloh(a)daniels-macbook-air.local>
> Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
>
> In my spare time at Redwerks I've been working on a Short URL
> configuration tool:
>
> http://shorturls.redwerks.org/
>
>
> Our Short URL manual pages have been VERY bad for quite awhile. Every last
> one of them has bad practice on them and I only managed to fix one of them.
>
> Considering how we have so many different manual pages simply because
> people have slightly different configuration requirements (eg: One for /w
> and /wiki/ another for / and /wiki/, another for /subpath/wiki, etc... One
> for .htaccess, another for Alias in Apache config, another for RewriteRule
> in Apache config, another for Nginx, etc...) rather than trying to fix I
> started writing a tool to build the configuration instead.
>
> The tool tries to auto-detect as much as possible (practically everything
> in fact). Everything from the type of server, the sapi (mod_php vs. ?),
> your scriptpath, etc... it even tries to jump ahead of you and guess what
> kind of article path you were intending to use. It even has an early
> feature to try and preemptively detect if you're likely to have root
> access or no root access (The idea is to detect what kind of host you're
> on using the reverse dns for the server you're on).
>
> The configuration generator actually isn't really a simple thing. There
> are a lot of conditionals involved in the tool. It can handle the special
> cases needed for root /$1 style urls. It knows how to add an extra rewrite
> when you use /w and /wiki and need / to redirect to your wiki. It uses
> Apache's %{DOCUMENT_ROOT} in RewriteRules but also lets you expand an
> absolute docroot when you use an Alias (you can't use %{DOCUMENT_ROOT}
> there). I've loaded the Nginx config full of deny rules and conditions
> that most people never bothered to properly configure (and yes, it can
> handle root urls, and even knows how to stop Nginx from executing php in
> uploaded files). Heck, this tool can actually handle TWN's wacky /w/i.php
> script path.
>
> The tool is definitely beta right now. I have Apache and Nginx support
> written. I'll probably want to have some discussion with Lighttpd and ISS
> users to fix the configuration some of them are using and add code to the
> tool to support those types of servers. There are still some conditions it
> might not handle just yet. For example I haven't written the code to
> handle root style urls in root Apache config files.
>
>
> Feel free to start using it when you setup a MediaWiki installation. I'd
> love to know when configuration doesn't work and what kind of tweaks I
> need to make to it. As well I'd like to see how the configurations handle
> different shared host setups, etc... I'd also like to see people on
> different hosts, both shared host users and VPS, Dedicated, etc... users
> running Apache jump in and make use of the yellow message's question on
> whether you're in a root or shared environment. If you use that specific
> feature it keeps track of reverse dns and the response, which I can use to
> try and preload rules to indicate what host's reverse dns patterns are for
> shared hosting users and what are for VPS servers and the like.
>
> --
> ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
>
>
>
> ------------------------------
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
> End of Wikitech-l Digest, Vol 103, Issue 60
> *******************************************
>
Greetings!
Building on the success of our inaugural session, MW.org's WikiProject Extensions is presenting our next MediaWiki Workshops for developers (volunteer and staff). "MediaWiki's ResourceLoader" will be held on 23 February, 2012 at 21:00 UTC in IRC (#wikimedia-dev).
This IRC workshop will be an opportunity to learn more about utilizing MediaWiki's ResourceLoader. Also an opportunity to ask questions about developing MediaWiki extensions.
Everyone is invited to attend. Developers interested in serving as "extensions" or "ResourceLoader" experts are encouraged to signup as participants at: https://www.mediawiki.org/wiki/Project:WikiProject_Extensions/Workshops#Med…
MediaWiki Workshops typically last one hour, and happen no more than twice a month to present trainings, hold discussions and collaborate on community or WikiProject Extensions projects. Facilitators host the session to introduce any presenters, determine the order of questions, and generally helps to keep things going. Time of day will vary in order to offer people in different parts of the world the opportunity to participate. Future topics will likely include MW.org documentation, API orientation and workshops similar to our inaugural chat to prepare for each MediaWiki release.
More information: https://www.mediawiki.org/wiki/Project:WikiProject_Extensions/MediaWiki_Wor…MediaWiki.org's WikiProject SysAdmins will also likely host similar MediaWiki Workshops to help third-party wiki system administrators. Stay tuned for more information, and chime in at: https://www.mediawiki.org/wiki/Project:WikiProject_SysAdmins/Ideas
I look forward to seeing folks on Thursday! Please feel free to forward this along to any interested folks.
-greg aka varnent
-------
Gregory Varnum
Lead Administrator, WikiQueer
Lead, Aequalitas Project
@GregVarnum
fb.com/GregVarnum
Hi all,
The 1.19 deploy to commons didn't go the way we hoped. We're planning
to try again tomorrow, after we have some time to debug some of the
problems we hit. Roan and Aaron are discussing some thumb generation
issues now, and there are also some Javascript issues that we'll need
to resolve tomorrow.
A new deployment window is planned for Wednesday, Feb 22 18:00-22:00 UTC
Rob
Hi,
Following recent events that unexpectatly broke many wiki bots monitoring
wikis in real-time via the irc recent changes feed (powered by routing
localized strings emitted by MediaWiki's rc2udp output to an IRC server),
The feed is mostly used by bots which have hardcoded most enviromental
variables, and had to do so since MediaWiki never offered a way to get this
parse information dynamically from an API (i.e. to the i18n messages used
and the meaning of the numbered replacement variables).
To avoid future breakages or mass migration while a replacement[1] is
already on the horizon, I think it's a good time as any to declare this
feature as "legacy" and therefor feature and bugfix froozen until
deprecated/superseeded by a more modern system[1].
Pretty much the only aspect that is still free to change (and always has) is
the content of the i18n messages (e.g. it's totally fine if translatewiki
commits a patch that changes [[MediaWiki:1movedto2/de]] from `verschob
„[[$1]]“ nach „[[$2]]“` to `verschieb [[$1]] auf [[$2]]` (which would
affect log comments of German content-langauge wikis such as in
irc.wikimedia.org/#de.wikipedia).. as long as the message is still stored at
message-key "1movedto2" and $1 is origin and $2 is target. Same goes for
messages like "MediaWiki:Revertpage",
"MediaWiki:Autosumm-blank" and "MediaWiki:Autosumm-replace". Which aren't
log messages, but are used the same way (edit summary is parsed and action
is determined).
I hope we can "soon" start focussing on the new system [1], start
elaborating on what the needs are, use cases, requirements and come up with
a design specification and implementation.
Related events: bug 34508[2], bug 30245[3].
-- Krinkle
[1] https://www.mediawiki.org/wiki/Requests_for_comment/Structured_data_push_no…
[2] https://bugzilla.wikimedia.org/show_bug.cgi?id=34508#c16
[3] https://bugzilla.wikimedia.org/show_bug.cgi?id=30245
[3] http://etherpad.wikimedia.org/IRCBot-Messages
Hello,
today I have a Sunday support question to the linker and hooks experts.
I know Hook:LinkEnd and use this almost successfully in an extension to
"tag" User and User_talk page with an additional attribute.
$wgHooks['LinkEnd'][] = 'wfWikiArticleFeedsAddSignatureMarker';
...
# https://www.mediawiki.org/wiki/Manual:Hooks/LinkEnd
function wfWikiArticleFeedsAddSignatureMarker( $skin, $title, $options,
$text, &$attribs, $ret ) {
if ( $title->getNamespace() == NS_USER) {
$attribs['userpage-link'] = 'true';
} elseif ( $title->getNamespace() == NS_USER_TALK ) {
$attribs['usertalkpage-link'] = 'true';
}
return true;
}
This works perfectly as long as the page exists, but fail to add the
attribute, if a "redlink" is created because the page does not exist.
I suppose that the getNamespace fails in this case,
Perhaps a patch in Linker.php is required to set Namespace already if
the page is non-existent.
Question:
=======
How can I add my attribute as shown also for such links which point to a
non-existing User or Usertalk page ?