#jmacSo at risk of tooting my own horn, I would like to politely petition to the relevant authorities to have Web::Microformats2 for Perl linked from somewhere in an official Microformats.* page, if even from http://microformats.org/wiki/microformats2#Development_parsers for the present. To its credit I can claim its passing the official MF2 tests, and its powering at least one public website's Webmention functionality.
#KartikPrabhujmac: you could login to the wiki and add it no?
#aaronpkI guess they didn't want to assume curl was installed
#jmacBut anyway... so I know what I might like to aim for, what sorts of metrics would qualify my MF2 library to advance from "in development" to join the "production ready" bunch? (I mean, *I* will declare it 1.0 at some point in the future, but that don't mean nuthin)
#tantekjmac I think passing the tests (as you're working on), *plus* some number of other people using it in their sites would make it "production ready"
#jmacOh, I have conquered the cold machine logic of the tests. Now comes the true challenge, the soft and squishy uncertainly of other people using this thing.
#tantekjmac, even using it yourself, e.g. to parse webmentions from others, would be a good start on that!
#jmacIf I can manage to successfully merge the experimental branch of my blogging platform (which does have a small but extant userbase) into master, and then actually getting people to use the Webmention features that it introduces, that'll be that
#jmacAnyway, thanks... I'll ask again about all that once I do have some buy-in
#Loqijmac has 7 karma in this channel (17 overall)
#tantekok folks I want to come up with labels for the microformats2-parsing issues to help indicate their current state (where they're stuck), and help with triaging / processing them once we have consensus / implementations etc.
#Loqi[Tantek Çelik] h-event is a simple, open format for events on the web. h-event is often used with both event listings and individual event pages. h-event is one of several open microformat draft standards suitable for embedding data in HTML.
h-event is the microfor...
[cleverdevil], GWG-, klez, [manton], gRegorLove, Phae, [matpacker], KartikPrabhu, [xavierroy] and [chrisaldrich] joined the channel
#@michaelfavia↩️ I totally see what you mean but didn't we try that with RDF and microformats too? I mean I'm game for the ride just like I was the first time None of the companies wanted to join though so it was just us out there linking our little islands together. (twitter.com/_/status/1024186722744246272)
#LoqigRegorLove: tantek__ left you a message 1 hour, 34 minutes ago: yes that is likely. file an issue for adding p-attendee to h-event?
#LoqigRegorLove: tantek__ left you a message 1 hour, 21 minutes ago: you might find this convenient now: http://ufs.cc/w/mf2p
#Loqi[gRegorLove] #4 Add backcompat for attendee property
Evo, snarfed, tantek__, [chrisaldrich], jgmac1106 and chrisaldrich joined the channel
#sknebelsnarfed: we want to do *something* there, since the current code crashes in some cases. so either make the decision to go back to modifying the input, not creating a copy, or fix that copying code (the PR needs extending for that tho, since I missed some cases...)
ibnesayeed, dbryant, [snarfed], 17SAAJIW3, Evo, snarfed and [kevinmarks] joined the channel
#snarfedso sknebel for https://github.com/microformats/mf2py/pull/114 , i'm inclined to go back to modifying the input, at least for now, to get the 1.1.2 release out, and then we can try again if we want. what do you think?
#Loqi[kartikprabhu] @sknebel I ma not sure that the `copy` function is actually broken on `Tag`. Here is an example that works outside mf2py
```python
import copy
from bs4 import BeautifulSoup
doc = '''<article class="hentry"></article>'''
soup = BeautifulSoup(...
#sknebelwhere I then said: "but that only works because you replace the list"
#KartikPrabhuoh I see. so the revert will still modify the BS doc
#sknebelbut since we never return the tree to the user, it's competely fine for us to just ... always replace the lists
#sknebelour copy isn't a complete copy, and if we handle it wrong, we will accidentially modify the source tree
#sknebelbut we control how we handle it, so as long as we do it right...
#snarfedsknebel: hmm, maybe that's all true? can we add new tests to the revert to confirm it?
#snarfedif you have those tests, feel free to pull my PR into a branch and try them
#sknebelmaybe, will look into that tomorrow. (getting kinda late here)
#snarfedsknebel: np! thanks for working on this today!
#snarfedi suspect the revert will have better performance, so if we can find some tests and convince ourselves it fixes the problem, we may want to go with it