User:Morgan

(Difference between revisions)
Jump to: navigation, search
(License)
Line 254: Line 254:
 
[[File:MPL.png|600px|thumb|left|<div align="left">'''Mozilla Public License 2.0 Can, Cannots, and Musts'''</div> ]]
 
[[File:MPL.png|600px|thumb|left|<div align="left">'''Mozilla Public License 2.0 Can, Cannots, and Musts'''</div> ]]
 
[[File:Apache.png|600px|thumb|left|<div align="left">'''Apache 2.0 Can, Cannots, and Musts'''</div> ]]
 
[[File:Apache.png|600px|thumb|left|<div align="left">'''Apache 2.0 Can, Cannots, and Musts'''</div> ]]
 +
 +
I would be comfortable using either Apache or MPL
 +
 +
==FOSS in Courses==
 +
I already teach a full FOSS course. I am looking at new assignments on foss2serve to replace some of my outdated assignments.
 +
 +
==Intro to Bug Trackers==
 +
===Part 1 - Bug Reports ===
 +
#  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.
 +
## ID
 +
## Sev
 +
## Pri
 +
## OS
 +
## Product
 +
## Status
 +
## Resolution
 +
## Summary
 +
# 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).
 +
# Identify the order in which the bugs are initially displayed.
 +
# What is the meaning of the colors used when describing a bug (red, gray, black)? (Hint: click on the Bug ID and examine the fields)
 +
# Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).
 +
## Identify when the bug was submitted.
 +
## Identify if there has been recent discussion about the bug?
 +
## Is the bug current?
 +
## Is the bug assigned? To whom?
 +
## Describe what you would need to do to fix the bug.
 +
# Repeat the previous step with a different kind of bug.
 +
 +
[edit]
 +
 +
===Part 2 - Collective Reports ===

Revision as of 22:08, 15 April 2017

Contents

Becka Morgan

Becka Morgan is currently an Associate Professor at Western Oregon University (WOU)in the lovely metropolis of Monmouth Oregon.

Quick Facts about WOU

  • Year founded 1856
  • Total enrollment 5,382
  • Number of undergraduate students 4,833
  • Number of graduate students 549
  • Location Monmouth, Oregon
  • Miles from Salem 16
  • Miles from Portland 63
    Western Oregon University Campus
    ClipartFest
  • Campus size (acres) 157
  • Most popular majors
    • Business
    • Criminal Justice
    • Education
    • Exercise Science
    • Psychology
  • Student-to-faculty ratio 18:1
  • Average class size 18
  • Average high school GPA 3.2 (unweighted)
  • Acceptance rate 88%
  • Geographic origins of undergraduate students
    • In-state: 75%
    • Out-of-state: 21%
    • International: 4%
  • Gender distribution 35% men 65% women
  • Students of color 27%
  • Number of clubs and student organizations 62
  • Athletics NCAA Division II
  • Great Northwest Athletic Conference
  • Mascot Wolf
  • School colors Red, Black, White (primary), Gray (secondary)

IRC

  1. How do people interact?
Using short, abbreviated phrases. The way we talk.
  1. What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix?
Communication is informal, without caps or punctuation. There is both linear and branched in different places. At times there is a back and forth on one topic with several two or more people, then there are places when there are multiple conversations happening at once.
  1. Are there any terms that seem to have special meaning?
The commands given by the bot at the beginning of the meeting: Useful Commands: #action #agreed #help #info #idea #link #topic.
  1. Can you make any other observations?
IRC is very conversational

Guided Tour

Sugar Labs

Contributions

  • Summarize the roles that you think would be most applicable for your students.
    • Content Writer - This is a good place to teach someone through tutorials created by students, study the code and work with the documentation team, or work on translation for International students
    • People Person - many students feel intimidated at first and enter the community by marketing and spreading the word. This is a great place to teach students that code is not the only valuable contribution.
    • Developer - Writing source code is a great experience and having access to mentors is a great way to ease students into writing patches.
    • Designer - We have a lot of students who take visual communication design and either double major or minor with computer science. This would be a great place for them.
    • Translator - Same as with Content Writer. This is good for International students
  • What are the commonalities across roles?
    • There are cross over in the teams that use people from various roles.
  • What are the differences?
    • The skill sets used in the various roles are different. This leads to different areas to pursue by people with different roles in the same teams or projects.

Tracker

  • Describe the general process for submitting a bug report
    • Reading How to report Bugs Effectively is a good starting place.
    • Log into GitHub
    • Then visit the issues tab of the repo that contains the code with your issue, and hit the big green button to report your issue.
  • Indicate the types/categories of tickets listed on this page as well as the information available for each ticket.
    • The categories for the BugTracker are the ticket number, summary of the bug, status, who owns the bug, what the bug type is, its priority, and milestone for the project.
    • Each ticket has information about details of the bug report -
      • Reported by, Owned by, Priority, Milestone, Component, Version, Severity, Keywords, Cc, Distribution/OS, Bug Status
    • A Description
    • A Change History which contains links to pull requests and the comments associated with the submitted patch if there is one.

