TeamMeeting 2016 01 Notes

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
(→Pathways Model)
(→Pathways Working Group Meeting)
 
(20 intermediate revisions by 2 users not shown)
Line 9: Line 9:
 
'''Review of what we have'''
 
'''Review of what we have'''
 
* Measurements as defined in the proposals - are we covering the bases?
 
* 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
 
* Existing instruments
 
** Pre/Post Survey - any update needed?
 
** 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?
 
** 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'''
 
'''Direct measurement of learning'''
 
* What study designs are possible?
 
* What study designs are possible?
 
* What instruments do we need?
 
* What instruments do we need?
 +
** Quizzes and tests in class
 
** GH pilot of general FOSS intro questions
 
** GH pilot of general FOSS intro questions
−
* Are there existing instruments that we might use, especially for professional skills?
+
*** 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?
 
* 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'''
 
'''How to measure instructor stage 3 activity'''
Line 25: Line 58:
 
* Multiple good stories told at Hopper (Patti, Becka)
 
* Multiple good stories told at Hopper (Patti, Becka)
 
** Is there a publication in this (experience report style perhaps)?
 
** Is there a publication in this (experience report style perhaps)?
 +
** Opensource.com
 +
** SIGCSE Inroads
 +
 
* Mentions of efforts in POSSE roundup applications
 
* Mentions of efforts in POSSE roundup applications
  
 
== Pathways Working Group Meeting ==
 
== Pathways Working Group Meeting ==
−
* Planning
+
{| border="1" style="width:100%"
−
** Goals
+
|-
−
** Agenda
+
| Thursday evening (4:00?)
−
** What materials need to be prepped?
+
| Dinner, Welcome, Introductions
 +
|-
 +
| Thursday 8:00
 +
| Return to hotel
 +
|-
 +
| Friday session 1
 +
| Model overview, faculty perspective
 +
|-
 +
| Friday session 2
 +
| Community perspective - Community reps provide input into model/approach (structure may be panel, individual discussion, round table, etc.).
 +
|-
 +
| Friday lunch
 +
|
 +
|-
 +
| Friday session 3
 +
| Have reps discuss how they get newbies started on their project.
 +
|-
 +
| Friday session 4
 +
| Pathway details - go down a level in the model, have people work on pathways, review pathways. (Need to review template and provide structure at the beginning) Critique what we've done.
 +
|-
 +
| Friday session 5
 +
| Develop further pathways
 +
|-
 +
| 6:00 PM
 +
| Dinner at Passionne(?)
 +
|-
 +
| Saturday session 1
 +
| HFOSS/University interactions - what works, suggestions, dreams, wishes. Ideal interactions between HFOSS and Universities. What does HFOSS/University nirvana look like? GSoC? Hackathons? Hopper Open Source Day?
 +
|-
 +
| Saturday session 2
 +
|
 +
|-
 +
| 12:00
 +
| Lunch
 +
|-
 +
| Saturday session 3
 +
| Wrap up
 +
|-
 +
|}
 +
 
 +
 
 +
* '''Goals'''
 +
*# Verify the model (Stairway to Heaven, paths, steps, outcomes, skills) - the structure of the approach
 +
*#* Understandable
 +
*#* Usable
 +
*#* Reflective of reality
 +
*# 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
 +
*# Identify resources to support learning
 +
 
 +
* '''Agenda'''
 +
 
 +
* What do we need to be ready?  
 +
** List of paths - Key ones:
 +
**# Report a bug
 +
**# Request a feature
 +
**# Verify a bug
 +
**# Fix a bug
 +
**# Review a patch
 +
**# Contribute code for a new feature
 +
**# Contribute documentation, e.g., fix, add, translate, etc.
 +
**#* Write/update installation instructions
 +
**# Write an article/review/blog to increase project visibility
 +
**# Evaluate the security of a project
 +
**# Build a demo server
 +
**# Helps support the project web site, e.g., adding users, plugins, etc.
 +
**# Create a storyboard or paper prototype for a new feature
 +
**# Create UML diagrams to document design of a feature or project
 +
**# Release packaging
 +
**# 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 ==
 
== Pathways Model ==
Line 50: Line 171:
 
== Planning for upcoming events ==
 
== Planning for upcoming events ==
 
* Weekly team meeting time for this term.  Doodle poll: http://doodle.com/poll/zhyivyx3dmshkexp
 
* 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  
 
* Need to come up with an approach for organizing publications/presentations  
 
** Identify venues for the next year+
 
** Identify venues for the next year+
 
** Identify possible authors
 
** Identify possible authors
 
** The overall goal is to improve our publications and include a larger number of POSSE/HFOSS community members
 
** 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?
 
* What are the next publication targets?
 
** SIGCAS Newsletter section based on POSSE Roundup
 
** SIGCAS Newsletter section based on POSSE Roundup
 
*** We need to write an overview (perhaps with some POSSE alum participation?)
 
*** 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
 
* 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
 
* SIGCSE

Latest revision as of 22:20, 8 January 2016

Contents

Team Meeting Notes

Nassau Community College
January 7-8, 2016

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?

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

Thursday evening (4:00?) Dinner, Welcome, Introductions
Thursday 8:00 Return to hotel
Friday session 1 Model overview, faculty perspective
Friday session 2 Community perspective - Community reps provide input into model/approach (structure may be panel, individual discussion, round table, etc.).
Friday lunch
Friday session 3 Have reps discuss how they get newbies started on their project.
Friday session 4 Pathway details - go down a level in the model, have people work on pathways, review pathways. (Need to review template and provide structure at the beginning) Critique what we've done.
Friday session 5 Develop further pathways
6:00 PM Dinner at Passionne(?)
Saturday session 1 HFOSS/University interactions - what works, suggestions, dreams, wishes. Ideal interactions between HFOSS and Universities. What does HFOSS/University nirvana look like? GSoC? Hackathons? Hopper Open Source Day?
Saturday session 2
12:00 Lunch
Saturday session 3 Wrap up


  • 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:

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
Retrieved from "http://foss2serve.org/index.php?title=TeamMeeting_2016_01_Notes&oldid=5068"
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox