http://foss2serve.org/api.php?action=feedcontributions&user=Jim.huggins&feedformat=atomFoss2Serve - User contributions [en]2024-03-29T09:49:31ZUser contributionsMediaWiki 1.18.1http://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T21:49:56Z<p>Jim.huggins: </p>
<hr />
<div>__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an HFOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
At many institutions, students often enroll in a "capstone" course which requires a completion of a "big" project: a project that requires months rather than weeks to perform. Often this project involves teams of students rather than individuals, but might be performed as individuals. Often, the project is chosen arbitrarily by the instructor, and results in an artificial academic artifact at the end of the project.<br />
<br />
Students and/or faculty who desire a project with a greater practical impact might be interested in joining an HFOSS community and choosing a project that would ultimately be submitted to that community. This activities outlines a potential path to planning such a project. <br />
<br />
The project could be appropriate for individuals or teams; it could be appropriate for upper-division or lower-division students; it could be appropriate for projects of various time lengths. The plan gives room for individual faculty to customize to meet their needs.<br />
<br />
=== Directions: ===<br />
<br />
==== Step One: Learn about HFOSS ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
# [[Intro to FOSS Activity]] <br />
# [[Project Anatomy Activity]] <br />
# [[FOSS Field Trip Activity]]<br />
# [[Project Evaluation Activity]]<br />
# As needed, activities to learn about contemporary tools commonly used in FOSS communities:<br />
## Wikis: [[Wiki Activity]]<br />
## IRC: [[Intro IRC Activity]]<br />
## Blogging: [[Blog Activity]]<br />
## Bug Trackers: [[Bug Tracker Activity]]<br />
## Git: [[Git Activity]]<br />
<br />
At the conclusion of Step One, the student will meet with the academic advisor to discuss the material covered and answer any questions.<br />
<br />
==== Step Two: Select and Investigate an HFOSS Community ====<br />
<br />
The student should investigate and a select an HFOSS community in which this capstone project will be performed. <br />
<br />
After selection, the student should complete the [[Project Evaluation Activity]], in order to ensure that the HFOSS project is mature enough to support the capstone project.<br />
<br />
Upon completion of the [[Project Evaluation Activity]], the student will meet with the academic advisor to discuss the results and ensure that the selected community is mature enough to support the capstone project.<br />
<br />
<br />
==== Step Three: Prepare The Capstone Plan ====<br />
<br />
First, the student should complete the following activities in order to identify possible concrete tasks and/or deliverables that could be used within the selected HFOSS community:<br />
<br />
# [[FOSS In Courses Activity]]<br />
# [[FOSS in Courses 2]]<br />
<br />
Finally, in consultation with the academic advisor, the student should prepare the '''Final Capstone Project Design Document'''. The format for this will depend upon the particular institution, but may include many of the following items:<br />
<br />
* Project title<br />
* Faculty members involved in final review of the project<br />
* Description of the work to be performed, including:<br />
** Value of the project to the HFOSS community<br />
** Relationship of the project to institutional capstone goals<br />
** Expected deliverables<br />
* Project timeline<br />
* Relationship to the overall HFOSS project, including dependencies (if any)<br />
* Prerequisite skills needed<br />
* Literature review (if needed)<br />
* Facilities and/or equipment required<br />
<br />
=== Deliverables: ===<br />
<br />
The only deliverable is the '''Final Capstone Project Design Document''', outlined in Step Three above.<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || various<br />
|-<br />
|'''ACM Topic''' || various<br />
|-<br />
|'''Level of Difficulty''' || Medium to challenging, depending upon the project selected <br />
|-<br />
|'''Estimated Time to Completion''' || Several weeks<br />
|-<br />
|'''Materials/Environment''' || Internet access, possibly access to various common FOSS tools (outlined below)<br />
|-<br />
|'''Author''' || Jim Huggins (jhuggins@kettering.edu)<br />
|-<br />
|'''Source''' || Based on the September 2015 POSSE workshop [[POSSE 2015-09]]<br />
|-<br />
|'''License''' || Licensed CC BY-SA<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T21:31:25Z<p>Jim.huggins: </p>
<hr />
<div>__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an HFOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
==== Step One: Learn about HFOSS ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
# [[Intro to FOSS Activity]] <br />
# [[Project Anatomy Activity]] <br />
# [[FOSS Field Trip Activity]]<br />
# [[Project Evaluation Activity]]<br />
# As needed, activities to learn about contemporary tools commonly used in FOSS communities:<br />
## Wikis: [[Wiki Activity]]<br />
## IRC: [[Intro IRC Activity]]<br />
## Blogging: [[Blog Activity]]<br />
## Bug Trackers: [[Bug Tracker Activity]]<br />
## Git: [[Git Activity]]<br />
<br />
At the conclusion of Step One, the student will meet with the academic advisor to discuss the material covered and answer any questions.<br />
<br />
==== Step Two: Select and Investigate an HFOSS Community ====<br />
<br />
The student should investigate and a select an HFOSS community in which this capstone project will be performed. <br />
<br />
After selection, the student should complete the [[Project Evaluation Activity]], in order to ensure that the HFOSS project is mature enough to support the capstone project.<br />
<br />
Upon completion of the [[Project Evaluation Activity]], the student will meet with the academic advisor to discuss the results and ensure that the selected community is mature enough to support the capstone project.<br />
<br />
<br />
==== Step Three: Prepare The Capstone Plan ====<br />
<br />
First, the student should complete the following activities in order to identify possible concrete tasks and/or deliverables that could be used within the selected HFOSS community:<br />
<br />
# [[FOSS In Courses Activity]]<br />
# [[FOSS in Courses 2]]<br />
<br />
Finally, in consultation with the academic advisor, the student should prepare the '''Final Capstone Project Design Document'''. The format for this will depend upon the particular institution, but may include many of the following items:<br />
<br />
* Project title<br />
* Faculty members involved in final review of the project<br />
* Description of the work to be performed, including:<br />
** Value of the project to the HFOSS community<br />
** Relationship of the project to institutional capstone goals<br />
** Expected deliverables<br />
* Project timeline<br />
* Relationship to the overall HFOSS project, including dependencies (if any)<br />
* Prerequisite skills needed<br />
* Literature review (if needed)<br />
* Facilities and/or equipment required<br />
<br />
=== Deliverables: ===<br />
<br />
The only deliverable is the '''Final Capstone Project Design Document''', outlined in Step Three above.<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T21:30:23Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an HFOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
==== Step One: Learn about HFOSS ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
# [[Intro to FOSS Activity]] <br />
# [[Project Anatomy Activity]] <br />
# [[FOSS Field Trip Activity]]<br />
# [[Project Evaluation Activity]]<br />
# As needed, activities to learn about contemporary tools commonly used in FOSS communities:<br />
## Wikis: [[Wiki Activity]]<br />
## IRC: [[Intro IRC Activity]]<br />
## Blogging: [[Blog Activity]]<br />
## Bug Trackers: [[Bug Tracker Activity]]<br />
## Git: [[Git Activity]]<br />
<br />
At the conclusion of Step One, the student will meet with the academic advisor to discuss the material covered and answer any questions.<br />
<br />
==== Step Two: Select and Investigate an HFOSS Community ====<br />
<br />
The student should investigate and a select an HFOSS community in which this capstone project will be performed. <br />
<br />
After selection, the student should complete the [[Project Evaluation Activity]], in order to ensure that the HFOSS project is mature enough to support the capstone project.<br />
<br />
Upon completion of the [[Project Evaluation Activity]], the student will meet with the academic advisor to discuss the results and ensure that the selected community is mature enough to support the capstone project.<br />
<br />
<br />
==== Step Three: Prepare The Capstone Plan ====<br />
<br />
First, the student should complete the following activities in order to identify possible concrete tasks and/or deliverables that could be used within the selected HFOSS community:<br />
<br />
# [[FOSS In Courses Activity]]<br />
# [[FOSS in Courses 2]]<br />
<br />
Finally, in consultation with the academic advisor, the student should prepare the '''Final Capstone Project Design Document'''. The format for this will depend upon the particular institution, but may include many of the following items:<br />
<br />
* Project title<br />
* Faculty members involved in final review of the project<br />
* Description of the work to be performed, including:<br />
** Value of the project to the HFOSS community<br />
** Relationship of the project to institutional capstone goals<br />
** Expected deliverables<br />
* Project timeline<br />
* Relationship to the overall HFOSS project, including dependencies (if any)<br />
* Prerequisite skills needed<br />
* Literature review (if needed)<br />
* Facilities and/or equipment required<br />
<br />
=== Deliverables: ===<br />
<br />
The only deliverable is the '''Final Capstone Project Design Document''', outlined in Step Three above.<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T21:25:30Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an HFOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
==== Step One: Learn about HFOSS ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
# [[Intro to FOSS Activity]] <br />
# [[Project Anatomy Activity]] <br />
# [[FOSS Field Trip Activity]]<br />
# [[Project Evaluation Activity]]<br />
# As needed, activities to learn about contemporary tools commonly used in FOSS communities:<br />
## Wikis: [[Wiki Activity]]<br />
## IRC: [[Intro IRC Activity]]<br />
## Blogging: [[Blog Activity]]<br />
## Bug Trackers: [[Bug Tracker Activity]]<br />
## Git: [[Git Activity]]<br />
<br />
At the conclusion of Step One, the student will meet with the academic advisor to discuss the material covered and answer any questions.<br />
<br />
==== Step Two: Select and Investigate an HFOSS Community ====<br />
<br />
The student should investigate and a select an HFOSS community in which this capstone project will be performed. <br />
<br />
After selection, the student should complete the [[Project Evaluation Activity]], in order to ensure that the HFOSS project is mature enough to support the capstone project.<br />
<br />
Upon completion of the [[Project Evaluation Activity]], the student will meet with the academic advisor to discuss the results and ensure that the selected community is mature enough to support the capstone project.<br />
<br />
<br />
==== Step Three: Prepare The Capstone Plan ====<br />
<br />
First, the student should complete the following activities in order to identify possible concrete tasks and/or deliverables that could be used within the selected HFOSS community:<br />
<br />
# [[FOSS In Courses Activity]]<br />
# [[FOSS in Courses 2]]<br />
<br />
<br />
=== Deliverables: ===<br />
<br />
The only deliverable is the '''Final Capstone Project Design Document''', outlined in Step Three above.<br />
<br />
<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:44:47Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
==== Step One: Learn about (H)FOSS ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
# [[Intro to FOSS Activity]] <br />
# [[Project Anatomy Activity]] <br />
# [[FOSS Field Trip Activity]]<br />
# [[Project Evaluation Activity]]<br />
# As needed, activities to learn about contemporary tools commonly used in FOSS communities:<br />
## Wikis: [[Wiki Activity]]<br />
## IRC: [[Intro IRC Activity]]<br />
## Blogging: [[Blog Activity]]<br />
## Bug Trackers: [[Bug Tracker Activity]]<br />
## Git: [[Git Activity]]<br />
<br />
At the conclusion of Step One, the student will meet with the academic advisor to discuss the material covered and answer any questions.<br />
<br />
==== Step Two: Select and Investigate an (H)FOSS Community ====<br />
<br />
The student should investigate and a select an (H)FOSS community in which this capstone project will be performed. <br />
<br />
After selection, the student should complete the [[Project Evaluation Activity]], in order to ensure that the (H)FOSS project is mature enough to support the capstone project.<br />
<br />
Upon completion of the [[Project Evaluation Activity]], the student will meet with the academic advisor to discuss the results and ensure that the selected community is mature enough to support the capstone project.<br />
<br />
<br />
==== Step Three: Prepare The Capstone Plan ====<br />
<br />
=== Deliverables: ===<br />
<br />
==== HFOSS Field Trip Report ====<br />
==== Final Capstone Project Proposal ====<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:39:18Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
==== Step One: Learn about (H)FOSS ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
# [[Intro to FOSS Activity]] <br />
# [[Project Anatomy Activity]] <br />
# [[FOSS Field Trip Activity]]<br />
# [[Project Evaluation Activity]]<br />
# As needed, activities to learn about contemporary tools commonly used in FOSS communities:<br />
## Wikis: [[Wiki Activity]]<br />
## IRC: [[Intro IRC Activity]]<br />
## Blogging: [[Blog Activity]]<br />
## Bug Trackers: [[Bug Tracker Activity]]<br />
## Git: [[Git Activity]]<br />
<br />
==== Step Two: Select and Investigate an (H)FOSS Community ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
<br />
==== Step Three: Prepare The Capstone Plan ====<br />
<br />
=== Deliverables: ===<br />
<br />
==== HFOSS Field Trip Report ====<br />
==== Final Capstone Project Proposal ====<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:37:48Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
==== Step One: Learn about (H)FOSS ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
# [[Intro to FOSS Activity]] <br />
# [[Project Anatomy Activity]] <br />
# [[FOSS Field Trip Activity]]<br />
# [[Project Evaluation Activity]]<br />
# As needed, activities to learn about contemporary tools commonly used in FOSS communities:<br />
## Wikis: [[Introduction to Wikis]]<br />
## IRC: [[Introduction to IRC]]<br />
## Blogging: [[Blogging Activity]]<br />
## Bug Trackers: [[Bug Tracker Activity]]<br />
## Git: [[Git Activity]]<br />
<br />
==== Step Two: Select and Investigate an (H)FOSS Community ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
<br />
==== Step Three: Prepare The Capstone Plan ====<br />
<br />
=== Deliverables: ===<br />
<br />
==== HFOSS Field Trip Report ====<br />
==== Final Capstone Project Proposal ====<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:25:50Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
==== Step One: Learn about (H)FOSS ====<br />
<br />
Complete the following Foss2Serve Learning Activities:<br />
<br />
# [[Intro to FOSS Activity]]<br />
<br />
<br />
==== Step Two: Investigate an (H)FOSS Community ====<br />
==== Step Three: Prepare The Capstone Plan ====<br />
<br />
=== Deliverables: ===<br />
<br />
==== HFOSS Field Trip Report ====<br />
==== Final Capstone Project Proposal ====<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:23:14Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
==== Step One: Learn about (H)FOSS ====<br />
==== Step Two: Investigate an (H)FOSS Community ====<br />
==== Step Three: Prepare The Capstone Plan ====<br />
<br />
=== Deliverables: ===<br />
<br />
==== HFOSS Field Trip Report ====<br />
==== Final Capstone Project Proposal ====<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:22:14Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
# '''Learn about (H)FOSS'''<br />
# '''Investigate an (H)FOSS Community'''<br />
# '''Prepare The Capstone Plan'''<br />
<br />
=== Deliverables: ===<br />
<br />
==== HFOSS Field Trip Report ====<br />
==== Final Capstone Project Proposal ====<br />
<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:21:09Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
# '''Learn about (H)FOSS'''<br />
# '''Investigate an (H)FOSS Community'''<br />
# '''Prepare The Capstone Plan'''<br />
<br />
=== Deliverables: ===<br />
<br />
# '''Final Capstone Project Proposal'''<br />
<br />
asdflk asdflkj<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:19:41Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
# '''Learn about (H)FOSS'''<br />
# '''Investigate an (H)FOSS Community'''<br />
# '''Prepare The Capstone Plan'''<br />
<br />
=== Deliverables: ===<br />
<br />
# '''Final Capstone Project Proposal'''<br />
<br />
=== Assessment: ===<br />
<br />
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.<br />
<br />
=== Comments: ===<br />
<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:17:12Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will prepare a detailed plan for a project that demonstrates the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
<br />
<br />
<br />
=== Directions: ===<br />
<br />
# '''Learn about (H)FOSS'''<br />
# '''Investigate an (H)FOSS Community'''<br />
# '''Prepare The Capstone Plan'''<br />
<br />
=== Deliverables: ===<br />
<br />
# '''Final Capstone Project Proposal'''<br />
<br />
=== Assessment: ===<br />
How will the activity be graded?<br />
<br />
How will learning will be measured?<br />
<br />
Include sample assessment questions/rubrics.<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 />
| '''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 />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:13:01Z<p>Jim.huggins: moved Independent Capstone Project to Independent Capstone Project Design</p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will demonstrate the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
Is there background reading material?<br />
<br />
Are there other activities the student should have done first?<br />
<br />
What is the rationale for this activity?<br />
<br />
Include helpful hints to faculty here.<br />
<br />
<br />
=== Directions: ===<br />
What should the student do?<br />
<br />
<br />
=== Deliverables: ===<br />
What will the student hand in?<br />
<br />
<br />
=== Assessment: ===<br />
How will the activity be graded?<br />
<br />
How will learning will be measured?<br />
<br />
Include sample assessment questions/rubrics.<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 />
| '''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 />
What should the instructor know before using this activity?<br />
<br />
What are some likely difficulties that an instructor may encounter using this activity?<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:12:05Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS!!!'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will demonstrate the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
Is there background reading material?<br />
<br />
Are there other activities the student should have done first?<br />
<br />
What is the rationale for this activity?<br />
<br />
Include helpful hints to faculty here.<br />
<br />
<br />
=== Directions: ===<br />
What should the student do?<br />
<br />
<br />
=== Deliverables: ===<br />
What will the student hand in?<br />
<br />
<br />
=== Assessment: ===<br />
How will the activity be graded?<br />
<br />
How will learning will be measured?<br />
<br />
Include sample assessment questions/rubrics.<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 />
| '''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 />
What should the instructor know before using this activity?<br />
<br />
What are some likely difficulties that an instructor may encounter using this activity?<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:11:50Z<p>Jim.huggins: </p>
<hr />
<div>'''DRAFT IN PROGRESS'''<br />
<br />
__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will demonstrate the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
Is there background reading material?<br />
<br />
Are there other activities the student should have done first?<br />
<br />
What is the rationale for this activity?<br />
<br />
Include helpful hints to faculty here.<br />
<br />
<br />
=== Directions: ===<br />
What should the student do?<br />
<br />
<br />
=== Deliverables: ===<br />
What will the student hand in?<br />
<br />
<br />
=== Assessment: ===<br />
How will the activity be graded?<br />
<br />
How will learning will be measured?<br />
<br />
Include sample assessment questions/rubrics.<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 />
| '''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 />
What should the instructor know before using this activity?<br />
<br />
What are some likely difficulties that an instructor may encounter using this activity?<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:09:53Z<p>Jim.huggins: </p>
<hr />
<div>__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Independent Capstone Project<br />
|-<br />
|'''Overview''' || The student will create a detailed plan for an independent capstone project in an (H)FOSS community<br />
|- <br />
|'''Prerequisite Knowledge''' || Basic knowledge of software development skills<br />
|-<br />
|'''Learning Objectives''' || The student will demonstrate the totality of skills required by a CS graduate.<br />
|}<br />
<br />
=== Background: ===<br />
Is there background reading material?<br />
<br />
Are there other activities the student should have done first?<br />
<br />
What is the rationale for this activity?<br />
<br />
Include helpful hints to faculty here.<br />
<br />
<br />
=== Directions: ===<br />
What should the student do?<br />
<br />
<br />
=== Deliverables: ===<br />
What will the student hand in?<br />
<br />
<br />
=== Assessment: ===<br />
How will the activity be graded?<br />
<br />
How will learning will be measured?<br />
<br />
Include sample assessment questions/rubrics.<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 />
| '''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 />
What should the instructor know before using this activity?<br />
<br />
What are some likely difficulties that an instructor may encounter using this activity?<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/Independent_Capstone_Project_DesignIndependent Capstone Project Design2016-03-02T20:06:10Z<p>Jim.huggins: initial creation</p>
<hr />
<div>__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' || Name of the activity<br />
|-<br />
|'''Overview''' || High level description of what the student will do <br />
|- <br />
|'''Prerequisite Knowledge''' || What topics and tools does the student need to know prior to beginning this activity? <br />
|-<br />
|'''Learning Objectives''' || What should the student be able to do after completing this activity?<br />
|}<br />
<br />
=== Background: ===<br />
Is there background reading material?<br />
<br />
Are there other activities the student should have done first?<br />
<br />
What is the rationale for this activity?<br />
<br />
Include helpful hints to faculty here.<br />
<br />
<br />
=== Directions: ===<br />
What should the student do?<br />
<br />
<br />
=== Deliverables: ===<br />
What will the student hand in?<br />
<br />
<br />
=== Assessment: ===<br />
How will the activity be graded?<br />
<br />
How will learning will be measured?<br />
<br />
Include sample assessment questions/rubrics.<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 />
| '''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 />
What should the instructor know before using this activity?<br />
<br />
What are some likely difficulties that an instructor may encounter using this activity?<br />
<br />
<br />
=== Additional Information: ===<br />
{| border="1"<br />
|- <br />
|'''ACM Knowledge Area/Knowledge Unit''' || What ACM Computing Curricula 2013 knowledge area and units does this activity cover? [[ACM_Body_of_Knowledge]]<br />
|-<br />
|'''ACM Topic''' || What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf<br />
|-<br />
|'''Level of Difficulty''' || Is this activity easy, medium or challenging? <br />
|-<br />
|'''Estimated Time to Completion''' || How long should it take for the student to complete the activity?<br />
|-<br />
|'''Materials/Environment''' || What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?<br />
|-<br />
|'''Author''' || Who wrote this activity? <br />
|-<br />
|'''Source''' || Is there another activity on which this activity is based? If so, please provide a link to the original resource.<br />
|-<br />
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)<br />
|}<br />
<br />
=== Suggestions for Open Source Community: ===<br />
Suggestions for an open source community member who is working in conjunction with the instructor.<br />
<br />
<br />
--------------------<br />
This work is licensed under a <br />
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]<br />
<br />
[[File:CC_license.png]]<br />
<br />
[[Category: Learning_Activity]]<br />
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]</div>Jim.hugginshttp://foss2serve.org/index.php/HFOSS_CommunitiesHFOSS Communities2015-09-12T15:45:19Z<p>Jim.huggins: /* Mifos */</p>
<hr />
<div>This page holds a list of HFOSS communities that have volunteered to participate in foss2serve activities. Please sign up below the community that you are interested in participating in.<br />
<br />
== MouseTrap ==<br />
From the MouseTrap web site: "MouseTrap is a standalone GNOME application that allows users with physical impairments to move a mouse cursor. It uses a webcam to track the motion of any object visible by the camera and moves the mouse cursor according to the path of the tracked object (a user's head, for example). Distributed with software that allows accessible mouse clicking, MouseTrap will give most physically impaired users access to the full functionality of a mouse. Our ultimate goal is to have a usable, stable solution that allows users to control their cursors just as well as someone using a mouse.<br />
<br />
MouseTrap is written in Python, based on the OpenCV library and uses image processing to translate the user's head movements into mouse events (movements, clicks) which allow users to interact with the different desktops managers and applications."<br />
<br />
The project has been worked on successfully by several different academic classes. Note that the project requires some understanding of computer vision.<br />
<br />
'''Website:''' [https://wiki.gnome.org/action/show/Projects/MouseTrap?action=show&redirect=MouseTrap]<br />
<br />
'''Foss2serve contact:''' Stoney Jackson (stoney.jackson(at)wne.edu), <br />
Heidi Ellis (ellis(at)wne.edu)<br />
<br />
'''Lanugage: ''' Varies by specific application<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
Dee Weikle dee.weikle@emu.edu<br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Stoney Jackson - Western New England University<br />
* Heidi Ellis - Western New England University<br />
<br />
== Mifos ==<br />
From SourceForge: "Mifos is an MIS purpose-built for the microfinance industry. It provides MFIs the key functionality to better serve the poor: client management, loans & savings portfolio tracking, reporting, & social performance measurement. "<br />
<br />
From the web site: " Mifos.org is a diverse community of microfinance institutions, technology professionals, business people, volunteers, and contributors.<br />
* We are guided by the vision to create and deploy technology that allows the microfinance industry to scale.<br />
* Our team and our community of users are distributed worldwide, spanning all time zones, in developing nations and developed.<br />
* We are a community that actively supports each other in the development and use of the Mifos software."<br />
<br />
'''Website:''' [http://mifos.org/ http://mifos.org/]<br />
<br />
'''Better Website:''' [https://mifosforge.jira.com/wiki/display/MDZ/Welcome+to+the+Zone Mifos Developer Zone]<br />
<br />
'''Foss2serve contact:''' Greg Hislop<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
* Nanette Veilleux<br />
* Lynn Lambert<br />
* Jim Huggins<br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
<br />
== OpenMRS ==<br />
From the website: "Open Medical Record System (OpenMRS®) was created in 2004 as a open source medical record system platform for developing countries – a tide which rises all ships. OpenMRS is a multi-institution, non-profit collaborative led by Regenstrief Institute, a world-renowned leader in medical informatics research, and Partners In Health, a Boston-based philanthropic organization with a focus on improving the lives of underprivileged people worldwide through health care service and advocacy. These teams nurture a growing worldwide network of individuals and organizations all focused on creating medical record systems and a corresponding implementation network to allow system development self reliance within resource constrained environments."<br />
<br />
'''Website:''' [http://openmrs.org/ http://openmrs.org/]<br />
<br />
'''Team Page:''' [http://foss2serve.org/index.php/TheOpenMRSTeam http://foss2serve.org/index.php/TheOpenMRSTeam]<br />
<br />
'''Getting Started:'''<br />
* General overview for developers -- [http://openmrs.org/help/developers/ http://openmrs.org/help/developers/]<br />
** Familiarize yourself with the various tools and resources - view this page only, you do not need to visit any of the pages linked from this page<br />
* Getting started book (OpenMRS Developers' Guide) -- [http://go.openmrs.org/newdev-web http://go.openmrs.org/newdev-web]<br />
** Read the information found on the following pages - these are also available as links in the main menu on the left<br />
*** Welcome to OpenMRS! - [http://en.flossmanuals.net/openmrs-developers-guide/index/ http://en.flossmanuals.net/openmrs-developers-guide/index/]<br />
*** The Need for Health IT - [http://en.flossmanuals.net/openmrs-developers-guide/the-need-for-health-it/ http://en.flossmanuals.net/openmrs-developers-guide/the-need-for-health-it/]<br />
*** Our Response - [http://en.flossmanuals.net/openmrs-developers-guide/story-of-openmrs/ http://en.flossmanuals.net/openmrs-developers-guide/story-of-openmrs/]<br />
*** OpenMRS Today - [http://en.flossmanuals.net/openmrs-developers-guide/state-of-openmrs/ http://en.flossmanuals.net/openmrs-developers-guide/state-of-openmrs/]<br />
*** Although all of the information in the Community and Technology sections is beneficial, skip it for now and proceed directly to the instructions for getting the development environment set up - [http://en.flossmanuals.net/openmrs-developers-guide/get-set-up/ http://en.flossmanuals.net/openmrs-developers-guide/get-set-up/]. Follow the instructions for doing a '''manual install''' (you will have to scroll down a bit).<br />
<br />
'''Foss2serve contact:''' Darci Burdge (<br />
<br />
=== Sign up ===<br />
* [[User:Emily.lovell|Emily Lovell]]<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Chris Murphy<br />
* Meghan Allen<br />
* Steven P. Crain<br />
<br />
== Sahana ==<br />
Sahana Eden is a flexible open source humanitarian platform with a rich feature set to provide effective solutions for critical humanitarian needs management, either prior to, or during, a crisis. Eden can be rapidly customized to adapt to existing processes and to integrate with existing systems. Eden is designed for most organizations and agencies engaged in humanitarian activities, including UN agencies, NGOs and government agencies, and provides solutions to challenges involved in resource management, information management, coordination, decision support and stakeholder communications. It is built with Python using the Web2Py framework. Sahana Eden currently supports a diverse set of humanitarian organizations, including the City of Los Angeles Emergency Management Department, the International Federation of the Red Cross (IFRC), the American Red Cross, the Helios Foundation, the UN World Food Programme, and several CERT chapters and VOAD organizations in the United States. <br />
<br />
'''Website:''' [http://sahanafoundation.org/ http://sahanafoundation.org/]<br />
<br />
'''Foss2serve contact:''' <br />
<br />
'''Language: ''' Python<br />
<br />
'''Team Page: ''' [[SahanaGroupNotes]] (Will help get you started, but may not be current.)<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Peter Bui (pnutzh4x0r)<br />
* Nannette Napier<br />
* Esmail Bonakdarian<br />
* Kiranmai Bellam<br />
* Howard Francis<br />
<br />
== Ushahidi ==<br />
From the website: "We are a non-profit tech company that specializes in developing free and open source software for information collection, visualization and interactive mapping."<br />
<br />
" "Ushahidi", which means "testimony" in Swahili, was a website that was initially developed to map reports of violence in Kenya after the post-election fallout at the beginning of 2008. Since then, the name "Ushahidi" has come to represent the people behind the "Ushahidi Platform". Our roots are in the collaboration of Kenyan citizen journalists during a time of crisis. The original website was used to map incidents of violence and peace efforts throughout the country based on reports submitted via the web and mobile phones. This website had 45,000 users in Kenya, and was the catalyst for us realizing there was a need for a platform based on it, which could be used by others around the world.<br />
<br />
Since early 2008 we have grown from an ad hoc group of volunteers to a focused organization. Our current team is comprised of individuals with a wide span of experience ranging from human rights work to software development. We have also built a strong team of volunteer developers primarily in Africa, but also Europe, South America and the U.S."<br />
<br />
'''Website:''' [http://www.ushahidi.com/ http://www.ushahidi.com/]<br />
<br />
'''Foss2serve contact:''' Cam MacDonell (cameron.macdonell@macewan.ca)<br />
<br />
'''Foss2Serve Page:''' [[Ushahidi]]<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Monisha Pulimood<br />
* [[User:Srebelsky|Samuel A. Rebelsky]] <br />
* [[User:Ssheth|Swapneel Sheth]]<br />
* [[User:Blu|Baochuan Lu]]<br />
<br />
== GNOME Accessibility ==<br />
From the web site: "The GNOME Accessibility project develops and fosters compelling free open source accessibility solutions for graphical user interfaces. Through a worldwide community of developers and users, we continue to empower everyone, regardless of physical or mental abilities." <br />
<br />
The GNOME Project was started in 1997 by two then university students, Miguel de Icaza and Federico Mena. Their aim: to produce a free (as in freedom) desktop environment. Since then, GNOME has grown into a hugely successful enterprise. Used by millions of people across the world, it is the most popular desktop environment for GNU/Linux and UNIX-type operating systems.<br />
<br />
The GNOME Accessibility Team works to ensure the GNOME Desktop and the software therein can be used by everyone, regardless of age or ability. Its efforts include the Orca screen reader, the GNOME Shell magnifier, and the Accerciser testing and debugging tool, Evolution (Contact manager, address manager and calendar), Empathy (Chat client), and Nautilus (File manager). <br />
<br />
'''Website:''' [https://live.gnome.org/Accessibility https://live.gnome.org/Accessibility]<br />
<br />
'''Foss2serve contact:''' Heidi Ellis (ellis@wne.edu)<br />
<br />
'''Lanugage: ''' Varies by specific application<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Ellen Zimmer - Edinboro Univeristy<br />
* Trish Hillman - Edinboro University<br />
<br />
<br />
<br />
[[Category:POSSE]]</div>Jim.hugginshttp://foss2serve.org/index.php/HFOSS_CommunitiesHFOSS Communities2015-09-12T15:44:55Z<p>Jim.huggins: /* Mifos */</p>
<hr />
<div>This page holds a list of HFOSS communities that have volunteered to participate in foss2serve activities. Please sign up below the community that you are interested in participating in.<br />
<br />
== MouseTrap ==<br />
From the MouseTrap web site: "MouseTrap is a standalone GNOME application that allows users with physical impairments to move a mouse cursor. It uses a webcam to track the motion of any object visible by the camera and moves the mouse cursor according to the path of the tracked object (a user's head, for example). Distributed with software that allows accessible mouse clicking, MouseTrap will give most physically impaired users access to the full functionality of a mouse. Our ultimate goal is to have a usable, stable solution that allows users to control their cursors just as well as someone using a mouse.<br />
<br />
MouseTrap is written in Python, based on the OpenCV library and uses image processing to translate the user's head movements into mouse events (movements, clicks) which allow users to interact with the different desktops managers and applications."<br />
<br />
The project has been worked on successfully by several different academic classes. Note that the project requires some understanding of computer vision.<br />
<br />
'''Website:''' [https://wiki.gnome.org/action/show/Projects/MouseTrap?action=show&redirect=MouseTrap]<br />
<br />
'''Foss2serve contact:''' Stoney Jackson (stoney.jackson(at)wne.edu), <br />
Heidi Ellis (ellis(at)wne.edu)<br />
<br />
'''Lanugage: ''' Varies by specific application<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
Dee Weikle dee.weikle@emu.edu<br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Stoney Jackson - Western New England University<br />
* Heidi Ellis - Western New England University<br />
<br />
== Mifos ==<br />
From SourceForge: "Mifos is an MIS purpose-built for the microfinance industry. It provides MFIs the key functionality to better serve the poor: client management, loans & savings portfolio tracking, reporting, & social performance measurement. "<br />
<br />
From the web site: " Mifos.org is a diverse community of microfinance institutions, technology professionals, business people, volunteers, and contributors.<br />
* We are guided by the vision to create and deploy technology that allows the microfinance industry to scale.<br />
* Our team and our community of users are distributed worldwide, spanning all time zones, in developing nations and developed.<br />
* We are a community that actively supports each other in the development and use of the Mifos software."<br />
<br />
'''Website:''' [http://mifos.org/ http://mifos.org/]<br />
<br />
'''Better Website:''' [https://mifosforge.jira.com/wiki/display/MDZ/Welcome+to+the+Zone]<br />
<br />
'''Foss2serve contact:''' Greg Hislop<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
* Nanette Veilleux<br />
* Lynn Lambert<br />
* Jim Huggins<br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
<br />
== OpenMRS ==<br />
From the website: "Open Medical Record System (OpenMRS®) was created in 2004 as a open source medical record system platform for developing countries – a tide which rises all ships. OpenMRS is a multi-institution, non-profit collaborative led by Regenstrief Institute, a world-renowned leader in medical informatics research, and Partners In Health, a Boston-based philanthropic organization with a focus on improving the lives of underprivileged people worldwide through health care service and advocacy. These teams nurture a growing worldwide network of individuals and organizations all focused on creating medical record systems and a corresponding implementation network to allow system development self reliance within resource constrained environments."<br />
<br />
'''Website:''' [http://openmrs.org/ http://openmrs.org/]<br />
<br />
'''Team Page:''' [http://foss2serve.org/index.php/TheOpenMRSTeam http://foss2serve.org/index.php/TheOpenMRSTeam]<br />
<br />
'''Getting Started:'''<br />
* General overview for developers -- [http://openmrs.org/help/developers/ http://openmrs.org/help/developers/]<br />
** Familiarize yourself with the various tools and resources - view this page only, you do not need to visit any of the pages linked from this page<br />
* Getting started book (OpenMRS Developers' Guide) -- [http://go.openmrs.org/newdev-web http://go.openmrs.org/newdev-web]<br />
** Read the information found on the following pages - these are also available as links in the main menu on the left<br />
*** Welcome to OpenMRS! - [http://en.flossmanuals.net/openmrs-developers-guide/index/ http://en.flossmanuals.net/openmrs-developers-guide/index/]<br />
*** The Need for Health IT - [http://en.flossmanuals.net/openmrs-developers-guide/the-need-for-health-it/ http://en.flossmanuals.net/openmrs-developers-guide/the-need-for-health-it/]<br />
*** Our Response - [http://en.flossmanuals.net/openmrs-developers-guide/story-of-openmrs/ http://en.flossmanuals.net/openmrs-developers-guide/story-of-openmrs/]<br />
*** OpenMRS Today - [http://en.flossmanuals.net/openmrs-developers-guide/state-of-openmrs/ http://en.flossmanuals.net/openmrs-developers-guide/state-of-openmrs/]<br />
*** Although all of the information in the Community and Technology sections is beneficial, skip it for now and proceed directly to the instructions for getting the development environment set up - [http://en.flossmanuals.net/openmrs-developers-guide/get-set-up/ http://en.flossmanuals.net/openmrs-developers-guide/get-set-up/]. Follow the instructions for doing a '''manual install''' (you will have to scroll down a bit).<br />
<br />
'''Foss2serve contact:''' Darci Burdge (<br />
<br />
=== Sign up ===<br />
* [[User:Emily.lovell|Emily Lovell]]<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Chris Murphy<br />
* Meghan Allen<br />
* Steven P. Crain<br />
<br />
== Sahana ==<br />
Sahana Eden is a flexible open source humanitarian platform with a rich feature set to provide effective solutions for critical humanitarian needs management, either prior to, or during, a crisis. Eden can be rapidly customized to adapt to existing processes and to integrate with existing systems. Eden is designed for most organizations and agencies engaged in humanitarian activities, including UN agencies, NGOs and government agencies, and provides solutions to challenges involved in resource management, information management, coordination, decision support and stakeholder communications. It is built with Python using the Web2Py framework. Sahana Eden currently supports a diverse set of humanitarian organizations, including the City of Los Angeles Emergency Management Department, the International Federation of the Red Cross (IFRC), the American Red Cross, the Helios Foundation, the UN World Food Programme, and several CERT chapters and VOAD organizations in the United States. <br />
<br />
'''Website:''' [http://sahanafoundation.org/ http://sahanafoundation.org/]<br />
<br />
'''Foss2serve contact:''' <br />
<br />
'''Language: ''' Python<br />
<br />
'''Team Page: ''' [[SahanaGroupNotes]] (Will help get you started, but may not be current.)<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Peter Bui (pnutzh4x0r)<br />
* Nannette Napier<br />
* Esmail Bonakdarian<br />
* Kiranmai Bellam<br />
* Howard Francis<br />
<br />
== Ushahidi ==<br />
From the website: "We are a non-profit tech company that specializes in developing free and open source software for information collection, visualization and interactive mapping."<br />
<br />
" "Ushahidi", which means "testimony" in Swahili, was a website that was initially developed to map reports of violence in Kenya after the post-election fallout at the beginning of 2008. Since then, the name "Ushahidi" has come to represent the people behind the "Ushahidi Platform". Our roots are in the collaboration of Kenyan citizen journalists during a time of crisis. The original website was used to map incidents of violence and peace efforts throughout the country based on reports submitted via the web and mobile phones. This website had 45,000 users in Kenya, and was the catalyst for us realizing there was a need for a platform based on it, which could be used by others around the world.<br />
<br />
Since early 2008 we have grown from an ad hoc group of volunteers to a focused organization. Our current team is comprised of individuals with a wide span of experience ranging from human rights work to software development. We have also built a strong team of volunteer developers primarily in Africa, but also Europe, South America and the U.S."<br />
<br />
'''Website:''' [http://www.ushahidi.com/ http://www.ushahidi.com/]<br />
<br />
'''Foss2serve contact:''' Cam MacDonell (cameron.macdonell@macewan.ca)<br />
<br />
'''Foss2Serve Page:''' [[Ushahidi]]<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Monisha Pulimood<br />
* [[User:Srebelsky|Samuel A. Rebelsky]] <br />
* [[User:Ssheth|Swapneel Sheth]]<br />
* [[User:Blu|Baochuan Lu]]<br />
<br />
== GNOME Accessibility ==<br />
From the web site: "The GNOME Accessibility project develops and fosters compelling free open source accessibility solutions for graphical user interfaces. Through a worldwide community of developers and users, we continue to empower everyone, regardless of physical or mental abilities." <br />
<br />
The GNOME Project was started in 1997 by two then university students, Miguel de Icaza and Federico Mena. Their aim: to produce a free (as in freedom) desktop environment. Since then, GNOME has grown into a hugely successful enterprise. Used by millions of people across the world, it is the most popular desktop environment for GNU/Linux and UNIX-type operating systems.<br />
<br />
The GNOME Accessibility Team works to ensure the GNOME Desktop and the software therein can be used by everyone, regardless of age or ability. Its efforts include the Orca screen reader, the GNOME Shell magnifier, and the Accerciser testing and debugging tool, Evolution (Contact manager, address manager and calendar), Empathy (Chat client), and Nautilus (File manager). <br />
<br />
'''Website:''' [https://live.gnome.org/Accessibility https://live.gnome.org/Accessibility]<br />
<br />
'''Foss2serve contact:''' Heidi Ellis (ellis@wne.edu)<br />
<br />
'''Lanugage: ''' Varies by specific application<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Ellen Zimmer - Edinboro Univeristy<br />
* Trish Hillman - Edinboro University<br />
<br />
<br />
<br />
[[Category:POSSE]]</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-09-11T15:10:09Z<p>Jim.huggins: /* Group Participants */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Available information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle<br />
<br />
=== SahanaEden ===<br />
<br />
# ''Community'': less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).<br />
## ''Developers'': full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform<br />
## ''Testers'': less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process<br />
## ''Designers'': even less information, just a few links to areas of design need<br />
# ''Tracker'': main page has various (presumably) common queries of subsets of bugs in the system<br />
## ''Types of tickets'': defect/bug, documentation, enhancement, task<br />
## ''Available information'': ticket number, summary, component, version, priority, type, owner, status, date created<br />
# ''Repository'': again, appears to be a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.<br />
<br />
== FOSS In Courses Activity (Stage 1, Part B, Item 4) ==<br />
<br />
Okay, so, in order for this to make sense, you may want to read my [http://jkhuggins.livejournal.com/193067.html blog entry] which describes my intended use case.<br />
<br />
At the moment, I've selected Mifos as my project, though that's mostly because it looks like there's lots of Java work going on there, and I haven't learned Python (yet).<br />
<br />
So, for existing class materials, I really didn't look that deeply at other people's stuff, because it's not as directly relevant. But that's okay, because the Kettering "Culminating Undergraduate Experience" has a pretty well-defined roadmap.<br />
<br />
The Kettering process begins by a student identifying a project which has the following four characteristics:<br />
* The project is of value to the client<br />
* The project is phrased as a problem, rather than a solution (i.e. the problem will require at least some level of design work to bring the task to completion)<br />
* The project requires the student to use their professional skills (i.e. this isn't just a grunt-work assignment)<br />
* The project can be completed in a reasonable time-frame (typically, 3-6 months of full-time effort)<br />
<br />
So, the first assignment for a Kettering student would be to investigate the project (Mifos in this case, but it really could be anything), with the goal of figuring out a larger task to tackle. The project investigation probably should involve some of the usual on-ramps (simple bug fixes, documentation cleanup, joining the online communities) in order to become a known part of the community. At that point, discussions within the community could evolve to consider what sort of project could be "claimed" by the student.<br />
<br />
Once a project is identified, a further roadmap would be developed, depending on the needs of the project.<br />
<br />
== Bug Tracker Activity Responses (Stage 1, Part C, Item 2) ==<br />
<br />
=== Part 1: Bug Reports ===<br />
<br />
# (No response required.)<br />
# Definitions below.<br />
## ID: presumably a unique identifier for each bug<br />
## Sev: appears not to be used<br />
## Pri: appears not to be used<br />
## OS: appears not to be used<br />
## Product: the specific product affected by the bug. Lots of possible values.<br />
## Status: point in the lifecycle of the bug. Observed values: NEEDINFO, REOPENED, ASSIGNED, NEW, UNCONFIRMED<br />
## Resolution: appears unused, but actually shows up in the list<br />
## Summary: short textual summary of issue<br />
# The help link provided some information; alt-text for some fields revealed other data.<br />
# Sort order appears to be based on status.<br />
# I don't see a difference based on shading ...<br />
# Red appears to be for critical bugs. Grey appears to be for enhancements. Black is for "normal" issues.<br />
# Bug 573941<br />
## Submitted 2009-03-03.<br />
## No discussion since 2009.<br />
## Bug still appears active.<br />
## Appears to be assigned to "At-spi maintainer(s)"<br />
## This is a small change to the documentation --- once the correct answer is identified.<br />
# Bug 669597<br />
## Submitted 2012-02-07.<br />
## Some discussion in 2012-13.<br />
## Bug still appears active.<br />
## Appears to be assigned to "Control-Center Maintainers"<br />
## Mostly, this is a change to the internal help documentation ... biggest issue will be identifying the proper phrasing to use.<br />
<br />
=== Part 2: Collective Reports ===<br />
<br />
# (No response required.)<br />
# (No response required.)<br />
# 316 reports opened. 274 reports closed.<br />
# Um, pretty clear that more reports were opened than closed (316 - 274 > 0).<br />
# Top three closers: Matthias Clasen, Carlos Soriano, Milan Crha. Important to give recognition/thanks to those who are contributing to the project.<br />
# Top three reporters: Bastien Nocera, Alexander Larsson, Andreas Nillson. No overlap with closers.<br />
# Top three patch contributors: Carlos Soriano, Bastien Nocera, Sebastian Droge<br />
# Top three patch reviewers: Carlos Soriano, Sebastian Droge, Matthias Clasen. Substantial overlap with closers and path contributers.<br />
# (No response required.)<br />
# (No response required.)<br />
# Most bugs for braille were "normal".<br />
# Line, table, and CSV.<br />
<br />
=== Stage 2: Planning for Stage 3 ===<br />
<br />
== Group Participants == <br />
* [[User:Jim.huggins|Jim Huggins]]<br />
* [[User:Llambert|Lynn Lambert]] <br />
* [[User:Nanette.veilleux|Nanette Veilleux]]<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 template here: <br />
[http://foss2serve.org/index.php/Stage_2_Activities/Activity_Template Learning Activity Template]<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 />
<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]]</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-09-11T15:09:28Z<p>Jim.huggins: /* Group Participants */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Available information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle<br />
<br />
=== SahanaEden ===<br />
<br />
# ''Community'': less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).<br />
## ''Developers'': full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform<br />
## ''Testers'': less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process<br />
## ''Designers'': even less information, just a few links to areas of design need<br />
# ''Tracker'': main page has various (presumably) common queries of subsets of bugs in the system<br />
## ''Types of tickets'': defect/bug, documentation, enhancement, task<br />
## ''Available information'': ticket number, summary, component, version, priority, type, owner, status, date created<br />
# ''Repository'': again, appears to be a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.<br />
<br />
== FOSS In Courses Activity (Stage 1, Part B, Item 4) ==<br />
<br />
Okay, so, in order for this to make sense, you may want to read my [http://jkhuggins.livejournal.com/193067.html blog entry] which describes my intended use case.<br />
<br />
At the moment, I've selected Mifos as my project, though that's mostly because it looks like there's lots of Java work going on there, and I haven't learned Python (yet).<br />
<br />
So, for existing class materials, I really didn't look that deeply at other people's stuff, because it's not as directly relevant. But that's okay, because the Kettering "Culminating Undergraduate Experience" has a pretty well-defined roadmap.<br />
<br />
The Kettering process begins by a student identifying a project which has the following four characteristics:<br />
* The project is of value to the client<br />
* The project is phrased as a problem, rather than a solution (i.e. the problem will require at least some level of design work to bring the task to completion)<br />
* The project requires the student to use their professional skills (i.e. this isn't just a grunt-work assignment)<br />
* The project can be completed in a reasonable time-frame (typically, 3-6 months of full-time effort)<br />
<br />
So, the first assignment for a Kettering student would be to investigate the project (Mifos in this case, but it really could be anything), with the goal of figuring out a larger task to tackle. The project investigation probably should involve some of the usual on-ramps (simple bug fixes, documentation cleanup, joining the online communities) in order to become a known part of the community. At that point, discussions within the community could evolve to consider what sort of project could be "claimed" by the student.<br />
<br />
Once a project is identified, a further roadmap would be developed, depending on the needs of the project.<br />
<br />
== Bug Tracker Activity Responses (Stage 1, Part C, Item 2) ==<br />
<br />
=== Part 1: Bug Reports ===<br />
<br />
# (No response required.)<br />
# Definitions below.<br />
## ID: presumably a unique identifier for each bug<br />
## Sev: appears not to be used<br />
## Pri: appears not to be used<br />
## OS: appears not to be used<br />
## Product: the specific product affected by the bug. Lots of possible values.<br />
## Status: point in the lifecycle of the bug. Observed values: NEEDINFO, REOPENED, ASSIGNED, NEW, UNCONFIRMED<br />
## Resolution: appears unused, but actually shows up in the list<br />
## Summary: short textual summary of issue<br />
# The help link provided some information; alt-text for some fields revealed other data.<br />
# Sort order appears to be based on status.<br />
# I don't see a difference based on shading ...<br />
# Red appears to be for critical bugs. Grey appears to be for enhancements. Black is for "normal" issues.<br />
# Bug 573941<br />
## Submitted 2009-03-03.<br />
## No discussion since 2009.<br />
## Bug still appears active.<br />
## Appears to be assigned to "At-spi maintainer(s)"<br />
## This is a small change to the documentation --- once the correct answer is identified.<br />
# Bug 669597<br />
## Submitted 2012-02-07.<br />
## Some discussion in 2012-13.<br />
## Bug still appears active.<br />
## Appears to be assigned to "Control-Center Maintainers"<br />
## Mostly, this is a change to the internal help documentation ... biggest issue will be identifying the proper phrasing to use.<br />
<br />
=== Part 2: Collective Reports ===<br />
<br />
# (No response required.)<br />
# (No response required.)<br />
# 316 reports opened. 274 reports closed.<br />
# Um, pretty clear that more reports were opened than closed (316 - 274 > 0).<br />
# Top three closers: Matthias Clasen, Carlos Soriano, Milan Crha. Important to give recognition/thanks to those who are contributing to the project.<br />
# Top three reporters: Bastien Nocera, Alexander Larsson, Andreas Nillson. No overlap with closers.<br />
# Top three patch contributors: Carlos Soriano, Bastien Nocera, Sebastian Droge<br />
# Top three patch reviewers: Carlos Soriano, Sebastian Droge, Matthias Clasen. Substantial overlap with closers and path contributers.<br />
# (No response required.)<br />
# (No response required.)<br />
# Most bugs for braille were "normal".<br />
# Line, table, and CSV.<br />
<br />
=== Stage 2: Planning for Stage 3 ===<br />
<br />
== Group Participants == <br />
* [[User:Jim.huggins|Jim Huggins]]<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 template here: <br />
[http://foss2serve.org/index.php/Stage_2_Activities/Activity_Template Learning Activity Template]<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 />
<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]]</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-09-11T15:08:47Z<p>Jim.huggins: /* Group Participants */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Available information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle<br />
<br />
=== SahanaEden ===<br />
<br />
# ''Community'': less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).<br />
## ''Developers'': full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform<br />
## ''Testers'': less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process<br />
## ''Designers'': even less information, just a few links to areas of design need<br />
# ''Tracker'': main page has various (presumably) common queries of subsets of bugs in the system<br />
## ''Types of tickets'': defect/bug, documentation, enhancement, task<br />
## ''Available information'': ticket number, summary, component, version, priority, type, owner, status, date created<br />
# ''Repository'': again, appears to be a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.<br />
<br />
== FOSS In Courses Activity (Stage 1, Part B, Item 4) ==<br />
<br />
Okay, so, in order for this to make sense, you may want to read my [http://jkhuggins.livejournal.com/193067.html blog entry] which describes my intended use case.<br />
<br />
At the moment, I've selected Mifos as my project, though that's mostly because it looks like there's lots of Java work going on there, and I haven't learned Python (yet).<br />
<br />
So, for existing class materials, I really didn't look that deeply at other people's stuff, because it's not as directly relevant. But that's okay, because the Kettering "Culminating Undergraduate Experience" has a pretty well-defined roadmap.<br />
<br />
The Kettering process begins by a student identifying a project which has the following four characteristics:<br />
* The project is of value to the client<br />
* The project is phrased as a problem, rather than a solution (i.e. the problem will require at least some level of design work to bring the task to completion)<br />
* The project requires the student to use their professional skills (i.e. this isn't just a grunt-work assignment)<br />
* The project can be completed in a reasonable time-frame (typically, 3-6 months of full-time effort)<br />
<br />
So, the first assignment for a Kettering student would be to investigate the project (Mifos in this case, but it really could be anything), with the goal of figuring out a larger task to tackle. The project investigation probably should involve some of the usual on-ramps (simple bug fixes, documentation cleanup, joining the online communities) in order to become a known part of the community. At that point, discussions within the community could evolve to consider what sort of project could be "claimed" by the student.<br />
<br />
Once a project is identified, a further roadmap would be developed, depending on the needs of the project.<br />
<br />
== Bug Tracker Activity Responses (Stage 1, Part C, Item 2) ==<br />
<br />
=== Part 1: Bug Reports ===<br />
<br />
# (No response required.)<br />
# Definitions below.<br />
## ID: presumably a unique identifier for each bug<br />
## Sev: appears not to be used<br />
## Pri: appears not to be used<br />
## OS: appears not to be used<br />
## Product: the specific product affected by the bug. Lots of possible values.<br />
## Status: point in the lifecycle of the bug. Observed values: NEEDINFO, REOPENED, ASSIGNED, NEW, UNCONFIRMED<br />
## Resolution: appears unused, but actually shows up in the list<br />
## Summary: short textual summary of issue<br />
# The help link provided some information; alt-text for some fields revealed other data.<br />
# Sort order appears to be based on status.<br />
# I don't see a difference based on shading ...<br />
# Red appears to be for critical bugs. Grey appears to be for enhancements. Black is for "normal" issues.<br />
# Bug 573941<br />
## Submitted 2009-03-03.<br />
## No discussion since 2009.<br />
## Bug still appears active.<br />
## Appears to be assigned to "At-spi maintainer(s)"<br />
## This is a small change to the documentation --- once the correct answer is identified.<br />
# Bug 669597<br />
## Submitted 2012-02-07.<br />
## Some discussion in 2012-13.<br />
## Bug still appears active.<br />
## Appears to be assigned to "Control-Center Maintainers"<br />
## Mostly, this is a change to the internal help documentation ... biggest issue will be identifying the proper phrasing to use.<br />
<br />
=== Part 2: Collective Reports ===<br />
<br />
# (No response required.)<br />
# (No response required.)<br />
# 316 reports opened. 274 reports closed.<br />
# Um, pretty clear that more reports were opened than closed (316 - 274 > 0).<br />
# Top three closers: Matthias Clasen, Carlos Soriano, Milan Crha. Important to give recognition/thanks to those who are contributing to the project.<br />
# Top three reporters: Bastien Nocera, Alexander Larsson, Andreas Nillson. No overlap with closers.<br />
# Top three patch contributors: Carlos Soriano, Bastien Nocera, Sebastian Droge<br />
# Top three patch reviewers: Carlos Soriano, Sebastian Droge, Matthias Clasen. Substantial overlap with closers and path contributers.<br />
# (No response required.)<br />
# (No response required.)<br />
# Most bugs for braille were "normal".<br />
# Line, table, and CSV.<br />
<br />
=== Stage 2: Planning for Stage 3 ===<br />
<br />
== Group Participants == <br />
[[User:Jim.huggins|Jim Huggins]]<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 template here: <br />
[http://foss2serve.org/index.php/Stage_2_Activities/Activity_Template Learning Activity Template]<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 />
<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]]</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-09-11T15:08:06Z<p>Jim.huggins: /* Group Participants */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Available information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle<br />
<br />
=== SahanaEden ===<br />
<br />
# ''Community'': less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).<br />
## ''Developers'': full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform<br />
## ''Testers'': less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process<br />
## ''Designers'': even less information, just a few links to areas of design need<br />
# ''Tracker'': main page has various (presumably) common queries of subsets of bugs in the system<br />
## ''Types of tickets'': defect/bug, documentation, enhancement, task<br />
## ''Available information'': ticket number, summary, component, version, priority, type, owner, status, date created<br />
# ''Repository'': again, appears to be a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.<br />
<br />
== FOSS In Courses Activity (Stage 1, Part B, Item 4) ==<br />
<br />
Okay, so, in order for this to make sense, you may want to read my [http://jkhuggins.livejournal.com/193067.html blog entry] which describes my intended use case.<br />
<br />
At the moment, I've selected Mifos as my project, though that's mostly because it looks like there's lots of Java work going on there, and I haven't learned Python (yet).<br />
<br />
So, for existing class materials, I really didn't look that deeply at other people's stuff, because it's not as directly relevant. But that's okay, because the Kettering "Culminating Undergraduate Experience" has a pretty well-defined roadmap.<br />
<br />
The Kettering process begins by a student identifying a project which has the following four characteristics:<br />
* The project is of value to the client<br />
* The project is phrased as a problem, rather than a solution (i.e. the problem will require at least some level of design work to bring the task to completion)<br />
* The project requires the student to use their professional skills (i.e. this isn't just a grunt-work assignment)<br />
* The project can be completed in a reasonable time-frame (typically, 3-6 months of full-time effort)<br />
<br />
So, the first assignment for a Kettering student would be to investigate the project (Mifos in this case, but it really could be anything), with the goal of figuring out a larger task to tackle. The project investigation probably should involve some of the usual on-ramps (simple bug fixes, documentation cleanup, joining the online communities) in order to become a known part of the community. At that point, discussions within the community could evolve to consider what sort of project could be "claimed" by the student.<br />
<br />
Once a project is identified, a further roadmap would be developed, depending on the needs of the project.<br />
<br />
== Bug Tracker Activity Responses (Stage 1, Part C, Item 2) ==<br />
<br />
=== Part 1: Bug Reports ===<br />
<br />
# (No response required.)<br />
# Definitions below.<br />
## ID: presumably a unique identifier for each bug<br />
## Sev: appears not to be used<br />
## Pri: appears not to be used<br />
## OS: appears not to be used<br />
## Product: the specific product affected by the bug. Lots of possible values.<br />
## Status: point in the lifecycle of the bug. Observed values: NEEDINFO, REOPENED, ASSIGNED, NEW, UNCONFIRMED<br />
## Resolution: appears unused, but actually shows up in the list<br />
## Summary: short textual summary of issue<br />
# The help link provided some information; alt-text for some fields revealed other data.<br />
# Sort order appears to be based on status.<br />
# I don't see a difference based on shading ...<br />
# Red appears to be for critical bugs. Grey appears to be for enhancements. Black is for "normal" issues.<br />
# Bug 573941<br />
## Submitted 2009-03-03.<br />
## No discussion since 2009.<br />
## Bug still appears active.<br />
## Appears to be assigned to "At-spi maintainer(s)"<br />
## This is a small change to the documentation --- once the correct answer is identified.<br />
# Bug 669597<br />
## Submitted 2012-02-07.<br />
## Some discussion in 2012-13.<br />
## Bug still appears active.<br />
## Appears to be assigned to "Control-Center Maintainers"<br />
## Mostly, this is a change to the internal help documentation ... biggest issue will be identifying the proper phrasing to use.<br />
<br />
=== Part 2: Collective Reports ===<br />
<br />
# (No response required.)<br />
# (No response required.)<br />
# 316 reports opened. 274 reports closed.<br />
# Um, pretty clear that more reports were opened than closed (316 - 274 > 0).<br />
# Top three closers: Matthias Clasen, Carlos Soriano, Milan Crha. Important to give recognition/thanks to those who are contributing to the project.<br />
# Top three reporters: Bastien Nocera, Alexander Larsson, Andreas Nillson. No overlap with closers.<br />
# Top three patch contributors: Carlos Soriano, Bastien Nocera, Sebastian Droge<br />
# Top three patch reviewers: Carlos Soriano, Sebastian Droge, Matthias Clasen. Substantial overlap with closers and path contributers.<br />
# (No response required.)<br />
# (No response required.)<br />
# Most bugs for braille were "normal".<br />
# Line, table, and CSV.<br />
<br />
=== Stage 2: Planning for Stage 3 ===<br />
<br />
== Group Participants == <br />
[[User:Jim.huggins]]<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 template here: <br />
[http://foss2serve.org/index.php/Stage_2_Activities/Activity_Template Learning Activity Template]<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 />
<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]]</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-09-11T15:06:54Z<p>Jim.huggins: </p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Available information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle<br />
<br />
=== SahanaEden ===<br />
<br />
# ''Community'': less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).<br />
## ''Developers'': full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform<br />
## ''Testers'': less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process<br />
## ''Designers'': even less information, just a few links to areas of design need<br />
# ''Tracker'': main page has various (presumably) common queries of subsets of bugs in the system<br />
## ''Types of tickets'': defect/bug, documentation, enhancement, task<br />
## ''Available information'': ticket number, summary, component, version, priority, type, owner, status, date created<br />
# ''Repository'': again, appears to be a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.<br />
<br />
== FOSS In Courses Activity (Stage 1, Part B, Item 4) ==<br />
<br />
Okay, so, in order for this to make sense, you may want to read my [http://jkhuggins.livejournal.com/193067.html blog entry] which describes my intended use case.<br />
<br />
At the moment, I've selected Mifos as my project, though that's mostly because it looks like there's lots of Java work going on there, and I haven't learned Python (yet).<br />
<br />
So, for existing class materials, I really didn't look that deeply at other people's stuff, because it's not as directly relevant. But that's okay, because the Kettering "Culminating Undergraduate Experience" has a pretty well-defined roadmap.<br />
<br />
The Kettering process begins by a student identifying a project which has the following four characteristics:<br />
* The project is of value to the client<br />
* The project is phrased as a problem, rather than a solution (i.e. the problem will require at least some level of design work to bring the task to completion)<br />
* The project requires the student to use their professional skills (i.e. this isn't just a grunt-work assignment)<br />
* The project can be completed in a reasonable time-frame (typically, 3-6 months of full-time effort)<br />
<br />
So, the first assignment for a Kettering student would be to investigate the project (Mifos in this case, but it really could be anything), with the goal of figuring out a larger task to tackle. The project investigation probably should involve some of the usual on-ramps (simple bug fixes, documentation cleanup, joining the online communities) in order to become a known part of the community. At that point, discussions within the community could evolve to consider what sort of project could be "claimed" by the student.<br />
<br />
Once a project is identified, a further roadmap would be developed, depending on the needs of the project.<br />
<br />
== Bug Tracker Activity Responses (Stage 1, Part C, Item 2) ==<br />
<br />
=== Part 1: Bug Reports ===<br />
<br />
# (No response required.)<br />
# Definitions below.<br />
## ID: presumably a unique identifier for each bug<br />
## Sev: appears not to be used<br />
## Pri: appears not to be used<br />
## OS: appears not to be used<br />
## Product: the specific product affected by the bug. Lots of possible values.<br />
## Status: point in the lifecycle of the bug. Observed values: NEEDINFO, REOPENED, ASSIGNED, NEW, UNCONFIRMED<br />
## Resolution: appears unused, but actually shows up in the list<br />
## Summary: short textual summary of issue<br />
# The help link provided some information; alt-text for some fields revealed other data.<br />
# Sort order appears to be based on status.<br />
# I don't see a difference based on shading ...<br />
# Red appears to be for critical bugs. Grey appears to be for enhancements. Black is for "normal" issues.<br />
# Bug 573941<br />
## Submitted 2009-03-03.<br />
## No discussion since 2009.<br />
## Bug still appears active.<br />
## Appears to be assigned to "At-spi maintainer(s)"<br />
## This is a small change to the documentation --- once the correct answer is identified.<br />
# Bug 669597<br />
## Submitted 2012-02-07.<br />
## Some discussion in 2012-13.<br />
## Bug still appears active.<br />
## Appears to be assigned to "Control-Center Maintainers"<br />
## Mostly, this is a change to the internal help documentation ... biggest issue will be identifying the proper phrasing to use.<br />
<br />
=== Part 2: Collective Reports ===<br />
<br />
# (No response required.)<br />
# (No response required.)<br />
# 316 reports opened. 274 reports closed.<br />
# Um, pretty clear that more reports were opened than closed (316 - 274 > 0).<br />
# Top three closers: Matthias Clasen, Carlos Soriano, Milan Crha. Important to give recognition/thanks to those who are contributing to the project.<br />
# Top three reporters: Bastien Nocera, Alexander Larsson, Andreas Nillson. No overlap with closers.<br />
# Top three patch contributors: Carlos Soriano, Bastien Nocera, Sebastian Droge<br />
# Top three patch reviewers: Carlos Soriano, Sebastian Droge, Matthias Clasen. Substantial overlap with closers and path contributers.<br />
# (No response required.)<br />
# (No response required.)<br />
# Most bugs for braille were "normal".<br />
# Line, table, and CSV.<br />
<br />
=== Stage 2: Planning for Stage 3 ===<br />
<br />
== Group Participants == <br />
[[Jim.huggins]]<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 template here: <br />
[http://foss2serve.org/index.php/Stage_2_Activities/Activity_Template Learning Activity Template]<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 />
<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]]</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-09-05T22:58:31Z<p>Jim.huggins: </p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Available information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle<br />
<br />
=== SahanaEden ===<br />
<br />
# ''Community'': less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).<br />
## ''Developers'': full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform<br />
## ''Testers'': less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process<br />
## ''Designers'': even less information, just a few links to areas of design need<br />
# ''Tracker'': main page has various (presumably) common queries of subsets of bugs in the system<br />
## ''Types of tickets'': defect/bug, documentation, enhancement, task<br />
## ''Available information'': ticket number, summary, component, version, priority, type, owner, status, date created<br />
# ''Repository'': again, appears to be a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.<br />
<br />
== FOSS In Courses Activity (Stage 1, Part B, Item 4) ==<br />
<br />
Okay, so, in order for this to make sense, you may want to read my [http://jkhuggins.livejournal.com/193067.html blog entry] which describes my intended use case.<br />
<br />
At the moment, I've selected Mifos as my project, though that's mostly because it looks like there's lots of Java work going on there, and I haven't learned Python (yet).<br />
<br />
So, for existing class materials, I really didn't look that deeply at other people's stuff, because it's not as directly relevant. But that's okay, because the Kettering "Culminating Undergraduate Experience" has a pretty well-defined roadmap.<br />
<br />
The Kettering process begins by a student identifying a project which has the following four characteristics:<br />
* The project is of value to the client<br />
* The project is phrased as a problem, rather than a solution (i.e. the problem will require at least some level of design work to bring the task to completion)<br />
* The project requires the student to use their professional skills (i.e. this isn't just a grunt-work assignment)<br />
* The project can be completed in a reasonable time-frame (typically, 3-6 months of full-time effort)<br />
<br />
So, the first assignment for a Kettering student would be to investigate the project (Mifos in this case, but it really could be anything), with the goal of figuring out a larger task to tackle. The project investigation probably should involve some of the usual on-ramps (simple bug fixes, documentation cleanup, joining the online communities) in order to become a known part of the community. At that point, discussions within the community could evolve to consider what sort of project could be "claimed" by the student.<br />
<br />
Once a project is identified, a further roadmap would be developed, depending on the needs of the project.<br />
<br />
== Bug Tracker Activity Responses (Stage 1, Part C, Item 2) ==<br />
<br />
=== Part 1: Bug Reports ===<br />
<br />
# (No response required.)<br />
# Definitions below.<br />
## ID: presumably a unique identifier for each bug<br />
## Sev: appears not to be used<br />
## Pri: appears not to be used<br />
## OS: appears not to be used<br />
## Product: the specific product affected by the bug. Lots of possible values.<br />
## Status: point in the lifecycle of the bug. Observed values: NEEDINFO, REOPENED, ASSIGNED, NEW, UNCONFIRMED<br />
## Resolution: appears unused, but actually shows up in the list<br />
## Summary: short textual summary of issue<br />
# The help link provided some information; alt-text for some fields revealed other data.<br />
# Sort order appears to be based on status.<br />
# I don't see a difference based on shading ...<br />
# Red appears to be for critical bugs. Grey appears to be for enhancements. Black is for "normal" issues.<br />
# Bug 573941<br />
## Submitted 2009-03-03.<br />
## No discussion since 2009.<br />
## Bug still appears active.<br />
## Appears to be assigned to "At-spi maintainer(s)"<br />
## This is a small change to the documentation --- once the correct answer is identified.<br />
# Bug 669597<br />
## Submitted 2012-02-07.<br />
## Some discussion in 2012-13.<br />
## Bug still appears active.<br />
## Appears to be assigned to "Control-Center Maintainers"<br />
## Mostly, this is a change to the internal help documentation ... biggest issue will be identifying the proper phrasing to use.<br />
<br />
=== Part 2: Collective Reports ===<br />
<br />
# (No response required.)<br />
# (No response required.)<br />
# 316 reports opened. 274 reports closed.<br />
# Um, pretty clear that more reports were opened than closed (316 - 274 > 0).<br />
# Top three closers: Matthias Clasen, Carlos Soriano, Milan Crha. Important to give recognition/thanks to those who are contributing to the project.<br />
# Top three reporters: Bastien Nocera, Alexander Larsson, Andreas Nillson. No overlap with closers.<br />
# Top three patch contributors: Carlos Soriano, Bastien Nocera, Sebastian Droge<br />
# Top three patch reviewers: Carlos Soriano, Sebastian Droge, Matthias Clasen. Substantial overlap with closers and path contributers.<br />
# (No response required.)<br />
# (No response required.)<br />
# Most bugs for braille were "normal".<br />
# Line, table, and CSV.</div>Jim.hugginshttp://foss2serve.org/index.php/HFOSS_CommunitiesHFOSS Communities2015-09-01T23:20:32Z<p>Jim.huggins: /* Sign up */</p>
<hr />
<div>This page holds a list of HFOSS communities that have volunteered to participate in foss2serve activities. Please sign up below the community that you are interested in participating in.<br />
<br />
== MouseTrap ==<br />
From the MouseTrap web site: "MouseTrap is a standalone GNOME application that allows users with physical impairments to move a mouse cursor. It uses a webcam to track the motion of any object visible by the camera and moves the mouse cursor according to the path of the tracked object (a user's head, for example). Distributed with software that allows accessible mouse clicking, MouseTrap will give most physically impaired users access to the full functionality of a mouse. Our ultimate goal is to have a usable, stable solution that allows users to control their cursors just as well as someone using a mouse.<br />
<br />
MouseTrap is written in Python, based on the OpenCV library and uses image processing to translate the user's head movements into mouse events (movements, clicks) which allow users to interact with the different desktops managers and applications."<br />
<br />
The project has been worked on successfully by several different academic classes. Note that the project requires some understanding of computer vision.<br />
<br />
'''Website:''' [https://wiki.gnome.org/action/show/Projects/MouseTrap?action=show&redirect=MouseTrap]<br />
<br />
'''Foss2serve contact:''' Stoney Jackson (stoney.jackson(at)wne.edu), <br />
Heidi Ellis (ellis(at)wne.edu)<br />
<br />
'''Lanugage: ''' Varies by specific application<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Stoney Jackson - Western New England University<br />
* Heidi Ellis - Western New England University<br />
<br />
== Mifos ==<br />
From SourceForge: "Mifos is an MIS purpose-built for the microfinance industry. It provides MFIs the key functionality to better serve the poor: client management, loans & savings portfolio tracking, reporting, & social performance measurement. "<br />
<br />
From the web site: " Mifos.org is a diverse community of microfinance institutions, technology professionals, business people, volunteers, and contributors.<br />
* We are guided by the vision to create and deploy technology that allows the microfinance industry to scale.<br />
* Our team and our community of users are distributed worldwide, spanning all time zones, in developing nations and developed.<br />
* We are a community that actively supports each other in the development and use of the Mifos software."<br />
<br />
'''Website:''' [http://mifos.org/ http://mifos.org/]<br />
<br />
'''Foss2serve contact:''' Greg Hislop<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
* Nanette Veilleux<br />
* Lynn Lambert<br />
* Jim Huggins<br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
<br />
== OpenMRS ==<br />
From the website: "Open Medical Record System (OpenMRS®) was created in 2004 as a open source medical record system platform for developing countries – a tide which rises all ships. OpenMRS is a multi-institution, non-profit collaborative led by Regenstrief Institute, a world-renowned leader in medical informatics research, and Partners In Health, a Boston-based philanthropic organization with a focus on improving the lives of underprivileged people worldwide through health care service and advocacy. These teams nurture a growing worldwide network of individuals and organizations all focused on creating medical record systems and a corresponding implementation network to allow system development self reliance within resource constrained environments."<br />
<br />
'''Website:''' [http://openmrs.org/ http://openmrs.org/]<br />
<br />
'''Team Page:''' [http://foss2serve.org/index.php/TheOpenMRSTeam http://foss2serve.org/index.php/TheOpenMRSTeam]<br />
<br />
'''Getting Started:'''<br />
* General overview for developers -- [http://openmrs.org/help/developers/ http://openmrs.org/help/developers/]<br />
** Familiarize yourself with the various tools and resources - view this page only, you do not need to visit any of the pages linked from this page<br />
* Getting started book (OpenMRS Developers' Guide) -- [http://go.openmrs.org/newdev-web http://go.openmrs.org/newdev-web]<br />
** Read the information found on the following pages - these are also available as links in the main menu on the left<br />
*** Welcome to OpenMRS! - [http://en.flossmanuals.net/openmrs-developers-guide/index/ http://en.flossmanuals.net/openmrs-developers-guide/index/]<br />
*** The Need for Health IT - [http://en.flossmanuals.net/openmrs-developers-guide/the-need-for-health-it/ http://en.flossmanuals.net/openmrs-developers-guide/the-need-for-health-it/]<br />
*** Our Response - [http://en.flossmanuals.net/openmrs-developers-guide/story-of-openmrs/ http://en.flossmanuals.net/openmrs-developers-guide/story-of-openmrs/]<br />
*** OpenMRS Today - [http://en.flossmanuals.net/openmrs-developers-guide/state-of-openmrs/ http://en.flossmanuals.net/openmrs-developers-guide/state-of-openmrs/]<br />
*** Although all of the information in the Community and Technology sections is beneficial, skip it for now and proceed directly to the instructions for getting the development environment set up - [http://en.flossmanuals.net/openmrs-developers-guide/get-set-up/ http://en.flossmanuals.net/openmrs-developers-guide/get-set-up/]. Follow the instructions for doing a '''manual install''' (you will have to scroll down a bit).<br />
<br />
'''Foss2serve contact:''' Darci Burdge (<br />
<br />
=== Sign up ===<br />
* [[User:Emily.lovell|Emily Lovell]]<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Chris Murphy<br />
* Meghan Allen<br />
* Steven P. Crain<br />
<br />
== Sahana ==<br />
Sahana Eden is a flexible open source humanitarian platform with a rich feature set to provide effective solutions for critical humanitarian needs management, either prior to, or during, a crisis. Eden can be rapidly customized to adapt to existing processes and to integrate with existing systems. Eden is designed for most organizations and agencies engaged in humanitarian activities, including UN agencies, NGOs and government agencies, and provides solutions to challenges involved in resource management, information management, coordination, decision support and stakeholder communications. It is built with Python using the Web2Py framework. Sahana Eden currently supports a diverse set of humanitarian organizations, including the City of Los Angeles Emergency Management Department, the International Federation of the Red Cross (IFRC), the American Red Cross, the Helios Foundation, the UN World Food Programme, and several CERT chapters and VOAD organizations in the United States. <br />
<br />
'''Website:''' [http://sahanafoundation.org/ http://sahanafoundation.org/]<br />
<br />
'''Foss2serve contact:''' <br />
<br />
'''Language: ''' Python<br />
<br />
'''Team Page: ''' [[SahanaGroupNotes]] (Will help get you started, but may not be current.)<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Peter Bui (pnutzh4x0r)<br />
* Nannette Napier<br />
* Esmail Bonakdarian<br />
* Kiranmai Bellam<br />
* Howard Francis<br />
<br />
== Ushahidi ==<br />
From the website: "We are a non-profit tech company that specializes in developing free and open source software for information collection, visualization and interactive mapping."<br />
<br />
" "Ushahidi", which means "testimony" in Swahili, was a website that was initially developed to map reports of violence in Kenya after the post-election fallout at the beginning of 2008. Since then, the name "Ushahidi" has come to represent the people behind the "Ushahidi Platform". Our roots are in the collaboration of Kenyan citizen journalists during a time of crisis. The original website was used to map incidents of violence and peace efforts throughout the country based on reports submitted via the web and mobile phones. This website had 45,000 users in Kenya, and was the catalyst for us realizing there was a need for a platform based on it, which could be used by others around the world.<br />
<br />
Since early 2008 we have grown from an ad hoc group of volunteers to a focused organization. Our current team is comprised of individuals with a wide span of experience ranging from human rights work to software development. We have also built a strong team of volunteer developers primarily in Africa, but also Europe, South America and the U.S."<br />
<br />
'''Website:''' [http://www.ushahidi.com/ http://www.ushahidi.com/]<br />
<br />
'''Foss2serve contact:''' Cam MacDonell (cameron.macdonell@macewan.ca)<br />
<br />
'''Foss2Serve Page:''' [[Ushahidi]]<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Monisha Pulimood<br />
* [[User:Srebelsky|Samuel A. Rebelsky]] <br />
* [[User:Ssheth|Swapneel Sheth]]<br />
* [[User:Blu|Baochuan Lu]]<br />
<br />
== GNOME Accessibility ==<br />
From the web site: "The GNOME Accessibility project develops and fosters compelling free open source accessibility solutions for graphical user interfaces. Through a worldwide community of developers and users, we continue to empower everyone, regardless of physical or mental abilities." <br />
<br />
The GNOME Project was started in 1997 by two then university students, Miguel de Icaza and Federico Mena. Their aim: to produce a free (as in freedom) desktop environment. Since then, GNOME has grown into a hugely successful enterprise. Used by millions of people across the world, it is the most popular desktop environment for GNU/Linux and UNIX-type operating systems.<br />
<br />
The GNOME Accessibility Team works to ensure the GNOME Desktop and the software therein can be used by everyone, regardless of age or ability. Its efforts include the Orca screen reader, the GNOME Shell magnifier, and the Accerciser testing and debugging tool, Evolution (Contact manager, address manager and calendar), Empathy (Chat client), and Nautilus (File manager). <br />
<br />
'''Website:''' [https://live.gnome.org/Accessibility https://live.gnome.org/Accessibility]<br />
<br />
'''Foss2serve contact:''' Heidi Ellis (ellis@wne.edu)<br />
<br />
'''Lanugage: ''' Varies by specific application<br />
<br />
=== Sign up ===<br />
<!-- Add your name and contact here as below --><br />
<br />
=== Faculty Members who may be Working on the Project ===<br />
* Ellen Zimmer - Edinboro Univeristy<br />
* Trish Hillman - Edinboro University<br />
<br />
<br />
<br />
[[Category:POSSE]]</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-20T15:50:40Z<p>Jim.huggins: /* FOSS In Courses Activity (Stage 2, Item 4) */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Available information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle<br />
<br />
=== SahanaEden ===<br />
<br />
# ''Community'': less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).<br />
## ''Developers'': full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform<br />
## ''Testers'': less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process<br />
## ''Designers'': even less information, just a few links to areas of design need<br />
# ''Tracker'': main page has various (presumably) common queries of subsets of bugs in the system<br />
## ''Types of tickets'': defect/bug, documentation, enhancement, task<br />
## ''Available information'': ticket number, summary, component, version, priority, type, owner, status, date created<br />
# ''Repository'': again, appears to be a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.<br />
<br />
== FOSS In Courses Activity (Stage 2, Item 4) ==<br />
<br />
Okay, so, in order for this to make sense, you may want to read my [http://jkhuggins.livejournal.com/193067.html blog entry] which describes my intended use case.<br />
<br />
At the moment, I've selected Mifos as my project, though that's mostly because it looks like there's lots of Java work going on there, and I haven't learned Python (yet).<br />
<br />
So, for existing class materials, I really didn't look that deeply at other people's stuff, because it's not as directly relevant. But that's okay, because the Kettering "Culminating Undergraduate Experience" has a pretty well-defined roadmap.<br />
<br />
The Kettering process begins by a student identifying a project which has the following four characteristics:<br />
* The project is of value to the client<br />
* The project is phrased as a problem, rather than a solution (i.e. the problem will require at least some level of design work to bring the task to completion)<br />
* The project requires the student to use their professional skills (i.e. this isn't just a grunt-work assignment)<br />
* The project can be completed in a reasonable time-frame (typically, 3-6 months of full-time effort)<br />
<br />
So, the first assignment for a Kettering student would be to investigate the project (Mifos in this case, but it really could be anything), with the goal of figuring out a larger task to tackle. The project investigation probably should involve some of the usual on-ramps (simple bug fixes, documentation cleanup, joining the online communities) in order to become a known part of the community. At that point, discussions within the community could evolve to consider what sort of project could be "claimed" by the student.<br />
<br />
Once a project is identified, a further roadmap would be developed, depending on the needs of the project.</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-20T15:38:34Z<p>Jim.huggins: </p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Available information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle<br />
<br />
=== SahanaEden ===<br />
<br />
# ''Community'': less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).<br />
## ''Developers'': full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform<br />
## ''Testers'': less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process<br />
## ''Designers'': even less information, just a few links to areas of design need<br />
# ''Tracker'': main page has various (presumably) common queries of subsets of bugs in the system<br />
## ''Types of tickets'': defect/bug, documentation, enhancement, task<br />
## ''Available information'': ticket number, summary, component, version, priority, type, owner, status, date created<br />
# ''Repository'': again, appears to be a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.<br />
<br />
== FOSS In Courses Activity (Stage 2, Item 4) ==<br />
<br />
Okay, so, in order for this to make sense, you may want to read my [http://jkhuggins.livejournal.com/193067.html blog entry] which describes my intended use case.<br />
<br />
At the moment, I've</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T01:40:54Z<p>Jim.huggins: /* Project Anatomy Activity Responses (Stage 1, Part A, Number 6) */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Available information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle<br />
<br />
=== SahanaEden ===<br />
<br />
# ''Community'': less emphasis on names of contributors, more emphasis on the work to be done (and how to get working on it).<br />
## ''Developers'': full step-by-step instructions on how to join the community, get the development environment, and find tasks to perform<br />
## ''Testers'': less instructions, more lists of project areas to work on. One note on ways for less tech-familiar people to get involved, but less detail on the process<br />
## ''Designers'': even less information, just a few links to areas of design need<br />
# ''Tracker'': main page has various (presumably) common queries of subsets of bugs in the system<br />
## ''Types of tickets'': defect/bug, documentation, enhancement, task<br />
## ''Available information'': ticket number, summary, component, version, priority, type, owner, status, date created<br />
# ''Repository'': again, appears to be a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap has a few milestones with key features noted. Dates appear to be slipping rather dramatically.</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T01:21:48Z<p>Jim.huggins: </p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
=== Sugar Labs ===<br />
<br />
# ''Community'': Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''<br />
## ''Types of tickets'': defect, enhancement, task<br />
## ''Availabile information'': ticket number, summary, status, owner, type, priority, milestone<br />
# ''Repository'': pretty clearly a web-based repository (using Git)<br />
# ''Release Cycle'': roadmap is updated at the beginning of each release cycle</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T01:12:14Z<p>Jim.huggins: /* Project Anatomy Activity Responses (Stage 1, Part A, Number 6) */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
# ''Community'' Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
# ''Tracker''</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T01:11:08Z<p>Jim.huggins: /* Project Anatomy Activity Responses (Stage 1, Part A, Number 6) */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
# ''Community''<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
<p>Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)</p><br />
# ''Tracker''</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T01:10:06Z<p>Jim.huggins: /* Project Anatomy Activity Responses (Stage 1, Part A, Number 6) */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
# ''Community''<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
:: Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
# ''Tracker''</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T01:09:55Z<p>Jim.huggins: /* Project Anatomy Activity Responses (Stage 1, Part A, Number 6) */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
# ''Community''<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
:: Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)<br />
<br />
# ''Tracker''</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T01:09:20Z<p>Jim.huggins: /* Project Anatomy Activity Responses (Stage 1, Part A, Number 6) */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
# ''Community''<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
:: Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T01:08:21Z<p>Jim.huggins: /* Project Anatomy Activity Responses (Stage 1, Part A, Number 6) */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
# ''Community''<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T01:07:35Z<p>Jim.huggins: /* Project Anatomy Activity Responses (Stage 1, Part A, Number 6) */</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
# ''Community''<br />
## ''Activity Team'': 2 coordinators, 13 contributors, mailing list & IRC channel<br />
## ''Development Team'': no coordinators (vacancy noted), 4 contributors, IRC channel<br />
## ''Documentation Team'': no coordinators (vacancy noted), 2 editors, IRC channel<br />
<br />
Seems like things are awfully loosely organized; I suspect more people are involved than those listed. (Or, people suck at updating the membership lists.)</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-08-19T00:58:57Z<p>Jim.huggins: </p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )<br />
<br />
== Project Anatomy Activity Responses (Stage 1, Part A, Number 6) ==<br />
<br />
# ''Community''<br />
## ''Activity Team'':</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-07-25T19:25:56Z<p>Jim.huggins: homework 1-a-5</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.<br />
<br />
== Introduction to IRC Activity Responses (Stage 1, Part A, Number 5) ==<br />
<br />
# ''How do people interact?'' Informally. It appears everyone knows each other on a first-name basis. Lots of references to people not in the chat.<br />
# ''What is the pattern of communication?'' Mostly linear, but with occasionall overlaps due to the nature of distributed chat. (E.g. someone starts a new topic while an old topic is still underway.)<br />
# ''Are there any terms that seem to have special meaning?'' Lots of them ... mostly technical terms dealing with the project at hand.<br />
# ''Can you make any other observations?'' Darci seems to do a nice job of summarizing salient points and decisions made (as should happen in real meetings, even though it doesn't :) )</div>Jim.hugginshttp://foss2serve.org/index.php/POSSE_2015-09_ParticipantsPOSSE 2015-09 Participants2015-07-19T01:58:01Z<p>Jim.huggins: adding Jim Huggins</p>
<hr />
<div>The participants in POSSE 2015-09 are:<br />
<br />
* [[User:Darci.burdge|Darci Burdge]] - email: Darci.Burdge@ncc.edu<br />
* [[User:Josh.dehlinger|Josh Dehlinger]] - email: jdehlinger at towson.edu<br />
* [[User:Heidi.ellis|Heidi Ellis]] - email: ellis at wne.edu, Blog: [https://heidiellis.wordpress.com/ Heidi Ellis' blog]<br />
* [[User:Hislop|Greg Hislop]] - Blog: [http://hislop.wordpress.com/ Notes from Greg Hislop]<br />
* [[User:Jim.huggins|Jim Huggins]] - email: jhuggins@kettering.edu. Blog: [http://jkhuggins.livejournal.com Jim Huggins' blog]<br />
* [[User:Stoney.jackson|Stoney Jackson]] - [http://stoney-jackson.blogspot.com Stoney Jackson's Blog][http://www.foss2serve.org/index.php/Gnome_Accessibility_Group GNOME Accessibility Group]<br />
* [[User:Clif.kussmaul|Clif Kussmaul]] - email: clif@kussmaul.org<br />
* [[User:Lori.postner|Lori Postner]] - email: Lori.Postner@ncc.edu<br />
* [[User:Welch|Joe Welch]] email: jwelch at hartnell.edu, Blog: TBD<br />
<br />
[[Category:POSSE]]</div>Jim.hugginshttp://foss2serve.org/index.php/User:Jim.hugginsUser:Jim.huggins2015-07-19T01:56:16Z<p>Jim.huggins: first home page</p>
<hr />
<div>Jim Huggins is an Associate Professor of Computer Science at [http://www.kettering.edu Kettering University] in Flint, Michigan.<br />
<br />
Jim's research interests include formal methods, computer science education, computing history, and computing ethics. He is also involved with the AP Computer Science A and Computer Science Principles examination communities.<br />
<br />
Jim's outside interests include church life, piano playing, and geocaching.</div>Jim.huggins