POSSE 2014-11 Feedback

(Difference between revisions)
Jump to: navigation, search
(Created page with "== Participant Observations == * Have participants look at and comment on each other's work * Some folks felt that logging the stage 1 activities was busy work * Some folks f...")
 
(Participant Observations)
Line 11: Line 11:
 
** Ask folks to put them on Opensource.com
 
** Ask folks to put them on Opensource.com
  
 +
Darci's Notes:
 +
* Interesting to see how you can integrate into an existing curriculum and/or to build new curriculum
 +
* Stage 1 exercises worked well regarding preparation for stage 2 – they were not over burdensome, the sequence was incredibly rich
 +
* Thought I was doing busy work in some cases, e.g. how many commits. Why do the copy and paste kind of thing.
 +
* The activity did force me to create a blog for example.
 +
* It might have been helpful to ask us to look at other people’s posts.
 +
* Complete newbie perspective – started worrying that stage 1 was going to be overwhelming. Stage 2 leveled this feeling; now have many pages of notes about things I want to do.
 +
* What time of year works? Software engineering conference is in May. Stage 1 could have started a bit earlier. Reading articles activity – some overlap, too much?, create captcha, having multiple people from the same institution was good, set up pairs during stage 1 (to replicate the benefits of having more than one person from the same institution).
 +
* Red Hat asks those who they fund to provide an immediate write up and a 1 year post evaluation.
 +
* Yes, we will attend and we will do a summary report at a department meeting for example. Or post a summary to an institution’s website. The H stuff is always great promotional materials for the institution.
  
 
== Thoughts for Stage 3 ==
 
== Thoughts for Stage 3 ==
 
* Get folks to communicate things like roadblocks that they encounter after stage 2
 
* Get folks to communicate things like roadblocks that they encounter after stage 2

Revision as of 19:04, 15 November 2014

Participant Observations

  • Have participants look at and comment on each other's work
  • Some folks felt that logging the stage 1 activities was busy work
  • Some folks felt overwhelmed by stage 1, felt better after stage 2
  • End of spring has conflict with ICSE
  • This timing worked, but having more lead time
  • Very helpful to have two folks from the same institution
  • Pair folks from different institutions during stage 1 to provide collaborators, similar to having two folks from same institution
  • Ask for summary of experience of what you got out of POSSE
    • Ask folks to put them on Opensource.com

Darci's Notes:

  • Interesting to see how you can integrate into an existing curriculum and/or to build new curriculum
  • Stage 1 exercises worked well regarding preparation for stage 2 – they were not over burdensome, the sequence was incredibly rich
  • Thought I was doing busy work in some cases, e.g. how many commits. Why do the copy and paste kind of thing.
  • The activity did force me to create a blog for example.
  • It might have been helpful to ask us to look at other people’s posts.
  • Complete newbie perspective – started worrying that stage 1 was going to be overwhelming. Stage 2 leveled this feeling; now have many pages of notes about things I want to do.
  • What time of year works? Software engineering conference is in May. Stage 1 could have started a bit earlier. Reading articles activity – some overlap, too much?, create captcha, having multiple people from the same institution was good, set up pairs during stage 1 (to replicate the benefits of having more than one person from the same institution).
  • Red Hat asks those who they fund to provide an immediate write up and a 1 year post evaluation.
  • Yes, we will attend and we will do a summary report at a department meeting for example. Or post a summary to an institution’s website. The H stuff is always great promotional materials for the institution.

Thoughts for Stage 3

  • Get folks to communicate things like roadblocks that they encounter after stage 2
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox