Sorry, I apparently replied to the wrong mailing list.
On 14/08/18 18:19, Isarra Yos wrote:
> As a total random, I'd also like to second this - as much as I think
> the CoC and the committee in particular have room to improve in how
> things are handled, this will never happen without proper support for
> the work they're doing in the first place.
>
> While some of us have been somewhat flabbergasted by specific events,
> these are after all the people we need to be working with to actually
> resolve the issues at hand, and indeed the events (and handling
> thereof) themselves have also highlighted the need for more clearer
> standards moving forward. I'm glad to see some steps have already been
> taken. Let's continue in this vein.
>
> Thank you!
>
> -I
>
> On 14/08/18 18:08, Amir Ladsgroup wrote:
>> Hey,
>> As a member of Code of conduct committee I just wanted to express how
>> much
>> I appreciate your statement. The work we are doing is not fun, we are
>> dealing with frustrations, harassments, trolling, and all sorts of
>> the dark
>> side of the Wikimedia movement but I genuinely believe that this type of
>> work is vital to keep the movement moving forward, to make us more
>> welcoming and foster a diverse environment.
>>
>> All of the support I've received, private and public, online and
>> offline is
>> overwhelming. Thank you, Thank you, Thank you.
>>
>> Best
>> On Tue, Aug 14, 2018 at 7:46 PM Victoria Coleman
>> <vcoleman(a)wikimedia.org>
>> wrote:
>>
>>> Hello everyone,
>>>
>>> The executive leadership team, on behalf of the Foundation, would
>>> like to
>>> issue a statement of unequivocal support for the Code of Conduct[1]
>>> and the
>>> community-led Code of Conduct Committee. We believe that the
>>> development
>>> and implementation of the Code are vital in ensuring the healthy
>>> functioning of our technical communities and spaces. The Code of
>>> Conduct
>>> was created to address obstacles and occasionally very problematic
>>> personal
>>> communications that limit participation and cause real harm to
>>> community
>>> members and staff. In engaging in this work we are setting the tone
>>> for the
>>> ways we collaborate in tech. We are saying that treating others
>>> badly is
>>> not welcome in our communities. And we are joining an important
>>> movement in
>>> the tech industry to address these problems in a way that supports
>>> self-governance consistent with our values.
>>>
>>> This initiative is critical in continuing the amazing work of our
>>> projects
>>> and ensuring that they continue to flourish in delivering on the
>>> critical
>>> vision of being the essential infrastructure of free knowledge now and
>>> forever.
>>>
>>> Toby, Maggie, Eileen, Heather, Lisa, Katherine, Jaime, Joady, and
>>> Victoria
>>>
>>>
>>> https://www.mediawiki.org/wiki/Code_of_Conduct <
>>> https://www.mediawiki.org/wiki/Code_of_Conduct>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Wikimedia-l mailing list, guidelines at:
>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
>>> https://meta.wikimedia.org/wiki/Wikimedia-l
>>> 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>
>> _______________________________________________
>> Wikimedia-l mailing list, guidelines at:
>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
>> https://meta.wikimedia.org/wiki/Wikimedia-l
>> 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>
>
>
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on
#wikimedia-tech.
Question can be asked in English, Bulgarian & Persian.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://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/681/51985.
Hello,
I would like to do some major changes to two factor auth. I am cross
posting this on phabricator and the mailing list to give it some more
attention and to start some proper discussion before anyone starts
working on this:
Right now there are only two options for two factor authentication:
* Don't use two-factor authentication (insecure)
* Use two factor authentication (annoying as hell)
With two factor authentication it doesn't seem to be possible to make
session persistent and it really is extremely annoying to look for
your mobile phone, open the app and fill in the code everytime you
want to do some simple wiki action. I am very lazy and even found
myself to rather decide not to do a minor change (be it fix of typo
correction etc. in article on English Wikipedia etc) rather than going
through the hassle of using the google authenticator.
I think it would be really cool to have an option (or maybe even more
of them?) that would help to specify when two factor auth is really
desired, so that for example users could decide that for simple
actions like wiki editing normal login would be sufficient, but for
changes like:
* Change of password
* Change of (some) preferences
* Admin actions (block, delete etc.)
P.S. Unfortunately I no longer have so much free time to track every
single thread in this mailing list, so maybe this is a duplicate of
some older idea by someone else, if that's the case, please merge the
phab task with whatever the other identical proposal is.
Thank you
FYI, this maintenance is starting in a few minutes and will result in
some CI downtime. Gerrit will probably refuse to test or merge patches
while the work is in progress.
-------- Forwarded Message --------
Subject: Re: [Cloud-announce] Operation on Cloud VPS next monday 13th Aug
Date: Mon, 13 Aug 2018 15:30:45 +0200
From: Arturo Borrero Gonzalez <aborrero(a)wikimedia.org>
Reply-To: cloud(a)lists.wikimedia.org
Organization: Wikimedia Foundation
To: cloud-announce(a)lists.wikimedia.org
On 07/08/18 18:24, Arturo Borrero Gonzalez wrote:
> Hi!
>
> Next monday 13th we will be doing some maintenance on the main Cloud VPS
> deployment to merge the keystone service of both main and eqiad1
> deployments (the new one that we will eventually put into production).
>
> Toolforge users will not be affected by this outage.
>
> Day: Monday 13th August
> Start time: 14:00 UTC
> Finish time: 16:00 UTC or ASAP
>
> Keystone is a central point in openstack, so most horizon operations
> like login, creating/deleting VMs could be affected. On the other hand,
> VMs will keep working and we don't expect any network outage.
>
> This operation will allow us to have a smooth transition in the future
> when we move all projects and instances to the new eqiad1 deployment and
> is a previous step to having multi-region support in our Cloud VPS service.
>
> Please let us know any question or suggestions you may have.
>
Reminder, this is happening today in 30 minutes.
_______________________________________________
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,
A gerrit administrator is required to review and handle
<https://phabricator.wikimedia.org/T193049>, either to ask for
clarifications or close it one way or another. Repository ownership
requests take aprox. one week; this has been sitting there since April
without virtually no activity but pings for assistance. I think the
user deserves an answer.
Thank you, M.
Recently, I was outside at night, and I was fortunate to see several
meteors. The 2018 Perseid <https://en.wikipedia.org/wiki/Perseids> meteor
shower is at its peak this weekend.
Also, yesterday I spent some time on English Wikipedia's main page
<https://en.wikipedia.org/wiki/Main_Page> and browsed some of the linked
articles. I was glad to be reminded that regardless of world events, good
or bad, we continue to create Wikipedia.
What's making you happy this week? You are welcome to write in any language.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
Greeting!
I am Tanvi Dadu, GSoC 2018 participant. For the past three months, I have
been working on Achievements Module in Commons App and
<https://phabricator.wikimedia.org/T189788#4153895>quiz
<https://phabricator.wikimedia.org/T189788#4153895>and it gives me immense
happiness to say that I have successfully completed it. Both of the
features have been released as part of 2.8 version. My works summary is
present at my MediaWiki
<https://www.mediawiki.org/wiki/User:Tanu_dadu#GSoC_WEEKLY_REPORTS>userpage
<https://www.mediawiki.org/wiki/User:Tanu_dadu#GSoC_WEEKLY_REPORTS>.
I would like to thank my Mentors ,Josephine Lim and Vivek Maskara, and the
whole Commons team for helping and encouraging me throughout the summer. It
feels very satisfying and amazing to be part of this community. I had an
amazing experience with lots of learning involved and I can't thank enough
to give this wonderful opportunity.
Regards
Tanvi Dadu