Hi, On 03/23/2012 05:48 PM, Martin Paljak wrote: > The trick is having a system that works and also helps to achieve the > target of having more people *actually* looking at code and some > testing (like automatic building) done before even considering ack-ing > something. But lagging on processing any flow is of course not really > acceptable. Given that resources are low, automation should help. Like > Gerrit och Jenkins.
Yes, but if you cannot sustain that infrastructure, then it is a stumbling block rather than a help. Maybe it could be solved by enabling more access to it. Or if this is not the way to go, than you can relay on people building and reporting back by hand. >> Maybe a daily^H^H^H^H^Hweekly scrum in >> IRC would be a good idea. > There is #opensc on freenode, but people on opensc-devel have most of > the time to date been against such communication, either because of > timezone differences or just because it is very difficult for a > handful of otherwise busy people to find that time (I guess). doodle would help on that: http://doodle.com/ > But a bi-weekly "recap" would be good idea to have. > > _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
