<commit_before>Humanitarian Free and Open Source Software 
Spring 2016 – <NAME>
Original Design – Professor <NAME>
Refinements – <NAME>

“Commarch” -- Community Architecture

Open Source Community Characterization Assignment

Working in groups of three or four (formed during class), you are going to look
at FOSS community/project and deduce how that community is organized. You may
also use some of these techniques to assess pre-existing FOSS projects you wish
to contribute to for your term project (highly recommended!)

0.  Choose your team. We'll be doing this in class, and teams must be approved
    by your instructor.

1.  Choose a FOSS Project. You can use distribution package databases or
    OpenHatch.org collect general information on Free/Open Source
    projects (including games!).  Select one active software project
    about which to write.  Have an alternative handy if you find that
    you cannot get much information about your first choice.  Project
    choices must be approved by your instructor.

2.  Follow the instructions included in the "Git By A Bus" repository on Github
    to generate a report on your selected project, available here:
    https://github.com/tomheon/git_by_a_bus

3.  Calculate your project's "Callaway Coefficient of Fail" using the rubric available here:
    http://hfoss-ritigm.rhcloud.com/static/books/tomspotcallaway-howtotellifyourfossprojectisdoomedtofail.pdf

4.  Dig deeper. Provide answers to the following questions:

    If applicable, list or provide links to:
        I.      The project's IRC Channel<commit_msg>slight update to commarch URL<commit_after>Humanitarian Free and Open Source Software 
Spring 2016 – <NAME>
Original Design – Professor <NAME>
Refinements – <NAME>

“Commarch” -- Community Architecture

Open Source Community Characterization Assignment

Working in groups of three or four (formed during class), you are going to look
at FOSS community/project and deduce how that community is organized. You may
also use some of these techniques to assess pre-existing FOSS projects you wish
to contribute to for your term project (highly recommended!)

0.  Choose your team. We'll be doing this in class, and teams must be approved
    by your instructor.

1.  Choose a FOSS Project. You can use distribution package databases or
    OpenHatch.org collect general information on Free/Open Source
    projects (including games!).  Select one active software project
    about which to write.  Have an alternative handy if you find that
    you cannot get much information about your first choice.  Project
    choices must be approved by your instructor.

2.  Follow the instructions included in the "Git By A Bus" repository on Github
    to generate a report on your selected project, available here:
    https://github.com/tomheon/git_by_a_bus

3.  Calculate your project's "Callaway Coefficient of Fail" using the rubric available here:
    http://hfoss-ritjoe.rhcloud.com/static/books/tomspotcallaway-howtotellifyourfossprojectisdoomedtofail.pdf

4.  Dig deeper. Provide answers to the following questions:

    If applicable, list or provide links to:
        I.      The project's IRC Channel
{'fraction_non_alphanumeric': 0.04714016341923319, 'fraction_numerical': 0.0056568196103079825, 'mean_word_length': 3.9968602825745685, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 9, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7212024', 'n_tokens_mistral': 825, 'n_tokens_neox': 793, 'n_words': 423}