TeamMeeting 2016 01 Notes

Latest revision as of 22:20, 8 January 2016

Team Meeting Notes

Original Agenda for this meeting: TeamMeeting_2016_01_Agenda

Topics

Measurement

Review of what we have

• Measurements as defined in the proposals - are we covering the bases?
  • Go back and look at the proposal - what did we say we would measure?
• Existing instruments
  • Pre/Post Survey - any update needed?
    • Other axes: compare non-HFOSS with HFOSS projects; compare "homegrown" projects with non-homegrown projects; longitudinal data - look at change over time?
    • Pre/post survey matching implemented in Fall 2016, Monisha's data (TCNJ) also tracks students
  • Experience Self-report survey (Karl and Stoney) - expand/refine and get IRB approval?
    • https://github.com/kwurst/se-topics-survey
    • Good first cut at learning outcomes for FOSS

Direct measurement of learning

• What study designs are possible?
• What instruments do we need?
  • Quizzes and tests in class
  • GH pilot of general FOSS intro questions
    • Ideal test bank would have multiple questions for each Step. - Likely 100's of questions.
    • Would be good to link questions to steps/activities.
    • "Questions" sprint to create questions to measure learning.

• Are there existing instruments that we might use, especially for process skills?
• How to we measure process skills?
  • POGIL skills & definitions https://pogil.org/about/pogil-process-skill-definitions
  • Contact Juliette Lantz (Drew University) from other POGIL project about lit search for their IUSE grant.
  • What are CS-specific process skills?
    • POGIL Def: Cognitive and affective processes student use to acquire, interpret, and apply knowledge.
      • Communication
      • Teamwork
      • Management
      • Information Processing
      • Critical thinking
      • Oral and Written Communication
      • Problem Solving
      • Assessment - self-assessment and reflection
    • CS add:
      • Design
      • Debugging
      • Code understanding
      • Code tracing
      • Software estimation
      • Effort estimation
      • Testing
      • Requirements elicitation
      • Professionalism
      • Analysis

How to measure instructor stage 3 activity

• One year post survey for POSSE alum
  • Poor response to last round - should we switch to interviews?
• Multiple good stories told at Hopper (Patti, Becka)
  • Is there a publication in this (experience report style perhaps)?
  • Opensource.com
  • SIGCSE Inroads

• Mentions of efforts in POSSE roundup applications

Pathways Working Group Meeting

• Goals
  1. Verify the model (Stairway to Heaven, paths, steps, outcomes, skills) - the structure of the approach
     • Understandable
     • Usable
     • Reflective of reality
  2. Refine list of paths
     • Which are the most useful paths? (i.e., Which ones are the most approachable by students? Which are the most valuable for the community?)
     • Strengths and weaknesses of model
  3. Identify resources to support learning

• Agenda

• What do we need to be ready?
  • List of paths - Key ones:
    1. Report a bug
    2. Request a feature
    3. Verify a bug
    4. Fix a bug
    5. Review a patch
    6. Contribute code for a new feature
    7. Contribute documentation, e.g., fix, add, translate, etc.
       • Write/update installation instructions
    8. Write an article/review/blog to increase project visibility
    9. Evaluate the security of a project
    10. Build a demo server
    11. Helps support the project web site, e.g., adding users, plugins, etc.
    12. Create a storyboard or paper prototype for a new feature
    13. Create UML diagrams to document design of a feature or project
    14. Release packaging
    15. Help organize community meeting (e.g., user group, hackathon)

• • Steps for a subset of paths - to do: pick one and flesh out
    • Verify a bug is done
    • Contribute documentation
    • Build a demo server
    • Evaluate security of a project
    • Create a storyboard or paper prototype for a new feature

• To be done
  • Finalize diagrams of the model
  • Flesh out paths (see subset above)
  • Add "computing for social good" to learning activities
  • Discuss with Gina how our model relates to her information structure (before Skype with larger group) - GH + HE
  • Skype call with group one week out to discuss what we're going to try to do
  • Two weeks out, get group an outline of what we're trying to do (GH)

Pathways Model

Goal - have a reviewable draft by the end of this meeting.

How do we move forward with the pathways model? We need to:

1. Finalize definitions
   1. Are there steps to accomplish a task or tasks to accomplish a step?
   2. Learning resource, Learning activity, categories of learning things (POGIL activity, assignment, case study, etc)
2. Flesh out some example paths

Related to diagrams:

• Happy Path: https://en.wikipedia.org/wiki/Happy_path
• Information cartography, Subway Map: http://cacm.acm.org/magazines/2015/11/193323-information-cartography/fulltext

Planning for upcoming events

• Weekly team meeting time for this term. Doodle poll: http://doodle.com/poll/zhyivyx3dmshkexp
  • Weekly meeting time: 8:00-9:00 a.m. Thursdays
• Need to come up with an approach for organizing publications/presentations
  • Identify venues for the next year+
  • Identify possible authors
  • The overall goal is to improve our publications and include a larger number of POSSE/HFOSS community members
• Data sources
• What are the next publication targets?
  • SIGCAS Newsletter section based on POSSE Roundup
    • We need to write an overview (perhaps with some POSSE alum participation?)
• Need for a better round of evaluation and data collection to support publications
• Paper ideas, immediate:
  • Heidi has end-of-term reflection papers for at least 4 years of SE student involvement in HFOSS projects.

• SIGCSE
  • POSSE Roundup, Wednesday, March 2, all day (Sultana)
  • BoF
  • NSF Showcase, Thursday, March 3, 10:00 am
• CCSCNE
• Posters at NSF/AAAS meeting
• POSSE
• Possible other events
  • Course materials sprint
  • Academic and HFOSS community summit about education for HFOSS
  • Publication sprint
• Working groups
  • Pathways model
  • Curriculum mapping

POSSE

• Planning for 2016
• Stage 1
  • What revisions are needed?
  • 6 vs 8 weeks
  • Participation by POSSE alums of HFOSS project people
• Stage 2
  • Date and location
  • Advertising
  • Team attendees and instructors
  • POSSE alum who might attend and present - including having alums start to be full instructors
  • What revisions are needed?
• Stage 3
  • Assessing success of stage 3
  • How can we better support stage 3 faculty?
  • Plan more organized faculty mentoring?
• Red Hat support / participation in POSSE

Teaching materials

• VM support for demo and development environments for key HFOSS projects
• How well have we packaged what we have?
  • OAI-PMH
• How do we create/collect more materials?
• Should we hold a learning materials sprint?
• How do we encourage more contributions by POSSE grads?
  • Use of stipends funds

Budget

• Review of budget status

Next Steps

• Encouraging use of faculty stipends
• Participant support for follow-up events
  • 50 ways - Part 2