Wikitech-ambassadors

wikitech-ambassadors@lists.wikimedia.org

3 participants
1661 discussions

Fwd: Apply for the FOSS Outreach Program for Women internships
by Quim Gil 20 Nov '12

20 Nov '12

Hi, I thought I had sent this email to this list, but it doesn't show up in the archives. Re-sending just in case. ---------- Forwarded message ---------- From: Quim Gil <qgil(a)wikimedia.org> Date: Thu, Nov 15, 2012 at 12:28 PM Subject: Apply for the FOSS Outreach Program for Women internships To: wikitech-l(a)lists.wikimedia.org Hi, the FOSS Outreach Program for Women internships has started! The blog post: http://blog.wikimedia.org/2012/11/15/apply-for-the-foss-outreach-program-fo… The program: https://live.gnome.org/OutreachProgramForWomen The Wikimedia specific information: https://www.mediawiki.org/wiki/Outreach_Program_for_Women If you are following Wikimedia in Identica, Twitter, G+ or Facebook, you likes and shares are welcome. Please help out reaching out to women in tech out there! -- Quim -- Quim Gil Technical Contributor Coordinator Wikimedia Foundation

1 0

Fwd: Please take this survey about new contributors
by Quim Gil 20 Nov '12

20 Nov '12

For your information. You are invited / encouraged to take this survey. Thank you! ---------- Forwarded message ---------- From: Quim Gil <qgil(a)wikimedia.org> Date: Mon, Nov 19, 2012 at 9:40 AM Subject: Please take this survey about new contributors To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> Hi, if you joined the MediaWiki / Wikimedia tech community in 2010 or later please consider taking this survey: Newcomer experience and contributor behavior in FOSS communities https://limesurvey.sim.vuw.ac.nz/index.php?sid=65151&lang=en The survey is open for sporadic contributors or full time Wikimedia employees, developers or any other profile. Anybody is welcome to leave their feedback as long as you have started contributing to this community in the past 3 years. 11 mature and well established open source projects are taking part in this survey: Debian, FreeBSD, GNOME, Gentoo, KDE, Mozilla, NetBSD, OpenSUSE, Python, Ubuntu and Wikimedia. Some of them started some days ago and have more than hundred responses by now. The data of this survey is anonymous and will be released under a ‘share-alike’ Open Data Commons Open Database License (ODbL). Some background: >From Kevin Carillo, the researcher: http://kevincarillo.org/survey-invitation/ >From OpenHatch, a non-profit working on the bridge between free software projects and new contributors: https://openhatch.org/blog/2012/a-research-project-to-understand-what-does-… PLEA If you, like me, became a bit tired of survey requests like this please consider filling this one anyway. It focuses in a specific area where we don't have much data. As fresh technical contributor coordinator at the WMF I'm looking forward to the results of this research and the lessons it will bring. Thank you. :) -- Quim Gil Technical Contributor Coordinator Wikimedia Foundation

1 0

Re: [Wikitech-ambassadors] Wikitech-ambassadors Digest, Vol 13, Issue 4
by Romaine Wiki 16 Nov '12

16 Nov '12

Hello, I would expect those things that are needed to inform my communities on what is going on with updates and so. Also when complete projectbranches like Wikivoyage and Wikidata are launched or so. I need to be able to tell the users of the projects what is going to be changed, it would be nice if reasons are given for better understanding, and what they can do to solve it if problems continue. Greetings - Romaine > Date: Sat, 10 Nov 2012 14:15:55 +0100 > From: J?r?mie Roquet <arkanosis(a)gmail.com> > To: "Coordination of technology deployments across > languages/projects" > <wikitech-ambassadors(a)lists.wikimedia.org> > Subject: Re: [Wikitech-ambassadors] What would you like on > this list? > Message-ID: > <CAFOazAP0AJN=q_n7+U1+7m-eXgxe8gy+C36TzObk46PPhcM5yg(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi, > > 100?% agree with previous answers :-) > > To sum it up in a few words: > - new features (including features available on request) > - future features (and demos) > - breaking changes (and workarounds) > - technical discussions go to wikitech-l, not here > > Best regards, > > -- > J?r?mie

1 0

VisualEditor fortnightly updates - 2012-10-29 & 2012-11-12
by James Forrester 15 Nov '12

15 Nov '12

