[Building Sakai] Hijri Calender

[Neal Caidin]

Trunk will give you the very latest code base, the most up to date. But it
depends on what you are trying to achieve. If you are working on getting a
version of Sakai 10 up and running, for example, you will want to work on
the 10 branch. If you are working on a big new feature, like Hijri, it
probably makes sense to work on trunk (but it still depends on the
specifics of your goals).

You can change code for your needs locally. If you want to contribute back
to Sakai, you will need to fill out licensing agreements, probably have one
filled out for your institution (if you are doing this as part of your job
for example, which is usually the case) and one for yourself, an individual
license [1].  To see our licensing terms go to [2].

We are planning to move to Git/Github for trunk in about a month or so. We
will keep this sakai-dev list posted.

When you contribute code back, at the moment, it would be by opening a Jira
ticket and adding your patch. You should either label the Jira type as
Contribution or as a New Feature and add a "PATCH_ADDED" label. It can help
immensely to attend a Sakai core team meeting and discuss your contribution
and/or get it reviewed. Actually, getting input as early as possible for a
patch potentially the size of the one you might be considering would be
critical, and keeping the Sakai core team updated on your progress. I
realize that time zone difference might make attending a meeting difficult,
in which case we can still use email and we have an online code review
system [3].

(Maybe this is documented in Confluence somewhere with more details?)

Is this getting close to what you need?

[1] https://www.apereo.org/licensing
[2] ECL v2.0 licensing - http://opensource.org/licenses/ECL-2.0
[3] Source code review system -  https://crucible.sakaiproject.org


On Sun, Nov 30, 2014 at 4:42 AM, ahmed adel <abou.alseoud at gmail.com> wrote:

> Unfortunately, yes i'm new to the community and taking step by step into
> how i modify things inside Sakai. I need to know first which SVN URL i
> should use to get all new fixes and feature, the trunk or a branch? Am i
> allowed to change code in one of the Sakai module or i must create new
> module to be able to do my work? How i do modification without affecting
> Sakai code and also override the default behavior and do my required
> business?
>
>
>
>
>
> On Fri, Nov 28, 2014 at 6:27 PM, Neal Caidin <neal.caidin at apereo.org>
> wrote:
>
>> Hi Ahmed,
>>
>> From the ticket it sounds like there is interest but no resources
>> available to address this change.
>>
>> What are your thoughts on getting resources to do the development? Are
>> you new to the community (and therefore maybe not familiar with how things
>> get addressed)?
>>
>> Best regards,
>> Neal
>>
>>
>> On Thu, Nov 27, 2014 at 8:20 AM, ahmed adel <abou.alseoud at gmail.com>
>> wrote:
>>
>>> Hi guys,
>>>
>>> I need to make the calender use Hijri date beside Gregorian date. I
>>> found this Jira feature but it's unresolved
>>> https://jira.sakaiproject.org/browse/SAK-22659
>>>
>>> --
>>> *Ahmed Adel*
>>> Senior Java Developer
>>> Cairo - Egypt
>>> Mobile no.: (+20) 100 3610 769
>>>
>>> _______________________________________________
>>> 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"
>>>
>>
>>
>
>
> --
> *Ahmed Adel*
> Senior Java Developer
> Cairo - Egypt
> Mobile no.: (+20) 100 3610 769
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20141201/87a0d45b/attachment.html