Wikitech-l April 2012

wikitech-l@lists.wikimedia.org

152 participants
192 discussions

Re: [Wikitech-l] GSOC-2012 proposal(Convention Extension)
by akshay chugh 04 Apr '12

04 Apr '12

Hi varnent, Before setting up this proposal , I have had some discussions with (^demon and saper) about the scope and need for such an extension. Not only they suggested me some features that they would want to see as part of this extension but they pointed out some issues as well that I would face while developing this extension . And seeing the links they provided for further clarity , I narrowed down the scope of this project keeping in mind the most important deliverables that need to be met. Well i didnt get any chance to talk to other wikimania folks about the web forms as such but they sure provided me some links showing the implementation of such features in wikimania . These are the implementation links :- - scholarship template(wikimania 2006) - http://wikimania2006.wikimedia.org/wiki/Scholarships/Application - scholarships code used for wikimania- https://github.com/saper/Scholarship<https://github.com/saper/Scholarships> Discussion with saper - https://www.mediawiki.org/wiki/User_talk:Chughakshay16/ConventionExtension

1 0

GSOC 2012 proposal - Ajax functions for editing, blocking, deleting and checking recent changes
by Marco 04 Apr '12

04 Apr '12

Following my proposal at http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/marco_in… I created a test wiki http://wikitest.freehosting.com/ <http://wikitest.freehosting.com/index.php?title=Main_Page> for you to take a look at the functionalities of the script I pretend to adapt, internationalize and use as base for my gsoc project (details at the proposal). It was a quick translation and much of it is still in Portuguese, but I think it's ok for a preview. Any considerations would be appreciated.

2 3

GSOC 2012 - Automatic Taxobox Usability and Feature Enhancements
by Bacon Prime 04 Apr '12

04 Apr '12

Hi, I'm writing a proposal to improve the usability of the automatic taxobox on Wikipedia; specifically, to create a GUI such that all future taxoboxes could be created with it, and most current taxoboxes could be edited without ever touching the templating syntax. In the optimal case, this would obviate the need for the extensive support needed (~10 archived talk pages over two years!) and might spark a conversion from the manual taxobox to the automatic (which is desirable to the micro-optimizing programmer in me) -- in the suboptimal case, such an improvement would still save many people many hours of work and even out the learning curve. As an ancillary benefit, the wizard-like processes described in the help pages could be easily converted into actual wizards, which would also cut down on errors (i.e. when steps are applied incorrectly, out of order or inappropriately). A quick blurb about myself: I'm 19, nearly into my third year of university and majoring in Computational Linguistics at Simon Fraser University. Also, I'd really, really like to be given the chance to contribute something positive to Wikipedia's community! Proposal Page <https://www.mediawiki.org/wiki/User:Baconprime/GSoC2012>

2 1

GSoC: Improving the interplay between Spark and SMW and the second one is Semantic Forms Rule
by riadh chtara 04 Apr '12

04 Apr '12

Hello! My name is Riadh Chtara.I'm Tunisian student.Two years ago I got an excellence scholarship from Tunisian Government to study Engineering In France. And today, I study in Ecole Centrale de Lyon which is one prestigious engineering school in France. I love web development . I know many programming language but one my favorite are JavaScript(with jQuery) and php. Last year, I made for example a web application called Grimdi Animator< http://www.grimdi.com/animator/> (which is a powerful and amazing tool that allows you to create cool javascript animation for you website without any required programming knowledge. It is very easy and fast. With Grimdi Animator you can also dynamically import data and manipulate XML. You can use Grimdi Animator to make animations,menus, galleries...) This application has today more than 8000 users in Chrome WebStore.Here is an example of what you could do with it .<http://www.grimdi.com/animator/example.html> It is a photo gallery loaded from this XML file <http://www.grimdi.com/animator/gallery.xml> I'm interested in two idea.The first one is Improving the interplay between Spark and SMW and the second one is Semantic Forms Rules. I discussed the first idea with Mr Jeroen De Dauw and Mr Denny Vrandecic, unfortunately none of them of them could be a full mentor( Mr Denny Vrandecic said he could be a co-mentor).So I am looking for a mentor for this idea.If any one want to volunteer please tell me. I'm also interested in Semantic Forms Rules.Like I said, I know JavaScript and jquery very well, the web application I made use basically javascript and jquery.I hve a few question to the mentor jquery (Mr Stephan Gambke) and I would like to ask him some questions. Yours sincerely Riadh

