| 00:57.07 | *** join/#brlcad LordOfBikes (~armin@dslb-088-066-150-194.088.066.pools.vodafone-ip.de) |
| 01:55.22 | *** join/#brlcad LordOfBikes (~armin@dslb-088-066-129-084.088.066.pools.vodafone-ip.de) |
| 06:33.18 | Moult | brlcad: ping |
| 08:08.54 | *** join/#brlcad TheJollyRoger (~Jolly_Rog@gateway/tor-sasl/thejollyroger) |
| 11:08.28 | *** join/#brlcad TheJollyRoger (~Jolly_Rog@gateway/tor-sasl/thejollyroger) |
| 16:22.22 | teepee | Moult: you should have received an invitation for the github team that maintains the GSoC repository |
| 16:23.19 | teepee | I hope we'll use that again for the application, but even if that should change, having the projects written out there is 95% of the required work |
| 18:03.08 | *** join/#brlcad TheJollyRoger (~Jolly_Rog@gateway/tor-sasl/thejollyroger) |
| 21:31.02 | Moult | teepee: so when should i start creating issues with project ideas? |
| 21:33.28 | teepee | I'd say, if someone has time for that, go ahead, brlcad confirmed the plan to apply, so there's no blocker for starting with preparation |
| 21:34.17 | teepee | I don't know if there's any plan for different presentation, but even if that would happen, copy&pasting the project ideas to somewhere else would not be a huge thing |
| 21:34.41 | teepee | the main task is certainly writing up those ideas, at least that's my experience |