[Building Sakai] KNL-257 (Basic Auth) merging to 2.6.x (Kernel 1.0.x)
Lydia Li
lydial at stanford.edu
Wed Dec 9 11:49:20 PST 2009
Stanford is not yet running 2.6.x in production but we are working on
the upgrade. We will also need to run a custom local kernel at Stanford.
We use c3p0 instead of dbcp. We also have local modifications to the
authz(change default rules about provided/nonprovided users),
EmailNotification.java(while sending emails we also need to email back
instructors a list of inactive accounts based on LDAP info)
BaseContentService.java (change the default top level folder/file
visibility when doing site copy/import. I guess this could be made
configurable pretty easily)...etc. just to give you some examples.
It will be a while before we can do away with a custom local kernel, so
the less unnecessary merges the better.
thanks,
Lydia
David Haines wrote:
> What kind of customization is IU needing to make? I'm curious if
> there are changes that would be helpful to be in the kernel for
> everybody. It also might be that the specific IU changes are IU
> specific, but are examples of an area that several installations need
> to change. In that case maybe the customizations point to kernel code
> that should be more generic and so would save people from having to
> change the kernel.
>
> - Dave
>
> David Haines
> CTools Developer
> Digital Media Commons
> University of Michigan
> dlhaines at umich.edu
>
>
>
>
> On Dec 9, 2009, at 9:52 AM, Maurer, Christopher Wayne wrote:
>
>
>> We run a custom local kernel at IU.
>>
>> Chris
>>
>> On Dec 9, 2009, at 8:45 AM, Stephen Marquard wrote:
>>
>>
>>> I agree with this - I think code cleanup fixes should not in
>>> general get merged to maintenance branches, unless they end up
>>> being dependencies for other merges that are for actual bugfixes.
>>>
>>> I'm also curious to find out how many other 2-6-x sites are running
>>> custom local kernels?
>>>
>>> Regards
>>> Stephen
>>>
>>>
>>>>>> Matthew Buckett <matthew.buckett at oucs.ox.ac.uk> 2009/12/09 03:40
>>>>>> PM >>>
>>>>>>
>>> Some of the basic auth (base64 related) tickets in the kernel look
>>> like they might be merged to 2.6.x (Kernel 1.0.x):
>>>
>>> http://jira.sakaiproject.org/browse/KNL-270
>>> Subtasked into:
>>> http://jira.sakaiproject.org/browse/KNL-257
>>> http://jira.sakaiproject.org/browse/KNL-271
>>> http://jira.sakaiproject.org/browse/KNL-272
>>>
>>> While I think it's a good thing that this issue has been addressed I
>>> wouldn't class it as a bug and don't see that it need to be merged
>>> into the 1.0.x kernel.
>>>
>>> The reason I'm bringing this up is that we have some patches to the
>>> kernel and so maintain our own local version of it and the more
>>> patches that are pushed back to the 1.0.x branch the more stuff we
>>> have to merge.
>>>
>>> Our longterm aim is not to have a custom local kernel but sadly we're
>>> not there yet.
>>>
>>> --
>>> Matthew Buckett
>>> VLE Developer, LTG, Oxford University Computing Services
>>> _______________________________________________
>>> 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"
>>>
>>> _______________________________________________
>>> 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"
>>>
>> _______________________________________________
>> 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"
>>
>
> _______________________________________________
> 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"
>
More information about the sakai-dev
mailing list