Wikitech-l

wikitech-l@lists.wikimedia.org

9 participants
23105 discussions

Anchorage Length of Rebars
by activityonline75＠gmail.com 28 Jun '24

28 Jun '24

Adequate anchorage length of rebars is a primary requirement for the safety of a member,especially a beam.When Analysis including seismic, structural design, manual design etc is important, proper detailing of a structure is equally important. https://www.civilera.com/post/anchorage

1 0

Anchorage Length of Rebars
by activityonline75＠gmail.com 28 Jun '24

28 Jun '24

1 0

Civil engineering online courses
by activityonline75＠gmail.com 28 Jun '24

28 Jun '24

Civilera offers world class Structural Engineering courses in a Structural consulting perspective covering basics,manual designs & software alike. We focus on ETABS Tutorials StaadPro Training, Revit structures, Foundation design using SAFE. We enable students to have a career in structures & help experienced engineers in other fields to shift their career to structural engineering. All civil engineering online courses are available in different payment plans. visit here for full info: https://www.civilera.com

1 0

How to make commits from mirrored Wikimedia repos show up on your GitHub profile
by Bartosz Dziewoński 27 Jun '24

27 Jun '24

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

3 3

Article source code style guide
by Bináris 27 Jun '24

27 Jun '24

Hi, is there anywhere a $subject? My first question is: is it better to leave an empty line under section titles or not? I would like to see pros and cons. Is there a consensus for preferred way? (I think source code style guides are primarily within the scope of programmers and not in that of users without programming experience, that's why I ask here.) -- Bináris

4 3

Maintenance release: 1.39.8 / 1.40.4 / 1.41.2 / 1.42.1
by Sam Reed 27 Jun '24

27 Jun '24

1 0

Announcing MediaWiki 1.42.0
by Mateus Santos 27 Jun '24

27 Jun '24

I am happy to announce the availability of the general release of MediaWiki 1.42! Tarballs have already been uploaded, and the git tag has been pushed. Thanks to everyone who helped out with this release, especially thanks to those who tested out the release candidate and provided feedback, as well as the developers who worked on fixes for the 1.42 final release. To see what's changed in 1.42, see the release notes file.[0] If you encounter any issues, please file a task.[1] You can see open tasks for the branch on Phabricator.[2] MediaWiki 1.42 is the first release of MediaWiki to formally drop PHP 7.4 and PHP 8.0 support; you should use PHP 8.1, 8.2, or 8.3. We also now have dropped support for Composer 1.x, and require Composer 2.x for those systems using it. MediaWiki 1.42 is due to be supported until the end of June 2025. It is noted that MediaWiki 1.40 is due to become end-of-life at the end of June 2024. A formal announcement will be made later this month, and will coincide with the next security and maintenance release which is also scheduled for the of June 2024. === Changes since MediaWiki 1.42.0-rc.0 === * Localisation updates. * wrapOldPasswords: Improve progress output and decrease batch size. * (T365060) Serialization test cases: fix filename after ParserOutput namespacing. * Use virtual domain when running update maintenance scripts. * (T361367) ApiFeedWatchlist: Fix handling of array parameters. * (T366130) EncryptedPassword: Store default parameters as strings. Release notes: [0] https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/… Bug report form: [1] https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tags=MW-1.42-… Open Bugs: [2] https://phabricator.wikimedia.org/tag/mw-1.42-release/ ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.0.tar.gz https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.0.zip Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.42/mediawiki-core-1.42.0.tar.gz https://releases.wikimedia.org/mediawiki/1.42/mediawiki-core-1.42.0.zip Patch to previous version (1.42.0-rc.0): https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.0.patch.gz https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.0.patch.zip GPG signatures for the above: https://releases.wikimedia.org/mediawiki/1.42/mediawiki-core-1.42.0.tar.gz.… https://releases.wikimedia.org/mediawiki/1.42/mediawiki-core-1.42.0.zip.sig https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.0.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.0.zip.sig https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.0.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.0.patch.zip.sig Public keys: https://www.mediawiki.org/keys/keys.html

1 0

Empowering Businesses with Innovative Digital Solutions
by consultancyservices393＠gmail.com 27 Jun '24

27 Jun '24

MCS offers software consulting and development services, delivering digital transformation. Our services includes web application development, mobile application development, chatbot development, Data Science & AI Development Services, MVP Development, End-to-End IT Strategy & Consulting and implementation support, intuitive digital solutions, and leveraging the latest technologies. visit here: https://www.mayuraconsultancy.com

1 0

Re: How to make commits from mirrored Wikimedia repos show up on your GitHub profile
by 沈澄心 27 Jun '24

27 Jun '24

Hi, may I ask how to join the wikimedia github "organization"? Thanks! 沈澄心 dringsim(a)qq.com ---Original--- From: "Brian Wolff"<bawolff(a)gmail.com> Date: Tue, Jun 18, 2024 08:45 AM To: "Wikitech-l"<wikitech-l(a)lists.wikimedia.org>gt;; Subject: [Wikitech-l] Re: How to make commits from mirrored Wikimedia repos show up on your GitHub profile The other solution is to ask to be added as a member of the wikimedia "organization". On Monday 17 June 2024, Bartosz Dziewoński <matma.rex(a)gmail.com> wrote: I'm digging up this ten-year-old message, because you may want to know that this solution no longer works: GitHub no longer shows your imported contributions in your starred repositories on your profile. This changed some time in April or May. You can follow the conversation about it here: https://github.com/orgs/community/discussions/128895 On Tue, 9 Jul 2013 at 22:06, Bartosz Dziewoński <matma.rex(a)gmail.com> wrote: > > 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 -- Bartosz Dziewoński _______________________________________________ Wikitech-l mailing list -- wikitech-l(a)lists.wikimedia.org To unsubscribe send an email to wikitech-l-leave(a)lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

1 0

Gerrit upgrade Wednesday June 26th at 8am UTC
by Antoine Musso 26 Jun '24

26 Jun '24

Hello, I will be *upgrading Gerrit* from the 3.9 series to the 3.10 series. I have scheduled the upgrade for *Wednesday 26th at 8:00am UTC*. It is immediately after the UTC morning backport & config window. The upgrade requires the Gerrit service to be stopped for the duration of the upgrade. Given we do not need to reindex all the changes, the downtime should be just a few minutes. Gerrit 3.10 brings: * Rebasing of merge commits from the web interface * Updating author and committer from the UI * Less email notifications (see the dedicated section in release notes <https://www.gerritcodereview.com/3.10.html#less-email-notifications>) The release notes: https://www.gerritcodereview.com/3.10.html The upgrade task: https://phabricator.wikimedia.org/T367419 Deployment calendar entry <https://phabricator.wikimedia.org/T367419> Antoine "hashar" Musso Wikimedia Release Engineering

1 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l