OK I guess I should chime in here. First thing SARE is going to do is get everything working as is right now. RDJ and rate limiter will learn to be nice to each other :)
Yes we have been getting slammed with the growing popularity of SARE. But we should be able to handle most with 1-4 mirrors if people had proper update schedules. (I'm still getting hits to my old site from a few peoples' RDJ scripts!! I'm about to firewall them if they don't wake up.) I don't think the ninjas mind what license we use. SF.net and Apache projects: The ninjas will start a dialog about this. What we don't want is red tape. We kind of paused a little with where we were going. Due to some miscommunications and such, we thought we might be stepping on some dev toes. It wasn't the case. But the devs and SARE have a very different approach to rule writing, and SARE has to continue to operate the way it does, very fast, very effective, and super sexy black uniforms :) Having lurked on the dev list for a while now, I can't believe how much work the devs already do. I can see why they don't have time to constantly write rules. They are very busy /b(?:ee|eaver)s/i ;) I'm also not sure if SARE even falls under a "Project" mentality for SF or even a subnet of SA in Apache. Its more like a group. SA is the project, and even an updater sub project of SA wouldn't really include SARE, as SARE isn't SA. (Does that make sense, or do I need more caffeine?) So I'll talk to a few devs, and the ninjas and see what direction is best. But again, for right now we will get this whole RDJ thing working properly once more. Thanks for all the suggestions, --Chris
