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/
Hiya,
We’ll be upgrading the Analytics Kafka cluster from 0.8.2 to 0.9.0.1 next
week. This is scheduled to start at Wednesday May 11th at 13:00 UTC (9:00
EST, 6:00 PST).
If all goes well*, this should be a rolling upgrade with no downtime.
Just a heads up, thanks!
-Andrew & Luca
*everybody knock on wood now
Forwarding.
Pine
---------- Forwarded message ----------
From: "Katherine Maher" <kmaher(a)wikimedia.org>
Date: May 4, 2016 17:47
Subject: [Wikimedia-l] Invitation to upcoming office hours with interim ED
To: <wikimedia-l(a)lists.wikimedia.org>, <wmfall(a)lists.wikimedia.org>, <
wikimediaannounce-l(a)lists.wikimedia.org>
Cc:
Hi everyone,
**Summary: I am delighted to invite you to join me for two upcoming office
hours, where I’ll answer community questions and share updates on the
Foundation’s work.**
It’s been a busy few weeks around the Wikimedia Foundation offices. We
shared our 2016-2017 annual plan, finished our quarterly reviews, and
attended Wikimedia Conference 2016 in Berlin with the Wikimedia affiliates.
[1]
In Berlin, I had the chance to do one of my favorite things: sit with
Wikimedians, listen, debate, and plan for the future. Of course, Berlin is
just one gathering, and there are thousands of other perspectives out
there. I want to hear more of these perspectives, and so I’m looking
forward to hosting two office hours over the coming weeks.
We plan to hold a traditional office hours on IRC, and will also experiment
with a video Q&A. We hope these different formats will make it easier for
more people to participate using their preferred communications channels.
We’ve chosen two different time zones, with the goal of reaching as many
people as possible. They are as follows:
*Video session*
*This session will be recorded, and the video will be posted on
Commons/Meta. Due to video conferencing limitations, we encourage advance
questions.*
Wednesday, 11 May 2016
00:00-1:00 UTC | 17:00-18:00 PDT [2]
*IRC session*
*This session follows the May monthly metrics meeting.[4] Like other office
hours, it will be held in #Wikimedia-office on Freenode.*
Thursday, 26 May 2016
19:00-20:00 UTC | 12:00-13:00 PDT [3]
We’re also collecting questions in advance for those who can’t make either
of those sessions. We’ve created a page on Meta where you can leave
questions or comments, check the details on the location of each session:
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Executive_Director/May…
Please share this invitation with others you think may be interested!
I look forward to speaking soon,
Katherine
Translation notice - This message is available for translation on
Meta-Wiki:
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Executive_Director/May…
[1] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2016
[2] Time converter link:
http://www.timeanddate.com/worldclock/fixedtime.html?hour=0&min=00&sec=0&da…
[3] Time converter link:
http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=00&sec=0&d…
[4] https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings
--
Katherine Maher
Wikimedia Foundation
149 New Montgomery Street
San Francisco, CA 94105
+1 (415) 839-6885 ext. 6635
+1 (415) 712 4873
kmaher(a)wikimedia.org
_______________________________________________
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
Hi everyone,
I've included the ArchCom-RFC status update in this mail below, which now
has a dedicated wiki page:
<https://www.mediawiki.org/wiki/Architecture_committee/Status>
Assuming we build the habit, this should be updated weekly.
Rob
----
Recent RFC office hours
- 2016-05-04: Phab:E169
- T130528: RFC: PSR-6 Cache interface in Mediawiki core
- Declined. A lot of the discussion was about these three
questions:
1. what problem was this RFC trying to solve?
2. if BagOStuff is an obstacle, then which is true?
- a) need a better caching abstraction than BagOStuff?
or
- b) does BagOStuff just need incremental improvement
- c) should BagOStuff be deprecated, and not replaced
with anything?
3. if we decide to rethink our caching model, do we need
tagged caching?
Upcoming RFC office hours
- 2016-05-11: Phab:E66/34(E171)
- T113034: RFC: Overhaul Interwiki map, unify with Sites and
WikiMap
- The ArchCom-RfCs board has a "Ready for RFC meeting" column which
should contain an ordered queue of RFCs planned for IRC office hour
Entering Final Comment Period
- Phab:T120164 - this is a last call for a process RFC about last
calls. See RobLa's email to wikitech-l on 2016-05-04 about this.
RFC inbox
- ArchCom RFC board:
- empty on 2016-05-04
Shepherd status
- Brion
- (?)
- Daniel
- Software Quality working group?
- Working on Multi Content Rev Spec with Brion
- Gabriel
- T39902 RFC: Implement rendering of redlinks as post-processor
(Gabriel): Solutions for highlighting links to non-existing
pages in Parsoid HTML. Plan in place / agreed between Parsing
and Services. Implementation in change propagation service
ready, preparing for deploy possibly next week.
- T122942 RFC: Support language variants in the REST API
(Gabriel): Waiting for progress on more general question of
language selection granularity / strategy & T114662.
- Roan
- I need to start the second part of T108655, but the recent
comments have me confused. I'll need to talk to Timo and figure
out what the subject of part two should be.
- RobLa
- Created mw:RFCstatus
- still need to schedule an RFC triage meeting outside of
ArchCom-RFC time
- Tim
- No update
- Timo
- No update
No activity in the last two weeks
- T123753 Establish retrospective reports for Security and Performance
incidents (RobLa)
- T122825 Service ownership and minimum maintenance requirements
(Gabriel)
- T124504 Transition WikiDev '16 working areas into working groups
(RobLa)
- T66214 Use content hash based image / thumb URLs & define an
official thumb API (Brion)
- T113034 RFC: Overhaul Interwiki map, unify with Sites and WikiMap
(Daniel)
- T128351 RFC: Notifications in core (Brion)
- T122825 Service ownership and minimum maintenance requirements
(Gabriel)
- T54807: Identify and remove legacy preferences from MediaWiki core
(no shepherd)
- T88596 Improving extension management (Daniel)
- T114444 RFC: Introduce notion of DOM scopes in wikitext (Tim)
AFAICT, in the last few days there were two unannounced upgrades of
Phabricator, to an unspecified version of the software, the second of
which applied rather radical UI changes, especially to Maniphest.
Initially I wasn't sure most/which UI changes were bad/good or why, but
now I've observed myself for a few days and I took the time to take
screenshots and describe my findings. Of course, most are about
* the consistent enlargement of some items to the expense of others,
* the introduction of a sidebar to host an ever-growing amount of buttons,
* the move of most task information under the description or under the
sidebar.
Please comment on the reports, add your findings and file new reports
for separate issues (I've not tested areas outside Maniphest, for instance):
* https://phabricator.wikimedia.org/T134393
* https://phabricator.wikimedia.org/T134394
* https://phabricator.wikimedia.org/T134398
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?
Nemo
Hi folks,
One thing we've implicitly adopted is "last calls" for ArchCom-RFCs.
I filed it as an RFC to get it on our workboard:
https://phabricator.wikimedia.org/T120164
However, what that means is that we need to have a last call on the
"last call" RFC. Obligatory xkcd reference: https://xkcd.com/244/
Barring objection in Phab, we'll consider T120164 approved then.
Rob
I am trying to work on https://ta.wikisource.org with python API.
This tamil wikisource has custom html option buttons to mention the edit status.
See a screenshot here.
https://snag.gy/f3aTBn.jpg
How to enable these custom option buttons via API?
Thanks.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com
Colorization
<https://en.wikipedia.org/wiki/Film_colorization#Digital_colorization>
refers to the process of adding color to black-and-white photographs. This
work was historically done by hand. These days, colorization is usually
done digitally, with the support of specialized tooling. But it is still
quite labor-intensive.
A forthcoming paper
<http://hi.cs.waseda.ac.jp/~iizuka/projects/colorization/en/> from
researchers at Waseda University of Japan have developed a method for
automatic image colorization using deep learning neural network. The
results are both impressive and easy to reproduce, as the authors have
published
their code <https://github.com/satoshiiizuka/siggraph2016_colorization> to
GitHub with a permissive license.
Someone has already taken this code and packaged it as a simple webapp,
available at http://colorizr.io/ (NSFW). The webapp lets you upload
black-and-white pictures and colorizes them for you. (The site is currently
not safe for work because it displays a gallery of recent uploads. We know
how that goes.)
In this thread, let's discuss how this technology could be integrated with
the projects. Should we have a bot that can perform colorization on demand,
the way Rotatebot <https://commons.wikimedia.org/wiki/User:Rotatebot> can
rotate images?
There's a reported ImageMagick security vulnerability making the rounds:
http://arstechnica.com/security/2016/05/easily-exploited-bug-exposes-huge-n…
Many MediaWiki sites are configured to use ImageMagick's 'convert' command
to perform image rescaling/thumbnailing, so it's worth double-checking that
everything is secure...
MediaWiki already performs file type validation checks on uploads, which
*should* prevent exploitation of the vulnerability for the standard image
types (JPEG, PNG, GIF, SVG etc) -- this is one of the recommended
mitigation strategies. But I am not confident enough to pronounce us immune
without actually checking!
Some folks are also recommending tweaking the ImageMagick policy.xml to
disable the most dangerous code modules; see the article linked above for
further links.
-- brion
Hello,
today the server that runs irc.wikimedia.org has been upgraded.
Or actually, we have installed a new, second server running on Debian
jessie and ported the puppet manifests and the IRC bot to work on
that, while the old
server still exists. MW appservers are sending RC data to both of them.
If you are making a new connection to irc.wikimedia.org you should now
be served by the new host, kraz.wikimedia.org but old connections
have not been broken.
The old server is still running unchanged and is reachable as
argon.wikimedia.org (as it was before too).
We have also made the change "URLs in the recent changes IRC feed will
no longer be rewritten to unencrypted HTTP." which was announced and
scheduled for today, May 2nd.
No action is required if your bot automatically reconnects, but bot
owners should ensure no IP addresses are hardcoded (see T123729 for
details.)
DNS caches slowly roll over and new connections will use kraz.
Existing sessions on argon and clients that hardcoded the argon IP
won't be affected yet, but after a grace period we are going to shut
down the old server argon.
refs: https://phabricator.wikimedia.org/T123729#2216681https://meta.wikimedia.org/wiki/Tech/News/2016/02
Best regards,
Daniel
--
Daniel Zahn <dzahn(a)wikimedia.org>
Operations Engineer
