Re: [Wikitech-l] Storing some values in the DB

[Jaime Crespo]

> It complicates extension installation

One could just copy and paste the existing migration code and just change
the SQL to the right CREATE TABLE, and be done. If you just have to create
a table, you will only have to do that once, no maintenance required.
Trying to fit values into existing tables, however will create a lot of
maintenance headaches, as Brian said.

# include/Hooks.php
$base = __DIR__ . "/../sql";
$updater->addExtensionTable( 'extension_value', $base .
'/ExtensionValue.sql' );
# sql/ExtensionValue.sql
CREATE TABLE extension_value (
k varchar(100) PRIMARY KEY,
v int NOT NULL,
);

If you are overwhelmed with SQL or mediawiki migration system please just
ask for help and people here, including me, will be able to help! :-D
Mediawiki core code can be intimidating because support of several
databases systems and its long history of schema changes, but in your case
adding a table should not take more than 2 files that are never touched
again :-D. Update.php will have to be run anyway on core updates. Handling
mysql and queries is way more difficult than creating it in the first place!

Or maybe we are not understanding what you are trying to achieve. 0:-)

On Mon, Jan 27, 2020 at 5:00 PM Jeroen De Dauw 
wrote:

> Hey,
>
> > Why are you so reluctant to create a table?
>
> It complicates extension installation and adds yet another thing to
> maintain. Which is a bit silly for a handful of values. I was hoping
> MediaWiki would have a generic table to put such things already. Page_props
> is exactly that, just bound to specific pages.
>
> Cheers
>
> --
> Jeroen De Dauw | www.EntropyWins.wtf 
> Professional wiki hosting and services: www.Professional.Wiki
> 
> Software Crafter | Speaker | Entrepreneur | Open Source and Wikimedia
> contributor ~=[,,_,,]:3
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Jaime Crespo

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

[Wikitech-l] Security Team collaboration

[John Bennett]

Hello,

In an effort to create a repeatable and streamlined process for consumption
of security services the Security Team has been working on changes and
improvements to our workflows. Much of this effort is an attempt to
consolidate work intake for our team in order to more effectively
communicate status, priority and scheduling.  This is step 1 and we expect
future changes as our tooling, capabilities and processes mature.

*How to collaborate with the Security Team*

The Security Team works in an iterative manner to build new and mature
existing security services as we face new threats and identify new risks.
For a list of currently deployed services please review our services [1]
page.

The initial point of contact for the majority of our services is now a
consistent Request For Services [2] (RFS) form [3].

The two workflow exceptions to RFS are the Privacy Engineering [4] service
and Security Readiness Review [5] process which already had established
methods that are working well.

If the RFS forms are confusing or don't lead you to the answers you need
try security-h...@wikimedia.org  to get assistance with finding the right
service, process, or person

secur...@wikimedia.org will continue to be our primarily external reporting
channel

*Coming changes in Phabricator*

We will be disabling the workboard on the #Privacy [6] project.  This
workboard is not actively or consistently cultivated and often confuses
those who interact with it.  #Privacy is a legitimate tag to be used in
many cases, but the resourced privacy contingent within the Security Team
will be using the #privacy engineering [7] component.

We will be disabling the workboard for the #Security [8] project.  Like the
#Privacy project this workboard is not actively or consistently cultivated
and is confusing.  Tasks which are actively resourced should have an
associated group [9] tag such as #Security Team [10].

The #Security project will be broken up into subprojects [11] with
meaningful names that indicate user relation to the #Security landscape.
This is in service to #Security no longer serving double duty as an ACL and
a group project.  An ACL*Security-Issues project will be created and
#Security will still be available to link cross cutting issues, but will
also allow equal footing for membership for all Phabricator users.

*Other Changes*

A quick callout to the consistency [12] and Gerrit sections of our team
handbook [13].  As a team we have agreed that all changesets we interact on
need a linked task with the #security-team tag.

security@ will soon be managed as a Google group collaborative inbox [14]
as outlined in T243446.

Thanks
John

[1] Security Services
https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Services
[2] Security RFS docs
https://www.mediawiki.org/wiki/Security/SOP/Requests_For_Service
[3] RFS form
https://phabricator.wikimedia.org/maniphest/task/edit/form/72/
[4] Privacy Engineering RFS
https://form.asana.com/?hash=554c8a8dbf8e96b2612c15eba479287f9ecce3cbaa09e235243e691339ac8fa4=1143023741172306
[5] Readiness Review SOP
https://www.mediawiki.org/wiki/Security/SOP/Security_Readiness_Reviews
[6] Phab Privacy tag
https://phabricator.wikimedia.org/tag/privacy/
[7] Privacy Engineering Project
https://phabricator.wikimedia.org/project/view/4425/
[8] Security Tag
https://phabricator.wikimedia.org/tag/security/
[9] Phab Project types
https://www.mediawiki.org/wiki/Phabricator/Project_management#Types_of_Projects
[10] Security Team tag
https://phabricator.wikimedia.org/tag/security-team/
[11] Security Sub Projects
https://phabricator.wikimedia.org/project/subprojects/4420/
[12] Security Team Handbook
https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Handbook#Consistency
[13] Secteam handbook-gerrit
https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Handbook#Gerrit
[14] Google collab inbox
https://support.google.com/a/answer/167430?hl=en
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Google Code-in 2019: Read what students worked on

