On May 23, 2010, at 8:33 PM, Guillermo Polito wrote: > Hi! > > First I may introduce myself. My name is Guillermo Polito and I'm from > Argentina. I've been using Pharo for several months with some colleagues > that are already here to teach OOP in the UTN university, and i've been > suscribed to this mailing list for some time. But it's my first mail here :P.
Welcome > > I participated yesterday in the Pharo Sprint in Argentina and there I had my > first look at the issue tracker. Thanks for your time. I will go over the produced fixes today using Torch :) > And well, it seemed to me to be a little messy. There are lots of issues > that aren't properly explained, some of them are duplicated, and they are not > well organized. And you would not imagine if we would not spend a lot of time on it.... This is like a garden. > It would be nice to use the labels googlecode provides to give them some > categorization, so we can browse them in a more intelligent way. Maybe we > can split the issues in "modules" (like Collection issues, Compiler Issues, > Closures Issues, Networking Issues...) or something like that. That will > help in avoiding duplications and looking for issues to solve (because I can > look for issues in the modules I know the most). > > At the moment I will stay looking for issues i can fix or commenting the ones > that lacks information :). Excellent Tagging the entries with semantics is a good idea. > > Regards, > Guille > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
