Stage 2 Activities/Stage 3 Planning Ushahidi-20160616

(Difference between revisions)
Jump to: navigation, search
(Relationship of this activity to course goals/objectives)
(Copied from TitanPad: https://titanpad.com/POSSE1606UshahidiStage3Planning)
Line 1: Line 1:
 
== Group Participants ==  
 
== Group Participants ==  
 
Alan, John, Ying, Leo, Jonathan, Janet
 
Alan, John, Ying, Leo, Jonathan, Janet
 +
 +
* Alan used Ushahidi in a mobile dev capstone last year.
 +
* John is teaching a mobile dev course this fall: SE, Android, HCI, HFOSS
 +
* Ying is teaching SE, a course with an existing syllabus, this fall.
 +
* Jonathan might have an independent study student do this in the fall.
 +
* Janet might too, depending on what she decides to do with her spring SE course.
 +
* Leo might use in extra-curricular activities.
  
 
== Planning an Initial HFOSS Learning Activity ==
 
== Planning an Initial HFOSS Learning Activity ==
Line 8: Line 15:
 
=== Course targeted for the activity ===
 
=== Course targeted for the activity ===
  
Any course using Ushahidi
+
Any course using Ushahidi in depth
  
 
=== Brief description of the activity ===
 
=== Brief description of the activity ===
  
Deploy ushahidi
+
Deploy & customize ushahidi
  
 
=== Time you expect the HFOSS activity to take ===
 
=== Time you expect the HFOSS activity to take ===
Line 18: Line 25:
 
Whether the activity will be completed in class or out of class
 
Whether the activity will be completed in class or out of class
  
* One week-ish
+
* Two weeks
 
* Start in class, finish out of class, at least one more class period to address questions/issues before due date
 
* Start in class, finish out of class, at least one more class period to address questions/issues before due date
 +
* Do this twice; Once to deploy and once to customize
  
 
=== Relationship of this activity to course goals/objectives ===
 
=== Relationship of this activity to course goals/objectives ===
  
Read, understand, follow documentation [comm, tech]
+
* Read, understand, follow documentation [comm, tech]
Practice a workflow [tech]
+
* Practice a workflow [tech]
 +
* Understanding the purpose and use of the project [cult]
 +
* Understand relationship between platform and domain [des]
 +
* Learn XML, JSON [tech]
 +
* Prior to a deeper engagement with Ushahidi
  
 
=== What students will submit upon completion of the activity ===
 
=== What students will submit upon completion of the activity ===
  
 
* A URL for a deployment
 
* A URL for a deployment
* Reflection
+
* Answers to POGIL questions (Google docs shows history)
 +
* For a team activity: Individual reflection, summarize own and others' contributions
  
 
=== Approach for assessing the student work ===
 
=== Approach for assessing the student work ===
 +
 +
* URL indicates successful install
 +
* Rubric to assess thoughtfulness of POGIL results
 +
* Evidence that all team members contributed and learned (Google docs history)
  
 
=== Questions or concerns you have about implementing your activity ===
 
=== Questions or concerns you have about implementing your activity ===
 +
 +
* How should students deploy Ushahidi?
 +
* How do we customize a Ushahidi installation? What technical skills are required?
 +
* How do we write good POGIL exercises?
 +
* Is this a team, pair, or individual activity?
 +
* How much time does this really need?
 +
* For customization, do we tell students the domain? The requirements?
 +
* Google Maps or OpenStreetMap?
 +
* How do you use Ushahidi?
  
 
=== Support you will need to implement your activity ===
 
=== Support you will need to implement your activity ===
 +
 +
* Should be able to do this informed by existing public documentation.
 +
* Might need support from Ushahidi team. Might want to talk to them ahead of time.
 +
** Robby might be able to help students from one class, but what if many classes are doing this activity at the same time?
 +
* Students need computers in class.
 +
* Students need a free heroku account.
  
 
== Planning Stage 3 Activities ==
 
== Planning Stage 3 Activities ==
  
 
=== Meetings ===
 
=== Meetings ===
 +
 
<Identify meeting times. Find out HFOSS project meeting times.>
 
<Identify meeting times. Find out HFOSS project meeting times.>
 +
Let's do this by Doodle later.
  
 
===Specific Tasks===
 
===Specific Tasks===
 
<What will various group members do.>  
 
<What will various group members do.>  
 +
  
 
=== Resources ===
 
=== Resources ===
Line 52: Line 87:
 
Prior related POSSE groups, if any:
 
Prior related POSSE groups, if any:
  
 
+
[[Ushahidi]]
 
+
 
+
  
 
[[Category:POSSE]]
 
[[Category:POSSE]]

Revision as of 20:13, 16 June 2016

Contents

Group Participants

Alan, John, Ying, Leo, Jonathan, Janet

  • Alan used Ushahidi in a mobile dev capstone last year.
  • John is teaching a mobile dev course this fall: SE, Android, HCI, HFOSS
  • Ying is teaching SE, a course with an existing syllabus, this fall.
  • Jonathan might have an independent study student do this in the fall.
  • Janet might too, depending on what she decides to do with her spring SE course.
  • Leo might use in extra-curricular activities.

Planning an Initial HFOSS Learning Activity

Please discuss and record your group's approach for an initial learning activity. When you have a good draft description of the learning activity using the sections below, you could create a learning activity page for it by copying the template here: Learning Activity Template

Course targeted for the activity

Any course using Ushahidi in depth

Brief description of the activity

Deploy & customize ushahidi

Time you expect the HFOSS activity to take

e.g. # classes, # homework assignments, # lab activities, etc. Whether the activity will be completed in class or out of class

  • Two weeks
  • Start in class, finish out of class, at least one more class period to address questions/issues before due date
  • Do this twice; Once to deploy and once to customize

Relationship of this activity to course goals/objectives

  • Read, understand, follow documentation [comm, tech]
  • Practice a workflow [tech]
  • Understanding the purpose and use of the project [cult]
  • Understand relationship between platform and domain [des]
  • Learn XML, JSON [tech]
  • Prior to a deeper engagement with Ushahidi

What students will submit upon completion of the activity

  • A URL for a deployment
  • Answers to POGIL questions (Google docs shows history)
  • For a team activity: Individual reflection, summarize own and others' contributions

Approach for assessing the student work

  • URL indicates successful install
  • Rubric to assess thoughtfulness of POGIL results
  • Evidence that all team members contributed and learned (Google docs history)

Questions or concerns you have about implementing your activity

  • How should students deploy Ushahidi?
  • How do we customize a Ushahidi installation? What technical skills are required?
  • How do we write good POGIL exercises?
  • Is this a team, pair, or individual activity?
  • How much time does this really need?
  • For customization, do we tell students the domain? The requirements?
  • Google Maps or OpenStreetMap?
  • How do you use Ushahidi?

Support you will need to implement your activity

  • Should be able to do this informed by existing public documentation.
  • Might need support from Ushahidi team. Might want to talk to them ahead of time.
    • Robby might be able to help students from one class, but what if many classes are doing this activity at the same time?
  • Students need computers in class.
  • Students need a free heroku account.

Planning Stage 3 Activities

Meetings

<Identify meeting times. Find out HFOSS project meeting times.> Let's do this by Doodle later.

Specific Tasks

<What will various group members do.>


Resources

<List any resources that you find>

Other Notes

Prior related POSSE groups, if any:

Ushahidi

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox