log☇︎
14100+ entries in 0.024s
mod6: ok! so you're looking at it the same way i was then -- and I thought this yesterday.
mod6: 2 & 7 are blockers to the completion of 8
mod6: %p UCI 8
mod6: err
mod6: %p UCI 2
mod6: i.e.
mod6: which it really should read
mod6: so... all of these obnoxious mental gymnastics are because i didn't want to use the term "blocker"
mod6: eh, maybe not.
mod6: does anyone agree with that assessment?
mod6: should read "ANTECEDENT OF" if anything
mod6: boy. i think that the logic might be correct in there -- but boy oh boy is "ANTECEDENT(s)" a bad label.
mod6: so im gonna dig into that a bit today, and see what needs to change if anything -- the structure shouldn't change too much, just a lot of labeling to make it more .... intuitive.
mod6: speaking of which, i think I'm going to need to rework this whole antecedent thing. while building it, it seemed to make sense to me, but now, looking at it through a different set of eyes, it seems unintuitive at best, out right backwards at worst. ☟︎☟︎
mod6: the gpg part isn't a prob or whatever.
mod6: <+mircea_popescu> mod6 aww, you didn't choke on the submit part did you ? just gpg --encrypt --armor -r bingo and put the text into dpaste or wotpaste.cascadianhacker.com << ah, no. my writing isn't good. so lol, it's difficult for me.
mod6: this kidna thing isn't forme.
mod6: should I just send you what I've got?
mod6: BingoBoingo hey, turns out that I won't have time to finish this tonight, and probably not until tomorrow night at very earliest.
mod6: %r foobar 2
mod6: %r foobar 1
mod6: my apologies, is this documented somewhere?
mod6: clearsign+encrypt -> dpaste ?
mod6: encrypt and send to you for review?
mod6: OK, so then what.
mod6: :P
mod6: no ajax?
mod6: ?
mod6: like this: <div class="entry-content">
mod6: do you want me to put in the class attributes?
mod6: :D
mod6: you don't want me to use a bunch of JS to do a bunch of things to make your eyes bleed?
mod6: How does that work?
mod6: do I have to add the HTML, links and all that? Or do you do the mark up?
mod6: im still working on a bit of a write up here...
mod6: cool!
mod6: BingoBoingo you may want to update the 'about' page on qntra, buncha #bitcoin-assets links and such.
mod6: i'll see what i can do, ya. ok.
mod6: i probably could/should have all of the tickets clumped under one tree. but i need to work on the tickets and ordering etc.
mod6: its hard because there are like a number of disconnected graphs, or hard because of mental gymnastics? i'd like to make it better, so your input helps.
mod6: <+asciilifeform> http://btcbase.org/log/2016-06-09#1479597 << veeery labour-intensive to read << ok, noted. so my first stab at this... more here please. ☝︎
mod6: :D
mod6: watch out or you'll start writing #!/usr/bin/perl all the time
mod6 turning people to the dark side, one at a time.
mod6: much more to come / work on.
mod6: salud; now that we've got a ticketing system, we can see how much there really is to do still! haha.
mod6: Couldn't have done it without you though, thanks for all the testing help. Most sincerely.
mod6: o7
mod6: ahaha
mod6: ah, ok. working on something here...
mod6: ah
mod6: unless mircea_popescu wants to have the honor, then by all means.
mod6: he'll get back to us, im sure its fine.
mod6: jdawg: does that work ok?
mod6: Ah, he's the man on that then, ok.
mod6: But I'll take a shot at it I guess as long as the proceeds can be donated to The Bitcoin Foundation.
mod6: lol
mod6: I'm not much of a writer. Obviously. ☟︎
mod6: btcalpha isn't updating from deedbot ? ☟︎
mod6: ah. ok.
mod6: ;;seen mike_c
mod6: oooh
mod6: I feel like we've needed this tool for some time as he was only needing a way to track and graph the work required. ☟︎
mod6: BingoBoingo: did you read these tickets? don't miss out on Mr. P.'s vision for TMSR~ here in the story.
mod6: and as we start to work on these features, it is meant (at least by me) that tasks and other atomic work will be children of the features.
mod6: wewt!
mod6: your tickets are awesome btw
mod6: that might make it that much more clear.
mod6: maybe "ANTECEDENTS" is a bad word here, perhaps "DEPENDENTS"
mod6: but to me looks like everything goes the right way, and dependentcies are in the correct direction
mod6: i guess this can be re-worked if it invokes too much mental gymnastics.
mod6: this looks right to me
mod6: so yeah, we start with a large chunk, and it breaks down to smaller chunks.
mod6: hmmm ok lemme see
mod6: and the same for 3, 4, 5
mod6: so for ticket 6, i may have put in its antecedent as 7
mod6: ooh, i see
mod6: yah, i kinda modled it after how the tree looks for V.
mod6: well and #2
mod6: and the 5, 6, 4, 3, are the leaves
mod6: ok then that should be fine it kinda looks funny i suppose. but 1 is the root.
mod6: so ticket 1 is a saga, which can't be complete until 8 is complete, correct?
mod6: no. actually.
mod6: hm. so is ticket 1 an antecedent (parent) of ticket 8?
mod6: ok refresh, it's updated :]
mod6: yeah, exactly.
mod6: the next update ~should~ contain them all.
mod6: probably because it was related to the timing of entering the tickets.
mod6: oh!
mod6: cool, your graphs are up :]
mod6: i'll check into that.
mod6: ah, yeah, ok. i see all of 'em came in at nearly the same time. should have handled it, but looks like it got a bit confused.
mod6: ok, yeah, i see all of those in the file. lemme see what happened when you were entering 'em. thanks for doing that, might be a weird timing issue or something, not sure.
mod6: %p UCI 8
mod6: %p UCI 7
mod6: %p UCI 6
mod6: %p UCI 5
mod6: %p UCI 4
mod6: %p UCI 3
mod6: %p UCI 2