#microformats 2020-05-19

2020-05-19 UTC
joshghent, KartikPrabhu, [jeremycherfas], jacky, [tantek], [prtksxna], [LewisCowles] and [grantcodes] joined the channel
#
[grantcodes]
I'd be all for that as long as it works (which I'm sure it does). Are there criteria in place for using it on microformats.io? Like number of people using it etc?
#
[grantcodes]
And same question for potentially moving it to a community organization on GitHub in the future (if [aimee] wants that of course) but I'd like to see that as that has been a big issue with the other one going unmaintained. Although someone could have forked it but obviously noone wanted to 😅
[aimee] joined the channel
#
[aimee]
If the community wants to pull it in, I’m for it
[prtksxna] joined the channel
#
[aimee]
As for npm, if the repo ownership was to transfer to a community organisation, so should the npm package, and we should consider scoping it
shimmy1996 joined the channel
#
shimmy1996
does mf specs respect anchor links? looks like xray parser does, but is it part of the spec? I'm trying to see if I can get away with just stuffing all comments in one page instead of giving each of them its own pages
KartikPrabhu and [jgarber] joined the channel
#
[jgarber]
shimmy1996: If you haven’t seen them yet, there are a few possibly related issues on the microformats2-parsing issues repo: https://github.com/microformats/microformats2-parsing/search?q=fragment&type=Issues
#
[jgarber]
One or more of those could give you a sense of what you’re looking for.
#
shimmy1996
thanks a lot! #44 was exactly what I was looking for.
#
[jgarber]
Perfect! :thumbsup::skin-tone-2:
KartikPrabhu joined the channel
#
[grantcodes]
I actually have the unused @indieweb org on npm but that might not make sense for the mf2 parser. But I'll try it out soon 🙂
[aimee] joined the channel
#
[aimee]
@microformats is not available sadly
#
[aimee]
Hmm, @microformat was available, that might do? I registered it so we have it...
[KevinMarks] joined the channel
#
[KevinMarks]
sounds good. I wonder who has microformats
#
[KevinMarks]
it's likely to be someone we know
[tantek] joined the channel
#
[aimee]
Yeah, we should explore that first
[prtksxna] and [chrisaldrich] joined the channel
#
sknebel
yeah, I think that got the move of the js parser stuck last time - moving the repo was one thing, but glenn wanted to look into how to handle npm rights and then it got stuck again. so good to think about now!
#
KartikPrabhu
maybe it is glenn jones who wrote the previous microformats parser in javascript?
#
sknebel
talked to him around IWC Brighton about it briefly
#
[tantek]
yes he wrote microformatsnode. no idea where the npm discussion went or "who has microformats" on npm. if anyone familiar with npm structure/governance could look into it and report back that would be great!
[grantcodes] joined the channel
#
[grantcodes]
https://www.npmjs.com/org/microformats don't know if there's any way to figure out who has access to it though
#
[grantcodes]
https://www.npmjs.com/policies/disputes someone officially affiliated with microformats could probably claim it on squatting
#
[grantcodes]
But only if it is actually going to be used
[aimee] joined the channel
#
[aimee]
Npm seemed to be decent with disputes when I did them in the past. I published a package with a work account that I lost access too got it back
#
[aimee]
Also would we ever have more than one package in the organisation?
[KevinMarks] joined the channel
#
[KevinMarks]
Is it worth putting non-node code in npm?
#
[KevinMarks]
We have other microformats related algorithms like author discovery and post types that are inbetween indieweb and microformats
#
[KevinMarks]
Also potentially richer things based on the rel microformats like identity consolidation and friend graphs that may make sense being mf2 rather than indieweb
#
[KevinMarks]
And xoxo for real old-school code. That feels like a useful npm package
#
[aimee]
Non node as in browser? Or?
#
[aimee]
Yeah I’ve also been looking at post types 😉
#
[KevinMarks]
I meant python/go/Ruby etc. I don't think that belongs in npm, but I was wondering if anyone does that.
#
[KevinMarks]
I don't think we have anything worth doing the wasm thing to.
#
[aimee]
No we shouldn’t bundle other languages in the org
#
[aimee]
I’m not sure if we need an organisation unless we want to publish more, maybe we would just need to make sure we have enough people as maintainers on the package in case someone goes quiet
#
[aimee]
Other languages there wouldn’t be much use, you’d want to use the respective package manager
#
Loqi
[microformats] xoxo: Code to transform back and forth between JSON and HTML outlines
KartikPrabhu, [tantek] and [tw2113] joined the channel
#
[tantek]
oh yeah!
#
[tantek]
[aimee] your mf2 parser would be a great start. There are other packages we could consider for inclusion as well. E.g. a converter to/from jf2