(feel free to forward the message as is to your friends, family members &
colleagues)
Hello folks,
We would like to invite you to apply to the Outreachy and Google Summer of
Code program with the Wikimedia Foundation (a non-profit organization
behind Wikipedia)!
About the Outreachy program
Wikimedia will be mentoring ~3 projects in the Outreachy program in the May
to August 2021 round. The initial applications are due February 22nd at 4
pm UTC.
Apply today: https://www.outreachy.org/apply/ [1]
Outreachy offers three-month internships to work remotely in Free and Open
Source Software (FOSS) projects with experienced mentors. The internships
may include programming, user experience, documentation, illustration, and
graphic design, or data science.
Outreachy internships run twice a year – from May to August and December to
March. Interns are paid a stipend of $5,500 USD for the three months of
work. They also have a $500 USD stipend to travel to conferences and
events. Interns often find employment after their internship with Outreachy
sponsors or in jobs that use the skills they learned during their
internship.
Outreachy is open to both students and non-students. Outreachy expressly
invites the following people to apply:
- Women (both cis and trans), trans men, and genderqueer people.
- Anyone who faces under-representation, systematic bias, or
discrimination in the technology industry in their country of residence is
invited to apply.
- Residents and nationals of the United States of any gender who are
Black/African American, Hispanic/Latin@, Native American/American
Indian, Alaska Native, Native Hawaiian, or Pacific Islander.
About the Google Summer of Code program
Wikimedia is planning to mentor 8-10 projects in 2021’s Google Summer of
Code (GSoC) program. Beginning March 9th, pending Wikimedia’s acceptance as
a mentoring organization, applicants can begin discussing ideas with the
mentors!
The student application will be due on April 13, 2021:
https://summerofcode.withgoogle.com/ [2]
Google Summer of Code, now in its 17th year, is Google's summer program for
candidates participating in any academic programs who want to get involved
in open-source software. Over 6,626 students from 121 countries have
already participated in the last year’s round i.e 2020 <
https://opensource.googleblog.com/2020/06/google-summer-of-code-2020-statis…>
[3]. Google Summer of Code is a unique program that pairs students with
mentors who introduce them to the open-source community and provide
guidance while they work on real-world open-source projects during their
summer break from university.
This year there are some new breaking changes in the GSoC program,
including:
- Smaller project size ~175 hr project (previously 350 hr)
- Shortened coding period ~10 weeks long (previously 3 months)
- Eligibility criteria redefined; the program is now open to candidates
participating in a variety of academic programs (previously accredited
university programs only)
Projects cover a wide range of fields including Cloud, Operating Systems,
Graphics, Medicine, Programming Languages, Robotics, Science, Security and
many more. It's a highly competitive program (and this year is expected to
be even bigger than last year), so don't wait until the last minute to
prepare!
About the Wikimedia Foundation
The Wikimedia Foundation is the nonprofit organization that hosts and
operates Wikipedia and the other Wikimedia free knowledge projects. Our
vision is a world in which every single human can freely share in the sum
of all knowledge. We believe that everyone has the potential to contribute
something to our shared knowledge and that everyone should be able to
access that knowledge, free of interference. We host the Wikimedia
projects, build software experiences for reading, contributing, and sharing
Wikimedia content, support the volunteer communities and partners who make
Wikimedia possible, and advocate for policies that enable Wikimedia and
free knowledge to thrive.
Resources
* Browse through the participants’ guides, to learn more about the
application process steps:
<https://www.mediawiki.org/wiki/Outreachy/Participants> [4]
<https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants> [5]
* All the projects will be showcased here:
<https://www.outreachy.org/communities/cfp/wikimedia/> [6]
<https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021> [7]
We hope you will help us spread the word about Wikimedia’s participation in
these programs (by sharing this email)
Looking forward to your participation!
Cheers,
Gopa, Srishti, Pavithra, Ankit & Mahveotm (Wikimedia organization
administrators for GSoC & Outreachy)
[1] https://www.outreachy.org/apply/
[2] https://summerofcode.withgoogle.com/
[3]
https://opensource.googleblog.com/2020/06/google-summer-of-code-2020-statis…
[4] https://www.mediawiki.org/wiki/Outreachy/Participants
[5] https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants
[6] https://www.outreachy.org/communities/cfp/wikimedia/
[7] https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021
--
Regards
Gopa Vasanth <https://www.mediawiki.org/wiki/User:Gopavasanth>
Amrita Vishwa Vidyapeetham <http://www.amrita.edu/> | Blog
<https://gopavasanth.wordpress.com/>
amFOSS <https://amfoss.in/@gopavasanth> | GitHub
<https://github.com/gopavasanth> | Gerrit
<https://gerrit.wikimedia.org/r/#/q/gopavasanth>
“Yesterday is not ours to recover, but tomorrow is ours to win or lose.”
On Tuesday we will be upgrading the cloud-vps OpenStack install to
version 'Train'. During the upgrade window (probably about an hour),
Horizon will be disabled.
Existing tools and VMs should be largely unaffected; there will likely
be a brief network interruption when the network software is restarted.
The upgrade is scheduled for 15:00 UTC, which is 7AM in California.
-Andrew + the WMCS team
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Wikimedia Cloud Services now supports attachable block storage via the
OpenStack Cinder project. Attachable block storage is a flexible storage
option that allows you to create volumes local to your project but not
coupled to a particular VM; they can be moved between different
instances and persist after their associated volume is deleted. Project
admins can access this feature via the 'Volumes' tab in Horizon.
I encourage all of you to start using Cinder storage for your new
databases and large data sets. Over the next few months we'll be working
to move various use cases onto Cinder volumes and off of NFS or LVM;
soon I hope to deprecate large-storage flavor types entirely and support
all new non-root file storage with Cinder.
The default storage quota is quite small, but we plan to be generous
with quota increases. To request additional storage, open a phabricator
ticket here:
https://phabricator.wikimedia.org/project/view/2880/
For more details about this feature, I've written a blog post, here:
https://techblog.wikimedia.org/2021/02/05/cinder-on-cloud-vps/
And, technical documentation can be found here:
https://wikitech.wikimedia.org/wiki/Help:Adding_Disk_Space_to_Cloud_VPS_ins…
Like any new feature, our implementation almost certainly includes bugs
and missteps. Please provide feedback or feature requests via
phabricator or on the cloud mailing list.
-Andrew + the WMCS Team
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
On Tue, Aug 18, 2020 at 9:03 AM Bryan Davis <bd808(a)wikimedia.org> wrote:
>
> TL;DR:
> * HTTP -> HTTPS redirection is live (finally!)
> * Currently allowing a "POST loophole"
> * "POST loophole" will be closed on 2021-02-01
>
> Today we merged a small change [0] to the front proxy used by Cloud
> VPS projects [1]. This change brings automatic HTTP -> HTTPS
> redirection to the "domain proxy" service and a
> Strict-Transport-Security header with a 1 day duration.
>
> The current configuration is conservative. We will only redirect GET
> and HEAD requests to HTTPS to avoid triggering bugs in the handling of
> redirects during POST requests. This "POST loophole" is the same
> process that we followed when converting the production wiki farm and
> Toolforge to HTTPS.
>
> When we announced similar changes for Toolforge in 2019 [2] we forgot
> to set a timeline for closing the POST loophole. This time we are
> wiser! We will close the POST loophole and make all HTTP requests,
> regardless of the verb used, redirect to HTTPS on 2021-02-01. This 6
> month transition period should give us all a chance to find and update
> URLs to use https and to fix any dependent software that might break
> if a redirect was sent for a POST request.
>
> If you find issues in your projects resulting from this change, please
> do let us know. The tracking task for this change is T120486 [3]. We
> also provide support in the #wikimedia-cloud channel on Freenode and
> via the cloud(a)lists.wikimedia.org mailing list [4].
>
>
> [0]: https://gerrit.wikimedia.org/r/c/operations/puppet/+/620122/
> [1]: https://wikitech.wikimedia.org/wiki/Help:Using_a_web_proxy_to_reach_Cloud_V…
> [2]: https://phabricator.wikimedia.org/phame/post/view/132/migrating_tools.wmfla…
> [3]: https://phabricator.wikimedia.org/T120486
> [4]: https://lists.wikimedia.org/mailman/listinfo/cloud
TL;DR:
* "POST loophole" closed per prior announcement on 2020-08-18
* 366 day Strict-Transport-Security header sent with all HTTPS responses
I am very happy to announce that today we have closed the "POST
loophole" for our *.wmflabs.org & *.wmcloud.org proxy layer [5]. This
is a follow up to the announcement of partial TLS enforcement by the
Cloud VPS front proxies on 2020-08-18.
There is a possibility that closing the POST loophole will break some
clients accessing services running in Cloud VPS behind the front
proxies. Specifically, POST actions sent to HTTP (not HTTPS) URLs will
now return a 301 Moved Permanently response to the same URL with the
scheme changed to https. The HTTP specifications are ambiguous about
how this response should be handled which means that implementations
in various browsers and libraries may or may not re-POST the original
payload to the new URL. The best fix we can suggest for this is
updating links and forms to always use HTTPS URLs.
If you find issues in your projects resulting from this change, please
do let us know. The tracking task for this change is T120486 [6]. We
also provide support in the #wikimedia-cloud channel on Freenode and
via the cloud(a)lists.wikimedia.org mailing list [7].
[5]: https://gerrit.wikimedia.org/r/661140
[6]: https://phabricator.wikimedia.org/T120486
[7]: https://lists.wikimedia.org/mailman/listinfo/cloud
Bryan, on behalf of the Cloud VPS admin team
--
Bryan Davis Technical Engagement Wikimedia Foundation
Principal Software Engineer Boise, ID USA
[[m:User:BDavis_(WMF)]] irc: bd808
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Hello,
we are planning to change how Cloud VPS instances and Toolforge tools contact
WMF-hosted wikis, in particular the source IP address for the network connection.
The new IP address that wikis will see is 185.15.56.1.
The change is scheduled to go live on 2021-02-08.
More detailed information in wikitech:
https://wikitech.wikimedia.org/wiki/News/CloudVPS_NAT_wikis
If you are a Cloud VPS user or Toolforge developer, check your tools after that
date to make sure they are properly running. If you detect a block, a rate-limit
or similar, please let us know.
If you are a WMF SRE or engineer involved with the wikis, be informed that this
address could generate a significant traffic volume, perhaps about 30%-40% total
wiki edits. We are trying to smooth the change as much as possible, so please
send your feedback if you think there is something we didn't account for yet.
Thanks, best regards.
--
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services
Wikimedia Foundation