You are looking at the HTML representation of the XML format.
HTML is good for debugging, but probably is not suitable for your application.
See complete documentation, or
API help for more information.
<?xml version="1.0"?>
<api>
<query-continue>
<allpages gapfrom="Rebelsky - CS2 Data Structures (Proposal)" />
</query-continue>
<query>
<pages>
<page pageid="463" ns="0" title="Rea, Yeates (Proposal)">
<revisions>
<rev xml:space="preserve">==Summary==
===Project Dissemination===
This resource will enable instructors to implement large-scale software implementation or rennovation projects in their classes using open source approaches, concepts, technologies, as well as agile development to analyze, develop, and implement successful collaborative projects between academia and industry.
The transition from http://teachingopensource.org/ to https://prod-openitup.rhcloud.com/
===Participants===
* '''Alan Rea''', Western Michigan University
* '''Nick Yeates''', Red Hat Incorporated
* '''Student Intern''', Western Michigan University.
Alan and Nick would work with a student intern to prepare all materials and processes. The student intern would be a student who was a team leader during the Fall 2015 project.
===Teaching Resource===
Ultimately, we see a combination of deliverables for this project residing on this Wiki, as well as the Teacher's Guide that will be present on the new TeachingOpenSource.org site.
These deliverables will include:
* '''Assignments''' used to help student teams move through the project and acquire knowledge and skills. Setting up OpenShift accounts and installing cartidges for testing, using Gimp to create sample rich wireframes, and helping them master using the myriad of Google offerings (Hangouts, etc.).
* '''Guides''' for approaching and implementing a similar FOSS or HFOSS project.
* '''Rubrics''' used to evaluate progress and deliverables.
===Process and Procedures===
We will put forth guides to help craft deliverables and move student teams through a large scale open source project.
For example, in order to ensure success we built in smaller deliverables and revisions of these deliverables as well as weekly check-in’s with the client and flexible objectives to keep the team moving forward on the established project critical path.
===Feedback and Rubrics===
We will discuss how one might best provide feedback to students in this agile collaborative environment as well as encourage students to provide feedback to their team.
Rubrics used to evaluate deliverables will be crafted to help instructors apply them to their projects.
===Suggestions for Implementation===
Here we will generalize the frameworks and processes we used to create and guide this collaborative process.
This will foster collaboration among instructors and open source communities.
==Target Venue==
===CIS3900: Business Web Architecture===
This course applies human computer interaction theories, principles, and techniques to develop effective and usable Web applications for the business environment. Topics include WWW architecture, modern web-based languages, search engines, interactive content, multimedia, and other technologies for the WWW. Students will evaluate the effectiveness of various websites and develop Web applications to support Internet commerce.
===TeachingOpenSource.org Project===
==Target Student Audience==
WMU routinely offers a Web Design and Development class for juniors and seniors at least once a year. Other than students specializing in electronic business marketing, this course is an elective for information systems majors. The course stresses client-side scripting (HTML5, CSS3, and JavaScript) as well as design theory. As part of the course requirements, students must work on a semester-long project to develop a website for either a business or a nonprofit client.
==Learning Activities==
===Assignments===
We used many assignments such as Site Specification, Information Architecture analysis, large-scale software research and recommendations (e.g., CMS), Prototype building, and actual deployments.
We will re-craft these assignments so that instructors can adopt them for their own uses whether these be for Web, mobile, or desktop development.
===Rubrics===
Throughout the course we routinely provided feedback to teams on initial drafts of deliverables, the deliverables themselves, and also many revisions. We will refine and share the rubrics that were used.
===Processes===
We will outline and discuss the processes we used making sure to note what worked well as well as flags of which one should be aware. For example, in our enthusiasm for the project we permitted too much scope creep. There are various reasons why this happened and we will put forth the warning signs.
==Evaluation==
We would supply the rubrics used for the class. Client feedback in terms of success or failure would also be used.
==Schedule==
'''Spring 2016''': Work with student intern to develop materials. Materials deployed on the wiki.
'''Summer 2016''': Finalize all materials as well as the TeachingOpenSource.org Website.
==Budget==
===Student Intern (Spring 16)===
'''$1500''': This will provide a stipend of 10 hours a week @ $10 for the student's work.
===Alan Rea (Summer 16)===
'''$1500''': Summer Stipend for finlizing all materials and sections on the new site.
===SIGCSE Travel and Expenses===
Alan Rea ('''$1000''')
To present the White paper at the POSSE workshop as well as work with faculty who are interested in implementing a project such as this one.
==Contact Information==
*'''Alan Rea''' (<rea> at <wmich> dot <edu>)
*'''Nick Yeates''' (<nyeates> at <redhat> dot <com>)
[[Category:Proposals]]</rev>
</revisions>
</page>
<page pageid="460" ns="0" title="Rea - Android Course (Proposal)">
<revisions>
<rev xml:space="preserve">==Summary==
Run a semester-long project in an upper-level Android development class.
This project will entail the use of many open source technologies to build an Android application (app) that interfaces via APIs with an Ushahidi (https://www.ushahidi.com/) server installed on OpenShift in order to enable a local community organization (to be determined) to track and report occurrences throughout a geographic area. Currently, we are looking at projects involving campus sustainability programs, voter registration initiatives, among other projects. Most likely this will be one large team of 10-15 students each performing various roles and contribution distinct modules to the overall Android Project.
This project will not only expose students to working with a FOSS community but also enable a local organization to experience the power that HFOSS can bring to the community.
==Target Venue==
===CIS4700 Mobile Commerce Development===
This is an advanced mobile programming course that focuses on advanced mobile commerce, or m-commerce, programming to include location-based services, mobile payment services and transactions, as well as designing and delivering advanced content and advertising for smartphones, tablets, and other mobile devices. Because m-commerce is constantly evolving, this course will integrate new topics as necessary as reflected in the mobile application development area.
===Android App Development with Ushahidi===
In addition to Android development and programming labs throughout the semester, a student team develops their own Android application throughout the course of the semester.
Student team leaders must convince others in the class to join their team according to the project being pitched to the class. Student teams then work to design, develop, present, and implement the Android application over the course of the semester.
Past student teams produced various mobile games, K-5 learning tools, bus route tracking, and customer loyalty apps.
'''However, this semester we will work as one team to create an HFOSS project for the community implementing an Android App via API connections to our own Ushahidi server.'''
==Target Student Audience==
This is an advanced programming and development course. Senior information systems and computer science majors take this course.
It is an elective course for majors and a required course for Business Mobile Development minors. CIS4700 requires students pass the pre-requisite course CIS2610: Business Mobile Programming.
==Learning Activities==
An assortment of smaller activities will contribute to the project's overall goals.
These are in addition to labs in the course that focus on particular advanced Android programming techniques and approaches such as encryption, network management, life-cycle control, etc.
Lab assignments will relate to the overall project needs and can be shared on the Wiki as part of the overall deliverable.
All other activities listed below are planned and will have deliverables associated with them and shared via the Wiki.
===Course Assignments===
Project assignments will account for 40% of the course grade with an additional 10% in exercises designed to help them master FOSS fundamentals.
====Community Interaction====
* '''Understand FOSS communities''' '''''(<span style="color: #ff9900;">Update</span>)''''' [[Intro to FOSS (Activity)|IntroToFOSS]] [[FOSS Field Trip (Activity)|FieldTrip]]: We will take time to explore all the Ushahidi offerings and compare it to other FOSS communities. Each student will write a short essay within the '''class project Wiki''' discussing how the Ushahidi offering compares to at least two other FOSS projects. Special emphasis on the project's wiki, documentation, and code repository so that students will understand how to develop and maintain usueful FOSS offerings.
* '''Understand FOSS development processes''' '''''(<span style="color: #00cc00;">New</span>)''''': We will mirror FOSS processes using GitHub, collaborative technologies (e.g., IRC or Slack), and agile programming. More on this in the '''Technology Implementation''' section.
* '''Participate in FOSS communities''' '''''(<span style="color: #00cc00;">New</span>)''''': Students will at a minimum take part in IRC or other weekly Ushahidi discussions at least twice during the semester and write about the experience in their '''blog''' '''''(<span style="color: #ff9900;">Update</span>)''''' [[Blog Activity]].
* '''Master a FOSS development processes''' '''''(<span style="color: #00cc00;">New</span>)''''': Perhaps not completely master, but a '''reflective paper''' at the end of the semester on the project discussing what the student has learned as a result of working with FOSS communities and building an HFOSS project.
====Technology Implementation====
In addition to the focus on developing advanced Android programming techniques, approaches, and designs such as fragment use, communication tools, and encryption, students will need to complete assignments and exercises that allow them to experience the following:
* '''Basic Git Usage''' with GitHub '''''(<span style="color: #ff9900;">Update</span>)''''' [[Git: Git Intro Activity]] : Similar to the basic Git assignment but focusing more on code management. Students will be permitted to use GitHub desktop (https://desktop.github.com/).
* '''Advanced Version Control''' with GitHub '''''(<span style="color: #ff9900;">Update</span>)''''' [[Git Activity 2]] [[Git Activity 3]] [[Git Activity 4]]: In this assignment each student will create their own repository. Other students will fork this repository, make code changes, and then issue pull requests. The repository owner must then manage merges while maintaining code integrity.
* '''Using Git with Android Studio''' '''''(<span style="color: #00cc00;">New</span>)''''': Android Studio allows for a Git plugin for code management. Similar to the '''Advanced Version Control''' activity students will learn how to manage and maintain Android code within the Android Studio.
* '''Use Dia for App Architecture and Design''' (This will depend if students can install the software.) '''''(<span style="color: #00cc00;">New</span>)''''': Tentative assignment. Students usually must design interfaces as well as software processes via LucidChart (https://www.lucidchart.com/). This semester we will move the same assignment to Dia if possible.
* Install, document the process, and use '''Wordpress on OpenShift''' '''''(<span style="color: #00cc00;">New</span>)''''': Each student will set up their own individual blog for the class on OpenShift. A class directory will be published and shared with POSSE.
* Install, document the process, and use a '''Wiki on OpenShift''' '''''(<span style="color: #00cc00;">New</span>)''''': The project will require students to install, configure, and maintain a project Wiki that should mirror comprehensive FOSS wikis complete with version information, usage guides, etc. This wiki will be made available to POSSE.
* Install, document, and use an '''Ushahidi server on OpenShift''' '''''(<span style="color: #00cc00;">New</span>)''''': The project will require an Ushahidi server to maintain data, as well as interface with the mobile application the student team will create. Specific students will be assigned to the server group. These students will follow Ushahidi install documentation and discuss the install process on their blogs. In addition, students must create an install process and perhaps a cartridge for the specific project server installation.
* Program, document, and implement an '''Android Ushahidi App''' '''''(<span style="color: #00cc00;">New</span>)''''': Although no one specific assignment is part of this deliverable, all previous activities discussed above are an essential component of developing a working deployed HFOSS Android app complete with documentation. This app will have been tested and deployed (at least as a prototype) by the end of the semester.
====Project Deliverables====
The final project demonstrates the power of FOSS technologies, processes, and approaches to mobile software development. Students will work to provide the robust resources found with the best FOSS offerings.
* '''Working Android Application''' '''''(<span style="color: #00cc00;">New</span>)''''': The application will be available on the project site and may be available on Google Play.
* '''Project Website and Wiki''' '''''(<span style="color: #00cc00;">New</span>)''''': The website will provide potential users with an overview of the application. The wiki will provide developer documentation as well as user information.
* '''User Guide''' '''''(<span style="color: #00cc00;">New</span>)''''': This will occupy a separate section of the wiki hosted on OpenShift.
==Evaluation==
===Planned===
* Students are required to fill out a course survey at the beginning and end of the semester to note if learning occurred.
* Use CATME (http://info.catme.org/) to help students understand how well they perform on the team.
* Rubrics and associated feedback on all project assignments as well as labs.
===POSSE Collaboration===
Instructor will complete the Institutional Context Survey.
At the beginning of the project we will conduct the student survey. The following questions will be used:
* All HFOSS questions.
* All General questions.
* CS1-CS3, CS7-11
* SE1-SE12
* Specific Ushahidi and Android Questions
Post questions will be asked as determined via POSSE collaboration.
==Schedule==
===Spring2016===
* Conduct pre- and post-surveys
* Develop assignments and materials
* Run the project
* Post updates to blog
* Submit Proposal to MWAIS and AMCIS
===Summer2016===
* Finalize materials
* Post all materials to Wiki
* Create section in the Teacher's Guide at http://teachingopensource.org
* Travel to MWAIS 2016 and AMCIS 2016 and present findings
==Budget==
===Spring16===
$1500: Develop Materials (Assignments, Rubrics, Videos, etc.), Run the Course, Post Updates to Blog
===Summer16===
$1500: Finalize Materials and Post to Wiki and Teacher's Guide
===Travel (Summer16)===
$1000: Defray cost of travel to MWAIS 2016 (http://mwais2016.sois.uwm.edu/) and AMCIS 2016 (http://amcis2016.aisnet.org/) to present in the SIGED Track.
==Contact Information==
*'''Alan Rea''' (<rea> at <wmich> dot <edu>)
[[Category:Proposals]]</rev>
</revisions>
</page>
</pages>
</query>
</api>