http://foss2serve.org/api.php?action=feedcontributions&user=Bmorgan&feedformat=atomFoss2Serve - User contributions [en]2024-03-29T00:32:42ZUser contributionsMediaWiki 1.18.1http://foss2serve.org/index.php/Stage_2_ActivitiesStage 2 Activities2019-02-22T21:10:09Z<p>Bmorgan: </p>
<hr />
<div>__NOTOC__<br />
= Local Information =<br />
<br />
Stage 2 will be held at Drexel University, PhilaJdelphia, PA. <br />
<br />
<!--<br />
* '''Meeting location''': The College street address is: 524 West 59th St. New York, NY, 10019, but the best way to enter for POSSE is to use the entrance on 11th Ave. between 58th and 59th streets. <br />
* '''Getting in''': Security will have a list of names for the "POSSE Workshop" and 6.67 as the room. You will need a picture ID to get in.<br />
* '''Meeting room''': Once past security, take the elevator to the 6th floor (Press the button that says 6; ignore the buttons that say L1, L2, etc) We are in room 6.67. The sixth floor has areas for Math and CS, Interdisciplinary studies, and Moot Court. Rooms 6.61 and 6.67 are opposite the glass doors that lead to departments.<br />
* '''Parking''': Parking is available on 11th avenue at the BMW building. There is also parking on 10th avenue at the Mount Sinai garage. 57th street has parking as well. The ParkWhiz App can help find cheap daily rates.<br />
* '''Wednesday Dinner''': We will be having dinner at 5:30 at the Greek Kitchen. Please select your entree from the [[Greek Kitchen Menu]].<br />
--><br />
<br />
= Objectives =<br />
<br />
Participants completing the Stage 2 workshop will be able to:<br />
<br />
* Describe the variety of learning activities that student participation in HFOSS projects may include<br />
* Implement HFOSS activities appropriate for a particular curriculum and student population<br />
* Explain challenges and opportunities of student HFOSS participation<br />
* Discuss key aspects of FOSS culture and process <br />
* Use a selection of tools common in HFOSS projects<br />
* Select an HFOSS project well-suited for student participation<br />
* Identify key sources of information for learning about HFOSS<br />
* Identify other participants with similar ideas about applying HFOSS<br />
* Participate in the TOS community<br />
<br />
== Quick Links == <br />
<!--<br />
*[https://drive.google.com/drive/folders/1NY_P-F9MignULHBMVtTZ03BK8Pnf6qNu Google Drive for Activities]<br />
*[https://pad.riseup.net/p/Intro_A-H Introductions - Last Name A-H]<br />
*[https://pad.riseup.net/p/Intro_I-Z Introductions - Last Name I-Z]<br />
*[https://docs.google.com/document/d/1AX94AXwj-MIOuDGMdQ1ugRmofDlKNJ1FXF8c44OuINI/edit Introductions - if you can't access the Rise-up Pad]<br />
--><br />
<br />
= TENTATIVE Schedule for POSSE 2019-06 in Philadelphia =<br />
<br />
Below is the schedule for the stage 2 workshop activities. <br />
{|border="1"<br />
! Time<br />
! Activity<br />
! Team<br />
|- <br />
|<br />
! Day 1 (Afternoon and Evening)<br />
|<br />
|-<br />
| 1:30 PM<br />
| Leave the hotel for POSSE<br />
| All<br />
|-<br />
| 2:00 <br />
| 1.1 Welcome<br />
* Plan for the day<br />
* Welcome to Philadelphia<br />
* Introducing everyone<br />
* Workshop overview and schedule<br />
| Greg, Darci<br />
|-<br />
| 2:45<br />
| 1.2 HFOSS in Education - (Activity 75 minutes, Slides 15 minutes)<br />
* 50 Ways to be a FOSSer<br />
* Exploration of student contributions <br />
| Chris, Heidi<br />
|-<br />
| 4:15<br />
| Break<br />
| All<br />
|-<br />
| 4:30<br />
| 1.3 HFOSS Process and Tools<br />
* How tools fit and support HFOSS culture<br />
* Upstream Adoption<br />
* Licensing<br />
| Darci, Heidi<br />
|-<br />
<!--<br />
| 5:00<br />
| GitHub Education<br />
| [http://mozzadrella.me/ Vanessa]<br />
|-<br />
--><br />
| 5:15<br />
| Dinner - working / social dinner<br />
| All<br />
|-<br />
| 6:15<br />
| 1.4 Git Intro Activity<br />
* [https://github.com/StoneyJackson/git-intro-activity Hands-on exploration] of managing a local repository <br />
| Darci, Greg<br />
|-<br />
| 8:00<br />
| Return to the hotel<br />
| All<br />
|-<br />
| 8:30<br />
| Social Hour - Optional<br />
| All<br />
|- <br />
|<br />
! Day 2<br />
|<br />
|- <br />
| 7:45<br />
| Leave the hotel for POSSE<br />
| All<br />
|-<br />
| 8:00<br />
| Breakfast<br />
| All<br />
|-<br />
| 8:30<br />
| 2.1 Approach to HFOSS Learning<br />
* POGIL<br />
* Pathways<br />
| Greg, Clif<br />
|-<br />
| 9:15<br />
| 2.2 GitHub Workflow Activity<br />
* [https://github.com/StoneyJackson/github-workflow-activity A common workflow] for HFOSS contribution<br />
| Darci, Greg<br />
|-<br />
| <br />
| Take Break When Convenient<br />
| All<br />
|-<br />
| 11:00<br />
| 2.3 Understanding Open Source Communities<br />
* Perspective on basic characteristics common in HFOSS communities<br />
** FOSSisms that capture FOSS culture and methods<br />
| Chris, Clif<br />
|-<br />
<!--<br />
| 12:15<br />
| Mozilla Open Source Student Network<br />
* [https://opensource.mozilla.community/] <br />
| Christos<br />
|-<br />
--><br />
| 12:30<br />
| Lunch <br />
| All<br />
|-<br />
| 1:30<br />
| 2.4 HFOSS in the Curriculum Activity (60 minutes)<br />
* Discussion (15 minutes)<br />
** Options for getting started in courses<br />
** HFOSS beyond the curriculum <br />
** Trying to find the right size student project<br />
** Evaluating student work<br />
** Instructional style: mentoring vs. lecturing; instructor as co-learner<br />
| Heidi, Clif<br />
|-<br />
| 2:30<br />
| 2.5 Project Evaluation Activity<br />
| Darci, Greg<br />
|-<br />
<!--<br />
| 3:15<br />
| Linux Foundation - Open Source Networking<br />
| Trishan<br />
|-<br />
--><br />
| 3:30<br />
| Break<br />
| All<br />
|-<br />
| 3:45<br />
| 2.6 Planning for HFOSS Participation<br />
* Form groups (based either on courses or HFOSS projects)<br />
* In each group:<br />
** Download and install dev environment for HFOSS project if appropriate<br />
** Identify three things that you would like to get done by the end of POSSE<br />
** Plan a schedule for accomplishing these<br />
| Heidi<br />
|-<br />
| 6:00 <br />
| Dinner - Pietro's, 1714 Walnut St.<br />
| All<br />
|- <br />
|<br />
! Day 3<br />
|<br />
|-<br />
| 7:45<br />
| Leave the hotel (checkout first)<br />
| All<br />
|-<br />
| 8:00<br />
| Breakfast <br />
| All<br />
|-<br />
| 8:30<br />
| 3.1 Understanding POSSE Stage 3<br />
* Experience reports<br />
** [http://www.seas.upenn.edu/~cdmurphy/foss/Murphy-POSSE-June2018.pptx Chris' slides]<br />
| Greg, [[user:cmurphy | Chris]], Darci<br />
|-<br />
| 9:30 <br />
| <br />
3.2 Sharing HFOSS Learning Activities<br />
* Review of Activity Template<br />
* Group work<br />
| Heidi<br />
|-<br />
| 10:30<br />
| Break<br />
| All<br />
|-<br />
| 10:45<br />
| 3.2 Sharing HFOSS Learning Activities - Continued<br />
* [http://foss2serve.org/index.php/Stage_2_Activities/Stage_3_Planning_-_Format Stage 3 Planning Template]<br />
| All<br />
|-<br />
<!--<br />
| 11:45<br />
| Red Hat University Outreach <br />
| Gina<br />
|---><br />
<br />
| 12:00<br />
| Lunch - Lunch Entertainment: [https://drexel.qualtrics.com/jfe/form/SV_72jbRS6I6TsrIyx Evaluation Form] <br />
| All<br />
|-<br />
| 12:45<br />
| 3.2 Sharing HFOSS Learning Activities - Continued<br />
* Groups report back on work done before lunch<br />
* Groups continue to work <br />
| All<br />
|-<br />
| 1:45 <br />
| 3.3 Stage 3 - First Steps<br />
* What will the group do together?<br />
* Plan some initial activities (faculty only or faculty and students)<br />
* Discuss group communication<br />
* Assessment<br />
| Heidi, Clif<br />
|-<br />
| 2:45<br />
| 3.4 Going Forward<br />
* Evaluation form<br />
* Open discussion <br />
* Closing remarks<br />
| Greg<br />
|-<br />
| 3:30<br />
| End - shuttles and taxi to airport<br />
| All<br />
|}<br />
<br />
= Downloads =<br />
<!-- * [https://drive.google.com/open?id=0B92hZzmXFmvQQlZnZG1EdGhSZEk Presentation Materials - Stage 2 - Day 1] --><br />
<!-- <br />
* [https://drive.google.com/drive/folders/0B1g5HGhZ4fOuU3ZIU0pRZkpKOG8 Presentation materials for stage 2]<br />
* [https://github.com/StoneyJackson/CollabDev Stoney's Git and GitHub Activities]<br />
* [https://docs.google.com/presentation/d/1YYi3STtYoMAfSc59bjz46Sqx4tkYgPhCvDKs5W9Lxew/edit?usp=sharing Matt's presentation] on Mozilla's Campus Clubs<br />
--><br />
<br />
<!-- = Shared Files Folder =<br />
<br />
* [https://drive.google.com/drive/folders/0B2rMbpfK2ojueVE3VmlvUUdCOUE?usp=sharing Google Drive folder for team activities] --><br />
<br />
= IRC =<br />
* Server: '''irc.freenode.net'''<br />
* Channel: '''#foss2serve'''<br />
<br />
Standard IRC clients may not work at some workshop locations due to port blockage. If you have problems, please let the team know and try one of the Web-based IRC interfaces below.<br />
<br />
=== Web-based IRC Clients ===<br />
<br />
* http://webchat.freenode.net/ (has a limit from one IP)<br />
* https://kiwiirc.com/client/irc.freenode.net/ <br />
* http://www.mibbit.com/<br />
<br />
== Logs ==<br />
<!-- <br />
* Thursday: <br />
** Minutes: <br />
** Log: <br />
<br />
* Friday: <br />
** Minutes: <br />
** Log: <br />
<br />
* Saturday:<br />
** Minutes:<br />
** Log:<br />
--><br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:POSSE]]</div>Bmorganhttp://foss2serve.org/index.php/Stage_2_ActivitiesStage 2 Activities2019-02-22T21:07:20Z<p>Bmorgan: </p>
<hr />
<div>__NOTOC__<br />
= Local Information =<br />
<br />
Stage 2 will be held at Drexel University, PhilaJdelphia, PA. <br />
<br />
<!--<br />
* '''Meeting location''': The College street address is: 524 West 59th St. New York, NY, 10019, but the best way to enter for POSSE is to use the entrance on 11th Ave. between 58th and 59th streets. <br />
* '''Getting in''': Security will have a list of names for the "POSSE Workshop" and 6.67 as the room. You will need a picture ID to get in.<br />
* '''Meeting room''': Once past security, take the elevator to the 6th floor (Press the button that says 6; ignore the buttons that say L1, L2, etc) We are in room 6.67. The sixth floor has areas for Math and CS, Interdisciplinary studies, and Moot Court. Rooms 6.61 and 6.67 are opposite the glass doors that lead to departments.<br />
* '''Parking''': Parking is available on 11th avenue at the BMW building. There is also parking on 10th avenue at the Mount Sinai garage. 57th street has parking as well. The ParkWhiz App can help find cheap daily rates.<br />
* '''Wednesday Dinner''': We will be having dinner at 5:30 at the Greek Kitchen. Please select your entree from the [[Greek Kitchen Menu]].<br />
--><br />
<br />
= Objectives =<br />
<br />
Participants completing the Stage 2 workshop will be able to:<br />
<br />
* Describe the variety of learning activities that student participation in HFOSS projects may include<br />
* Implement HFOSS activities appropriate for a particular curriculum and student population<br />
* Explain challenges and opportunities of student HFOSS participation<br />
* Discuss key aspects of FOSS culture and process <br />
* Use a selection of tools common in HFOSS projects<br />
* Select an HFOSS project well-suited for student participation<br />
* Identify key sources of information for learning about HFOSS<br />
* Identify other participants with similar ideas about applying HFOSS<br />
* Participate in the TOS community<br />
<br />
== Quick Links == <br />
<!--<br />
*[https://drive.google.com/drive/folders/1NY_P-F9MignULHBMVtTZ03BK8Pnf6qNu Google Drive for Activities]<br />
*[https://pad.riseup.net/p/Intro_A-H Introductions - Last Name A-H]<br />
*[https://pad.riseup.net/p/Intro_I-Z Introductions - Last Name I-Z]<br />
*[https://docs.google.com/document/d/1AX94AXwj-MIOuDGMdQ1ugRmofDlKNJ1FXF8c44OuINI/edit Introductions - if you can't access the Rise-up Pad]<br />
--><br />
<br />
= TENTATIVE Schedule for POSSE 2019-06 in Philadelphia =<br />
<br />
Below is the schedule for the stage 2 workshop activities. <br />
{|border="1"<br />
! Time<br />
! Activity<br />
! Team<br />
|- <br />
|<br />
! Day 1 (Afternoon and Evening)<br />
|<br />
|-<br />
| 1:30 PM<br />
| Leave the hotel for POSSE<br />
| All<br />
|-<br />
| 2:00 <br />
| 1.1 Welcome<br />
* Plan for the day<br />
* Welcome to Philadelphia<br />
* Introducing everyone<br />
* Workshop overview and schedule<br />
| Greg, Darci<br />
|-<br />
| 2:45<br />
| 1.2 HFOSS in Education - (Activity 75 minutes, Slides 15 minutes)<br />
* 50 Ways to be a FOSSer<br />
* Exploration of student contributions <br />
| Chris, Heidi<br />
|-<br />
| 4:15<br />
| Break<br />
| All<br />
|-<br />
| 4:30<br />
| 1.3 HFOSS Process and Tools<br />
* How tools fit and support HFOSS culture<br />
* Upstream Adoption<br />
* Licensing<br />
| Darci, Heidi<br />
|-<br />
<!--<br />
| 5:00<br />
| GitHub Education<br />
| [http://mozzadrella.me/ Vanessa]<br />
|-<br />
--><br />
| 5:15<br />
| Dinner - working / social dinner<br />
| All<br />
|-<br />
| 6:15<br />
| 1.4 Git Intro Activity<br />
* [https://github.com/StoneyJackson/git-intro-activity Hands-on exploration] of managing a local repository <br />
| Becka, Greg<br />
|-<br />
| 8:00<br />
| Return to the hotel<br />
| All<br />
|-<br />
| 8:30<br />
| Social Hour - Optional<br />
| All<br />
|- <br />
|<br />
! Day 2<br />
|<br />
|- <br />
| 7:45<br />
| Leave the hotel for POSSE<br />
| All<br />
|-<br />
| 8:00<br />
| Breakfast<br />
| All<br />
|-<br />
| 8:30<br />
| 2.1 Approach to HFOSS Learning<br />
* POGIL<br />
* Pathways<br />
| Greg, Clif<br />
|-<br />
| 9:15<br />
| 2.2 GitHub Workflow Activity<br />
* [https://github.com/StoneyJackson/github-workflow-activity A common workflow] for HFOSS contribution<br />
| Darci, Greg<br />
|-<br />
| <br />
| Take Break When Convenient<br />
| All<br />
|-<br />
| 11:00<br />
| 2.3 Understanding Open Source Communities<br />
* Perspective on basic characteristics common in HFOSS communities<br />
** FOSSisms that capture FOSS culture and methods<br />
| Chris, Clif<br />
|-<br />
<!--<br />
| 12:15<br />
| Mozilla Open Source Student Network<br />
* [https://opensource.mozilla.community/] <br />
| Christos<br />
|-<br />
--><br />
| 12:30<br />
| Lunch <br />
| All<br />
|-<br />
| 1:30<br />
| 2.4 HFOSS in the Curriculum Activity (60 minutes)<br />
* Discussion (15 minutes)<br />
** Options for getting started in courses<br />
** HFOSS beyond the curriculum <br />
** Trying to find the right size student project<br />
** Evaluating student work<br />
** Instructional style: mentoring vs. lecturing; instructor as co-learner<br />
| Heidi, Clif<br />
|-<br />
| 2:30<br />
| 2.5 Project Evaluation Activity<br />
| Darci, Becka<br />
|-<br />
<!--<br />
| 3:15<br />
| Linux Foundation - Open Source Networking<br />
| Trishan<br />
|-<br />
--><br />
| 3:30<br />
| Break<br />
| All<br />
|-<br />
| 3:45<br />
| 2.6 Planning for HFOSS Participation<br />
* Form groups (based either on courses or HFOSS projects)<br />
* In each group:<br />
** Download and install dev environment for HFOSS project if appropriate<br />
** Identify three things that you would like to get done by the end of POSSE<br />
** Plan a schedule for accomplishing these<br />
| Heidi<br />
|-<br />
| 6:00 <br />
| Dinner - Pietro's, 1714 Walnut St.<br />
| All<br />
|- <br />
|<br />
! Day 3<br />
|<br />
|-<br />
| 7:45<br />
| Leave the hotel (checkout first)<br />
| All<br />
|-<br />
| 8:00<br />
| Breakfast <br />
| All<br />
|-<br />
| 8:30<br />
| 3.1 Understanding POSSE Stage 3<br />
* Experience reports<br />
** [http://www.seas.upenn.edu/~cdmurphy/foss/Murphy-POSSE-June2018.pptx Chris' slides]<br />
| Greg, [[user:cmurphy | Chris]], Darci<br />
|-<br />
| 9:30 <br />
| <br />
3.2 Sharing HFOSS Learning Activities<br />
* Review of Activity Template<br />
* Group work<br />
| Becka<br />
|-<br />
| 10:30<br />
| Break<br />
| All<br />
|-<br />
| 10:45<br />
| 3.2 Sharing HFOSS Learning Activities - Continued<br />
* [http://foss2serve.org/index.php/Stage_2_Activities/Stage_3_Planning_-_Format Stage 3 Planning Template]<br />
| All<br />
|-<br />
<!--<br />
| 11:45<br />
| Red Hat University Outreach <br />
| Gina<br />
|---><br />
<br />
| 12:00<br />
| Lunch - Lunch Entertainment: [https://drexel.qualtrics.com/jfe/form/SV_72jbRS6I6TsrIyx Evaluation Form] <br />
| All<br />
|-<br />
| 12:45<br />
| 3.2 Sharing HFOSS Learning Activities - Continued<br />
* Groups report back on work done before lunch<br />
* Groups continue to work <br />
| All<br />
|-<br />
| 1:45 <br />
| 3.3 Stage 3 - First Steps<br />
* What will the group do together?<br />
* Plan some initial activities (faculty only or faculty and students)<br />
* Discuss group communication<br />
* Assessment<br />
| Heidi, Clif<br />
|-<br />
| 2:45<br />
| 3.4 Going Forward<br />
* Evaluation form<br />
* Open discussion <br />
* Closing remarks<br />
| Greg<br />
|-<br />
| 3:30<br />
| End - shuttles and taxi to airport<br />
| All<br />
|}<br />
<br />
= Downloads =<br />
<!-- * [https://drive.google.com/open?id=0B92hZzmXFmvQQlZnZG1EdGhSZEk Presentation Materials - Stage 2 - Day 1] --><br />
<!-- <br />
* [https://drive.google.com/drive/folders/0B1g5HGhZ4fOuU3ZIU0pRZkpKOG8 Presentation materials for stage 2]<br />
* [https://github.com/StoneyJackson/CollabDev Stoney's Git and GitHub Activities]<br />
* [https://docs.google.com/presentation/d/1YYi3STtYoMAfSc59bjz46Sqx4tkYgPhCvDKs5W9Lxew/edit?usp=sharing Matt's presentation] on Mozilla's Campus Clubs<br />
--><br />
<br />
<!-- = Shared Files Folder =<br />
<br />
* [https://drive.google.com/drive/folders/0B2rMbpfK2ojueVE3VmlvUUdCOUE?usp=sharing Google Drive folder for team activities] --><br />
<br />
= IRC =<br />
* Server: '''irc.freenode.net'''<br />
* Channel: '''#foss2serve'''<br />
<br />
Standard IRC clients may not work at some workshop locations due to port blockage. If you have problems, please let the team know and try one of the Web-based IRC interfaces below.<br />
<br />
=== Web-based IRC Clients ===<br />
<br />
* http://webchat.freenode.net/ (has a limit from one IP)<br />
* https://kiwiirc.com/client/irc.freenode.net/ <br />
* http://www.mibbit.com/<br />
<br />
== Logs ==<br />
<!-- <br />
* Thursday: <br />
** Minutes: <br />
** Log: <br />
<br />
* Friday: <br />
** Minutes: <br />
** Log: <br />
<br />
* Saturday:<br />
** Minutes:<br />
** Log:<br />
--><br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:POSSE]]</div>Bmorganhttp://foss2serve.org/index.php/Stage_2_ActivitiesStage 2 Activities2019-02-22T19:57:43Z<p>Bmorgan: </p>
<hr />
<div>__NOTOC__<br />
= Local Information =<br />
<br />
Stage 2 will be held at Drexel University, PhilaJdelphia, PA. <br />
<br />
<!--<br />
* '''Meeting location''': The College street address is: 524 West 59th St. New York, NY, 10019, but the best way to enter for POSSE is to use the entrance on 11th Ave. between 58th and 59th streets. <br />
* '''Getting in''': Security will have a list of names for the "POSSE Workshop" and 6.67 as the room. You will need a picture ID to get in.<br />
* '''Meeting room''': Once past security, take the elevator to the 6th floor (Press the button that says 6; ignore the buttons that say L1, L2, etc) We are in room 6.67. The sixth floor has areas for Math and CS, Interdisciplinary studies, and Moot Court. Rooms 6.61 and 6.67 are opposite the glass doors that lead to departments.<br />
* '''Parking''': Parking is available on 11th avenue at the BMW building. There is also parking on 10th avenue at the Mount Sinai garage. 57th street has parking as well. The ParkWhiz App can help find cheap daily rates.<br />
* '''Wednesday Dinner''': We will be having dinner at 5:30 at the Greek Kitchen. Please select your entree from the [[Greek Kitchen Menu]].<br />
--><br />
<br />
= Objectives =<br />
<br />
Participants completing the Stage 2 workshop will be able to:<br />
<br />
* Describe the variety of learning activities that student participation in HFOSS projects may include<br />
* Implement HFOSS activities appropriate for a particular curriculum and student population<br />
* Explain challenges and opportunities of student HFOSS participation<br />
* Discuss key aspects of FOSS culture and process <br />
* Use a selection of tools common in HFOSS projects<br />
* Select an HFOSS project well-suited for student participation<br />
* Identify key sources of information for learning about HFOSS<br />
* Identify other participants with similar ideas about applying HFOSS<br />
* Participate in the TOS community<br />
<br />
== Quick Links == <br />
<!--<br />
*[https://drive.google.com/drive/folders/1NY_P-F9MignULHBMVtTZ03BK8Pnf6qNu Google Drive for Activities]<br />
*[https://pad.riseup.net/p/Intro_A-H Introductions - Last Name A-H]<br />
*[https://pad.riseup.net/p/Intro_I-Z Introductions - Last Name I-Z]<br />
*[https://docs.google.com/document/d/1AX94AXwj-MIOuDGMdQ1ugRmofDlKNJ1FXF8c44OuINI/edit Introductions - if you can't access the Rise-up Pad]<br />
--><br />
<br />
= TENTATIVE Schedule for POSSE 2019-06 in Philadelphia =<br />
<br />
Below is the schedule for the stage 2 workshop activities. <br />
{|border="1"<br />
! Time<br />
! Activity<br />
! Team<br />
|- <br />
|<br />
! Day 1 (Afternoon and Evening)<br />
|<br />
|-<br />
| 1:30 PM<br />
| Leave the hotel for POSSE<br />
| All<br />
|-<br />
| 2:00 <br />
| 1.1 Welcome<br />
* Plan for the day<br />
* Welcome to Philadelphia<br />
* Introducing everyone<br />
* Workshop overview and schedule<br />
| Greg, Darci<br />
|-<br />
| 2:45<br />
| 1.2 HFOSS in Education - (Activity 75 minutes, Slides 15 minutes)<br />
* 50 Ways to be a FOSSer<br />
* Exploration of student contributions <br />
| Chris, Heidi<br />
|-<br />
| 4:15<br />
| Break<br />
| All<br />
|-<br />
| 4:30<br />
| 1.3 HFOSS Process and Tools<br />
* How tools fit and support HFOSS culture<br />
* Upstream Adoption<br />
* Licensing<br />
| Darci, Heidi<br />
|-<br />
<!--<br />
| 5:00<br />
| GitHub Education<br />
| [http://mozzadrella.me/ Vanessa]<br />
|-<br />
--><br />
| 5:15<br />
| Dinner - working / social dinner<br />
| All<br />
|-<br />
| 6:15<br />
| 1.4 Git Intro Activity<br />
* [https://github.com/StoneyJackson/git-intro-activity Hands-on exploration] of managing a local repository <br />
| Darci, Greg<br />
|-<br />
| 8:00<br />
| Return to the hotel<br />
| All<br />
|-<br />
| 8:30<br />
| Social Hour - Optional<br />
| All<br />
|- <br />
|<br />
! Day 2<br />
|<br />
|- <br />
| 7:45<br />
| Leave the hotel for POSSE<br />
| All<br />
|-<br />
| 8:00<br />
| Breakfast<br />
| All<br />
|-<br />
| 8:30<br />
| 2.1 Approach to HFOSS Learning<br />
* POGIL<br />
* Pathways<br />
| Greg, Clif<br />
|-<br />
| 9:15<br />
| 2.2 GitHub Workflow Activity<br />
* [https://github.com/StoneyJackson/github-workflow-activity A common workflow] for HFOSS contribution<br />
| Darci, Greg<br />
|-<br />
| <br />
| Take Break When Convenient<br />
| All<br />
|-<br />
| 11:00<br />
| 2.3 Understanding Open Source Communities<br />
* Perspective on basic characteristics common in HFOSS communities<br />
** FOSSisms that capture FOSS culture and methods<br />
| Chris, Clif<br />
|-<br />
<!--<br />
| 12:15<br />
| Mozilla Open Source Student Network<br />
* [https://opensource.mozilla.community/] <br />
| Christos<br />
|-<br />
--><br />
| 12:30<br />
| Lunch <br />
| All<br />
|-<br />
| 1:30<br />
| 2.4 HFOSS in the Curriculum Activity (60 minutes)<br />
* Discussion (15 minutes)<br />
** Options for getting started in courses<br />
** HFOSS beyond the curriculum <br />
** Trying to find the right size student project<br />
** Evaluating student work<br />
** Instructional style: mentoring vs. lecturing; instructor as co-learner<br />
| Heidi, Clif<br />
|-<br />
| 2:30<br />
| 2.5 Project Evaluation Activity<br />
| Darci, Greg<br />
|-<br />
<!--<br />
| 3:15<br />
| Linux Foundation - Open Source Networking<br />
| Trishan<br />
|-<br />
--><br />
| 3:30<br />
| Break<br />
| All<br />
|-<br />
| 3:45<br />
| 2.6 Planning for HFOSS Participation<br />
* Form groups (based either on courses or HFOSS projects)<br />
* In each group:<br />
** Download and install dev environment for HFOSS project if appropriate<br />
** Identify three things that you would like to get done by the end of POSSE<br />
** Plan a schedule for accomplishing these<br />
| Heidi<br />
|-<br />
| 6:00 <br />
| Dinner - Pietro's, 1714 Walnut St.<br />
| All<br />
|- <br />
|<br />
! Day 3<br />
|<br />
|-<br />
| 7:45<br />
| Leave the hotel (checkout first)<br />
| All<br />
|-<br />
| 8:00<br />
| Breakfast <br />
| All<br />
|-<br />
| 8:30<br />
| 3.1 Understanding POSSE Stage 3<br />
* Experience reports<br />
** [http://www.seas.upenn.edu/~cdmurphy/foss/Murphy-POSSE-June2018.pptx Chris' slides]<br />
| Greg, [[user:cmurphy | Chris]], Darci<br />
|-<br />
| 9:30 <br />
| <br />
3.2 Sharing HFOSS Learning Activities<br />
* Review of Activity Template<br />
* Group work<br />
| Heidi<br />
|-<br />
| 10:30<br />
| Break<br />
| All<br />
|-<br />
| 10:45<br />
| 3.2 Sharing HFOSS Learning Activities - Continued<br />
* [http://foss2serve.org/index.php/Stage_2_Activities/Stage_3_Planning_-_Format Stage 3 Planning Template]<br />
| All<br />
|-<br />
<!--<br />
| 11:45<br />
| Red Hat University Outreach <br />
| Gina<br />
|---><br />
<br />
| 12:00<br />
| Lunch - Lunch Entertainment: [https://drexel.qualtrics.com/jfe/form/SV_72jbRS6I6TsrIyx Evaluation Form] <br />
| All<br />
|-<br />
| 12:45<br />
| 3.2 Sharing HFOSS Learning Activities - Continued<br />
* Groups report back on work done before lunch<br />
* Groups continue to work <br />
| All<br />
|-<br />
| 1:45 <br />
| 3.3 Stage 3 - First Steps<br />
* What will the group do together?<br />
* Plan some initial activities (faculty only or faculty and students)<br />
* Discuss group communication<br />
* Assessment<br />
| Heidi, Clif<br />
|-<br />
| 2:45<br />
| 3.4 Going Forward<br />
* Evaluation form<br />
* Open discussion <br />
* Closing remarks<br />
| Greg<br />
|-<br />
| 3:30<br />
| End - shuttles and taxi to airport<br />
| All<br />
|}<br />
<br />
= Downloads =<br />
<!-- * [https://drive.google.com/open?id=0B92hZzmXFmvQQlZnZG1EdGhSZEk Presentation Materials - Stage 2 - Day 1] --><br />
<!-- <br />
* [https://drive.google.com/drive/folders/0B1g5HGhZ4fOuU3ZIU0pRZkpKOG8 Presentation materials for stage 2]<br />
* [https://github.com/StoneyJackson/CollabDev Stoney's Git and GitHub Activities]<br />
* [https://docs.google.com/presentation/d/1YYi3STtYoMAfSc59bjz46Sqx4tkYgPhCvDKs5W9Lxew/edit?usp=sharing Matt's presentation] on Mozilla's Campus Clubs<br />
--><br />
<br />
<!-- = Shared Files Folder =<br />
<br />
* [https://drive.google.com/drive/folders/0B2rMbpfK2ojueVE3VmlvUUdCOUE?usp=sharing Google Drive folder for team activities] --><br />
<br />
= IRC =<br />
* Server: '''irc.freenode.net'''<br />
* Channel: '''#foss2serve'''<br />
<br />
Standard IRC clients may not work at some workshop locations due to port blockage. If you have problems, please let the team know and try one of the Web-based IRC interfaces below.<br />
<br />
=== Web-based IRC Clients ===<br />
<br />
* http://webchat.freenode.net/ (has a limit from one IP)<br />
* https://kiwiirc.com/client/irc.freenode.net/ <br />
* http://www.mibbit.com/<br />
<br />
== Logs ==<br />
<!-- <br />
* Thursday: <br />
** Minutes: <br />
** Log: <br />
<br />
* Friday: <br />
** Minutes: <br />
** Log: <br />
<br />
* Saturday:<br />
** Minutes:<br />
** Log:<br />
--><br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:POSSE]]</div>Bmorganhttp://foss2serve.org/index.php/Stage_2_ActivitiesStage 2 Activities2019-02-22T19:54:39Z<p>Bmorgan: </p>
<hr />
<div>__NOTOC__<br />
= Local Information =<br />
<br />
Stage 2 will be held at Drexel University, PhilaJdelphia, PA. <br />
<br />
<!--<br />
* '''Meeting location''': The College street address is: 524 West 59th St. New York, NY, 10019, but the best way to enter for POSSE is to use the entrance on 11th Ave. between 58th and 59th streets. <br />
* '''Getting in''': Security will have a list of names for the "POSSE Workshop" and 6.67 as the room. You will need a picture ID to get in.<br />
* '''Meeting room''': Once past security, take the elevator to the 6th floor (Press the button that says 6; ignore the buttons that say L1, L2, etc) We are in room 6.67. The sixth floor has areas for Math and CS, Interdisciplinary studies, and Moot Court. Rooms 6.61 and 6.67 are opposite the glass doors that lead to departments.<br />
* '''Parking''': Parking is available on 11th avenue at the BMW building. There is also parking on 10th avenue at the Mount Sinai garage. 57th street has parking as well. The ParkWhiz App can help find cheap daily rates.<br />
* '''Wednesday Dinner''': We will be having dinner at 5:30 at the Greek Kitchen. Please select your entree from the [[Greek Kitchen Menu]].<br />
--><br />
<br />
= Objectives =<br />
<br />
Participants completing the Stage 2 workshop will be able to:<br />
<br />
* Describe the variety of learning activities that student participation in HFOSS projects may include<br />
* Implement HFOSS activities appropriate for a particular curriculum and student population<br />
* Explain challenges and opportunities of student HFOSS participation<br />
* Discuss key aspects of FOSS culture and process <br />
* Use a selection of tools common in HFOSS projects<br />
* Select an HFOSS project well-suited for student participation<br />
* Identify key sources of information for learning about HFOSS<br />
* Identify other participants with similar ideas about applying HFOSS<br />
* Participate in the TOS community<br />
<br />
== Quick Links == <br />
<!--<br />
*[https://drive.google.com/drive/folders/1NY_P-F9MignULHBMVtTZ03BK8Pnf6qNu Google Drive for Activities]<br />
*[https://pad.riseup.net/p/Intro_A-H Introductions - Last Name A-H]<br />
*[https://pad.riseup.net/p/Intro_I-Z Introductions - Last Name I-Z]<br />
*[https://docs.google.com/document/d/1AX94AXwj-MIOuDGMdQ1ugRmofDlKNJ1FXF8c44OuINI/edit Introductions - if you can't access the Rise-up Pad]<br />
--><br />
<br />
= TENTATIVE Schedule for POSSE 2019-06 in Philadelphia =<br />
<br />
Below is the schedule for the stage 2 workshop activities. <br />
{|border="1"<br />
! Time<br />
! Activity<br />
! Team<br />
|- <br />
|<br />
! Day 1 (Afternoon and Evening)<br />
|<br />
|-<br />
| 1:30 PM<br />
| Leave the hotel for POSSE<br />
| All<br />
|-<br />
| 2:00 <br />
| 1.1 Welcome<br />
* Plan for the day<br />
* Welcome to Philadelphia<br />
* Introducing everyone<br />
* Workshop overview and schedule<br />
| Greg, Darci<br />
|-<br />
| 2:45<br />
| 1.2 HFOSS in Education - (Activity 75 minutes, Slides 15 minutes)<br />
* 50 Ways to be a FOSSer<br />
* Exploration of student contributions <br />
| Chris, Heidi<br />
|-<br />
| 4:15<br />
| Break<br />
| All<br />
|-<br />
| 4:30<br />
| 1.3 HFOSS Process and Tools<br />
* How tools fit and support HFOSS culture<br />
* Upstream Adoption<br />
* Licensing<br />
| Darci, Heidi<br />
|-<br />
<!--<br />
| 5:00<br />
| GitHub Education<br />
| [http://mozzadrella.me/ Vanessa]<br />
|-<br />
--><br />
| 5:15<br />
| Dinner - working / social dinner<br />
| All<br />
|-<br />
| 6:15<br />
| 1.4 Git Intro Activity<br />
* [https://github.com/StoneyJackson/git-intro-activity Hands-on exploration] of managing a local repository <br />
| Becka, Greg<br />
|-<br />
| 8:00<br />
| Return to the hotel<br />
| All<br />
|-<br />
| 8:30<br />
| Social Hour - Optional<br />
| All<br />
|- <br />
|<br />
! Day 2<br />
|<br />
|- <br />
| 7:45<br />
| Leave the hotel for POSSE<br />
| All<br />
|-<br />
| 8:00<br />
| Breakfast<br />
| All<br />
|-<br />
| 8:30<br />
| 2.1 Approach to HFOSS Learning<br />
* POGIL<br />
* Pathways<br />
| Greg, Clif<br />
|-<br />
| 9:15<br />
| 2.2 GitHub Workflow Activity<br />
* [https://github.com/StoneyJackson/github-workflow-activity A common workflow] for HFOSS contribution<br />
| Darci, Greg<br />
|-<br />
| <br />
| Take Break When Convenient<br />
| All<br />
|-<br />
| 11:00<br />
| 2.3 Understanding Open Source Communities<br />
* Perspective on basic characteristics common in HFOSS communities<br />
** FOSSisms that capture FOSS culture and methods<br />
| Chris, Clif<br />
|-<br />
<!--<br />
| 12:15<br />
| Mozilla Open Source Student Network<br />
* [https://opensource.mozilla.community/] <br />
| Christos<br />
|-<br />
--><br />
| 12:30<br />
| Lunch <br />
| All<br />
|-<br />
| 1:30<br />
| 2.4 HFOSS in the Curriculum Activity (60 minutes)<br />
* Discussion (15 minutes)<br />
** Options for getting started in courses<br />
** HFOSS beyond the curriculum <br />
** Trying to find the right size student project<br />
** Evaluating student work<br />
** Instructional style: mentoring vs. lecturing; instructor as co-learner<br />
| Heidi, Clif<br />
|-<br />
| 2:30<br />
| 2.5 Project Evaluation Activity<br />
| Darci, Becka<br />
|-<br />
<!--<br />
| 3:15<br />
| Linux Foundation - Open Source Networking<br />
| Trishan<br />
|-<br />
--><br />
| 3:30<br />
| Break<br />
| All<br />
|-<br />
| 3:45<br />
| 2.6 Planning for HFOSS Participation<br />
* Form groups (based either on courses or HFOSS projects)<br />
* In each group:<br />
** Download and install dev environment for HFOSS project if appropriate<br />
** Identify three things that you would like to get done by the end of POSSE<br />
** Plan a schedule for accomplishing these<br />
| Heidi<br />
|-<br />
| 6:00 <br />
| Dinner - Pietro's, 1714 Walnut St.<br />
| All<br />
|- <br />
|<br />
! Day 3<br />
|<br />
|-<br />
| 7:45<br />
| Leave the hotel (checkout first)<br />
| All<br />
|-<br />
| 8:00<br />
| Breakfast <br />
| All<br />
|-<br />
| 8:30<br />
| 3.1 Understanding POSSE Stage 3<br />
* Experience reports<br />
** [http://www.seas.upenn.edu/~cdmurphy/foss/Murphy-POSSE-June2018.pptx Chris' slides]<br />
| Greg, [[user:cmurphy | Chris]], Darci<br />
|-<br />
| 9:30 <br />
| <br />
3.2 Sharing HFOSS Learning Activities<br />
* Review of Activity Template<br />
* Group work<br />
| Becka<br />
|-<br />
| 10:30<br />
| Break<br />
| All<br />
|-<br />
| 10:45<br />
| 3.2 Sharing HFOSS Learning Activities - Continued<br />
* [http://foss2serve.org/index.php/Stage_2_Activities/Stage_3_Planning_-_Format Stage 3 Planning Template]<br />
| All<br />
|-<br />
<!--<br />
| 11:45<br />
| Red Hat University Outreach <br />
| Gina<br />
|---><br />
<br />
| 12:00<br />
| Lunch - Lunch Entertainment: [https://drexel.qualtrics.com/jfe/form/SV_72jbRS6I6TsrIyx Evaluation Form] <br />
| All<br />
|-<br />
| 12:45<br />
| 3.2 Sharing HFOSS Learning Activities - Continued<br />
* Groups report back on work done before lunch<br />
* Groups continue to work <br />
| All<br />
|-<br />
| 1:45 <br />
| 3.3 Stage 3 - First Steps<br />
* What will the group do together?<br />
* Plan some initial activities (faculty only or faculty and students)<br />
* Discuss group communication<br />
* Assessment<br />
| Heidi, Clif<br />
|-<br />
| 2:45<br />
| 3.4 Going Forward<br />
* Evaluation form<br />
* Open discussion <br />
* Closing remarks<br />
| Greg<br />
|-<br />
| 3:30<br />
| End - shuttles and taxi to airport<br />
| All<br />
|}<br />
<br />
= Downloads =<br />
<!-- * [https://drive.google.com/open?id=0B92hZzmXFmvQQlZnZG1EdGhSZEk Presentation Materials - Stage 2 - Day 1] --><br />
<!-- <br />
* [https://drive.google.com/drive/folders/0B1g5HGhZ4fOuU3ZIU0pRZkpKOG8 Presentation materials for stage 2]<br />
* [https://github.com/StoneyJackson/CollabDev Stoney's Git and GitHub Activities]<br />
* [https://docs.google.com/presentation/d/1YYi3STtYoMAfSc59bjz46Sqx4tkYgPhCvDKs5W9Lxew/edit?usp=sharing Matt's presentation] on Mozilla's Campus Clubs<br />
--><br />
<br />
<!-- = Shared Files Folder =<br />
<br />
* [https://drive.google.com/drive/folders/0B2rMbpfK2ojueVE3VmlvUUdCOUE?usp=sharing Google Drive folder for team activities] --><br />
<br />
= IRC =<br />
* Server: '''irc.freenode.net'''<br />
* Channel: '''#foss2serve'''<br />
<br />
Standard IRC clients may not work at some workshop locations due to port blockage. If you have problems, please let the team know and try one of the Web-based IRC interfaces below.<br />
<br />
=== Web-based IRC Clients ===<br />
<br />
* http://webchat.freenode.net/ (has a limit from one IP)<br />
* https://kiwiirc.com/client/irc.freenode.net/ <br />
* http://www.mibbit.com/<br />
<br />
== Logs ==<br />
<!-- <br />
* Thursday: <br />
** Minutes: <br />
** Log: <br />
<br />
* Friday: <br />
** Minutes: <br />
** Log: <br />
<br />
* Saturday:<br />
** Minutes:<br />
** Log:<br />
--><br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:POSSE]]</div>Bmorganhttp://foss2serve.org/index.php/ConferencesConferences2018-06-20T20:38:24Z<p>Bmorgan: </p>
<hr />
<div>=Conferences=<br />
<br />
The following is a list of conferences that are good places to submit papers, etc. on HFOSS work. The name of the conference and the approx month it is held in are in the heading. The approx month for submission and a link to either the conference or the call for papers page is below each heading.<br />
<br />
===RESPECT W/SIGCSE February=== <br />
Submit papers September<br><br />
[http://respect2018.stcbp.org/call-for-papers/ Conference Website]<br />
<br />
===Frontiers in Education October===<br />
Submit papers February<br><br />
[http://fie2018.org/pages/call-papers Conference Website]<br />
<br />
===SIGITE - October===<br />
Submit papers April<br><br />
[https://sigite2018.sigite.org/authors/call-for-participation/ Conference Website]<br />
<br />
===HICCS January=== <br />
Paper submission begins April<br><br />
[http://hicss.hawaii.edu/ Conference Website]<br />
<br />
===SIGCSE February===<br />
August: Paper Abstracts<br><br />
August end: Full Papers, Panels, Special Sessions, & Workshops<br><br />
October: ACM SRC, BoFs, Demos, Lightning Talks, Posters, Nifty Assignments, & Presymposium Events<br><br />
[https://sigcse2019.sigcse.org/info/cfp.html#papers Conference Website]<br />
<br />
===International Conference on Open Source Systems June===<br />
Full & Short papers: January<br><br />
Workshop, Tutorial Proposals: January<br><br />
Posters & Short Industry Papers: February<br><br />
[https://www.oss2018.org/important-dates/ Conference Website]<br />
<br />
===FIE Frontiers in Education October===<br />
Submit papers May<br><br />
[http://fie2018.org/ Conference Website]<br />
<br />
===Tapia September===<br />
Submit papers March<br><br />
[http://tapiaconference.org/ Conference Website]<br />
<br />
===Grace Hopper Celebration of Women in Technology September=== <br />
[https://ghc.anitab.org/calendar/2018-grace-hopper-celebration/ Conference Website]<br />
<br />
===Annual CCSC Northwestern Regional Conference October===<br />
Submit papers, panels, and tutorials June<br><br />
[http://www.ccsc.org/northwest/2018/index.html Conference Website]</div>Bmorganhttp://foss2serve.org/index.php/ConferencesConferences2018-06-20T20:30:31Z<p>Bmorgan: </p>
<hr />
<div>===RESPECT W/SIGCSE February (ish)=== <br />
Submit papers September (ish)<br><br />
[http://respect2018.stcbp.org/call-for-papers/ Conference Website]<br />
<br />
===Frontiers in Education - October (ish)===<br />
Submit papers February (ish)<br><br />
[http://fie2018.org/pages/call-papers Conference Website]<br />
<br />
===SIGITE - October (ish)===<br />
Submit papers April (ish)<br><br />
[https://sigite2018.sigite.org/authors/call-for-participation/ Conference Website]<br />
<br />
===HICCS 2018 January (ish)=== <br />
Paper submission begins April (ish)<br><br />
[http://hicss.hawaii.edu/ Conference Website]<br />
<br />
===SIGCSE February (ish)===<br />
August (ish): Paper Abstracts<br><br />
August end (ish): Full Papers, Panels, Special Sessions, & Workshops<br><br />
October (ish): ACM SRC, BoFs, Demos, Lightning Talks, Posters, Nifty Assignments, & Presymposium Events<br><br />
[https://sigcse2019.sigcse.org/info/cfp.html#papers Conference Website]<br />
<br />
===International Conference on Open Source Systems June (ish)===<br />
Full & Short papers: January (ish)<br><br />
Workshop, Tutorial Proposals: January (ish)<br><br />
Posters & Short Industry Papers: February (ish)<br><br />
[https://www.oss2018.org/important-dates/ Conference Website]<br />
<br />
===FIE Frontiers in Education October (ish)===<br />
Submit papers May (ish)<br><br />
[http://fie2018.org/ Conference Website]<br />
<br />
===Tapia September (ish)===<br />
Submit papers March (ish)<br><br />
[http://tapiaconference.org/ Conference Website]<br />
<br />
===Grace Hopper Celebration of Women in Technology September (ish)=== <br />
[https://ghc.anitab.org/calendar/2018-grace-hopper-celebration/ Conference Website]<br />
<br />
===Annual CCSC Northwestern Regional Conference October (ish)===<br />
Submit papers, panels, and tutorials June (ish)<br><br />
[http://www.ccsc.org/northwest/2018/index.html Conference Website]</div>Bmorganhttp://foss2serve.org/index.php/ConferencesConferences2018-06-20T20:29:26Z<p>Bmorgan: </p>
<hr />
<div>===RESPECT W/SIGCSE February (ish)=== <br />
Submit papers September (ish)<br><br />
[http://respect2018.stcbp.org/call-for-papers/ Conference Website]<br />
<br />
===Frontiers in Education - October (ish)===<br />
Submit papers February (ish)<br><br />
[http://fie2018.org/pages/call-papers Conference Website]<br />
<br />
===SIGITE - October (ish)===<br />
Submit papers April (ish)<br><br />
[https://sigite2018.sigite.org/authors/call-for-participation/ Conference Website]<br />
<br />
===HICCS 2018 January (ish)=== <br />
Paper submission begins April (ish)<br><br />
[http://hicss.hawaii.edu/ Conference Website]<br />
<br />
===SIGCSE February (ish)===<br />
August (ish): Paper Abstracts<br><br />
August end (ish): Full Papers, Panels, Special Sessions, & Workshops<br><br />
October (ish): ACM SRC, BoFs, Demos, Lightning Talks, Posters, Nifty Assignments, & Presymposium Events<br><br />
[https://sigcse2019.sigcse.org/info/cfp.html#papers Conference Website]<br />
<br />
===International Conference on Open Source Systems June (ish)===<br />
Full & Short papers: January (ish)<br><br />
Workshop, Tutorial Proposals: January (ish)<br><br />
Posters & Short Industry Papers: February (ish)<br><br />
[https://www.oss2018.org/important-dates/ Conference Website]<br />
<br />
===FIE Frontiers in Education October (ish)===<br />
Submit papers May (ish)<br><br />
[http://fie2018.org/ Conference Website]<br />
<br />
===Tapia 2018 - September (ish)===<br />
Submit papers March (ish)<br><br />
[http://tapiaconference.org/ Conference Website]<br />
<br />
===Grace Hopper Celebration of Women in Technology September (ish)=== <br />
[https://ghc.anitab.org/calendar/2018-grace-hopper-celebration/ Conference Website]<br />
<br />
===2018 Annual CCSC (Consortium for Computing Sciences in Colleges) Northwestern Regional Conference October 12‐13, 2018===<br />
Submit papers, panels, and tutorials June (ish)<br><br />
[http://www.ccsc.org/northwest/2018/index.html Conference Website]</div>Bmorganhttp://foss2serve.org/index.php/ConferencesConferences2018-06-20T20:28:47Z<p>Bmorgan: Created page with "===RESPECT W/SIGCSE February (ish)=== Submit papers September (ish)<br> [http://respect2018.stcbp.org/call-for-papers/ Conference Website] ===Frontiers in Education - Octobe..."</p>
<hr />
<div>===RESPECT W/SIGCSE February (ish)=== <br />
Submit papers September (ish)<br><br />
[http://respect2018.stcbp.org/call-for-papers/ Conference Website]<br />
<br />
===Frontiers in Education - October (ish)===<br />
Submit papers February (ish)<br><br />
[http://fie2018.org/pages/call-papers Conference Website]<br />
<br />
===SIGITE - October (ish)===<br />
Submit papers April (ish)<br><br />
[https://sigite2018.sigite.org/authors/call-for-participation/ Conference Website]<br />
<br />
===HICCS 2018 January (ish)=== <br />
Paper submission begins April (ish)<br><br />
[http://hicss.hawaii.edu/ Conference Website]<br />
<br />
===SIGCSE February (ish)===<br />
August (ish): Paper Abstracts<br><br />
August end (ish): Full Papers, Panels, Special Sessions, & Workshops<br><br />
October (ish): ACM SRC, BoFs, Demos, Lightning Talks, Posters, Nifty Assignments, & Presymposium Events<br><br />
[https://sigcse2019.sigcse.org/info/cfp.html#papers Conference Website]<br />
<br />
<br />
===International Conference on Open Source Systems June (ish)===<br />
Full & Short papers: January (ish)<br><br />
Workshop, Tutorial Proposals: January (ish)<br><br />
Posters & Short Industry Papers: February (ish)<br><br />
[https://www.oss2018.org/important-dates/ Conference Website]<br />
<br />
<br />
===FIE Frontiers in Education October (ish)===<br />
Submit papers May (ish)<br><br />
[http://fie2018.org/ Conference Website]<br />
<br />
===Tapia 2018 - September (ish)===<br />
Submit papers March (ish)<br><br />
[http://tapiaconference.org/ Conference Website]<br />
<br />
===Grace Hopper Celebration of Women in Technology September (ish)=== <br />
[https://ghc.anitab.org/calendar/2018-grace-hopper-celebration/ Conference Website]<br />
<br />
===2018 Annual CCSC (Consortium for Computing Sciences in Colleges) Northwestern Regional Conference October 12‐13, 2018===<br />
Submit papers, panels, and tutorials June (ish)<br><br />
[http://www.ccsc.org/northwest/2018/index.html Conference Website]</div>Bmorganhttp://foss2serve.org/index.php/Stage_2_Activities/Stage_3_Planning_SoftwareEngineeringStage 2 Activities/Stage 3 Planning SoftwareEngineering2018-06-20T15:01:52Z<p>Bmorgan: </p>
<hr />
<div>== Group Participants ==<br />
Marco Gerosa<br />
<br />
Becka Morgan <morganb@wou.edu><br />
<br />
Lin Deng<br />
<br />
== Planning an Initial HFOSS Learning Activity ==<br />
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 [[Learning Activity Format with Directions]].<br />
<br />
=== Course targeted for the activity ===<br />
<br />
=== Brief description of the activity ===<br />
<br />
=== Time you expect the HFOSS activity to take ===<br />
e.g. # classes, # homework assignments, # lab activities, etc.<br />
<br />
Whether the activity will be completed in class or out of class<br />
<br />
=== Relationship of this activity to course goals/objectives ===<br />
<br />
=== What students will submit upon completion of the activity ===<br />
<br />
=== Approach for assessing the student work ===<br />
<br />
=== Questions or concerns you have about implementing your activity ===<br />
<br />
=== Support you will need to implement your activity ===<br />
<br />
== Planning Stage 3 Activities ==<br />
<br />
=== Meetings ===<br />
<Identify meeting times. Find out HFOSS project meeting times.><br />
<br />
===Specific Tasks===<br />
<What will various group members do.> <br />
<br />
=== Resources ===<br />
<List any resources that you find><br />
<br />
== Other Notes ==<br />
<br />
Prior related POSSE groups, if any:<br />
<br />
<br />
<br />
<br />
<br />
[[Category:POSSE]]<br />
<br />
When creating an activity, remove it from the Formats category.<br />
[[Category:Formats]]</div>Bmorganhttp://foss2serve.org/index.php/Connect_with_the_Community_(Activity)Connect with the Community (Activity)2018-04-29T18:32:11Z<p>Bmorgan: /* PART 1: IRC */</p>
<hr />
<div>__NOTOC__<br />
<br />
{{Learning Activity Overview<br />
|title=<br />
Connect with the Community<br />
|overview= <br />
Learners should get familiar with communication tools (such as IRC, TitanPad, Skype, etc.) that are commonly used by FOSS communities.<br />
|prerequisites=<br />
|objectives=<br />
* Be familiar with different communication tools (such as iRC, TitanPad, Skype etc.) that are freely available for everyone. <br />
* Explore interactions and find out how different FOSS communities (HFOSS in particular) use these tools to communicate among their members.<br />
|process skills=<br />
}}<br />
<br />
=== Background ===<br />
<br />
If your class is embedded with an open source project, you should:<br />
# Join the comms channels for your project, <br />
# Discussed codes of conduct with your community liaison,<br />
# Discuss how to handle CoC violations when your students are involved.<br />
<br />
<br />
For general info on how open source projects use IRC, mailing lists and the like, there's a nice [[https://www.youtube.com/watch?v=0Z_KwdPvFy0 video]] on "how to communicate with your community" that Brian Proffitt at Red Hat has created that may be worth watching.<br />
<br />
=== Directions ===<br />
<br />
== PART 1: IRC ==<br />
<br />
'''This is the longest and most important part of this activity.'''<br />
<br />
IRC, which stands for Internet Relay Chat, is an essential tool used by open source software developers. It allows members of the community, or those interested in becoming involved in the community, to communicate 24/7, regardless of their geographic location. IRC is much like Instant Messaging with a group. Bear in mind that ‘talking’ is not always a requirement. You will learn a great deal by ‘listening’, especially in the beginning. <br />
<br />
* Choose a client from below<br />
** Web-based client: http://webchat.freenode.net <br />
** Web-based client: https://kiwiirc.com/client/irc.freenode.net <br />
** Windows: HydraIRC (http://www.hydrairc.com)<br />
** Linux: Konversation (http://konversation.kde.org)<br />
** Linux: xchat iRC (http://xchat.org/)<br />
** Mac OS X: Colloquy (http://colloquy.info)<br />
<br />
* Everybody should then<br />
** Connect to the server via the command: /server irc.freenode.net<br />
** Join our own (newly created) channel via the command: /join #chooseYourOwnChannel<br />
<br />
* Now let’s chat<br />
** each student should write at least one line, and use at least one command!<br />
** A list of useful iRC commands can be found here. http://www.ircbeginner.com/ircinfo/ircc-commands.html<br />
** Commands on using the Meetbot can be found here. https://wiki.debian.org/MeetBot<br />
<br />
* '''HOMEWORK 1''': join and observe an existing channel discussion<br />
** Connect to the '''freenode''' server via the command: '''/server irc.freenode.net'''<br />
** Join the '''foss2serve''' channel via the command: '''/join #sourceforge'''<br />
** Monitor, then write and return a 1-page paper on the discussion you discover in here for at least a couple of hours:<br />
*** Pay attention to the interactions that occur between community members. <br />
*** Ignore the technical terms you don't understand. <br />
*** Accept that the content may be beyond your understanding at this point<br />
*** Observe:<br />
**** How do people interact in this context? <br />
**** What is the pattern of communication you just observed? <br />
**** Can you make any other observations?<br />
<br />
== PART 2: Titanpad ==<br />
<br />
Titanpad allows authors to simultaneously edit a text document, and see all of the participants' edits in real-time, with the ability to display each author's text in their own color. There is also a chat box in the sidebar to allow meta communication.<br />
<br />
In this part of the activity you will need to:<br />
* use a web browser to connect to: https://titanpad.com/ChooseYourPage<br />
* let’s chat:<br />
** do you have any comments you would like to share here about what you just observed in the iRC channel? <br />
** every student should write at least one line!<br />
<br />
<br />
== PART 3: Alternatives ==<br />
<br />
Propose some alternatives ways team can collaborate such as: mailing lists, blogs, twitter, facebook, google+, skype, wiki, iRC, community sites, blogs, twitter, youtube, slideshare, vimeo, etc. which ones do you think are most effective and why?<br />
'''In-class discussion'''. <br />
* Split the class in teams of 2-3 students each. Each team should visit one the following websites and identify as many ways of communications as possible for this community:<br />
** https://wiki.gnome.org/Accessibility<br />
** http://mifos.org/ <br />
** http://openmrs.org/<br />
** http://sahanafoundation.org/<br />
** http://www.ushahidi.com/<br />
* Discuss, in class, your findings.<br />
* '''HOMEWORK 2''': Write a 1-page paper with these findings.<br />
<br />
<br />
== PART 4: Discussions ==<br />
<br />
* Describe the difference between synchronous and asynchronous communication.<br />
* Compare the HCI issues in individual interaction with group interaction.<br />
* Discuss several issues of social concern raised by collaborative software.<br />
* Discuss the HCI issues in software that embodies human intention.<br />
<br />
<br />
== OTHER REFERENCES ==<br />
<br />
* http://foss2serve.org/index.php/Intro_IRC_Activity <br />
* http://foss2serve.org/index.php/IRC_Meeting_1 <br />
* http://foss2serve.org/index.php/HFOSS_Communities<br />
<br />
<br />
== SOME IRC CHANNELS ==<br />
<br />
* '''#openstack''' <br />
* '''#openstack-101'''<br />
* '''#openstack-doc'''<br />
* '''#wikipedia'''<br />
* '''##java''' <br />
** only registered nicks are allowed!!! You must create a registered nick on iRC. <br />
* '''##C++'''<br />
* '''##c++-basic'''<br />
* '''#sagemath'''<br />
* '''#ubuntu'''<br />
* '''##linuxmint'''<br />
<br />
=== Deliverables ===<br />
<br />
A paper with students' findings, or a blog post.<br />
<br />
=== Assessment ===<br />
<br />
=== Comments ===<br />
<br />
Depending on the project that you've chosen, it may be worthwhile to spend some time talking with students about the sort of interactions they might see -- and the lens to view it through. If you are working with a project that is historically not very diverse, you may want to pay particular attention to women and other underrepresented groups and their experience in open source.<br />
<br />
Finally, it may be that some channels are quiet and there is little activity. Providing some alternative channels such as OpenHatch could introduce the culture in a fairly neutral way.<br />
<br />
=== Variants and Adaptations ===<br />
<br />
[https://github.com/ChrisMurphyOnline/open-source-software-development-course/blob/master/activities/foss-get-involved.txt Modified version of activity] used by [[User:Cmurphy|Chris Murphy]] in his [[FOSS Course, UPenn, Murphy]].<br />
<br />
{{Learning Activity Info<br />
|acm unit=<br />
HCI/Collaboration and Communication<br />
|acm topic=<br />
* Asynchronous group communication, e.g., e-mail, forums, social networks<br />
* Synchronous group communication, e.g., chat rooms, conferencing, online games<br />
* Social media, social computing, and social network analysis<br />
* Online collaboration, 'smart' spaces, and social coordination aspects of workflow technologies<br />
* Online communities<br />
|difficulty=<br />
Easy<br />
|time=<br />
50-120 minutes<br />
|environment=<br />
IRC client, email client, browser and web access<br />
|author=<br />
Razvan A. Mezei<br />
|source=<br />
[[50 Ways to be a FOSSer]]<br />
|license=<br />
{{License CC BY SA}}<br />
}}<br />
<br />
=== Suggestions for the Open Source Project ===<br />
<br />
Be prepared for the additional influx of students -- and although they are in lurk mode, there’s a possibility that someone will goof and send something to the list. <br />
<br />
Also, if you have a code of conduct, you need to know what your “enforcement” routes are, should an issue occur.<br />
<br />
[[Category:Learning_Activity]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]<br />
[[Category:CS Principles]]<br />
[[Category:Good Draft]]</div>Bmorganhttp://foss2serve.org/index.php/Connect_with_the_Community_(Activity)Connect with the Community (Activity)2018-04-29T18:31:19Z<p>Bmorgan: /* PART 1: IRC */</p>
<hr />
<div>__NOTOC__<br />
<br />
{{Learning Activity Overview<br />
|title=<br />
Connect with the Community<br />
|overview= <br />
Learners should get familiar with communication tools (such as IRC, TitanPad, Skype, etc.) that are commonly used by FOSS communities.<br />
|prerequisites=<br />
|objectives=<br />
* Be familiar with different communication tools (such as iRC, TitanPad, Skype etc.) that are freely available for everyone. <br />
* Explore interactions and find out how different FOSS communities (HFOSS in particular) use these tools to communicate among their members.<br />
|process skills=<br />
}}<br />
<br />
=== Background ===<br />
<br />
If your class is embedded with an open source project, you should:<br />
# Join the comms channels for your project, <br />
# Discussed codes of conduct with your community liaison,<br />
# Discuss how to handle CoC violations when your students are involved.<br />
<br />
<br />
For general info on how open source projects use IRC, mailing lists and the like, there's a nice [[https://www.youtube.com/watch?v=0Z_KwdPvFy0 video]] on "how to communicate with your community" that Brian Proffitt at Red Hat has created that may be worth watching.<br />
<br />
=== Directions ===<br />
<br />
== PART 1: IRC ==<br />
<br />
'''This is the longest and most important part of this activity.'''<br />
<br />
IRC, which stands for Internet Relay Chat, is an essential tool used by open source software developers. It allows members of the community, or those interested in becoming involved in the community, to communicate 24/7, regardless of their geographic location. IRC is much like Instant Messaging with a group. Bear in mind that ‘talking’ is not always a requirement. You will learn a great deal by ‘listening’, especially in the beginning. <br />
<br />
* Choose a client from below<br />
** Web-based client: http://webchat.freenode.net <br />
** Web-based client: https://kiwiirc.com/client/irc.freenode.net <br />
** Windows: HydraIRC (http://www.hydrairc.com)<br />
** Linux: Konversation (http://konversation.kde.org)<br />
** Linux: xchat iRC (http://xchat.org/)<br />
** Mac OS X: Colloquy (http://colloquy.info)<br />
<br />
* Everybody should then<br />
** Connect to the server via the command: /server irc.freenode.net<br />
** Join our own (newly created) channel via the command: /join #chooseYourOwnChannel<br />
<br />
* Now let’s chat<br />
** each student should write at least one line, and use at least one command!<br />
** A list of useful iRC commands can be found here. http://www.ircbeginner.com/ircinfo/ircc-commands.html<br />
** Commands on using the Meetbot can be found here. https://wiki.debian.org/MeetBot<br />
<br />
* '''HOMEWORK 1''': join and observe an existing channel discussion<br />
** Connect to the '''freenode''' server via the command: '''/server webchat.freenode.net'''<br />
** Join the '''foss2serve''' channel via the command: '''/join #sourceforge'''<br />
** Monitor, then write and return a 1-page paper on the discussion you discover in here for at least a couple of hours:<br />
*** Pay attention to the interactions that occur between community members. <br />
*** Ignore the technical terms you don't understand. <br />
*** Accept that the content may be beyond your understanding at this point<br />
*** Observe:<br />
**** How do people interact in this context? <br />
**** What is the pattern of communication you just observed? <br />
**** Can you make any other observations?<br />
<br />
== PART 2: Titanpad ==<br />
<br />
Titanpad allows authors to simultaneously edit a text document, and see all of the participants' edits in real-time, with the ability to display each author's text in their own color. There is also a chat box in the sidebar to allow meta communication.<br />
<br />
In this part of the activity you will need to:<br />
* use a web browser to connect to: https://titanpad.com/ChooseYourPage<br />
* let’s chat:<br />
** do you have any comments you would like to share here about what you just observed in the iRC channel? <br />
** every student should write at least one line!<br />
<br />
<br />
== PART 3: Alternatives ==<br />
<br />
Propose some alternatives ways team can collaborate such as: mailing lists, blogs, twitter, facebook, google+, skype, wiki, iRC, community sites, blogs, twitter, youtube, slideshare, vimeo, etc. which ones do you think are most effective and why?<br />
'''In-class discussion'''. <br />
* Split the class in teams of 2-3 students each. Each team should visit one the following websites and identify as many ways of communications as possible for this community:<br />
** https://wiki.gnome.org/Accessibility<br />
** http://mifos.org/ <br />
** http://openmrs.org/<br />
** http://sahanafoundation.org/<br />
** http://www.ushahidi.com/<br />
* Discuss, in class, your findings.<br />
* '''HOMEWORK 2''': Write a 1-page paper with these findings.<br />
<br />
<br />
== PART 4: Discussions ==<br />
<br />
* Describe the difference between synchronous and asynchronous communication.<br />
* Compare the HCI issues in individual interaction with group interaction.<br />
* Discuss several issues of social concern raised by collaborative software.<br />
* Discuss the HCI issues in software that embodies human intention.<br />
<br />
<br />
== OTHER REFERENCES ==<br />
<br />
* http://foss2serve.org/index.php/Intro_IRC_Activity <br />
* http://foss2serve.org/index.php/IRC_Meeting_1 <br />
* http://foss2serve.org/index.php/HFOSS_Communities<br />
<br />
<br />
== SOME IRC CHANNELS ==<br />
<br />
* '''#openstack''' <br />
* '''#openstack-101'''<br />
* '''#openstack-doc'''<br />
* '''#wikipedia'''<br />
* '''##java''' <br />
** only registered nicks are allowed!!! You must create a registered nick on iRC. <br />
* '''##C++'''<br />
* '''##c++-basic'''<br />
* '''#sagemath'''<br />
* '''#ubuntu'''<br />
* '''##linuxmint'''<br />
<br />
=== Deliverables ===<br />
<br />
A paper with students' findings, or a blog post.<br />
<br />
=== Assessment ===<br />
<br />
=== Comments ===<br />
<br />
Depending on the project that you've chosen, it may be worthwhile to spend some time talking with students about the sort of interactions they might see -- and the lens to view it through. If you are working with a project that is historically not very diverse, you may want to pay particular attention to women and other underrepresented groups and their experience in open source.<br />
<br />
Finally, it may be that some channels are quiet and there is little activity. Providing some alternative channels such as OpenHatch could introduce the culture in a fairly neutral way.<br />
<br />
=== Variants and Adaptations ===<br />
<br />
[https://github.com/ChrisMurphyOnline/open-source-software-development-course/blob/master/activities/foss-get-involved.txt Modified version of activity] used by [[User:Cmurphy|Chris Murphy]] in his [[FOSS Course, UPenn, Murphy]].<br />
<br />
{{Learning Activity Info<br />
|acm unit=<br />
HCI/Collaboration and Communication<br />
|acm topic=<br />
* Asynchronous group communication, e.g., e-mail, forums, social networks<br />
* Synchronous group communication, e.g., chat rooms, conferencing, online games<br />
* Social media, social computing, and social network analysis<br />
* Online collaboration, 'smart' spaces, and social coordination aspects of workflow technologies<br />
* Online communities<br />
|difficulty=<br />
Easy<br />
|time=<br />
50-120 minutes<br />
|environment=<br />
IRC client, email client, browser and web access<br />
|author=<br />
Razvan A. Mezei<br />
|source=<br />
[[50 Ways to be a FOSSer]]<br />
|license=<br />
{{License CC BY SA}}<br />
}}<br />
<br />
=== Suggestions for the Open Source Project ===<br />
<br />
Be prepared for the additional influx of students -- and although they are in lurk mode, there’s a possibility that someone will goof and send something to the list. <br />
<br />
Also, if you have a code of conduct, you need to know what your “enforcement” routes are, should an issue occur.<br />
<br />
[[Category:Learning_Activity]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]<br />
[[Category:CS Principles]]<br />
[[Category:Good Draft]]</div>Bmorganhttp://foss2serve.org/index.php/IRC_Meeting_3IRC Meeting 32018-04-29T18:30:27Z<p>Bmorgan: /* To Join */</p>
<hr />
<div>{{Category:IRC}}<br />
<br />
== Agenda ==<br />
<br />
'''IRC Meeting 3''' has the following goals:<br />
<br />
* Discuss progress - please continue to log feedback in the [https://docs.google.com/spreadsheets/d/1hG45B8aK4A7JaSDx4PE3UvXQNMw6Ph-iE53YqvMOrWQ/edit?ts=5ae33a5d#gid=0 activity evaluation spreadsheet]<br />
* Discuss the results of B.4 and C.3 (FOSS in Courses Planning I and II) and answer any questions<br />
** These will be used as a base for [[Stage 2 Activities]] so more detail is better<br />
* Sign up for Stage 2 groups [http://foss2serve.org/index.php/Stage2_Groups here]<br />
** Join one project and one or more courses<br />
* Enter your arrival and departure times in the [https://docs.google.com/spreadsheets/d/1CRYf4xY6O0Pq5bacvMcyvxBDQtFR4iVpE6V56OcNxgU/edit#gid=0 POSSE Travel Arrangement Google Sheet] <br />
* Please make sure to arrive at Stage 2 with Git installed on your laptop and having completed C.2.<br />
* As always, please remember to log your progress in the [https://docs.google.com/spreadsheets/d/1hG45B8aK4A7JaSDx4PE3UvXQNMw6Ph-iE53YqvMOrWQ/edit?ts=5ae33a5d#gid=0 spreadsheet]<br />
<br />
== To Join ==<br />
<br />
Server: <br />
/attach irc.freenode.net<br />
Channel: <br />
/join #foss2serve<br />
<br />
As with previous IRC meetings, we'll have several of the POSSE team members to facilitate. We've asked people to sign up for different times to accommodate schedules, but also so that everyone will get to talk some without the conversation getting too confusing.<br />
<br />
== Notes ==<br />
<br />
* The IRC meetings will be recorded and processed by a MeetBot.<br />
* The meeting logs and summaries will be at http://meetbot-raw.fedoraproject.org/foss2serve/ under the date of the meeting.<br />
* They will also be on the wiki page for the individual POSSE.<br />
<br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]</div>Bmorganhttp://foss2serve.org/index.php/POSSE_2018-06POSSE 2018-062018-04-29T18:29:52Z<p>Bmorgan: /* Tools */</p>
<hr />
<div>__NOTOC__<br />
<br />
<!--<br />
README: To create a new POSSE page:<br />
# Update the announcement on the foss2serve.org homepage<br />
# Create a homepage for this POSSE. the page title is POSSE_yyyy-mm<br />
## Edit the page for the most recent POSSE, copy the entire contents, and paste into the new POSSE page.<br />
## Create the page for the new POSSE by changing the date & location in the title.<br />
## Change the dates for applications, the 3 stages, the 3 parts of Stage 1.<br />
## Change the link for the participants page.<br />
## Save the new POSSE page. <br />
# Edit the new participants page and set it up for this POSSE. An easy way to do this is to copy the prior participants page and delete all entries but the team<br />
# Edit the pages for Stage_1_Activities and Stage_2_Activities with due dates, IRC dates, etc.<br />
--><br />
<br />
===<center> POSSE - The Professors' Open Source Software Experience </center>===<br />
===<center>June 18-20, 2018 - Drexel University, Philadelphia, PA</center>===<br />
====<center><nowiki>http://foss2serve.org</nowiki>'''</center>====<br />
<!--<br />
====<center>[http://foss2serve.org/index.php/POSSE_Announcement_2017-04 Call for Participation]</center>====<br />
--><br />
====<center>[https://docs.google.com/forms/d/e/1FAIpQLSfwyz6liWKOdEL3im-JO6qutT8i8tC5SsFGcihr5puNlBFnUQ/viewform?c=0&w=1 Application]</center>====<br />
<center>Applications due: April 6, 2018; Notifications: April 16, 2018 </center><br />
<br />
====<center><font color='red'>Please note that due to NSF funding, only faculty members at U. S. institutions who are teaching in the United States are eligible for support.</font></center>====<br />
<br />
POSSE has three stages of participation: <br />
* [[Stage_1_Activities | Stage 1]] includes approximately 20 hours of online activities (both asynchronous and synchronous) over 8 weeks<br />
* [[Stage_2_Activities | Stage 2]] includes a 2.5 day face-to-face workshop<br />
* Stage 3 is ongoing participation in a community of faculty members who use HFOSS in their classes<br />
<br />
=== Welcome! ===<br />
<br />
Welcome to POSSE! This page provides some basic information to help you get started.<br />
<br />
=== Set Up ===<br />
There are several things that you should do to get set up for the POSSE experience. First, read this page thoroughly. Next, check that your login for this wiki works.<br />
<br />
=== Schedule ===<br />
This POSSE will include three stages. The schedule for these stages is shown below. <br />
<br />
==== Stage 1: April 23 - June 17 - Online activities ====<br />
The [[Stage_1_Activities | Stage 1 activities]] have been subdivided into three segments. Click on the link for each segment and please complete the activities by the due date. <br />
<br />
{| border="1" style="width:50%"<br />
|-<br />
| [[Stage_1_Activities#Part_A:_First_Two_Weeks|Part A]]<br />
| Due by May 6, 2018<br />
|-<br />
| [[Stage_1_Activities#Part_B:_Second_Two_Weeks|Part B]]<br />
| Due by May 27, 2018<br />
|-<br />
| [[Stage_1_Activities#Part_C:_Third_Two_Weeks|Part C]]<br />
| Due by June 17, 2018<br />
|}<br />
<br />
<br />
==== Stage 2: June 18-20, 2018 - Workshop in Philadelphia, PA ====<br />
The [[Stage_2_Activities|Stage 2 activities]] occur face to face.<br />
<br />
====<font color='red'>Note that funding support for Stage 2 is dependent on completing all Stage 1 activities.</font>====<br />
<br />
==== Stage 3: June 20th and beyond - Small group participation in HFOSS projects and the POSSE community ====<br />
<br />
=== Logistics ===<br />
This POSSE provides support for travel, lodging, and meals. Details will be provided to participants by email.<br />
<br />
=== Participants ===<br />
[[POSSE 2018-06 Participants]]<br />
<br />
=== Tools ===<br />
# IRC:<br />
## First connect to the server via the command: /server irc.freenode.net<br />
## Second, join the foss2serve channel via the command: /join #foss2serve<br />
# [http://www.foss2serve.org/index.php/Main_Page Wiki]<br />
# [http://foss2serve.org/index.php/HFOSS_Communities POSSE HFOSS projects]<br />
<br />
=== IRC Meeting Minutes ===<br />
<br />
* https://meetbot-raw.fedoraproject.org/foss2serve/<br />
<br />
===Additional Information===<br />
<br />
If you have questions contact one of the team members. For local arrangements, contact Greg Hislop at hislop at drexel.edu<br />
<br />
[[Category:POSSE]]<br />
[[Category:POSSE 2018-06]]</div>Bmorganhttp://foss2serve.org/index.php/Intro_to_IRC_(Activity)Intro to IRC (Activity)2018-04-29T18:28:35Z<p>Bmorgan: /* Comments */</p>
<hr />
<div>__NOTOC__<br />
<br />
{{Learning Activity Overview<br />
|title=<br />
Intro to IRC (Internet Relay Chat)<br />
|overview= <br />
Learners will gain a basic understanding of IRC (Internet Relay Chat) as well as the role that IRC plays in open source software development. <br />
Participants will learn about IRC etiquette and explore the interactions that occur between members of an open source community.<br />
|prerequisites=<br />
None.<br />
|objectives=<br />
# Describe the importance of IRC as it relates to open source software development.<br />
# Connect to an IRC server and join a channel.<br />
# Participate in a brief interaction on an IRC channel.<br />
|process skills=<br />
}}<br />
<br />
=== Background ===<br />
<br />
IRC (Internet Relay Chat) is an essential tool used by open source software developers. It allows members of the community, or those interested in becoming involved in the community, to communicate 24/7, regardless of their geographic location. IRC is much like Instant Messaging with a group. <br />
<br />
Bear in mind that ‘talking’ is not always a requirement. You will learn a great deal by ‘listening’, especially in the beginning. When you join a channel, it is not necessary to identify yourself or to say hi, you can simply 'lurk'. Feel free to ask questions, and note that it is not necessary to ask first if you can ask a question.<br />
<br />
IRC resources: <br />
* [http://www.irchelp.org IRC Help: tutorials and more] <br />
* http://teachingopensource.org/index.php/IRC<br />
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html A list of IRC commands] <br />
* [http://www.greenday.net/chat/commands.html More complete list of IRC Commands]<br />
<br />
=== Directions ===<br />
Throughout this activity you will be asked to answer questions, make observations, and may wish to take notes. These should be posted to your wiki page.<br />
<br />
==== Part 1 – Walk through of IRC Conversation ====<br />
<br />
Download this sample [[Media:mouseTrapMeeting.pdf | IRC Conversation]]<br />
<br />
This conversation is part of a meeting being run with a '''meetbot'''. <br />
A [http://wiki.debian.org/MeetBot meetbot] is a type of "bot" (or program that simulates a human activity) that works in IRC channels to help take notes for a meeting. <br />
Note the dark green entries in the conversation that begin with a hashmark. These are meetbot commands. <br />
* The first line of the conversation shows "darci" starting the meeting.<br />
* "totally" is the name of the meetbot.<br />
* The #topics command sets the topic of the conversation and is one of several commands. <br />
<br />
As you review the conversation, you should:<br />
# Pay attention to the interactions that occur between community members.<br />
# Ignore the technical terms.<br />
# Accept that the content may be beyond your understanding at this point, your first step in being productively lost.<br />
# Answer the following questions on your wiki page:<br />
#* How do people interact? <br />
#* What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix?<br />
#* Are there any terms that seem to have special meaning?<br />
#* Can you make any other observations?<br />
# Now look at the [[Media:mousetrapBot2013-03-01.pdf | results of the meetbot]]. This shows you how each meetbot command is formatted into a legible page that summarizes the meeting. Some additional formatting may be needed, but it certainly provides a great starting point. Here's a link to the final version of the [https://wiki.gnome.org/Projects/MouseTrap/Meetings/20130301 meeting notes]. <br />
#* Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?<br />
<br />
==== Part 2 – Install and Start an IRC Client ====<br />
<br />
There are many IRC clients to choose from, below is a brief list of suggestions:<br />
# Windows and Linux: Hexchat (https://hexchat.github.io/) or Pidgin (https://pidgin.im/)<br />
# Mac OS X: Colloquy (http://colloquy.info/) <br />
# Firefox add-on: ChatZilla (https://addons.mozilla.org/en-US/firefox/addon/chatzilla/) is a multi-platform add-on that will work on Windows, Linux and Mac OS X.<br />
<br />
For example, if you have Firefox running, follow these steps to add ChatZilla. <br />
<br />
# Click '''Tools''' from the main menu and then choose '''Add-ons'''. The Get Add-ons tab should be selected on the left. If you don’t see the main menu, click the menu button in the upper, right corner, and select Add-ons.<br />
# Scroll down and click the '''See more add-ons!''' button.<br />
# Type ChatZilla in the search box found in the upper, right corner.<br />
# Hover over the ChatZilla add-on and then click the '''Add to Firefox''' button to the right of the ChatZilla add-on. Note that ChatZilla is available in a number of languages, so be sure to select the appropriate one.<br />
# Restart Firefox.<br />
<br />
Note that there are some locations or situations where the IRC port is blocked. In such cases you may want to use a web-based client:<br />
# Kiwiirc, supports the freenode server and you can access the foss2serve channel from here. - https://kiwiirc.com/client/irc.freenode.net/<br />
# Mibbit, allows you to connect to a variety of servers. - http://www.mibbit.com/<br />
<br />
==== Part 3 – Join and Observe Channel Discussion ====<br />
The GNOME Accessibility Team (https://wiki.gnome.org/Accessibility) utilizes a fairly active channel. You should observe the #a11y channel for 24 hours and no, you do not need to be physically present for this length of time! You can join the channel and let the IRC client record the communications that occur. <br />
<br />
# Connect to the server via the command: /server irc.gnome.org<br />
# Join the a11y channel via the command: /join #a11y (note that 1 is the number one, not the letter L) <br />
# Summarize your observations on your wiki page. <br />
#* Pay particular attention to the ways that the communication in this channel differs from the sample dialog you examined in Part 1<br />
<br />
==== Part 4 – (Optional - Make your own channel and experiment) ====<br />
<br />
Sometimes the best way to figure out what's possible is just to play around and know you're not going to step on anyone's toes. In IRC you can create a channel by typing<br />
/join #channelname <br />
(and you can make "channelname" whatever made up thing that you want!).<br />
<br />
A variant of that is that if you type <br />
/join #yournick <br />
and no one has created the channel #yournick on that IRC server then a new channel called #yournick will be created and you'll automatically have Ops privileges. This is a fun way to experiment with Ops privs!<br />
<br />
Next, try one of the most useful commands (for almost any system, anywhere): help<br />
* Remember to precede it with the /, as that's what tells the client that it's a command, not text to be sent.<br />
* Invite another student to the your channel and try some of the commands that you can only do with Ops privileges <br />
* Record the commands you tried and what they did (in your own words) on your wiki page.<br />
<br />
=== Deliverables ===<br />
<br />
POSSE: Be ready to participate in the upcoming IRC meeting:<br />
* Have the appropriate IRC client installed and running<br />
* Test that you can connect to the network<br />
* Test that you can access freenode and the foss2serve channel<br />
** /server irc.freenode.net/<br />
** /join #foss2serve<br />
<br />
POSSE and Students will deliver:<br />
# For Part 1, their observations/answers to the following questions:<br />
#* How do people interact?<br />
#* What is the pattern of communication?<br />
#* Are there any terms that seem to have special meaning?<br />
#* What advantages might IRC have over other real-time communication methods (like Google Chat or Facebook Messenger?) Are there potential disadvantages? <br />
#* Can you make any other observations?<br />
#* Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?<br />
# For Part 2: nothing to deliver, should have successfully installed IRC client<br />
# For Part 3: observations of the #a11y channel communications and how they differed from the sample dialog in Part 1.<br />
# For Part 4 (optional): a list of at least 5 commands that will work in the channel that was created, and what they mean.<br />
<br />
= Notes for Instructors = <br />
The remaining sections of this document are intended for the instructor. They are not part of the learning activity that would be given to students.<br />
<br />
=== Assessment ===<br />
Some possible questions:<br />
* For what purposes do FOSS projects use IRC channels?<br />
* Why choose IRC over another synchronous collaboration method (like a conference call)?<br />
* How can IRC be used to facilitate project management?<br />
* In your own words, explain how to find a channel and join it for whichever IRC client you prefer.<br />
<br />
<br />
{| class="wikitable"<br />
|- <br />
|'''Criteria''' ||'''Level 1 (fail)'''||'''Level 2 (pass)'''||'''Level 3 (good)'''||'''Level 4 (exceptional)''' <br />
|-<br />
|Understanding of importance of IRC in open source (from observations of IRC log) || Did not attempt observations || Minimum effort put into observations (one statement per question, for example) || Complete observations || Well thought-out observations that tie the material back to other knowledge (bonus question also a nice addition) <br />
|-<br />
|Ability to connect to an IRC server and join a channel || Did not attempt || Installed client but did not join channel || Installed client, joined channel || Installed client, joined channel, made good observations of project <br />
|-<br />
|Become familiar with the interactions that occur in an IRC channel (from Observations of HFOSS project) || Did not attempt observations || Minimum effort put into observations (one statement per question, for example) || Complete observations || Well thought-out observations that tie the material back to other knowledge<br />
|-<br />
|}<br />
<br />
=== Comments ===<br />
<br />
* Some projects have multiple channels. There may be one for developers, another for documentation and another still for end users. These should all be listed on the project website. See, for example, [http://wiki.sahanafoundation.org/community/chat Sahana], which has:<br />
** Sahana : for general Sahana developer or user support from the community (starting point for most discussions)<br />
** Sahana-Meeting : for scheduled Sahana meetings<br />
** Sahana-Agasti : for Sahana Agasti-specific developer discussions<br />
** Sahana-Eden : for Sahana Eden-specific developer discussions<br />
** Sahana-GIS : for Sahana GIS-specific discussions<br />
<br />
* Depending on the project, its size, and the amount of activity on a project's channel, it may be necessary to determine an appropriate day for this observation. If there is a specific day/tim that the developers meet, you might want to schedule your observation for this day. You can join the channel and identify yourself as _afk (away from keyboard, for example joe_afk using the /nick command). When you return the following day, you will be able to observe the communication that occurred during the previous 24 hour period.<br />
<br />
*Note that many of the POSSE and OpenFE team hang out in the foss2serve channel throughout the day:<br />
** Connect to the server via the command: /server irc.freenode.net/<br />
** Join the foss2serve channel via the command: /join #foss2serve<br />
** Come join us!!!<br />
<br />
{{Learning Activity Info<br />
|acm unit=<br />
HCI/Collaboration and Communication, HCI/Foundations, SE/Software Project Management<br />
|acm topic=<br />
* Synchronous Group Communication<br />
* Social models that inform interaction design, e.g., culture, communication, networks and organizations (*why* IRC and not something else)<br />
* Team Participation/Team Management<br />
|difficulty=<br />
Easy<br />
|time=<br />
60-75 minutes<br />
|environment=<br />
Internet access, a Web browser and an IRC client.<br />
|author=<br />
Darci Burdge, Heidi Ellis & Gina Likins<br />
|source=<br />
[http://129.25.203.54/xcitegroup/softhum/doku.php?id=f:assignments Communication and Community]<br />
|license=<br />
{{License CC BY SA}}<br />
}}<br />
<br />
=== Suggestions for the Open Source Project ===<br />
<br />
What channels does your project use? Which would be most useful for students to join?<br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:Learning Activity]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]<br />
[[Category:CS Principles]]<br />
[[Category:Ready to Use]]</div>Bmorganhttp://foss2serve.org/index.php/Intro_to_IRC_(Activity)Intro to IRC (Activity)2018-04-29T18:27:05Z<p>Bmorgan: /* Deliverables */</p>
<hr />
<div>__NOTOC__<br />
<br />
{{Learning Activity Overview<br />
|title=<br />
Intro to IRC (Internet Relay Chat)<br />
|overview= <br />
Learners will gain a basic understanding of IRC (Internet Relay Chat) as well as the role that IRC plays in open source software development. <br />
Participants will learn about IRC etiquette and explore the interactions that occur between members of an open source community.<br />
|prerequisites=<br />
None.<br />
|objectives=<br />
# Describe the importance of IRC as it relates to open source software development.<br />
# Connect to an IRC server and join a channel.<br />
# Participate in a brief interaction on an IRC channel.<br />
|process skills=<br />
}}<br />
<br />
=== Background ===<br />
<br />
IRC (Internet Relay Chat) is an essential tool used by open source software developers. It allows members of the community, or those interested in becoming involved in the community, to communicate 24/7, regardless of their geographic location. IRC is much like Instant Messaging with a group. <br />
<br />
Bear in mind that ‘talking’ is not always a requirement. You will learn a great deal by ‘listening’, especially in the beginning. When you join a channel, it is not necessary to identify yourself or to say hi, you can simply 'lurk'. Feel free to ask questions, and note that it is not necessary to ask first if you can ask a question.<br />
<br />
IRC resources: <br />
* [http://www.irchelp.org IRC Help: tutorials and more] <br />
* http://teachingopensource.org/index.php/IRC<br />
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html A list of IRC commands] <br />
* [http://www.greenday.net/chat/commands.html More complete list of IRC Commands]<br />
<br />
=== Directions ===<br />
Throughout this activity you will be asked to answer questions, make observations, and may wish to take notes. These should be posted to your wiki page.<br />
<br />
==== Part 1 – Walk through of IRC Conversation ====<br />
<br />
Download this sample [[Media:mouseTrapMeeting.pdf | IRC Conversation]]<br />
<br />
This conversation is part of a meeting being run with a '''meetbot'''. <br />
A [http://wiki.debian.org/MeetBot meetbot] is a type of "bot" (or program that simulates a human activity) that works in IRC channels to help take notes for a meeting. <br />
Note the dark green entries in the conversation that begin with a hashmark. These are meetbot commands. <br />
* The first line of the conversation shows "darci" starting the meeting.<br />
* "totally" is the name of the meetbot.<br />
* The #topics command sets the topic of the conversation and is one of several commands. <br />
<br />
As you review the conversation, you should:<br />
# Pay attention to the interactions that occur between community members.<br />
# Ignore the technical terms.<br />
# Accept that the content may be beyond your understanding at this point, your first step in being productively lost.<br />
# Answer the following questions on your wiki page:<br />
#* How do people interact? <br />
#* What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix?<br />
#* Are there any terms that seem to have special meaning?<br />
#* Can you make any other observations?<br />
# Now look at the [[Media:mousetrapBot2013-03-01.pdf | results of the meetbot]]. This shows you how each meetbot command is formatted into a legible page that summarizes the meeting. Some additional formatting may be needed, but it certainly provides a great starting point. Here's a link to the final version of the [https://wiki.gnome.org/Projects/MouseTrap/Meetings/20130301 meeting notes]. <br />
#* Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?<br />
<br />
==== Part 2 – Install and Start an IRC Client ====<br />
<br />
There are many IRC clients to choose from, below is a brief list of suggestions:<br />
# Windows and Linux: Hexchat (https://hexchat.github.io/) or Pidgin (https://pidgin.im/)<br />
# Mac OS X: Colloquy (http://colloquy.info/) <br />
# Firefox add-on: ChatZilla (https://addons.mozilla.org/en-US/firefox/addon/chatzilla/) is a multi-platform add-on that will work on Windows, Linux and Mac OS X.<br />
<br />
For example, if you have Firefox running, follow these steps to add ChatZilla. <br />
<br />
# Click '''Tools''' from the main menu and then choose '''Add-ons'''. The Get Add-ons tab should be selected on the left. If you don’t see the main menu, click the menu button in the upper, right corner, and select Add-ons.<br />
# Scroll down and click the '''See more add-ons!''' button.<br />
# Type ChatZilla in the search box found in the upper, right corner.<br />
# Hover over the ChatZilla add-on and then click the '''Add to Firefox''' button to the right of the ChatZilla add-on. Note that ChatZilla is available in a number of languages, so be sure to select the appropriate one.<br />
# Restart Firefox.<br />
<br />
Note that there are some locations or situations where the IRC port is blocked. In such cases you may want to use a web-based client:<br />
# Kiwiirc, supports the freenode server and you can access the foss2serve channel from here. - https://kiwiirc.com/client/irc.freenode.net/<br />
# Mibbit, allows you to connect to a variety of servers. - http://www.mibbit.com/<br />
<br />
==== Part 3 – Join and Observe Channel Discussion ====<br />
The GNOME Accessibility Team (https://wiki.gnome.org/Accessibility) utilizes a fairly active channel. You should observe the #a11y channel for 24 hours and no, you do not need to be physically present for this length of time! You can join the channel and let the IRC client record the communications that occur. <br />
<br />
# Connect to the server via the command: /server irc.gnome.org<br />
# Join the a11y channel via the command: /join #a11y (note that 1 is the number one, not the letter L) <br />
# Summarize your observations on your wiki page. <br />
#* Pay particular attention to the ways that the communication in this channel differs from the sample dialog you examined in Part 1<br />
<br />
==== Part 4 – (Optional - Make your own channel and experiment) ====<br />
<br />
Sometimes the best way to figure out what's possible is just to play around and know you're not going to step on anyone's toes. In IRC you can create a channel by typing<br />
/join #channelname <br />
(and you can make "channelname" whatever made up thing that you want!).<br />
<br />
A variant of that is that if you type <br />
/join #yournick <br />
and no one has created the channel #yournick on that IRC server then a new channel called #yournick will be created and you'll automatically have Ops privileges. This is a fun way to experiment with Ops privs!<br />
<br />
Next, try one of the most useful commands (for almost any system, anywhere): help<br />
* Remember to precede it with the /, as that's what tells the client that it's a command, not text to be sent.<br />
* Invite another student to the your channel and try some of the commands that you can only do with Ops privileges <br />
* Record the commands you tried and what they did (in your own words) on your wiki page.<br />
<br />
=== Deliverables ===<br />
<br />
POSSE: Be ready to participate in the upcoming IRC meeting:<br />
* Have the appropriate IRC client installed and running<br />
* Test that you can connect to the network<br />
* Test that you can access freenode and the foss2serve channel<br />
** /server irc.freenode.net/<br />
** /join #foss2serve<br />
<br />
POSSE and Students will deliver:<br />
# For Part 1, their observations/answers to the following questions:<br />
#* How do people interact?<br />
#* What is the pattern of communication?<br />
#* Are there any terms that seem to have special meaning?<br />
#* What advantages might IRC have over other real-time communication methods (like Google Chat or Facebook Messenger?) Are there potential disadvantages? <br />
#* Can you make any other observations?<br />
#* Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?<br />
# For Part 2: nothing to deliver, should have successfully installed IRC client<br />
# For Part 3: observations of the #a11y channel communications and how they differed from the sample dialog in Part 1.<br />
# For Part 4 (optional): a list of at least 5 commands that will work in the channel that was created, and what they mean.<br />
<br />
= Notes for Instructors = <br />
The remaining sections of this document are intended for the instructor. They are not part of the learning activity that would be given to students.<br />
<br />
=== Assessment ===<br />
Some possible questions:<br />
* For what purposes do FOSS projects use IRC channels?<br />
* Why choose IRC over another synchronous collaboration method (like a conference call)?<br />
* How can IRC be used to facilitate project management?<br />
* In your own words, explain how to find a channel and join it for whichever IRC client you prefer.<br />
<br />
<br />
{| class="wikitable"<br />
|- <br />
|'''Criteria''' ||'''Level 1 (fail)'''||'''Level 2 (pass)'''||'''Level 3 (good)'''||'''Level 4 (exceptional)''' <br />
|-<br />
|Understanding of importance of IRC in open source (from observations of IRC log) || Did not attempt observations || Minimum effort put into observations (one statement per question, for example) || Complete observations || Well thought-out observations that tie the material back to other knowledge (bonus question also a nice addition) <br />
|-<br />
|Ability to connect to an IRC server and join a channel || Did not attempt || Installed client but did not join channel || Installed client, joined channel || Installed client, joined channel, made good observations of project <br />
|-<br />
|Become familiar with the interactions that occur in an IRC channel (from Observations of HFOSS project) || Did not attempt observations || Minimum effort put into observations (one statement per question, for example) || Complete observations || Well thought-out observations that tie the material back to other knowledge<br />
|-<br />
|}<br />
<br />
=== Comments ===<br />
<br />
* Some projects have multiple channels. There may be one for developers, another for documentation and another still for end users. These should all be listed on the project website. See, for example, [http://wiki.sahanafoundation.org/community/chat Sahana], which has:<br />
** Sahana : for general Sahana developer or user support from the community (starting point for most discussions)<br />
** Sahana-Meeting : for scheduled Sahana meetings<br />
** Sahana-Agasti : for Sahana Agasti-specific developer discussions<br />
** Sahana-Eden : for Sahana Eden-specific developer discussions<br />
** Sahana-GIS : for Sahana GIS-specific discussions<br />
<br />
* Depending on the project, its size, and the amount of activity on a project's channel, it may be necessary to determine an appropriate day for this observation. If there is a specific day/tim that the developers meet, you might want to schedule your observation for this day. You can join the channel and identify yourself as _afk (away from keyboard, for example joe_afk using the /nick command). When you return the following day, you will be able to observe the communication that occurred during the previous 24 hour period.<br />
<br />
*Note that many of the POSSE and OpenFE team hang out in the foss2serve channel throughout the day:<br />
** Connect to the server via the command: /server webchat.freenode.net/<br />
** Join the foss2serve channel via the command: /join #foss2serve<br />
** Come join us!!!<br />
<br />
{{Learning Activity Info<br />
|acm unit=<br />
HCI/Collaboration and Communication, HCI/Foundations, SE/Software Project Management<br />
|acm topic=<br />
* Synchronous Group Communication<br />
* Social models that inform interaction design, e.g., culture, communication, networks and organizations (*why* IRC and not something else)<br />
* Team Participation/Team Management<br />
|difficulty=<br />
Easy<br />
|time=<br />
60-75 minutes<br />
|environment=<br />
Internet access, a Web browser and an IRC client.<br />
|author=<br />
Darci Burdge, Heidi Ellis & Gina Likins<br />
|source=<br />
[http://129.25.203.54/xcitegroup/softhum/doku.php?id=f:assignments Communication and Community]<br />
|license=<br />
{{License CC BY SA}}<br />
}}<br />
<br />
=== Suggestions for the Open Source Project ===<br />
<br />
What channels does your project use? Which would be most useful for students to join?<br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:Learning Activity]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]<br />
[[Category:CS Principles]]<br />
[[Category:Ready to Use]]</div>Bmorganhttp://foss2serve.org/index.php/Connect_with_the_Community_(Activity)Connect with the Community (Activity)2018-04-29T18:22:04Z<p>Bmorgan: /* PART 1: IRC */</p>
<hr />
<div>__NOTOC__<br />
<br />
{{Learning Activity Overview<br />
|title=<br />
Connect with the Community<br />
|overview= <br />
Learners should get familiar with communication tools (such as IRC, TitanPad, Skype, etc.) that are commonly used by FOSS communities.<br />
|prerequisites=<br />
|objectives=<br />
* Be familiar with different communication tools (such as iRC, TitanPad, Skype etc.) that are freely available for everyone. <br />
* Explore interactions and find out how different FOSS communities (HFOSS in particular) use these tools to communicate among their members.<br />
|process skills=<br />
}}<br />
<br />
=== Background ===<br />
<br />
If your class is embedded with an open source project, you should:<br />
# Join the comms channels for your project, <br />
# Discussed codes of conduct with your community liaison,<br />
# Discuss how to handle CoC violations when your students are involved.<br />
<br />
<br />
For general info on how open source projects use IRC, mailing lists and the like, there's a nice [[https://www.youtube.com/watch?v=0Z_KwdPvFy0 video]] on "how to communicate with your community" that Brian Proffitt at Red Hat has created that may be worth watching.<br />
<br />
=== Directions ===<br />
<br />
== PART 1: IRC ==<br />
<br />
'''This is the longest and most important part of this activity.'''<br />
<br />
IRC, which stands for Internet Relay Chat, is an essential tool used by open source software developers. It allows members of the community, or those interested in becoming involved in the community, to communicate 24/7, regardless of their geographic location. IRC is much like Instant Messaging with a group. Bear in mind that ‘talking’ is not always a requirement. You will learn a great deal by ‘listening’, especially in the beginning. <br />
<br />
* Choose a client from below<br />
** Web-based client: http://webchat.freenode.net <br />
** Web-based client: https://kiwiirc.com/client/irc.freenode.net <br />
** Windows: HydraIRC (http://www.hydrairc.com)<br />
** Linux: Konversation (http://konversation.kde.org)<br />
** Linux: xchat iRC (http://xchat.org/)<br />
** Mac OS X: Colloquy (http://colloquy.info)<br />
<br />
* Everybody should then<br />
** Connect to the server via the command: /server webchat.freenode.net<br />
** Join our own (newly created) channel via the command: /join #chooseYourOwnChannel<br />
<br />
* Now let’s chat<br />
** each student should write at least one line, and use at least one command!<br />
** A list of useful iRC commands can be found here. http://www.ircbeginner.com/ircinfo/ircc-commands.html<br />
** Commands on using the Meetbot can be found here. https://wiki.debian.org/MeetBot<br />
<br />
* '''HOMEWORK 1''': join and observe an existing channel discussion<br />
** Connect to the '''freenode''' server via the command: '''/server webchat.freenode.net'''<br />
** Join the '''foss2serve''' channel via the command: '''/join #sourceforge'''<br />
** Monitor, then write and return a 1-page paper on the discussion you discover in here for at least a couple of hours:<br />
*** Pay attention to the interactions that occur between community members. <br />
*** Ignore the technical terms you don't understand. <br />
*** Accept that the content may be beyond your understanding at this point<br />
*** Observe:<br />
**** How do people interact in this context? <br />
**** What is the pattern of communication you just observed? <br />
**** Can you make any other observations?<br />
<br />
== PART 2: Titanpad ==<br />
<br />
Titanpad allows authors to simultaneously edit a text document, and see all of the participants' edits in real-time, with the ability to display each author's text in their own color. There is also a chat box in the sidebar to allow meta communication.<br />
<br />
In this part of the activity you will need to:<br />
* use a web browser to connect to: https://titanpad.com/ChooseYourPage<br />
* let’s chat:<br />
** do you have any comments you would like to share here about what you just observed in the iRC channel? <br />
** every student should write at least one line!<br />
<br />
<br />
== PART 3: Alternatives ==<br />
<br />
Propose some alternatives ways team can collaborate such as: mailing lists, blogs, twitter, facebook, google+, skype, wiki, iRC, community sites, blogs, twitter, youtube, slideshare, vimeo, etc. which ones do you think are most effective and why?<br />
'''In-class discussion'''. <br />
* Split the class in teams of 2-3 students each. Each team should visit one the following websites and identify as many ways of communications as possible for this community:<br />
** https://wiki.gnome.org/Accessibility<br />
** http://mifos.org/ <br />
** http://openmrs.org/<br />
** http://sahanafoundation.org/<br />
** http://www.ushahidi.com/<br />
* Discuss, in class, your findings.<br />
* '''HOMEWORK 2''': Write a 1-page paper with these findings.<br />
<br />
<br />
== PART 4: Discussions ==<br />
<br />
* Describe the difference between synchronous and asynchronous communication.<br />
* Compare the HCI issues in individual interaction with group interaction.<br />
* Discuss several issues of social concern raised by collaborative software.<br />
* Discuss the HCI issues in software that embodies human intention.<br />
<br />
<br />
== OTHER REFERENCES ==<br />
<br />
* http://foss2serve.org/index.php/Intro_IRC_Activity <br />
* http://foss2serve.org/index.php/IRC_Meeting_1 <br />
* http://foss2serve.org/index.php/HFOSS_Communities<br />
<br />
<br />
== SOME IRC CHANNELS ==<br />
<br />
* '''#openstack''' <br />
* '''#openstack-101'''<br />
* '''#openstack-doc'''<br />
* '''#wikipedia'''<br />
* '''##java''' <br />
** only registered nicks are allowed!!! You must create a registered nick on iRC. <br />
* '''##C++'''<br />
* '''##c++-basic'''<br />
* '''#sagemath'''<br />
* '''#ubuntu'''<br />
* '''##linuxmint'''<br />
<br />
=== Deliverables ===<br />
<br />
A paper with students' findings, or a blog post.<br />
<br />
=== Assessment ===<br />
<br />
=== Comments ===<br />
<br />
Depending on the project that you've chosen, it may be worthwhile to spend some time talking with students about the sort of interactions they might see -- and the lens to view it through. If you are working with a project that is historically not very diverse, you may want to pay particular attention to women and other underrepresented groups and their experience in open source.<br />
<br />
Finally, it may be that some channels are quiet and there is little activity. Providing some alternative channels such as OpenHatch could introduce the culture in a fairly neutral way.<br />
<br />
=== Variants and Adaptations ===<br />
<br />
[https://github.com/ChrisMurphyOnline/open-source-software-development-course/blob/master/activities/foss-get-involved.txt Modified version of activity] used by [[User:Cmurphy|Chris Murphy]] in his [[FOSS Course, UPenn, Murphy]].<br />
<br />
{{Learning Activity Info<br />
|acm unit=<br />
HCI/Collaboration and Communication<br />
|acm topic=<br />
* Asynchronous group communication, e.g., e-mail, forums, social networks<br />
* Synchronous group communication, e.g., chat rooms, conferencing, online games<br />
* Social media, social computing, and social network analysis<br />
* Online collaboration, 'smart' spaces, and social coordination aspects of workflow technologies<br />
* Online communities<br />
|difficulty=<br />
Easy<br />
|time=<br />
50-120 minutes<br />
|environment=<br />
IRC client, email client, browser and web access<br />
|author=<br />
Razvan A. Mezei<br />
|source=<br />
[[50 Ways to be a FOSSer]]<br />
|license=<br />
{{License CC BY SA}}<br />
}}<br />
<br />
=== Suggestions for the Open Source Project ===<br />
<br />
Be prepared for the additional influx of students -- and although they are in lurk mode, there’s a possibility that someone will goof and send something to the list. <br />
<br />
Also, if you have a code of conduct, you need to know what your “enforcement” routes are, should an issue occur.<br />
<br />
[[Category:Learning_Activity]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]<br />
[[Category:CS Principles]]<br />
[[Category:Good Draft]]</div>Bmorganhttp://foss2serve.org/index.php/IRC_Meeting_3IRC Meeting 32018-04-29T18:19:10Z<p>Bmorgan: /* To Join */</p>
<hr />
<div>{{Category:IRC}}<br />
<br />
== Agenda ==<br />
<br />
'''IRC Meeting 3''' has the following goals:<br />
<br />
* Discuss progress - please continue to log feedback in the [https://docs.google.com/spreadsheets/d/1hG45B8aK4A7JaSDx4PE3UvXQNMw6Ph-iE53YqvMOrWQ/edit?ts=5ae33a5d#gid=0 activity evaluation spreadsheet]<br />
* Discuss the results of B.4 and C.3 (FOSS in Courses Planning I and II) and answer any questions<br />
** These will be used as a base for [[Stage 2 Activities]] so more detail is better<br />
* Sign up for Stage 2 groups [http://foss2serve.org/index.php/Stage2_Groups here]<br />
** Join one project and one or more courses<br />
* Enter your arrival and departure times in the [https://docs.google.com/spreadsheets/d/1CRYf4xY6O0Pq5bacvMcyvxBDQtFR4iVpE6V56OcNxgU/edit#gid=0 POSSE Travel Arrangement Google Sheet] <br />
* Please make sure to arrive at Stage 2 with Git installed on your laptop and having completed C.2.<br />
* As always, please remember to log your progress in the [https://docs.google.com/spreadsheets/d/1hG45B8aK4A7JaSDx4PE3UvXQNMw6Ph-iE53YqvMOrWQ/edit?ts=5ae33a5d#gid=0 spreadsheet]<br />
<br />
== To Join ==<br />
<br />
Server: <br />
/attach webchat.freenode.net<br />
Channel: <br />
/join #foss2serve<br />
<br />
As with previous IRC meetings, we'll have several of the POSSE team members to facilitate. We've asked people to sign up for different times to accommodate schedules, but also so that everyone will get to talk some without the conversation getting too confusing.<br />
<br />
== Notes ==<br />
<br />
* The IRC meetings will be recorded and processed by a MeetBot.<br />
* The meeting logs and summaries will be at http://meetbot-raw.fedoraproject.org/foss2serve/ under the date of the meeting.<br />
* They will also be on the wiki page for the individual POSSE.<br />
<br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]</div>Bmorganhttp://foss2serve.org/index.php/POSSE_2018-06POSSE 2018-062018-04-29T18:18:22Z<p>Bmorgan: /* Tools */</p>
<hr />
<div>__NOTOC__<br />
<br />
<!--<br />
README: To create a new POSSE page:<br />
# Update the announcement on the foss2serve.org homepage<br />
# Create a homepage for this POSSE. the page title is POSSE_yyyy-mm<br />
## Edit the page for the most recent POSSE, copy the entire contents, and paste into the new POSSE page.<br />
## Create the page for the new POSSE by changing the date & location in the title.<br />
## Change the dates for applications, the 3 stages, the 3 parts of Stage 1.<br />
## Change the link for the participants page.<br />
## Save the new POSSE page. <br />
# Edit the new participants page and set it up for this POSSE. An easy way to do this is to copy the prior participants page and delete all entries but the team<br />
# Edit the pages for Stage_1_Activities and Stage_2_Activities with due dates, IRC dates, etc.<br />
--><br />
<br />
===<center> POSSE - The Professors' Open Source Software Experience </center>===<br />
===<center>June 18-20, 2018 - Drexel University, Philadelphia, PA</center>===<br />
====<center><nowiki>http://foss2serve.org</nowiki>'''</center>====<br />
<!--<br />
====<center>[http://foss2serve.org/index.php/POSSE_Announcement_2017-04 Call for Participation]</center>====<br />
--><br />
====<center>[https://docs.google.com/forms/d/e/1FAIpQLSfwyz6liWKOdEL3im-JO6qutT8i8tC5SsFGcihr5puNlBFnUQ/viewform?c=0&w=1 Application]</center>====<br />
<center>Applications due: April 6, 2018; Notifications: April 16, 2018 </center><br />
<br />
====<center><font color='red'>Please note that due to NSF funding, only faculty members at U. S. institutions who are teaching in the United States are eligible for support.</font></center>====<br />
<br />
POSSE has three stages of participation: <br />
* [[Stage_1_Activities | Stage 1]] includes approximately 20 hours of online activities (both asynchronous and synchronous) over 8 weeks<br />
* [[Stage_2_Activities | Stage 2]] includes a 2.5 day face-to-face workshop<br />
* Stage 3 is ongoing participation in a community of faculty members who use HFOSS in their classes<br />
<br />
=== Welcome! ===<br />
<br />
Welcome to POSSE! This page provides some basic information to help you get started.<br />
<br />
=== Set Up ===<br />
There are several things that you should do to get set up for the POSSE experience. First, read this page thoroughly. Next, check that your login for this wiki works.<br />
<br />
=== Schedule ===<br />
This POSSE will include three stages. The schedule for these stages is shown below. <br />
<br />
==== Stage 1: April 23 - June 17 - Online activities ====<br />
The [[Stage_1_Activities | Stage 1 activities]] have been subdivided into three segments. Click on the link for each segment and please complete the activities by the due date. <br />
<br />
{| border="1" style="width:50%"<br />
|-<br />
| [[Stage_1_Activities#Part_A:_First_Two_Weeks|Part A]]<br />
| Due by May 6, 2018<br />
|-<br />
| [[Stage_1_Activities#Part_B:_Second_Two_Weeks|Part B]]<br />
| Due by May 27, 2018<br />
|-<br />
| [[Stage_1_Activities#Part_C:_Third_Two_Weeks|Part C]]<br />
| Due by June 17, 2018<br />
|}<br />
<br />
<br />
==== Stage 2: June 18-20, 2018 - Workshop in Philadelphia, PA ====<br />
The [[Stage_2_Activities|Stage 2 activities]] occur face to face.<br />
<br />
====<font color='red'>Note that funding support for Stage 2 is dependent on completing all Stage 1 activities.</font>====<br />
<br />
==== Stage 3: June 20th and beyond - Small group participation in HFOSS projects and the POSSE community ====<br />
<br />
=== Logistics ===<br />
This POSSE provides support for travel, lodging, and meals. Details will be provided to participants by email.<br />
<br />
=== Participants ===<br />
[[POSSE 2018-06 Participants]]<br />
<br />
=== Tools ===<br />
# IRC:<br />
## First connect to the server via the command: /server webchat.freenode.net<br />
## Second, join the foss2serve channel via the command: /join #foss2serve<br />
# [http://www.foss2serve.org/index.php/Main_Page Wiki]<br />
# [http://foss2serve.org/index.php/HFOSS_Communities POSSE HFOSS projects]<br />
<br />
=== IRC Meeting Minutes ===<br />
<br />
* https://meetbot-raw.fedoraproject.org/foss2serve/<br />
<br />
===Additional Information===<br />
<br />
If you have questions contact one of the team members. For local arrangements, contact Greg Hislop at hislop at drexel.edu<br />
<br />
[[Category:POSSE]]<br />
[[Category:POSSE 2018-06]]</div>Bmorganhttp://foss2serve.org/index.php/Intro_to_IRC_(Activity)Intro to IRC (Activity)2018-04-29T18:15:19Z<p>Bmorgan: /* Comments */</p>
<hr />
<div>__NOTOC__<br />
<br />
{{Learning Activity Overview<br />
|title=<br />
Intro to IRC (Internet Relay Chat)<br />
|overview= <br />
Learners will gain a basic understanding of IRC (Internet Relay Chat) as well as the role that IRC plays in open source software development. <br />
Participants will learn about IRC etiquette and explore the interactions that occur between members of an open source community.<br />
|prerequisites=<br />
None.<br />
|objectives=<br />
# Describe the importance of IRC as it relates to open source software development.<br />
# Connect to an IRC server and join a channel.<br />
# Participate in a brief interaction on an IRC channel.<br />
|process skills=<br />
}}<br />
<br />
=== Background ===<br />
<br />
IRC (Internet Relay Chat) is an essential tool used by open source software developers. It allows members of the community, or those interested in becoming involved in the community, to communicate 24/7, regardless of their geographic location. IRC is much like Instant Messaging with a group. <br />
<br />
Bear in mind that ‘talking’ is not always a requirement. You will learn a great deal by ‘listening’, especially in the beginning. When you join a channel, it is not necessary to identify yourself or to say hi, you can simply 'lurk'. Feel free to ask questions, and note that it is not necessary to ask first if you can ask a question.<br />
<br />
IRC resources: <br />
* [http://www.irchelp.org IRC Help: tutorials and more] <br />
* http://teachingopensource.org/index.php/IRC<br />
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html A list of IRC commands] <br />
* [http://www.greenday.net/chat/commands.html More complete list of IRC Commands]<br />
<br />
=== Directions ===<br />
Throughout this activity you will be asked to answer questions, make observations, and may wish to take notes. These should be posted to your wiki page.<br />
<br />
==== Part 1 – Walk through of IRC Conversation ====<br />
<br />
Download this sample [[Media:mouseTrapMeeting.pdf | IRC Conversation]]<br />
<br />
This conversation is part of a meeting being run with a '''meetbot'''. <br />
A [http://wiki.debian.org/MeetBot meetbot] is a type of "bot" (or program that simulates a human activity) that works in IRC channels to help take notes for a meeting. <br />
Note the dark green entries in the conversation that begin with a hashmark. These are meetbot commands. <br />
* The first line of the conversation shows "darci" starting the meeting.<br />
* "totally" is the name of the meetbot.<br />
* The #topics command sets the topic of the conversation and is one of several commands. <br />
<br />
As you review the conversation, you should:<br />
# Pay attention to the interactions that occur between community members.<br />
# Ignore the technical terms.<br />
# Accept that the content may be beyond your understanding at this point, your first step in being productively lost.<br />
# Answer the following questions on your wiki page:<br />
#* How do people interact? <br />
#* What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix?<br />
#* Are there any terms that seem to have special meaning?<br />
#* Can you make any other observations?<br />
# Now look at the [[Media:mousetrapBot2013-03-01.pdf | results of the meetbot]]. This shows you how each meetbot command is formatted into a legible page that summarizes the meeting. Some additional formatting may be needed, but it certainly provides a great starting point. Here's a link to the final version of the [https://wiki.gnome.org/Projects/MouseTrap/Meetings/20130301 meeting notes]. <br />
#* Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?<br />
<br />
==== Part 2 – Install and Start an IRC Client ====<br />
<br />
There are many IRC clients to choose from, below is a brief list of suggestions:<br />
# Windows and Linux: Hexchat (https://hexchat.github.io/) or Pidgin (https://pidgin.im/)<br />
# Mac OS X: Colloquy (http://colloquy.info/) <br />
# Firefox add-on: ChatZilla (https://addons.mozilla.org/en-US/firefox/addon/chatzilla/) is a multi-platform add-on that will work on Windows, Linux and Mac OS X.<br />
<br />
For example, if you have Firefox running, follow these steps to add ChatZilla. <br />
<br />
# Click '''Tools''' from the main menu and then choose '''Add-ons'''. The Get Add-ons tab should be selected on the left. If you don’t see the main menu, click the menu button in the upper, right corner, and select Add-ons.<br />
# Scroll down and click the '''See more add-ons!''' button.<br />
# Type ChatZilla in the search box found in the upper, right corner.<br />
# Hover over the ChatZilla add-on and then click the '''Add to Firefox''' button to the right of the ChatZilla add-on. Note that ChatZilla is available in a number of languages, so be sure to select the appropriate one.<br />
# Restart Firefox.<br />
<br />
Note that there are some locations or situations where the IRC port is blocked. In such cases you may want to use a web-based client:<br />
# Kiwiirc, supports the freenode server and you can access the foss2serve channel from here. - https://kiwiirc.com/client/irc.freenode.net/<br />
# Mibbit, allows you to connect to a variety of servers. - http://www.mibbit.com/<br />
<br />
==== Part 3 – Join and Observe Channel Discussion ====<br />
The GNOME Accessibility Team (https://wiki.gnome.org/Accessibility) utilizes a fairly active channel. You should observe the #a11y channel for 24 hours and no, you do not need to be physically present for this length of time! You can join the channel and let the IRC client record the communications that occur. <br />
<br />
# Connect to the server via the command: /server irc.gnome.org<br />
# Join the a11y channel via the command: /join #a11y (note that 1 is the number one, not the letter L) <br />
# Summarize your observations on your wiki page. <br />
#* Pay particular attention to the ways that the communication in this channel differs from the sample dialog you examined in Part 1<br />
<br />
==== Part 4 – (Optional - Make your own channel and experiment) ====<br />
<br />
Sometimes the best way to figure out what's possible is just to play around and know you're not going to step on anyone's toes. In IRC you can create a channel by typing<br />
/join #channelname <br />
(and you can make "channelname" whatever made up thing that you want!).<br />
<br />
A variant of that is that if you type <br />
/join #yournick <br />
and no one has created the channel #yournick on that IRC server then a new channel called #yournick will be created and you'll automatically have Ops privileges. This is a fun way to experiment with Ops privs!<br />
<br />
Next, try one of the most useful commands (for almost any system, anywhere): help<br />
* Remember to precede it with the /, as that's what tells the client that it's a command, not text to be sent.<br />
* Invite another student to the your channel and try some of the commands that you can only do with Ops privileges <br />
* Record the commands you tried and what they did (in your own words) on your wiki page.<br />
<br />
=== Deliverables ===<br />
<br />
POSSE: Be ready to participate in the upcoming IRC meeting:<br />
* Have the appropriate IRC client installed and running<br />
* Test that you can connect to the network<br />
* Test that you can access freenode and the foss2serve channel<br />
** /server webchat.freenode.net/<br />
** /join #foss2serve<br />
<br />
POSSE and Students will deliver:<br />
# For Part 1, their observations/answers to the following questions:<br />
#* How do people interact?<br />
#* What is the pattern of communication?<br />
#* Are there any terms that seem to have special meaning?<br />
#* What advantages might IRC have over other real-time communication methods (like Google Chat or Facebook Messenger?) Are there potential disadvantages? <br />
#* Can you make any other observations?<br />
#* Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?<br />
# For Part 2: nothing to deliver, should have successfully installed IRC client<br />
# For Part 3: observations of the #a11y channel communications and how they differed from the sample dialog in Part 1.<br />
# For Part 4 (optional): a list of at least 5 commands that will work in the channel that was created, and what they mean.<br />
<br />
= Notes for Instructors = <br />
The remaining sections of this document are intended for the instructor. They are not part of the learning activity that would be given to students.<br />
<br />
=== Assessment ===<br />
Some possible questions:<br />
* For what purposes do FOSS projects use IRC channels?<br />
* Why choose IRC over another synchronous collaboration method (like a conference call)?<br />
* How can IRC be used to facilitate project management?<br />
* In your own words, explain how to find a channel and join it for whichever IRC client you prefer.<br />
<br />
<br />
{| class="wikitable"<br />
|- <br />
|'''Criteria''' ||'''Level 1 (fail)'''||'''Level 2 (pass)'''||'''Level 3 (good)'''||'''Level 4 (exceptional)''' <br />
|-<br />
|Understanding of importance of IRC in open source (from observations of IRC log) || Did not attempt observations || Minimum effort put into observations (one statement per question, for example) || Complete observations || Well thought-out observations that tie the material back to other knowledge (bonus question also a nice addition) <br />
|-<br />
|Ability to connect to an IRC server and join a channel || Did not attempt || Installed client but did not join channel || Installed client, joined channel || Installed client, joined channel, made good observations of project <br />
|-<br />
|Become familiar with the interactions that occur in an IRC channel (from Observations of HFOSS project) || Did not attempt observations || Minimum effort put into observations (one statement per question, for example) || Complete observations || Well thought-out observations that tie the material back to other knowledge<br />
|-<br />
|}<br />
<br />
=== Comments ===<br />
<br />
* Some projects have multiple channels. There may be one for developers, another for documentation and another still for end users. These should all be listed on the project website. See, for example, [http://wiki.sahanafoundation.org/community/chat Sahana], which has:<br />
** Sahana : for general Sahana developer or user support from the community (starting point for most discussions)<br />
** Sahana-Meeting : for scheduled Sahana meetings<br />
** Sahana-Agasti : for Sahana Agasti-specific developer discussions<br />
** Sahana-Eden : for Sahana Eden-specific developer discussions<br />
** Sahana-GIS : for Sahana GIS-specific discussions<br />
<br />
* Depending on the project, its size, and the amount of activity on a project's channel, it may be necessary to determine an appropriate day for this observation. If there is a specific day/tim that the developers meet, you might want to schedule your observation for this day. You can join the channel and identify yourself as _afk (away from keyboard, for example joe_afk using the /nick command). When you return the following day, you will be able to observe the communication that occurred during the previous 24 hour period.<br />
<br />
*Note that many of the POSSE and OpenFE team hang out in the foss2serve channel throughout the day:<br />
** Connect to the server via the command: /server webchat.freenode.net/<br />
** Join the foss2serve channel via the command: /join #foss2serve<br />
** Come join us!!!<br />
<br />
{{Learning Activity Info<br />
|acm unit=<br />
HCI/Collaboration and Communication, HCI/Foundations, SE/Software Project Management<br />
|acm topic=<br />
* Synchronous Group Communication<br />
* Social models that inform interaction design, e.g., culture, communication, networks and organizations (*why* IRC and not something else)<br />
* Team Participation/Team Management<br />
|difficulty=<br />
Easy<br />
|time=<br />
60-75 minutes<br />
|environment=<br />
Internet access, a Web browser and an IRC client.<br />
|author=<br />
Darci Burdge, Heidi Ellis & Gina Likins<br />
|source=<br />
[http://129.25.203.54/xcitegroup/softhum/doku.php?id=f:assignments Communication and Community]<br />
|license=<br />
{{License CC BY SA}}<br />
}}<br />
<br />
=== Suggestions for the Open Source Project ===<br />
<br />
What channels does your project use? Which would be most useful for students to join?<br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:Learning Activity]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]<br />
[[Category:CS Principles]]<br />
[[Category:Ready to Use]]</div>Bmorganhttp://foss2serve.org/index.php/Intro_to_IRC_(Activity)Intro to IRC (Activity)2018-04-29T18:14:37Z<p>Bmorgan: /* Deliverables */</p>
<hr />
<div>__NOTOC__<br />
<br />
{{Learning Activity Overview<br />
|title=<br />
Intro to IRC (Internet Relay Chat)<br />
|overview= <br />
Learners will gain a basic understanding of IRC (Internet Relay Chat) as well as the role that IRC plays in open source software development. <br />
Participants will learn about IRC etiquette and explore the interactions that occur between members of an open source community.<br />
|prerequisites=<br />
None.<br />
|objectives=<br />
# Describe the importance of IRC as it relates to open source software development.<br />
# Connect to an IRC server and join a channel.<br />
# Participate in a brief interaction on an IRC channel.<br />
|process skills=<br />
}}<br />
<br />
=== Background ===<br />
<br />
IRC (Internet Relay Chat) is an essential tool used by open source software developers. It allows members of the community, or those interested in becoming involved in the community, to communicate 24/7, regardless of their geographic location. IRC is much like Instant Messaging with a group. <br />
<br />
Bear in mind that ‘talking’ is not always a requirement. You will learn a great deal by ‘listening’, especially in the beginning. When you join a channel, it is not necessary to identify yourself or to say hi, you can simply 'lurk'. Feel free to ask questions, and note that it is not necessary to ask first if you can ask a question.<br />
<br />
IRC resources: <br />
* [http://www.irchelp.org IRC Help: tutorials and more] <br />
* http://teachingopensource.org/index.php/IRC<br />
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html A list of IRC commands] <br />
* [http://www.greenday.net/chat/commands.html More complete list of IRC Commands]<br />
<br />
=== Directions ===<br />
Throughout this activity you will be asked to answer questions, make observations, and may wish to take notes. These should be posted to your wiki page.<br />
<br />
==== Part 1 – Walk through of IRC Conversation ====<br />
<br />
Download this sample [[Media:mouseTrapMeeting.pdf | IRC Conversation]]<br />
<br />
This conversation is part of a meeting being run with a '''meetbot'''. <br />
A [http://wiki.debian.org/MeetBot meetbot] is a type of "bot" (or program that simulates a human activity) that works in IRC channels to help take notes for a meeting. <br />
Note the dark green entries in the conversation that begin with a hashmark. These are meetbot commands. <br />
* The first line of the conversation shows "darci" starting the meeting.<br />
* "totally" is the name of the meetbot.<br />
* The #topics command sets the topic of the conversation and is one of several commands. <br />
<br />
As you review the conversation, you should:<br />
# Pay attention to the interactions that occur between community members.<br />
# Ignore the technical terms.<br />
# Accept that the content may be beyond your understanding at this point, your first step in being productively lost.<br />
# Answer the following questions on your wiki page:<br />
#* How do people interact? <br />
#* What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix?<br />
#* Are there any terms that seem to have special meaning?<br />
#* Can you make any other observations?<br />
# Now look at the [[Media:mousetrapBot2013-03-01.pdf | results of the meetbot]]. This shows you how each meetbot command is formatted into a legible page that summarizes the meeting. Some additional formatting may be needed, but it certainly provides a great starting point. Here's a link to the final version of the [https://wiki.gnome.org/Projects/MouseTrap/Meetings/20130301 meeting notes]. <br />
#* Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?<br />
<br />
==== Part 2 – Install and Start an IRC Client ====<br />
<br />
There are many IRC clients to choose from, below is a brief list of suggestions:<br />
# Windows and Linux: Hexchat (https://hexchat.github.io/) or Pidgin (https://pidgin.im/)<br />
# Mac OS X: Colloquy (http://colloquy.info/) <br />
# Firefox add-on: ChatZilla (https://addons.mozilla.org/en-US/firefox/addon/chatzilla/) is a multi-platform add-on that will work on Windows, Linux and Mac OS X.<br />
<br />
For example, if you have Firefox running, follow these steps to add ChatZilla. <br />
<br />
# Click '''Tools''' from the main menu and then choose '''Add-ons'''. The Get Add-ons tab should be selected on the left. If you don’t see the main menu, click the menu button in the upper, right corner, and select Add-ons.<br />
# Scroll down and click the '''See more add-ons!''' button.<br />
# Type ChatZilla in the search box found in the upper, right corner.<br />
# Hover over the ChatZilla add-on and then click the '''Add to Firefox''' button to the right of the ChatZilla add-on. Note that ChatZilla is available in a number of languages, so be sure to select the appropriate one.<br />
# Restart Firefox.<br />
<br />
Note that there are some locations or situations where the IRC port is blocked. In such cases you may want to use a web-based client:<br />
# Kiwiirc, supports the freenode server and you can access the foss2serve channel from here. - https://kiwiirc.com/client/irc.freenode.net/<br />
# Mibbit, allows you to connect to a variety of servers. - http://www.mibbit.com/<br />
<br />
==== Part 3 – Join and Observe Channel Discussion ====<br />
The GNOME Accessibility Team (https://wiki.gnome.org/Accessibility) utilizes a fairly active channel. You should observe the #a11y channel for 24 hours and no, you do not need to be physically present for this length of time! You can join the channel and let the IRC client record the communications that occur. <br />
<br />
# Connect to the server via the command: /server irc.gnome.org<br />
# Join the a11y channel via the command: /join #a11y (note that 1 is the number one, not the letter L) <br />
# Summarize your observations on your wiki page. <br />
#* Pay particular attention to the ways that the communication in this channel differs from the sample dialog you examined in Part 1<br />
<br />
==== Part 4 – (Optional - Make your own channel and experiment) ====<br />
<br />
Sometimes the best way to figure out what's possible is just to play around and know you're not going to step on anyone's toes. In IRC you can create a channel by typing<br />
/join #channelname <br />
(and you can make "channelname" whatever made up thing that you want!).<br />
<br />
A variant of that is that if you type <br />
/join #yournick <br />
and no one has created the channel #yournick on that IRC server then a new channel called #yournick will be created and you'll automatically have Ops privileges. This is a fun way to experiment with Ops privs!<br />
<br />
Next, try one of the most useful commands (for almost any system, anywhere): help<br />
* Remember to precede it with the /, as that's what tells the client that it's a command, not text to be sent.<br />
* Invite another student to the your channel and try some of the commands that you can only do with Ops privileges <br />
* Record the commands you tried and what they did (in your own words) on your wiki page.<br />
<br />
=== Deliverables ===<br />
<br />
POSSE: Be ready to participate in the upcoming IRC meeting:<br />
* Have the appropriate IRC client installed and running<br />
* Test that you can connect to the network<br />
* Test that you can access freenode and the foss2serve channel<br />
** /server webchat.freenode.net/<br />
** /join #foss2serve<br />
<br />
POSSE and Students will deliver:<br />
# For Part 1, their observations/answers to the following questions:<br />
#* How do people interact?<br />
#* What is the pattern of communication?<br />
#* Are there any terms that seem to have special meaning?<br />
#* What advantages might IRC have over other real-time communication methods (like Google Chat or Facebook Messenger?) Are there potential disadvantages? <br />
#* Can you make any other observations?<br />
#* Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?<br />
# For Part 2: nothing to deliver, should have successfully installed IRC client<br />
# For Part 3: observations of the #a11y channel communications and how they differed from the sample dialog in Part 1.<br />
# For Part 4 (optional): a list of at least 5 commands that will work in the channel that was created, and what they mean.<br />
<br />
= Notes for Instructors = <br />
The remaining sections of this document are intended for the instructor. They are not part of the learning activity that would be given to students.<br />
<br />
=== Assessment ===<br />
Some possible questions:<br />
* For what purposes do FOSS projects use IRC channels?<br />
* Why choose IRC over another synchronous collaboration method (like a conference call)?<br />
* How can IRC be used to facilitate project management?<br />
* In your own words, explain how to find a channel and join it for whichever IRC client you prefer.<br />
<br />
<br />
{| class="wikitable"<br />
|- <br />
|'''Criteria''' ||'''Level 1 (fail)'''||'''Level 2 (pass)'''||'''Level 3 (good)'''||'''Level 4 (exceptional)''' <br />
|-<br />
|Understanding of importance of IRC in open source (from observations of IRC log) || Did not attempt observations || Minimum effort put into observations (one statement per question, for example) || Complete observations || Well thought-out observations that tie the material back to other knowledge (bonus question also a nice addition) <br />
|-<br />
|Ability to connect to an IRC server and join a channel || Did not attempt || Installed client but did not join channel || Installed client, joined channel || Installed client, joined channel, made good observations of project <br />
|-<br />
|Become familiar with the interactions that occur in an IRC channel (from Observations of HFOSS project) || Did not attempt observations || Minimum effort put into observations (one statement per question, for example) || Complete observations || Well thought-out observations that tie the material back to other knowledge<br />
|-<br />
|}<br />
<br />
=== Comments ===<br />
<br />
* Some projects have multiple channels. There may be one for developers, another for documentation and another still for end users. These should all be listed on the project website. See, for example, [http://wiki.sahanafoundation.org/community/chat Sahana], which has:<br />
** Sahana : for general Sahana developer or user support from the community (starting point for most discussions)<br />
** Sahana-Meeting : for scheduled Sahana meetings<br />
** Sahana-Agasti : for Sahana Agasti-specific developer discussions<br />
** Sahana-Eden : for Sahana Eden-specific developer discussions<br />
** Sahana-GIS : for Sahana GIS-specific discussions<br />
<br />
* Depending on the project, its size, and the amount of activity on a project's channel, it may be necessary to determine an appropriate day for this observation. If there is a specific day/tim that the developers meet, you might want to schedule your observation for this day. You can join the channel and identify yourself as _afk (away from keyboard, for example joe_afk using the /nick command). When you return the following day, you will be able to observe the communication that occurred during the previous 24 hour period.<br />
<br />
*Note that many of the POSSE and OpenFE team hang out in the foss2serve channel throughout the day:<br />
** Connect to the server via the command: /server irc.freenode.net<br />
** Join the foss2serve channel via the command: /join #foss2serve<br />
** Come join us!!!<br />
<br />
{{Learning Activity Info<br />
|acm unit=<br />
HCI/Collaboration and Communication, HCI/Foundations, SE/Software Project Management<br />
|acm topic=<br />
* Synchronous Group Communication<br />
* Social models that inform interaction design, e.g., culture, communication, networks and organizations (*why* IRC and not something else)<br />
* Team Participation/Team Management<br />
|difficulty=<br />
Easy<br />
|time=<br />
60-75 minutes<br />
|environment=<br />
Internet access, a Web browser and an IRC client.<br />
|author=<br />
Darci Burdge, Heidi Ellis & Gina Likins<br />
|source=<br />
[http://129.25.203.54/xcitegroup/softhum/doku.php?id=f:assignments Communication and Community]<br />
|license=<br />
{{License CC BY SA}}<br />
}}<br />
<br />
=== Suggestions for the Open Source Project ===<br />
<br />
What channels does your project use? Which would be most useful for students to join?<br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:Learning Activity]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]<br />
[[Category:CS Principles]]<br />
[[Category:Ready to Use]]</div>Bmorganhttp://foss2serve.org/index.php/IRC_Meeting_2IRC Meeting 22018-04-29T18:10:46Z<p>Bmorgan: /* To Join */</p>
<hr />
<div>{{Category:IRC}}<br />
<br />
== Agenda ==<br />
<br />
'''IRC Meeting 2''' has the following goals:<br />
* To provide an opportunity for all participants to provide an update on their progress on POSSE stage 1 activities (your feedback in the spreadsheet is important)<br />
* To allow participants to ask questions about POSSE [[Stage 1 Activities]]<br />
* To allow participants to talk about the courses in which they plan to use HFOSS<br />
* To allow participants to ask questions about POSSE [[Stage 2 Activities]]<br />
* To inform participants about signing up for [[Stage2 Groups]]<br />
* Reminder: Please log your progress in the google doc: https://docs.google.com/spreadsheets/d/1ICKFeErc3F2-94ByaG3E4QAc67W5Opk_emTL0_Rh51w/edit#gid=0<br />
<br />
== To Join ==<br />
<br />
Server: <br />
/attach http://webchat.freenode.net/<br />
Channel: <br />
/join #foss2serve<br />
<br />
As with the previous IRC meetings, we'll have several of the POSSE team members to facilitate. We've asked people to sign up for different times to accommodate schedules, but also so that everyone will have the opportunity to ask questions.<br />
<br />
== Notes ==<br />
<br />
* The IRC meetings will be recorded and processed by a MeetBot.<br />
* The meeting logs and summaries will be at http://meetbot-raw.fedoraproject.org/foss2serve/ under the date of the meeting.<br />
* They will also be on the wiki page for the individual POSSE.<br />
<br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]</div>Bmorganhttp://foss2serve.org/index.php/IRC_Meeting_2IRC Meeting 22018-04-29T18:06:44Z<p>Bmorgan: /* To Join */</p>
<hr />
<div>{{Category:IRC}}<br />
<br />
== Agenda ==<br />
<br />
'''IRC Meeting 2''' has the following goals:<br />
* To provide an opportunity for all participants to provide an update on their progress on POSSE stage 1 activities (your feedback in the spreadsheet is important)<br />
* To allow participants to ask questions about POSSE [[Stage 1 Activities]]<br />
* To allow participants to talk about the courses in which they plan to use HFOSS<br />
* To allow participants to ask questions about POSSE [[Stage 2 Activities]]<br />
* To inform participants about signing up for [[Stage2 Groups]]<br />
* Reminder: Please log your progress in the google doc: https://docs.google.com/spreadsheets/d/1ICKFeErc3F2-94ByaG3E4QAc67W5Opk_emTL0_Rh51w/edit#gid=0<br />
<br />
== To Join ==<br />
<br />
Server: <br />
/attach webchat.freenode.net/<br />
Channel: <br />
/join #foss2serve<br />
<br />
As with the previous IRC meetings, we'll have several of the POSSE team members to facilitate. We've asked people to sign up for different times to accommodate schedules, but also so that everyone will have the opportunity to ask questions.<br />
<br />
== Notes ==<br />
<br />
* The IRC meetings will be recorded and processed by a MeetBot.<br />
* The meeting logs and summaries will be at http://meetbot-raw.fedoraproject.org/foss2serve/ under the date of the meeting.<br />
* They will also be on the wiki page for the individual POSSE.<br />
<br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:Communication and Tools]]<br />
[[Category:IRC]]</div>Bmorganhttp://foss2serve.org/index.php/FOSS_in_Courses_1_(Instructors)FOSS in Courses 1 (Instructors)2018-04-29T17:38:12Z<p>Bmorgan: /* Directions */</p>
<hr />
<div>__NOTOC__<br />
<br />
{{Learning Activity Overview<br />
|title=<br />
FOSS In Courses 1<br />
|overview= <br />
Learners will gain an understanding of the variety of different ways that FOSS can be incorporated into a variety of courses as well as explore different ways to include FOSS into a course of their choosing.<br />
|prerequisites=<br />
An understanding of the course in which students will be involved in a FOSS project.<br />
|objectives=<br />
# List a variety of activities and different ways to contribute to FOSS projects beyond code, <br />
# Identify activities within a FOSS project you are interested in including in a course, <br />
# Identify activities or topics within your course where you think FOSS could fit.<br />
|process skills=<br />
}}<br />
<br />
=== Background ===<br />
<br />
When many people think about including FOSS in a class, they are typically thinking of one of two things:<br />
# Finding an artifact from the FOSS project such as a code segment that provides the base for study within the classroom (e.g., code review), or <br />
# Making a code contribution to the project by fixing a bug or making an enhancement.<br />
However, there are myriad different activities based on FOSS as well as ways of contributing to FOSS projects that go beyond coding. The purpose of this activity is to explore some of the other ways to introduce students to and/or involve students in FOSS projects.<br />
<br />
Note that the goal of this activity is to get a general idea of appropriate activities and things that you could do in class. It is not expected that you have a complete set of assignments or possibly even one complete assignment by the end of this activity. But by the end you should have an idea of some possibilities of where you could use activities with your course(s). <br />
<br />
=== Directions ===<br />
<br />
# Let's start by observing some of the different activities and ways to contribute. <br />
## Read Andy Lester's [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]. Andy does a great job of identifying and ameliorating roadblocks for newbies. <br />
## Read Craig Buchek's [http://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ great list of ways to contribute other than code]. <br />
## Read through the list of activities on the [[50 Ways to be a FOSSer]] page. <br />
# Rather than reinvent the wheel, lets explore some of the existing materials based on student involvement in FOSS.Read through the following collection of resources.<br />
## This wiki has a set of [[:Category:Learning Activity|Learning Activities]], most of which are introductory. This learning activity itself is part of that set. You'll find it in the [[:Category:POSSE|POSSE]] sub-category. <br />
## TeachingOpenSource has a [http://teachingopensource.org/all-teaching-materials/ Teaching Materials Catalog] that contains examples of courses and a few individual assignments. <br />
<!--## There is an [http://www.xcitegroup.org/softhum/doku.php?id=f:wnecsefa10 case study] of a software engineering course where students make contributions to HFOSS projects. The course used a series of [http://www.xcitegroup.org/softhum/doku.php?id=f:templates document templates and rubrics]. --><br />
## Seneca College has a [http://zenit.senecac.on.ca/wiki/index.php/Main_Page Center for Open Source Technology] that has links to courses that utilize FOSS.<br />
## Rensselaer Polytechnic Institute also has a [https://rcos.io/ Center for Open Source Software].<br />
# Lets turn our attention to your HFOSS project of interest:<br />
## Identify activities or topics that you are interested in within your HFOSS project of interest. This can be a rough list and can serve as the basis for identifying possible class activities/topics.<br />
# Let's turn our attention to your own course. <br />
## Now that you have an idea of the possible types of activities or topics, identify one or two that you think would fit in your class. These do not need to be polished. This can be a rough list of ideas.<br />
## In your reading, did you find existing materials? If so, describe how would you modify them to fit your class? <br />
## If you did not find existing materials, summarize the activity in a sentence or two.<br />
## Post the activity to your wiki page. Note that you may end up identifying more activities than you can use in a single class. Think big!<br />
<br />
=== Deliverables ===<br />
<br />
POSSE: On your foss2serve user wiki page, a section describing the course and identifying one or two possible activities that students can complete as part of the course.<br />
<br />
= Notes for Instructors =<br />
<br />
The remaining sections of this document are intended for the instructor. <br />
They are not part of the learning activity that would be given to students.<br />
<br />
=== Assessment ===<br />
<br />
* How will the activity be graded?<br />
* How will learning will be measured?<br />
* Include sample assessment questions/rubrics.<br />
<br />
{| class="wikitable"<br />
! Criteria<br />
! Level 1 (fail)<br />
! Level 2 (pass)<br />
! Level 3 (good)<br />
! Level 4 (exceptional)<br />
|-<br />
| '''The purpose of the project'''<br />
| <br />
| <br />
|<br />
|<br />
<br />
|-<br />
| '''Why the project is open source'''<br />
| <br />
| <br />
| <br />
| <br />
<br />
|}<br />
<br />
=== Comments ===<br />
<br />
* What should the instructor know before using this activity?<br />
* What are some likely difficulties that an instructor may encounter using this activity?<br />
<br />
{{Learning Activity Info<br />
|acm unit=<br />
|acm topic=<br />
|difficulty=<br />
|time=<br />
60-90 minutes<br />
|environment=<br />
Access to Internet/Web and web browser.<br />
|author=<br />
|source=<br />
|license=<br />
{{License CC BY SA}}<br />
}}<br />
<br />
=== Suggestions for Open Source Community ===<br />
<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
[[Category:Instructor Activities]]</div>Bmorganhttp://foss2serve.org/index.php/Stage2_GroupsStage2 Groups2018-04-29T17:09:27Z<p>Bmorgan: </p>
<hr />
<div>__NOTOC__<br />
<br />
='''Instructions:''' =<br />
During POSSE Stage 2, we will do a variety of small group exercises. To help organize the small groups, please sign up for one project and one course by entering your name below. We will pick projects based on available facilitator coverage and attendee interest.<br />
<br />
<br />
== Projects ==<br />
<br />
=== [https://www.ushahidi.com/ Ushahidi] ===<br />
* <Name><br />
<br />
=== [https://developer.mozilla.org/en-US/docs/Tools Mozilla Developer Tools Accessibility] ===<br />
* <Name><br />
<br />
=== [https://www.sakaiproject.org/ Sakai Accessibility] ===<br />
* <Name><br />
<br />
=== Note that the projects below are less likely to be covered in this POSSE ===<br />
<br />
=== [https://developers.google.com/blockly/ Blockly] ===<br />
* <Name><br />
<br />
=== [http://openmrs.org/ OpenMRS] ===<br />
* <Name><br />
<br />
=== [https://asqatasun.org/ Asqatasun] ===<br />
* <Name><br />
<br />
=== [http://mifos.org/ Mifos] ===<br />
* <Name><br />
<br />
=== [https://sahanafoundation.org/ Sahana] ===<br />
* <name><br />
<br />
== Courses ==<br />
We know that undergraduate curriculum structure varies some across institutions, but do what you can to pick from the general course categories below.<br />
<br />
=== Introductory Programming I ===<br />
A first course for computing majors; typically with no computing course pre-requisites<br />
* <Name><br />
<br />
=== Introductory Programming II/Data Structures ===<br />
A second course for computing majors<br />
* <Name><br />
<br />
=== Software Engineering/Capstone ===<br />
An advanced undergraduate course for computing majors; often involves a team project<br />
* <Name><br />
<br />
=== Stand-alone HFOSS/Openness ===<br />
An elective course that might be targeted at computing majors or non-majors; covers broader concepts of open source<br />
* <Name><br />
<br />
=== Other course (include the name of the course) ===<br />
* <Name><br />
[[Category:POSSE]]</div>Bmorganhttp://foss2serve.org/index.php/File:GitHubRepSize.pngFile:GitHubRepSize.png2018-04-29T17:04:26Z<p>Bmorgan: uploaded a new version of &quot;File:GitHubRepSize.png&quot;</p>
<hr />
<div>Image for addons for Firefox</div>Bmorganhttp://foss2serve.org/index.php/Project_Evaluation_(Activity)Project Evaluation (Activity)2018-04-29T16:15:11Z<p>Bmorgan: /* Walk through of an evaluation of the OpenMRS project */</p>
<hr />
<div>__NOTOC__<br />
<br />
{{Learning Activity Overview<br />
|title=<br />
Project Evaluation<br />
|overview= <br />
This activity provides a guided approach to evaluating an HFOSS project for someone trying to pick a project to which they will contribute. The activity is designed with particular attention to instructors who need to identify an HFOSS project that they will use in a class. The characteristics evaluated include the pattern of contributions, pattern of commits, programming languages used, and more. This activity uses OpenMRS as a sample project to evaluate. <br />
|prerequisites=<br />
* Completion of [[FOSS Field Trip (Activity)]] or an understanding of GitHub and OpenHub <br />
* Have Google Chrome installed<br />
* Understanding of the course in which an HFOSS project will be used.<br />
|objectives=<br />
* Identify HFOSS projects that are good candidates for new contributors<br />
|process skills= Assessment, Critical Thinking<br />
}}<br />
<br />
=== Background ===<br />
Not all projects are equally good for someone wanting to become a contributor. Some projects just don't welcome new contributors, or are not well organized to support getting new people up to speed. Other projects are welcoming to new contributors and provide clear pathways to join the community. Anyone considering becoming a contributor to a project should have some idea what to look for in evaluating whether a project is a good choice for becoming a contributor. While these evaluation criteria are not foolproof, they at least provide a starting point and framework of things to consider.<br />
<br />
=== Directions ===<br />
<br />
==== Walk through of an evaluation of the OpenMRS project ====<br />
<br />
There are many criteria that should be looked at when determining if a project is appropriate to use in your class. These criteria are prioritized and explored below. The [http://foss2serve.org/index.php/Project_Evaluation_Rubric_(Activity) Project Evaluation Rubric] contains instructions for each criterion and directions on scoring criteria. Place a copy of the Project Evaluation Rubric on your wiki page. Include your findings (notes and the answers to the below questions) in your copy of the rubric, along with your scores for each. <br><br><br />
<br />
'''Licensing''' - An important first step is to identify the license used by the project. An open source project must specify that others are free to use it, redistribute it, change it, and redistribute modified versions too. An extensive list of open source licenses can be found at https://opensource.org/licenses/alphabetical. A list of free software licenses can be found at https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses<br />
* Go to the OpenMRS core repository (https://github.com/openmrs/openmrs-core). On the repository page, click on the "< > Code" tab below the repository name. Look at the information line below the tabs for a license name (see below image). Note: if the license does not appear here, or if a project is not on GitHub, look at the top level files in the repository for a license file.<br />
* Does OpenMRS use an OSI approved open source license? Enter your findings in the rubric.<br />
[[File:ProjEval-Img1.jpg|600px|thumb|center]] <br />
'''Language''' - The language(s) used in the project is an essential consideration for your students. If the project is written in a language(s) that your students are already familiar with, or better yet, well versed in, this is one less hurdle to overcome.<br />
* Click on the language details bar (see above image). Record the top three languages used and the percentage for each.<br />
'''Activity''' - To support student participation, a project should be reasonably active. Number of commits can be used as an indicator of activity. Little to no activity over a year, for example, may indicate that the project is dead, or mature and not being actively developed. <br />
* Click the "Insights" tab then select "Commits"<br />
* If we define "Active" as meaning that a majority of the weeks in a given quarter have commits, determine whether each quarter was active over the last year and place your findings in the rubric. Note: since the definition of "active" is approximate, assess each quarter at a glance rather than by actual count of commits.<br />
'''Number of contributors''' - A common fossism states that "It's all about community," so a suitable project should have an active user community. The community members are great resources for both faculty and students as they begin to learn about a new project, its culture, and norms. <br />
* Click the "< > Code" tab. The number of contributors is listed above the language details bar. Determine how many contributors there are to the OpenMRS core project and enter your findings in the rubric.<br />
'''Size''' - The size of the project is likely to be a factor depending on the level of your students. A large project that is built using many various technologies is likely to seem overwhelming to a CS2 student, for example, but may be a perfect fit for a senior capstone course. A simple first step is to determine how large the project is, additional research could be done to ascertain complexity. By default, Github does not provide information about how many lines of code there are in a repository or its size. You can however install an extension for Google Chrome and for Mozilla Firefox that will display the size(not all versions of Google Chrome have this extension). Follow the instructions below to install the extension.<br />
Google Chrome<br />
# Click the “Customize and control Google Chrome” button (see 1st image below)<br />
# Click “More tools”<br />
# Click “Extensions”<br />
# Scroll down and click “Get more extensions” <br />
# Search for “GitHub Repository Size”<br />
<br />
Mozilla Firefox<br />
# Click the “Open Menu” button (see 2nd image below)<br />
# Click “Add-ons”<br />
# Search should be the tab opened. Make sure that the "Available Add-ons" radio button is chosen.<br />
# Search for “GitHub Repository Size”<br />
<br />
* You should now see the repository size next to license type. Record the size in the rubric.<br />
[[File:ProjEval-Img2.jpg|600px|thumb|center]]<br />
<br />
[[File:GitHubRepSize.png|600px|thumb|center]] <br />
'''Issue tracker''' - The issue tracker can provide insight into the health of a project. An active issue tracker should highlight issues that clients/developers have logged as well as an indication that these issues are being addressed. <br />
* Click "Issues" (note: this should appear next to "< > Code"; if you do not see this tab, then there are no issues logged in Github). OpenMRS uses a third-party issue tracker - click the link to openmrs.org located near the top of the repository page, scroll to the bottom and click the "OpenMRS Issue Tracking" link. Scroll to the table labeled "Two Dimensional Filter Statistics: All JIRA Tickets" located near the bottom of the page. Provide answers to the following in the rubric.<br />
# How many open (for OpenMRS look at "ready for work") issues are there? <br />
# How many closed issues are there?<br />
# When was the fifth issue opened (for OpenMRS look at the "ready for work" issues)?<br />
# Based on browsing the table, and clicking on some of the table cells, assess whether issues are actively being added and resolved <br />
'''New contributor''' - The project should appear welcoming to new contributors. Some clear examples of this would be links to getting started pages or information on ways to become involved. These pages, in turn, should include additional detail about '''how''' to become involved, as well as information about '''how''' to connect with the community.<br />
* Browse the repository and associated links, is there any indication that the project welcomes new contributors? Indicate which of the following are present and provide links in the rubric. Note: for OpenMRS you will find that the link at the top to openmrs.org and the link toward the bottom of the repository page to the OpenMRS wiki quite useful!<br />
# Are there instructions for downloading and installing the development environment?<br />
# Are communication mechanisms, such as IRC, list serves, you can join, meeting notices, etc. apparent?<br />
# Is there a discussion platform? If so, how recent are the responses?<br />
# Is there Web presence? This might include information about the project, how to get started as a developer, links to blogs, links to IRC logs, links to pages that contain information about coding standards and the code submission process.<br />
'''Community norms''' - The way in which community members interact with one another is equally important, especially for student involvement. You do not want to point students to a project that advocates or permits lewd and unprofessional behavior.<br />
* Some projects provide a "Code of Conduct", yet others do not. It it quite possible that you will find the code of conduct more quickly by doing a Google search. For OpenMRS you should look in the "Developer Guide" (link along the left side in the OpenMRS wiki) and then choose "Conventions"<br />
* You should also review some actual communications to determine if there any indications of rude or inappropriate behavior. This could be quite time consuming since you would first have to determine the type of communication typically used by community members and then locate and review the appropriate artifacts. For OpenMRS, click the "TALK" link at the top of the OpenMRS wiki page and review the communications that occurred for two of the topics. Choose two that have at least 5 members and 15 or more replies.<br />
* Record the following in the rubric.<br />
# Provide three observations about the OpenMRS Code of Conduct.<br />
# Provide three observations about the type of communication that occurred between community members on TALK. Is there any indication of rude or inappropriate behavior?<br />
'''User base''' - A project will not thrive without a core user-base. The user-base consists of clients, people who use the product on a day-to-day basis. They provide the development team with necessary feedback about the project, what works, what doesn't and what new features they might like to see. If no one is using the product then developers are likely to abandon it. Browse the repository and related links.<br />
* In the rubric record your answers to the following.<br />
# Does there appear to be a user base?<br />
# Are there instructions for downloading and setting up the software for use by clients?<br />
# Are there instructions for how to use the software?<br />
<br />
=== Deliverables ===<br />
<br />
POSSE Participants: On your user wiki page, create a section that contains the Project Evaluation rubric describing your evaluation of OpenMRS as a suitable project for your course.<br />
<br />
= Notes for Instructors =<br />
<br />
The remaining sections of this document are intended for the instructor. They are not part of the learning activity that would be given to students.<br />
<br />
=== Assessment ===<br />
<br />
* For a more introductory class, assessment can be based on simply answering the question included above for evaluating OpenMRS. This generally requires nothing more than being able to point and click and record the correct information. Students will get a simple view of evaluation in one context<br />
* For more advanced students, some possible extensions would include:<br />
** Providing the activity as shown above, but having them do an evaluation for another HFOSS project, perhaps one not on GitHub<br />
** Having students assess several HFOSS projects<br />
** Adding additional assessment questions that require interpretation or comparison of data for various criteria<br />
** This particular activity can be the basis for a larger discussion or reflection about the general problem of product evaluation, selection, and comparison. Those issues are relevant whether the product is FOSS, proprietary, or developed in-house.<br />
** This activity could also prompt discussion of measurement problems including qualitative vs. quantitative measures, development of frameworks for evaluation, and weighting of criteria to reach an overall evaluation conclusion<br />
<br />
The table below provides an outline of a rubric reflecting the recommended evaluation criteria.<br />
<br />
{| border="1" class="wikitable"<br />
! Criteria<br />
! Level 1 (fail)<br />
! Level 2 (pass)<br />
! Level 3 (good)<br />
! Level 4 (exceptional)<br />
|-<br />
| '''Licensing'''<br />
| <br />
| <br />
|<br />
|<br />
<br />
|-<br />
| '''Languages'''<br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| '''Activity'''<br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| '''Contributors'''<br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| '''Issue Tracker'''<br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| '''New Contributor'''<br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| '''Norms'''<br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| '''Client Base'''<br />
| <br />
| <br />
| <br />
| <br />
<br />
|}<br />
<br />
=== Comments ===<br />
<br />
* The criteria defined above are general, but the specific ways of evaluating each criterion will vary by project. OpenMRS provides a good example for evaluating each criterion for projects on GitHub. Projects on other forges will require different approaches to evaluate many of the criteria.<br />
* There tend to be similarities in the way HFOSS projects are structured. If you repeat this evaluation for a series of candidate projects, it gets easier to do the evaluation quickly. The situation is similar to the time it takes to learn a first or second programming language vs a sixth or seventh programming language. After doing a few, you know what to look for.<br />
<br />
=== Variants and Adaptations ===<br />
<br />
[https://github.com/ChrisMurphyOnline/open-source-software-development-course/blob/master/activities/foss-evaluation-activity.txt POGIL-style combined FOSS Field Trip and Project Evaluation] used by [[User:Cmurphy|Chris Murphy]] in his [[FOSS Course, UPenn, Murphy]].<br />
<br />
=== Additional Information ===<br />
<br />
* Explore this list of [[HFOSS Projects]] that may be of interest.<br />
* Read the [http://foss2serve.org/images/foss2serve/a/ac/Evaluating_FOSS_Projects.docx SIGCSE paper on evaluating FOSS projects]<br />
* Watch these videos introducing the FOSS project evaluation criteria:<br />
*# [http://youtu.be/MAGet2D5o2c Mission critical criteria]<br />
*# [http://youtu.be/e4lnIXjqczU Secondary criteria]<br />
* Other sources that may help you select a project include:<br />
** [https://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html How to Tell if a FLOSS Project is Doomed to Fail] or a summarized version: [https://opensource.com/life/15/7/why-your-open-source-project-failing Why your open source project is failing]<br />
** [http://producingoss.com/ Producing Open Source Software (2017)] by Karl Fogel is a great reference for many topics. Chapter 2, Getting Started, discusses things a project should address to be successful. That chapter can also be read as a checklist for things a project should have completed if you are considering being a contributor.<br />
<br />
{{Learning Activity Info<br />
|acm unit=<br />
SE/Software Project Management, SP/Professional Ethics, SP/Intellectual Property, SP/Professional Communication<br />
|acm topic=<br />
* Project Management<br />
* Exposure to the idea that a project has a code of conduct<br />
* Exposure to the idea that licensing of an open source project is essential<br />
* Professional communication and exposure to communication and collaboration tools<br />
|difficulty=<br />
Easy<br />
|time=<br />
60-90 minutes<br />
|environment=<br />
* Access to Internet/Web and web browser<br />
* [[Media:Evaluating_FOSS_Projects.docx | SIGCSE paper on evaluating FOSS projects]]<br />
* [http://www.foss2serve.org/images/foss2serve/0/0c/Blank_Evaluation_Template.xlsx Blank evaluation template referred to in the SIGCSE paper]<br />
|author=<br />
Darci Burdge, Greg Hislop, Michele Purcell<br />
|source=<br />
|license=<br />
{{License CC BY SA}}<br />
}}<br />
<br />
=== Suggestions for Open Source Community ===<br />
None at this time.<br />
<br />
<br />
[[Category:Instructor Activities]]<br />
[[Category:Learning Activity]]<br />
[[Category:Use and Evaluate]]<br />
[[Category: Good Draft]]</div>Bmorganhttp://foss2serve.org/index.php/File:GitHubRepSize.pngFile:GitHubRepSize.png2018-04-29T16:13:58Z<p>Bmorgan: uploaded a new version of &quot;File:GitHubRepSize.png&quot;: Smaller version of the image</p>
<hr />
<div>Image for addons for Firefox</div>Bmorganhttp://foss2serve.org/index.php/File:GitHubRepSize.pngFile:GitHubRepSize.png2018-04-29T15:55:55Z<p>Bmorgan: Image for addons for Firefox</p>
<hr />
<div>Image for addons for Firefox</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-28T02:20:41Z<p>Bmorgan: </p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [[File:Intro_to_Wiki.docx|Wiki Assignment]]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|[[File:IRCWeeklyMeetings.docx|Team IRC meeting]]<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [[File:BlogAssignment.docx|Blog activity]] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [[File:BugTrackerAssn.docx|Bug-Tracker Activity]]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [[File:GitAssn.docx|Git Activity]]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [[File:GettingStartedwithOpenMRS.docx|Getting Started OpenMRS]]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [[File:ModuleAssignment.docx|Create your first module]]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [[File:DocumentationandTranslation.docx|Documentation and Translation]]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [[File:IntroductoryTicket.docx|Work on a Ticket]] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [[File:ContributionPath.docx|Contribution Path]]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| [[File:FinalWritingPrompts.docx|Final Reflection]]<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/File:FinalWritingPrompts.docxFile:FinalWritingPrompts.docx2018-04-28T02:20:14Z<p>Bmorgan: </p>
<hr />
<div></div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-28T02:18:46Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [[File:Intro_to_Wiki.docx|Wiki Assignment]]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|[[File:IRCWeeklyMeetings.docx|Team IRC meeting]]<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [[File:BlogAssignment.docx|Blog activity]] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [[File:BugTrackerAssn.docx|Bug-Tracker Activity]]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [[File:GitAssn.docx|Git Activity]]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [[File:GettingStartedwithOpenMRS.docx|Getting Started OpenMRS]]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [[File:ModuleAssignment.docx|Create your first module]]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [[File:DocumentationandTranslation.docx|Documentation and Translation]]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [[File:IntroductoryTicket.docx|Work on a Ticket]] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [[File:ContributionPath.docx|Contribution Path]]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/File:GettingStartedwithOpenMRS.docxFile:GettingStartedwithOpenMRS.docx2018-04-28T02:16:12Z<p>Bmorgan: </p>
<hr />
<div></div>Bmorganhttp://foss2serve.org/index.php/File:ModuleAssignment.docxFile:ModuleAssignment.docx2018-04-28T02:12:37Z<p>Bmorgan: </p>
<hr />
<div></div>Bmorganhttp://foss2serve.org/index.php/File:IntroductoryTicket.docxFile:IntroductoryTicket.docx2018-04-28T02:11:54Z<p>Bmorgan: </p>
<hr />
<div></div>Bmorganhttp://foss2serve.org/index.php/File:DocumentationandTranslation.docxFile:DocumentationandTranslation.docx2018-04-28T02:11:34Z<p>Bmorgan: </p>
<hr />
<div></div>Bmorganhttp://foss2serve.org/index.php/File:ContributionPath.docxFile:ContributionPath.docx2018-04-28T02:07:11Z<p>Bmorgan: </p>
<hr />
<div></div>Bmorganhttp://foss2serve.org/index.php/File:BlogAssignment.docxFile:BlogAssignment.docx2018-04-28T01:42:24Z<p>Bmorgan: </p>
<hr />
<div></div>Bmorganhttp://foss2serve.org/index.php/File:BugTrackerAssn.docxFile:BugTrackerAssn.docx2018-04-28T01:39:55Z<p>Bmorgan: Bug Tracker assignment.</p>
<hr />
<div>Bug Tracker assignment.</div>Bmorganhttp://foss2serve.org/index.php/File:GitAssn.docxFile:GitAssn.docx2018-04-28T01:39:25Z<p>Bmorgan: Assignment to get familiar with Git.</p>
<hr />
<div>Assignment to get familiar with Git.</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-28T01:26:16Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [[File:Intro_to_Wiki.docx|Wiki Assignment]]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|[[File:IRCWeeklyMeetings.docx | Team IRC meeting]]<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-28T01:15:49Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [[File:Intro_to_Wiki.docx|Wiki Assignment]]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|First [[File:IRCWeeklyMeetings.docx | Team IRC meeting]]<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-28T01:15:15Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [[File:Intro_to_Wiki.docx|Wiki Assignment]]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|First [File:IRCWeeklyMeetings.docx|Team IRC meeting]<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-28T01:14:30Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [[File:Intro_to_Wiki.docx|Wiki Assignment]]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|First [File:IRCWeeklyMeetings.docx | Team IRC meeting]<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/File:IRCWeeklyMeetings.docxFile:IRCWeeklyMeetings.docx2018-04-28T01:13:30Z<p>Bmorgan: This is an assignment for group weekly IRC meetings. There is a reference to uploading to Moodle, the LMS I use. Replace with your submission directions for your course.</p>
<hr />
<div>This is an assignment for group weekly IRC meetings. There is a reference to uploading to Moodle, the LMS I use. Replace with your submission directions for your course.</div>Bmorganhttp://foss2serve.org/index.php/File:IntroToIRC.docxFile:IntroToIRC.docx2018-04-27T20:28:52Z<p>Bmorgan: Foss2serve Intro to IRC</p>
<hr />
<div>Foss2serve Intro to IRC</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-27T20:26:10Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [[File:Intro_to_Wiki.docx|Wiki Assignment]]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|First [http://www.wou.edu/~morganb/HFOSS%20course/IRC%20team%20meeting.pdf Team IRC meeting] – wiki editing<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-27T20:17:14Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [[File:Intro_to_Wiki.docx Wiki Assignment]]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|First [http://www.wou.edu/~morganb/HFOSS%20course/IRC%20team%20meeting.pdf Team IRC meeting] – wiki editing<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-27T20:16:47Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [[File:Intro_to_Wiki.docx]]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|First [http://www.wou.edu/~morganb/HFOSS%20course/IRC%20team%20meeting.pdf Team IRC meeting] – wiki editing<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-27T20:15:34Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [File:Intro_to_Wiki.docx]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|First [http://www.wou.edu/~morganb/HFOSS%20course/IRC%20team%20meeting.pdf Team IRC meeting] – wiki editing<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-27T20:08:46Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [File:Intro_to_Wiki.docx Wiki Assignment]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|First [http://www.wou.edu/~morganb/HFOSS%20course/IRC%20team%20meeting.pdf Team IRC meeting] – wiki editing<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorganhttp://foss2serve.org/index.php/HFOSS_Course,_Western_Oregon,_MorganHFOSS Course, Western Oregon, Morgan2018-04-27T19:52:18Z<p>Bmorgan: /* Lesson Plan */</p>
<hr />
<div>This page has the activities and assignments for a 10 week course (the 11th week is finals) on participation in a FOSS project.<br />
<br />
=== Overview ===<br />
<br />
{{Course Overview<br />
|course= <br />
HFOSS Course<br />
|institution=<br />
Western Oregon University<br />
|instructors=<br />
Becka Morgan<br />
|offerings=<br />
|overview= <br />
|students=<br />
|prerequisites=<br />
|infrastructure=<br />
}}<br />
<br />
== Lesson Plan ==<br />
{| class="wikitable" cellpadding="10" ! style="text-align:center; color:purple"<br />
! Week<br />
! Assignment/Activity<br />
! Homework<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 1<br />
| Intro to Class/(HF)OSS – Pre test evaluation<br />
| [http://firstmonday.org/ojs/index.php/fm/article/view/578/499 The Cathedral and the Bazaar]<br />
<br />
[https://wiki.openmrs.org/display/docs/Home OpenMRS Wiki:Read through the Welcome and Introduction to OpenMRS pages and links contained on each page]<br />
|- style="text-align:left; color:black"<br />
|Intro to wiki**Focus on OpenMRS wiki<br />
*[https://wiki.openmrs.org/display/docs/Welcome Welcome] <br />
*[https://wiki.openmrs.org/display/docs/Introduction+to+OpenMRS Introduction to OpenMRS] <br />
*[https://wiki.openmrs.org/display/docs/Implementer+Documentation Implementer Documentation] <br />
*[https://wiki.openmrs.org/display/docs/User+Guide User Guide] <br />
Introduce yourself on [https://talk.openmrs.org/t/welcome-please-introduce-yourself/32 OpenMRS Talk]<br />
| [File:Intro to Wiki.docx Wiki Assignment]<br />
|- style="text-align:left; color:black"<br />
| Intro to IRC <br />
* open the OpenMRS IRC<br />
* create an IRC channel in class and have students chat<br />
Form teams /Set up team IRC channels and nicks/Determine group meeting schedule outside of class (via IRC, logs to be turned in)<br />
|First [http://www.wou.edu/~morganb/HFOSS%20course/IRC%20team%20meeting.pdf Team IRC meeting] – wiki editing<br />
[http://www.ted.com/playlists/13/open_source_open_world.html Ted Talks]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 2<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Blog%20Assignment.pdf Blog activity] (Add a page to my Wiki and, using wiki markup, add a link to their blog)<br />
| [http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/ 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star]<br />
[https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/ How to Contribute to Open Source Without Coding]<br />
|- style="text-align:left; color:black"<br />
| FOSS field trip <br />
[https://www.openhub.net/ Black Duck Open Hub] - find projects of interest <br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 5 and 6]<br />
[http://www.producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers] <br />
[https://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Bug%20Tracker%20Assn.pdf Bug-Tracker Activity]<br />
| Watch videos about git<br />
[http://git-scm.com/video/what-is-version-control Video One]<br />
[http://git-scm.com/video/what-is-git Video Two]<br />
[http://git-scm.com/video/get-going Video Three]<br />
[http://git-scm.com/video/quick-wins Video Four]<br />
Complete tutorial then take a screen shot <br />
of the last screen of the tutorial to turn in:<br />
[http://try.github.io/levels/1/challenges/1 TUTORIAL]<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 3<br />
| Source Code Management/Control [http://www.wou.edu/~morganb/HFOSS%20course/Git%20Assn.pdf Git Activity]<br />
| BLOG (Ongoing Blog about experiences)<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 7 and 8]<br />
|- style="text-align:left; color:black"<br />
| Wiki for OpenMRS read through:<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
| Continue Reading<br />
•[https://wiki.openmrs.org/display/docs/Developer+Guide Developer Guide] <br />
•[https://wiki.openmrs.org/display/docs/Troubleshooting Troubleshooting] <br />
•[https://wiki.openmrs.org/display/docs/Technical+Road+Map Technical Road Map] <br />
•[https://wiki.openmrs.org/display/docs/Modules Modules] <br />
•[https://wiki.openmrs.org/display/docs/Design Design] <br />
•[https://wiki.openmrs.org/display/docs/Documentation+Playground Documentation Playground]<br />
|- style="text-align:left; color:black"<br />
| Catch up and Reflection<br />
| Read all for contribute links:<br />
http://openmrs.org/help/<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 9]<br />
|- style="text-align:left; color:black"<br />
| 4 & 5<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Getting%20Started%20with%20OpenMRS.pdf Getting Started OpenMRS]<br />
1. Set up openMRS dev environment on lab computers or lap tops<br />
2. If using laptops duel boot Linux Mint<br />
|<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 6<br />
| rowspan="3" | [http://www.wou.edu/~morganb/HFOSS%20course/Module%20Assignment.pdf Create your first module]<br />
[http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapter 11]<br />
| [http://en.flossmanuals.net/_booki/openmrs-developers-guide/openmrs-developers-guide.pdf OpenMRS Chapters 12 – 14 +Appendices]<br />
|- style="text-align:left; color:black"<br />
|<br />
|- style="text-align:left; color:black"<br />
| https://wiki.openmrs.org/display/docs/Testing<br />
<br />
|- style="text-align:left; color:black"<br />
| rowspan="3" | 7<br />
| Testing Code<br />
[https://wiki.openmrs.org/display/docs/Generate+Test+Case+Plugin Generate a test plugin]<br />
| http://openmrs.org/help/document/<br />
http://openmrs.org/help/translate/<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Documentation%20and%20Translation.pdf Documentation and Translation]<br />
| https://wiki.openmrs.org/display/docs/Different+Types+of+OpenMRS+Developers<br />
|- style="text-align:left; color:black"<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Introductory%20Ticket.pdf Work on a Ticket] <br />
|<br />
|- style="text-align:left; color:black"<br />
| 8, 9, and 10<br />
| [http://www.wou.edu/~morganb/HFOSS%20course/Contribution%20Path.pdf Contribution Path]<br />
|<br />
|- style="text-align:left; color:black"<br />
| 11<br />
| Final Reflection<br />
|<br />
|}<br />
<br />
<br />
[[Category:Courses]]<br />
[[Category:(H)FOSS Course]]</div>Bmorgan