dirakx: yup. So, I will be comfortable, if the bug-filing is done by someone who has been at the helm longer (you, anish, anyone else); and the tickets assigned to me as appropriate. The estimations may initially be set by the filer, and later changed (if at all necessary) by me (and that will most probably happen, if the ticket(s) need way more R&D)

ajay_, m_anish: sorry, the dev meeting took longer than planned and tired me out quite a lot (check out http://meeting.sugarlabs.org/s[…]11-12-13T15:00:22 when you have some time; I passed the maintainership of sugar-toolkit-gtk3 to dsd+erikos). Let's try to work on the WPA2-Enterprise patch Fri or Sat (are you working on Sat?).

diraksx, silbe: regarding the WPA2 enterprise patch, it's more or less complete from my side (just the LEAP configuration not testable due to lack of setup). So, it's (WPA-enterprise patch) is not too much to handle for me in parallel (with ceibal and au).

ajay_: I see you're using eval(). I don't know where the data you're eval()ing is coming from, but try to avoid it anyway. The debug prints should be removed as well (interesting that you seem to prefer them over logging.debug()). AUTHENTICATION_LIST is indented too much and (as a global constant) should be moved to before the classes.

alsroot, ok, I think what they want most is a working build, the impression I got from Sridhar is that they are happy postponing stats enhancements for a future release, but i still need to confirm with them rather than make the decision unilateraly

1. eval() is being used to read the data from "connections.cfg" in the required python-type form (list here); not doing it, reads the data as a string (and not "list"). 2. Regarding the logs, I will be careful (sorry). 3. I will move AUTHENTICATION_LIST right at the beginning (thanks); the indentation is there for aesthetic purposes, so as to aid reading the deeply nested elements easily.

pflores: if you can get me an Olidata JumPC (or tell me where to get one here in Europe), that would be appreciated. Emulation is a good start, but I'd like to get a feeling for how close to the screen the viewer will usually be (=> angular size).