As frequent visitors to the forums may have noticed of late, I have become more of a bottleneck than anything else for SQLUnit. The reason is increased responsibilities at work, and to some extent, my increased involvement in things other than SQLUnit.
I would rather step down as project owner and let someone else take over if somebody will volunteer, rather than be a bottleneck. SQLUnit is fairly stable now, so there is not much work that needs to be done for it. So a deep understanding of the code is not mandatory, though preferred. The person must have the time to post submitted patches to CVS, and to make regular releases (perhaps once in 3 months?). Alternatively, at the new project owner's discretion, the patch submitter may be given CVS commit rights to CVS as well.
I can be available to answer questions and to help out if needed.
Let me know. Thanks
-sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
As frequent visitors to the forums may have noticed of late, I have become more of a bottleneck than anything else for SQLUnit. The reason is increased responsibilities at work, and to some extent, my increased involvement in things other than SQLUnit.
I would rather step down as project owner and let someone else take over if somebody will volunteer, rather than be a bottleneck. SQLUnit is fairly stable now, so there is not much work that needs to be done for it. So a deep understanding of the code is not mandatory, though preferred. The person must have the time to post submitted patches to CVS, and to make regular releases (perhaps once in 3 months?). Alternatively, at the new project owner's discretion, the patch submitter may be given CVS commit rights to CVS as well.
I can be available to answer questions and to help out if needed.
Let me know. Thanks
-sujit