http://foss2serve.org/api.php?action=feedcontributions&user=MSkalak&feedformat=atomFoss2Serve - User contributions [en]2024-03-29T06:07:04ZUser contributionsMediaWiki 1.18.1http://foss2serve.org/index.php/DickinsonFOSSDickinsonFOSS2016-06-17T17:40:41Z<p>MSkalak: Created page with "== Group Participants == Michael Skalak John MacCormick Grant Braught Tim Wahls == HFOSS == We are planning to have Dickinson's senior capstone class students explore HF..."</p>
<hr />
<div>== Group Participants ==<br />
Michael Skalak<br />
<br />
John MacCormick<br />
<br />
Grant Braught<br />
<br />
Tim Wahls<br />
<br />
== HFOSS ==<br />
<br />
We are planning to have Dickinson's senior capstone class students explore HFOSS and participate in an HFOSS project. Currently, we plan to work with the Ushadidi project. <br />
<br />
First semester will mostly be exploring the project and learning FOSS skills, tools, and culture. In the second semester, the students will have a specific part of the project to work on.<br />
<br />
We will hammer out more specifics including activities over the summer. <br />
<br />
== Planning Stage 3 Activities ==<br />
<br />
=== Meetings ===<br />
Lunch meetings Friday at noon.<br />
<br />
===Specific Tasks===<br />
Grant- overall course planning<br />
<br />
Michael- testing plans, homework, exercises, consultation on install tools<br />
<br />
John- extra testing, general consultation, second semester preparation<br />
<br />
Tim- activity planning<br />
<br />
<br />
=== Resources ===<br />
https://www.ushahidi.com/<br />
<br />
John Barr, Alan Ray, John Poritz, TOS website/ mailing list<br />
<br />
<br />
== Other Notes ==<br />
<br />
<br />
Prior related POSSE groups, if any:<br />
<br />
<br />
<br />
<br />
<br />
[[Category:POSSE]]</div>MSkalakhttp://foss2serve.org/index.php/Stage_2_Activities/bugfindingmrsStage 2 Activities/bugfindingmrs2016-06-16T19:07:51Z<p>MSkalak: started writing</p>
<hr />
<div>== Group Participants == <br />
Michael Skalak<br />
Grant Braught<br />
Chris Murphy<br />
Tim Wahls<br />
John MacCormick <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 />
Senior Capstone<br />
<br />
=== Brief description of the activity ===<br />
<br />
Students will start with an exploration of the bug tracker and what goes into a quality bug report. Students review a specific bug previously identified by instructor and reproduce it. They will also examine its characterization in the bug tracker and suggest improvements. <br />
<br />
=== Time you expect the HFOSS activity to take ===<br />
<br />
Two hours + homework<br />
<br />
=== Relationship of this activity to course goals/objectives ===<br />
<br />
Reach out <br />
<br />
=== What students will submit upon completion of the activity ===<br />
<br />
-wiki writeup<br />
<br />
<br />
=== Approach for assessing the student work ===<br />
<br />
Homework assignment practicing these steps on a different bug. <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>MSkalakhttp://foss2serve.org/index.php/User:MSkalakUser:MSkalak2016-06-14T13:35:24Z<p>MSkalak: </p>
<hr />
<div>== Bio ==<br />
<br />
Michael Skalak is Lecturer/Technician in Dickinson College's Department of Mathematics and Computer Science. His interests are in algorithms and pedagogy.<br />
<br />
<br />
== FOSS field trip ==<br />
<br />
=== Part 1, Sourceforge ===<br />
<br />
I looked at the games tab. There are 25247 projects in 15 different languages. The most popular ones are listed at the top of the page. <br />
<br />
For a specific project I examined FreeCiv. It let's you play a Civilization-like game. It's mostly written in C. The project appears very active and had its last release in February. It was unclear how to tell the number or type of committers. <br />
<br />
=== Part 2, OpenHub ===<br />
<br />
OpenMRS is primarily in Java. It has 3.7m lines of code. The second most used language is Javascript. Of the top three languages, Java has the most comments at 32%. There are about 25 commits/month and 10 contributors/month. The top contributors have been with the project for more than 5 years, 5 years, and 2 years.<br />
<br />
<br />
== FOSS In Courses Activity ==<br />
<br />
My algorithms course is a writing requirement course, meaning that students are expected to produce and edit 15 pages of technical writing in the discipline. In the past, I have had them create or edit Wikipedia articles as an option for the assignment. I would like to add writing documentation for a FOSS project as an option as well. This might be a difficult to do as writing that amount of documentation could be prohibitively difficult, particularly for a project that they are unfamiliar with. I'm going to continue thinking about ways to effectively try this idea as I go through the POSSE workshop.<br />
<br />
<br />
==Bug activity==<br />
<br />
===Bug examination=== <br />
<br />
2. <br />
a. ID- A unique identifying number<br />
b. Sev- Severity (blocker, critical, major, normal, minor, trivial, enhancement)<br />
c. Pri- Priority (Immediate, Urgent, High, Normal, Low)<br />
d. OS- Operating System (All, AIX, BSDI, Cygwin, GNU Hurd, HP-UX, IRIX, Linux, FreeBSD, NetBSD, OpenBSD, opensolaris, OSF/1, Solaris, BeOS, Mac OS, Neutrino, OS/2, Windows, OpenVMS, other)<br />
e. Product- The part of the program that is broken (many options)<br />
f. Status- current situation for bug (NEW, ASSIGNED, REOPENED, NEEDINFO, RESOLVED, VERIFIED)<br />
g. Resolution- How the bug was addressed<br />
h. Summary- description of bug<br />
<br />
3. I found the information from the advanced search.<br />
<br />
4. They are sorted by status and then assignee.<br />
5. I could not find a pattern for shaded bugs.<br />
6. Color indicates severity. For example, there is a red bug where it crashes when trying to print a pdf.<br />
7. <br />
I'm examining bug 349190<br />
It was submitted July 29th, 2006. The last discussion was June 15th, 2014. The bug is listed as "NEED", presumably because the developers want more information. It's not assigned. To fix the bug, I would need to find where and how the color scheming is coded and change it to be more flexible. The bug report suggests using theme colors.<br />
<br />
===Collective reports===<br />
<br />
3. 286 were opened and 329 were closed.<br />
4. The general trend had more closed than opened.<br />
5. Michael Gratton, Matthias Clasen, and Bastien Nocera. This lets you know who the active contributors are.<br />
6. Bastien Nocera, Alexandre Franke, Simon McVittie. They're not the same, though Nocera is on both lists.<br />
7. Bastien Nocera, slomo, and Rui Matos.<br />
8. slomo, Nocera, and stormer<br />
11. I generated the report for ocr. The majority of the bugs were "normal" for both the UI and "general".<br />
<br />
==FOSS in courses 2==<br />
I would like to include a FOSS option in the writing assignment for the algorithms course. As a requirement for the course, the students must produce 15 pages of revised technical writing. It also must algorithms-related, which I judge on a case-by-case basis. In the past, I have offered the option of creating or substantially editing a Wikipedia article on an appropriate topic. For this project, I think the best option would be having the student document a particular algorithm employed by a project, including what the algorithm does, how it works, what options could have been chosen, and why this particular algorithm was selected. <br />
<br />
Prerequisite knowledge:<br />
<br />
1. Need to know something about the project and its algorithmic basis. <br />
<br />
2. Probably other stuff, but number 1 is vague enough to cover most things.<br />
<br />
<br />
Time<br />
<br />
1. Instructor prep time should be relatively low. I probably should also know something about the algorithm, which would take more time if they select something I haven't seen before.<br />
<br />
2. The students will need quite a bit of time on the project. They know about the assignment in general at the beginning of the course, and give more explicit instructions about a month before it's due. It is probably not particularly dependent on the HFOSS community schedule.<br />
<br />
Input from community<br />
<br />
1. The project will not require a lot of input from the FOSS community. Some background on the algorithm would be appreciated, but not necessary.<br />
<br />
Contribution<br />
<br />
1. The writing could form part of the documentation for the project.<br />
<br />
Assessment<br />
<br />
1. Assessment could be tricky. I have a generic writing rubric that I would use, but that could be insufficient given the variety of projects. A student must individually complete the writing. <br />
<br />
Questions/Concerns/Stumbling blocks<br />
<br />
1. Finding an appropriate algorithm/project to write about.</div>MSkalakhttp://foss2serve.org/index.php/User:MSkalakUser:MSkalak2016-06-09T16:14:35Z<p>MSkalak: </p>
<hr />
<div>== Bio ==<br />
<br />
Michael Skalak is Lecturer/Technician in Dickinson College's Department of Mathematics and Computer Science. His interests are in algorithms and pedagogy.<br />
<br />
<br />
== FOSS field trip ==<br />
<br />
=== Part 1, Sourceforge ===<br />
<br />
I looked at the games tab. There are 25247 projects in 15 different languages. The most popular ones are listed at the top of the page. <br />
<br />
For a specific project I examined FreeCiv. It let's you play a Civilization-like game. It's mostly written in C. The project appears very active and had its last release in February. It was unclear how to tell the number or type of committers. <br />
<br />
=== Part 2, OpenHub ===<br />
<br />
OpenMRS is primarily in Java. It has 3.7m lines of code. The second most used language is Javascript. Of the top three languages, Java has the most comments at 32%. There are about 25 commits/month and 10 contributors/month. The top contributors have been with the project for more than 5 years, 5 years, and 2 years.<br />
<br />
<br />
== FOSS In Courses Activity ==<br />
<br />
My algorithms course is a writing requirement course, meaning that students are expected to produce and edit 15 pages of technical writing in the discipline. In the past, I have had them create or edit Wikipedia articles as an option for the assignment. I would like to add writing documentation for a FOSS project as an option as well. This might be a difficult to do as writing that amount of documentation could be prohibitively difficult, particularly for a project that they are unfamiliar with. I'm going to continue thinking about ways to effectively try this idea as I go through the POSSE workshop.<br />
<br />
<br />
==Bug activity==<br />
<br />
===Bug examination=== <br />
<br />
2. <br />
a. ID- A unique identifying number<br />
b. Sev- Severity (blocker, critical, major, normal, minor, trivial, enhancement)<br />
c. Pri- Priority (Immediate, Urgent, High, Normal, Low)<br />
d. OS- Operating System (All, AIX, BSDI, Cygwin, GNU Hurd, HP-UX, IRIX, Linux, FreeBSD, NetBSD, OpenBSD, opensolaris, OSF/1, Solaris, BeOS, Mac OS, Neutrino, OS/2, Windows, OpenVMS, other)<br />
e. Product- The part of the program that is broken (many options)<br />
f. Status- current situation for bug (NEW, ASSIGNED, REOPENED, NEEDINFO, RESOLVED, VERIFIED)<br />
g. Resolution- How the bug was addressed<br />
h. Summary- description of bug<br />
<br />
3. I found the information from the advanced search.<br />
<br />
4. They are sorted by status and then assignee.<br />
5. I could not find a pattern for shaded bugs.<br />
6. Color indicates severity. For example, there is a red bug where it crashes when trying to print a pdf.<br />
7. <br />
I'm examining bug 349190<br />
It was submitted July 29th, 2006. The last discussion was June 15th, 2014. The bug is listed as "NEED", presumably because the developers want more information. It's not assigned. To fix the bug, I would need to find where and how the color scheming is coded and change it to be more flexible. The bug report suggests using theme colors.<br />
<br />
===Collective reports===<br />
<br />
3. 286 were opened and 329 were closed.<br />
4. The general trend had more closed than opened.<br />
5. Michael Gratton, Matthias Clasen, and Bastien Nocera. This lets you know who the active contributors are.<br />
6. Bastien Nocera, Alexandre Franke, Simon McVittie. They're not the same, though Nocera is on both lists.<br />
7. Bastien Nocera, slomo, and Rui Matos.<br />
8. slomo, Nocera, and stormer<br />
11. I generated the report for ocr. The majority of the bugs were "normal" for both the UI and "general".</div>MSkalakhttp://foss2serve.org/index.php/User:MSkalakUser:MSkalak2016-06-09T16:14:13Z<p>MSkalak: </p>
<hr />
<div>== Bio ==<br />
<br />
Michael Skalak is Lecturer/Technician in Dickinson College's Department of Mathematics and Computer Science. His interests are in algorithms and pedagogy.<br />
<br />
<br />
== FOSS field trip ==<br />
<br />
=== Part 1, Sourceforge ===<br />
<br />
I looked at the games tab. There are 25247 projects in 15 different languages. The most popular ones are listed at the top of the page. <br />
<br />
For a specific project I examined FreeCiv. It let's you play a Civilization-like game. It's mostly written in C. The project appears very active and had its last release in February. It was unclear how to tell the number or type of committers. <br />
<br />
=== Part 2, OpenHub ===<br />
<br />
OpenMRS is primarily in Java. It has 3.7m lines of code. The second most used language is Javascript. Of the top three languages, Java has the most comments at 32%. There are about 25 commits/month and 10 contributors/month. The top contributors have been with the project for more than 5 years, 5 years, and 2 years.<br />
<br />
<br />
== FOSS In Courses Activity ==<br />
<br />
My algorithms course is a writing requirement course, meaning that students are expected to produce and edit 15 pages of technical writing in the discipline. In the past, I have had them create or edit Wikipedia articles as an option for the assignment. I would like to add writing documentation for a FOSS project as an option as well. This might be a difficult to do as writing that amount of documentation could be prohibitively difficult, particularly for a project that they are unfamiliar with. I'm going to continue thinking about ways to effectively try this idea as I go through the POSSE workshop.<br />
<br />
<br />
==Bug activity==<br />
<br />
=Bug examination= <br />
<br />
2. <br />
a. ID- A unique identifying number<br />
b. Sev- Severity (blocker, critical, major, normal, minor, trivial, enhancement)<br />
c. Pri- Priority (Immediate, Urgent, High, Normal, Low)<br />
d. OS- Operating System (All, AIX, BSDI, Cygwin, GNU Hurd, HP-UX, IRIX, Linux, FreeBSD, NetBSD, OpenBSD, opensolaris, OSF/1, Solaris, BeOS, Mac OS, Neutrino, OS/2, Windows, OpenVMS, other)<br />
e. Product- The part of the program that is broken (many options)<br />
f. Status- current situation for bug (NEW, ASSIGNED, REOPENED, NEEDINFO, RESOLVED, VERIFIED)<br />
g. Resolution- How the bug was addressed<br />
h. Summary- description of bug<br />
<br />
3. I found the information from the advanced search.<br />
<br />
4. They are sorted by status and then assignee.<br />
5. I could not find a pattern for shaded bugs.<br />
6. Color indicates severity. For example, there is a red bug where it crashes when trying to print a pdf.<br />
7. <br />
I'm examining bug 349190<br />
It was submitted July 29th, 2006. The last discussion was June 15th, 2014. The bug is listed as "NEED", presumably because the developers want more information. It's not assigned. To fix the bug, I would need to find where and how the color scheming is coded and change it to be more flexible. The bug report suggests using theme colors.<br />
<br />
=Collective reports=<br />
<br />
3. 286 were opened and 329 were closed.<br />
4. The general trend had more closed than opened.<br />
5. Michael Gratton, Matthias Clasen, and Bastien Nocera. This lets you know who the active contributors are.<br />
6. Bastien Nocera, Alexandre Franke, Simon McVittie. They're not the same, though Nocera is on both lists.<br />
7. Bastien Nocera, slomo, and Rui Matos.<br />
8. slomo, Nocera, and stormer<br />
11. I generated the report for ocr. The majority of the bugs were "normal" for both the UI and "general".</div>MSkalakhttp://foss2serve.org/index.php/Intro_to_Bug_Trackers_(Activity)Intro to Bug Trackers (Activity)2016-06-09T16:07:44Z<p>MSkalak: /* Part 2 - Collective Reports */</p>
<hr />
<div>__NOTOC__<br />
{| border="1"<br />
|- <br />
|'''Title''' ||Bug Trackers<br />
|-<br />
|'''Overview''' || Learners will gain an understanding of the features of bug trackers and how they are used to identify work items to be completed in a FOSS project. <br />
|- <br />
|'''Prerequisite Knowledge''' || None<br />
|-<br />
|'''Learning Objectives''' || Ability to: 1) Describe the role that a bug tracker plays in a FOSS project, 2) Describe the different types of issues stored in a bug tracker and their priorities, and 3) Identify and track the status of a particular bug in a project. <br />
|}<br />
<br />
<br />
=== Background: ===<br />
Bug tracking systems are a form of change management and organization used by FOSS projects. Bug trackers do far more than simply keep track of bugs. They also are used to hold new feature requests, patches, and some tasks. Bug trackers are also called request trackers, issue trackers, request trackers and ticket systems. Please read the two readings below for a more complete treatment of bug trackers and their use in FOSS projects.<br />
<br />
* [http://producingoss.com/en/bug-tracker.html Karl Fogel's chapter on bug trackers]<br />
* [http://en.wikipedia.org/wiki/Bug_tracking_system Wikipedia's page on Bug Tracking Systems]<br />
<br />
=== Directions: ===<br />
We will begin by looking at a typical Bugzilla instance for a project. We will be using GNOME's Bugzilla instance, but specifically looking at the bugs for the Accessibility Team. <br />
<br />
== Part 1 - Bug Reports ==<br />
# Open a browser and go to the [https://bugzilla.gnome.org/buglist.cgi?type0-7-0=notequals;field0-3-0=product;keywords=accessibility;type0-1-0=notequals;type0-5-0=notequals;keywords_type=allwords;value0-5-0=accerciser;value0-4-0=at-poke;field0-1-0=product;field0-0-0=product;type0-4-0=notequals;field0-6-0=product;value0-3-0=gnome-mag;field0-7-0=product;query_format=advanced;value0-2-0=Dasher;value0-6-0=gnome-speech;value0-1-0=Gok;type0-3-0=notequals;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;bug_status=NEEDINFO;field0-2-0=product;field0-5-0=product;field0-4-0=product;type0-6-0=notequals;type0-0-0=notequals;value0-0-0=Orca;type0-2-0=notequals GNOME Accessibility Bugs]<br />
# Define what each of the column names below indicate. Include the range of possible values for 2-7 below. Feel free to explore beyond the page to find more information.<br />
## ID <br />
## Sev <br />
## Pri<br />
## OS <br />
## Product <br />
## Status <br />
## Resolution <br />
## Summary <br />
# Describe how you discovered the definitions and how did you find the information from above (hint: the advanced search shows the options or the Reports link has a link)? <br />
# Identify the order in which the bugs are initially displayed?<br />
# What is the meaning of the shading of some bug reports?<br />
# What is the meaning of the colors used when describing a bug (red, gray, black)?<br />
# Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number). <br />
## Identify when the bug was submitted.<br />
## Identify if there has been recent discussion about the bug?<br />
## Is the bug current?<br />
## Is the bug assigned? To whom?<br />
## Describe what you would need to do to fix the bug. <br />
# Repeat the previous step with a different kind of bug.<br />
<br />
== Part 2 - Collective Reports ==<br />
# Click on the “Reports” link on the top of the page.<br />
# Click on the "Summary of Bug Activity for the last week".<br />
# How many bug reports were opened in the last week? How many were closed?<br />
# What was the general trend last week? Were more bugs opened than closed or vice versa?<br />
# Who were the top three bug closers? Why is this important to know?<br />
# Who were the top three bug reporters? Are these the same as the top three bug closes? What is the overlap in these two lists?<br />
# Who are the top three contributors of patches?<br />
# Who are the top three reviewers of patches? What is the overlap between these lists and the bug closers and bug reporters? What is the overlap between patch contributors and patch reviewers?<br />
# Click on the “Generate Graphical Reports” link.<br />
# Plot a line graph of the severity of bugs by component for Orca:<br />
## Select "Severity" for the vertical axis<br />
## Select "Component" for the horizontal axis<br />
## Select "Bar Graph" for type of graph<br />
## Leave the "Multiple Images" as <none><br />
## Scroll down and select Orca from the Product menu. <br />
## Click "Generate Report". <br />
# What class were the majority of the bugs for braille?<br />
# What other reports can you generate?<br />
<br />
<br />
===Deliverables: ===<br />
Wiki posting describing the results of your exploration below. <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''' || 60 Minutes<br />
|-<br />
|'''Materials/Environment''' || Access to Internet/Web and web browser. <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''' || Licensed CC BY-SA <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 />
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 />
<br />
[[Category:Communication_and_Tools]]</div>MSkalakhttp://foss2serve.org/index.php/POSSE_2016-06_ParticipantsPOSSE 2016-06 Participants2016-06-08T19:43:46Z<p>MSkalak: </p>
<hr />
<div>The participants in POSSE 2016-06 are:<br />
* [[User:JBarr|John Barr]] -email:barr@ithaca.edu [https://ithacathoughts.wordpress.com John's Blog]<br />
* [[User:GBraught|Grant Braught]] - Dickinson College - [http://www.google.com/recaptcha/mailhide/d?k=0149I7Mrv37UX2n3ob1zgzLQ==&c=0Fr94EE5lN45A4B1hv2MIFX4pxDJ6WLieyzb_Z_M-2I= email] - [http://gbposse16.tumblr.com/ Blog]<br />
* [[User:Darci.burdge|Darci Burdge]] - email: Darci.Burdge@ncc.edu<br />
* [[User:Afchernik|Aria Chernik]] - email: aria.chernik@duke.edu, [http://ariachernik.com/teachinglearning/ Blog]<br />
* [[User:JDavis|Janet Davis]] - email: davisj@whitman.edu, Blog: [http://blogs.whitman.edu/countingfromzero/ Counting From Zero]<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: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:LLi|Jiang (Leo) Li]] - email: lij at scs dot howard.edu<br />
* [[User:Glikins|Gina Likins]] email: gina at redhat.com [http://www.lintqueen.com/ Gina's blog]<br />
* [[User:YLiu|Ying Liu]] email: liuy1 at stjohns.edu [https://liuy12014.wordpress.com/ Ying's Blog]<br />
* [[User:JMac|John MacCormick]] - email: jmac@dickinson.edu, [https://posse2016jmac.wordpress.com/ blog]<br />
* [[User:JPoritz|Jonathan Poritz]] - email: jonathan.poritz@gmail.com, [http://mathematikoi.net/ blog]<br />
* [[User:Lori.postner|Lori Postner]] - email: Lori.Postner@ncc.edu<br />
* [[User:Alan.rea|Alan Rea]] - [http://www.google.com/recaptcha/mailhide/d?k=01xHuLnJJKDBxfDBAP7OIYqA==&c=cwfVYW5MX4uUfsHJbKIAZA== email] [http://foss.docrea.org blog]<br />
* [[User:GSena|Giuseppe (Tony) Sena]] - email: gsena@massbay.edu - [https://gsenafoss.wordpress.com/ Tony's Blog] - [http://www.massbay.edu/Faculty-Profiles/Giuseppe-Sena.aspx Tony's MassBay Profile]<br />
* [[User:MSkalak|Michael Skalak]] - email: skalakm at dickinson dot edu [https://packagecontainedbobcat.wordpress.com/ blog]<br />
* [[User:DSkrien|Dale Skrien]] - email: djskrien at colby.edu, Blog: [https://daleskrien.wordpress.com/ Dale Skrien's blog]<br />
* [[User:GThomas|George Thomas]] - email: thomasg at uwosh.edu, [https://gt3267.wordpress.com/ George's blog]<br />
* [[User:TWahls|Tim Wahls]] - [http://www.google.com/recaptcha/mailhide/d?k=0149I7Mrv37UX2n3ob1zgzLQ==&c=RyjPuSJHG7MfCjTLMTHOQds0sOnl2Ah8w9rvQxVqfXM= email] [https://wahlst.wordpress.com/ blog]<br />
* [[User:SWeiss|Stewart Weiss]] -email:stewart.weiss at hunter.cuny.edu [https://musingsonteaching.wordpress.com Stewart's blog]<br />
* [[User:GIsern|Germinal Isern]] -email: gisern@massbay.edu-[https://example61268.wordpress.com/ Germinal's blog POSSE]-[ [https://sites.google.com/site/germinalisernqccnsp]<br />
<br />
<br />
[[Category:POSSE]]</div>MSkalakhttp://foss2serve.org/index.php/User:MSkalakUser:MSkalak2016-05-25T17:18:14Z<p>MSkalak: added foss in course activity section</p>
<hr />
<div>== Bio ==<br />
<br />
Michael Skalak is Lecturer/Technician in Dickinson College's Department of Mathematics and Computer Science. His interests are in algorithms and pedagogy.<br />
<br />
<br />
== FOSS field trip ==<br />
<br />
=== Part 1, Sourceforge ===<br />
<br />
I looked at the games tab. There are 25247 projects in 15 different languages. The most popular ones are listed at the top of the page. <br />
<br />
For a specific project I examined FreeCiv. It let's you play a Civilization-like game. It's mostly written in C. The project appears very active and had its last release in February. It was unclear how to tell the number or type of committers. <br />
<br />
=== Part 2, OpenHub ===<br />
<br />
OpenMRS is primarily in Java. It has 3.7m lines of code. The second most used language is Javascript. Of the top three languages, Java has the most comments at 32%. There are about 25 commits/month and 10 contributors/month. The top contributors have been with the project for more than 5 years, 5 years, and 2 years.<br />
<br />
<br />
== FOSS In Courses Activity ==<br />
<br />
My algorithms course is a writing requirement course, meaning that students are expected to produce and edit 15 pages of technical writing in the discipline. In the past, I have had them create or edit Wikipedia articles as an option for the assignment. I would like to add writing documentation for a FOSS project as an option as well. This might be a difficult to do as writing that amount of documentation could be prohibitively difficult, particularly for a project that they are unfamiliar with. I'm going to continue thinking about ways to effectively try this idea as I go through the POSSE workshop.</div>MSkalakhttp://foss2serve.org/index.php/Stage2_GroupsStage2 Groups2016-05-25T17:07:47Z<p>MSkalak: /* Courses */</p>
<hr />
<div>'''Instructions:''' Please sign up for one project and one course below:<br />
<br />
== Projects ==<br />
=== Ushahidi ===<br />
<br />
* Aria Chernik<br />
<br />
=== OpenMRS ===<br />
<br />
* Tim Wahls<br />
* John MacCormick<br />
* Stewart Weiss<br />
* Tom Naps<br />
* Dale Skrien<br />
* Michael Skalak<br />
<br />
=== MouseTrap ===<br />
<br />
* Germinal Isern<br />
* Tony Sena<br />
<br />
== Courses ==<br />
=== CS1 ===<br />
=== CS2/Data Structures ===<br />
* Stewart Weiss<br />
<br />
=== Software Engineering/Capstone ===<br />
* Tim Wahls<br />
* John MacCormick<br />
* Janet Davis<br />
<br />
=== Stand-alone HFOSS/Openness ===<br />
<br />
* Aria Chernik<br />
<br />
=== Object-Oriented Design ===<br />
* Dale Skrien<br />
<br />
<br />
=== Algorithms ===<br />
* Michael Skalak</div>MSkalakhttp://foss2serve.org/index.php/Stage2_GroupsStage2 Groups2016-05-25T17:07:18Z<p>MSkalak: /* OpenMRS */</p>
<hr />
<div>'''Instructions:''' Please sign up for one project and one course below:<br />
<br />
== Projects ==<br />
=== Ushahidi ===<br />
<br />
* Aria Chernik<br />
<br />
=== OpenMRS ===<br />
<br />
* Tim Wahls<br />
* John MacCormick<br />
* Stewart Weiss<br />
* Tom Naps<br />
* Dale Skrien<br />
* Michael Skalak<br />
<br />
=== MouseTrap ===<br />
<br />
* Germinal Isern<br />
* Tony Sena<br />
<br />
== Courses ==<br />
=== CS1 ===<br />
=== CS2/Data Structures ===<br />
* Stewart Weiss<br />
<br />
=== Software Engineering/Capstone ===<br />
* Tim Wahls<br />
* John MacCormick<br />
* Janet Davis<br />
<br />
=== Stand-alone HFOSS/Openness ===<br />
<br />
* Aria Chernik<br />
<br />
=== Object-Oriented Design ===<br />
* Dale Skrien</div>MSkalakhttp://foss2serve.org/index.php/User:MSkalakUser:MSkalak2016-05-25T16:36:29Z<p>MSkalak: </p>
<hr />
<div>== Bio ==<br />
<br />
Michael Skalak is Lecturer/Technician in Dickinson College's Department of Mathematics and Computer Science. His interests are in algorithms and pedagogy.<br />
<br />
<br />
== FOSS field trip ==<br />
<br />
=== Part 1, Sourceforge ===<br />
<br />
I looked at the games tab. There are 25247 projects in 15 different languages. The most popular ones are listed at the top of the page. <br />
<br />
For a specific project I examined FreeCiv. It let's you play a Civilization-like game. It's mostly written in C. The project appears very active and had its last release in February. It was unclear how to tell the number or type of committers. <br />
<br />
=== Part 2, OpenHub ===<br />
<br />
OpenMRS is primarily in Java. It has 3.7m lines of code. The second most used language is Javascript. Of the top three languages, Java has the most comments at 32%. There are about 25 commits/month and 10 contributors/month. The top contributors have been with the project for more than 5 years, 5 years, and 2 years.</div>MSkalakhttp://foss2serve.org/index.php/POSSE_2016-06_ParticipantsPOSSE 2016-06 Participants2016-05-06T20:07:32Z<p>MSkalak: </p>
<hr />
<div>The participants in POSSE 2016-06 are:<br />
* [[User:JBarr|John Barr]] -email:barr@ithaca.edu [http://foss2serve.org/index.php/User:JBarr John's Blog]<br />
* [[User:GBraught|Grant Braught]] - [http://www.google.com/recaptcha/mailhide/d?k=0149I7Mrv37UX2n3ob1zgzLQ==&c=0Fr94EE5lN45A4B1hv2MIFX4pxDJ6WLieyzb_Z_M-2I= email] - Dickinson College<br />
* [[User:Darci.burdge|Darci Burdge]] - email: Darci.Burdge@ncc.edu<br />
* [[User:JDavis|Janet Davis]] - email: davisj@whitman.edu, Blog: [http://blogs.whitman.edu/countingfromzero/ Counting From Zero]<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: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:LLi|Jiang (Leo) Li]] - email: lij at scs dot howard.edu<br />
* [[User:Glikins|Gina Likins]] email: gina at redhat.com [http://www.lintqueen.com/ Gina's blog]<br />
* [[User:JMac|John MacCormick]] - email: jmac@dickinson.edu<br />
* [[User:JPoritz|Jonathan Poritz]] - email: jonathan.poritz@gmail.com<br />
* [[User:Lori.postner|Lori Postner]] - email: Lori.Postner@ncc.edu<br />
* [[User:Alan.rea|Alan Rea]] - [http://www.google.com/recaptcha/mailhide/d?k=01xHuLnJJKDBxfDBAP7OIYqA==&c=cwfVYW5MX4uUfsHJbKIAZA== email] [http://foss.docrea.org blog]<br />
* [[User:MSkalak|Michael Skalak]] - email: skalakm at dickinson dot edu<br />
* [[User:DSkrien|Dale Skrien]] - email: djskrien at colby.edu<br />
* [[User:GThomas|George Thomas]] - email: thomasg at uwosh.edu<br />
* [[User:TWahls|Tim Wahls]] - [http://www.google.com/recaptcha/mailhide/d?k=0149I7Mrv37UX2n3ob1zgzLQ==&c=RyjPuSJHG7MfCjTLMTHOQds0sOnl2Ah8w9rvQxVqfXM= email]<br />
<br />
[[Category:POSSE]]</div>MSkalakhttp://foss2serve.org/index.php/User:MSkalakUser:MSkalak2016-05-02T17:47:35Z<p>MSkalak: Created page with "Michael Skalak is Lecturer/Technician in Dickinson College's Department of Mathematics and Computer Science. His interests are in algorithms and pedagogy."</p>
<hr />
<div>Michael Skalak is Lecturer/Technician in Dickinson College's Department of Mathematics and Computer Science. His interests are in algorithms and pedagogy.</div>MSkalak