All, Apologies for sending two at once - I failed to do this for the late-October one when the focus was on the monthly update: 2012-10-29 (MW 1.21wmf3)<https://www.mediawiki.org/wiki/VisualEditor/status#2012-10-29_.28MW_1.21wmf…> The VisualEditor was updated as part of the wider MediaWiki 1.21wmf3 branch deployment <https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf3> on Monday 29 October. In two weeks since 1.21wmf2, the team have continued to devote most of their time working on re-designing how the code integrates together and providing clean interfaces between them so new developers can re-use and extend VisualEditor in the future. Beyond the API work, we have worked to fix a number of serious bugs in the new code from the last release such as not being able to enter text in blank paragraphs in Firefox 41120<https://bugzilla.wikimedia.org/show_bug.cgi?id=41120>, as well as copy-and-paste (41055<https://bugzilla.wikimedia.org/show_bug.cgi?id=41055>) and cutting (41092 <https://bugzilla.wikimedia.org/show_bug.cgi?id=41092>) both breaking, a JavaScript error being caused when editing a blank page ( 37843 <https://bugzilla.wikimedia.org/show_bug.cgi?id=37843>), and not being able to change the formatting on two lists at once (41434<https://bugzilla.wikimedia.org/show_bug.cgi?id=41434> ). A complete list of individual code commits is available in the 1.21/wmf3 changelog <https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf3#VisualEditor>, and all Bugzilla bugs closed in this period on Bugzilla's list<https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&bug_status…> . 2012-11-12 (MW 1.21wmf4)<https://www.mediawiki.org/wiki/VisualEditor/status#2012-11-12_.28MW_1.21wmf…> The VisualEditor was updated as part of the wider MediaWiki 1.21wmf4 branch deployment <https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf4> on Monday 12 November. In two weeks since 1.21wmf3, the team have spent their time mostly working on finalising the code in preparation for its deployment in December as a test for users. One of the major changes to the integration code is how the VisualEditor can be used; it now can work on other pages than just those in the VisualEditor: namespace. (This is configurable on a per-wiki basis, rather than defined in the code itself.) Amongst other things, this now means that editing the wikitext of VisualEditor: namespace pages can be done by anyone, and is no longer restricted to just sysops (as will be needed for the December deployment). The related bugs surrounding permission checks, filter checks, conflicts, *etc.* remain, and will be fixed in the next release. Part of the preparations involved entirely re-writing the user interface code including the way in which commands operate (40896<https://bugzilla.wikimedia.org/show_bug.cgi?id=40896>). Another aspect was the addition of "Change Markers" to the data sent to the Parsoid <https://www.mediawiki.org/wiki/Parsoid> system to reduce any accidental changes that should not happen when users save. Finally, a bug with how the "save page" button worked on old revisions was fixed (41865<https://bugzilla.wikimedia.org/show_bug.cgi?id=41865> ). A complete list of individual code commits is available in the 1.21/wmf4 changelog <https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf4#VisualEditor>, and all Bugzilla bugs closed in this period on Bugzilla's list<https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&bug_status…> . An update for the Parsoid is available on its status page<https://www.mediawiki.org/wiki/Parsoid/status> . Yours, -- James D. Forrester Product Manager, VisualEditor Wikimedia Foundation, Inc. jforrester(a)wikimedia.org | @jdforrester | +1 415-839-6885 x6844

1 0

Fwd: Re: [Wikimedia-l] Wikivoyage project launch/migration update
by Quim Gil 12 Nov '12

12 Nov '12

Great opportunity for ambassadors to get involved. -------- Original Message -------- Subject: Re: [Wikimedia-l] Wikivoyage project launch/migration update Date: Sun, 11 Nov 2012 11:29:08 +0530 From: Erik Moeller <erik(a)wikimedia.org> Reply-To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org> To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org> So, if you've not been following along on wikivoyage-l ( https://lists.wikimedia.org/mailman/listinfo/wikivoyage-l ), you should know that Wikivoyage is now hosted on WMF servers. :) We're currently in "beta", as there's still lots of smaller and larger issues to work through, including transferring images to Commons or local wikis as appropriate. But now's a great time to get involved if you want to help fix things. These are the languages that are live now: httsp://en.wikivoyage.org/ https://de.wikivoyage.org/ https://ru.wikivoyage.org/ https://nl.wikivoyage.org/ https://it.wikivoyage.org/ https://sv.wikivoyage.org/ But, any other language code should gracefully redict you to Wikimedia Incubator, where you can easily get started to prove viability of a new language. :-) Like I said: Lots of things are still wonky. If you notice something you can't fix, please report it on Bugzilla and add it as a blocker for the tracking bug here: https://bugzilla.wikimedia.org/show_bug.cgi?id=41184 While we're not done yet, I'd like to take this chance to thank everyone who's been part of the process so far: * the existing communities for being awesome in supporting this migration :-) * Wikivoyage e.V. and especially Hans (for being our main tech contact managing the DB transfers), Stefan (for handling all the organizational fun), and Roland (for technical support and review). * the WMF technical launch team: Chris Steipp, Daniel Zahn, Matthias Mullie, Sam Reed + everyone who chipped in with help and support. * the WMF legal and community advocacy team: Geoff Brigham, Kelly Kay, Philippe Beaudette, and everyone else who helped. * anyone else I've forgotten to name :-) All the best, Erik -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate _______________________________________________ Wikimedia-l mailing list Wikimedia-l(a)lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

