Re: [Wikimedia-l] Recognition of Wikimedia Belgium as a Wikimedia chapter by the WMF Board
Congratulations Belgium. Douze points. On behalf of the Board of Wikimedia Nederland, best wishes! We're looking forward to cooperation and collaboration in the future. Wikimedia Nederland is prepared to support Wikimedia Belgium in the founding process and thereafter. However, you're out on your own to gather the required number of people in one place to sign the founding papers. Ad Huikeshoven Ad Huikeshoven Bestuurslid / Board member Wikimedia Nederland Internationaal / International Affairs Educatieprogramma / Education Program tel.(+31) (0)70 3608510 mob. (+31) (0)6 40293574 Steun vrije kennis! Kijk op wikimedia.nl http://www.wikimedia.nl/pagina/doneren-aan-wikimedia-nederland *Postadres*: * Bezoekadres:* Postbus 167Mariaplaats 3 3500 AD Utrecht Utrecht ABNAMRO NL33 ABNA 0497164833 - Kamer van Koophandel 17189036 2014-09-02 20:07 GMT+02:00 Romaine Wiki romaine.w...@gmail.com: Thanks all! The next step will be the actual founding. In two days we already have a meeting to talk about it. Anyone interested in the founding, you are welcome to sign up at https://be.wikimedia.org/wiki/Founding/Interested_people Romaine 2014-09-02 20:00 GMT+02:00 Nasir Khan nasir8...@gmail.com: Congrats to all who were involved in this success :D -- *Nasir Khan Saikat* www.nasirkhn.com On Tue, Sep 2, 2014 at 11:46 PM, Carlos M. Colina ma...@wikimedia.org.ve wrote: Dear all, It is an honour for me to announce that during Wikimania, the WMF resolved [1] to recognise Wikimedia Belgium as a Wikimedia chapter. The resolution was made public a few days ago. The first discussions towards the establishment of a Belgian chapter started many years ago, with the local community doing projects related to freedom of knowledge since then, like organisation of WLM Belgium Luxembourg in 2011, 2012 and 2013. Along with these and other activities, the idea of a chapter grew and evolved to the moment when, the decision was taken to start officially the chapter creation process. This process took longer than usual, due to many reasons, among those the change in the chapter approval process by the WMF Board last year. Nevertheless, after months of intensive discussion and interaction between all parties involved, a recommendation from the AffCom was sent to the WMF regarding Wikimedia Belgium. And here we are :-) Please welcome the newest member of the family of Wikimedia affiliates! Regards, Carlos 1: https://wikimediafoundation.org/wiki/Resolution: Recognition_of_Wikimedia_Belgium -- *Jülüjain wane mmakat* ein kapülain tü alijunakalirua jee wayuukanairua junain ekerolaa alümüin supüshuwayale etijaanaka. Ayatashi waya junain. Carlos M. Colina Vicepresidente, A.C. Wikimedia Venezuela | RIF J-40129321-2 | www.wikimedia.org.ve http://wikimedia.org.ve Chair, Wikimedia Foundation Affiliations Committee Phone: +972-52-4869915 Twitter: @maor_x ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe -- Ad Huikeshoven Bestuurslid / Board member Wikimedia Nederland Internationaal / International Affairs Educatieprogramma / Education Program tel.(+31) (0)70 3608510 mob. (+31) (0)6 40293574 Steun vrije kennis! Kijk op wikimedia.nl http://www.wikimedia.nl/pagina/doneren-aan-wikimedia-nederland *Postadres*: * Bezoekadres:* Postbus 167Mariaplaats 3 3500 AD Utrecht Utrecht ABNAMRO NL33 ABNA 0497164833 - Kamer van Koophandel 17189036 ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
Re: [Wikimedia-l] Let's fix templates
tl;dr: We've been collectively whining about templates for long enough. Who wants to help with fixing them? I want to help fix them. I hope we can, for the coming period, accomplish the following: * Catalog the problems with templates. Make a comprehensive list that enumerates the problems with templates we have now, categories the problems (right now I'm roughly thinking in style, wikitext parsing rules and generated HTML, creation and writing issues (let's hope there is little of this one left after Scribunto), and usability by editors). * Note which quirks that lead to technical difficulties are used in the wild as features rather than bugs. * Brain storm possible (partial) solutions. * Find candidates that have high bang-for-buck possible solutions without impeding future improvements much. * Refine those solutions so we know quite exactly what it will fix, what it won't fix, and what it would possibly break. * Define sane fallback procedures for when things break; this should mainly come from the editing communities, but could probably use some guidance of what is possible/easy/logical/feasible from a technical POV from the development community. * Fix templates. I'd like to add distribution as one of the pain points. I wanted to have the templates that are available on enwiki for another Mediawiki installation, but I couldn't get them to work. It seems like every template has a maze of dependencies, and when I resorted to exporting all of the templates from the Mediawiki site, the software consistently crashed before all templates were exported. I might have been doing it wrong, but I couldn't find any other options. Ideally, something like a package management system for templates, extensions, and skins would be a godsend. What do you all think? Should we make this happen? I'm no template expert, but I agree with a lot of what you've said based on the experiences I've had. I think we should discuss this somewhere that is less transient than this list. ln short, I'm down. ,Wil ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Recognition of Wikimedia Belgium as a Wikimedia chapter by the WMF Board
Well done everyone involved! I know how hard you have all worked to make this happen, I'm very pleased for you all. Congrats! Stevie On 3 September 2014 07:41, Ad Huikeshoven a...@wikimedia.nl wrote: Congratulations Belgium. Douze points. On behalf of the Board of Wikimedia Nederland, best wishes! We're looking forward to cooperation and collaboration in the future. Wikimedia Nederland is prepared to support Wikimedia Belgium in the founding process and thereafter. However, you're out on your own to gather the required number of people in one place to sign the founding papers. Ad Huikeshoven Ad Huikeshoven Bestuurslid / Board member Wikimedia Nederland Internationaal / International Affairs Educatieprogramma / Education Program tel.(+31) (0)70 3608510 mob. (+31) (0)6 40293574 Steun vrije kennis! Kijk op wikimedia.nl http://www.wikimedia.nl/pagina/doneren-aan-wikimedia-nederland *Postadres*: * Bezoekadres:* Postbus 167Mariaplaats 3 3500 AD Utrecht Utrecht ABNAMRO NL33 ABNA 0497164833 - Kamer van Koophandel 17189036 2014-09-02 20:07 GMT+02:00 Romaine Wiki romaine.w...@gmail.com: Thanks all! The next step will be the actual founding. In two days we already have a meeting to talk about it. Anyone interested in the founding, you are welcome to sign up at https://be.wikimedia.org/wiki/Founding/Interested_people Romaine 2014-09-02 20:00 GMT+02:00 Nasir Khan nasir8...@gmail.com: Congrats to all who were involved in this success :D -- *Nasir Khan Saikat* www.nasirkhn.com On Tue, Sep 2, 2014 at 11:46 PM, Carlos M. Colina ma...@wikimedia.org.ve wrote: Dear all, It is an honour for me to announce that during Wikimania, the WMF resolved [1] to recognise Wikimedia Belgium as a Wikimedia chapter. The resolution was made public a few days ago. The first discussions towards the establishment of a Belgian chapter started many years ago, with the local community doing projects related to freedom of knowledge since then, like organisation of WLM Belgium Luxembourg in 2011, 2012 and 2013. Along with these and other activities, the idea of a chapter grew and evolved to the moment when, the decision was taken to start officially the chapter creation process. This process took longer than usual, due to many reasons, among those the change in the chapter approval process by the WMF Board last year. Nevertheless, after months of intensive discussion and interaction between all parties involved, a recommendation from the AffCom was sent to the WMF regarding Wikimedia Belgium. And here we are :-) Please welcome the newest member of the family of Wikimedia affiliates! Regards, Carlos 1: https://wikimediafoundation.org/wiki/Resolution: Recognition_of_Wikimedia_Belgium -- *Jülüjain wane mmakat* ein kapülain tü alijunakalirua jee wayuukanairua junain ekerolaa alümüin supüshuwayale etijaanaka. Ayatashi waya junain. Carlos M. Colina Vicepresidente, A.C. Wikimedia Venezuela | RIF J-40129321-2 | www.wikimedia.org.ve http://wikimedia.org.ve Chair, Wikimedia Foundation Affiliations Committee Phone: +972-52-4869915 Twitter: @maor_x ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe -- Ad Huikeshoven Bestuurslid / Board member Wikimedia Nederland Internationaal / International Affairs Educatieprogramma / Education Program tel.(+31) (0)70 3608510 mob. (+31) (0)6 40293574 Steun vrije kennis! Kijk op wikimedia.nl http://www.wikimedia.nl/pagina/doneren-aan-wikimedia-nederland *Postadres*: * Bezoekadres:* Postbus 167Mariaplaats 3 3500 AD Utrecht
Re: [Wikimedia-l] Let's fix templates
On Sep 3, 2014 4:46 AM, MZMcBride z...@mzmcbride.com wrote: Hi Martijn. Thanks for starting this thread. Martijn Hoekstra [roughly] wrote: * Catalog the problems with [dev issue]. Make a comprehensive list that enumerates the problems with [dev issue] we have now, categorise the problems (right now I'm roughly thinking in style, wikitext parsing rules and generated HTML, creation and writing issues (let's hope there is little of this one left after Scribunto), and usability by editors). * Note which quirks that lead to technical difficulties are used in the wild as features rather than bugs. * Brainstorm possible (partial) solutions. * Find candidates that have high bang-for-buck possible solutions without impeding future improvements much. * Refine those solutions so we know quite exactly what it will fix, what it won't fix, and what it would possibly break. * Define sane fallback procedures for when things break; this should mainly come from the editing communities, but could probably use some guidance of what is possible/easy/logical/feasible from a technical POV from the development community. * Fix [dev issue]. Yeah there are a couple of dev issues above. This email is purposefully sent to the broadest list I could find, because it are broad issues, and the dev community is part of the audience of this list. One of the issues (but not the only issue) is that if templates were less troublesome, it would be easier for dev to make great products. It would be easy to say that is their problem, but since everyone benefits from the software being better, helping dev by reducing template madness helps all of us. I don't disagree with what you're saying, but I don't think it's really specific to templates. We should roughly be following these steps for most development issues, no? There won't be a one size fits all approach to templates. In the recent discussions/debacles about technical and stylistic advances, a recurring theme is that the use of some templates causes major headaches, and a commonly heard complaint from the developers and designers is that their products exhibit problems and shortcoming because of that. Anecdotal evidence I've lately encountered includes: * The mobile skin obfuscates talk page access because the templates commonly found on talk pages makes them render horribly. Talk page templates are dumb. We should integrate their functionality into a MediaWiki extension. We currently have people going around assessing articles on talk pages and adding talk page banners using iterator tools such as AutoWikiBrowser. These are fine people and they're doing fine work, but the mechanism by which they're doing it is sorely lacking. We can easily store and manage page properties such as an article's quality assessment or which WikiProjects are interested in the article in a structured database. We already track (and can query!) by many page properties. Let's leverage the software platform we've built. Regardless of whether we use a built-in tool or we continue to use templates, you're talking about trashing templates because of CSS issues. That doesn't make much sense to me. Templates make life vastly easier. We can likely update most talk page templates on large wikis with a single edit to a meta-template or perhaps even just a CSS edit. That's great! * The mobile skin special-cases some templates (notably issue templates and infoboxes) because they would render horribly. Second mention of the mobile skin. Perhaps it's the mobile skin that needs work. I think the mobile experience is horribly and painfully deficient and flawed. Any help you can provide in trying to make it better would surely be welcome. I've tried a few times and it only results in sadness. There are a couple of interlocking problems here. Templates are often inline styled for the desktop. Writing and maintaining inline styles is a bit cumbersome, writing good styles that work for desktop and mobile isn't all that easy, and those two amplify each other. The mobile skin does the wrong thing (stripping inline styles) because the templates have inline styles that aren't suitable for mobile, and they have to do something to get an acceptable end result. The templates don't have suitable styles for mobile because it's so hard to inline style something. If the styling of the templates becomes less cumbersome, we can start making them better suited for mobile, the mobile skin can stop special casing them, and everyone will be happier. * Media-viewer has a tough time doing to correct thing with attribution and license information because parsing template-madness is hard. Structured data, a.k.a. Wikidata, as Brad noted. * VE development has spent a large amount of time around templates, and it's still one of its weakest suits. Template substitution is still a problem, as well as templates that produce wikitext that in itself
Re: [Wikimedia-l] Let's fix templates
On Wed, Sep 3, 2014 at 10:04 AM, Wil Sinclair w...@wllm.com wrote: tl;dr: We've been collectively whining about templates for long enough. Who wants to help with fixing them? I want to help fix them. Great to hear. Getting my ass in to gear is one of my greatest weaknesses, and from what I know from you you're really good at that. :) I hope we can, for the coming period, accomplish the following: * Catalog the problems with templates. Make a comprehensive list that enumerates the problems with templates we have now, categories the problems (right now I'm roughly thinking in style, wikitext parsing rules and generated HTML, creation and writing issues (let's hope there is little of this one left after Scribunto), and usability by editors). * Note which quirks that lead to technical difficulties are used in the wild as features rather than bugs. * Brain storm possible (partial) solutions. * Find candidates that have high bang-for-buck possible solutions without impeding future improvements much. * Refine those solutions so we know quite exactly what it will fix, what it won't fix, and what it would possibly break. * Define sane fallback procedures for when things break; this should mainly come from the editing communities, but could probably use some guidance of what is possible/easy/logical/feasible from a technical POV from the development community. * Fix templates. I'd like to add distribution as one of the pain points. I wanted to have the templates that are available on enwiki for another Mediawiki installation, but I couldn't get them to work. It seems like every template has a maze of dependencies, and when I resorted to exporting all of the templates from the Mediawiki site, the software consistently crashed before all templates were exported. I might have been doing it wrong, but I couldn't find any other options. Ideally, something like a package management system for templates, extensions, and skins would be a godsend. A Mediawiki core templates pack sounds like a good idea - as would making template and module interdependencies explicit to somewhat avoid the Great Tangle. aside - wikitech-l as well as #mediawiki freenode are in my experience happy to help with individual setup woes, which could help you with the acute import issues /aside What do you all think? Should we make this happen? I'm no template expert, but I agree with a lot of what you've said based on the experiences I've had. I think we should discuss this somewhere that is less transient than this list. Stop rushing me all y'all! ;) ln short, I'm down. ,Wil ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Let's fix templates
Exsqueeze the ignorance. I'm still a n00b. Martijn, where should we set this discussion up? It's clear that there are several people who are interested in talking templates. I'm getting my hands dirty with them on another project I'm working on. I don't mean to rush you; just tell me what to set up for this discussion and where, and I'll make sure it gets done. ,Wil On Wed, Sep 3, 2014 at 1:48 AM, Martijn Hoekstra martijnhoeks...@gmail.com wrote: On Wed, Sep 3, 2014 at 10:04 AM, Wil Sinclair w...@wllm.com wrote: tl;dr: We've been collectively whining about templates for long enough. Who wants to help with fixing them? I want to help fix them. Great to hear. Getting my ass in to gear is one of my greatest weaknesses, and from what I know from you you're really good at that. :) I hope we can, for the coming period, accomplish the following: * Catalog the problems with templates. Make a comprehensive list that enumerates the problems with templates we have now, categories the problems (right now I'm roughly thinking in style, wikitext parsing rules and generated HTML, creation and writing issues (let's hope there is little of this one left after Scribunto), and usability by editors). * Note which quirks that lead to technical difficulties are used in the wild as features rather than bugs. * Brain storm possible (partial) solutions. * Find candidates that have high bang-for-buck possible solutions without impeding future improvements much. * Refine those solutions so we know quite exactly what it will fix, what it won't fix, and what it would possibly break. * Define sane fallback procedures for when things break; this should mainly come from the editing communities, but could probably use some guidance of what is possible/easy/logical/feasible from a technical POV from the development community. * Fix templates. I'd like to add distribution as one of the pain points. I wanted to have the templates that are available on enwiki for another Mediawiki installation, but I couldn't get them to work. It seems like every template has a maze of dependencies, and when I resorted to exporting all of the templates from the Mediawiki site, the software consistently crashed before all templates were exported. I might have been doing it wrong, but I couldn't find any other options. Ideally, something like a package management system for templates, extensions, and skins would be a godsend. A Mediawiki core templates pack sounds like a good idea - as would making template and module interdependencies explicit to somewhat avoid the Great Tangle. aside - wikitech-l as well as #mediawiki freenode are in my experience happy to help with individual setup woes, which could help you with the acute import issues /aside What do you all think? Should we make this happen? I'm no template expert, but I agree with a lot of what you've said based on the experiences I've had. I think we should discuss this somewhere that is less transient than this list. Stop rushing me all y'all! ;) ln short, I'm down. ,Wil ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Recognition of Wikimedia Belgium as a Wikimedia chapter by the WMF Board
Congratulations! On Tuesday, September 2, 2014, Romaine Wiki romaine.w...@gmail.com wrote: Thanks all! Looking forward to seeing WMBE coordinating an European effort to have the best Wikimedia participation at http://fosdem.org ever. (Tech-minded wikimedians, take note: Brussels, 31 January 1 February 2015) -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Let's fix templates
I'm thinking a page on Meta to start with. I'll get round to it when I get home from work tonight CET. On Wed, Sep 3, 2014 at 11:33 AM, Wil Sinclair w...@wllm.com wrote: Exsqueeze the ignorance. I'm still a n00b. Martijn, where should we set this discussion up? It's clear that there are several people who are interested in talking templates. I'm getting my hands dirty with them on another project I'm working on. I don't mean to rush you; just tell me what to set up for this discussion and where, and I'll make sure it gets done. ,Wil On Wed, Sep 3, 2014 at 1:48 AM, Martijn Hoekstra martijnhoeks...@gmail.com wrote: On Wed, Sep 3, 2014 at 10:04 AM, Wil Sinclair w...@wllm.com wrote: tl;dr: We've been collectively whining about templates for long enough. Who wants to help with fixing them? I want to help fix them. Great to hear. Getting my ass in to gear is one of my greatest weaknesses, and from what I know from you you're really good at that. :) I hope we can, for the coming period, accomplish the following: * Catalog the problems with templates. Make a comprehensive list that enumerates the problems with templates we have now, categories the problems (right now I'm roughly thinking in style, wikitext parsing rules and generated HTML, creation and writing issues (let's hope there is little of this one left after Scribunto), and usability by editors). * Note which quirks that lead to technical difficulties are used in the wild as features rather than bugs. * Brain storm possible (partial) solutions. * Find candidates that have high bang-for-buck possible solutions without impeding future improvements much. * Refine those solutions so we know quite exactly what it will fix, what it won't fix, and what it would possibly break. * Define sane fallback procedures for when things break; this should mainly come from the editing communities, but could probably use some guidance of what is possible/easy/logical/feasible from a technical POV from the development community. * Fix templates. I'd like to add distribution as one of the pain points. I wanted to have the templates that are available on enwiki for another Mediawiki installation, but I couldn't get them to work. It seems like every template has a maze of dependencies, and when I resorted to exporting all of the templates from the Mediawiki site, the software consistently crashed before all templates were exported. I might have been doing it wrong, but I couldn't find any other options. Ideally, something like a package management system for templates, extensions, and skins would be a godsend. A Mediawiki core templates pack sounds like a good idea - as would making template and module interdependencies explicit to somewhat avoid the Great Tangle. aside - wikitech-l as well as #mediawiki freenode are in my experience happy to help with individual setup woes, which could help you with the acute import issues /aside What do you all think? Should we make this happen? I'm no template expert, but I agree with a lot of what you've said based on the experiences I've had. I think we should discuss this somewhere that is less transient than this list. Stop rushing me all y'all! ;) ln short, I'm down. ,Wil ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Let's fix templates
On Wed, Sep 3, 2014 at 6:04 PM, Wil Sinclair w...@wllm.com wrote: I'd like to add distribution as one of the pain points. I wanted to have the templates that are available on enwiki for another Mediawiki installation, but I couldn't get them to work. It seems like every template has a maze of dependencies, and when I resorted to exporting all of the templates from the Mediawiki site, the software consistently crashed before all templates were exported. This sounds like a bug. Does anyone know of related bugs in bugzilla? I might have been doing it wrong, but I couldn't find any other options. One option is to use a tool (e.g. pywikibot) to transfer each template. https://www.mediawiki.org/wiki/Manual:Pywikibot This script transferbot.py does some of the required work, but it would be nice if it was improved to detect and copy any dependencies semi-automatically. https://git.wikimedia.org/blob/pywikibot%2Fcore.git/HEAD/scripts%2Ftransferbot.py Ideally, something like a package management system for templates, +1 .. extensions, and skins would be a godsend. This seems to be unrelated to templates, as they rarely depend on extensions or skins, and deploy of templates is a very different mechanism to deploy of extensions and skins. fwiw, package management systems do include separate packages for commonly needed extensions and skins. (Wouldn't it be nice if all skins could be written in Lua + LESS stored as wikipages on the wiki, instead of distributed as php files; I know of one LESS skin which works well: https://www.mediawiki.org/wiki/Skin:Chameleon ; are there others?) -- John Vandenberg ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
[Wikimedia-l] Lyon Declaration on access to information and development
Dear all, in Switzerland it's starting a meeting of libraries and one theme of discussion is the Lyon Declaration on access to information and development: http://www.lyondeclaration.org/ I see a lot of NGOs and libraries but any Wikimedia related association (or foundation). Regards -- Ilario Valdelli Wikimedia CH Verein zur Förderung Freien Wissens Association pour l’avancement des connaissances libre Associazione per il sostegno alla conoscenza libera Switzerland - 8008 Zürich Wikipedia: Ilario https://meta.wikimedia.org/wiki/User:Ilario Skype: valdelli Facebook: Ilario Valdelli https://www.facebook.com/ivaldelli Twitter: Ilario Valdelli https://twitter.com/ilariovaldelli Linkedin: Ilario Valdelli http://www.linkedin.com/profile/view?id=6724469 Tel: +41764821371 http://www.wikimedia.ch ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Recognition of Wikimedia Belgium as a Wikimedia chapter by the WMF Board
El Tue, 02 Sep 2014 20:46:45 +0300 Carlos M. Colina ma...@wikimedia.org.ve escribió: Dear all, It is an honour for me to announce that during Wikimania, the WMF resolved to recognise Wikimedia Belgium as a Wikimedia chapter. The resolution was made public a few days ago. [...] Many congratulations! Keep going forward, Belgium. -- Allan J. Aguilar B387 F3B1 0F2C F46B 36AD FAFF 7BC3 594D F7C0 E1A3 https://editandowikimedia.wordpress.com https://twitter.com/userralgis signature.asc Description: PGP signature ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
[Wikimedia-l] AffCom - Call for candidates 2015
(in the case you received it already, sorry for re-sending it, my Thunderbird crashed just as I clicked the send button :-( ) Dear all, The Affiliations Committee [1], the committee that is responsible for guiding volunteers in establishing Chapters, User Groups and Thematic Organizations and approving them when they are ready is looking for new members. The main focus of the AffCom is to guide groups of volunteers in forming affiliates. We make sure that the groups are large enough to be viable (and advise them on how to get bigger), review bylaws for compliance with the requirements and best practices, and advise the Board of the Wikimedia Foundation on issues connected to Chapters, Thematic Organizations and User Groups. This requires communication with volunteers all over the World, negotiating skills and cultural sensitivity and the ability to understand legal texts. We try to get a healthy mix of different skill sets in our members. The key skills/experience that we are looking for in candidate members, are typically the following: * Excitement by the challenge of helping to empower groups of volunteers worldwide * Willingness to process applications through a set, perhaps bureaucratic process * Readiness to participate in (movement roles) political discussions on the role and future of affiliates, models of affiliations, and similar questions * 5 hours per week availability [2], and the time to participate in a monthly ~2 hour voice/video meeting * International orientation * Very good communication skills in English * Ability to work and communicate with other languages and cultures * Strong understanding of the structure and work of affiliates and the WMF * Knowledge of different legal systems; experience in community building and organising is a plus * Effective communication skills in other languages are a major plus * Experience with or in an active affiliate is a major plus * Willingness to use full (real) name in committee activities (including reaching out to potential affiliates) when appropriate In 2012, new types of affiliations were introduced, and the role of the Committee has increased in guiding through volunteers towards affiliation models that empower them to further our mission, and making sure these models meet both the needs of the volunteers and the movement. We are looking for new people to help, who are not afraid of the workload and are motivated by helping other volunteers to get organized and form communities that further our mission around the world. Members are usually selected every twelve months for staggered two-year terms. The applications will be voted on by the current members not seeking re-election, taking into account comments put forward by the committee's members, advisers, WMF staff and board liaisons based on the above membership criteria. A final decision will be made by the end of the year, with new members expected to join on or around 1 January 2015. If you are interested, You can send your applications with your full name, contact data (e-mail address, wiki username), relevant experience and motivation letter to our treasurer Salvador Alcántar at salvador AT gmail.com by 30 September 2014. You will get a confirmation that your application came through. If you have any questions, please don't hesitate to email me and/or the committee as a whole. We are happy to chat or have a phone call with anyone about our work, if this helps them decide to apply. Please distribute this call among your networks, and do apply if you are interested. Best regards, Carlos Colina Chair, Affiliations Committee [1]: https://meta.wikimedia.org/wiki/Affiliations_Committee (please follow the links and familiarize yourself with our work) [2]: Our member standards of participation are at: http://meta.wikimedia.org/wiki/Affiliations_Committee/Resolutions/Standard_of_participation_%E2%80%93_September_2012 -- *Jülüjain wane mmakat* ein kapülain tü alijunakalirua jee wayuukanairua junain ekerolaa alümüin supüshuwayale etijaanaka. Ayatashi waya junain. Carlos M. Colina Vicepresidente, A.C. Wikimedia Venezuela | RIF J-40129321-2 | www.wikimedia.org.ve http://wikimedia.org.ve Chair, Wikimedia Foundation Affiliations Committee Phone: +972-52-4869915 Twitter: @maor_x ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] editor retention initiatives
On 02/09/14 10:56, Ricordisamoa wrote: Il 26/08/2014 12:18, Craig Franklin ha scritto: The editor retention problem will not be solved with technological gizmos and doodads, nor with top-down solutions imposed from above. It will be solved with positive human contact and creating a collaborative community that people actually want to be a part of, rather than one that they put up with. This makes my first RFBOT on the Italian Wikipedia https://it.wikipedia.org/wiki/Wikipedia:Bot/Autorizzazioni/Archivio/2013#SamoaBot come to my mind. I was much less experienced than now, and ended up flooding Recent Changes. A bureaucrat threatened https://it.wikipedia.org/w/index.php?diff=56154161oldid=5615 to block me, and I even retired https://it.wikipedia.org/w/index.php?diff=56157910 for a day. But I was already 'addicted' to Wikipedia and came back soon after. Thanks to that episode, I gradually became a quite experienced operator. But... how many users would have given up in my place? If someone has already gone to the trouble of making a bot, it seems unlikely that they would give up after a single incident. I've seen it happen after a protracted series of such incidents/screwups, but that's perhaps better for everyone involved anyway at that point. -I ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Next steps regarding WMF-community disputes about deployments
Hoi, Maybe... but it assumes that we have plenty of time and work sequently. Both are not the case and as it is, the framework is broken.to the extend that people refuse to use it. So yes, ideally you want to fix many issues nicely and in a collaborative manner. At the same time our readers are disappearing from our old platform and new editors are not happening on the old platform. The question is very much to what extend we can suffer all the baggage and backlog from the past. The question is very much what to do when we do not have that 80% on a subject that stops other developments. Thanks, GerardM On 3 September 2014 21:58, Isarra Yos zhoris...@gmail.com wrote: On 02/09/14 11:46, Marc A. Pelletier wrote: On 09/02/2014 02:52 AM, Yann Forget wrote: OK, I could buy that [fixing image pages]. But then why not fixing that *first*, so that any MV implementation coming afterwards would be smooth? In the best of worlds, that would have been ideal. Now, no doubt I'm going to be branded a cynic for this, but have you ever /tried/ to standardize something on a project? Obviously, my frame of reference is the English Wikipedia and not Commons; but in a world where there exists at least six distinct templates whose primary function is to transclude a single references/ onto a page and where any attempt to standardize to one of them unfailingly results in edit wars, that doesn't seem like a plausible scenario. I have. It's a lot of work to set up and keep on track, and can take a goodly long while to get going at all, but when it succeeds, it's totally AWESOME. Wasn't on Wikimedia, but should be totally doable here, too, provided the time, energy, and utter insanity required. Principles are the same. -I ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Next steps regarding WMF-community disputes about deployments
Hoi, Maybe... but it assumes that we have plenty of time and work sequently. Both are not the case and as it is, the framework is broken.to the extend that people refuse to use it. So yes, ideally you want to fix many issues nicely and in a collaborative manner. At the same time our readers are disappearing from our old platform and new editors are not happening on the old platform. Open source has a lot of benefits. Delivering quality software '''on a schedule''' is not one of them. But it can be done. We did it with Zend Framework with quarterly major releases. We also turned community sentiment around after the negative reaction to 1.0, which was released right before I joined Zend. I'd say that the most impactful thing we did to right the ship was hearing people out wherever they chose to discuss ZF. We monitored all channels of communication and responded to frustrations as quickly as possible. Most of our comments boiled down to: You're right. We have a problem here. Will you help us fix it? In other words, we made sure we walked the walk so that we could invite others to walk with us. And the constructive critics figured out that walking is more fun/satisfying than all the talking. Of course, that meant we walked away from some critics who weren't interested in being constructive. We never looked back. I believe this community can also turn all this dysfunction and stress in to something positive. So, let's start walking; here's a proposal/challenge for those who think Media Viewer isn't worthy: Take all that time you're investing in petitioning the community and use it to build something better than Media Viewer. A lot of you have already identified pain points in MV and some solutions have also been put forward; so, if you are not planning to get involved in the project that the WMF has set up for whatever reasons, join us in building what Media Viewer should be without the complications of dealing with the WMF. If it turns out to be a better solution than Media Viewer, then I suggest we create a petition to replace MV with the community's solution. That's the kind of positive, action-oriented petition I can sign. I'll even kick it off. We can start listing the requirements for the Worthy Media Viewer on this page: https://meta.wikimedia.org/wiki/WorthyMV. So, who's ready to walk? ,Wil ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
