On Sun, Oct 23, 2011 at 11:01 PM, Aaron Meurer <asmeu...@gmail.com> wrote: > Great! > > I have created labels in the issue tracker, CodeIn-Code, > CodeIn-Documentation, etc., and also CodeIn-Easy, CodeIn-Medium, and > CodeIn-Hard. If people can tag issues based on > http://code.google.com/p/google-code-in/wiki/GCIAdminMentorInformation > that would be good tasks, this would be great. We have to have at > least five tasks in each category to apply, and obviously we will need > many more if we are accepted. Also, we should create new issues for > various things. If you want to help but don't have the ability to add > labels to issues in the issue tracker, just let me know and I will > give you the access.
I also think the Code-In is a great idea (I wanted to comment sooner, but just couldn't find the time). As I've spent a lot of time lately looking at the various issues, I'll try as much as I can to tag them appropriately (and add new issues, if required). It might be a good idea to consider a more thorough cleaning of the issue list now, like we've discussed before (Aaron). Closing old issues lowers cruft and might inspire people to make some more Code-In tasks (was this called GHOP before?). > > By the way, according to people here at the mentor summit who have > participated before, we should not underestimate what some of these > students can do. So don't be afraid to mark somewhat difficult tasks > for CodeIn. > > Aaron Meurer > > On Sun, Oct 23, 2011 at 2:35 PM, krastanov.ste...@gmail.com > <krastanov.ste...@gmail.com> wrote: >> I would also like to help. Hopefully I'll find the time. >> >> About the translations - I speak Bulgarian and I can probably find few >> people willing to help with French translations. >> >> Stefan Krastanov >> >> On 23 October 2011 21:33, Aaron Meurer <asmeu...@gmail.com> wrote: >>> >>> Another thing: we need to have at least five translation tasks. We >>> were thinking to just create tasks for translating tutorials. We need >>> to have people who are fluent in the language to evaluate the task. >>> Apparently, the task should only be considered as completed if the >>> translation is perfect, i.e., from someone who is also fluent, to >>> avoid people using machine translations. What languages are people >>> fluent in, who are willing to evaluate translations tasks? Ondrej >>> speaks Czech and Mateusz speaks Polish. I speak Serbian (Bosnian/Croatian/Montenegrian etc) fluently and I can help with Czech, too. I'd also be willing to help with reviews and generally I plan to be around on IRC (time-permitting). In particular I can be around for US-centric holidays and Christmas (since our Christmas is on the 7th), as that webpage you linked to recommends. I also took a look at the categories of tasks we need to have, and I think we are going to have troubles with some: * Translation. Disregarding the fact that between all of us, we still cover only a few languages, there's a question of _what_ to translate exactly? I think translating the tutorial is fine, but getting people to translate all our documentation would be a bit too much. I don't think it would be used much, it'd almost definitely be outdated and fact is, SymPy just doesn't depend so much on translations and as such we have no framework around it. We can translate the SymPy Live UI at least, though. I'm sure it's impossible but could we somehow waive that requirement? * Research. Seeing as we're talking about some pretty hardcore math here, I doubt the average high school student will be able to contribute. I'm sure we can scrounge up the 5/10 tasks required, but it'll be a stretch. There's also the question of how many new tasks do we wish to create? Usually, we don't make tasks as such small "chunks" (eg. all the Documentation tasks about See Also Hector made -- I like them though, nothing against it) so I'm worried we might spam our issue tracker a bit if we over do it (not that it doesn't have so many open issues right now). Just something that crossed my mind... >>> >>> Aaron Meurer >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "sympy" group. >>> To post to this group, send email to sympy@googlegroups.com. >>> To unsubscribe from this group, send email to >>> sympy+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/sympy?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sympy" group. >> To post to this group, send email to sympy@googlegroups.com. >> To unsubscribe from this group, send email to >> sympy+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/sympy?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to sympy@googlegroups.com. > To unsubscribe from this group, send email to > sympy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > > -- Vladimir Perić -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com. To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
