From: Jon M. <jo...@te...> - 2007-07-18 00:16:09
|
O.K. I hadn't realised it was quite that far out of synch. In which case it might be better for me to work out what has changed in sourceforge since the divergence and patch that onto the Oxford version to produce a new svn archive for my use. It would be helpful if you could answer two questions; 1) What was the approximate date that your svn started to diverge from sourceforge's cvs? If I know that, I can examine checked in changes to Sourceforge from that date to the present and produce some patches that can be applied to the current Oxford version to produce a merged version. 2) Do you think there are any things that you added to the Oxford localized version that are intended for use only at Oxford and which might cause problems for others? For example, you have an authentication system that is linked into the Oxford webauth - is that done as a nice friendly module which can be configured in or out or is it hardwired in? That's the sort of thing I'm thinking about. Are there other cvs/svn trees out there with even more source code in? Aggie? Sean? Aggie, are you producing new code that you want to check into Sourceforge? Is that why you would prefer me not to check stuff in at the moment? Lastly, a question for anyone who knows Sourceforge: if I set up an svn repository can the cvs one keep going in parallel? I think that might be ideal: I'd leave the cvs tree alone but import the Oxford svn into sourceforge and work on that - first applying patches one by one from the cvs tree and then working on changes that I need. If that isn't possible then I suppose I could create a new SourceForge project for this purpose: Boxingford, Oxbod, TheContinuityBOD, KNob = Knob is NOt Bodington. Some examples of things I want to add: *) Configurable sysadmin option for new user names to be anything you want (when not using administrative zones) or prefixed with a code for the admin zone or suffixed with @domain.ac.uk per admin zone. *) Option for use of multiple virtual host names at the top level - requires work on resource menus and the addition of a new type of resource 'network' at the root with 'site' at the next level down. *) New optional authentication module: provide email address and password. Depending on which site the URL refers to the form will assume the second half of the email address. Option for user to request new password - which will be sent to their email address. *) Addition of another cookie as part of the authentication with wider scope - the whole of the domain. This is to provide single sign on for users who access more than one virtual host name - i.e. navigate between the sites of different colleges. *) Option for user creation tool to send email to each new user with their password in. *) Improved management of aliases. *) Addition of a new resource which is just a 'folder' - folders will be allowed anywhere from sites down so that a site can be built just out of folders if the users aren't interested in the building metaphor. *) WebDAV functionality so that users can drag and drop files to and from Bodington using any WebDAV compliant tool. I think this might also require some restructuring of the way uploaded files are stored. Jon Paul Davis wrote: > If it was an hour or two, or a day or two we'd have synched frequently, but > I believe we'd be talking months of work and that wouldn't give us any > benefit I'm afraid. > > Adam's suggestion of using Weblearn code as your new core seems reasonable > to me - it's been updated, has bug fixes, has a reasonable level of user > testing - which is probably well ahead of any other version currently > > Paul > > ------------------------------------------------------------------------- > Dr Paul V Davis > Acting Head, Learning Technologies Group > Marketing coordinator, Bodington.org > Oxford University Computing Services > 13 Banbury Road, Oxford, OX2 6NN > Tel: 01865 283414 > > % -----Original Message----- > % From: bod...@li... > % [mailto:bod...@li...] On Behalf Of > % Jon Maber > % Sent: 17 July 2007 13:41 > % To: Bodington developers > % Subject: Re: [Bodington-developers] Bodington and WebLearn code > % > % What I had in mind was to put Oxford bug fixes into the sourceforge CVS > % at HEAD and to work on new features in my own file store. As I complete > % each new feature I can make a Bodington build available for approval for > % inclusion into the official source tree. > % > % Adam, do you think you could devote an hour or two to reviewing your own > % code repository to reassess the option that you might find time to > % commit it yourselves? I will work on it if that's the only option but I > % can't help thinking that the authors of the code might find the job > % easier. Maybe Paul Davis could fund some overtime.... ;-) > % > % Jon > % > % Alexis O'Connor wrote: > % > Matthew Buckett wrote: > % > > % >> In message > % <510...@HE...> > % >> a.g...@le..., Bodington developers > % >> <bod...@li...> writes: > % >> > % >> > % >>> Just to let you know that in FBS at Leeds we are still using the code > % from > % >>> SourceForge, so anything that beaks that would be bad news for us. > % >>> > % >>> Jon - it might be best for you to set up your own CVS repository, at > % least > % >>> initially. > % >>> > % >>> > % >> Could you just work on a branch in the SF CVS, at least then most of > % the code > % >> remains in the same place rather than getting more fragmented. > % >> > % >> > % >> > % > > % > Another branch certainly. It may even be an opportune time to switch to > % > using svn at sourceforge? > % > > % > Alexis > % > > % > > % > ------------------------------------------------------------------------ > % - > % > This SF.net email is sponsored by DB2 Express > % > Download DB2 Express C - the FREE version of DB2 express and take > % > control of your XML. No limits. Just data. Click to get it now. > % > http://sourceforge.net/powerbar/db2/ > % > _______________________________________________ > % > Bodington-developers mailing list > % > Bod...@li... > % > https://lists.sourceforge.net/lists/listinfo/bodington-developers > % > > % > > % > % > % ------------------------------------------------------------------------- > % This SF.net email is sponsored by DB2 Express > % Download DB2 Express C - the FREE version of DB2 express and take > % control of your XML. No limits. Just data. Click to get it now. > % http://sourceforge.net/powerbar/db2/ > % _______________________________________________ > % Bodington-developers mailing list > % Bod...@li... > % https://lists.sourceforge.net/lists/listinfo/bodington-developers > > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > > |