#@brandonmblack@davidcelis People drove hard at this years ago, but it kind of died off. No one could seem to establish a well adopted open standard and everything else became too tightly coupled to the underlying systems. I’d love to see someone like yourself take a fresh swipe at it ? (twitter.com/_/status/930283495519170561)
tantek, snarfed, KartikPrabhu and [kevinmarks] joined the channel
#Loqi[kevinmarks]: snarfed left you a message 1 day, 8 hours ago: btw http://www.indiemap.org/ is a good source for the kinds of stats you all were idly guessing about while debating authorship and representative h-card. easy to data mine w/SQL. happy to help!
tantek, [pfefferle], cweiske, [colinwalker], loicm and bengo joined the channel
#aaronpki'm kind of surprised the "require" command doesn't support that
#aaronpkseems like it wouldn't be a stretch for the require command to add the appropriate stuff to the composer.json file
#ZegnatAnd for quick things, the amount of @dev-master I have had to write ... because the repos wouldn’t have “proper” version tags in place. Ugh.
#sknebelI think there is an extra command to add a repository via cmd
#ZegnatFor big packages it is all nice and done, they are on GitHub, on Packagist, correctly linked up, etc. But for my own local workflow I find composer to be a nightmare.
#aaronpkZegnat: you get used to it. i've been publishing more and more on packagist.
#ZegnatI used git-flow for linkextractor now. That takes care of the tagging. So one less thing to worry about.
#sknebelthat's something basically all packaging systems don't do very well IMHO
#sknebel(of course it doesn't help that every single one is slightly different...)
#Loqigit-flow (or git-flow (AVH Edition)) is a collection of Git extensions for following a popular branching model of the same name https://indieweb.org/git-flow
#dgoldreading some links; other than the git-flow toolset, I appear to always have been using git-flow concepts anyway
#dgoldI always branch to start a feature, then close the branch when its done - what I've not been doing is a develop/master dichotomy
#ZegnatThe pretty nice thing is that the git extensions can handle a lot of it for you. E.g. `git flow feature start my-great-new-thing`. Then you can just do `git flow feature finish` while on that branch and it’ll take care of the merges and branch removal etc.
#ZegnatLinkExtractor is my first “serious” use of the extensions. I liked it especially because `git flow release finish` also creates the git tag, which is necessary for Packagist.
#dgoldsknebel: its been loads of fun - script does googlebooksAPI searches, fills in all the details on my booksdb, and since last night sends a note to my blog confirming I've started reading a new book
snarfed, j12t, KartikPrabhu, [miklb] and tantek joined the channel
#aaronpk"Every 30 days, we look at the maximum number of feeds to which you subscribed since the last invoice and we’ll bill you according to the table on the right. "
#snarfedconfusing. definitely not how bridgy has been billed (or not billed, more accurately)
#snarfedyeah. "Finally, even though this pricing should almost always mean lower invoices for our existing customers, we offer them the ability to remain on the current pricing for as long as they want."