date:20200824

[Wikitech-l] Wikimedia's GitHub org help

2020-08-24 Thread Tyler Cipriani

Hi all!

If you've never created a repo or fork on the Wikimedia GitHub
organization you can skip this email.

I know that some repos are developed on our GitHub org for reasons.
What is developed on our GitHub org? How many things are actively
being developed on GitHub org? I have no idea :)

I recently realized that there's not a great way to figure this
out[0], but I've been able to narrow the scope a bit. Now I have a
list of repos that are (a) in our GitHub org and (b) not in our Gerrit
that I could use some help sorting through[1].

== Help, please ==

* Look through repos on The List™[1]

If your repos are on the list, for each of your repos either:

* Archive or Delete it if it's no longer maintained or empty/useless,
respectively (and remove them from the list on mw.org)[2]

Or:

* put a "{{tick}}" in the "Active" column on the list on mw.org

== Why==

In a more perfect future we could add the "mirror"[3] tag to repos on
GitHub that are mirrored from Gerrit (with a link to their canonical
repo locations; for example, gnome-deskop has this[4] and I'm very
jealous).

Hopefully, this will help folks wanting to contribute -- either a
Wikimedia GitHub repo is a mirror (in which case there's a link to
Gerrit in the description) or it's actively being developed on GitHub.

<3
-- Tyler

[0]: 
[1]: 
[2]: 

[3]: 

[4]: 

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

Re: [Wikitech-l] Upgrading mailman (the software behind mailing lists)

2020-08-24 Thread Amir Sarabadani

I think it's because mailman3 doesn't need something like listadmin
anymore. It provides a REST API that you can use to achieve the same
functionality in a couple lines of code:
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.html

HTH

On Mon, Aug 24, 2020 at 1:30 AM Michael Schönitzer <
michael.schoenit...@wikimedia.de> wrote:

> A sad side effect of the upgrade will probably be that listadmin[1] will
> break. Does anyone know an alternative?
>
> [1] https://sourceforge.net/projects/listadmin/
>
> Am So., 9. Aug. 2020 um 23:13 Uhr schrieb David Gerard  >:
>
> > In fairness, pipermail archives were always a bit shaky - on the
> > occasions when an email's had to be removed from the archive
> > previously, it's messed up the URLs of all the other emails in that
> > month's archive.
> >
> > But let's say it would be *nice* not to mess up the public archive
> > URLs if feasible :-)
> >
> >
> > - d.
> >
> >
> > On Sun, 9 Aug 2020 at 21:19, Amir Sarabadani 
> wrote:
> > >
> > > hmm, Links of archived discussions in private mailing lists are not as
> > > important as the ones in public lists, we definitely should migrate
> > public
> > > mailing lists first and after that we can migrate any private mailing
> > list
> > > that is okay with their links being broken (and then we remove those
> old
> > > archives to make it unaccessible to public). It probably means we need
> to
> > > keep mailman2 around for a while.
> > >
> > > On Sun, Aug 9, 2020 at 9:38 PM AntiCompositeNumber <
> > > anticompositenum...@gmail.com> wrote:
> > >
> > > > I would agree that it would be a good solution, except for the next
> > > > bullet in the same document:
> > > > "The above mechanism won’t work for private archives since the
> > > > archives are gated with password and without a Mailman 2 list, there
> > > > is no password. You can however import them to Mailman 3."
> > > >
> > > > Since keeping private lists private is also a requirement, that
> pretty
> > > > much means rolling our own auth system on top of Mailman 3 or
> creating
> > > > a bunch of HTTP redirect rules.
> > > >
> > > > On Sun, Aug 9, 2020 at 3:31 PM Amir Sarabadani 
> > > > wrote:
> > > > >
> > > > > According to the upgrade guide (
> > > > >
> > https://docs.mailman3.org/en/latest/migration.html#other-considerations
> > > > ):
> > > > > "If you need your URLs for Mailman 2 archives to work, you can keep
> > the
> > > > > HTML files generated for the archives around and your web server
> > > > > configuration for the archives intact (possibly with a notice to
> > viewers
> > > > > that it is now a read-only archive, see this list
> > > > >  for example)."
> > > > >
> > > > > Here's an example: https://mail.python.org/pipermail/security-sig/
> > > > (with a
> > > > > notice).
> > > > >
> > > > > It means, the old archives will stay the same (and
> > accessible/searchable
> > > > > with the new interface as well) but new mails won't get added there
> > to
> > > > the
> > > > > old archives. I think that's a good compromise.
> > > > >
> > > > >
> > > > > On Sun, Aug 9, 2020 at 9:19 PM David Gerard 
> > wrote:
> > > > >
> > > > > > yes - those links are thrown around as if they're archival. How
> > will
> > > > > > the change affect links to past messages? Will someone need to
> > > > > > construct a redirect farm?
> > > > > >
> > > > > >
> > > > > > - d.
> > > > > >
> > > > > > On Sun, 9 Aug 2020 at 19:54, AntiCompositeNumber
> > > > > >  wrote:
> > > > > > >
> > > > > > > Glad to hear this is moving forward!
> > > > > > >
> > > > > > > Keeping archive links working, for both public and private
> lists,
> > > > > > > should be a requirement. There's a lot of institutional
> knowledge
> > > > > > > stored in the mailing list archives, and it's very important to
> > keep
> > > > > > > that around.
> > > > > > >
> > > > > > > ACN
> > > > > > >
> > > > > > > On Sun, Aug 9, 2020 at 1:05 PM Zoran Dori <
> > zorandori4...@gmail.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > Hello,
> > > > > > > > this looks great. Especially because of "mobile friendly"
> > function.
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Zoran Dori
> > > > > > > > Volunteer on Wikimedia Foundation's projects
> > > > > > > > E: zorandori4...@gmail.com
> > > > > > > > W: kizule.tk
> > > > > > > > I: iamkizule 
> > > > > > > > ___
> > > > > > > > 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
> > > > > >
> > > > > > ___
> > > > > > Wikitech-l mailing list

