Hello everyone,
TL;DR if you are not deploying services to the eqiad kubernetes
cluster, you can safely skip this.
Long version:
After having tested thrice our cluster reinitialization procedure, next
week, on Tuesday 2021-03-23 we will be reinitializing our eqiad
kubernetes cluster. All
traffic will be drained from it beforehand and we expect no user
visible impact. However, for the duration of the process, the
kubernetes eqiad cluster will be unavailable to deployers and thus
efforts to deploy to it will fail or worse, not have the expected
outcomes. This is normal until SRE serviceops announces that the
cluster is fully operational again.
SRE service-ops will be deploying all services before marking the
cluster as usable and pooling traffic back to it, so there will be no
need for deployers to re-deploy their services.
For your convenience the list of services that are currently deployed
on that cluster is: apertium api-gateway blubberoid changeprop
changeprop-jobqueue citoid cxserver echostore eventgate-analytics
eventgate-analytics-external eventgate-logging-external eventgate-main
eventstreams eventstreams-internal linkrecommendation mathoid
mobileapps proton push-notifications recommendation-api sessionstore
similar-users termbox wikifeeds zotero
Regards,
--
Alexandros Kosiaris
Principal Site Reliability Engineer
Wikimedia Foundation
Hi All!
tl;dr: if you're a developer looking for guidance on how to deploy changes
to Wikimedia's MediaWiki cluster read https://w.wiki/36nY ; if you have
thoughts on our existing deployment documentation comment on
https://w.wiki/36nZ
---
Over time The Train™ has become the default way to deploy changes to
Wikimedia's MediaWiki cluster -- for some patches that may not always be
the right path. If a developer needs a change deployed *now*, or if there
is a desire to deploy a change in isolation then backports might be a
better path.
As with all things, some exceptions may apply. The Release Engineering team
has created some guidelines[0] that will hopefully help explain when
something MUST, SHOULD, or MAY[1] be deployed via the train or via backport.
This documentation is a bookmarkable quick reference for developers. It
does not change our backport window guidelines[2] or special deployment
window guidelines[3], those documents should not be in conflict with the
advice in the new guidelines. The new guidelines target a different
use-case.
Our deployment documentation is up-to-date but sprawling. The same
information is in multiple places and multiple audiences and use-cases are
often mixed into the same documents. Work to improve deployment
documentation is tracked on Phabricator[4].
Please reach out in #wikimedia-releng on freenode in IRC or attend the
Deployment Office Hours meeting (weekly on Mondays at 17:00UTC in
#wikimedia-office on freenode in IRC) if you have questions.
Thank you!
-- Tyler
[0]: <https://wikitech.wikimedia.org/wiki/Deployments/Train_vs_backport>
[1]: <https://tools.ietf.org/html/rfc2119>
[2]: <https://wikitech.wikimedia.org/wiki/Backport_windows#Guidelines>
[3]: <https://wikitech.wikimedia.org/wiki/Deployments/Inclusion_criteria>
[4]: <https://phabricator.wikimedia.org/T273802>
Greetings,
This is a follow up from our last email some months ago (and a crosspost).
You may already have seen today's announcement from Legal about the
upcoming changes to the Maps Terms of Use. Here is an extra heads-up
that Wikimedia
Maps are transitioning towards a more modern architecture. The first phase
of this transition will be replacing Tilerator [0] with Tegola [1] as our
vector tile server. This is a change in the Maps infrastructure, so there
should be little to no impact to the end users’ experience.
It is important that we are able to provide software that is sustainable to
support, before we can guarantee a reliable user experience. Wikimedia Maps
aim to provide Wikimedia users a consistent experience contributing to and
learning about geoinformation. To achieve this goal, we will empower those
engineers maintaining the Wikimedia Maps infrastructure to do so with ease
and low effort.
If you want to learn more, please head to mediawiki.org [2], where you will
also find a Questions & Answers section.
Thanks, and take care,
Erica Litrenta (on behalf of the Product Infrastructure team)
[0] https://wikitech.wikimedia.org/wiki/Maps/Tilerator
[1] https://tegola.io/
[2] https://www.mediawiki.org/wiki/Wikimedia_Maps/2021_modernization_plan
--
------------------------------
Erica Litrenta (she/her)
Manager, Community Relations Specialists
Wikimedia Foundation <https://meta.wikimedia.org/wiki/User:Elitre_(WMF)>
I just noticed that I can no longer amend other peoples patch sets. I used to have this ability, but it appears that it was moved to Trusted-Contributors. [1] Can someone in that group add me?
Thanks in advance.
Mainframe98
[1] https://phabricator.wikimedia.org/T238651
Hello,
This is Swathi new to this MediaWiki environment and really excited to
contribute to it for which I already created a Wikimedia developer account
using this https://wikitech.wikimedia.org/wiki/Special:CreateAccount and
now when I am trying to login to Gerrit (https://gerrit.wikimedia.org/)
using the same credentials the message is been displayed that the
authentication failed. Can someone help me out to solve this issue, please--
Regards,
Swathi Kasikala.
amFOSS <https://amfoss.in/@swathi>
Hi all,
On April 5, 2020, we will update the Wikimedia Maps Terms of Use. Following
the access limits announced in August 2020 [0] and implemented in October
2020 [1], the Wikimedia Maps service no longer supports third-party usage
of Wikimedia map tiles. We are now updating the terms to reflect this
policy.
This change will not affect support for Wikimedia Maps on the Wikimedia
projects, tools hosted on Wikimedia Cloud Services, or other allowed
Wikimedia-affiliated domains. [2]
The updated Maps Terms of Use is available here:
https://meta.wikimedia.org/wiki/Revised_Maps_Terms_of_Use_(March_2021)
If you have any suggestions, you can add them to the talk page:
https://meta.wikimedia.org/wiki/Talk:Revised_Maps_Terms_of_Use_(March_2021)
Under our Maps Terms of Use, we've committed to providing 14 days notice
before changes are made to the policy.
Best,
Stephen
[0] https://lists.wikimedia.org/pipermail/maps-l/2020-August/001729.html
[1] https://phabricator.wikimedia.org/T261424
[2] https://phabricator.wikimedia.org/T261694
--
Stephen LaPorte (he/him/his)
Legal Director
Wikimedia Foundation
*NOTICE: This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal and ethical
reasons, I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity. For more
on what this means, please see our legal disclaimer
<https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer>.*
// sorry for cross-posting
Hi! Another improvement for the syntax highlighting (CodeMirror) is coming
soon:
The Technical Wishes team at Wikimedia Deutschland will update the colors
in the syntax highlighting feature to add more contrast, improving
accessibility and readability. The changes ensure that the syntax
highlighting color scheme is compliant with the Web Content Accessibility
Guidelines (WCAG 1.4.3 AA).[1]
This not only helps people with reduced vision, but can also be helpful
when editing in glaring daylight. Examples can be found on the project
page.[2]
As usual, we deploy in batches, and plan to start with a German, Catalan
and Turkish Wikipedia on March 24.[3]
Feedback is, as always, welcome on the talk page of the project.[4]
Best,
Johanna for the Technical Wishes team
[1] https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines
[2]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Improved_Color_Scheme…
[3] https://phabricator.wikimedia.org/T276346
[4]
https://meta.wikimedia.org/wiki/Talk:WMDE_Technical_Wishes/Improved_Color_S…
--
Johanna Strodt
Project manager Community Communications Technical Wishes
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
https://wikimedia.de
Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit
teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
https://spenden.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Hi!
I'm Shahansha, a student at Heritage Institute of technology. I have
experince from last more than 1 year in my journey as a developer and have
worked with HTML, CSS, JS,java, Bootstrap 4, Python3, C/C++,mongoDB, MySQL
to enchance MY creativity.
Im interested to enchance develops, enhances, tests and web content
applications with an end goal of creating engaging and user-friendly site
layout and function, I'm much fascinated to be a part of the community,
learn and contribute In wikimedia Gsoc.
Thank You!!
Hi Wikitech-I Team,
I am Rohit Purkait, 1st year B.Tech undergraduate at Techno India Main.
I would like to contribute to Wikitech-I*.* I have working experience in
HTML, CSS, SASS, JavaScript and Node.js
This is one of the responsive websites created by me in the Front-End
Mentor Challenge:
My created website <https://loop-studios-chi.vercel.app/>
Here is the GitHub repo link for the above: Github Repo Link
<https://github.com/codeswithroh/loop-studios>
Thanks and Regards,
Rohit Purkait