2 1

GSOC-2012 proposal(Convention Extension)
by akshay chugh 04 Apr '12

04 Apr '12

Hi everyone, I am an engineering student from Bits Pilani (India) currently in my 5th and final year.I seek to apply for GSOC this year under Mediawiki. So from the list of ideas given on the Mediawiki gsoc page, I wish to work on building a convention extension which would help convert any wiki into a conference like website such as Wikimania.After having discussions over IRC channels regarding the features that this extension should possess , and some feedback that I got from other developers I have written a proposal for this extension. I would really appreciate any feedback in this short period of time left, as it would help me in setting the right deliverables for this project. The proposal page - http://www.mediawiki.org/wiki/User:Chughakshay16/GSOCProposal%282012%29 The other details about this extension can be found on the following pages: 1. implementation details (+UI mockups) - http://www.mediawiki.org/wiki/User:Chughakshay16/ConventionExtension 2. database details - http://www.mediawiki.org/wiki/User:Chughakshay16/databasedetails The talk pages for the above can also be used for the feedback. Thanks, Akshay Chugh (irc - chughakshay16) On Tue, Apr 3, 2012 at 4:46 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: Time to redirect to https by default? (Ryan Lane) > 2. Re: Time to redirect to https by default? (Ryan Lane) > 3. Re: Time to redirect to https by default? (Ryan Lane) > 4. Re: Time to redirect to https by default? (MZMcBride) > 5. Re: Committing followups: please no --amend (Chad) > 6. Re: Time to redirect to https by default? (Platonides) > 7. Re: Time to redirect to https by default? (Ryan Lane) > 8. rsync on scap/sync reporting 'no space left on device' for a > lot of hosts (Arthur Richards) > 9. Re: Time to redirect to https by default? (Antoine Musso) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 3 Apr 2012 03:34:13 +0900 > From: Ryan Lane <rlane32(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Time to redirect to https by default? > Message-ID: > <CALKgCA0RLExmwpdJ18ATtPJ_b=h7JBc7AJ=Pj+2zgUYvnRPJ4w(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > On Mon, Apr 2, 2012 at 12:33 PM, Tim Starling <tstarling(a)wikimedia.org> > wrote: > > On 02/04/12 06:14, Ryan Lane wrote: > >> TL;DR: we have no plans for anonymous HTTPS by default, but will > >> eventually default to HTTPS for logged-in users. > >> > >> 1. It would require an ssl terminator on every frontend cache. The ssl > >> terminators eat memory, which is also what the frontend caches do. > > > > Once we enable it by default for logged-in users, we will care a lot > > more if someone tries to take it down with a DoS attack. Unless the > > redirection can be disabled without actually logging in, a DoS attack > > on the HTTPS frontend would prevent any authenticated activity. > > > > It suggests a need for a robust, overprovisioned service, with tools > > and procedures in place for identifying and blocking or throttling > > malicious traffic. > > > > Indeed. We're already pretty over provisioned. We have 4 servers per > datacenter, each of which is very bored. All they are doing is acting > as a transparent proxy, after ssl termination. We're using RC4 by > default (due to BEAST), and AES is also available (the processors we > are using have AES support). > > Ideally we'll be using STS for logged in users. This will mean it's > impossible to turn off the redirection for users that have already > logged in for whatever period of time we have STS headers set. We need > to consider blocking a DoS from the SSL proxies, the LVS servers, or > the routers. > > >> 3. Some countries may completely block HTTPS, but allow HTTP to our > >> sites so that they can track users. Is it better for us to provide > >> them content, or protect their privacy? > >> 4. It's still possible for governments to see that people are going to > >> wikimedia sites when using HTTPS, so it's still possible to oppress > >> people for trying to visit sites that are disallowed. > > > > It's also possible for governments to snoop on HTTPS communications, > > by using a private key from a trusted CA to perform a > > man-in-the-middle attack. Apparently the government of Iran has done > this. > > > > We really should publish our certificate fingerprints. An attack like > this can be detected. An end-user being attacked can see if the > certificate they are being handed is different from the one we > advertise. We could also provide a convergence notary service (or one > of the other things like convergence). > > > If we really want to protect the privacy of our users then we should > > shut down the regular website and serve our content only via a Tor > > hidden service ;) > > > > I agree that it's impossible to provide total protection of a user's > privacy. We could provide a number of services that would help users, > though. That said, I don't feel this should be on the top of our > priority list. > > - Ryan > > > > ------------------------------ > > Message: 2 > Date: Tue, 3 Apr 2012 03:58:41 +0900 > From: Ryan Lane <rlane32(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Time to redirect to https by default? > Message-ID: > <CALKgCA1ZXK8TBedG4cgdLeg-LsW7aN=ujf9O2V0QKL33DUYDVA(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > On Mon, Apr 2, 2012 at 4:20 PM, Petr Bena <benapetr(a)gmail.com> wrote: > > That's not what I wanted to say, I wanted to say "https may cause > > troubles with caching", In fact some caching servers have problems > > with https since the header is encrypted as well, so they usually just > > forward the encrypted traffic to server. I don't say it's impossible > > to cache this, but it's very complicated > > > > Using SSL by default means all transparent proxies inbetween aren't > hit at all, since they'd be a MITM. I don't necessarily see this as a > bad thing, as transparent proxies often break things. > > Browsers cache things differently from HTTPS sites, but otherwise > everything should work as normal. The SSL termination proxies > transparently proxy to our frontend caches after termination. Links > are sent as protocol-relative so that we don't split our cache, as > well. > > - Ryan > > > > ------------------------------ > > Message: 3 > Date: Tue, 3 Apr 2012 04:00:32 +0900 > From: Ryan Lane <rlane32(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Time to redirect to https by default? > Message-ID: > <CALKgCA18yzdDpiqS1RAViaz8O7nw68K2Bz0qZaCp1i0g1TxTNg(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > On Mon, Apr 2, 2012 at 6:34 PM, Tei <oscar.vives(a)gmail.com> wrote: > > Perhaps have a black list of countries that are know to break the > > privacy of communications, then make https default for logued users in > > these countries. > > > > This may help because: > > > > ?- It only affect a subgroup of users (the ones from these countries) > > ?- It only affect a subgroup of that subgroup, ?the logued users (not > all) > > ?- It create a blacklist of "bad countries" where citizens are under > > surveillance by the governement > > > > This perhaps is not feasible, if theres not easy way to detect the > > country based on the ip. > > > > I'd definitely not support doing something like this. This would > incredibly complicate things. > > - Ryan > > > > ------------------------------ > > Message: 4 > Date: Mon, 02 Apr 2012 16:26:57 -0400 > From: MZMcBride <z(a)mzmcbride.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Time to redirect to https by default? > Message-ID: <CB9F83D1.18E9B%z(a)mzmcbride.com> > Content-Type: text/plain; charset="ISO-8859-1" > > Ryan Lane wrote: > > On Mon, Apr 2, 2012 at 6:34 PM, Tei <oscar.vives(a)gmail.com> wrote: > >> Perhaps have a black list of countries that are know to break the > >> privacy of communications, then make https default for logued users in > >> these countries. > >> > >> This may help because: > >> > >> ?- It only affect a subgroup of users (the ones from these countries) > >> ?- It only affect a subgroup of that subgroup, ?the logued users (not > all) > >> ?- It create a blacklist of "bad countries" where citizens are under > >> surveillance by the governement > >> > >> This perhaps is not feasible, if theres not easy way to detect the > >> country based on the ip. > > > > I'd definitely not support doing something like this. This would > > incredibly complicate things. > > Someone came into #wikimedia-tech a few days ago and asked about something > similar to this. The idea was to use site-wide JavaScript to auto-redirect > users to https on one of the Chinese Wikipedias. I believe this was in > combination with geolocation functionality, but I'm not sure. > > Do you have any thoughts on individual wikis doing this, assuming there's > local community consensus? > > MZMcBride > > > > > > ------------------------------ > > Message: 5 > Date: Mon, 2 Apr 2012 17:05:03 -0400 > From: Chad <innocentkiller(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Committing followups: please no --amend > Message-ID: > <CADn73rPYs_H5tR0fQ0bvwAkjrJTnhA3Tk52FmLj1RbsekMp38A(a)mail.gmail.com > > > Content-Type: text/plain; charset=UTF-8 > > On Tue, Mar 27, 2012 at 6:06 AM, Tim Starling <tstarling(a)wikimedia.org> > wrote: > > On 27/03/12 19:49, Roan Kattouw wrote: > >> On Mon, Mar 26, 2012 at 9:50 PM, Tim Starling <tstarling(a)wikimedia.org> > wrote: > >>> For commits with lots of files, Gerrit's diff interface is too broken > >>> to be useful. It does not provide a compact overview of the change > >>> which is essential for effective review. > >>> > >>> Luckily, there are alternatives, specifically local git clients and > >>> gitweb. However, these don't work when git's change model is broken by > >>> the use of git commit --amend. > >>> > >> They do; it just wasn't obvious to you how to do it, but that doesn't > >> mean it can't be done. > >> > >> $ git fetch https://gerrit.wikimedia.org/r/p/analytics/udp-filters > >> refs/changes/22/3222/3 && git branch foo FETCH_HEAD > >> $ git fetch https://gerrit.wikimedia.org/r/p/analytics/udp-filters > >> refs/changes/22/3222/4 && git branch bar FETCH_HEAD > >> $ git diff foo..bar > >> > >> The two 'git fetch' commands (or at least the part before the &&) can > >> be taken from the change page in Gerrit. > > > > It doesn't work, I'm afraid. Because of the implicit rebase on push, > > usually subsequent changesets have a different parent. So when you > > diff between the two branches, you get all of the intervening commits > > which were merged to the master. > > > > Examples from today: > > > > https://gerrit.wikimedia.org/r/#change,3367 > > Patchsets 1 and 2 have different parents. > > > > https://gerrit.wikimedia.org/r/#change,3363 > > Patchsets 1, 2 and 3 have different parents. > > > > It's possible to get a diff between them, and I did, but it's tedious. > > I figure we should pick a workflow that doesn't waste the reviewer's > > time quite so much. > > > > The problem here is the implicit rebase. As long as the review > backlog isn't long and/or people aren't submitting conflicting > changes, rebasing amended changes against master creates > more harm than good. > > For amending commits, you should use `git review -R` so you > don't rebase the change (again) against master (see for example > [0], difference between patch 2 and 3). I've updated the docs[1], > but they are, briefly: > > git review -d 123 > (make changes) > git commit -a --amend > git review -R > > If you're not using git-review and have been using the alias, your > amended patchsets have not been creating this problem. > > -Chad > > [0] https://gerrit.wikimedia.org/r/#change,4020 > [1] https://www.mediawiki.org/wiki/Git/Workflow#Amend_your_change > > > > ------------------------------ > > Message: 6 > Date: Mon, 02 Apr 2012 23:31:28 +0200 > From: Platonides <Platonides(a)gmail.com> > To: wikitech-l(a)lists.wikimedia.org > Subject: Re: [Wikitech-l] Time to redirect to https by default? > Message-ID: <jld5hm$suh$1(a)dough.gmane.org> > Content-Type: text/plain; charset=ISO-8859-1 > > On 02/04/12 20:34, Ryan Lane wrote: > >> It's also possible for governments to snoop on HTTPS communications, > >> by using a private key from a trusted CA to perform a > >> man-in-the-middle attack. Apparently the government of Iran has done > this. > >> > > > > We really should publish our certificate fingerprints. An attack like > > this can be detected. An end-user being attacked can see if the > > certificate they are being handed is different from the one we > > advertise. We could also provide a convergence notary service (or one > > of the other things like convergence). > > Indeed. Detecting a potential MITM is useless if you can't determine if > it's real or not. For instance the switch from RapidSSL to DigiCert > certificate was quite suspicious. > > I don't know how to best publicise it, though. I suppose we would list > them somewhere like https://secure.wikimedia.org/servers.html but if > nobody knows it's there... > > > > > > ------------------------------ > > Message: 7 > Date: Tue, 3 Apr 2012 06:35:50 +0900 > From: Ryan Lane <rlane32(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Time to redirect to https by default? > Message-ID: > <CALKgCA0xW+wJu5LxzxQrJTaUfAf1ELPFjfucVeHaBF8CbaJjAw(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > > Indeed. Detecting a potential MITM is useless if you can't determine if > > it's real or not. For instance the switch from RapidSSL to DigiCert > > certificate was quite suspicious. > > > > I don't know how to best publicise it, though. I suppose we would list > > them somewhere like https://secure.wikimedia.org/servers.html but if > > nobody knows it's there... > > > > What's https://secure.wikimedia.org? > > - Ryan > > > > ------------------------------ > > Message: 8 > Date: Mon, 2 Apr 2012 16:19:20 -0700 > From: Arthur Richards <arichards(a)wikimedia.org> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] rsync on scap/sync reporting 'no space left on > device' for a lot of hosts > Message-ID: > <CAG5Yvh+pr-=KLLzj2sVucWX5a8PJG1mb=sd+0wc+FK+0KZpybw(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > I just ran scap and saw the following for a lot of hosts: > > srv285: rsync: write failed on > "/usr/local/apache/common-local/php-1.19/cache/l10n/l10n_cache-ab.cdb": No > space left on device (28) > > srv285: rsync error: error in file IO (code 11) at receiver.c(302) > [receiver=3.0.7] > > srv285: rsync: connection unexpectedly closed (2051 bytes received so far) > [generator] > > srv285: rsync error: error in rsync protocol data stream (code 12) at > io.c(601) [generator=3.0.7] > > > Also, on configchange: > > mw21: rsync: write failed on > "/apache/common-local/wmf-config/CommonSettings.php": No space left on > device (28) > > mw21: rsync error: error in file IO (code 11) at receiver.c(302) > [receiver=3.0.7] > > mw21: rsync: connection unexpectedly closed (37 bytes received so far) > [generator] > > mw21: rsync error: error in rsync protocol data stream (code 12) at > io.c(601) [generator=3.0.7] > > > Not sure if this is a problem and/or if others are aware/working on it, but > thought I'd mention it. > > -- > Arthur Richards > Software Engineer, Mobile > [[User:Awjrichards]] > IRC: awjr > +1-415-839-6885 x6687 > > > ------------------------------ > > Message: 9 > Date: Tue, 03 Apr 2012 01:22:10 +0200 > From: Antoine Musso <hashar+wmf(a)free.fr> > To: wikitech-l(a)lists.wikimedia.org > Subject: Re: [Wikitech-l] Time to redirect to https by default? > Message-ID: <jldcat$bto$1(a)dough.gmane.org> > Content-Type: text/plain; charset=ISO-8859-1 > > On April 2nd, 2012 at 23:35, Ryan Lane wrote: > > What's https://secure.wikimedia.org? > > Some old experiment. Nothing to see here :-) > > -- > Antoine "hashar" Musso > > > > > ------------------------------ > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > End of Wikitech-l Digest, Vol 105, Issue 10 > ******************************************* >