1 0

Requests for comment/Bugzilla taxonomy
by Quim Gil 11 Nov '12

11 Nov '12

Hi, you might be interested in this discussion about improving the current taxonomy of products and components in WikiMedia's bugzilla: http://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy You can watch the page and CC your selves at https://bugzilla.wikimedia.org/show_bug.cgi?id=38990 to follow the progress. Your feedback as bug reporters is welcome. -- Quim

1 0

Feedback on tech community metrics
by Quim Gil 11 Nov '12

11 Nov '12

Hi, we welcome your feedback and help on how the tech community metrics can help you finding spots to get involved and contribute. http://www.mediawiki.org/wiki/Community_metrics See the first monthly report, which started with code repository stats: http://www.mediawiki.org/wiki/Community_metrics/October_2012 See also the current draft to add Bugzilla stats in the next reports: http://www.mediawiki.org/wiki/Talk:Community_metrics#Drafting_Bugzilla_metr… You can post your feedback in the Talk pages or at wikiteck-l. You can also find me as qgil at #mediawiki and #wikimedia-dev IRC channels. Hopefully one day the metrics reports will be a good resource to find instantly your next task for the weekend. :) Thank you! -- Quim

1 0

jQuery 1.9 will remove $.browser (deprecated since jQuery 1.3 - January 2009)
by Krinkle 07 Nov '12

07 Nov '12

Hey all, Just a reminder that jQuery will (after almost 4 years of deprecation!) drop $.browser [1] in jQuery 1.9. Please check your scripts and make sure you are are no longer using "$.browser" (or "jQuery.browser"). After jQuery 1.9 is released, from the next MediaWiki deployment after that $.browser will be undefined and old code trying to access a property of it will throw a TypeError for accessing a property of undefined. Don't be alarmed, this has been a long time coming. It's been almost 4 years, and by the time this is deployed it will probably have been 4 years. For those who just realised their script is still using it, or if you read this later to fix someone else's script that just broke (hello future, did the world end in 2012?), I'll briefly describe two migration paths you can take from here: == Feature detection In most (if not all) cases of people using $.browser it is because they want different behaviour for browsers that don't support a certain something. Please take a minute to look at the code and find out what it is you are special-casing for that apparently doesn't work in a certain browser. Research on the internet and look for a way to detect this properly (examples below). Browser detection (instead of feature detection) is not reliable, nor is it very effective. For example, Internet Explorer has changed a lot since IE6. Blindly doing A for IE and B for non-IE isn't very useful anymore as most (if not all) of the new features will work fine in IE8, IE9 or IE10. The opposite is also true. If you do something cool for Chrome, you're missing other WebKit-based browsers that should get the same awesomeness (Safari, Chromium, iPhone/iPod/iPad, possibly Android, Flock, etc.) these all share the exact same engine that backs Chrome). And what if Firefox and IE also start to support this new awesome feature? There are many ways to do feature detection. jQuery comes with various detectors built-in in the object "jQuery.support"[2]. This contains for example "support.ajax", "support.opacity" and many more[2]. You can also easily make your own feature detector: * var supportPlaceholder = 'placeholder ' in document.createElement('input'); * var supportJSON = !!window.JSON; etc. If you need any help with feature detection, I'd recommend asking in one of the following channels on irc.freenode.net: * ##javascript (recommended) * #jquery * #wikimedia-dev == jQuery.client [3] If you can't figure out how to detect what you really want to switch for, there is an elaborate plugin in MediaWiki that does the same thing that jQuery.browser used to do (and more). This can be used as an alternative migration path. To give an impression: > jQuery.browser < { chrome: true, version: "22.0.1229.94", webkit: true } > $.client.profile(); < { name: "chrome", layout: "webkit", layoutVersion: 537, platform: "mac", version: "22.0.1229.94", versionBase: "22", versionNumber: 22 } For example: if ( $.browser.chrome ) {} Would become: ++ dependency: jquery.client var profile = $.client.profile(); if ( profile.name === 'chrome ) {} But: if ( $.browser.msie ) { // IE doesn't support opacity el.style.filter = 'alpha(opacity=50)'; } else { .. } Should become: if ( $.support.opacity ) { el.style.filter = 'alpha(opacity=50)'; } else { .. } Or better yet, since this is supported by jQuery core for a while now, like this: $(el).css('opacity', 0.5); Which will do the right thing for newer browsers and old IE respectively. -- Krinkle [1] http://api.jquery.com/jQuery.browser/ [2] http://api.jquery.com/jQuery.support/ [3] https://www.mediawiki.org/wiki/RL/DM#jQuery.client

