Ask yourself do you have any specific requirements you need to solve at your university that makes it easier to develop your own code. Having your own system can make a lot life easier when customising specific features, though I'd advise you keep the core features as simple as possible to make life simpler. It is a lot of work for an individual to develop and maintain a CMS so get others involved if you haven't already. There's nothing better than peer review :-)
Open Source CMS software may well do the job for you, but you'd need to evaluate each one carefully. The knowledge you've learnt by developing your own CMS will undoubtedly help you with any such research. Often such software is targeted at certain sectors (i.e. portal sites, intranets) so look at example customers which match your situation. >From a brief look around MySource Matrix seems very comprehensive. It has support for versioning and metadata schema though it is PHP4 (which isn't in itself bad though it means you cannot use Zend Framework with MySource Matrix). And possibly important for you it doesn't seem to have support for multiple languages in the core. Finally bear in mind you have written your CMS already. Unless it's broken or needs very high maintenance it is worth rolling it out to one or two departments for evaluation to see if it will work across your university. best wishes, Si
