[Building Sakai] 2.7 update

[Steve Swinsburg]

I like the idea of more bundles and less separate services, ala the 
edu-service, bringing all the common functionality that these services 
depend on, into one module that can be installed or not.

It will make pulling out or adding in tools and services to a local 
install much easier. I often  work on the cafe source but as soon as I 
want to bring in an additional major tool I find I need half a dozen 
other tools as well since they all depend on each other. Having a 
smaller subset of service bundles will make this much easier.

Whilst keeping tools separate makes thing more modular, grouping common 
services into one makes good sense.

+1

cheers,
Steve

-- 
Steve Swinsburg
Systems Developer
Enterprise Systems
Division of Information
K Block, Building 3K
The Australian National University
Canberra ACT 0200 Australia

T: +61 2 6125 6608
F: +61 2 6125 0449

CRICOS Provider # 00120C



David Horwitz wrote:
> Hi Chuck
>
>> This is fine as long as the only thing that is happening is source 
>> moves and artifact renaming.   I would suggest *not* changing package 
>> names or API signatures for the moved code until after 2.7 - this 
>> way, if patches need to move backwards or forwards, the only thing 
>> that changes is where the patch goes in the source tree (at least for 
>> 2.7).
>>
>> Lets not make API changes simply to make package names "prettier".
>>
>
> That is exactly what I propose.
>
>
> As 2 the gradebook change I had 2 aims in mind:
> 1) Rationalize the our dependencies (as we did with k1) to enable the 
> tool releases and at the same time keep Sakai fairly modular.
> 2) Prevent the forking of code and effort in the community maintaining 
> 2 sets of code.
>
> 1) Is where my self interest lies. However examining the code shows 
> that simply isolating the gradebook service won't suffice because that 
> gets us stuck in another set of dependencies. So modified proposal:
>
> *2) Create edu-service package (was Separate Gradebook Service from tool)
> *Create a package of common teaching service (open to name suggestions 
> for it). The list of services to include:
> a) gradebook service
> b) coursemanagement service
> c) sections service
>
> D
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090930/88dfc68c/attachment.html