[Building Sakai] Sakai development estimate

[Steve Swinsburg]

Hi Benjamin,

Without having fuller details, you'd be looking at a few months, maybe 4-6,
and feasible for one developer.

Can you elaborate on the lessons aspect, do you mean the lessons tool? Or
Sakai overall? You mention navigation so I wasnt sure if that meant Sakai
overall.
For peer reviewing, would they be new tools or modifications to existing
tools? If mods, which ones?
For responsive design, there is a new portal and skin coming out of NYU
that adds this, so you might be able to utilise that. It will be for Sakai
10.
For localisation, what locale/language?

You probably want to get the deployment right first, so you know how the
build works and how things come together, then modify code and add bits and
pieces. I'd allow a week or two to get the build/deployment process
understood and bedded down and code modules figured out, then you could
begin development on the features you were after.

Depending on when you start, I would probably be using the Sakai 10 branch
so you can take advantage of the new features and save yourself some time.
In 6 months the release will be well and truly nailed down so you'll be on
a stable codebase. Keep up to date.

cheers,
Steve


On Thu, Feb 27, 2014 at 8:53 AM, Benjamin Fouassier
<b.fouassier at gmail.com>wrote:

> Hi everybody,
>
> I am completely new to Sakai (and open source projects actually), beginner
> in Java (but advanced in OOP and design patterns using PHP and AS3 with
> FLEX framework) and would like to have your opinion about a Sakai project
> implementation in terms of time estimate and feasibility.
> Without giving too much details, here are the main steps :
>
> - Deploy Sakai from the current trunk on a "classic" hosting platform
> (that validates the requirement Java / Tomcat / etc..) to validate the
> process of installation / deployment.
> - Changing completely the presentation layer, including the way lessons
> are visually represented as the menu to simplify a lot the navigation.
> - Extend/create some modules to add features in terms of sharing/peer
> reviewing
> - Responsive design
> - Localization
> - Deploy the final version on a cloud based environment such as AWS
>
> A rough estimate would be useful to know if this can be done within a
> couple of months, by a single developer, or this isn't realistic at all.
>
> Although from your experience, what do you think is the best way to get
> the development going, to start from the last release stable version and
> don't update or keep the code up to date with the last improvements
> committed in trunk ?
>
> Ultimately I would be glad to have your general opinion about this kind of
> sakai development.
>
> Thank you all for your help.
> Benjamin
>
>
> On Wed, Feb 26, 2014 at 11:41 AM, Benjamin Fouassier <
> b.fouassier at gmail.com> wrote:
>
>> Hi everybody,
>>
>> I am completely new to Sakai (and open source projects actually),
>> beginner in Java (but advanced in OOP and design patterns using PHP and AS3
>> with FLEX framework) and would like to have your opinion about a Sakai
>> project implementation in terms of time estimate and feasibility.
>> Without giving too much details, here are the main steps :
>>
>> - Deploy Sakai from the current trunk on a "classic" hosting platform
>> (that validates the requirement Java / Tomcat / etc..) to validate the
>> process of installation / deployment.
>> - Changing completely the presentation layer, including the way lessons
>> are visually represented as the menu to simplify a lot the navigation.
>> - Extend/create some modules to add features in terms of sharing/peer
>> reviewing
>> - Responsive design
>> - Localization
>> - Deploy the final version on a cloud based environment such as AWS
>>
>> A rough estimate would be useful to know if this can be done within a
>> couple of months, by a single developer, or this isn't realistic at all.
>>
>> Although from your experience, what do you think is the best way to get
>> the development going, to start from the last release stable version and
>> don't update or keep the code up to date with the last improvements
>> committed in trunk ?
>>
>> Ultimately I would be glad to have your general opinion about this kind
>> of sakai development.
>>
>> Thank you all for your help.
>> Benjamin
>>
>
>
> _______________________________________________
> 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/20140227/cc6130ba/attachment.html