[sakai2-tcc] OSP as an indie

[Steve Swinsburg]

Hi Noah,

Runnings a grep over trunk, It looks like warehouse is only used by OSP itself, whereas metaobj is a bit more widely used. This would mean these need to be indie releases as well.

Of course there may be contrib or local projects that are affected, whose poms will need to be updated as required if they want to move forward.

I don't think anything outside OSP depends on OSP itself does it? In that case it should be relatively straightforward to bundle up into a discrete package.

cheers,
Steve



On 25/11/2010, at 10:59 AM, Noah Botimer wrote:

> While it generally seems like a fair idea with its merits (and some costs), we just didn't get to it for 2.8.
> 
> If I remember correctly, the remaining plan was to have a look at the dependencies (including metaobj and warehouse) to see if anything else would need to be broken out, work with the OSP committers to understand the POM changes, and get things set up in Hudson so we could churn out releases in a click.
> 
> To me, this is a case study. If it's ugly because of dependencies, and we talk about shuttling more stuff into the meta-modules (common, edu-services), we've got something grossly wrong. I've had a suspicion for a while that we've been half-stepping and should just get to where we're going if it's the right idea. Piecemeal frobbing won't help anyone. But I think that's a whole discussion by itself.
> 
> Thanks,
> -Noah
> 
> On Nov 24, 2010, at 5:55 PM, Steve Swinsburg wrote:
> 
>> Hi all,
>> 
>> A while back we discussed making OSP an indie release. Did this get any traction?
>> 
>> thanks,
>> Steve
>> 
>> _______________________________________________
>> sakai2-tcc mailing list
>> sakai2-tcc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>> 
>> 
>