[sakai-core-team] OSP Projects and trunk

[Anthony Whyte]

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>
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>
> 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
>>
>> 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
>> 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/20150128/42f93823/attachment.html