User:Rhoyle

Roberto Hoyle

Roberto Hoyle is an Assistant Professor in Computer Science at Oberlin College, in Oberlin OH. Oberlin is a small, liberal arts college 40 minutes outside of Cleveland. It has around 2700 students, and around 80-100 of them are Computer Science majors.

Roberto researches Privacy and Security, focusing on how people communicate on online social networks. He received his doctorate from Indiana University, Bloomington in 2016.

Notes from IRC Assignment:

• How do people interact?

The communication style seems to be informal, though focused on a single subject at a time. Everyone seems to jump in when they have something to say, but the meeting chair takes notes with the update and action commands.

• Are there any terms that seem to have special meaning?

Actions, Updates, and Next Steps have meanings that are picked up by meetbot

• What advantages might IRC have over other real-time communication methods (like Google Chat or Facebook Messenger?) Are there potential disadvantages?

The bot is extremely useful for keeping track of minutes and action items.

• Bonus question: Why didn't Heidi and Darci's actions get picked up by the meetbot?

They weren't triggered by the chair?

Notes from Intro to FOSS Anatomy Assignment

• Summarize the roles that you think would be most applicable for your students.

My students would mostly be interested in the designer or developer roles.

• What are the commonalities across roles? What are the differences?

Communication seems to be a common thread throughout the roles. Each role also has a contact person that can be used to get a new user started. In terms of differences, there's all sorts of skills that would be useful. It's not just programmers or translators that are needed.

• Describe the general process for submitting a bug

Go to the github repository and submit an issue.

• Indicate the types/categories of tickets listed on this page as well as the information available for each ticket.

Types: : defects, enhancement requests, and tasks. For each ticket, you have a high-level description, the name of the person who submitted it, severity, and information on how to replicate the issue. There's a comment section for each issue as well, showing the interactions between developers discussing the issues. Finally, there's a status.

• Record the date on your wiki page

Oct 10, 2016

• Describe how the release cycle and roadmap update are related.

The roadmap is the list of all the upcoming features. The release cycle is the list of features that will make it into the current release, and a timeline for the release.

Sahana Eden:

The developers section seems more formalized with regards to the steps that users take. The testers and designers sections are not as fleshed out.

• How is the information here different than the information found on the Sugar Labs tracker page?

There is a different version of Trac being used, one that has pre-built reports that you can select. When you click through to the individual bug report, it looks similar to SugarLab.

• Click the Active Tickets link. Indicate the types/categories of tickets listed on this page as well as the information available for each ticket.

Types: defect/bug, documentation, enhancement, task. The information available seems to be similar.

• Record the date on your wiki page

11 hours ago

Release Map:

They have 3 releases planned, and have a display bar showing how close they are to getting each release out the door.