#microformats 2024-09-17

2024-09-17 UTC
#
jacky https://ruby.microformats.io/ looks like it's down?
#
[tantek] ugh it appears so 😞 https://downforeveryoneorjustme.com/ruby.microformats.io?proto=https
barnaby, [qubyte], [fluffy]1, [KevinMarks], ms_boba[d], [schmarty], [snarfed] and to2ds joined the channel; pcarrier left the channel
#
[tantek] [aaronpk] do you have the ability to change the setup of http://microformats.io subdomains?
#
[tantek] Not sure how to fix the ruby.microformats problem noted above (it's still down)
[dave] joined the channel
#
aaronpk that is running on heroku, so we need to look into what's wrong
#
aaronpk turns out heroku dropped support for the ruby version it was using
#
aaronpk speaking of admin tax
barnabywalters joined the channel
#
aaronpk who wants a little project
#
aaronpk we need to get this and its dependencies brought up to date with a modern ruby version https://github.com/microformats/microformats-parser-website-ruby
#
[tantek] ^ who is a ruby dev here who understands this?
#
[tantek] (parallels the CLI topic in #indieweb-dev ironically)
#
[mattl] I can take a look, can you assign a GitHub issue to me?
#
aaronpk https://github.com/microformats/microformats-parser-website-ruby/issues/84
#
Loqi [preview] [aaronpk] #84 Upgrade Ruby and dependencies
#
[mattl] thanks
#
[mattl] any way you can assign it to me?
#
aaronpk looks like i will need to add you to the org to do that
[jgarber] joined the channel
#
[jgarber] hoo boy yeah that repo needs love
#
[mattl] yeah, add me to the org that’s fine with me.
#
[jgarber] (Ruby dev reporting for duty 🫡 )
#
aaronpk you should have an invite
#
[mattl] resisting the natural urge to troll:
#
[mattl] https://chat-uploads.indieweb.org/files/2024/09/microformats-20240917-161452-screenshot_2024-09-17_at_12.14.36.png
#
[mattl] i’m in
#
Loqi yea!
[pfefferle] joined the channel
#
aaronpk done
#
aaronpk hmm looking through this list of people/teams, I think we need to do a serious audit
#
[tantek] likely
#
aaronpk I am worried about people who haven't been active in the community for years, the more accounts with push access the more chance someone's account is compromised and used to push malware to the package
#
[jgarber] Looks like [mattl] and I are on Team Ruby along with [aaronpk] . Not sure what permissions that team might have but seems reasonable to tack it on to any Ruby repos on the Organization with “admin” permissions.
#
[jgarber] (Up to the mods’ discretion there, of course.)
#
[mattl] i think that’s a general worry about github orgs and other things.
#
[jgarber] Or maybe even “manage” permissions if you want to restrict some of the repository settings access.
#
[jgarber] Publishing bad packages is as related but different concern.
#
aaronpk i just made the ruby team for you
#
aaronpk there are a lot of other teams and other people on them who i haven't heard from in a long time
#
[jgarber] awww blushes
#
[jgarber] [mattl] If you want any help or reviews or anything, feel free to tag me in on GitHub: jgarber623
#
[jgarber] Happy to pitch in. 👍
#
[mattl] feel free to take the issue too if you want. I won’t have immediate time to work on it but may have some time this weekend
#
[tantek] [mattl]++ [jgarber]++
#
Loqi [mattl] has 1 karma in this channel over the last year (15 in all channels)
#
Loqi [jgarber] has 1 karma over the last year
gRegor and [Joe_Crawford] joined the channel
#
gRegor php-mf2 got several pull requests, one of which suggests updating minimum PHP to 7.1. I know in the past we've kept to a lower minimum version due to WordPress support, but wondering if we should revisit that now.
#
gRegor It think this was the last discussion: https://github.com/microformats/php-mf2/issues/101
#
gRegor This is the new PR: https://github.com/microformats/php-mf2/pull/264
#
Loqi [preview] [dshanske] #101 Minimum PHP version
#
Loqi [preview] [jrfnl] #264 Fix PHP 8.4 compatibility / drop support for PHP < 7.1
#
gRegor 2.4% of WP on php5.6 according to https://wordpress.org/about/stats/
#
[tantek] philosophically speaking I'd prefer keeping old PHP compat, however I defer to the folks actually maintaining php-mf2 as to the marginal labor for doing so
#
aaronpk I don't see any reason to set a new minimum version just for funsies
#
aaronpk is there something in particular driving this?
#
aaronpk goes to read the issue
#
aaronpk Hmm I see... the alternatives to getting support in 8.4 do seem worse
#
gRegor I don't have a strong preference, haven't looked at it in depth yet
#
jimw it seems very unlikely that someone stuck with php < 7.1 is going to even be upgrading to a new version of php-mf2. composer will just give them last version that included support for whatever very old version of php they're running.
#
aaronpk Right, the main concern is whether they want any of the new features in the parser before they are able to upgrade their PHP version
#
aaronpk But IIRC there aren't a lot of new features pending release at the moment so maybe this is a good time to draw that line
to2ds joined the channel
#
jimw yeah, looks like it's been a while since a mf2 release, so maybe it makes sense to kick out one last 0.5.x as the last pre-7.1-supporting release and then just immediately release 0.6.0 that adds in the necessary php8.4 changes and drops support for pre-7.1.
#
[tantek] There's a bunch of mf2 parsing features in-flight
#
[tantek] I would kinda prefer we resolve on those, land spec changes so phpmf2 can roll out prototypes as mainline and then we can consider cutting over
#
[tantek] also, I'd like to see someone document the use-case (like in the issue) for this. how will changing min version help users or developers?
#
[tantek] newminversionforfunsies-
#
[tantek] newminversionforfunsies--
#
Loqi newminversionforfunsies has -1 karma over the last year
#
jimw the use-case is in the PR, using php-mf2 will emit deprecation warnings in PHP 8.4 (and errors in PHP 9.x) because it uses a syntax that is being obsoleted.
#
aaronpk Wait what features are in flight? I thought we shipped a bunch recently
#
aaronpk If there are features ready to go then we should knock those out and do a release that's compatible with 7.1 first
#
[tantek] aaronpk, spec features in-flight. mf2 parsing issues
#
[tantek] upstream from (some) parser implementations
#
[tantek] some implementations have already implemented prototypes of proposed resolutions which have not been integrated into the spec yet, per process to try proposals in an implementation or two before resolving/committing to spec
#
[tantek] jimw, is there no updated syntax that works (no warnings) in both old and new?
#
[tantek] like it's a breaking change in the language?
#
aaronpk that is my understanding
#
jimw in the sense that the language was broken, yes.
#
jimw the addition of type handing to php has been a bumpy road and as a result, has gone down a few blind alleys. this was one of them.
#
jimw the relevant PHP RFC is here for more nitty-gritty details: https://wiki.php.net/rfc/deprecate-implicitly-nullable-types
#
[tantek] I'm not clicking on that rn bc I have a feeling it will make me mad
#
[tantek] is there not some maxim somewhere like "PHP is not C"?
#
jimw not that i've heard. but certainly the philosophy of the language has changed a lot since the early days. like i said, a bumpy road and some blind alleys. the community does what it can.
#
gRegor Personally I don't think I'll have much time to commit towards getting in-flight parsing issues into php-mf2 in a reasonable timeframe
#
gRegor I am interested in which ones you're thinking of, though