Repository

  • Date of the last commit - Feb 5, 2017

Release cycle

  • Describe how the release cycle and roadmap update are related.
    • The section about the release cycle covered what a release cycle is and defined terminology. The roadmap was the details for a specific release.

Communication

The Sahana Eden Project (https://sahanafoundation.org/eden/)

Community

  • Developers -
    • To get started, you should:
    • Join our Mailing List to say Hi and introduce yourself to the community!
    • Follow the Sahana Eden Virtual Technical Training either through the published slides, watching a recorded training sessions or a attending a live session.
    • Install a Developers Environment
    • Read our Developer Guidelines
    • Sign the Contributor's License Agreement - this says you retain all rights to your code, while allowing us to distribute it and users to use it.
    • You are welcome to go ahead work on any of tasks, tickets or projects on the Contribute Code page. It may be worth doing some initial Please feel free to contact the Mailing List to let us know what you're working on or if your have any specific questions, but this is probably more valuable once you've investigated the work yourself.
  • Testers -
    • MANUAL
      • It is possible for non-technical users to assist with the QA process for Sahana by performing manual testing & documenting new Test Cases:
        • Test Cases
      • If you find any issues, please report them following the Bug Reporting Guidelines.
    • DEVELOPERS
      • Developers who wish to check if their changes have broken anything or who wish to write tests for their new code should look here:
        • DeveloperGuidelines/Testing
    • CONTINUOUS INTEGRATION
      • SysAdmins who wish to help with Sahana's CI server or setup one of their own can look for details here:
        • Continuous Integration
    • SEE ALSO
      • Bug Reporting Guidelines
  • Designers -
    • We can always use input from Graphic Designers on what could make our sites look nicer & more usable:
      • The Application
      • The Websites
    • Ideally this help would be in the form of CSS and HTML, but any help is welcomed :)
    • Ideas for tasks here:
      • Projects/Design
    • Guidelines:
      • DeveloperGuidelines/Themes
      • DeveloperGuidelines/Usability
  1. Are there any commonalities?
    All three communities have a great deal of information specific to the sub community. There are also guidelines for all communities as well as links to ways to contribute.
  2. Is there something distinct for each type of contributor?
    The ways in which contributions are made varies.
  3. How is this structure different than the one you found on the Sugar Labs website?
    SugarLabs website is more simplistic, but when you click on a role there is an overwhelming amount of information. Sahana's links are more modularized. each page has a distinct focus without an overwhelming amount of information.

Tracker

  • How is the information here different than the information found on the Sugar Labs tracker page?
    • SugarLabs is less intuitive. Everything is listed together. SugarLabs requires you to query. Sahana has categories that provide you with the bugs you are searching for.
  • Click the Active Tickets link. Indicate the types/categories of tickets listed on this page as well as the information available for each ticket.
    • The types of tickets are:
      • Defect/Bug,
      • Documentation,
      • Enhancement, or
      • Task.
    • The information available for each ticket is:
      • Ticket,
      • Summary,
      • Component,
      • Version,
      • Priority,
      • Type,
      • Owner,
      • Status, and
      • Created.

Repository

  • Date of the last commit - Mar 31, 2017

Release cycle

  • There appear to be three different versions in various stages of completion, this version 0.9 reporting that it is 5 years late. There is a visual of the completion percentage of each stage. The road map is not very clear to an outsider.

Communication

FOSS Field Trip

GitHub

  1. Use the Search feature on the top right next to the Log In button to search for educational applications by placing the word education in the search box and click Search.
    1. How many repositories are there in this category?
      12,290 repository results
    2. Click on the first project. Click on Graphs, then Commits. What information does this page provide?
      It is the graphical view of the number of commits for the last 50 weeks. Using the left and right arrow keys on the computer a daily commit graph is displayed for the given week.
  2. Go back to the main page and use the Search feature to look for humanitarian applications. Type the word humanitarian in the search box and click Search.
    1. How many repositories are there in this category?
      289 repository results
    2. Locate the HTBox/crisischeckin project. When was the last update?
      Aug 7, 2016
  3. Use the Search feature to look for disaster management applications. Type the phrase disaster management the search box and click Search.
    1. How many projects are there in this category?
      143 repository results

