Originally posted on mastodon.technology.
What's the value in using Linux packages for your software vs installing from git? https://lists.debian.org/debian-devel/2018/06/msg00097.html explained it really well. The explanation I tell people for MediaWiki is that if you want a wiki that just works and would like to forget about administering it - use the Debian package. If you want to customize and love it - install from a tarball/git.
Originally posted on mastodon.technology.
Nothing like having someone rush into your precinct at 7:58pm, just in time to vote.
Volunteering was a stressful blast once again.
git.legoktm.com is now open for hosting free software projects, providing git hosting, issue trackers, and basic wiki functionality. It runs the free software Gogs: "a painless self-hosted Git service".
You're welcome to host any freely licensed projects on git.legoktm.com.
I've been running git.legoktm.com for two years now, mainly using it to host personal projects and things a few friends asked for. I think others will find a friendly git hosting service useful. Nearly all of my major projects can be found on git.legoktm.com, whether they are the canonical repository, or just a mirror (automatically sychronizing about every 10 minutes).
In terms of privacy, you will need to confirm your email before being able to join the site. I collect minimal server logs, and only use IP address information for anti-abuse measures. Mail is handled by FastMail. You should be able to delete your data at any time. Backups are currently running weekly, but I can increase frequency if usage/demand increases.
If you're comfortable with your current git host, feel free to set up a mirror! Git is a great distributed protocol, and mirroring helps increase the right to fork.
If you have any questions, you can contact me on Mastodon, email, IRC, or the git.legoktm.com support tracker.
Originally posted on mastodon.technology.
Your IRC channel can only be considered diverse once you have members whose nicks start with every letter of the alphabet.
CoverMe, hosted on Wikimedia Toolforge
Test coverage is a useful metric, but it can be difficult to figure out exactly where to start. That's where CoverMe is useful - it sorts functions by how often they're called on Wikimedia production servers, and then displays their coverage status.
Try it out! You can filter by Git repository and entry point (index.php, load.php, etc.). So if you look at the api.php entry point, you'll see mostly API related code. If I look at the Linter extension, I can see that the RecordLintJob::run is well covered, while ApiRecordLint::run is not covered at all. If some extensions simply aren't called that frequently, there might not be any function call data at all.
The function call data comes from the daily Xenon logs that are used for profiling FlameGraphs, and the CI test coverage data. CoverMe fetches updated data on the hour if it's available.
The source code is published on Phabricator and licensed under the AGPL v3, or any later version.
Originally posted on mastodon.technology.
Preview of a project I've been working on: identifying the most valuable parts of our code to write tests for by sorting test coverage data by number of times the function is called in production.
#mediawiki #testcoverage
