Perl 6 - the future is here, just unevenly distributed

IRC log for #pdl, 2013-06-17

| Channels | #pdl index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
04:19 Meiermann joined #pdl
11:19 _vicash_ joined #pdl
12:50 _vicash_ joined #pdl
14:22 run4flat joined #pdl
14:23 run4flat hmm, none of the bots are up
14:25 liddle_piddle_bot joined #pdl
14:25 run4flat hey opers, share the love?
14:25 run4flat ping drrho jberger lungching osfameron
14:25 run4flat :-)
14:28 perigrin but I don't trust *you* in #pdl run4flat
14:29 jberger o/
14:30 run4flat ah, thanks!
14:30 run4flat hmm... who else gets ops?
14:30 * run4flat checks liddle_piddle_bot's source to see if it still restores ops
14:32 Bender2 joined #pdl
14:32 Bender1 joined #pdl
14:33 * run4flat feels reassured
14:35 run4flat liddle_piddle_bot, trust Bender1
14:35 run4flat liddle_piddle_bot, trust Bender2
14:35 run4flat liddle_piddle_bot, trust jberger
14:36 run4flat liddle_piddle_bot, trust perigrin
14:36 jberger haha, I like the pm you get
14:36 run4flat pm?
14:36 jberger private message
14:36 run4flat oh, you get a personal messag?
14:37 perigrin yeah
14:37 perigrin we've been welcomed to the inner sanctum
14:37 run4flat haha, I was just looking at the code and I forgot it did that
14:37 run4flat :-)
14:37 jberger liddle_piddle_bot is becoming sentient!!
14:37 jberger aaaaaaaaaarhh
14:37 run4flat down, liddle_piddle_bot, down!
14:40 perigrin Bender1: spread the love
14:42 pdurbin Bender1: trust pdurbin
14:42 Bender1 But I don't trust you in #pdl, pdurbin
14:42 run4flat pdurbin, don't be silly
14:42 run4flat we removed your from the trusted list
14:42 run4flat :-)
14:42 perigrin you can hoist yourself :)
14:42 pdurbin >:
14:42 pdurbin >:(
14:42 run4flat pdurbin, would you like to be an oper?
14:43 run4flat liddle_piddle_bot, trust pdurbin
14:43 pdurbin no, no, just funnin'
14:43 run4flat too late
14:43 pdurbin heh
14:43 run4flat but, you must behave yourself
14:43 run4flat Bender1, trust pdurbin
14:43 Bender1 run4flat, I already trust pdurbin
14:43 pdurbin fine
14:43 run4flat really?
14:43 * run4flat scratches head
15:38 perigrin Bender1: spread the love
15:38 perigrin oh ner
15:38 perigrin run4flat: 10:43 mode/#pdl ("+o pdurbin"); by run4flat
15:38 perigrin bender follows trusts
15:39 run4flat oh, ok
15:39 run4flat :-)
15:39 perigrin he trusts you, you opped pdurbin ... so by the transitive property of trust
15:39 perigrin he now trusts pdurbin
15:39 run4flat neat
17:25 chm joined #pdl
17:27 chm An updated plan for PDL3 development is available for comment/feedback at http://mailman.jach.hawaii.edu/piperma​il//pdl-porters/2013-June/005704.html
17:27 chm I hope this clears up some of the concerns.  Stay tuned to the pdl-porters list for coming announcements.
17:27 chm _vicash_: Does this address your concerns?  Feedback at pdl-porters welcome.
18:14 * run4flat is writing an email response to chm
18:41 sivoais we should put the PDL3 proposal in the topic
18:42 run4flat sivoais++
18:43 Topic for #pdl is now Install PDL: http://pdl.perl.org/?page=install  | Book: http://pdl.perl.org/content/pdl-book-toc.html | Mailing list: http://pdl.perl.org/?page=mailing-lists | Pasting: http://scsys.co.uk:8001/pdl | Channel is logged by ilbot2: http://irclog.perlgeek.de/pdl/today/ | PDL3 proposal and discussion: http://mailman.jach.hawaii.edu/piperma​il//pdl-porters/2013-June/005704.html
18:43 run4flat should I put that higher up in the list, I wonder?
18:43 Topic for #pdl is now PDL3 proposal and discussion: http://mailman.jach.hawaii.edu/piperma​il//pdl-porters/2013-June/005704.html | Install PDL: http://pdl.perl.org/?page=install  | Book: http://pdl.perl.org/content/pdl-book-toc.html | Mailing list: http://pdl.perl.org/?page=mailing-lists | Pasting: http://scsys.co.uk:8001/pdl | Channel is logged by ilbot2: http://irclog.perlgeek.de/pdl/today/
19:04 run4flat and my reply: http://mailman.jach.hawaii.edu/piperma​il//pdl-porters/2013-June/005712.html
19:19 preaction as a future potential user of pdl, i second the move to github. in a long-running, asynchronous, distributed project, gantt charts are not really needed (and will never be accurate)
19:41 sivoais yeah, I never got much use out of Gantt charts, but people in engineering and business continue to teach them
19:43 sivoais Tufte has a page on those <http://www.edwardtufte.com/bboard​/q-and-a-fetch-msg?msg_id=000076>
19:59 preaction they're great if you've got a full-time project manager and want to know the date something is going to get finished, but otherwise, not really needed
20:00 preaction and there are few issue trackers that i actually like using, github's is one of them, and i had to write the other one
20:20 run4flat haha, "and I had to write the other one"
20:20 run4flat thanks
20:21 run4flat but, how do you ensure that things get pushed out by the deadline of August?
20:21 run4flat Or, how do you minimize the cost of somebody picking up a half-finished feature?
20:25 run4flat I can only come up with two solutions: (1) have the same person do said feature from start to finish; if they fail, the feature evaporates
20:26 run4flat (2) Set up a series of milestones and have the initial contributor create their own feature branch where they push through each milestone methodically
20:26 run4flat The second option takes more work by the contributor, but is more easily picked up if the initial person has to step away
20:49 preaction i'd do what Perl does: do all the work on a branch, if the branch is not merged by the release date, it stays out
20:51 preaction or, it's on github, do it in your own fork
20:52 run4flat so, we operate under the assumption that a single contributor will contribute a single idea?
20:53 preaction no, you can have shared feature branches with more than one person contributing, but keep it out of mainline (in my opinion)
20:53 preaction imho, master should be ready for release at all times
20:54 preaction it's hard to do that, of course, but it helps if you need to get a bugfix out immediately
20:57 run4flat ah, but that doesn't quite address my concern
20:57 run4flat suppose that I start working on some major feature
20:57 run4flat and then my mom passes away and I all but abandon PDL
20:57 run4flat I leave said feature unfinished
20:58 run4flat do I just leave that sitting in a branch somewhere, to suffer branch degredation?
21:09 preaction until someone picks it up for you, yes
21:11 run4flat Then, what would be a Git best practice to make it easy for somebody to pick up that branch?
21:12 run4flat Some sort of branch-description.txt?
21:12 run4flat in the root dir?
21:12 preaction if it's an important branch, keep it in the main repository on github
21:12 preaction and keep some issues open for that branch
21:12 preaction the issues should be what the Scrum people call "the backlog". an issue gets created before any code gets writ
21:13 run4flat hmm
21:13 run4flat ok
21:14 preaction but i guess the main defense against unmaintained branches is the pumpking, the project manager
22:43 chm joined #pdl

| Channels | #pdl index | Today | | Search | Google Search | Plain-Text | summary