From: Krzysztof D. <krz...@gm...> - 2014-02-25 04:31:01
|
Hello. I'm Krzysztof Drewniak. I'm planning to apply to Google Summer of Code in order to work on SBCL's Unicode support. I'm still thinking through the details of my proposal, especially since there's some things I could change that I should run by the list before proposing them. Who should I talk to about Unicode/string issues? Also, I went through the easy bugs list and made a patch for #777346, which involved making a very minor improvement to error reporting. I've attached the patch. Should I also upload it to Launchpad? kad |
From: Christophe R. <cs...@ca...> - 2014-02-25 10:28:52
|
Krzysztof Drewniak <krz...@gm...> writes: > Hello. I'm Krzysztof Drewniak. I'm planning to apply to Google Summer of > Code in order to work on SBCL's Unicode support. I'm still thinking > through the details of my proposal, especially since there's some things > I could change that I should run by the list before proposing them. Who > should I talk to about Unicode/string issues? This list generally is not a bad place for discussing design issues. Latency can sometimes be a bit high, but it's a reasonable place to start. > Also, I went through the easy bugs list and made a patch for #777346, > which involved making a very minor improvement to error reporting. I've > attached the patch. Should I also upload it to Launchpad? Here is fine, though since we're in code freeze it might be worth also putting it on launchpad so it doesn't get lost. Since it's here, though I might say: * please format the commit message so that linebreaks happen; * I would avoid "should" and language with implied value judgment. A neutral way of communicating the information would be better (e.g. "The datum X (of type Y) is not of type Z") * an entry in NEWS, formatted appropriately, would also be helpful. (entries in NEWS are almost guaranteed to conflict, though, so I'm not totally sure what to recommend as best practice). Cheers, Christophe |
From: Krzysztof D. <krz...@gm...> - 2014-02-25 17:08:40
|
On 02/25/2014 04:28 AM, Christophe Rhodes wrote: > Krzysztof Drewniak <krz...@gm...> writes: > >> Hello. I'm Krzysztof Drewniak. I'm planning to apply to Google Summer of >> Code in order to work on SBCL's Unicode support. I'm still thinking >> through the details of my proposal, especially since there's some things >> I could change that I should run by the list before proposing them. Who >> should I talk to about Unicode/string issues? > > This list generally is not a bad place for discussing design issues. > Latency can sometimes be a bit high, but it's a reasonable place to start. > >> Also, I went through the easy bugs list and made a patch for #777346, >> which involved making a very minor improvement to error reporting. I've >> attached the patch. Should I also upload it to Launchpad? > > Here is fine, though since we're in code freeze it might be worth also > putting it on launchpad so it doesn't get lost. Since it's here, though > I might say: > > * please format the commit message so that linebreaks happen; > > * I would avoid "should" and language with implied value judgment. A > neutral way of communicating the information would be better (e.g. "The > datum X (of type Y) is not of type Z") > > * an entry in NEWS, formatted appropriately, would also be helpful. > (entries in NEWS are almost guaranteed to conflict, though, so I'm not > totally sure what to recommend as best practice). > > Cheers, > > Christophe > I've attached an improved patch to the relevant Launchpad bug. Thanks! |