3 3

(no subject)
by Valentina Faussone 03 Apr '12

03 Apr '12

<a href="http://ryanwharvey.com/tommy.old/wp-content/plugins/extended-comment-option…"> http://ryanwharvey.com/tommy.old/wp-content/plugins/extended-comment-option…</a>

1 0

GSoC -- TranslateSvg: Bringing the translation revolution to Wikimedia Commons
by Harry Burt 03 Apr '12

03 Apr '12

Hey all, Now I have more of the details sorted out, I'd like to invite feedback on my Google Summer of Code proposed project, entitled *TranslateSvg: Bringing the translation revolution to Wikimedia Commons *.[1]. Obviously the deadline for submissions is rapidly closing in, but comments would still be very welcome, either before or after that deadline. To quote from my proposal: > TranslateSvg has the potential to revolutionise the ability of Wikimedia's > diverse groups of image maintainers to work together creating and improving > the same communal set of SVG (vector) images. At the moment, providing > alternative translations of SVG files typically requires "forking" the > image. This drastically increases the image's maintenance burden and > thereby discourages image improvement. Where such improvement does take > place, it is seldom shared between different language versions. > TranslateSvg would completely change this suboptimal workflow by removing > the need for the image to be forked; instead, translations (provided using > a streamlined special page) would be saved inside the image itself, in > accordance with the SVG 1.1 specification. The file, complete with these > embedded translations, could then be displayed in either the language of a > wiki, the user's preferred interface language, or any given arbitrary > language. If the SVG file were to be served directly, it would helpfully > display in the user's system language where such a translation was > available, aiding reuse possibilities. When I originally raised this idea > it received the support of several Wikimedia Commons users as well as WMF > developers. > Thanks! Harry (User:Jarry1250) [1] https://www.mediawiki.org/wiki/User:Jarry1250/GSoC_2012_application