2 1

Fwd: [Wikimedia-l] Info action
by Federico Leva (Nemo) 23 Oct '12

23 Oct '12

-------- Messaggio originale -------- Oggetto: [Wikimedia-l] Info action Data: Mon, 22 Oct 2012 17:41:21 -0400 Hi. This is just a heads-up that you'll start seeing a "Page information" link in the sidebar (under "Toolbox") in the coming days on Wikimedia wikis. It is deployed now to a few wikis already. This "Page information" link leads to a newly reimplemented info action: https://en.wikipedia.org/w/index.php?title=Main_Page&action=info Many, many years ago, the info action was added to MediaWiki, but due to performance issues, it was quickly disabled by default and was mostly forgotten about. This year, with the wonderful help of Madman, Krenair, and others, we have reimplemented the info action to provide an information dashboard of sorts about a particular page title to users. This dashboard includes a variety of metadata about the page, including the page's protection status, length, default categorization sort key, internal page ID, templates used on the page, and more. The content is somewhat dynamic: for some pages it will omit certain irrelevant fields and for some users (such as administrators), certain additional fields (such as the number of page watchers) will be displayed. This will slowly allow for the deprecation of outside tools that currently provide information of this nature. The hope is that this action will evolve over time to become a valuable resource for users. If you can think of data points that are missing from the current action's output or have other ideas to improve the info action (it desperately needs a little design love), please feel free to e-mail this list or file a bug at <https://bugzilla.wikimedia.org/>. MZMcBride _______________________________________________ Wikimedia-l mailing list Wikimedia-l(a)lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

1 0

VisualEditor fortnightly update - 2012-10-15 (MW 1.21wmf2)
by James Forrester 17 Oct '12

17 Oct '12

All, This fortnight's update for VisualEditor[0] - I'm skipping the one for Parsoid based on your feedback, but it is available here[1]: The VisualEditor was updated as part of the wider MediaWiki 1.21wmf2 branch deployment[2] on Monday 15 October. In two weeks since 1.21wmf2, the team have again spent most of their time working on re-designing how the code integrates together, providing clean interfaces between them so new developers can re-use and extend VisualEditor to support new 'node types' like categories or tables when we work on these later. Beyond the API work, we have entirely re-written the selection system ([3], [4], [5], [6], [7], [8], [9], and [A]), part of which included us adding IME support back in to the VisualEditor ([B]). We also fixed some bugs including selections not being restored correctly on undo/redo ([C]), backspace not always deleting the right character ([D]), pre-annotations ([E]), and fixing a JavaScript error when using Internet Explorer 10 ([F]). A complete list of individual code commits is available in the 1.21/wmf2 changelog [10], and all Bugzilla bugs closed in this period on Bugzilla's list[11]. [0] - https://www.mediawiki.org/wiki/VisualEditor/status#2012-10-15_.28MW_1.21wmf… [1] - https://www.mediawiki.org/wiki/Parsoid/status#2012-10-15 [2] - https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf1 [3] - https://bugzilla.wikimedia.org/show_bug.cgi?id=33058 [4] - https://bugzilla.wikimedia.org/show_bug.cgi?id=34095 [5] - https://bugzilla.wikimedia.org/show_bug.cgi?id=37814 [6] - https://bugzilla.wikimedia.org/show_bug.cgi?id=37833 [7] - https://bugzilla.wikimedia.org/show_bug.cgi?id=37834 [8] - https://bugzilla.wikimedia.org/show_bug.cgi?id=38000 [9] - https://bugzilla.wikimedia.org/show_bug.cgi?id=39465 [A] - https://bugzilla.wikimedia.org/show_bug.cgi?id=39965 [B] - https://bugzilla.wikimedia.org/show_bug.cgi?id=33076 [C] - https://bugzilla.wikimedia.org/show_bug.cgi?id=40538 [D] - https://bugzilla.wikimedia.org/show_bug.cgi?id=40416 [E] - https://bugzilla.wikimedia.org/show_bug.cgi?id=40677 [F] - https://bugzilla.wikimedia.org/show_bug.cgi?id=37851 [10] - https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf2#VisualEditor [11] - https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&bug_status… Yours, -- James D. Forrester Product Manager, VisualEditor Wikimedia Foundation, Inc. jforrester(a)wikimedia.org | @jdforrester | +1 415-839-6885 x6844

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Wikitech-ambassadors