[Bodington-developers] Bodington Hosting and Implications for Development

[Jon M. <jo...@te...>]

Dear All,

I'm planning to launch a hosting service next year - Campus Academicus, 
www.campusacademicus.com.  (I start marketing in Spring with the 
intention of attracting schools and colleges who will start using the 
service in earnest in the autumn term of 2008.) I will be piloting it in 
the upcoming academic year with one college.

This will be a very low cost solution because a single Bodington 
installation will be shared by multiple customers.  Pricing will be 
based on the volume of uploaded files, not the number of users. My long 
term aim is to migrate from Bodington a little at a time to a new 
software product which I am planning to create myself.  However, in the 
short/medium term I need to do some fairly significant work on Bodington 
to make it work for my own application.  For example, I will be using 
administrative zones for each client but I also intend to give each 
client its own host name.  So, the top level resource menu will not be a 
list of buildings but a list of sites and the URLs of the sites will 
each refer to the root directory of a host.  As the service expands this 
will allow me to split clients off onto their own servers without 
changing the URLs. 

The question is, how can my work on Bodington fit in with those of you 
who are still using it? Is anyone out there planning to commit anything 
significant into the SourceForge project over the next year or so? Am I 
going to be the only person doing any work on Bodington during this 
period?  Can I just do whatever I want or is there anyone left whose 
approval/agreement I need to gain?

Jon