5 4

Gerrit and Jenkins failures
by Antoine Musso 03 Apr '12

03 Apr '12

Hello, This European afternoon, I have done a serie of mistakes that made Jenkins to build a lot of pending Gerrit changes and submit a failure message. You can happily discard such message for now. During some time, we had a faulty test in master that makes any patch based on it to happily fail the MediaWiki-Test-API job. I have marked that test broken with change 4159 : https://gerrit.wikimedia.org/r/4159 Meanwhile, any change based on a commit before 633c454 will be marked by Jenkins as a failing. If you want to have a worthwile result, you will want to rebase your change on top of current master. New changes are not subject to the broken test above. Any failing build should mean that your patch as an issue :-] The Jenkins jobs currently only run the PHPUnit tests against a sqlite backend, more will be added soon (tm). -- Antoine "hashar" Musso

1 0

rsync on scap/sync reporting 'no space left on device' for a lot of hosts
by Arthur Richards 03 Apr '12

03 Apr '12

I just ran scap and saw the following for a lot of hosts: srv285: rsync: write failed on "/usr/local/apache/common-local/php-1.19/cache/l10n/l10n_cache-ab.cdb": No space left on device (28) srv285: rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7] srv285: rsync: connection unexpectedly closed (2051 bytes received so far) [generator] srv285: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7] Also, on configchange: mw21: rsync: write failed on "/apache/common-local/wmf-config/CommonSettings.php": No space left on device (28) mw21: rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7] mw21: rsync: connection unexpectedly closed (37 bytes received so far) [generator] mw21: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7] Not sure if this is a problem and/or if others are aware/working on it, but thought I'd mention it. -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

4 4

Automatic Taxobox
by Ashwin Ravichandran 03 Apr '12

03 Apr '12

Hey, I am very much interested in the idea of a Taxobox. I have an interesting method of generating it using a basic Python script. It would gather all the data using the basic Python application and would be able to store it in the taxonomy templates and we can display according with respect to the display templates. I will look into the merits and de - merits of the Generation of Automatic Taxobox and you will be receiving my proposal in the following week. I just need to know whether I am on the right track here? Regards, Ashwin -- Ashwin.S.Ravichandran

5 10

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l April 2012