[sakai-mobile] Mobile Sakai ­ Next Steps

[Klapdor, Timothy]

Thanks Doug,

Thanks for the email and call to action! The division of working groups
looks fine to me and seems like a good way to structure a way forward.

I would be happy to contribute staff resources and time to both D & E
groups (Interface & OAE) as part of CSU's mobile learning project. I would
be also willing to put my hand up to lead some this work - the Interface
area would be my preference.

I personally can't offer a lot of technical skills but have a background
in design, web and multimedia. We will have two new staff - a graphic and
interface designer and a UI developer - joining the project by the end of
the year who will be resources specifically allocated to work on mobile
across a number of areas in the university. The UI developer will have
their primary focus on contributing to mobilising Sakai.

The schedule for our project has us working to mobilise some of the CLE
tools we will be running in Hybrid before moving onto our OAE work in
around May 2012. We might not be able to contribute a lot in the February
code bash but we would definitely like to take part and contribute where
we can.

My team would be more than happy to contribute to the initial discussions
and planning for the direction of the mobile sakai project and to help
things get underway. I would love an opportunity to get a broad snapshot
of what the community is doing and to understand where are our common
points. Could I suggest an online meeting of some sorts or a collecting an
overview from each institution of what they are working on and their
priorities for the next 6-12 months??

Looking forward to it all kicking off!

Cheers

Tim Klapdor
Media Technologist - Strategic
Learning & Teaching Innovation | Division of Learning & Teaching
Services
Boorooma Street
Wagga Wagga, NSW 2650
Australia
Tel: +61 2 6933 2233
Email: tklapdor at csu.edu.au



On 4/11/11 9:08 AM, "Johnson,Douglas F" <wanderer at ufl.edu> wrote:

>Greetings All; and a special welcome to those who have joined us
>following the EuroSakai Conference!
>
>While in California and in Europe, I spent a fair amount of time talking
>to various individuals and groups about this Mobile Sakai initiative. To
>put it mildly, wrapping my mind around all the various initiatives
>already under way has been quite a challenge. At the same time, it has
>been truly exciting to me to be able to engage the vast creativity of the
>Sakai Community, even at a superficial level.
>
>That being said, I think the biggest task in front of the Mobile Sakai
>project is to figure how best to tap your expertise and creativity to a
>more-or-less common end. So I have three proposals to put forward:
>
>1. After many discussions, I¹d like to suggest we establish five working
>groups:
>       a. Data ­ What data? How to move data to and from mobile devices? Most
>likely focusing on Entity Broker
>       b. Authentication & security ­ OAuth/Shibboleth; addressing security on
>mobile devices, two factor
>                authentication?
>       c. Services ­ Identifying. prioritizing Sakai tools to work in the
>mobile environment; identifying necessary
>               components to mobilize
>       d. Interface ­ UI/UX
>       e. OEA ­ Defining a-d above for OAE
>
>To start with, I need someone to volunteer to coordinate each work group;
>so let me know ASAP if you¹re interested. For example, I know that
>Charles Sturt is very interested in the OAE work; Indiana has done good
>work on data exchange; and Oxford has done some excellent work on
>Authentication and Mobile. If these schools are willing to bring their
>work to the table, we could find ourselves well on the way to a
>functioning project. The work group leaders primary tasks will be to: a)
>coordinate group activities (conference calls, coding sessions, etc.); b)
>to maintain and update files and documents associated with the work
>group; c) to serve as the primary interface with other work groups; d) to
>guide actual work within each work group.
>
>Each working group will be tasked with identifying a coherent direction
>for addressing fundamental issues (e.g. What data is needed on a mobile
>device? How best to ³chunk² and transfer data? Etc.). In addition, each
>work group will want to collect code to address these processes from
>various participants willing to share ­ these code contributions will
>become a ³seed bank² for further development.
>
>2. To help stimulate the actual development process, I¹d like to schedule
>a ³Virtual Sakai Mobile Hackathon² (or ³Code Bash,² or whatever you
>prefer to call it) shooting for some time in February 2012 (³Sakai Winter
>of Code?²). I am proposing a ³work where you are,² follow the sun,
>48-hour (plus) marathon of collaboration and coding mediated by
>synchronous and asynchronous collaboration tools. Coding teams would use
>a common repository for documents, documentation, code, etc. (see item 3)
>with various participants picking up where previous work left off as
>daylight (or moonlight for you nocturnal coders) travels around the
>planet.
>
>After the Hackathon, we¹ll meet to regroup, assess where we are, and
>identify next steps in reaching the common framework for Mobile Sakai.
>
>Ideally the 5 work groups will each have a number of conversations
>between now and February to frame specific goals and objectives for their
>own piece of this Hackathon.
>
>3. We need to set up a working repository for documents, code, and any
>other ³artifacts² related to this project. One obvious possibility is for
>everyone to upload files to the Mobile Sakai Confluence site
>[http://tinyurl.com/sakai-mobile] ­ though that is not the ideal location
>for storage. Another possibility is that I can set up some Google
>resources (docs, hangouts, etc.) to host materials and collaboration.
>
>Comments and suggestions are welcome on each and all of these topics. So
>let¹s get the discussion started and quickly follow that with some work!
>
>
>Peace,
>
>Doug
>
>-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>Douglas F. Johnson, Ph.D.
>Assistant Director for Learning Services
>Office of Information Technology
>Hub 132 | 352.392.4357, opt 3.
>
>Between the idea and the reality Š Between the conception and the
>creation Š Falls the Shadow.
>- T.S. Elliot, The Hollow Men
>
>_______________________________________________
>sakai-mobile mailing list
>sakai-mobile at collab.sakaiproject.org
>http://collab.sakaiproject.org/mailman/listinfo/sakai-mobile

Charles Sturt University

| ALBURY-WODONGA | BATHURST | CANBERRA | DUBBO | GOULBURN | MELBOURNE | ONTARIO | ORANGE | SYDNEY | WAGGA WAGGA |

LEGAL NOTICE
This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University (CSU) does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with CSU may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at CSU. The views expressed in this email are not necessarily those of CSU.

Charles Sturt University in Australia  http://www.csu.edu.au  The Chancellery, Panorama Avenue, Bathurst NSW Australia 2795  ABN: 83 878 708 551; CRICOS Provider Numbers: 00005F (NSW), 01947G (VIC), 02960B (ACT)

Charles Sturt University in Ontario  http://www.charlessturt.ca 860 Harrington Court, Burlington Ontario Canada L7N 3N4  Registration: www.peqab.ca

Consider the environment before printing this email.