OpenHub

  1. In the search space, enter: education
    1. Notice it tells you how many pages of results there are, not number of projects. By default, there should be 10 projects per page. How many projects were returned?
      3456 projects
    2. KDE Education should be the second result. Click on it. Look on the right hand side of the page and click on Code Locations. There are a number of projects listed here. Is any of the code located on GitHub?
      No. They are all git repositories located on the OpenHub hosting service.
    3. Go back one page. Under the Code Locations, it provides several projects that are Similar. Click on Similar Projects. How many similar projects are listed?
      There are 10 listed projects similar to KDE
    4. Scroll down. What information does OpenHub provide about the project?
      Code: There is a graphical representation of how many lines of code there are. Under that there is a pie chart of how many languages are used in KDE.
      Activity: There is a graphical representation of how many commits per month for the life of the project. This can be changed to show the most recent 1,3,5,and 10 year span. Additionally there is a 30 day and 12 month summary of the number of commits and the contributors that link to graphical representation of those statistics.
      Community: Shows how many committers per month and the most recent committers are highlighted.
  2. Perform searches for both humanitarian and disaster management.
    1. How many projects were returned for each search?
      Humanitarian - 34 projects
      Disaster Management - 54
    2. Click on the Activity icon. Why do so many projects do not have activity information available?
      There is no Activity Icon, but sorting by activity level shows a number of projects that have 0 lines of code, 0 current contributors, over X years since last commit, and 0 users on Open Hub
  3. Click on Organizations.
    1. What information is provided on this page?
      Information about organizations that house their code on OpenHub. This includes:
      Most Active Orgs,
      Orgs by 30 Day Commit Volume,
      Newest Organizations, and
      Stats by Sector.
  4. Search for OpenMRS.
    1. When was the last commit for OpenMRS Core?
      There is no link to OpenMRS core on OpenHub. The closest thing I found was OpenMRS Core Apps Module and the last commit was on March 8, 2017.
  5. Go back to GitHub and search for OpenMRS Core.
    1. When was the last commit?
      For OpenMRS Core the latest commit 11 hours ago
    2. Why do you think these sites have different information?
      Because GitHub and OpenHub are two different hosting sites so the repositories are unrelated. Updating one would not automatically update the other.
  6. What would be the benefits/drawbacks of using both GitHub and OpenHub to search for a project?
    The benefit would be to find the project if it existed. The draw back is if there are two different versions of the same project it would be possible to end up working on an inactive version of the project.

Project Evaluation

Evaluation Factor Level
(0-2)
Evaluation Data
Licensing 2 MPL v2.0 (OSI approved)
Language 2 Java 95.4% SQLPL 3.0% GAP 0.7% XSLT 0.4% CSS 0.3% JavaScript 0.1% HTML 0.1%
Level of Activity 2 The forst 3 months of the 12 month cycle was low on the scale of commits, but there were increasingly more commits with the highest numbers in the last 2 - 3 months.
Number of Contributors 2 256 contributors
Product Size 2 218.82MB
Issue Tracker 2 ready for Work 1262 Closed 9889
New Contributor 2 The repository has great instructions and links on how to install and the order in which to install all components of the dev environment. Additionally OpenMRS.org has a link to a wiki that has a great deal of information. This is a welcoming environment for new contributors.

There is a forum called OpenMRS Talk that has activity within the last few hours to days. Note all of the cool links of information available across the top of the wiki page!!!

OpenMRS Wiki Cool Links!!
Community Norms 2 The Code of Conduct is based on the Ubuntu Code of Conduct, which is a broad and inclusive Code. There are disciplinary steps outlined for breaking the rules laid out.

All of the pages I looked at in Talk were respectful.

User Base 2 There are download instructions as well as serveral places to get questions answered
Total Score 18

License

Identify the license for the following projects:

   https://github.com/openmrs/openmrs-core
MPL 2.0
   https://github.com/apache/incubator-fineract
Apache 2.0
   https://github.com/regulately/regulately-back-end 
None Found

Go to https://tldrlegal.com/ . Look up each of the above licenses. Identify the “cans” the “cannots” and the “musts” for each.

Mozilla Public License 2.0 Can, Cannots, and Musts
Apache 2.0 Can, Cannots, and Musts

I would be comfortable using either Apache or MPL

FOSS in Courses

I already teach a full FOSS course. I am looking at new assignments on foss2serve to replace some of my outdated assignments.

Intro to Bug Trackers

Part 1 - Bug Reports

  1. 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.
    1. ID
    2. Sev
    3. Pri
    4. OS
    5. Product
    6. Status
    7. Resolution
    8. Summary
  2. 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).
  3. Identify the order in which the bugs are initially displayed.
  4. What is the meaning of the colors used when describing a bug (red, gray, black)? (Hint: click on the Bug ID and examine the fields)
  5. Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).
    1. Identify when the bug was submitted.
    2. Identify if there has been recent discussion about the bug?
    3. Is the bug current?
    4. Is the bug assigned? To whom?
    5. Describe what you would need to do to fix the bug.
  6. Repeat the previous step with a different kind of bug.

[edit]

===Part 2 - Collective Reports ===
Retrieved from "http://foss2serve.org/index.php?title=User:Morgan&oldid=10202"
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox