Re: [Wikitech-l] Wikimedia Chat

[Amir Sarabadani]

Hey!

On Mon, Aug 31, 2020 at 9:56 AM Count Count 
wrote:

> Hi!
>
> Thanks for providing another communication tool.
>
> Some questions:
>
>- Is there a reason why we are not using Wikimedia account SSO for the
>chat?
>
Due to the privacy policy of Wikimedia Cloud, we are not allowed to use SUL
or LDAP of Wikimedia or Wikitech respectively, but I have been looking into
improving the user integration because it has been asked in multiple
places. You can follow it in https://phabricator.wikimedia.org/T261631

Mattermost doesn't have a native support for Wikimedia OAuth but it has
support for GitLab OAuth and funnily enough, since everything is
customizable in settings, I assume it should workTM, if yes, it would look
weird but it would work. If not, we have to file a bug in upstream
(mattermost) and ask for a general OAuth support.

   - The Terms link leads directly to the Tech Code of Conduct. Shouldn't
>it link to  https://foundation.wikimedia.org/wiki/Terms_of_Use/en
> instead?
>After all terms are usually more than just a Code of Conduct.
>

I don't have many preferences in that regard, I have one choice for terms
of use and can't decide between this or that.

>- The linked privacy policy
>
> is
>a bit scary. It states that there is no expectation of privacy as my
> chats
>could be published at any time and that the administrators might have
>access to my username/password combination, which should not at all be
>necessary. Is that really the intent here?
>

As said before, this is the standard privacy policy that we must use in
order to comply with the Cloud terms of use
https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use

Not that I won't publish anything private, also the mattermost itself
protects private data (like passwords) by hashing them.

>
>
> Best regards,
>
> Count Count
>
> On Sun, Aug 30, 2020 at 2:00 AM Amir Sarabadani 
> wrote:
>
> > Hello,
> > Due to the current situation, there are more and more collaborations
> > happening online instead. and now you can see Wikimedia-related
> discussion
> > groups in Slack, Discord, Telegram, Facebook, and many more. Besides
> being
> > scattered and inaccessible to people who don't have accounts in those
> > platforms (for privacy reasons for example), these platforms use
> > proprietary and closed-source software, are outside Wikimedia
> > infrastructure and some harvest our personal data for profit.
> >
> > IRC on freenode is a good alternative but it lacks basic functionalities
> of
> > a modern chat platform. So we created Wikimedia Chat, a mattermost
> instance
> > in Wikimedia Cloud. Compared to IRC, you have:
> > * Ability to scrollback and read messages when you were offline
> > * Push notification and email notification
> > * You don't need to get a cloak to hide your IP from others
> > * Proper support for sharing media
> > * Two factor authentication
> > * A proper mobile app support
> > * Ability to add custom emojis (yes, it's extremely important)
> > * Profile pictures
> > * Ability to ping everyone with @here
> > * much much more.
> >
> > You can use Wikimedia Chat by going to https://chat.wmcloud.org, anyone
> > can
> > make an account. This is part of Wikimedia Social suite [1], the oher
> > similar project is "Wikimedia Meet". [2]
> >
> > Some notes:
> > * This is done in my volunteer capacity and has been maintained by a
> group
> > of volunteers. If you're willing to join the team (either technical or
> > enforcing CoC, kicking out spammers, other daily work), drop me a
> message.
> > * Privacy policy of Wikimedia Cloud applies: https://w.wiki/aQW
> > * As a result, all messages older than 90 days get automatically deleted.
> > * As a Wikimedia Cloud project, all of discussions, private and public
> are
> > covered by Code of conduct in technical spaces:  https://w.wiki/AK$
> >
> > Hope that would be useful for you, if you encounter any technical issues,
> > file a bug in the phabricator.
> >
> > [1] https://meta.wikimedia.org/wiki/Wikimedia_Social_Suite
> > [2] https://meta.wikimedia.org/wiki/Wikimedia_Meet
> >
> > Best
> > --
> > Amir (he/him)
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>


-- 
Amir (he/him)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] MediaWiki 1.35.0-rc.3 is ready for testing

[Sam Reed]

I'm pleased to announce the immediate availability of MediaWiki
1.35.0-rc.3, the fourth (and hopefully final; only minor documentation and
packaging changes are expected) release candidate for 1.35.x, the next LTS
version to replace 1.31 which is due to go end of life in June 2021.
Download links at the end of the e-mail. The tag has been signed and pushed
to Git.

Please note that the PHP version requirement has been raised from 7.2.9 in
MediaWiki 1.34 (and 7.0 in MediaWiki 1.31), to 7.3.19.

This is not a final release and should not be used for production websites.
Known issues are tracked in Phabricator on the release workboard [1]. As
always please do try out the release candidate in a test environment and
report any issues that you discover. Please use the #MW-1.35-Release [2]
tag in Phabricator when reporting issues specific to this release.

It is expected that MediaWiki 1.35 will become final in mid September 2020
(apologies for the delay), and will be supported for 3 years after that.

Known/outstanding issues/things to test:
* The PHP requirement for MediaWiki 1.35 has been raised to 7.3.19.
* Both the Vector skin and the underlying skin infrastructure are
undergoing numerous changes, so there might be things broken that are
already fixed in master and as such need backporting.
* VisualEditor and Parsoid are now bundled in the tarball and no longer
need a separate nodejs service. The documentation for this still may still
require some updates.
* Watchlist expiry (behind the $wgWatchlistExpiry flag) is currently
experimental. It should be finished for the 1.35.0 final release.
* If you're on Windows and use 7zip and had issues in the previous release
candidates (and the last round of security releases) extracting the
tarball, this should be fixed for this release.

Changes since 1.35.0-rc.2:
* (T258662) mediawiki.visibleTimeout: Update the nextVisibleTimeoutId value.
* Ensure Parsoid doesn't throw when  is used w/o Cite installed.
* Remove maintenance/createCommonPasswordCdb.php.
* (T260468) Increase "sites.site_global_key" to varbinary(64).
* (T183759) Fix shell edge-cases in Windows.
* (T257879) Drop PHP 7.2 support; require 7.3.19.
* (T251661) User::pingLimiter: add user-global rate limit type.
* (T246991) User: enforce pingLimiter() expiry time.
* (T256831) Rest: Handle Uri constructor exception.
* (T259094) Fix RequestFromGlobalsTest failing in Travis CI.
* (T256831, T261344) Rest: Use try/catch to handle URIs with embedded colon.

Preliminary release notes:
https://phabricator.wikimedia.org/source/mediawiki/browse/REL1_35/RELEASE-NOTES-1.35
https://www.mediawiki.org/wiki/Release_notes/1.35

Open Bugs:
[1] https://phabricator.wikimedia.org/project/board/4035/

Bug report form:
[2]
https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tags=MW-1.35-Release

**
Download:
https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0-rc.3.tar.gz

Download without bundled extensions:
https://releases.wikimedia.org/mediawiki/1.35/mediawiki-core-1.35.0-rc.3.tar.gz

Patch to previous version (1.35.0-rc.2):
https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0-rc.3.patch.gz

GPG signatures:
https://releases.wikimedia.org/mediawiki/1.35/mediawiki-core-1.35.0-rc.3.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0-rc.3.tar.gz.sig

Public keys:
https://www.mediawiki.org/keys/keys.html
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] TechCom weekly digest 2020-09-02

[Daniel Kinzler]

Hi all,

Here are the minutes from this week's TechCom meeting:

=== New RFC: Challenges of developing with npm dependencies ===
* The “frontend build step” RFC is overly broad, and has drifted over time, see
  https://phabricator.wikimedia.org/T199004
* Dan will draft a new RFC focused on some of the issues we encounter in the
  Analytics team when developing Node.js services. Specifically around code
  review, CI/deploy, and dependency auditing.

=== Parsoid extension API ===
* https://phabricator.wikimedia.org/T260714
* TT: this is a major milestone RFC, the new parser will replace the old one.
  Hooks and methods not mentioned here will likely be deprecated/removed. I
  believe that’s well-understood and the
* Parsoid team did great outreach over the past year. This should be detailed
  and summarised on the RFC, or linked to.

=== Session expiry ===
* Pywikibot users have been experiencing CSRF tokens, see
  https://phabricator.wikimedia.org/T261050
* This may be due to the fact that we have become more strict about expiring web
  sessions after a given time since we moved session storage to the Kask
  service.
* It is currently unclear from the documentation for how long a CSRF token is
  valid for. This should be made more clear.

=== Removal of unused code without deprecation ===
* Daniel proposed a change to the stable interface policy on wikitech-l, in a
  thread titled “Making breaking changes without deprecation?”
* Reactions are mixed, more feedback welcome.
* The input from the mailing list will be used to update the current policy


You can also find our meeting minutes at


If you prefer you can subscribe to our newsletter here


-- 
Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] OTRS major version upgrade on Monday September 14th 2020

[Alexandros Kosiaris]

I 've already sent the email below to otrs related mailing lists, but
I think wikitech-l can also benefit from this, so here it is.

--
Hello everyone,

This is to let you know that per
https://phabricator.wikimedia.org/T187984#6433997 on September 14th
2020 a 48 hour maintenance window for OTRS from 5.0 to 6.0 will begin.
While this is an unusually large time window, the migration process
from 5.0 to 6.0 is rather slow. We have looked into optimizing it, but
at the end preferred to stick with the software developers
recommendations.

During the maintenance window the system will be completely offline. That means:

* No access over the web to the interface
* No scheduled jobs of any kind will be run
* Email will not be delivered but rather backlogged. It will not be
lost as our MX systems will accept them and put them in the queue.
Once the system is back to being fully functional, the emails will
flow into the system.

We will have a rollback plan ready of course, just in case the
migration goes awry. We already have tested it but something might
arise anyway.

I am sorry for any inconvenience this might cause.

--
Alexandros Kosiaris
Principal Site Reliability Engineer
Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l