User:RMccleary

(Difference between revisions)
Jump to: navigation, search
m (Fix "Ron McCleary" title)
(Sugar labs use of tracker)
Line 44: Line 44:
 
'''Translator'''
 
'''Translator'''
 
We have several international students, mainly from Saudi Arabia and a few from Japan, who could be helpful here.
 
We have several international students, mainly from Saudi Arabia and a few from Japan, who could be helpful here.
 +
 +
=== Use of Tracker ===
 +
 +
To submit a bug, first visit the [https://github.com/sugarlabs sugarlabs page at github] and look for the activity or a sugar component repository that is relevant.
 +
describe the general process for submitting a bug and indicate the types/categories of tickets listed on this page as well as the information available for each ticket

Revision as of 04:51, 11 June 2016

Contents

About Ron McCleary

Ron is assistant professor of computer science at Avila University in south Kansas City, Missouri. He has been at Avila for 14 years. Before that, he was Director of Corporate Information Systems for Terracon, a national engineering consulting company with headquarters in the Kansas City area. Before that, he was at Rockhurst University in Kansas City for 13 years, four of them as a computer science instructor and nine as Director of Computer Services.

Avila is a liberal arts schools sponsored by the Sisters of St. Joseph of Carondelet. The Computer Science Department offers three majors: computer science, software engineering, and a newly approved one in health informatics. Ron teaches a variety of courses that includes operating systems, computer organization and architecture, database, networking, systems analysis and design, Java, and C#.

Ron's interests and activities outside the classroom include reading, hiking, and teaching in the education program of his church.

FOSS Deliverables

IRC

How do people interact? While the meeting has a "flow" to it, because of the asynchronous characteristics of the typed responses, it is more of be a flow with ripples.

What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix? Generally, a linear flow of ideas but with a lot of small branching in and out of the current theme. It is informal. Generally, it is one-to-many, interspersed with occasional one-to-one communications; i.e. it is a mix.

Are there any terms that seem to have special meaning? Don't think I noticed any.

Can you make any other observations? At first, I thought the comments to oneself (the /me commands) were inhibiting the flow of the meeting. On further reflection, I think they add value by giving a little comic relief.

Sugar Labs Project

Roles most applicable for my students

My students come with a variety of skills and interests, so some of them may fit several roles while others may only fit one role. Some of roles seem to have some common skills required: content writer and people person seem to require good communication skills; designers and developers need to use complex programs (for programming and graphic design, respectively). The educator role doesn't seem to fit well for any of my current students.

Content writer Several of my students are good writers and have the skills to write content.

People Person Again, several of my students would be good at this role. In fact, many of the ones who could do well as Content Writers would also do well in this category.

Developer We have a two-semester Python requirement in the major to introduce our students to programming, so most of my students should do well in this category.

Designer A few of our students are doing graphic arts minors and would be well fitted for this category.

Translator We have several international students, mainly from Saudi Arabia and a few from Japan, who could be helpful here.

Use of Tracker

To submit a bug, first visit the sugarlabs page at github and look for the activity or a sugar component repository that is relevant.

describe the general process for submitting a bug and indicate the types/categories of tickets listed on this page as well as the information available for each ticket
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox