Re: [Wikitech-l] Improving static analysis tools for MediaWiki.
Hi Krys, On Mon, 2015-03-09 at 17:23 -0800, Krys Nu wrote: I wish to express my interest in working on the above mentioned project. I have the required technical skill -PHP- and I am willing tread new grounds. I would love to discuss more about the project, what is really expected of the student, to establish some measurable goals before getting myself soak into the community. Improving static analysis tools for MW sounds like a wide topic. Could you provide more context please? Is this about some proposed Google Summer of Code / Outreachy task? Is there a link to some wiki page or Phabricator task providing more details? You might not get much feedback on a mailing list if you only write Please discuss with me without providing a proposal or question. :) Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Regarding gsoc 2015
Hi Arindam, On Sat, 2015-03-21 at 00:50 +0530, Arindam Padhy wrote: How can project ideas being assigned to a student before all students have submitted their proposal. i too wanted to put my proposal but my mentor says he has already selected one student for this project. this is not fair. In general, organizations have a limited number of slots and usually get more applications than slots. If there are great candidates who have expressed interest in a task and have already gotten involved (e.g. by providing an initial contribution) it might happen that a mentor already has one or more strong preferences (I don't know the exact wording of the conversation that you had). So from a different angle, it might be even fair to tell someone that their chances are low. Depends on what people consider fair. :) Are there any further tasks that interest you? In any case, I hope that you will find a great task and mentor! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 503 errors in Phabricator
On Fri, 2015-03-06 at 16:43 -0800, Pine W wrote: I figured it out: this error happens whenever I use advanced search with my browser cookies disabled. This appears to be a bug in Phabricator. If there are good and clear steps to reproduce, please file a task in Phabricator. Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] rel=canonical links changes
On Sat, 2015-03-14 at 09:41 +0100, Antoine Musso wrote: On 14/03/15 02:17, Jiang BIAN wrote: I'd like to understand if this is just a bug or is a starting of some large change across all language sites (then what's the timeline)? The change has been made on Feb 25th by changing the value of $wgCanonicalServer for the ru*wikis: https://phabricator.wikimedia.org/T90527 See also https://phabricator.wikimedia.org/T91352#1103471 for some more background. In the long run it is a goal to enable HTTPS by default on all core projects. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Hackathon anti-vandalism mini-conference
On Tue, 2015-03-31 at 23:59 +0200, Petr Bena wrote: I was looking at pages on wiki and couldn't find where to submit proposals https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015 says There are many proposals under development (see the Wikimedia Hackathon 2015 project in Phabricator). :) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Foreign commits create mess in Phabricator
(No need to CC Evan, hence moving him to BCC). On Wed, 2015-03-04 at 11:24 +0100, Petr Kadlec wrote: somebody probably already noticed this, Thanks for the notice! We are sorry for any confusion. Task status changes in Wikimedia Phabricator have been already manually reverted. For everything else, please refer to https://phabricator.wikimedia.org/T91488 Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Fwd: Phabricator monthly statistics - 2015-01
On Mon, 2015-03-02 at 11:47 -0800, Gergo Tisza wrote: It could be more interesting, although probably on the team level rather than globally, is the number of open tasks for a given priority. If, for example, the number of tasks with normal priority is growing continuously, that does signal some sort of problem with the planning. https://phabricator.wikimedia.org/maniphest/report/project/ lists total numbers of open tasks per project per priority. It does not allow tracking over time and it does not offer percentage values (like 70% of open tasks are high priority‽) but as a poor man's workaround, one could save that page once a month and compare manually. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [OT] Global user pages deployed to all wikis
Emilio, it is in everybody's interest that Wikimedia is an environment where people treat each other with respect and assume that people mean well. Criticize ideas instead of people. There is some guidance at http://wikimediafoundation.org/wiki/Code_of_conduct_policy Thank you. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator monthly statistics - 2015-03
On Wed, 2015-04-01 at 09:31 -0700, Pine W wrote: it seems to me that unbreak now bugs should be fixed in something like 10 days max. If something is seriously broken, 48 days is long time to wait for a fix. Note that the value does not express how long a task has had this priority, but how long a task which currently has this priority set has been open. For example, T1090 has been open since Nov 2014 but has Unbreak now priority only since March 2015. On Wed, 2015-04-01 at 20:40 -0300, Brian Wolff wrote: Or perhaps we need better definitions of what unbreak now means. Wasn't the original definition supposed to be for major outages? The type of thing where 48 hours was the very outside limit on acceptability? E.g. bugs of the form 25% of users can't edit. The task priorities are defined here: https://www.mediawiki.org/wiki/Phabricator/Project_management#Priority_levels The list of open or stalled tasks with Unbreak now priority: https://phabricator.wikimedia.org/maniphest/query/WtxxGlVJ.aPg/#R Some of these tasks likely don't match the definition of Unbreak now. It is welcome to ask about the progress of tasks which have had Unbreak now priority set for a while and point to the priority definitions. Generally speaking, some teams/developers are better and some are worse setting realistic expectations via priorities. The absolute numbers of open tasks per priority and project (distribution of priorities in each project) can be seen here: https://phabricator.wikimedia.org/maniphest/report/project/?order=total In my opinion, low and lowest priority should be used way more often. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Bugs to fix for MediaWiki 1.25.0
The MediaWiki 1.25.0 tarball release is planned for 2015-05-25 [1],[2]. There are currently 21 open tickets in the MW-1.25-release project: https://phabricator.wikimedia.org/maniphest/query/BPlQRzYIEE31/#R Seven tickets have patches awaiting review: https://phabricator.wikimedia.org/maniphest/query/tfwMAVRECGaZ/#R The other 14 tickets welcome help / input / code: https://phabricator.wikimedia.org/maniphest/query/HWHn.kQ9k7xU/#R If you are aware of open tasks in Wikimedia Phabricator that must be fixed before releasing 1.25.0, please associate the MW-1.25-release to these open tasks (or create a dedicated task if none exists yet). Thanks for your help! andre [1] https://www.mediawiki.org/wiki/Version_lifecycle [2] https://www.mediawiki.org/wiki/MediaWiki_1.25#Release_schedule -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Too many connections...
On Wed, 2015-04-08 at 15:36 +0200, Andre Klapper wrote: An incident report will be made available at https://wikitech.wikimedia.org/wiki/Incident_documentation once investigation has finished. https://wikitech.wikimedia.org/wiki/Incident_documentation/20150408-s2-SiteStatsInit andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] please help: promote or close your RFCs on mediawiki.org
On Fri, 2015-04-10 at 12:57 +, Cristian B. wrote: Umm, what happens to the contributors UNABLE TO USE phab? See: http://www.mediawiki.org/wiki/Topic:Sewfq489tp3iic43 Quoting a part of Bryan's reply in that thread: quoteThe Wikimedia MediaWiki API Team is working on https://phabricator.wikimedia.org/T88757 which would add an authenticate only grant to our OAuth extension. Once this is implemented we can change the Phabricator OAuth configuration so that Phabricator is not granted any rights to interact with the wikis as your user and instead only receives a yes this user is valid and authenticated response./quote andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Too many connections...
Thanks for bringing this up! There was an outage of s2 wikis. https://phabricator.wikimedia.org/T95426 is the related task and will get updated with any findings. An incident report will be made available at https://wikitech.wikimedia.org/wiki/Incident_documentation once investigation has finished. Thanks again, andre On Wed, 2015-04-08 at 21:11 +0800, Liangent wrote: I haven't seen this myself, but there're some reports about the same problem in the village pump of zhwiki. -Liangent On Wed, Apr 8, 2015 at 9:00 PM, florian.schmidt.wel...@t-online.de florian.schmidt.wel...@t-online.de wrote: Nope, it's working for me. Maybe a temp problem, have you asked on #wikimedia-operations? Freundliche Grüße / Best Florian Schmidt -Original-Nachricht- Betreff: [Wikitech-l] Too many connections... Datum: Wed, 08 Apr 2015 14:29:57 +0200 Von: Ilario Valdelli valde...@gmail.com An: wikitech-l@lists.wikimedia.org Sorry, are you experiencing the same problem than me accessing to the Italian Wikipedia? Sorry! This site is experiencing technical difficulties. Try waiting a few minutes and reloading. (Cannot access the database: Too many connections (10.64.32.30)) -- 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 Tel: +41764821371 http://www.wikimedia.ch ___ 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 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikitech-l Digest, Vol 142, Issue 9
On Fri, 2015-05-08 at 23:40 -0700, Pine W wrote: I've never seen that before. Pinging Wikitech list admin AKlapper. Feel welcome to create a bug report against the #Wikimedia-Mailing-lists project in phabricator.wikimedia.org so someone could take a look, including the affected mailing list(s) and the browsers / email applications / settings (HTML vs plain text) used. So far this does not (yet) sound like list admin territory to me. Thanks! andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Community project ideas
On Tue, 2015-05-19 at 14:34 +0200, Moushira Elamrawy wrote:
This is heads up that Kaldari has kindly started a page for community tech
projects ideas: https://meta.wikimedia.org/wiki/Community_Tech_project_ideas.
Feel free to check and add your wishlist :)
Thanks for making us aware and for collecting that list!
Are those ideas available as tasks in Phabricator so contributors could
claim them? If so, they should get linked via the {{tracked}} template.
There is a #Possible-Tech-Projects project in Phabricator for such
tasks: https://phabricator.wikimedia.org/project/profile/1042/
Curious if mw.org might be better than meta. There's for example
https://www.mediawiki.org/wiki/Outreach_programs/Possible_projects
And I'm not sure why the wiki page links to an outdated old-bugzilla
query instead of Phabricator. Maybe because by number by votes is not
available in Phab [1]? I'm not convinced that votes are more important
than linking to up-to-date task information. (Before anyone bikesheds on
votes: all arguments were already exchanged ten years ago in [2].)
andre
[1] https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Votes
[2] https://lists.wikimedia.org/pipermail/wikitech-l/2005-June/017829.html
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikitech-l Digest, Vol 142, Issue 9
On Tue, 2015-05-19 at 15:15 +0200, Andre Klapper wrote: On Fri, 2015-05-08 at 23:40 -0700, Pine W wrote: I've never seen that before. Pinging Wikitech list admin AKlapper. Feel welcome to create a bug report against the #Wikimedia-Mailing-lists https://phabricator.wikimedia.org/T99690 might be related? andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] old-bugzilla.wikimedia.org to be switched off in favor of static-bugzilla
On Mon, 2015-06-08 at 09:48 -0700, Legoktm wrote: Do we have usage statistics on how many people are still using old-bugzilla? I still use it frequently for searching for example. Only data that I am aware of is https://phabricator.wikimedia.org/T86859#1182758 (And yes, Phabricator's Search can be improved as stated in https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Considerations ) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
On Tue, 2015-06-09 at 11:32 +0200, Steinsplitter Wiki wrote: Maybe someone with enough time and knowledge can fork compat and keep it alive... As far as I understand it, there is no need to fork anything (no disagreement with existing maintainers; no contribution barriers). Anybody interested could have kept compat (more) alive over the last years. Or could in the future. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please help a patch not to become two years old
On Sat, 2015-06-06 at 21:40 +0200, Ricordisamoa wrote: https://gerrit.wikimedia.org/r/67588 needs love. Less than 2 days left! Thanks in advance. For future reference, adding basic context (e.g.: Scribunto here) is very welcome if you would also like to reach people who normally do not click links named 50 things that will make you say Oh! or You cannot imagine what will happen at the end of this video. :) Thanks, andre (obviously surprise-averse) -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] old-bugzilla.wikimedia.org to be switched off in favor of static-bugzilla
Hi everybody! More than six months ago, Wikimedia migrated its bug report management from Bugzilla to Phabricator. At the same time, Bugzilla was turned read-only (but still allowed users to log in to access and manually migrate votes or saved searches) and moved to the address old-bugzilla.wikimedia.org. Before that migration, users were asked to join Phabricator and were made aware of required steps and limitations [1]. This was done via a banner on top of Bugzilla, emails on wikitech-l@, announcements on en.wp Village Pump, and two emails to all Bugzilla users who had logged in since October 2013 [2]. Now after everybody had more than six months to switch to Phabricator, old-bugzilla.wikimedia.org is planned to get switched off on June 22nd [3] (as keeping Bugzilla running requires maintenance like applying security updates). Thanks to John and Daniel, a static HTML version of old-bugzilla exists at https://static-bugzilla.wikimedia.org [4]. It allows to still access those historical Bugzilla reports and the related history/activity. Please note that you can still claim the activity of your Bugzilla account imported into Phabricator [5] after switching off old-bugzilla, as this functionality does not rely on old-bugzilla being available. I'd like to thank John Daniel for all their work creating static-bz! Cheers, andre [1] https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Missing_data [2] https://phabricator.wikimedia.org/T618 [3] https://phabricator.wikimedia.org/T95184#1327072 [4] https://phabricator.wikimedia.org/T85140 [5] https://www.mediawiki.org/wiki/Phabricator/Help#Claiming_your_previous_Bugzilla_and_RT_accounts -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Feedback requested on our search APIs
On Wed, 2015-06-10 at 02:01 -0400, MZMcBride wrote: a list of a dozen features that are missing (search by file size, by color, by image file format, etc.). Also see https://phabricator.wikimedia.org/T101089 and https://phabricator.wikimedia.org/T101087 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
On Wed, 2015-06-10 at 15:01 -0400, Brad Jorsch (Anomie) wrote: Legal recommended we only post the list of bots, not the human accounts. These are: AHbot AsuraBot [...] Note this list is still from May 23–29; a bot appearing in this list may have been updated since then. As there are seven days left, does someone have time / capacity to provide an updated list of bots that likely haven't seen updates yet? Also, in [1], Sitic came up with a query of de.wp *gadgets* affected: https://de.wikipedia.org/w/index.php?title=Spezial:Suchelimit=100offset=0ns2=1ns8=1search=%22query-continue%22+-%22rawcontinue%22+intitle%3A*.js Has there been on-wiki outreach to *gadget* maintainers? Thanks in advance! andre [1] https://de.wikipedia.org/wiki/Wikipedia:Bots/Notizen#Hinweis_an_alle_Bot-Betreiber_.28API-.C3.84nderung.29 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] No easy tags
Hi Smriti, On Wed, 2015-06-24 at 17:38 +0300, Smriti Singh wrote: The Easy tag is becoming rarer and rarer as new tasks are coming in. This would make it pretty difficult for new developers like myself to sort through tasks to look for ones we can do. Could the community come up with something for this? It would be great if people could start adding an Easy tag if they think a task they come across is in fact an easy one :) Thanks for bringing this up! I don't have numbers whether such tasks actually become rarer (currently there are 440 open easy tasks in Phab [1]; 23 of these tasks were created this month [2]) but I can only second that everybody who looks at tasks in their area of interest and feels able to judge the complexity of a task is encouraged to tag tasks as easy [3]. The more ideas new contributors can choose from, the better! Smriti: What is your area of interest? Let's see if we can help finding some easy tasks! Cheers, andre [1] https://phabricator.wikimedia.org/maniphest/query/9XbZc7TgB8C1/#R [2] https://phabricator.wikimedia.org/maniphest/query/VJlz9JVhUIad/#R [3] https://phabricator.wikimedia.org/project/profile/169/ -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Search errors on multiple Wikimedia projects
On Mon, 2015-06-15 at 00:11 -0700, Pine W wrote: I'm getting this same error on multiple Wikimedia projects: An error has occurred while searching: Search is currently too busy. Please try again later. Help? Likely https://phabricator.wikimedia.org/T102454 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator monthly statistics - 2015-06
On Tue, 2015-06-30 at 19:08 -0600, Stephen Niedzielski wrote: Would it be difficult to report on easy tasks opened and easy tasks completed metrics? Depends on definitions I'd say (closed != resolved/fixed and projects can be added to/removed from tasks at any time), plus closed numbers aren't trivial to get (see the note in the monthly email). The code to get those monthly stats is raw SQL and in Git at [1]. I think you'd check phabricator_maniphest.maniphest_task.status and in phabricator_maniphest.edge for type = 21 (21 = project got associated to a task) and dst = PHID-PROJ-2iftynis5nwxv3rpizpe (the project ID for easy). Talking about Maniphest metrics in the long run [2] though, we now have a Maniphest backend for korma.wmflabs.org [3] and in upstream the Facts [4] application will replace Reports [5] at some point. (I'm referring specifically to the Easy tag.) It'd be a great reminder for devs to encourage new contributors. Cheers, andre [1] /operations/puppet/modules/phabricator/templates/community_metrics.sh.erb [2] https://phabricator.wikimedia.org/T28 [3] https://phabricator.wikimedia.org/T96238 [4] https://secure.phabricator.com/T1562 [5] https://phabricator.wikimedia.org/maniphest/report/ -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Automatic Transfer SVN Extension to GIT
On Tue, 2015-07-07 at 16:37 +, Thomas Mulhall wrote: I think this was moved to phabricator. If this is requesting the creation of new Git repositories, it's handled at https://www.mediawiki.org/wiki/Git/New_repositories/Requests (linked from https://phabricator.wikimedia.org/project/profile/330/ ) Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] extension updates for 1.23.x?
On Tue, 2015-08-11 at 14:17 -0400, Mark A. Hershberger wrote: Jim Tittsler j...@onjapan.net writes: What is the recommended path for updating extensions if you are still using the 1.23.x series? Generally, extensions don't update their release branches. Sometimes you can use the latest from master's HEAD for an extension, but breaking changes happen often enough in core that this can cause a problem. If you want fixes back-ported to the LTS version, your best bet is to talk to the extension's maintainer. Related task: https://phabricator.wikimedia.org/T108734 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator filter by language
On Fri, 2015-07-17 at 10:04 +0200, Petr Bena wrote: What if we added extra projects to phabricator for programming languages (such as language-php, language-c) which could be optionally added to some tickets if help of people who know these languages would be needed. So that it would be possible for example to c++ experts to filter out open tasks that need c++ expert to look in them and so on? Currently I have few of such tasks that I would like to have experts in some language to look at, but there isn't really an easy way to do that. What you think? Should we add these meta-projects? If there was enough shared interest to add such tags, they should have a naming format need-XYZ-help or such. Whenever a new tag is created, you need to raise awareness so 1) tasks actually gets tagged and 2) people get to know they are supposed to search for such tags. Communicating to your target group, maybe. A tag language-php would not imply it's optional. Searching for tasks under a project/tag, I'd expect results not to be optional results. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator tag for bugs in local projects
On Thu, 2015-07-16 at 01:00 -0500, Alex Monk wrote: A single gadgets project that just tracks an issue with any MediaWiki gadget out there is just going to create a completely useless mess. +1. On Jul 15, 2015 10:16 PM, Jon Robson jdlrob...@gmail.com wrote: On phabricator should there be a gadgets project? Community project? Any input for a potential general concept is welcome on https://phabricator.wikimedia.org/T85433 . Examples for obstacles / questions to answer can also be found in https://phabricator.wikimedia.org/T102657 Note that we have an example for a Gadgets project in Phabricator at https://phabricator.wikimedia.org/project/profile/1278/ because the discussion in https://phabricator.wikimedia.org/T100512 was convincing. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator tag for bugs in local projects
On Thu, 2015-07-16 at 07:27 +0300, Amir E. Aharoni wrote: In the past it happened to me a few times that I opened bugs about something wrong that happened on a Wikimedia site, and it was closed as invalid because the issue was not in MediaWiki code, but in a local gadget, style or template on that project. The bugs were actually fixed, but I'd like to question the invalid closure. https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle cur rently says A report is given the Invalid status when the problem is not a bug, or when it is a change that is outside the power of the component's developers. When closing a task as invalid the person closing the task should add an explanation. In this case: User scripts, gadgets and templates are local features and managed on wiki. Phabricator/Maniphest is used for MediaWiki, MediaWiki extensions, or server configuration. You could contact the author of the script/gadget or ask for help on the local Technical Village Pump. Closing as INVALID here in Phabricator as this is a matter to discuss and fix on the local wiki and currently not handled in Phabricator/Maniphest. See https://phabricator.wikimedia.org/T85433 for using Phabricator for gadget-related tasks (and discussing that idea). Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Defining and marking inactive/unmaintained code repositories
Hi everybody, one requirement for the Gerrit Cleanup Day planned for September 23rd ([1], I still need to send a proper announcement, sorry for that) is to allow marking code repositories as inactive. This requires agreeing on criteria what's inactive, after which time span, and on a process that allows people to mark projects as such. There is a proposal in https://phabricator.wikimedia.org/T102920 concentrating on what's feasible currently with our given tools. It welcomes more feedback. If you're interested I kindly ask you to take a look at the Phabricator task and add your comments there. Thanks in advance! andre [1] https://phabricator.wikimedia.org/T88531 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] XSS warning for an image download
On Sat, 2015-10-24 at 20:57 -0700, Pine W wrote: > When I right-click on the image download link for > File:Commodore_Grace_M._Hopper,_USN_(covered).jpg the download I get > is > only 269 bytes and it contains a 404 error in plaintext even though > it's a > jpg file. > > When I click on the image preview that's 480x600 pixels, I get an XSS > warning from Noscript. > > All other images download ok for me. > > Any knowledge of what the issue is with this one file? Does the first behavior also happen when NoScript is disabled? If it only happens with NoScript enabled, I'd rather ask in a NoScript forum or mailing list... andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Get those small bugs in your project fixed: It's Google Code-In time!
Ask yourself: * Does your documentation need improvements? * Do you have small, self-contained, "easy" bugs you'd love to get fixed? (Also see https://www.mediawiki.org/wiki/Annoying_little_bugs ) * Do your old bugs welcome some testing? * Does your user interface have some small design issues? * Does the Outreachy/GSoC project you finished welcome small tweaks? * Would you enjoy helping someone port your template to Lua? * Does your gadget use some deprecated API calls? * Do you have some tasks that welcome some research? Google Code-In (GCI) will take place again in Dec+Jan: a contest for 13-17 year old students to provide small contributions to free software projects. And Wikimedia will apply again to take part in GCI! Unsure about quality of contributions and effort? Read about tgr's post about Multimedia achievements in GCI 2014: https://lists.wikimedia.org/pipermail/multimedia/2015-January/001009.html In short: * Add the project "GCI2015" + a comment to Phabricator tasks you'd mentor. * Tasks are welcome in five areas: Code; Outreach/Research; Documentation/Training; Quality Assurance; User Interface. * Make sure the task description provides pointers to help the student. * Add yourself to the table of mentors on the wikipage. * "Beginner tasks" (<30 min for an experienced contributor) also welcome. * "Generic" tasks also welcome (e.g. "Fix two user interface messages from the "Blocked By" list in https://phabricator.wikimedia.org/T40638 ;). For all information, check https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner Wikimedia has more than 600 "easy" tasks available: https://phabricator.wikimedia.org/maniphest/query/609oZQR8EpOH/#R Can you imagine helping someone fix one of these tasks? Please ask if you have questions. Thank you! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 1.26 Release
Hej hej, On Wed, 2015-10-28 at 13:53 +, Marcin Cieslak wrote: > 1) Should I add RELEASE NOTES entry in every change that closes a > bug? To be answered by someone who knows. My uneducated guess is Yes. > 2) When should I tag MW-1.26-release-notes ? You are welcome to add #MW-1.26-release to any task that got fixed for the 1.26.x tarball release. #MW-1.26-release-notes does not exist. For 1.27, #MW-1.27-release is to be used for tasks that shall get fixed for the tarball release of 1.27.x. #MW-1.27-release-notes shall be used for any tasks that got fixed for 1.27. For more background, see https://phabricator.wikimedia.org/T113628 > 3) How should I tag changes that are in master but should be > backported? I wonder how much https://www.mediawiki.org/wiki/Backporting_fixes#Backports_to_stable.2Fsupported_release still reflects the reality. There is a #MediaWiki-Tarball-Backports in Phabricator but I'm not sure if anyone really uses it. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 1.26 Release
On Wed, 2015-10-28 at 16:05 +, Chad wrote: > Please do not do this. I'm using the 1.26-release tag to track > things that need to be done prior to the release. I've been actively > removing the (mostly automated, from the release tagger bot) 1.26 > tag from things that are just "fixed and will be in the branch." I stand corrected. Thanks Chad! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Developer Relations Weekly Summary
Hi, On Thu, 2015-10-22 at 08:23 -0700, Pine W wrote: > There has been a lot of discussion recently about the Education Exension's > problems. Any chance of getting Developer Relations resources in making > that code at least secure and maintainable enough to keep it deployed on > its current wikis in the short term and in order to buy some time for > development of long term solutions? See https://phabricator.wikimedia.org/T110619#1714416 Potentially related: https://phabricator.wikimedia.org/T91676 > I want to express moral support for anything related to improving the code > review experience, which seems to be a pinch point in multiple workflows > and I hear is a subject of frequent concern. I would support finding > additional budget resources (preferably through internal transfer rather > than new expenditure) to address this problem if analysis shows that > transferring or adding some resources (maybe 0.5 FTE?) would make a > meaningful difference. Wikimedia plans to migrate code review from Gerrit to Phabricator's Differential - see https://phabricator.wikimedia.org/T114311 There is also a task about reducing code review queues + waiting times which welcomes input: https://phabricator.wikimedia.org/T101686 > Can you provide a brief update on how the deployment is going of the > Newsletter extension? https://phabricator.wikimedia.org/T110170 is the corresponding task, as far as I know the tasks listed under "Blocked By" are up-to-date. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia accepted in Google Code-in 2015 - Bring your tasks!
Wikimedia is among the 14 organizations in Google Code-in (GCI) 2015! In Dec & Jan, many young students will want to contribute to Wikimedia. Will you mentor some tasks? It's easy and fun. GCI is a great opportunity to let new contributors complete those small little tasks on your To-Do list! Task areas are: Code, docs/training, outreach/research, quality assurance, and user interface. Do your docs on your wiki need some improvements? Does your template or gadget code needs some updates? Do you have small and self-contained bugs you'd love to get fixed? Does your UI have small design issues? Do your old bugs welcome some testing? Then become a mentor and enjoy working with a contributor! Add yourself to the mentor's table on the wiki page, get an invitation email to register on the contest site, and create tasks (which would take you 2-3h to complete, or less technical ~30min "beginner tasks")! Explain the expectations and deliverables in the task. Once the contest starts on Dec 07, be ready to answer and review contributions quickly. See https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner Need task ideas? Check out the list of "easy" tasks in Phabricator: https://www.mediawiki.org/wiki/Annoying_little_bugs lists Phabricator queries for your area! https://www.mediawiki.org/wiki/Google_Code-in_2015 has all information. Or just ask and we'll be happy to help! Thank you! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Contributing to Wikimedia Foundation
Hi Bill, On Sun, 2015-11-01 at 22:22 +0100, Bill Morrisson wrote: > I want to contribute to Wikimedia's opensource projects. I am a newbie in > PHP and MySQL(just started learning the language 8 months ago) and had in > mind in contributing to the organization as soon as I am comfortable in the > languages. > I would like to contribute in PHP and looking forward to learn javascript > on the go with other projects as well. I would love to hear from wikimedia > if there is anything I can do first. Great! Thank you for your interest! https://www.mediawiki.org/wiki/How_to_contribute is an overview of all the many ways how to contribute to Wikimedia. As you state that you are interested in hacking, https://www.mediawiki.org/wiki/Developer_hub provides a high-level overview of MediaWiki development for hackers. It also links to https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker for starters. If you are looking for some "easy" bugs to work on, https://www.mediawiki.org/wiki/Annoying_little_bugs is also linked from that page. It offers some queries for bug reports in Wikimedia's issue tracking system. Don't hesitate to ask if you have any questions! Looking forward to your first patch contribution! Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tech Talk: Nothing Left but Always Right: The Twisted Road to RTL Support: November 2
On Tue, 2015-11-03 at 22:25 +0100, DaB. wrote: > Am 03.11.2015 um 20:20 schrieb Rachel Farrand: > > <http://www.youtube.com/watch?v=qmLdHuFRGgM>* > > It has been released under a creative commons license. > > may I ask why it was not uploaded to Wikimedia Commons? I once uploaded a Hangout/Youtube video to Commons by following https://commons.wikimedia.org/wiki/Commons:YouTube_files and it felt cumbersome - in my humble opinion our tool chain is currently very "manual" in this area. Would love to see something similar to the Flickr import support in UploadWizard. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Technical expertise needed for Individual Engagement Grant proposals!
On Tue, 2015-10-06 at 21:05 -0600, Brian Wolff wrote: > It would be nice if before asking for general review, the proposals > were vetted to have sufficient detail. Some of these seem to be "I > want X$ to do Y, and I'm not going to tell you how I plan to do Y, or > how I determined X$ is needed, or even give a detailed definition of > what Y is". > > For a grant proposal, I'd expect to see budget justifications, time > estimations broken down by rough sub tasks, a general plan of attack, > potential risks and how the grantee plans to mitigate them, user > acceptance criteria, etc Thanks Brian. These sound like very valid points. I'm curious if application templates of other (technical) programs have already been looked at for IEG and which conclusions were drawn. Seeing https://www.mediawiki.org/wiki/Outreach_programs/Application_template a nd https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project I can imagine there's knowledge to share (*if* that hasn't happened yet). andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Saving MediaWiki:common.js
Hi Phillip, On Wed, 2015-08-26 at 19:38 +, Legault, Phillip [ITSUS] wrote: I ran into an issue trying to save MediaWiki:Common.js I get this page not available (index.php?title=MediaWiki:Common.jsaction=submit) MediaWiki:Common.css save fine On some Wikimedia site (which one)? Or a private wiki? Is that the complete error message displayed (if not: please make sure to not post private data like your IP adress)? Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Gerrit Cleanup Day: Wed, Sep 23
I'm happy to announce a Gerrit Cleanup Day on Wed, September 23. It's an experiment to reduce Wikimedia's code review backlog which hurts growing our long-term code contributor base. Development/engineering teams of the Wikimedia Foundation are supposed to join and use the day to primarily review recently submitted open Gerrit changesets without a review, focussing on volunteer contributions. And developers of other organizations and individual developers are of course also very invited to join and help! :) https://phabricator.wikimedia.org/T88531 provides more information, steps, links. Note it's still work in progress. Your questions and feedback are welcome. Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator monthly statistics - 2015-08
On Wed, 2015-09-02 at 06:53 +0900, Yongmin Hong wrote: > 2015. 9. 1. 오후 7:18에 <communitymetr...@wikimedia.org>님이 작성: > > Needs Volunteer: 16678 > > I thought this "Needs Volunteer" has been renamed to "Lowest" a while > ago? It has been, but the string in the script [1] has not been updated. Patches welcome [2]. :) Also, as Krenair pointed out the number "16678" is wrong. Not sure yet what's broken here. Cheers, andre [1] https://git.wikimedia.org/blob/operations%2Fpuppet.git/45eae7321e2e2ee15eebb542983dd4bc7b1eb3ad/modules%2Fphabricator%2Ftemplates%2Fcommunity_metrics.sh.erb#L206 [2] https://mediawiki.org/wiki/Gerrit/Tutorial -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] UploadWizard long term problems
On Tue, 2015-09-15 at 08:10 -0500, Mark Holmquist wrote: > What file(s) were you using? How long did you wait between opening the page > and uploading the file(s)? What license(s) are you uploading them under? > What file format are they? What browser were you using? What OS? Do you get > any error messages in the browser console? Does any other process on your > system seem slow or halted? Are these questions listed on some UploadWizard wikipage/section? https://commons.wikimedia.org/wiki/Commons:Upload_Wizard_feedback says "To resolve issues, it helps us to have exact steps to reproduce" so I'd love that sentence to link to such "basic" debugging questions. Does also asking users to add "?debug=true" to the URL and to try again make sense in the context of debugging UploadWizard issues, or not? andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Mentors and projects needed for Outreachy round 11
On Mon, 2015-09-28 at 12:09 -0700, Pine W wrote: > Hi Brian, > I was told by a WMF non-management employee that they have little > discretion about which projects they're working on, and that the decisions > about priorities come top-down. Hence my interest in engaging with the > quarterly planning processes and the people managing those processes to see > if there's a way to get community input into the teams' quarterly goals. WMF is made up of several teams. For a list, click "Organizational overview" on https://wikimediafoundation.org/wiki/Staff?showall=1 Some members of some teams might either be or have the feeling of being more influenced by potential top-down priorities. Others less. About engaging with the planning processes and people: For Engineering, the main goals and contacts for Oct-Dec are here: https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q2_Goals That page links to each team's homepages (they are also linked from https://www.mediawiki.org/wiki/Wikimedia_Engineering ) which should cover the planning processes, communication/contact info, etc. Hope that helps a bit? Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] MediaWiki 1.26 release blockers
MediaWiki 1.26 will be released later this year. There are 62 open tasks in Phabricator tagged with "MW-1.26-release". Some tasks miss an assignee; some tasks welcome patch review. Dropping some links here to raise awareness and ask for help: 12 without any assignee and without a "Patch-For-Review": https://phabricator.wikimedia.org/maniphest/query/MoC9YKZ4gsR./#R 48 with "Patch-For-Review": https://phabricator.wikimedia.org/maniphest/query/w6gwbg0JIWRl/#R 23 with Assignees set (Aaron, Addshore, Bawolff, bd808, Catrope, Cenarium, Dchan, Gilles, Jdlrobson, Hexmode, Legoktm, Matmarex, Seb35, Sn1per, Tgr, Željko): https://phabricator.wikimedia.org/maniphest/query/KWoEsNbaAjFX/#R andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Gerrit Cleanup Day: Wed, Sep 23
On Tue, 2015-09-01 at 00:27 +0200, Andre Klapper wrote: > I'm happy to announce a Gerrit Cleanup Day on Wed, September 23. Thank you to everybody who participated yesterday and took the time to review patches, reduce our backlog, and give feedback to contributors! We collect feedback & "lessons learned" about our Code Review Cleanup Day experiment in https://phabricator.wikimedia.org/T113378 Please raise your voice! It will help our goal to reduce code review queues and waiting times [1] and coming up with a plan how to prioritize code review of patches contributed by volunteers [2]. Thanks, andre [1] https://phabricator.wikimedia.org/T101686 [2] https://phabricator.wikimedia.org/T78768 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] [Reminder] Gerrit Cleanup Day: Wed, Sep 23
Reminder: This is in two days. Everybody is very welcome to join and help, especially in areas with unclear maintainership! Please check out https://phabricator.wikimedia.org/T88531 for Gerrit queries and for points of contact per area! Happy reviewing!, andre On Tue, 2015-09-01 at 00:27 +0200, Andre Klapper wrote: > I'm happy to announce a Gerrit Cleanup Day on Wed, September 23. > > It's an experiment to reduce Wikimedia's code review backlog which > hurts growing our long-term code contributor base. > > Development/engineering teams of the Wikimedia Foundation are supposed > to join and use the day to primarily review recently submitted open > Gerrit changesets without a review, focussing on volunteer > contributions. And developers of other organizations and individual > developers are of course also very invited to join and help! :) > > https://phabricator.wikimedia.org/T88531 provides more information, > steps, links. Note it's still work in progress. > > Your questions and feedback are welcome. > > Thanks, > andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Google Code-in 2015 starts today! Contributors and questions, tasks and mentors.
Google Code-in 2015 will start today and run for seven weeks: https://www.mediawiki.org/wiki/Google_Code-in_2015 Many young students will make their first contributions to Wikimedia hence there will be lots of questions on IRC and mailing lists. Your help (and patience) is welcome to answer them and provide a helping hand to an onboarding newcomer. Thanks to all mentors who have registered & provided some tasks! You have not become a mentor yet? Consider it - it's fun! * Think of easy tasks in your area that you could mentor. Areas are: Code, docs/training, outreach/research, quality assurance, and user interface. "Easy" means 2-3h to complete for you, or less technical ~30min "beginner tasks" for onboarding). * OR: provide one easy clonable task (a type of task that is generic and could be repeated many times by different students. * Note that you commit to answer to students' questions and to evaluate their work within 36 hours (but the better your task description the less questions. No worries, we're there to help!) For the full info, please check out https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner and don't hesitate to ask questions if something is unclear! Thank you again for giving young contributors the opportunity to learn about and work on Free and Open Source Software projects! Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] PHP 7.0.0 Released
On Fri, 2015-12-04 at 00:40 +, Alex Monk wrote: > Wasn't newphp actually a keyword imported from Bugzilla into > Phabricator as a tag? Exactly. It's been around for ages so its desc isn't too accurate as "new" becomes "not so new anymore" at some point, and it's not about PHP 7 only (though there are already some PHP 7 incompatibility tasks). andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Is there some non-ssl mirror of wikipedia?
On Sun, 2015-12-06 at 17:07 +0100, Petr Bena wrote: > I noticed that since we enforce SSL on Wikipedia for everyone, > Wikipedia is much more restricted in some countries, such as China, > where it's entirely blocked (I think only SSL is blocked, but users > now have no option to fall back to non-ssl version). > > Is there some non-ssl mirror for people in these countries? Or did we > just gave up on "free knowledge for everyone"? https://meta.wikimedia.org/wiki/HTTPS#Links links to a "Discussions" subpage which lists past discussions. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Mediawiki message delivery problems
On Fri, 2015-12-11 at 09:02 +0100, Bináris wrote: > Please, please, for anyobody working on Wikipedia, be basic to use ! > This is the first lesson taught. Currently the actual creator is added as a (HTML source code) comment (your link to the diff shows "User:Matiia@metawiki"). It's not too obvious and I'd also prefer real user names, for accountability. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Half-time achievements in Google Code-in 2015
We are half way through this year's Google Code-in contest: https://www.mediawiki.org/wiki/Google_Code-in_2015 Thanks to our GCI contributors (and the help of Wikimedia's 31 mentors) we have seen more than 150 tasks resolved already! To list only some of the students' achievements: * More than a dozen of MediaWiki extensions converted to use extension registration * Confirmation dialogs in UploadWizard + TimedMediaHandler use OOjs-UI * Vagrant roles created for the EmbedVideo and YouTube extensions * Two more scraping functions in the html-metadata node.js library (used by Citoid) * Many MediaWiki documentation pages marked as translatable * lc, lcfirst, uc and ucfirst magic words implemented in jqueryMsg * Screenshots added to some MW extension homepages on mediawiki.org * ConfirmEdit's ReCaptchaNoCaptcha uses the UI language for the captcha * MobileFrontend, MultimediaViewer, UploadWizard, Newsletter, Huggle, and Pywikibot received numerous improvements (too many to list) * ...and many, many, many more. Please join me in congratulating and thanking our contributors and mentors for working hard on improving Wikimedia! I'd also like to thank everybody on the #mediawiki and #wikimedia-dev IRC channels who has helped with onboarding and answering questions. Sounds interesting? Got a small well-defined task in mind you are willing to mentor? Join and become a mentor if you aren't already! Read https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner and contact us if you need help! Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Fwd: Your stand proposal for FOSDEM 2016 has been accepted
On Tue, Dec 22, 2015 at 2:38 AM, Moriel Schottlender wrote: > Is this the first year we'll have a stand in FOSDEM, or did we have > one in previous years? Wikimedia had stands in the AW building in '14 [1] & in K in '15 [2]. andre [1] https://www.mediawiki.org/wiki/Events/FOSDEM/2014#Wikimedia_stand [2] https://www.mediawiki.org/wiki/Events/FOSDEM/2015#Wikimedia_stand -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] git.wikimedia.org down?
On Fri, 2015-11-27 at 11:06 +0100, planetenxin wrote: > Since yesterday we could not reach git.wikimedia.org any more. See https://phabricator.wikimedia.org/T83702 : The gitblit software powering git.wikimedia.org is in the process of being replaced by Phabricator Diffusion. https://phabricator.wikimedia.org/diffusion/ is available. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Community Wishlist Survey: Top 10 wishes!
On Sat, 2016-01-09 at 12:13 -0800, Brian Wolff wrote: > On Saturday, January 9, 2016, Rob Lanphier wrote: > > As Danny said, this is a wonderful thing to point out, and his > > answer > > way more authoritative than mine. Thinking back to my early MediaWiki > > contribution experience, I would have loved to have had a ranked list > > of "these are things that are really important" so that I knew my > > contribution would ultimately be appreciated and important to the > > project. > > > > RIP bugzilla votes... I consider votes within a separate developer-focused tool (Bugzilla, which required a separate account) less representative than on-wiki. The latter allows a broader variety of community members to participate and raise their voices in an environment they are familiar with. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Crediting the work of our community members
Is there a Phabricator task so this topic does not get forgotten? andre On Mon, 2016-05-30 at 09:40 -0700, Jon Robson wrote: > "I came across a patch from a user who was keen to move himself from > "Patch contributors" to "Developers" in the MediaWiki CREDITS file > [1]. It had been sitting there for over a year. He doesn't seem to > have been active since. I don't know what to do with it. It made me > think. > > Do we have it documented anywhere how we use this credits file and why > we feel the need to distinguish between Developers and Patch > Contributors? It seems like a recipe for disaster in my opinion as it > can only lead to hurt feelings due to contributors feeling unfairly > treated. https://www.mediawiki.org/wiki/Special:Version/Credits leads > with 'We would like to recognize the following persons for their > contribution to MediaWiki." - if someone is not in that list are they > not as important? > > If we keep these files we should probably explain the rules to what > adding names looks like within these files and what the process to > adding your name is (can I add myself? Is there a process like > getting +2?) > > To take another extreme, we might consider abandoning such a file in > favour of something automatically generated. Things like > https://github.com/wikimedia/mediawiki/graphs/contributors do a far > better job at allowing people to see who contributed to a tool and > making people feel like their work is rewarded. > > On a slightly related note, can we abandon the practice of putting > names inside files themselves? I see this practice in JavaScript and > PHP files throughout core (grep for @author). As Team Geek [2] (great > read btw) says "unlike other collaborative pieces of creative work... > software keeps changing even after it's "done". So while listing > contributors credits at the end of a movie is a safe and static thing, > attempting to add and remove names from a source file is a > never-ending exercise in insanity". For similar reasons this practice > gives an impression of ownership of a file/code review > responsibilities (which are not always true) and risks hurt feelings. > > [1] https://github.com/wikimedia/mediawiki/blob/master/CREDITS > [2] > http://www.amazon.com/gp/search?index=books=qs=9781449302443 > > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia Git/Gerrit/Code Review technical documentation updates
On Mon, 2016-05-23 at 17:32 +, Chad wrote: > On Mon, May 23, 2016 at 9:42 AM Bernd Sitzmann wrote: > > > > I think it would be great to favor git fetch and git rebase over git pull > > and merge[1] in the beginners documentation so people don't start out with > > bad habits. > > > > [1] https://wikitech.wikimedia.org/wiki/Help:Git_rebase > > > `git pull -r` for life :) > > -Chad I concentrated on Git docs on mediawiki.org and pretty much ignored content on wikitech.wikimedia.org. I'm not a Git pro at all so if there seems to be consensus, please anyone be bold and edit to improve our contribution guidelines. Thank you in advance! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator monthly statistics - 2016-05
On Wed, 2016-06-01 at 01:24 +0100, Alex Monk wrote: > If you look back through all the previous monthly statistics emails, > account creations regularly go above 300 per month. For a graphical overview over the last months, also see https://www.mediawiki.org/wiki/Community_metrics#New_accounts_in_Phabricator Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator monthly statistics - 2016-05
There have been months when the number of open tickets in Bugzilla decreased, but IMO that was always due to a mass-cleanup of ancient open tickets and not because of a sudden burst of coding activity. Bugzilla was a bug tracker for software bug reports & feature requests. Phabricator is a project management tool also welcoming managing projects unrelated to software (e.g. chapter activities) plus superseding activity previously taking place in Mingle, Trello, or RT, which I see as one reason for the amount of activity and tasks. andre On Tue, 2016-05-31 at 19:01 -0700, Pine W wrote: > Just to add to Bartosz's comment, the definition of tasks in Phabricator > includes feature requests, so more tasks may or may not correlate with more > problems. > > Someone in QA may be able to comment with more detail about the number, > severity or percentage of problems relative to the number of tickets, and > the general quality trends of MediaWiki. > > Pine > On May 31, 2016 18:20, "Bartosz Dziewoński" <matma@gmail.com> > wrote: > > > > > On 2016-06-01 02:24, Alex Monk wrote: > > > > > > > > Here are the numbers that I'd like to draw people's attentions > > > to: > > > Tasks created in (2016-05): 2572 > > > Tasks closed in (2016-05): 2275 > > > That's a difference of 297 tasks... > > > Difference (2016-05): 297 > > > Difference (2016-04): 243 > > > Difference (2016-03): 454 > > > Difference (2016-02): 238 > > > Difference (2016-01): 418 > > > These difference should really be negative, but right now it > > > looks like > > > we're slowly accumulating more and more bugs... > > > > > We are, and we've always been. If you go through the same data from > > the > > time of Bugzilla, I don't think you'll find a single month where > > the count > > decreased. I don't remember any myself. > > > > -- > > Bartosz Dziewoński > > > > ___ > > 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 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator monthly statistics - 2016-05
On Wed, 2016-06-01 at 04:23 +0200, Danny B. wrote: > If tasks were properly triaged and tagged, it would be easy to create > various quite accurate statistics. If you think that tasks aren't "properly triaged" currently, could you elaborate what specifically you'd like to see changed? > But attempts to create tags which would allow it were and are > unfortunatelly being questioned, delayed, stalled or even declined. Do you have specific examples? I do ask for usecases on proposed tags when I don't see how they'd support those folks managing and fixing tasks, as I'd like to avoid categorizing for the sake of categorizing (+people need to do the categorizing, which triggers notifications). > In one of my previous jobs, where I was taking care of the bugtracker as a > part of my duty, after I made an order in it, the number of opened tasks > decreased to nearly 70% of the original count. Was that a public bugtracker where anyone could file tasks and anyone could work on tasks (FOSS project?), or an internal instance? Cheers, andre > Then after some statistics I' > ve ran from the new data, our teams became more effective and productive due > to having better data to work with and at the end of the consolidation > process, we ended up in oscilating between 30-50% of the original amount of > opened tasks. > > I wish it was possible to achieve the same here... -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Authentication session unwanted across wikis (was Recent authentication session instability)
On Sun, 2016-06-19 at 16:48 +0200, Purodha Blissenbach wrote: > The unified account login has been a pain my ass since the very earliest > discussions about it. I knew, it would not work well, and indeed, it > does not work well. Could you please point to bug reports which cover specific aspects so that we can understand what "does not work well" for you? > You argue like a car maker that now offers automatic car only, > regardless of their customer base and regardless of the increased > fuel consumption, wear, etc. The 'customer base' asked for Single User Login: https://meta.wikimedia.org/w/index.php?title=Wikimedia_Forum=next=3619272 If your car with Single User Login increases fuel consumption, can you please point to specific issues with steps to reproduce the problem? > I suggest, if you make an additional feature changing basic behavior, > have it as an addition, not a replacement. If you must make it a > default, you must add an option to switch it off. Anomie already explained why adding options and if/then/else code complexity creates huge software maintenance costs over the years... andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] [Update] Wikimedia Code Review technical documentation
As part of the effort to improve our code review process, the documentation for patch *authors* saw some improvements at https://www.mediawiki.org/wiki/Gerrit/Code_review/Getting_reviews The page now lists some prerequisites, expectations about the patch (scope, testing, docs), and a new section about dealing with obstacles (no timely review, further reasons for rework or rejection). [1],[2] Your feedback is welcome on its talk/discussion page! The next step will be to discuss having a structured, standardized approach for reviewing code contributions and to generally improve the documentation for reviewers. Please help in https://phabricator.wikimedia.org/T129067 Cheers, andre [1] https://phabricator.wikimedia.org/T129068 [2] Diff: https://www.mediawiki.org/w/index.php?title=Gerrit%2FCode_review%2FGetting_reviews=revision=216=1910448 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Google Code-in 2015 is over. Congratulations everybody!
Google Code-in 2015 has come to an end. Thanks to our students for resolving 461 Wikimedia tasks. Thanks to our 35 mentors for being available, also on weekends & holidays. Thanks to everybody on IRC for your friendliness, patience, and help provided to new contributors. Some more achievements, apart from those already mentioned in https://lists.wikimedia.org/pipermail/wikitech-l/2015-December/084421.html : * The CommonsMetadata extension parses vcards in the src field * The MediaWiki core API exposes "actual watchers" as in "action=info" * MediaWiki image thumbnails are interlaced whenever possible * Kiwix is installable/moveable to the SD card, automatically opens the virtual keyboard for "find in page", (re)starts with the last open article * imageinfo queries in MultimediaViewer are cached * Twinkle's set of article maintenance tags was audited and its XFD module has preview functionality * The RandomRootPage extension got merged into MediaWiki core * One can remove items from Gather collections * A new MediaWiki maintenance script imports content from text files * Pywikibot has action=mergehistory support implemented * Huggle makes a tone when someone writes something * Many i18n issues fixed and strings improved * Namespace aliases added to MediaWiki's export dumps * The Translate extension is compatible with PHP 7 The Grand Prize winners & finalists will be announced on February 8th. Again congratulations everybody, and thanks for the hard work. See you around on IRC, mailing lists, Gerrit, and Phabricator! Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Developer Relations Weekly Summary
On Thu, 2016-01-28 at 14:57 -0800, Pine W wrote: > Is there, or will there be, a page somewhere that describes the > outcomes of the Developer Summit? I'm not aware of a page but summaries for specific tracks or sessions can be found in the corresponding Phabricator tasks: https://phabricator.wikimedia.org/maniphest/query/aCQDiHyEiCjl/#R andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GSoC 2016
On Tue, 2016-02-23 at 21:34 +0530, Mehul Sawarkar wrote: > I am Mehul Sawarkar, a Computer Science student from India . I want to be > part of wikimedia in GSoC 2016.Pplease help me getting started .Is there > any small bug that I can fix? Hi Mehul! Thanks for your interest and welcome! Please check out https://www.mediawiki.org/wiki/Google_Summer_of_Code_2016 for more info and links. To find small bugs for new contributors, please take a look at https://www.mediawiki.org/wiki/Annoying_little_bugs Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [GSoC2016] Automatically create a summary of wiki articles
On Mon, 2016-02-22 at 20:19 +0530, Ultimate Supreme wrote: > Though there has been some independent research > <http://lms.comp.nus.edu.sg/sites/default/files/publication.../acl09- > yesr.pdf> "The requested page "/sites/default/files/publication.../acl09- yesr.pdf" could not be found." Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Page for newbie/projects?
On Wed, 2016-01-20 at 13:07 -0800, Russell Uman wrote: > The "Easy" tag in Phabricator is one place to start if folks are > looking for simple tasks. https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker refers to https://www.mediawiki.org/wiki/Annoying_little_bugs which provides several queries per area for Phabricator tasks marked as "easy", instead of directly going to that long list in Phabricator. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Guidance regarding project
Hi! Thanks for your interest & welcome to the Wikimedia community! On Thu, 2016-03-10 at 20:55 +0530, Rupinder Kaur wrote: > I am Rupinderjit Kaur. I am pursuing B.Tech in Information Technology > from Guru Nanak Dev Engineering College, Ludhiana, India. I am 2016 > GSoC aspirant. I'm interested in contributing and working on the > project "Reading List" https://phabricator.wikimedia.org/T120756. > Kindly suggest me from where I should start contributing to it. Have you already checked https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#Coming_up_with_a_proposal and https://www.mediawiki.org/wiki/Google_Summer_of_Code_2016 ? If yes, could you specify which kind of suggestions you are looking for? Thanks! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Guidance regarding project
On Thu, 2016-03-10 at 23:29 +0530, Rupinder Kaur wrote: > On Thu, Mar 10, 2016 at 10:04 PM, Joaquin Oltra Hernandez wrote: > > I'd suggest starting by working on *Easy > > <https://phabricator.wikimedia.org/project/board/169/> *bugs and meanwhile > Where to find the code of any bugs which I choose to work on it. See https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker . It links to https://www.mediawiki.org/wiki/Gerrit/Tutorial which explains how to check out code repositories. To propose code changes in Gerrit, see https://www.mediawiki.org/wiki/Developer_access . Try to fix "easy" bugs: https://www.mediawiki.org/wiki/Annoying_little_bugs . > How do I get to know that certain project is not assigned to any > other student? See the "Assigned To" field in each Wikimedia Phabricator task. Happy hacking! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Improving Wikimedia's Code Review process
Hey everybody! At the Wikimedia Developer Summit there was a session about "Making Code Review not suck" [1]. The outcome are Phabricator (sub)tasks of the task "Define potential actions to reduce code review queues and waiting times" in https://phabricator.wikimedia.org/T101686 The following potential actions items have been identified: * https://phabricator.wikimedia.org/T129842 : Decide whether to have a "Code Review" committee / working group * https://phabricator.wikimedia.org/T129067 : Agree on and document a structured, standardized approach for reviewing code contributions * https://phabricator.wikimedia.org/T129068 : Improve code contribution guidelines for patch authors * https://phabricator.wikimedia.org/T128370 : Update ownership list on [[mw:Developers/Maintainers]] * https://phabricator.wikimedia.org/T128371 : Set up Code Review office hours * https://phabricator.wikimedia.org/T128372 : Document use of Owners in Phabricator and advertise it * https://phabricator.wikimedia.org/T115852 : Fix unclear maintenance responsibilities for some parts of MediaWiki core repository Discussion on each of those proposals is welcomed in the corresponding tasks! Thanks, andre [1] https://phabricator.wikimedia.org/T114419 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Guidance regarding project
Hi, On Thu, 2016-03-17 at 19:52 +0530, Rupinder Kaur wrote: > I did not find the description of this project > https://phabricator.wikimedia.org/T86106. Please tell me what is this? That specific task indeed misses information. I have commented on that task as it seems to be specific question about the task itself - see [1]. Cheers, andre [1] https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker#Feedback.2C_questions_and_support -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] RFC meeting (E148): Review backlog, Thumb API
On Wed, 2016-03-16 at 17:27 +0100, Daniel Kinzler wrote: > We plan to discuss two RFCs at the 2016-03-16 RFC Meeting [...] > * How to address the long tail of low priority tasks in active projects > <https://phabricator.wikimedia.org/T78639> > See also: > - Define potential actions to reduce code review queues and waiting times > <https://phabricator.wikimedia.org/T101686> > - Make code review not suck > <https://phabricator.wikimedia.org/T114419> The title of the RfC meeting says "review backlog". Assuming this refers to code/patches and not tasks/bug reports, in my understanding the linked task only refers to the latter - see https://phabricator.wikimedia.org/T78639#1910641 . The task for potential actions to improve Wikimedia's Code Review process is actually https://phabricator.wikimedia.org/T101686 See its sub-tasks under "Blocked By". The proposed actions/sub-tasks are based on the Developer summit session outcome in https://phabricator.wikimedia.org/T114419 Also see yesterday's email here, listing those sub-tasks: https://lists. wikimedia.org/pipermail/wikitech-l/2016-March/085042.html The follow-up task to agree and implement those actions is https://phabricator.wikimedia.org/T78768 Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reply： [GSoC 2016] Query about the ideas' project time
On Tue, 2016-03-22 at 02:14 +0800, DJAKN wrote: > Thank you for your reply. I have read the instruction and the blog of > this project and have some ideas now. But there appears another > question: What does the "reputation score" in the description refer > to? Should we design it and make some metrics, or just use the > existed scoring standard? That seems to be a specific question about the proposed task. Maybe the potential mentor (jsalsman) will reply here, but you might have more luck asking task-related questions [1] on the task itself: https://phabricator.wikimedia.org/T89416 Cheers, andre [1] Also see https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker#Feedback.2C_questions_and_support -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [GSoC 2016] Query about the ideas' project time
Hi, thanks for your interest and welcome to Wikimedia! :) On Mon, 2016-03-21 at 20:58 +0800, DJAKN wrote: > I am interested in the "Accuracy Review" project, but there is a note > saying the estimated time for a senior contributor is 3 weeks. Other > projects in the idea list have the similar estimated time. So should > we complete more than one project during the three-month internship > or just one? It's only one. "3 weeks for senior contributors" is meant to provide a rough idea / ballpark figure to mentors how big a project is supposed to be. For general information about Wikimedia in GSoC 2016, please see https://www.mediawiki.org/wiki/Google_Summer_of_Code_2016 Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Heads-up: "Write The Docs" conference in Sep 2016
For those interested + working on Wikimedia documentation: There is a conf in Prague (Czech Rep) on Sep 18-20 "to explore the art and science of documentation" for "writers, developers, support folks". See http://www.writethedocs.org/conf/eu/2016 for more information. There is https://meta.wikimedia.org/wiki/Grants which could be helpful when it comes to supporting travelling. I haven't attended the event myself but I've heard good stuff about it. :) Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Google Summer of Code 2016 and Outreachy results out, Congrats interns
On Sat, 2016-04-23 at 13:44 +0530, Tony Thomas wrote: > The best approach would be to open up a Conpherence with your mentors > ( I hope they appreciate it ), and asking the same. If you do not find any > lucky with that, kindly ping or add in the org-admins too, and we will > get this resolved. For those wondering: "Conpherence" is the name of the discussion tool in Wikimedia Phabricator. It allows private conversations. See https://www.mediawiki.org/wiki/Phabricator/Help#Using_Conpherence Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia Git/Gerrit/Code Review technical documentation updates
[For your info] I've spend some time in the last weeks rewriting and cleaning up our technical Git / Gerrit / Code Review documentation on mediawiki.org. 135 edits later, things feel a bit cleaner. :) === Changes === There is a central Git/Gerrit "Troubleshooting" page linked from the most relevant pages, instead of separate sections on three or four different pages which partially duplicated content (setting up Git and Gerrit on different operating systems had similar problems and missing central information). Some rather specific subpages were merged into existing pages (e.g. into "Gerrit/Advanced usage"). The entrance page https://www.mediawiki.org/wiki/Gerrit has a "Prerequisites" section and the sections are now structured by usecase / type of user. Some "too much detail" content was also removed (like the history of the Git and Gerrit software; you can check Wikipedia as it's irrelevant if you want just to get your patch done). Full list of changes: https://phabricator.wikimedia.org/T134256#2317711 === No changes === Some stuff I did not touch (as perfect is the enemy of good). For example, I'm still wondering about the role of https://www.mediawiki.org/wiki/Git_for_dummies compared to https://www.mediawiki.org/wiki/Gerrit/Getting_started and https://www.mediawiki.org/wiki/Gerrit/Tutorial . Plus I still consider the screenshots of command line text output distractive on https://www.mediawiki.org/wiki/Gerrit/Tutorial . === Thank you === Thank you a lot to everybody who provided feedback, answers to my Gerrit questions, and helped editing those pages! === Next steps === After this technical documentation exercise, the next steps will focus on soft / social+organizational aspects of code review: * https://phabricator.wikimedia.org/T129068 Improve code contribution guidelines for patch authors by fixing https://www.mediawiki.org/wiki/Gerrit/Code_review/Getting_reviews etc * https://phabricator.wikimedia.org/T129067 Agree on + document a structured, standardized approach for reviewing code contributions by fixing https://www.mediawiki.org/wiki/Gerrit/Code_review etc. Needless to say, your help is very welcome. More information to come soon. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Proposal to invest in Phabricator Calendar
On Sat, 2016-05-14 at 20:51 +0200, Ricordisamoa wrote: > If we're going to be investing money into improving Phabricator > upstream, I think we should start with making Differential usable > (i.e. a suitable replacement for Gerrit) If you have *specific* issues, please point them out by linking to tasks. "Usable" is too subjective to be a basis for discussions. Thanks! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator upgrade and UI changes
Hej, On Wed, 2016-05-04 at 17:57 +0200, Federico Leva (Nemo) wrote: > It would also be nice to have some precise and authoritative information > on when Phabricator was upgrade to what version, what the release notes > and gotchas are, etc. Did I miss such an announcement and if yes where > is it? Upgrades happen in the weekly Phab maintenance window (Thu -0100UTC): https://www.mediawiki.org/wiki/Phabricator/Maintenance The latest upgrade was on Thu April 28th: https://phabricator.wikimedia.org/T128009 The next upgrade is tracked in https://phabricator.wikimedia.org/T133820 Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] "Troubleshooting Git/Gerrit/git-review" docs: Help welcome.
On Wed, 2016-05-04 at 23:28 -0500, Andrew Bogott wrote: > On 5/4/16 8:59 AM, Andre Klapper wrote: > > https://www.mediawiki.org/wiki/Gerrit/Troubleshooting > > Although technically correct, some of those instructions encourage users > to use 'git pull.' Git doc writers, please join me in my crusade to > stop gerrit users from ever, ever using 'git pull.' Please be bold and edit. I'm certainly not an advanced Git user; I just want the learning curve for new contributors to be less steep. > Thank you for compiling these docs! Nah. I just moved, restructured + cleaned up content a bit. :) If anyone feels like joining the Git/Gerrit doc cleanup efforts: I have dumped an incomplete "stuff to do" list in https://phabricator.wikimedia.org/T134256#2260631 for ideas. For example, I'd love to kill [[mw:Git/Tips]] + [[mw:Git/Rebase]] as we already have a Tutorial, an FAQ, Advanced usage, Getting started, ... Thanks! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] "Troubleshooting Git/Gerrit/git-review" docs: Help welcome.
Hej, I went ahead & centralized the 5 git/Gerrit/git-review troubleshooting sections that I've found so far on random mediawiki.org pages into one single page (and eliminated duplicates with different solutions): https://www.mediawiki.org/wiki/Gerrit/Troubleshooting 1) More help is welcome to clean up and structure that page (plain git vs. git-review vs. Gerrit UI). 2) As a user, I prefer section headings to describe problems instead of solutions (as I don't know which solution is related to my problem). On https://www.mediawiki.org/wiki/Gerrit/Tutorial there is one section called "Pushing via HTTPS when SSH is not functional" which I'd also like to move to [[mw:Gerrit/Troubleshooting]]. Anyone knows how users would actually realize that SSH is not functional? (Specific output after a specific command?) How would Gerrit users realize they are behind a proxy server? Thanks for your help. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Diff algorithms: the shootout
On Fri, 2016-04-15 at 21:00 -0500, MZMcBride wrote: > Max Semenik wrote: > > > > Right now, MediaWiki has 2 pure-PHP engines to produce diffs (there's also > > a native PHP extension wikidiff2, but we're not discussing it right now): > > * DairikiDiff is what everybody uses, and > > * Wikidiff3, and alternative implementation by Guy Van den Broeck that was > > around for 8 years but required a configuration change > > While less battle-tested, Wikidiff3 offers vastly improved performance on > > heavy diffs compared to DairikiDiff. The price, however, is that it makes > > certain shortcuts if the diff is too complex. I ran through 100K diffs > > from English Wikipedia, and 6% of diffs were different. Lots of changes > > were seemingly insignificant but I need your help with determining if > > it's really so. > Is there a related Phabricator Maniphest task about this? I'm not sure I > understand the motivation for making a switch. I would think that heavy > diffs are a very small portion of traffic. https://phabricator.wikimedia.org/T128896 looks related. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Image cannot be deleted
On Thu, 2016-07-28 at 17:25 +0200, Bináris wrote: > This is the file: > https://hu.wikipedia.org/wiki/F%C3%A1jl:Pesti_szerb_templom_3.jpg > > Four admins have tried to delete it unsuccessfully. Message: > Hiba a fájl törlésekor: Nem sikerült törölni ezt a fájlt: > mwstore://local-swift-eqiad/local- > public/d/d8/Pesti_szerb_templom_3.jpg . > *(Error while deleting file. Couldn't delete file:)* Please report the software issue at https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=media-storage by following https://www.mediawiki.org/wiki/How_to_report_a_bug Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Ops] [Engineering] The train will resume tomorrow (was Re: All wikis reverted to wmf.8 last night due to T119736)
On Tue, 2016-07-12 at 20:15 -0400, aude wrote: > This (unbreak now) bug has been open since November. I wonder how > this has been allowed to remain open and not addressed for this long? FYI, Matt created a task about "Unbreak now" priority, to receive input from Team-Practices: https://phabricator.wikimedia.org/T140207 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Contribute to Wikimedia Foundation
On Wed, 2017-01-25 at 19:00 +0530, Nethmi Pathirana wrote: > I am Nethmi Pathirana, a 3rd year undergraduate from the Department of > Computer Science and Engineering, University of Moratuwa. > > I am very interested in supporting your vision of sharing the knowledge > freely around the world. I would like to support that by contributing to > Media wiki as a developer. Can some one guide me on more specifics about > contributing to media wiki and where I can find some beginner tasks/issues > which I can try. Hi Nethmi, thanks for your interest! Please see https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker for more information and links to potential tasks to start with. Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] PHP fatal error: Call to undefined method stdClass::get()
On Wed, 2017-01-11 at 11:36 -0800, Pine W wrote: > I just started getting a lot of these errors when trying to load > pages on multiple Wikimedia sites. If you'd like to report a software bug, Phabricator is the best place: https://www.mediawiki.org/wiki/How_to_report_a_bug If a bug is urgent, #wikimedia-tech on Freenode IRC is the best place: https://www.mediawiki.org/wiki/MediaWiki_on_IRC Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Google Code-in 2016 is over. Congratulations everybody!
Google Code-in 2016 ended today.
Our students resolved a total of 424 Wikimedia tasks. Thanks to our 46
mentors for being available, also on weekends & holidays. Thanks to
everybody on IRC for your friendliness, patience, and help provided.
Some latest students' achievements:
* jQuery.suggestions used to add reason suggestions to block/delete/protect
forms
* Created a {{PAGELANGUAGE}} magic word
* The Newsletter extension received more fixes and improvements
* Integrated SwaggerUI with the service template
* Special:PageLanguage allows a user to enter a reason/comment
* More MediaWiki code removed that was marked for removal in a past release
* More updated screencast videos on the Phabricator help pages
* More split videos of Wikimedia's CREDIT showcases
*
https://meta.wikimedia.org/wiki/Research_on_open_source_team_communication_tools
The Grand Prize winners & finalists will be announced on January 30th.
Do you have any ideas or feedback what to improve for next time?
Add it to https://phabricator.wikimedia.org/T154620 !
Again congratulations everybody, and thanks for your hard work!
See you around on IRC, mailing lists, Gerrit, and Phabricator!
Cheers,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia is participating in Google Summer of Code 2017. Interested in being a mentor?
On Tue, 2017-02-28 at 11:19 -0800, Pine W wrote: > If I may promote some projects that would be nice to go along with the > LearnWiki project and improving the new user experience in general: For those projects not ready to be mentored, please feel free to either mentor these tasks yourself or to contact potential mentors. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator monthly statistics - 2017-02
On Wed, 2017-03-01 at 00:22 +, Dan Garry wrote: > 17226 days ago was 1st January 1970 > <https://en.wikipedia.org/wiki/Unix_time>, naturally. :-) Good catch. I filed https://phabricator.wikimedia.org/T159314 If someone has some SQL skills to share, a patch is very welcome! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia is participating in Google Summer of Code 2017. Interested in being a mentor?
On Wed, 2017-03-01 at 05:32 -0800, James Hare wrote: > I just had an idea. My bot Reports Bot is always in need of updates > and minor maintenance, and I think GSOC could be good for people > interested in working in Python. But I don't want to propose > something if it would be too much work for the person doing it. Is > there guidance on how complex/major these tasks and projects can or > should be? https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project says that "A good internship project should take about two weeks for a senior developer to complete." If that time frame is not already mentioned in https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#For_possible_mentors please feel very free to edit / add. :) Thanks!, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Hph de Wikipedia
Hi, On Wed, 2017-03-01 at 08:00 -0500, Michael Junior Obregon Pozo wrote: > Quisiera saber cómo conseguir un archivo hph de una Wikipedia > existente Did you mean PHP? If you meant HPH, can you explain what it is? In any case: Can you explain what exactly you want to do and why? Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Introduction for Gsoc 2017
On Wed, 2016-08-24 at 22:39 +0530, MAYANK JINDAL wrote: > My name is Mayank Jindal. I am third year undergraduate student > currently studying at Indian Institute of Technology, Kharagpur. I > want to take part in Gsoc-2017 from Wikimedia. > I have knowledge of C, C++, JAVA, Python, Android app development and > Web development and beginner in *Machine Learning, Artificial > Intelligence.* > I am very enthusiastic to learn new skills which would be required. Thanks for your early interest. Glad to hear you'd like to get involved! Regarding machine learning, https://meta.wikimedia.org/wiki/Objective_Revision_Evaluation_Service might be interesting? https://meta.wikimedia.org/wiki/Research:Revision_scoring_as_a_service lists mailing list and IRC channel contact information. We don't have any information about GSoC 2017 yet but you could get an impression by looking at the page for GSoC 2016 at https://www.mediawiki.org/wiki/Google_Summer_of_Code_2016 and https://www.mediawiki.org/wiki/Outreach_programs for general info on workflows and expectations for GSoC, Outreachy and other programs. About technical contributions in general, have you taken a look at https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker already? It explains how to set up your testing environment, how to find good "easy" tasks to start with, how to check out code via Git, how to submit patches via Gerrit, recommendations for communication, and best places where to ask any questions you might have. Hope that helps for the start? If not, tell us! Looking forward to your contributions! :) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Google Summer of Code
Hi, On Thu, 2016-09-08 at 14:13 +0700, Arif Hidayat wrote: > I am Arif Hidayat from UIN Sultan Syarif Kasim Riau, Pekanbaru. I've learn > about cms. I so interest about developing cms especially mediawiki. > My favorite programming language is php but I can use java programming and > other component of website like css and js. > I hope can submit my google summer of code proposal to mediawiki project. > Thanks Thanks for your early interest. Glad to hear you'd like to get involved! We don't have any information about GSoC 2017 yet but you could get an impression by looking at the page for GSoC 2016 at https://www.mediawiki.org/wiki/Google_Summer_of_Code_2016 and https://www.mediawiki.org/wiki/Outreach_programs for general info on workflows and expectations for GSoC, Outreachy and other programs. About technical contributions in general, have you taken a look at https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker already? It explains how to set up your testing environment, how to find good "easy" tasks to start with, how to check out code via Git, how to submit patches via Gerrit, recommendations for communication, and best places where to ask any questions you might have. Hope that helps for the start? If not, tell us! Looking forward to your contributions! :) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Introduction
Hi Taufik, Thanks for your early interest. Glad to hear you'd like to get involved! On Thu, 2016-09-08 at 14:29 +0700, Taufik Hidayat wrote: > I'd love to do submit proposal for google summer of code 2017 in wikimedia > foundation about "Automatic Summarization of Articles" i found on this link > https://phabricator.wikimedia.org/T127038. > i hope you can share advice or what should i do or prepare, and which > idea(s) that's a good fit for my skills. thank you very much in advance. Please check out my reply to a similar request on this mailing list at https://lists.wikimedia.org/pipermail/wikitech-l/2016-September/086482.html Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] google summer of code
Hi Harisandy, Thanks for your early interest. Glad to hear you'd like to get involved! On Thu, 2016-09-08 at 14:31 +0700, Mhs TEKNIK INFORMATIKA Harisandy wrote: > I harisandy . student uin Suska Riau > I am a programmer at PT . Sela Express Tour , I have the ability in the > field of java desktop and CodeIgniter PHP framework , Yii , laravel . > Here I am interested in several projects in the offer google , I hope > google can respond to my request . thank you Please check out my reply to a similar request on this mailing list at https://lists.wikimedia.org/pipermail/wikitech-l/2016-September/086482.html Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Recently proposed patchsets by new contributors awaiting code review
Your help is welcome to provide feedback and guidance: == All in "mediawiki/core": == since 2016-08-01: Incorrect redirect for titles starting with '/' in special cases https://gerrit.wikimedia.org/r/#/c/302088/ since 2016-08-02: Fix to incorrect calls of header () breaking saving some pages and login https://gerrit.wikimedia.org/r/#/c/302430/ since 2016-08-11: Change wording, change grammar in lang/en.json https://gerrit.wikimedia.org/r/#/c/304329/ since 2016-08-11: Cleaned up some unneeded wording in the english lang file, as well as minor wording changes. https://gerrit.wikimedia.org/r/#/c/302061/ since 2016-08-11: Add Localisation to the links, add the link to Localisation in Languages/Language.php https://gerrit.wikimedia.org/r/#/c/304153/ Thanks in advance for your reviews. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Memento MediaWiki Extension at the W3C
On Mon, 2016-09-12 at 11:57 -0600, Shawn Jones wrote: > We appreciate the help received from this list during the development of > the Memento MediaWiki Extension [1]. > [1] https://www.mediawiki.org/wiki/Extension:Memento Interesting, hadn't heard of that. https://www.mediawiki.org/wiki/Extension:Memento#Usage states that the "best way to experience this extension is by installing Memento Time Travel for the Chrome browser." Is the source code of the Chrome extension available? (I didn't spot in on https://github.com/mementoweb ). Also, under which license is it? Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia Developer Summit 2017 discussion
On Tue, 2016-09-27 at 14:23 -0700, Info WorldUniversity wrote: > Is there a current (curated) summary of all the good suggestions for > WikiDev themes, and structuring of conference If I get the question correctly that's likely https://www.mediawiki.org/wiki/Talk:Wikimedia_Developer_Summit For the structure, see last year's schedule on https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016 Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Code of Conduct
On Wed, 2016-09-28 at 11:07 +, Steinsplitter Wiki wrote: > I noticed that a Code of Conduct for Phabricator is getting > developed. Cool to see that people are creating such a policy, it is > standard yet in big other projects. :-) A Code of Conduct for Wikimedia's technical spaces is being developed; Phabricator is one of those technical spaces. > Unfortunately, the whole Code of Conduct Voting hasn't been widely > announced (just on phabricator). [...] Such a important decision > should be widely announced imho. To reach more people like you, what would be the best place to post messages so you'd see them? andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