[Wikitech-l] No train next week; no deployments next Tuesday

2020-08-24 Thread Tyler Cipriani

Hi all

There is a planned switchover to our secondary datacenter scheduled for
Tuesday, September 2nd 2020.

To avoid creating problems for our SREs we'll be skipping the train for
next week -- the week of 2020-08-31 -- and not doing any deployments the
day of the switchover -- 2020-09-01.

The deployment calendar is up-to-date[1].

Thanks!
-- Tyler


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

[Wikitech-l] [Wikimedia Technical Talks] Wednesday on 26 August 2020 at 17:00 UTC

2020-08-24 Thread Sarah R

Hi Everyone,

It's time for Wikimedia Tech Talks 2020 Episode 7! This talk will take
place next Wednesday on 26 August 2020 at 17:00 UTC.

Title: openZIM/Kiwix ETL toolchain for Wikipedia dumping

Speaker: Emmanuel Engelhart

Summary:

Enjoying Wikipedia offline wherever, whenever is easy with Kiwix. But
behind the scenes, a bunch of tools are needed to make it work. From
article selection, to dump publishing through scraping, optimization, and
packaging: here is a quick overview of how we do it.

The link to the Youtube Livestream can be found here:


https://www.youtube.com/watch?v=9rFWaPSP3AM

During the live talk, you are invited to join the discussion on IRC at
#wikimedia-office

You can browse past Tech Talks here:
https://www.mediawiki.org/wiki/Tech_talks

If you are interested in giving your own tech talk, you can learn more here:
https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Tech_talks

General WMF Slack channel and in #wikimedia-staff and #wikimedia-office IRC

Wikimedia Tech Talks 2020 will be happening in 30 minutes at 17:00 UTC.


-- 
Sarah R. Rodlund
Senior Technical Writer, Developer Advocacy

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

Re: [Wikitech-l] New member

2020-08-24 Thread Pavithra Eswaramoorthy

Hi Rahul,


Welcome! You can learn more about GSoC and other Wikimedia outreach programs 
here: https://www.mediawiki.org/wiki/Outreach_programs


Some resources to help you get started:

  *   https://www.mediawiki.org/wiki/New_Developers
  *   https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker
  *   https://www.mediawiki.org/wiki/Good_first_bugs

Please feel free to reach out with any questions or doubts. You can also join 
us on Zulip here: https://wikimedia.zulipchat.com


A friendly note that we encourage inclusive language, see https://heyguys.cc/ :)


Happy contributing!

Best,

Pavithra


From: Wikitech-l  on behalf of Rahul 
Pawar 
Sent: 24 August 2020 20:35
To: For developers discussing technical aspects and organization of Wikimedia 
projects 
Subject: [Wikitech-l] New member

Hello Guys!!
I'm Rahul Pawar a B.tech second-year student at Visvesvarya National
Institute of Technology, Nagpur, India. I am a newbie but have tried
frontend mentor challenge, 2-star coder in Codechef, Gold medal in C, Cpp,
Python in hackerRank. I'm interested in working with this organization and
even participate in GSOC 2021. SO any mentor out there to guide me.
Thanks in advance.
Regards
Rahul Pawar
___
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

[Wikitech-l] New member

2020-08-24 Thread Rahul Pawar

Hello Guys!!
I'm Rahul Pawar a B.tech second-year student at Visvesvarya National
Institute of Technology, Nagpur, India. I am a newbie but have tried
frontend mentor challenge, 2-star coder in Codechef, Gold medal in C, Cpp,
Python in hackerRank. I'm interested in working with this organization and
even participate in GSOC 2021. SO any mentor out there to guide me.
Thanks in advance.
Regards
Rahul Pawar
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Scrum of scrums/2020-08-19