[Andre Klapper]

A few days ago, Google Code-in 2019 ended.

194 students completed 715 Wikimedia tasks.[1]
Big thanks and congratulations to everybody!

Read about their GCI experience with Wikimedia in their blog posts:
https://www.mediawiki.org/wiki/Google_Code-in/2019#Wrap-up_blog_posts

Thanks to our 43 mentors for being available, also on weekends &
holidays. Thanks to everyone on IRC, Gerrit, Phabricator, mailing
lists, Github, etc. for your friendliness, patience, support and help.
Thanks to Wikimedia org admins for making this run really smoothly.
And thanks to Google for organizing this opportunity for young people
to learn about and contribute to free software and free knowledge.
Google will announce Grand Prize winners and finalists on February 10.

We also welcome everybody's feedback what Wikimedia could improve:
https://www.mediawiki.org/wiki/Google_Code-in/Lessons_learned#2019

Sharing some of the students' achievements, to give you an impression:

 * WMCZ's Tracker software received 40 fixes and improvements
 * 37 fixes and improvements to the WatchTranslations tool
 * 24 fixes and improvements to the VideoCutTool tool
 * 12 fixes and improvements to the WikiContrib tool
 * Tasks to learn programming in Lua were completed 218 times (such as:
   Introduction to Lua in Wikipedia, Working with modules, Calculations
   and tests, Loops and tables, Lua libraries, MediaWiki libraries,
   Wikibase client, Name formats, Date formats, Using Wikidata)
 * 13 extensions got extension.json converted to manifest_version 2
 * 8 extensions got jshint and jscs replaced with eslint
 * 5 extensions got jsonlint replaced with eslint
 * Blockly, Huggle, Phabricator, video2commons, and Wiki Ed Dashboard
   got migrated to the new Translate validator framework
 * Flask-JSONLocale received three bug fixes
 * Watchlist notifications can be delivered as web notifications
   through Echo (but not enabled yet on Wikimedia sites)
 * Kiwix Android App has a button to search for a new article
 * Quarry has a button to toggle syntax highlighting
 * Wikilink tool has a namespace filter and can filter bot edits
 * Commons Android App has screenshots in 14 more languages, the
   username can be clicked in the navigation drawer, an improved share
   message, and videos for best media upload practices were created
 * Commons Mass Description tool: /users does not throw a fatal error
 * EasyTimeline has a system message to track category description
 * MediaWiki Core's UploadFromUrl::isAllowedHost has tests
 * Google Drive to Commons tool allows removing files after selection
   before uploading, and has a redesigned 'upload complete' screen
 * Hashtags tool allows charts to be downloaded as images
 * MobileFrontend extension allows turning on the lead paragraph in
   other namespaces and the nav menu drawer received a CSS shadow
 * DynamicPageList extension uses page images as the image in gallery
   mode for pages which are not in the File namespace
 * MassMailer tool has improved internationalization, its alerts are
   dismissable, and is integrated with Translatewiki.net
 * Map of Monuments tool can filter by country and language
 * Wiki Education Dashboard Android App has better screenshots and a
   placeholder for empty screens
 * WikiEduDashboard has a git pull hook to update gems and packages,
   and its ArticleViewer adds appropriate styling for Wikidata
 * Music on Wikimedia pages was transcribed to LilyPond 9 times
 * 4 templates on English Wikipedia received Documentation
 * A web app to showcase a variety of tools hosted on Wikimedia
   Toolforge was created
 * meta:Research_on_open_source_team_communication_tools was expanded
 * Hackathons of other FOSS orgs were researched, to improve ours
 * 14 text files in MediaWiki core's /doc got converted to Markdown
 * Logos designed for VideoCutTool tool, the MediaWiki FormWizard
   Extension, the Friends of the Docs working group, and the Google
   Drive to Wikimedia Commons Uploader tool
 * Designs for "Personal Space Needed" and "Wikimedia Friends of the
   Docs" stickers created
 * HD logos were added for several Wikimedia project websites

Thanks for helping making free knowledge available to everybody. <3

On behalf of the org admins,
andre

[1] https://www.mediawiki.org/wiki/Google_Code-in/Statistics

-- 
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/


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

[Wikitech-l] TechCom Radar 2020-01-22

[Kate Chapman]

Hi All,

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

* RFC Approved: Hook container with strong types and DI


* Reviewed discussion on Standalone service to evaluate user-provided
regular expressions, summary available here:


* New RFC under discussion: Allow extensions to register handlers with
factories without the use of global variables.


* Further discussion on RFC: Adopt a modern JavaScript framework for
use with MediaWiki. 
scheduling IRC meeting soon

* No TechCom meeting this week

You can also find our meeting minutes at


See also the TechCom RFC board
.

If you prefer you can subscribe to our newsletter here


Thanks,
Kate

--
Kate Chapman
Senior Program Manager, Core Platform
Wikimedia Foundation
kchap...@wikimedia.org

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