kylewmoh yeah to answer your earlier question, mf2py.herokuapp.com is run by tommorris. i'm wondering if there's a way to have it track the github master
Loqimicroformats are extensions to HTML for marking up people, organizations, events, locations, blog posts, products, reviews, resumes, recipes etc https://indiewebcamp.com/microformats
tantekKartikPrabhu: re: alternate storage system and UI - YES! That's precisely it. The UI of the inspectability of a storage system is essential to reliability and repairability, which are essential to any "in development" storage system.
kylewmI'm going to note it on the How-to-push page, since most people looking at that are going to be using superfeedr, and if they follow the doc as-is it won't work
Loqislack/snarfed: kylewm: aaronpk: strongly agree! full domains are nice but definitely not necessary for every little project. (and maybe slightly harmful: maintenance burden, naming restrictions, etc)
elf-pavlikwould maintainer of the project use URL of my original issue in one's own personal taskboard or make copy of it and use copy under ones own control instead?
elf-pavlikonce again, most ineresting case comes with which URL to use as cannonical by people who want to assign to the issue, comment on it, upvote/downvote it etc
voxpelliI think that either the issue will be owned by the project and then created at the project or the issue will be owned by the creator and created at its site and aggregated elsewhere
elf-pavlikvoxpelli, do you see problem with maintainer of the project creating copy of original issue (keeping provenance with rel="???" to original issue) and everyone would use this one as cannonical for further collaboration?
Loqielf-pavlik meant to say: voxpelli, do you see problem with one of maintainers of the project creating copy of original issue (keeping provenance with rel="???" to original issue) and everyone would use this one as cannonical for further collaboration?
elf-pavliksimilar to aaronpk's instinct i would prefer not to use URLs in namespace not controlled by project team as cannonical for tracking issues...
voxpellibut thinking about it, it feels like step 1 would be to create issues at ones own site and any steps beyond that would be informed bvy that first step
voxpellijumping directly to trying to recreate the full existing GitHub:esque flows just feels to me like it may skip a few steps in the dogfeeding and might arrive at the wrong conclusion
voxpellielf-pavlik: if you want to create an issue, then create a page – mark it up as an issue (not sure if there's mf2-markup for that) – and webmention my project with is a "reply" or something
Vendanmaybe separate "issue report" from "issue". Non-Dev creates issue report, dev creates issue from that issue report, possibly automatically using a webmention type flow
elf-pavliktrue, but reinventing already existing technologies (e.g. http://www.w3.org/TR/prov-o/ ) doesn't make sense to me, especially that it all could interoperate nicely with microformats terms via efforts like https://github.com/rhiaro/mf2rdf
aaronpkmicroformats2 is currently the easiest and quickest way to publish and consume structured data on each others' websites, so unless some other way comes along that is easier and more compelling, i think you'll have a hard time convincing anyone to do anything different
voxpelliaaronpk: Vendan: if one were to start publishing mf2 "issue" data – would one start coming up with a new "h-issue" or just build of "h-entry" or how would one approach it?
voxpellielf-pavlik: I guess it would be good to compose existing practises of GitHub etc – what fields etc do they have for issues and how does that map to existing mf-fields?
Loqivoxpelli meant to say: elf-pavlik: I guess it would be good to compose a list of existing practises of GitHub etc – what fields etc do they have for issues and how does that map to existing mf-fields?
Loqiconneg is short for HTTP Content Negotiation, a method by which a browser or other web client can request content of various types from a web server, and depending on what is requested, and what the server supports, it tries to provide the best it can https://indiewebcamp.com/conneg
voxpelliwell, no matter if it's RDF, JSON-LD or microformats – the model would need to be able to describe issues of more kinds than just GitHubs and thus probably need to be modeled after more than just GitHub
voxpellielf-pavlik: would be great if you documented those structures independently of your JSON-LD-work so that other works could be based upon the same