On Tue, May 22, 2012 at 05:02:36PM -0000, Einstein Toolkit wrote:
Since we seem to be accumulating Trac issues with simfactory faster than for any other component (right now: 93 open simfactory tickets vs. 62 for Cactus which is the next biggest chunk), I'd like to suggest the following (this was originally prepared within <RANT>...</RANT> tags so hopefully I sufficiently defused the wording when copying it in):
We do not currently seem to have anyone in the project who is the official maintainer of simfactory (since Michael Thomas left LSU), yes? At least no one who feels confident enough and actually has time to fix bugs as they are reported? I admit that I am not very good at fixing bugs in simfactory since I most often find the code hard to understand and too deeply nested. Given that we consider simfactory one of our core components should we at one point schedule an EVO/Skype/Email/IM simfactory bug sqashing session to try and reduce the number and more maintainers become familarized enough with the internals?
... taking this to the users list ...
I think that this is in general a good idea. It will be a challenge to find time for it though.
Frank