Project Evaluation Activity V1

(Difference between revisions)

Jump to: navigation, search

Revision as of 03:46, 25 February 2013

Description	Learners will gain an understanding of the breadth of available FOSS projects. Learners will also gain an understanding of the identifying characteristics of FOSS projects including pattern of contributions, patterns of commits, programming languages used, and more.
Source
Prerequisite Knowledge	Completion of Browsing a Forge Activity or understanding of SourceForge and Ohloh; Understanding of course in which students will be participating in an HFOSS project.
Estimated Time to Completion	60-90 minutes
Learning Objectives	Ability to: 1)Utilize the rubric to identify likely HFOSS projects.
Materials/Environment	Link to SIGCSE paper. Access to Internet/Web and web browser.
Additional Information	Lists of projects
Rights	Licensed CC BY-SA

Describe the rubric and how it is used.

Evaluate viability

Size/Scale/Complexity
1. Go to Ohloh.net, type Mifos into the Search Projects box, Click on Mifos to see the Project Summary page
2. Scroll down to the Community area and calculate the average number of contributors in the last month. The average was 9 so it passed the minimum average number of contributors metric of 6.
3. Go to the Mifos web page and choose Tech Overview from the Contributors tab. From examination of the technology stack, the architecture looks modular and further search shows it is documented elsewhere on the site.
4. Result-Based on the modular design and meeting the minimum average number of contributors metric, the project is scored a 2 for size/scale/complexity.

1. Activity
2. Return to the Mifos project summary page in Ohloh. Scroll to the Activity area on the page.
3. Compute the 12-month average of commits. The 12-month average was about 108, above the minimum average level of commits recommended for activity.
4. Result-Because commits exceed the favorable level of activity for this project it may be a little large/complex. However, still appears manageable, the project is score a 2 for activity.

@@ Line 33: / Line 33: @@
 ##Go to the Mifos web page and choose Tech Overview from the Contributors tab.  From examination of the technology stack, the architecture looks modular and further search shows it is documented elsewhere on the site.
 ##Result-Based on the modular design and meeting the minimum average number of contributors metric, the project is scored a 2 for size/scale/complexity.
+##Activity
+##Return to the Mifos project summary page in Ohloh.  Scroll to the Activity area on the page.
+##Compute the 12-month average of commits.  The 12-month average was about 108, above the minimum average level of commits recommended for activity.
+##Result-Because commits exceed the favorable level of activity for this project it may be a little large/complex.  However, still appears manageable, the project is score a 2 for activity.
+##Community
+##Examine download activity.
+###Go to Sourceforge.net and enter Mifos into the search box.
+###Choose Mifos-Microfinance Open Source from the search results.
+###Click on the number of downloads that is listed on the project page.
+###Change the date range to give a graph of downloads over the last year.
+##Examine mailing list activity.  Return to the Mifos web page.
 ====Part 2-Evaluate Secondary Criteria====