| 00:41.33 | *** join/#brlcad teepee_ (~teepee@unaffiliated/teepee) | |
| 02:33.23 | *** join/#brlcad LordOfBikes (~armin@dslb-092-075-156-238.092.075.pools.vodafone-ip.de) | |
| 06:04.19 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) | |
| 06:40.32 | *** join/#brlcad ofnlut_ (~ofnlut_@2601:143:8001:646d:60b2:f03f:7a3b:eabd) | |
| 06:42.25 | *** part/#brlcad ofnlut_ (~ofnlut_@2601:143:8001:646d:60b2:f03f:7a3b:eabd) | |
| 07:53.05 | *** join/#brlcad teepee_ (~teepee@unaffiliated/teepee) | |
| 08:32.26 | *** join/#brlcad merzo (~merzo@92.60.189.225) | |
| 09:00.12 | *** join/#brlcad tandoorichick (~chatzilla@182.75.45.225) | |
| 09:03.29 | *** join/#brlcad tandoorichick_ (~chatzilla@111.93.5.194) | |
| 09:07.29 | *** join/#brlcad tandoorichick_ (~chatzilla@182.75.45.225) | |
| 09:13.28 | *** join/#brlcad tandoorichick_ (~chatzilla@182.75.45.225) | |
| 09:17.32 | *** join/#brlcad tandoorichick_ (~chatzilla@111.93.5.194) | |
| 09:21.37 | *** join/#brlcad teepee` (bc5c2134@gateway/web/freenode/ip.188.92.33.52) | |
| 09:23.31 | *** join/#brlcad tandoorichick_ (~chatzilla@111.93.5.194) | |
| 09:27.33 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 09:33.33 | *** join/#brlcad tandoorichick_ (~chatzilla@111.93.5.194) | |
| 09:37.35 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 09:43.33 | *** join/#brlcad tandoorichick_ (~chatzilla@111.93.5.194) | |
| 09:47.31 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 10:03.07 | *** join/#brlcad merzo (~merzo@92.60.189.225) | |
| 10:22.58 | *** join/#brlcad tandoorichick (~chatzilla@111.93.5.194) | |
| 10:25.42 | *** join/#brlcad tandoorichick_ (~chatzilla@111.93.5.194) | |
| 10:29.44 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 10:33.45 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 10:39.42 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 10:43.42 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 10:49.42 | *** join/#brlcad tandoorichick_ (~chatzilla@182.75.45.225) | |
| 10:53.41 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 10:59.45 | *** join/#brlcad tandoorichick_ (~chatzilla@111.93.5.194) | |
| 11:03.44 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 11:09.43 | *** join/#brlcad tandoorichick_ (~chatzilla@182.75.45.225) | |
| 11:14.01 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 11:19.43 | *** join/#brlcad tandoorichick_ (~chatzilla@182.75.45.225) | |
| 11:26.16 | *** join/#brlcad tandoorichick_ (~chatzilla@182.75.45.225) | |
| 11:30.21 | *** join/#brlcad tandoorichick_ (~chatzilla@61.12.40.177) | |
| 12:10.24 | *** join/#brlcad teepee (~teepee@unaffiliated/teepee) | |
| 14:41.11 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) | |
| 17:20.20 | brlcad | this is awesome... http://publicdomain.nypl.org/pd-visualization/ |
| 17:21.09 | brlcad | new york public library released http://www.nypl.org/research/collections/digital-collections/public-domain |
| 17:40.27 | brlcad | 673k digitized items |
| 17:48.03 | *** join/#brlcad ickby (~stefan@x5d8443f2.dyn.telefonica.de) | |
| 17:54.27 | ickby | brlcad: Hello! |
| 17:54.36 | brlcad | hello |
| 17:54.55 | ickby | GSoC appication period starts today, any progress made on the desicion on your side? |
| 17:55.54 | brlcad | yes, received several responses over the weekend and tallying up mentor support today |
| 17:56.55 | *** join/#brlcad brlcad (~sean@66-118-151-70.static.sagonet.net) | |
| 17:57.24 | ickby | oh nice. I've seen the mailing list entry and was a bit nervous because nobody answered on the list. |
| 17:57.24 | brlcad | wow, irssi actually crashed... that's new |
| 17:57.29 | ickby | :) |
| 17:58.06 | brlcad | several contacted me back privately |
| 17:59.09 | ickby | so we made up a project list on our wiki. I've scanned through yours and it seems like a central place for all application in the umbrella. I think it is best to integrate at least some links in your wiki I suppose |
| 18:00.40 | brlcad | the public sentiment isn't too far offset, though, that we will likely keep things really light for our mentors (i.e., few slots if any for us) |
| 18:01.25 | brlcad | I have a few replies and inquiries to make today, and will follow-up on the gsocax list |
| 18:02.49 | brlcad | how many projects are you up to? |
| 18:03.28 | brlcad | you'll want at least 10 project ideas with some detail |
| 18:03.55 | ickby | 4 ideas, 2 we can actually handle. One for me one for yorik. We have some guys which will stay in the background and provide support |
| 18:04.04 | ickby | 10? ok thats alot. any reason for this number? |
| 18:04.18 | brlcad | the titles on our wiki ideas page links to pages with more info on each, the level of detail expected |
| 18:04.47 | ickby | yes we modeled our ideas after what we found on this pages |
| 18:04.54 | brlcad | because you will not likely get applications for all your ideas, variety is needed to match up skills and interest |
| 18:04.55 | ickby | they are pretty solid |
| 18:05.03 | brlcad | if you were applying solo, you'd want 20-30 ideas |
| 18:06.19 | ickby | ok, if this is the experience we will catch up. Shout not be hard, ideas are basically endless :) |
| 18:07.23 | brlcad | if you can't, that's fine -- just as a group, we will need 30+ -- but to attract viable students, you will want some interesting variety |
| 18:08.08 | brlcad | to set expectations consistently, I've found it best if mentors scope a project that would take the mentor 1-2 months of time AT MOST, closer to 1-month of full-time effort estimated |
| 18:08.49 | brlcad | because invariable and with high disparity, gsoc students will exceptionally under-estimate their time and their progress will be slow, especially getting up to speed with existing code bases |
| 18:09.23 | brlcad | this is a perspective shared across most orgs and communities |
| 18:09.34 | brlcad | scope it for 1.5 and the student has a chance of completing it in 3 :) |
| 18:09.41 | ickby | hehe |
| 18:10.37 | brlcad | it's easy to add more work and scope if they actually get done faster, but it's dangerous and demotivating if they're behind schedule |
| 18:10.49 | ickby | I mentor studends in my company, they are even slow when physically available. could imagine what happens on distance |
| 18:11.23 | brlcad | one of the proposal review guidelines is to figure out if the student's skill matches the timeline they include in their proposal |
| 18:11.43 | brlcad | that's great, you have some mentoring experience |
| 18:12.29 | brlcad | I've found it to not be a whole lot different other than being very wary of students that require extra attention, for whatever reason |
| 18:13.36 | brlcad | every year, there's usually 1 or 2 "rock star" applications where it's a student that is adept at navigating code, communicating well but great at learning and exploring independently |
| 18:14.57 | brlcad | we had a phd student in china helping with our NURBS boolean evaluation infrastructure (surface-surface intersection, etc) working with us for a couple years, for example |
| 18:15.50 | brlcad | not the norm, though -- it's very much a bell curve with the average requiring consistent attention, review, and discussion to feel like it's productive |
| 18:15.54 | ickby | I've read his application partially |
| 18:16.40 | brlcad | there have been a few others as well, just last year was an outstanding student converting our ray trace pipeline over to opencl |
| 18:17.10 | ickby | Yeah in the end I hope we get more work out than we put in, that would be the goal. |
| 18:18.04 | brlcad | our goal is usually to get someone that continues to contribute after gsoc is over |
| 18:18.14 | brlcad | code comes and goes, quality is all over the map |
| 18:18.40 | brlcad | if we can get good code, great, but I'd rather get a new dev :) |
| 18:19.29 | ickby | so back to some try stuff: should I start update your wiki with our information (contacts, projects etc.)? Or will there be annother resource you guys use? |
| 18:19.41 | ickby | *dry |
| 18:21.23 | brlcad | go ahead and add your details there |
| 18:21.41 | ickby | how do I get edit permissions? |
| 18:21.51 | brlcad | that may not be the final destination, but it's closest to getting everything in one place |
| 18:22.02 | brlcad | just create an account and go to town |
| 18:22.13 | ickby | ok sounds good |
| 18:22.14 | brlcad | our wiki is traditional style, open |
| 18:22.41 | brlcad | you might be asked to do some math :) |
| 18:22.56 | ickby | we tried this too, but never managed to hold the spam back. now personal permission is needed |
| 18:25.34 | brlcad | we don't keep it back, but with that and about 6 other measures, it reduces spam to actual humans about 10-20 instances per year |
| 18:25.37 | brlcad | manageable |
| 18:26.13 | brlcad | once a month seems to be about the norm |
| 18:37.15 | Notify | 03BRL-CAD Wiki:Ickby freecad * 0 /wiki/User:Ickby_freecad: |
| 19:00.28 | Notify | 03BRL-CAD Wiki:Ickby freecad * 9527 /wiki/Summer_of_Code/Checklis: |
| 19:01.13 | Notify | 03BRL-CAD Wiki:Ickby freecad * 9528 /wiki/Summer_of_Code/Checklis: |
| 19:11.34 | teepee | ahh, freecad, yay \o/ |
| 19:11.38 | Notify | 03BRL-CAD Wiki:Ickby freecad * 9529 /wiki/Summer_of_Code/Checklis: |
| 19:31.02 | *** join/#brlcad teepee (~teepee@unaffiliated/teepee) | |
| 21:24.25 | *** join/#brlcad merzo (~merzo@56-41-133-95.pool.ukrtel.net) | |
| 21:39.16 | *** join/#brlcad ickby (~stefan@x5d8443f2.dyn.telefonica.de) | |
| 21:47.19 | *** join/#brlcad ickby (~stefan@x5d8443f2.dyn.telefonica.de) | |
| 22:26.16 | starseeker | brlcad: that is awesome - I hadn't tried the visualization of the whole collection, very cool idea |
| 23:33.21 | *** join/#brlcad teepee_ (~teepee@unaffiliated/teepee) | |
| 23:45.13 | Notify | 03BRL-CAD:brlcad * 67066 brlcad/trunk/src/librt/CMakeLists.txt: remove the old unpublished rt_shoot_many_rays() multiple-ray dispatching interface. while an interesting approach, relying on a per-ray callback to set each ray for dispatch, the approach is inherently contentious with the need to semaphore block the book-keeping called per ray. plus, it doesn't let the caller precompute all rays in advance coherently. |