User:Morgan

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

• IRC
• Mailing lists
• Blog
• Wiki

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

• IRC
• Mailing lists
• Google Groups