The Gareth code review project has been steadily moving forward.
I've settled on Python+Django for the project.
It's still not ready to start doing actual code review. But a number of
key pieces are already implemented:
- The whole view/template/theme system is ready
- A git layer has been implemented and new git commands are fairly easy to
add (depending on the command's complexity)
- Project and remote handling is ready
- The low level git remote fetch implementation is ready (still needs a
queue and websockets though to get the ui for it working)
- Remote pages already understand what commits have not yet been added to
the repo or a head
I also have commit lists and commit pages ready. I'm currently working on
diffs ( ;) And I mean diffs better than Gerrit, GitHub, or anything else)
which will likely finally lead into review pages.
Since the project has been going fairly seriously I've setup a website for
the project:
http://gareth-review.com/
I've put the latest screenshots up:
http://gareth-review.com/screenshots.html
And a blog is up and you can subscribe to updates on the project's
progress:
http://gareth-review.com/blog/
--
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
Hi everyone,
Firstly, thanks to all Mentors and Sumana for accepting my GSOC proposal.
It has been a pleasure working with the Wikimedia and SMW community so far
for me and I look forward to an awesome summer.
Secondly, Markus and I have started working on the project. We have made
some priority assignments to our goals and as per that we will be making
some changes to the Database access code(make it cleaner) first and than
look into other performance degradation issues. While we do the first part
feedback/ideas/suggestions on performance degradation issues with SMW are
most welcomed. Most of the ideas we discussed has been documented at
SQLStore_Update <http://semantic-mediawiki.org/wiki/SQLStore_Update>.
I am also maintaining a blog <http://greenswm.wordpress.com> specifically
for this project; I write most of my activities there. Comments/feedback
are most welcomed on my blog <http://greenswm.wordpress.com/> or on the
project talk-page
Nischayn22/Gsoc<https://www.mediawiki.org/wiki/User_talk:Nischayn22/Gsoc>
Thanks
--
Nischay Nahata
B.tech 3rd year
Department of Information Technology
NITK,Surathkal
In the Wikimedia wikis, right now, we succeed to a varied degree at
letting communities know about deployments that affect them. We're
definitely getting better, and the 1.20wmf1 page is an example of
release notes done well:
http://www.mediawiki.org/wiki/MediaWiki_1.20/wmf1http://www.mediawiki.org/wiki/MediaWiki_1.20/wmf1/overview
A concise summary with translations in multiple languages, followed by
a detailed list compiled from manually collected and curated commit
summaries. Nifty. And so much work that it's unlikely to be
sustainable. Indeed with wmf2 we're already taking shortcuts:
http://www.mediawiki.org/wiki/MediaWiki_1.20/wmf2
No translations, no overview, less curation. And let's keep in mind
that this covers only the "regular two week cycle" deployment -- major
changes deployed between cycles aren't covered in either of those
summaries.
So how can we do better? I'd posit that it should be impossible to
deploy code without leaving an exposed audit trail generated from
commit messages, which can in turn be expanded by any interested
volunteer into a human-readable and translated summary.
I'd suggest exposing this information to a special page directly in
the relevant wiki, say "Special:SiteChanges". This special page would
show an automatically generated summary like so:
<example>
== Wednesday May 2, 19:03 ==
(2 hours ago)
'''[[mw:WMF deployments/345|Write or translate a deployment summary]]'''
Deployment 345 completed. The following changes are now running on this wiki.
=== In core ===
* ca7eb5c - Removed intval for undelete reason in API - ''committed by
Petr Onderka''
* 5813680 - Few documentation/type hint updates - ''committed by Reedy''
* e22a369 - Prevent sidebar links from jumping on page load -
''committed by Trevor Parscal'
...
=== In extension FlaggedRevs ===
* ce146dc - Fixing up LSB related stuff.. Some code duplication, but
meh for the moment (yay for us using static classes for hooks)
=== In extension DynamicPageList ===
..
== Tuesday, May 1, 15:01 ==
(1 day ago)
...
</example>
I leave it up to your imagination whether the summary would be
generated from the git repo the wiki resides in (in combination with a
deployment log), or pulled from MediaWiki.org, some combination
thereof, or some other implementation strategy. Suffice it to say that
we'd ideally want to:
* Ensure that the process of recording this information is an
automated part of deploying code updates
* Filter extensions from the Special:SiteChanges summary that are not
actually activated
* Notice when new extensions are activated that were not active in a
previous state
* Enable anyone to write deployment summaries on MediaWiki.org
* Enable anyone to translate those summaries
* Load an existing summary in the correct language on Special:SiteChanges
In the magical database backed configuration future,
Special:SiteChanges might also be able to list out config changes, but
that seems far fetched right now
In the equally magical "notifications for everything" future, users
would be able to opt into getting notified whenever a deployment
occurs.
But keeping it at a base level of functionality, does this seem like a
feasible and desirable change? Like I said, I worry about our ability
to keep up without automating this whole process, so IMO it would be
good to incrementally start building out this functionality. Otherwise
we're constantly fighting an uphill battle to ensure information gets
disseminated in a consistent fashion. But it's possible I'm
overlooking major issues that would make this too difficult to be
worthwhile.
All best,
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
Some Wikimedia developers have requested help improving their English
writing skills. Erika Hanson is volunteering her proofreading skills to
help by leading interactive proofreading sessions -- we ran a pilot
today and it was successful enough that we'll do another one next weekend.
Participants paste what they've written into the Etherpad
http://notes.wikimediadc.org/p/english-lessons by Thursday night, so
Erika has time to read it and mark problem areas in boldface. Then,
during the tutorial session, Erika gives the learner lessons in
spelling, grammar, punctuation, etc., for about 15 minutes per student.
If she has time in the 15 min., she'll then move on to matters of
style. Discussion can be within the Etherpad chat.
If you want to participate, email Erika (cc'd) with the date/times that
you can attend (your 2 choices are below - I don't know whether Erika
can do both times or just the more popular 1), and put something you've
written into the Etherpad by the end of Thursday. It should be at least
200 words long -- blog entry, email, school essay, whatever.
ALBUQUERQUE, 1:30pm-3:30pm , Sat, May 5 2012
UTC, 19:30-21:30 Sat, May 5 2012
AMSTERDAM, 21:30-23:30 Sat, May 5 2012
MUMBAI, 1am-3am Sun, May 6 2012
or
ALBUQUERQUE, 10am-noon, Sun, May 6 2012
MUMBAI, 9:30pm-11:30pm, Sun, May 6 2012
UTC, 16:00-18:00, Sun, May 6 2012
AMSTERDAM, 18:00-20:00, Sun, May 6 2012
If people learn effectively from this, then we could repeat it.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Hi,
Ryan and I upgraded our Gerrit install to 2.3 today. This release
brings lots of fixes and various other improvements. The big feature
we're using in 2.3 is called "submodule subscriptions" which I've
already deployed for our extensions.
To check out all extensions in Gerrit, you can now do the following:
$ git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions.git
$ cd extensions
$ git submodule update --init
To update the extensions to their latest versions, just do this:
$ cd /path/to/extensions
$ git pull
$ git submodule update --init
I hope you all enjoy the new version of Gerrit. Please let me know if
you find any regressions.
-Chad
Wow,
Thanks Steph, Maggie, Subhashish, Alollita, Joslyn, Mani, Victor, Barry,
Ayush and Rachel! And I thought nobody reads these mails :)
On Fri, May 4, 2012 at 1:38 AM, Rachel Farrand <rfarrand(a)wikimedia.org>wrote:
> Yay Arun! It was great to meet you in Pune and I am glad that you have
> finally officially joined up!
>
>
> On Thu, May 3, 2012 at 10:57 AM, Ayush Khanna <akhanna(a)wikimedia.org>wrote:
>
>> Welcome!
>>
>> Also, the MTC project sounds very interesting. As some who was heavily
>> reliant on public transport back in Mumbai, I can imagine how helpful that
>> would be.
>>
>> Ayush Khanna
>> Data Analyst, Global Development
>> Wikimedia Foundation
>> 415.839.6885 x6805
>>
>>
>>
>>
>> On Thu, May 3, 2012 at 10:22 AM, Barry Newstead (WMF) <
>> bnewstead(a)wikimedia.org> wrote:
>>
>>> Welcome Arun. It was a nice surprise to meet you in person at CIS in
>>> Bangalore on Sunday. Great to have you onboard.
>>> Best,
>>> Barry
>>>
>>> --
>>> Barry Newstead
>>> Chief Global Development Officer
>>> Wikimedia Foundation
>>>
>>> On Thursday, May 3, 2012 at 10:19 AM, Victor Grigas wrote:
>>>
>>> ARUN!!! I'm happy you are on board! You are perfect for our team :)
>>>
>>> On Thu, May 3, 2012 at 8:38 AM, Mani Pande <mpande(a)wikimedia.org> wrote:
>>>
>>> Welcome aboard.!!
>>>
>>>
>>> On Thu, May 3, 2012 at 8:12 AM, asharma(a)wikimedia.org <
>>> asharma(a)wikimedia.org> wrote:
>>>
>>> Hi Arun,
>>>
>>> A very warm welcome to you on the I18n/L10N engineering team. We are
>>> excited about the Universal Language Selector UI/UX work that you and Pau
>>> are helping us with.
>>>
>>> Happy to see you onboard!
>>>
>>> Alolita
>>>
>>> __
>>> Alolita Sharma
>>> Wikimedia Foundation
>>>
>>>
>>> ----- Reply message -----
>>> From: "Subhashish Panigrahi" <subha(a)wikimedia.org>
>>> To:
>>> Cc: <wikitech-l(a)lists.wikimedia.org>, <wmfall(a)lists.wikimedia.org>,
>>> "Arun Ganesh" <arun.planemad(a)gmail.com>
>>> Subject: [Wmfall] Introduction - Arun
>>> Date: Thu, May 3, 2012 6:55 am
>>>
>>>
>>> Congratulations Arun!
>>>
>>> Happy that I met you a month back, now the L10n have more people from
>>> Indic
>>> communities and it makes me happier again ;-)
>>>
>>> On Thu, May 3, 2012 at 7:17 PM, Maggie Dennis <mdennis(a)wikimedia.org>
>>> wrote:
>>>
>>> > Welcome, Arun! Somehow I feel sure that you are in for an interesting
>>> > ride. :D
>>> >
>>> > Maggie
>>> >
>>> > On Thu, May 3, 2012 at 9:16 AM, Arun Ganesh <arun.planemad(a)gmail.com
>>> >wrote:
>>> >
>>> >> Hi everyone,
>>> >> I wanted to introduce myself to the community and the WMF team, I'm
>>> Arun
>>> >> Ganesh (user:planemad)[1a] from Bangalore, India and have joined as
>>> >> contractor for the foundation's L10n team[1b] as an Interaction
>>> designer
>>> >> along with Pau to improve the user experience of language tools and
>>> >> features.
>>> >>
>>> >> I have been a longtime contributer to both commons[2] and the
>>> >> openstreetmap[3] project and got involved with foundation work during
>>> the
>>> >> Mumbai and Pune hackathons recently[4][5][6] where I proposed some of
>>> the
>>> >> first ideas for the Universal Language Selector widget with Brandon,
>>> with
>>> >> which we want to make language selection for anyone easy peasy.
>>> >>
>>> >> Apart from that, I love cartography and maps [7], which would explain
>>> my
>>> >> map contributions and the occasional headline for wikipedia [8], use
>>> only
>>> >> public transport[9] and traveling with my pocket camera[10].
>>> >>
>>> >> Its feels great to have this opportunity to work more seriously on a
>>> >> project which has been an important part of my life. I'm new here, I
>>> wont
>>> >> claim to know much, but I hope to make a difference in whichever way
>>> >> possible. I also look forward to interacting more closely and
>>> learning from
>>> >> the rest of the designers - Brandon, Heather and Pau to do the
>>> wonderful
>>> >> things that designers like to do .So keep the usability bugs coming :)
>>> >> -Arun
>>> >>
>>> >> [1a] http://en.wikipedia.org/wiki/User:Planemad
>>> >> [1b] http://wikimediafoundation.org/wiki/Localization_team
>>> >> [2]
>>> >>
>>> http://tools.wikimedia.de/~daniel/WikiSense/Gallery.php?&wiki=commons.wikim…
>>> >> [3]
>>> >>
>>> http://yosmhm.neis-one.org/?zoom=4&lat=21.96627&lon=81.68268&layers=B0T&u=P…
>>> >> [4]
>>> >>
>>> http://www.mediawiki.org/wiki/Universal_Language_Selector#Arun_Ganesh.27s_O…
>>> >> [5]
>>> http://commons.wikimedia.org/wiki/File:Mobile_language_selector.pdf
>>> >> [6]
>>> >>
>>> http://commons.wikimedia.org/wiki/File:L10n-ux-Universal_Language_Selector-…
>>> >> [7] http://bit.ly/timesofindia-osm
>>> >> [8]
>>> >>
>>> http://www.guardian.co.uk/news/datablog/2010/jul/30/information-beautiful-i…
>>> >> [9]
>>> >>
>>> http://www.thehindu.com/todays-paper/tp-national/tp-tamilnadu/article182223…
>>> >> [10] http://www.time.com/time/world/article/0,8599,1663025,00.html
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> Wmfall mailing list
>>> >> Wmfall(a)lists.wikimedia.org
>>> >> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > Maggie Dennis
>>> > Community Liaison
>>> > WikimediaFoundation.org
>>> >
>>> >
>>> > _______________________________________________
>>> > Wmfall mailing list
>>> > Wmfall(a)lists.wikimedia.org
>>> > https://lists.wikimedia.org/mailman/listinfo/wmfall
>>> >
>>> >
>>>
>>>
>>> --
>>> *Subha*
>>>
>>>
>>> *Imagine a world in which every single human being can freely share in
>>> the
>>> sum of all knowledge. Help us make it a reality!*
>>>
>>> _______________________________________________
>>> Wmfall mailing list
>>> Wmfall(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>>
>>>
>>>
>>>
>>> --
>>> Mani Pande, PhD
>>> Head of Global Development Research
>>> Twitter: manipande Skype: manipande
>>>
>>>
>>> _______________________________________________
>>> Wmfall mailing list
>>> Wmfall(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>>
>>>
>>>
>>>
>>> --
>>> *Victor Grigas*
>>> Storyteller
>>> *Wikimedia Foundation*
>>> vgrigas(a)wikimedia.org
>>> +1 (415) 839-6885 x 6773
>>> 149 New Montgomery Street 6th floor
>>> San Francisco, CA 94105
>>> <http://wikimediafoundation.org/w/index.php?title=WMFJA085/en/US&utm_source=…>
>>>
>>>
>>>
>>> _______________________________________________
>>> Wmfall mailing list
>>> Wmfall(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>>
>>>
>>>
>>> _______________________________________________
>>> Wmfall mailing list
>>> Wmfall(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>>
>>>
>>
>> _______________________________________________
>> Wmfall mailing list
>> Wmfall(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>
>>
>
--
j.mp/ArunGanesh
Not 100% for us, but important to know / to whom it may concern:
http://www.h-online.com/open/news/item/Critical-open-hole-in-PHP-creates-ri…
Critical open hole in PHP creates risks
The US CERT is warning of a critical vulnerability in PHP which has been
disclosed, by mistake, to the public while the developers are still
working on a fix. The vulnerability affect servers that are running PHP
in CGI mode; FastCGI for PHP installations are not affected.
** Keine Antwort erforderlich ** no reply needed **