Camelia, the Perl 6 bug

IRC log for #darcs, 2013-05-02

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

All times shown according to UTC.

Time Nick Message
00:34 slack1256 joined #darcs
00:35 slack1256 on the wiki says that the most recent patch theory is the onde described on camp.
00:35 slack1256 is this true or there is another resource, that pdf says it's a work in progress.
00:48 gh_ joined #darcs
00:56 mizu_no_oto joined #darcs
01:15 intripoon_ joined #darcs
01:25 gh_ joined #darcs
01:25 mizu_no_oto joined #darcs
02:35 gh_ joined #darcs
02:37 slack1256 btw the understanding darcs wikibook is good
02:56 mizu_no_oto joined #darcs
04:11 thorkilnaur joined #darcs
04:15 thorkilnaur_ joined #darcs
04:44 gh_ joined #darcs
05:22 edwardk joined #darcs
06:16 kmels_ joined #darcs
06:39 jochu joined #darcs
07:02 ilbot_bck joined #darcs
07:02 Topic for #darcs is now http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.8.4 is out http://darcs.net/Releases/2.8
07:22 lelit joined #darcs
07:58 bsrk joined #darcs
08:27 amgarchIn9 joined #darcs
08:57 kmels_ joined #darcs
09:05 owst joined #darcs
09:24 raichoo joined #darcs
09:29 donri joined #darcs
10:11 jochu joined #darcs
10:12 thorkilnaur joined #darcs
10:22 bsrk hi,
10:22 bsrk I will like some reviews on my gsoc proposal
10:22 bsrk http://darcs.net/GSoC/2013-Darcsden
10:22 bsrk it is basically at a rough draft stage
10:59 bsrk joined #darcs
11:03 owst bsrk: I'd fold the "About the project" into the Abstract. The abstract tells you nothing, if you don't know what Darcsden is...
11:04 owst "Project Design" seems a bit fluffy. You've not said what it is that you're going to do, yet you're talking about deployment and testing already...
11:05 owst The timeline gives a nice list of goals (to me, as a darcs dev) but you need to explain what they are, and why they're important.
11:05 owst (to people who aren't darcs devs)
11:05 owst So to sumarise: be upfront about what you're going to do and *why* those things are important.
11:06 * owst disappears again
11:57 kmels_ joined #darcs
12:39 Spamchecker16 joined #darcs
12:49 Spamchecker16 left #darcs
13:07 mizu_no_oto joined #darcs
13:29 bsrk joined #darcs
13:36 mizu_no_oto joined #darcs
13:39 gh_ joined #darcs
13:51 bsrk joined #darcs
13:57 mizu_no_oto joined #darcs
14:09 Kindaro_ joined #darcs
14:10 Kindaro_ joined #darcs
14:36 edwardk joined #darcs
15:13 javier_rooster joined #darcs
15:18 dolio joined #darcs
15:19 mizu_no_oto joined #darcs
15:23 uniquenick joined #darcs
15:27 javier_rooster joined #darcs
15:49 kmels_ joined #darcs
16:29 lambdabot joined #darcs
17:04 raichoo joined #darcs
17:04 bsrk joined #darcs
17:06 bsrk Hi,
17:06 bsrk I have made the changes suggested by owst
17:06 bsrk the proposal is at: http://darcs.net/GSoC/2013-Darcsden
17:08 bsrk Any suggestions?
17:10 sm looking good bsrk
17:10 sm looking quite ambitious I would say, that's a lot of projects
17:11 sm some of them might need more discussion before you commit to them, Eg: getting from a remote repo is actually supported but disabled on darcs hub because it triggers excessive memory usage by darcs
17:12 bsrk ah
17:12 bsrk Then I suppose I need to remove it. :-)
17:15 sm ..so yeah, re-enabling that for a local darcsden is easy but getting it deployed on darcs hub is hard
17:16 sm resetting password via ssh may be nice, but I think a web-based password reset will be much more generally useful
17:16 sm tarballs - do people need that ?
17:16 bsrk sm: true, but can we actually send email from darcs hub?
17:17 sm packs - sounds great, if tests show they provide enough benefit to be worthwhile
17:17 sm bsrk: sending email can be arranged, sure
17:18 bsrk sm: then we should probably shift to a web based reset
17:19 bsrk though, do we have email id's for accounts?
17:19 sm hakyll - FYI I think this would run a standard safe hakyll script, not any arbitrary hakyll code
17:19 sm yes we do
17:20 bsrk I see. Then I will change it to web based password change
17:21 sm fork relationships/patch counts - I'm very keen on this type of thing, just note it includes clarifying and managing the performance/scalability impact of the extra queries
17:21 sm great
17:23 sm my perf/scalability comment is assuming darcs hub deployment - of course if you limit these to single-user darcsden instances these tasks are easier. The proposal could maybe mention/clarify which of darcs hub and/or local darcsdens are the target
17:24 bsrk it is all for darcs hub deployment
17:26 sm excellent!
17:26 sm github/openid/other login federation I think is a great idea, quite a valuable feature that seems relatively "simple" to do (of course it won't be, but..), I'd consider doing this one first
17:28 bsrk okay, I am going to move it to week 1
17:31 sm re deployment, hopefully deploying all of your work on hub right away will be an easy choice for me. But it might not be so in all cases - hopefully you can take this into account in your success criteria, so that the GSOC will definitely be a success.
17:32 bsrk sm, I am okay with that
17:32 sm also, think about how much support you might need from me for these tasks - we don't want you blocked when I'm unavailable
17:34 sm even though you are an experienced darcs developer, and hopefully you'll find darcsden refreshingly easier, my feeling the schedule as written right now is too ambitious
17:35 sm maybe you can divide up the deliverables into must haves and nice to haves
17:36 bsrk Okay
17:36 bsrk What do you think are the must haves?
17:37 sm also the separate (different ?) lists of features and deliverables might allow a little confusion about success/failure, maybe there's a way you can deduplicate/sync them a little more
17:38 bsrk Ah, okay. I will merge them
17:38 * sm wishing this was trello so I could drag tasks around and figure my priorities :)
17:38 sm thinking, just a sec
17:43 sm if it was my gsoc, I'd prioritise these first: easier login, web-based password reset/reminder, through-the-web editing, enhancements to display of branches and their relationships
17:46 sm these second: simple static site generation/hosting, per-file changes list, file annotate, evaluating/integrating pack support
17:47 bsrk I almost came up with the same list
17:47 sm and leave the rest as possible future items for when-I-run-out-of-things-to-do
17:47 bsrk but with packs, and enhancements to display of branches and their relationships reversed
17:48 bsrk but I think you know better, and I will go with your list
17:48 sm that makes sense, since you're already well into the packs task
17:48 bsrk yes
17:49 sm and it's your proposal, you get to decide :)
17:50 amgarchIn9 joined #darcs
17:50 sm "limit memory usage, prevent OOM restarts" on trello is the most important thing for me personally right now, but I'm not sure if that's attractive/visible enough to be part of your gsoc
17:50 bsrk sm: what about giving a ui to applying patch bundles?
17:51 sm I have not yet seen the light about patch bundles projects, they don't motivate me in any way. I'm not sure why I need them yet
17:52 bsrk It is a simpler way to update the repository as compared to ssh?
17:53 bsrk In my case, I can't use ssh, so I really badly need it. :)
17:53 bsrk On the other hand, this won't be a problem in summer,
17:54 bsrk so it won't be that helpful for me anymore
17:55 sm not being able to use ssh seems quite a niche problem. Also I bet you can use it, just a matter of following one of those docs about redirecting it over port 80, no ?
17:55 bsrk University Firewall
17:57 bsrk but, as I said, it wont be a problem in the summer, because I will be working from home
17:57 sm can't some of these help -
17:57 sm https://www.google.com/search?q=how+to+ssh+throu​gh+firewall+port+80&oq=how+to+ssh+through+fi​rewall+port+80&aqs=chrome.0.57.5840j0&so​urceid=chrome&ie=UTF-8#sclient=psy-ab&q=​how+to+ssh+through+firewall+port+80+superuser+st​ackoverflow&oq=how+to+ssh+through+firewall+p​ort+80+superuser+stackoverflow&gs_l=serp.3...6570.10271.0.10941.24.24.0.0.0.0.315.5896.2-2​3j1.24.0...0.0...1c.1.12.psy-ab._hzPZ3YcgCg&pbx=1&​bav=on.2,or.r_qf.&bvm=bv.45960087,d.aGc&fp=6ffbc76
17:57 sm I haven't done it myself but I hear people do
17:58 bsrk I will look through them. :)
17:59 sm part of a solution might also be to let darcs hub listen on alternate ports, like my mail provider does
18:12 * sm to work, see you bsrk
18:14 sm ps other tasks/ideas: update code to latest libs/GHC; evaluate/test alternate/simpler DB setups
18:15 sm couchdb is problem free so far, but not terribly familiar/easy to work with, eg for admin tasks
18:15 sm also don't forget alexsuraci might have ideas, this is his code
18:15 bsrk sm: I have merge the task lists
18:16 bsrk and have split the features into must have and nice to have
18:16 sm much better
18:16 sm how many hours/weeks is gsoc ?
18:17 bsrk thanks for the help sm.
18:17 bsrk ~30-40 hrs per week
18:17 dolio joined #darcs
18:17 sm and 12 weeks ?
18:17 bsrk yes
18:18 sm ok, the must haves seem pretty safe then
18:18 sm no problem bsrk, thanks for the work
18:20 sm patch bundles feature still needs clarifying/justifying :)
18:21 bsrk sm: It is at the very end of the list!
18:22 sm well I see it at top of the nice to haves, and I'm not yet sure what it is exactly.. but that may not be necessary
18:23 bsrk ah. I will move it down.
18:25 Heffalump patch bundles are the pull requests of darcs
18:25 carter joined #darcs
18:28 bsrk Heffalump: Ah. Until now, I assumed that only the repository owner can submit the patch bundle.
18:29 bsrk I think that what you actually mean is that any user can submit a patch bundle, and the owner decides to accept/reject it?
18:30 edwardk joined #darcs
18:31 sm http://hub.darcs.net/darcs/darcs-screened/patches is also pull requests of a sort.. a simple flag would make them better
18:32 sm being able to apply patch bundles seems like a complex workaround for not having ssh access ?
18:32 sm github doesn't have this feature, and I don't see it benefitting many people. I'm probably missing the real benefit of it
18:41 Heffalump bsrk: yes
18:41 Heffalump sm: less state than an entire fork
18:53 edwardk joined #darcs
19:05 Heffalump bsrk: I suggest submitting at least a preliminary version soon in case anything happens
19:09 bsrk Heffalump: okay
19:09 gh_ joined #darcs
19:11 bsrk Heffalump: http://google-melange.appspot.com/gsoc/propo​sal/review/google/gsoc2013/bsrkaditya/32002
19:12 kmels_ joined #darcs
19:14 bsrkaditya joined #darcs
19:14 bsrkaditya It is nearly 1AM here,
19:15 bsrkaditya so I am going to sleep.
19:15 bsrkaditya bye, everyone. :)
19:15 sm night bsrk
19:17 gh_ \o/
19:18 gh_ good to know we have one proposal
19:18 gh_ oh, mentors have to apply to the google-melange website, it seems
19:19 * gh_ does it
19:19 gh_ who would mentor bsrk's project?
19:19 gh_ Heffalump, sm?
19:21 mizu_no_oto joined #darcs
19:21 * gh_ reads the proposal
19:25 gh_ so the idea of local darcsden went away
19:33 gh_ I'm answering to Joe on the mailing list..
19:47 Heffalump gh_: I've signed up as a possible mentor
19:47 gh_ cool
19:57 owst joined #darcs
20:04 gh_ I'm not sure if my connection is bad or if the gsoc website is dying
20:18 * sm looks shifty
20:20 gh_ sm, what looks shifty?
20:21 dolio joined #darcs
20:24 sm me
20:25 sm gh_: have you mentored before ?
20:25 gh_ sm, no
20:25 gh_ sm, you?
20:26 Heffalump sm is welcome to if he'd like to, but I thought he said before when we suggested the idea that he didn't want to
20:26 sm no, not for gsoc. Your mail feedback was good
20:27 sm Heffalump: thanks, yes I was in work-avoidance mode then too
20:27 gh_ I could mentor the darcsden project although I'm not sure I'm the most qualified.. nor the most interested in the project, to begin with :-)
20:28 gh_ but that BSRK already participated last year and has stuck around with us since then is reassuring
20:29 sm Heffalump: if you're able, that's great - I'll be here to help
20:50 owst Heffalump: could you update your IRC log?
20:50 owst I was going to see what I've missed :-)
20:52 nomeata joined #darcs
21:05 Heffalump owst: the new bits of log are at the old URL
21:05 Heffalump and the bits that were at the old URL are now at darcs-older.log instead of darcs.log
21:40 jochu joined #darcs
21:40 jochu joined #darcs
21:43 mizu_no_oto joined #darcs
21:56 edwardk joined #darcs
22:07 dolio joined #darcs
22:08 favonia joined #darcs
22:43 mizu_no_oto joined #darcs
23:02 jochu joined #darcs
23:10 whaletechno joined #darcs
23:12 edwardk joined #darcs
23:49 dolio joined #darcs
23:50 gh_ joined #darcs
23:51 mizu_no_oto joined #darcs

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