[Building Sakai] Sakai core modules business changes

[Matthew Jones]

You either
- Submit a patch on a jira can be disabled with a property that can be
contributed to the community code. If it can be completely disabled then it
can be backported to previous versions of Sakia.

- Apply a patch as part of your pre-build process. Some schools did this
pretty regularly, download the source code, apply all local patches, build.
The biggest problem with this is local patch files can possibly become out
of date and cause conflicts if you want to get newer updates in the future
(like 10.1 and 10.2) but resolving conflicts against a fork would be the
same amount of work.

- You can make a copy of the code in git (like github) and apply the patch
there. There is an Sakai mirror that has seemed to stay updated in github (
https://github.com/sakai-mirror) that you could also fork. We're planning
on putting Sakai 11 (latest trunk) in github in the near future, though
that wouldn't help so much for old code, probably this old mirror would be
better. You'd have to do that yourself for those old versions. You can just
a github repo in your regular svn externals.

On Mon, Oct 20, 2014 at 10:16 AM, ahmed adel <abou.alseoud at gmail.com> wrote:

> Dear all,
>
> Did anyone faced a situation to change a functionality or the business of
> a core module like assignments?
> What will the best solution to accomplish this change without the need to
> fork from Sakai SVN updates and commits?
>
> Best regards
>
> _______________________________________________
> 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/20141020/9a9a923f/attachment.html