I know it has been annoying a couple of people other than me, so now that I've learned how to make it work I'll share the knowledge here.
tl;dr: Star the repositories. No, seriously. (And yes, you need to star each extension repo separately.)
(Is there a place on mw.org to put this tidbit on?)
------- Forwarded message -------
From: "Brian Levine" <support(a)github.com> (GitHub Staff)
To: matma.rex(a)gmail.com
Cc:
Subject: Re: Commits in mirrored repositories not showing up on my profile
Date: Tue, 09 Jul 2013 06:47:19 +0200
Hi Bartosz
In order to link your commits to your GitHub account, you need to have some association with the repository other than authoring the commit. Usually, having push access gives you that connection. In this case, you don't have push permission, so we don't link you to the commit.
The easy solution here is for you to star the repository. If you star it - along with the other repositories that are giving you this problem - we'll see that you're connected to the repository and you'll get contribution credit for those commits.
Cheers
Brian
--
Matma Rex
We just released a new version of Research:FAQ on Meta [1], significantly
expanded and updated, to make our processes at WMF more transparent and to
meet an explicit FDC request to clarify the role and responsibilities of
individual teams involved in research across the organization.
The previous version – written from the perspective of the (now inactive)
Research:Committee, and mostly obsolete since the release of WMF's open
access policy [2] – can still be found here [3].
Comments and bold edits to the new version of the document are welcome. For
any question or concern, you can drop me a line or ping my username on-wiki.
Thanks,
Dario
[1] https://meta.wikimedia.org/wiki/Research:FAQ
[2] https://wikimediafoundation.org/wiki/Open_access_policy
[3] https://meta.wikimedia.org/w/index.php?title=Research:FAQ&oldid=15176953
*Dario Taraborelli *Head of Research, Wikimedia Foundation
wikimediafoundation.org • nitens.org • @readermeter
<http://twitter.com/readermeter>
Hi,
On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote:
> We will be holding this brownbag in 25 minutes. The Bluejeans link has
> changed:
>
> https://bluejeans.com/396234560
I'm not familiar with bluejeans and maybe have missed a transition
because I wasn't paying enough attention. is this some kind of
experiment? have all meetings transitioned to this service?
anyway, my immediate question at the moment is how do you join without
sharing your microphone and camera?
am I correct thinking that this is an entirely proprietary stack
that's neither gratis nor libre and has no on-premise (not cloud)
hosting option? are we paying for this?
-Jeremy
Hello,
can someone to update list https://phabricator.wikimedia.org/P10500 which
contains repositories which haven't mediawiki/mediawiki-codesniffer.
I found in list that much repositories are empty, and repositories which
aren't available on Gerrit.
So, can someone please update this list of repositories (in
mediawiki/extensions) which haven't mediawiki/mediawiki-codesniffer, but at
least, contains one PHP file. or to provide me command with which I can
update list when I want, so I don't need to request it every time.
Best regards,
Zoran.
P. S.: Happy weekend! :)
Last week, we had a Indic Wikisource Proofreadthon 2020 event. see
here for full details
https://meta.wikimedia.org/wiki/Indic_Wikisource_Proofreadthon_2020
Though I did not participate in this event, (feels sad for this. Life
is too messy nowadays), I thought to build a small tool to give report
on any wikipedia user’s contribution on a given wikisite for a given
date range.
It may help to calculate, measure, decide on the contributions for
such competitions.
Mediawiki has a good API to fetch user contributions.
https://www.mediawiki.org/wiki/API:Usercontribs
Get all edits by a user.
https://www.mediawiki.org/wiki/Special:MyLanguage/API:Usercontribs
For my wonder, there was a sample python code on the same page.
The code gave only 500 results. I wrote a loop to get the data batch
by batch till all the data is received.
Published the tool here –
https://github.com/tshrinivasan/wiki_user_contributions_report
How to run?
python3 get_user_contributions.py <language> <wikisite> <username>
<start_date> <end_date>
This will give the data as a CSV file. Used a csv-to-html converter
utility to convert this to a web page with all the data in a sortable
table.
For my wonder, my friend Dinesh Karthik, converted this as a nice web
application with flask, dash and hosted in heroku.
https://wiki-user-contributions.herokuapp.com/
Source : https://github.com/Dineshkarthik/wiki-user-contributions
Thanks to Info-farmer for providing the idea, Bartosz Dziewoński on
wikipedia mailing list for answering all my questions, Dinesh for
making a web application quickly.
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
is a good place to ask any tech questions regarding wikipedia.
Thanks to all wikisource contributors for the event and in general.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com
Hi everyone,
On the French Wikipedia we're currently reworking our help page about
redirects and some of us would like to include a section about common
misconceptions, especially those described at
<https://en.wikipedia.org/w/index.php?title=Wikipedia:Tools/Navigation_popup…>.
However one user who's used to "fix" redirects is strongly opposed
because "this page is from 2006" and it's "unsourced".[1]
So I would like to ask the sysadmins from Wikimedia and the MediaWiki
developers who are following this mailing list: is this page created in
2006 still true and relevant in 2020?
Thank you.
--
Kind regards,
Thibaut Payet
[[User:Thibaut120094]]
[1]
<https://sigma.toolforge.org/usersearch.py?name=Alaspada&page=Discussion_aid…>
This is the weekly TechCom board review. If there are additional topics for
TechCom to review, please let us know by replying to this email. However,
please keep discussion about individual RFCs to the Phabricator tickets.
This week, the meeting is async, so we'll be replying to the email as
well, *feel
free to join in*!
Activity since Wednesday 2020-11-25 on the following boards:
https://phabricator.wikimedia.org/tag/techcom/https://phabricator.wikimedia.org/tag/techcom-rfc/
Committee inbox:
- Automatically index extensions in Codesearch
<https://phabricator.wikimedia.org/T268328> is still in the inbox, no
activity since last week's discussion
- Create WikiTeq group on Gerrit
<https://phabricator.wikimedia.org/T267213> is now more clear (see note
from Daniel <https://phabricator.wikimedia.org/T267213#6653536> to
discuss, which we should do here)
Committee board activity:
- General ParserCache service class for large "current" page-derived data
<https://phabricator.wikimedia.org/T227776> was declined by Daniel, see
his reasoning there
New RFCs: (none)
Phase progression: (none)
IRC meeting request: (none)
Other RFC activity:
- RFC: Re-evaluate librsvg as SVG renderer for WMF wikis
<https://phabricator.wikimedia.org/T40010:> saw more conversation
- RFC: Discourage use of MySQL's ENUM type
<https://phabricator.wikimedia.org/T119173> Amir points out the need to
overhaul all db documentation (I agree, could we have a doc sprint about
this?) including policies
- RFC: Amendment to the Stable interface policy, November 2020
<https://phabricator.wikimedia.org/T268326> has a suggestion/question
about clarifying default status and deprecation procedure
- RFC: Store WikibaseQualityConstraint check data in persistent storage
<https://phabricator.wikimedia.org/T214362> WMDE calls for help from
TechCom and the Platform team to collaborate here. See Adam Shorland's
comment about putting it through the new Technical Decision Making Process
- RFC: Expand API title generator to support other generated data
<https://phabricator.wikimedia.org/T263841> Carly Bogen is asking for
clarity on the need for a steward. Timo's comment
<https://phabricator.wikimedia.org/T263841#6617970> on the task indeed
seem to contradict his note from last week's grooming email. Timo, would
you please clarify.
Hi everyone,
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds
office hours the first Wednesday of each month. Come talk to us about
anything related to Wikimedia search, Wikidata Query Service, Wikimedia
Commons Query Service, etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, December 2nd, 2020
Time: 16:00-17:00 GMT / 08:00-09:00 PST / 11:00-12:00 EST / 17:00-18:00 CET
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vyc-jvgq-dww
Join by phone in the US: +1 786-701-6904 PIN: 262 122 849#
Hope to talk to you in a week!
—Trey
Trey Jones
Sr. Computational Linguist, Search Platform
Wikimedia Foundation
UTC-5 / EST
As per the MediaWiki version lifecycle,[1] I would like to announce the
formal end of life (EOL) of MediaWiki 1.34 as of today, Monday November 30,
2020.
This means that MediaWiki 1.34 will no longer receive maintenance or
security backports. It is therefore strongly discouraged that you continue
to use it.
It is recommended to upgrade to MediaWiki 1.35, the current Long Term
Support (LTS) version which is not due to become EOL until September 2023.
The legacy Long Term Support version of MediaWiki, MediaWiki 1.31, is older
and downgrading is not supported.
MediaWiki 1.35 bumps the required PHP version from 7.2.9 in 1.34 (which is
unsupported upstream), to PHP 7.3.19 or later.
Thanks!
Sam Reed
[1] https://www.mediawiki.org/wiki/Version_lifecycle
This is the weekly TechCom board review in preparation of our meeting on
Wednesday. If there are additional topics for TechCom to review, please let
us know by replying to this email. However, please keep discussion about
individual RFCs to the Phabricator tickets.
Activity since Monday 2020-11-02 on the following boards:
https://phabricator.wikimedia.org/tag/techcom/https://phabricator.wikimedia.org/tag/techcom-rfc/
Committee inbox:
- T268328: Automatically index extensions in Codesearch
<https://phabricator.wikimedia.org/T268328>
- Daniel is raising that people effectively use Codesearch to guide
deprecation efforts under theStable Interface policy. As such, we should
define what inclusion criteria it has (or should have), and simply or
document how to implement that in practice through adding and removing
repositories from its index (esp those not hosted by Wikimedia).
- T267085 <https://phabricator.wikimedia.org/T267085>: Clarify
deprecation of method overrides
- A question about the stable interface policy.
Committee board activity:
- T175745 <https://phabricator.wikimedia.org/T175745>: Do not overwrite
edits when conflicting with self
- Some renewed interest on this question about how MW should handle
when e.g. someone starts editing the same page from multiple
tabs and then
submits those edits.
- T227776 <https://phabricator.wikimedia.org/T227776>: General
ParserCache service class
- Addshore asking for an update.
New RFCs:
- T268326: RFC: Amendment to the Stable interface policy (Nov 2020)
<https://phabricator.wikimedia.org/T268326>
- Proposal by Daniel, to:
- … fill some gaps (e.g. traits, and member fields).
- … allow for removal without (released) deprecation if it is
unused in code we know about and is considered "maintained".
Input welcome.
Phase progression:
- T266866 RFC <https://phabricator.wikimedia.org/T266866>: Bump Basic
browser support to require TLS 1.2 for MediaWiki core
- Ed lists which Web APIs and other browser capabilities would become
safe to use in the base layer (HTML/CSS), as well as some JS
features that
will automatically become available to Grade A.
- Ed confirmed TLS 1.2 mapping to browser names/versions.
- Moved to Phase 3: Explore.
- T260330 RFC: PHP microservice for containerized shell
<https://phabricator.wikimedia.org/T260330>
- Moved to Last Call last week, until 2 December (next week).
- Tim answered and added a section to clarify the backwards
compatible nature of the PHP interface in core, for third-parties that
would not or have not installed Shellbox.
- T259771: RFC: Drop support for database upgrade older than two LTS
<https://phabricator.wikimedia.org/T259771>
- Last week's concerns about detection and failure prevention have
been answered by Amir.
- The Platform Engineering Team has filled the ownership gap for this
policy.
- Moved to Phase 4: Tune.
IRC meeting request:
- Later today (Wed 25 Nov), this RFC will be discussed in
#wikimedia-office on Freenode IRC:
RFC: Provide mechanism for configuration sets for development and tests
https://phabricator.wikimedia.org/T267928
Other RFC activity:
- T263841 RFC <https://phabricator.wikimedia.org/T263841>: Expand API
title generator to support other generated data
- Rescoped from potential software change to policy update.
- Awaiting resourcing from core API steward to confirm support, risk,
compatibility as proposed.
- T250406 RFC: Hybrid extension management
<https://phabricator.wikimedia.org/T250406 >
- Conversation about what we would need to commit to for WMF
software, and seeking placing and approval of said resourcing.
- T119173: RFC: Discourage use of MySQL ENUM type
<https://phabricator.wikimedia.org/T119173>
- Next step is for the consensus to be turned into concrete wording
for the policy.
- T40010: RFC: Re-evaluate librsvg as SVG renderer for WMF wikis
<https://phabricator.wikimedia.org/T40010:>
- Some general clarifications, and statistics from production.
-- Timo