Discussing this 'wassup' script, something that just came to mind: I
think OpenSRS probably has a lot of competent programmers as RSPs who do a
lot of work to get their own configurations in working order. Given the
present state of Tucow's development team (I certainly dont think they're
incompetent, they just have a lot to do), I would think that Tucows would
want to draw on this talent base more than they do.
Think of it this way: if you have, say, 75 resellers who use
Authorize.Net to do realtime transactions, they probably all spent at least
several hours integrating this into the distribution scripts. So say each
one of those 75 resellers dedicated 8 hours to this task (for me it was a
good deal longer). Thats 600 manhours of work that went into a problem that
could have been solved much more elegantly in much less time if there were
some kind of cooperation involved. I think that most of the people involved
in OpenSRS are very keenly aware of the benefits of the open source movement
and would gladly put their work toward the public good if there were an easy
way to do so.
Although I hate to shove an idea out without a clear solution to the
problem, this is indeed a discussion list. Although I am not exactly sure
what it is, I am sure that there is a way for those RSPs that feel inclined
to share their development work in such a way which wont poison the
integrity of the current code base. Its obviously something that should be
thought about. Especially with the 'branching' of the codebase to include
selling certs and that sort of thing.
Anyway. Theres my 2cents. Apologies for the ranty long-windedness. : - )
- Matt
