User:Kthurston

Revision as of 13:27, 14 June 2019

Name: Karen Thurston

Position: Assistant Professor of Computer Science, North Idaho College, 1000 W. Garden Ave., Coeur d'Alene, ID 83814

email: karen.thurston@nic.edu

Page: https://www.nic.edu/directories/single_entry.aspx?id=2855

GitHub: https://github.com/karenthurstonnic

IRC: server: freenode.net nick: XXXXX channels: foss2serve

HFOSS Projects:

  Open Food Facts https://world.openfoodfacts.org/

HFOSS-Related Courses:

CSC151 - Computer Science II, CSC210 - Concepts of Programming Languages, CS270 - System Software

Grants:

Publications:

    Summer 2019 Deliverables: (INCOMPLETE)

SUGAR LABS (http://sugarlabs.org/) Project Goals: The project has educational, technical, and community goals.

The educational goals are not about education, but about the availability of technology to support education:

  To make Sugar and Sugar activities freely and readily available to learners everywhere
  To explore and share best practices
  To provide a forum for discussion and support for technology for learning
  To provide mechanism for evaluation and dissemination of results.

The technical goals are:

  To make it “simple” to share Sugar activities. This will require an architecture that 
  allows discovery of activities.
  To create versions of Sugar that run on multiple operating systems and on multiple hardware platforms. 
  It should be “simple” to install Sugar everywhere. Specifically, it means packaging for every
  distribution and every virtual machine—removing hardware-related dependencies wherever possible.
  To make it “simple” to write Sugar activities. This necessitates stable APIs and example code that
  uses these APIs.
  To make Sugar activities even more secure. Our principal user community is comprised of children;
  they must be protected from malware, phishing, botnets, etc.

The community goals listed are a combination of community, technical, and educational goals:

  To provide local and regional technical and pedagogical support. (community)
  To create new learning activities and pedagogical practice. (educational)
  To provide localization and internationalization of software, content, and documentation. (technical)
  To provide integration and customization services. (technical)

The project roles include: Activity Team Design Team Documentation Team Development Team Infrastructure Team Marketing Team Platform Team Translation Team Wiki Team Oversight Board

Roles most suitable for my students: Design, documentation, development, and platform team roles.

Commonalities/differences across roles? The roles my students could fill would be directly related to software development. I teach C++, Concepts of Programming Languages, and Operating Systems Software, so these roles would be the best fit. Students should be aware of the other roles, however, since systems development requires all of them and all are important.

General Process for submitting a bug: The SugarLabs site has a page devoted to this topic: https://wiki.sugarlabs.org/go/Submit_Bugs/Problems It also has a page describing how to write a bug ticket. The advice on the page is general good, but one area not addressed is that if a software system has a formatted bug ticket with fields to fill out, this is a preferable to a free form bug ticket. The form will typically be more efficient as it will provide specific information to the programmer. For example, it is helpful to categorize bugs by severity or category. If the software crashes, the bug report may be given a higher priority than if the report is simply a typographical error in a program message.

Types/categories of tickets listed on this page as well as the information available for each ticket: As of June 13, 2019, there are 687 open, and 1,683 closed tickets for all SugarLabs projects combined. Some of the issues are tagged with a category, but the sort doesn't seem to allow sorting by categories. Scrolling to an issue with a category label, then clicking on the label, displays all issues with that label.

Date of last commit: To sugarlabs/readetexts 2 days ago (June 11, 2019)

Repository -- https://github.com/sugarlabs/sugar/ last commit: March 3, 2019

How the release cycle and roadmap update are related: This page describes the schedule for releases: https://wiki.sugarlabs.org/go/Development_Team#Schedule Previously Sugar was released roughly every 6 months, but now releases are ad hoc, "if at all". The current version appears to be .82. I have the "Sugarizer" Android app on my phone (Lionel Laske, developer), it is version 1.1.0, last updated 1/20/2019, first released 10/16/2014.

Communication -- Sugar Labs promotes communication among its community members in the following ways. IRC: https://wiki.sugarlabs.org/go/Internet_Relay_Chat Mailing lists: https://wiki.sugarlabs.org/go/Mailing_Lists Blog: http://planet.sugarlabs.org/ Wiki: http://wiki.sugarlabs.org/go/Welcome_to_the_Sugar_Labs_wiki

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

Community -- In the section titled Want to Contribute to Sahana Eden?, you will find a list of ways in which one can contribute. Again, you will note that there are a variety of distinct groups, each with a distinct responsibility. On your wiki page:

Follow the links to each of the groups listed and summarize the information you find there. For example, are there any commonalities? Is there something distinct for each type of contributor? How is this structure different than the one you found on the Sugar Labs website? Tracker -- The code for Sahana Eden is hosted on GitHub: https://github.com/sahana/eden .

Along the top of that page you will find an "Issues" tab and "Pull requests" tab. These are used to track bugs and feature requests and the efforts to address them. Review the contents of these tabs and then answer the questions below on your wiki page.

How is the information here different than the information found on the Sugar Labs tracker page? Click the "Labels" near the search box on either tab. Indicate the types/categories of issues listed on this page. Repository -- https://github.com/sahana/eden Click the "Commits" link and determine the date of last commit (an update of the repository).

Record the date on your wiki page. Release cycle -- Information about Sahana Eden's release cycle and roadmap can be found here.

Include a brief entry on your wiki page that summarizes the information you find here. Communication -- Sahana Eden promotes communication among its community members in the following ways.

Chat (via Slack): http://eden.sahanafoundation.org/wiki/Chat Mailing lists: http://wiki.sahanafoundation.org/community/mailing_lists Google Groups: https://groups.google.com/forum/?fromgroups#!forum/sahana-eden [edit] Deliverables POSSE: Notes on your user wiki page summarizing selected observations made while exploring HFOSS projects.

Other Organizations:

Bio: www.linkedin.com/in/karenhthurston