[sakai-core-team] OSP Projects and trunk

[Charles Hedrick]

I’ve looked at it under Morpheus. I’ll fix anything that breaks. I’m just not sure we’ll have a big enough QA effort to find it all. I’d leave it where it is, make it writable, but not include it in the modules built.

We’re moving our OSP projects to other software. But we’ve got existing data that we’re going to have to be able to retain access to. Either we’re going to have to make it work for a few more years or we’re going to have to split out a copy of Sakai just for OSP and keep the version frozen. If it’s not much work it’s probably better to keep it working.


> On Jan 28, 2015, at 4:32 PM, Matthew Jones <matthew at longsight.com> wrote:
> 
> Yeah, agreed, moving to contrib would be *nice* but would be an effort to both have wush do a dump and filter to get these repositories out and load it into contrib retaining the history, and if we just removed it, it would break anyone that's currently using it. 
> 
> If significant effort continues on it, it should be in a separate github repository under Apereo, but I have a feeling these are maintenance fixes. I just saw this one for 2.9 and seemed like it might be applicable to both 10.x (where OSP is still used) and trunk.
> 
> I'm just going to restore write to these projects and comment on this ticket.
> 
> On Wed, Jan 28, 2015 at 4:16 PM, Earle Nietzel <enietzel at anisakai.com <mailto:enietzel at anisakai.com>> wrote:
> Understood makes sense...
> 
> On Wed, Jan 28, 2015 at 4:12 PM, Anthony Whyte <arwhyte at umich.edu <mailto:arwhyte at umich.edu>> wrote:
> That option I consider not an optimal use of admin time.  Besides for earlier versions of Sakai OSP is not contrib but production.  So avoid confusion, keep it where it is and as Matt suggests restore write permissions to it.
> 
> Anth
> 
> On Wed, Jan 28, 2015 at 3:35 PM, Earle Nietzel <enietzel at anisakai.com <mailto:enietzel at anisakai.com>> wrote:
> We should probably move osp to contrib and any other projects that didn't come over to github that are in trunk?
> 
> On Wed, Jan 28, 2015 at 12:42 PM, Matthew Jones <matthew at longsight.com <mailto:matthew at longsight.com>> wrote:
> I'm thinking we should make the osp projects (reports/osp/metaobj/warehouse) trunk writable again so commits like this aren't lost just incase anyone is fixing bugs in there. These projects didn't come over into the sakai github branch.
> 
> https://jira.sakaiproject.org/browse/SAK-29024 <https://jira.sakaiproject.org/browse/SAK-29024>
> 
> I think if someone wanted to take the lead and maintain them that it would be nice if they had their own separate repository in github, but this seems like the easier fix for now to keep it maintained in svn.
> 
> Any thoughts? Just happened to see this commit come across.
> 
> _______________________________________________
> sakai-core-team mailing list
> sakai-core-team at collab.sakaiproject.org <mailto:sakai-core-team at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team <http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team>
> 
> 
> 
> 
> -- 
> earle,
> asahi net int.
> 
> _______________________________________________
> sakai-core-team mailing list
> sakai-core-team at collab.sakaiproject.org <mailto:sakai-core-team at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team <http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team>
> 
> 
> 
> 
> 
> -- 
> earle,
> asahi net int.
> 
> _______________________________________________
> sakai-core-team mailing list
> sakai-core-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150129/e800768c/attachment.html