2020-08-24 Thread Deb Tankersley

Hello,

This email contains updates for last week - August 19, 2020, with apologies
for the lateness.

For the HTML versions, see:
https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-08-19

Cheers,

Deb





*= 2020-08-19 =*

== Product ==

=== Web ===
* Updates:
** '''Summary''': Vue.js-focused week.
** [[Reading/Web/Desktop Improvements|Desktop Improvements Project (Vector
/ DIP)]]:
*** [[phab:T258493|[Spike 8hrs] "Use Legacy Vector" is not working as a
global preference]]
*** [[phab:T258465|[Bug] Sidebar Expand/Collapse button impacted by Narrow
Width]]
*** [[phab:T255727|Make collapsible sidebar persistent for logged-in users]]
*** [[phab:T249363|Move the existing search to the header in preparation
for Vue.js search development]]
*** [[phab:T251817|[Dev] Allow extensions to update the footer without
resorting to SkinTemplateOutputPageBeforeExec hook]]
*** [[phab:T244392|Vue.js search case study]]:
 See [[Reading/Web/Desktop Improvements/Vue.js case study/Status
log|weekly status updates]].
** Mobile website (MinervaNeue / MobileFrontend):
*** [[phab:T260155|PHP Fatal error: Uncaught Error: Call to undefined
method TitleValue::isSubpage() in
/srv/mediawiki/php-1.36.0-wmf.4/skins/MinervaNeue/includes/Skins/SkinUserPageHelper.php:55
in
/srv/mediawiki/php-1.36.0-wmf.4/skins/MinervaNeue/includes/Skins/SkinUserPageHelper.php
on line 55]]
*** [[phab:T231160|HtmlFormatter incorrectly removes partial classname
matches in "xenomobile" or "not-an-navbox"]]
*** [[phab:T214647|[EPIC] Re-define the contract for displaying drawers and
overlays in MobileFrontend]]
*** [[phab:T212465|[EPIC] None of our View's should exhibit 2 levels of
inheritance]]
*** [[phab:T258096|Regression: Nested references do not open if user clicks
on [ or ] (which are wrapped in span)]]
*** [[phab:T240622|[Technical debt payoff] Remove InlineDiffFormatter and
InlineDifferenceEngine from MobileFrontend]]
** Standardization
*** [[phab:T256520|Consider 'normalize' stylesheet RL module]]
*** [[phab:T259906|Add 'volumeUp' icon in OOUI]]
** Miscellaneous
*** [[phab:T224985|Rename Special:ElectronPdf to Special:Download as Pdf or
Special:Export as Pdf]]

== Technology ==

=== Search Platform ===
* Blocked by:
* Blocking:
* Updates ''(long list of updates, we were lagging behind in reporting
those)'':
** Integrate Wikimedia Event Utilities with discovery-parent-pom -
https://phabricator.wikimedia.org/T260375
** Search does not return exact title match -
https://phabricator.wikimedia.org/T257922
** Querying WCQS should allow me to use prefixes for MediaInfo items -
https://phabricator.wikimedia.org/T258625
** Gather statistics on head and tail query distribution on Commons -
https://phabricator.wikimedia.org/T252544
** Slow indexing of Lexemes for wbsearchentities -
https://phabricator.wikimedia.org/T240328
** Create spreadsheet of last 90 days of Commons search queries -
https://phabricator.wikimedia.org/T257361
** Validate and fix TTL dumps of SDoC -
https://phabricator.wikimedia.org/T251496
** Create a Examples Page for WCQS -
https://phabricator.wikimedia.org/T258489
** v: prefix not correctly prefixed in Wikibase when using entitysource
config and extra prefixes -https://phabricator.wikimedia.org/T258507
** CirrusSearch throws an error on several wikis when searching for
"intitle:/regex/" -https://phabricator.wikimedia.org/T250810
** Access restriction for SPARQL Endpoint for Commons -
https://phabricator.wikimedia.org/T251498
** UI for SPARQL Endpoint for Commons -
https://phabricator.wikimedia.org/T251514


--

deb tankersley (she/her)

sr program manager, engineering

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

[Wikitech-l] Wikimedia's GitHub org help

Re: [Wikitech-l] Upgrading mailman (the software behind mailing lists)

[Wikitech-l] No train next week; no deployments next Tuesday

[Wikitech-l] [Wikimedia Technical Talks] Wednesday on 26 August 2020 at 17:00 UTC

Re: [Wikitech-l] New member

[Wikitech-l] New member

[Wikitech-l] Scrum of scrums/2020-08-19

7 matches

Site Navigation

Mail list logo

Footer information