Re: [Wikitech-l] Replicating enwiki and dewiki for research purposes
Hi, You might also try the following mailing list: * XML Data Dumps mailing listhttps://lists.wikimedia.org/mailman/listinfo/xmldatadumps-l * Here is some info on importing XML dumps ( not sure what tools work well but probably the mailing list can help with that) http://meta.wikimedia.org/wiki/Data_dumps/Tools_for_importing Also, Ariel Glenn recently announced two new tools for importing dumps on the XML list: http://lists.wikimedia.org/pipermail/xmldatadumps-l/2013-February/000701.html Mariya On Tue, Mar 5, 2013 at 4:15 PM, Quim Gil q...@wikimedia.org wrote: On 03/05/2013 02:54 AM, Andreas Nüßlein wrote: Hi list, so I need to set up a local instance of the dewiki- and enwiki-DB with all revisions.. :-D Just in case: http://meta.wikimedia.org/**wiki/Mirroring_Wikimedia_**project_XML_dumpshttp://meta.wikimedia.org/wiki/Mirroring_Wikimedia_project_XML_dumps Also, you might want to ask / discuss at https://lists.wikimedia.org/**mailman/listinfo/offline-lhttps://lists.wikimedia.org/mailman/listinfo/offline-l Good luck with this interesting project! -- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/**User:Qgilhttp://www.mediawiki.org/wiki/User:Qgil __**_ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-lhttps://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Join mediawiki for GSOC 2013
Hi Malinthra, I added the XML Sitemaps project as some users expressed interest in being able to use http://www.mediawiki.org/wiki/Manual:GenerateSitemap.php without using the command line. This is not a very urgent project but might be interesting for some. I am no expert in extension development but I imagine it will involve making an extension which creates a Special page to run and schedule GenerateSitemaps.php ,something like what Extension:Maintenancehttps://www.mediawiki.org/wiki/Extension:Maintenance does for some maintainance scprits. Mariya On Mon, Feb 25, 2013 at 9:03 AM, Thomas PT thoma...@hotmail.fr wrote: Hi! For rendering of x3d files there is x3dom that is the official library of the web3D consortium. It provides two backends: one using webGL and a fallback using Flash. http://www.x3dom.org . This library looks pretty easy to integrate with MediaWiki. Tpt Brian Wolff bawo...@gmail.com a écrit : On 2013-02-24 5:21 PM, Brian Wolff bawo...@gmail.com wrote: On 2013-02-24 4:22 PM, Malintha Adikari malintha.adik...@hotmail.com wrote: Hi, I am final year computer engineering undergraduate from University of Peradeniya. I would like to join MediaWiki for GSOC 2013. I am interesting about these projects Write an extension to support XML Sitemaps without using command lineAdd support for x3d 3D files to MediaWiki Could you please provide more detail about these projects. Thanks regards, Malintha Adikari ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l If its helpful in deciding - x3d would probably be much more useful (particularly to Wikimedia, but even generally to third parties). However it would also be more difficult and also represents quite a bit more work. -bawolff Sorry I realized that wasnt actually answering your question. What type of information were you looking for? For the x3d one - you would probably be doing two main things. First you would need to write a filter that validates the file, and more importantly strips any dangerous elements ( im not familar with x3d format, but for example if user can also supply arbitrary macro scripts we would want to filter that out probably, etc). Second step would probably be to include some way of displaying the 3d models inline in articles (maybe some webgl js library exists that could be integrated in mediawiki, you would have to do some research there) Its possible a gsoc project could be scoped to be just the first step, or both steps depending on how much work that is. For background research you may want to check out extensions that do the same thing but for different formats, e.g. OggHandler (which isn't used anymore but a lot simpler than its replacement), and PagedTiffHandler. Emw has also started work on displaying 3d models of chemicals which sounds related (not sure how related it actually is) I hope that was helpful. Please don't hesitate to ask any questions. -bawolff ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Corporate needs are different (RE: How can we help Corporations use MW?)
Hi, There are so many extensions useful to the enterprise but probably also so many which are not useful at all or not maintained and if I wanted to start a corporate wiki right now I would probably be very lost what to look at and how people do things, so it seemed like a good idea to list the extensions that ARE actually used. Also, I guess one team solved a certain problem one way, while another solved it differenty, using a different extension or set of extensions, so writing this out might help everybody get new ideas/ avoid reinventing the wheel. But I guess I either asked on the wrong list or there is not much interest at all. Mariya On Thu, Feb 14, 2013 at 9:06 PM, Dmitriy Sintsov ques...@rambler.ru wrote: On 14.02.2013 21:14, vita...@yourcmc.ru wrote: I guess this would not directly solve any of the problems listed, but would it be helpful to bring back to life https://www.mediawiki.org/**wiki/Enterprise_hubhttps://www.mediawiki.org/wiki/Enterprise_hub? It was started by somebody an year or two ago but seems to have been abandoned at a draft stage. I am thinking if everybody adds some information about extensions/pages they find particularly useful in the enterprise world, it will help future users but also help current enterprise wikis exchange experience. Does this seem worthwhile? IMHO there are so much useful extensions that I think it can be a little much for that page. For example if I edited that article I would put almost all extensions from our distribution there... so I'm documenting them on http://wiki.4intra.net/**Category:Mediawiki4Intranet_**extensionshttp://wiki.4intra.net/Category:Mediawiki4Intranet_extensions:-) The question is, how much they are stable and secure. MediaWiki is high-quality software that should not be impaired by low-quality extension. Also, when extension is unmaintained, it's stability and security becomes questional as well. Also, I remember for major MW extensions scalability is the big problem. Efficient SQL queries, using APC / Memcached cache, not invalidating parser cache too often. For example my own Extension:QPoll is not well-scaling requiring some major rewrites. That applies to many of another extensions as well. Dmitriy __**_ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-lhttps://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Corporate needs are different (RE: How can we help Corporations use MW?)
Hi everyone, I guess this would not directly solve any of the problems listed, but would it be helpful to bring back to life https://www.mediawiki.org/wiki/Enterprise_hub ? It was started by somebody an year or two ago but seems to have been abandoned at a draft stage. I am thinking if everybody adds some information about extensions/pages they find particularly useful in the enterprise world, it will help future users but also help current enterprise wikis exchange experience. Does this seem worthwhile? Mariya On Wed, Feb 13, 2013 at 11:38 PM, Brian Wolff bawo...@gmail.com wrote: On 2013-02-13 11:27 AM, Marco Fleckinger marco.fleckin...@wikipedia.at wrote: On 02/12/2013 05:30 PM, Mark A. Hershberger wrote: On 02/11/2013 11:25 AM, Daniel Barrett wrote: Imagine if Wikipedia had a separate wiki for every city in the world. The same problem would result. I find it is easier to imagine what would happen if each language had a separate Wikipedia. We would end up with slightly different facts maintained on each wiki. Come on, this will be a similar discussion of what is the NPOV concerning the Falkland island on the English and the Spanish Wikipedia. IMHO each community should organize his wiki on it's own. Meta, Mediawiki, Commons and Wikidata already have interlanguage-communities and I think this doesn't work bad. Wikidata will be a bit different because it will integrate itself into the wikis' structures. Therefore I think that there will be discussion. So it's really great that the developers let the consumers the choice if they wanted to use wikidata or not. Cheers Marco I think you missed the point of the previous email. -bawolff ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Stable PHP API for MediaWiki ?
Hi everyone, I guess it is a little difficult for me to describe what I mean since I am just rephrasing what I've heard from others. I am still waiting for some more specific examples. However, I think most people are facing the kind of problems which Daniel has so well described in his post to the mailing list. Maybe this quotation will help clarify things. Mostly I want core developers to think about MediaWiki as framework with programming interfaces for extension developers. All the changes in those interfaces have to be calm, with slow deprecation. A role model for that is Python compiler. ( http://www.mediawiki.org/wiki/Talk:Third-party_MediaWiki_users_discussion#Features_Wish_List_22689 ) I understand from your comments that keeping things stable and preserving compatibiliy HAS been a priority for core developers at least since Daniel's email. Is this really the case? If this is the case, it makes me wonder why I hear some complaints about it. Is it maybe that documentation is not clear on what will be stable and can be used and what should not be used? Or is it a matter of educating extension developers how to find such information? On a brighter note, I heard that the LTS version 1.19 was the best thing that happened since sliced bread :) Mariya On Tue, Feb 12, 2013 at 10:03 AM, Antoine Musso hashar+...@free.fr wrote: Le 11/02/13 19:58, vita...@yourcmc.ru a écrit : 1) removal of global $action 2) removal of Xml::hidden() 3) broken Output::add() (had to migrate to resource loader) 4) various parser tag bugs 5) removal of MessageCache::addMessage() 6) removal of ts_makeSortable() (javascript) 7) brokage of WikiEditor adaptation 8) MediaWiki:common.js no more loading by default (security) 9) addHandler() javascript broken in IE8 Most of these were deprecations, am I correct? I guess so. Probably methods we simply removed instead of deprecating them like we are doing nowadays. -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Stable PHP API for MediaWiki ?
Yes, precisely. Is there an accepted way to call it, so I don't confuse people every time I talk about it ? Yuri, I am working on getting some concrete examples. Mariya On Mon, Feb 11, 2013 at 3:24 PM, Chad innocentkil...@gmail.com wrote: I believe Mariya is talking about the internal APIs available to extensions, (eg: User, Title, EditPage, so forth), not the public API. Yay, acronyms! -Chad On Mon, Feb 11, 2013 at 8:14 AM, Yuri Astrakhan yuriastrak...@gmail.com wrote: Mariya, Could you be more specific? What types of changes caused extensions to break? I might be mistaken but the vast majority of the API framework classes have been established over 5 years ago, with very few breaking changes since. Most changes were related to adding new functionality (new actions, new query submodules, new parameters), but that shouldn't have significantly affected extension development. I do plan to introduce a few breaking changes (majority of the extensions should not be affected) in 1.21, such as the introduction of versioning, further modularization to allow pageset reuse, etc. See http://www.mediawiki.org/wiki/Requests_for_comment/API_Future Please note that in a rare case some features might be purposefully removed due to the security or scalability issues. --Yuri On Mon, Feb 11, 2013 at 7:58 AM, Mariya Nedelcheva Miteva mariya.mit...@gmail.com wrote: Hi all, I have been talking to many third-party yas part of my WMF internship in the last few weeks and one the main concerns they express is the lack of stability in the PHP classes MediaWiki exposes from version to version. The frequent changes in what I would call the PHP-API makes extentions developement and maintenance much more difficult with compatibility from version to version becoming a problem. Solving the problem would probably result in the development of more extensions, easier maintenance, less hacks to core and more users upgrading to the latest MediaWiki version. I am sure WMF developers are facing similar issues especially with projects like WikiData going on. My question is: With the given technical heritage that MediaWiki carries, is it possible to have a (relatively) stable set of PHP classes defined, with a pledge not to change them in the next X releases or at least with some longer deprecation time? What would maintaining such a PHP-API entail? How difficult is it given the vast number of dependancies in MediaWiki code? Does it require restructuring a lot of the current core code? Do you think it should be a definite goal for WMF? Thank you. Mariya ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How can we help Corporations use MW? (Was Re: Comparisons to Confluence)
Hi Dan, We have http://www.mediawiki.org/wiki/Talk:Third-party_MediaWiki_users_discussion where we've been discussing some MW user issues, but the dicussion was not focused on corporate per se. We can use the same page or maybe set up a subpage if you think it will be easier. There is also https://www.mediawiki.org/wiki/Enterprise_hub. If anyone know of another appropriate place, please share. I would be glad to see such a space set up and discussion going on and would be happy to assist with that. Mariya On Thu, Feb 7, 2013 at 7:06 PM, Dan Andreescu dandree...@wikimedia.orgwrote: Sorry about that - Gmail reload glitch On 02/06/2013 10:00 PM, Tim Starling wrote: For corporate adoption, the main thing MediaWiki needs is not some particular feature. It needs to be supported. It needs an organisation with people who will care if corporate users are screwed over by a change. It needs community management, so that the features needed by corporate users will be discoverable and well-maintained, rather than developed privately, over and over. And it needs the smallest nudge of promotion, on top of what Wikipedia fans are doing for it. Say, a nice-looking website aimed at this user base. I was on the other side of this, albeit a while back. We had to decide between MediaWiki and Confluence to power Disney's ParentPedia (which has since been abandoned): http://www.theregister.co.uk/2007/03/13/disney_eisner/ http://family.go.com/parenting/ The main reasons we chose Confluence: * An easier to understand API. This seems to not be a problem any more: http://www.mediawiki.org/wiki/API:Client_code * Easier setup on Windows: http://www.mediawiki.org/wiki/Manual:Running_MediaWiki_on_Windows, possibly made easier now by Bitnami: http://bitnami.org/stack/mediawiki Do we have a place where people can talk through problems with corporate adoption? I suspect Tim's correct about the general case but that focusing on specifics would drive adoption. Dan ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
