User:Jburge

(Difference between revisions)
Jump to: navigation, search
(Created page with "==== Janet Burge ==== Janet Burge is an Associate Professor in the Department of Mathematics and Computer Science at Colorado College. Colorado College is a small liberal art...")
 
Line 6: Line 6:
  
 
Dr. Burge also spent 20 years in industry before starting her academic career.
 
Dr. Burge also spent 20 years in industry before starting her academic career.
 +
 +
 +
----
 +
 +
 +
'''Exercises:'''
 +
 +
'''Intro to Project Autonomy:
 +
'''
 +
Sugarlabs Project
 +
 +
Contributions:
 +
What would be the most suitable roles for my students? Developer, maybe Content Writer? Possibly
 +
Designer if students have the right skills.
 +
What are commonalities across roles? What are differences?. Educator can overlap with
 +
  quite a few other roles. Content writer and People Person overlaps.
 +
 +
Tracker:
 +
What is the process for submitting a bug? File a bug using Trac. Describe, Categorize, Create.
 +
Types/categories of tickets: Defects and Enhancements. There are more detailed fields
 +
that can be set by the developers.
 +
 +
Repository:
 +
Date of last commit: October 10, 2016
 +
 +
Release cycle:
 +
How the release cycle and roadmap update are related:
 +
 +
Milestones are mapped to tickets to show the percentage complete. The
 +
roadmap lists items that are going into the particular Milestone. I am guessing
 +
Milestones represent releases? Some of the tasks have names next to them, some do not.
 +
 +
Sahana:
 +
 +
Contributions:
 +
Developers, Testers, Designers: commonality? Differences? Compare w/Sugarlabs
 +
Developers - work on tasks, tickets, projects
 +
Testers: - three types: manual testing by non-technical, developers writing tests, and
 +
administrators working on Continuous Integration.
 +
Designers: looking for help with the website - they mention graphic design but skills
 +
listed are HTML and CSS.
 +
 +
Overlap between developers and testers since developers write tests.
 +
Differences with Sugarlabs: explicit test role, designers are more developer like
 +
(Sugarlabs was looking for graphic-designer specific experience)
 +
Commonalities with Sugarlabs: developer role is similar.
 +
 +
Tracker:
 +
      This is still using Trac, so that's similar to Sugarlabs'. The view we're taken to is
 +
      a list of queries on reports (some are confusing - why would I have a list of reports if
 +
      I am not logged in?). They have more types - defect, enhancement, documentation, and task.
 +
      In Sugarlabs we were taken to instructions for creating a ticket. Here we're on a reporting page
 +
      but it does not provide a way to add a ticket. Is this restricted?
 +
 
 +
  Bug info: number, summary, version, priority, type, owner, status
 +
 
 +
Repository: last commit today (March 7, 2017)
 +
 +
Release cycle:
 +
 +
  The format is the same as Sugarlabs. It must be generated from Trac? More
 +
  detail under the tasks.

Revision as of 21:10, 7 March 2017

Janet Burge

Janet Burge is an Associate Professor in the Department of Mathematics and Computer Science at Colorado College. Colorado College is a small liberal arts college in Colorado Springs and teaches on the Block Plan where students take one course at a time.

Prior to joining Colorado College Dr. Burge was an Associate Professor at Wesleyan University and at Miami University. While at Miami, she was awarded an NSF Career Award for her research in Design Rationale. Her research interests are AI in Design and Software Engineering.

Dr. Burge also spent 20 years in industry before starting her academic career.




Exercises:

Intro to Project Autonomy: Sugarlabs Project

Contributions: What would be the most suitable roles for my students? Developer, maybe Content Writer? Possibly Designer if students have the right skills. What are commonalities across roles? What are differences?. Educator can overlap with quite a few other roles. Content writer and People Person overlaps.

Tracker: What is the process for submitting a bug? File a bug using Trac. Describe, Categorize, Create. Types/categories of tickets: Defects and Enhancements. There are more detailed fields that can be set by the developers.

Repository: Date of last commit: October 10, 2016

Release cycle: How the release cycle and roadmap update are related:

Milestones are mapped to tickets to show the percentage complete. The roadmap lists items that are going into the particular Milestone. I am guessing Milestones represent releases? Some of the tasks have names next to them, some do not.

Sahana:

Contributions: Developers, Testers, Designers: commonality? Differences? Compare w/Sugarlabs Developers - work on tasks, tickets, projects Testers: - three types: manual testing by non-technical, developers writing tests, and administrators working on Continuous Integration. Designers: looking for help with the website - they mention graphic design but skills listed are HTML and CSS.

Overlap between developers and testers since developers write tests. Differences with Sugarlabs: explicit test role, designers are more developer like (Sugarlabs was looking for graphic-designer specific experience) Commonalities with Sugarlabs: developer role is similar.

Tracker:

      This is still using Trac, so that's similar to Sugarlabs'. The view we're taken to is
      a list of queries on reports (some are confusing - why would I have a list of reports if
      I am not logged in?). They have more types - defect, enhancement, documentation, and task. 
      In Sugarlabs we were taken to instructions for creating a ticket. Here we're on a reporting page
     but it does not provide a way to add a ticket. Is this restricted?
 
 Bug info: number, summary, version, priority, type, owner, status
 

Repository: last commit today (March 7, 2017)

Release cycle:

 The format is the same as Sugarlabs. It must be generated from Trac? More 
 detail under the tasks.
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox