User:Mgondree

Revision as of 20:55, 22 March 2017

Mark Gondree is an Assistant Professor in the Computer Science department at Sonoma State University. Sonoma State is one of 23 campuses in the Cal State system and the only public liberal arts college in California. SSU has over 240 full-time tenured/tenure-track faculty and over 8,000 undergraduate students.

Dr. Gondree's research focus is on computer security and computer security education. He is an evangelist for (and a designer of) games intended to engage students with security topics, and is a PI of the TableTop Security project. His professional website is http://www.gondree.com/.

IRC Assignment

Stage 1 Activities >> Intro to IRC (Activity)

Part 1

1. How do people interact? Darci is running the meeting and calls people and summarizes in minutes. Others mostly take turns speaking in front of the group.
2. What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix? Interactions are informal, a mix of one-to-one and one-(at-a-time)-to-many. There is sometimes cross-talk so people are careful about addressing each other directly so listeners can disentangle the threads.
3. Are there any terms that seem to have special meaning? All the #commands interpreted by the meetbot.
4. Can you make any other observations? Sentences are pretty short. People can't tell the difference between a long pause and afk, so people don't write whole paragraphs per msg.
5. Bonus: Why didn't Heidi and Darci's actions get picked up by the meetbot? ... didn't they? There are three #action items in the transcript, and all three are all reflected here (in the "meeting summary" and the "action items" sections) and also here (at the end, in the action items section). I'm confused by the question. UPDATE: Ah, they are "unassigned" in the "Action items, by person" section -- nicks are case sensitive.

Part 3

Summary of 24 hrs of observing #a11y on irc.gnome.org (3/13 - 3/14/17)

No activity. Lots of people coming and going. Saw a couple POSSE folks in my log.

Summary of 24 hrs of observing #ushashidi on freenode (3/13 - 3/14/17)

Sadly, no real activity. MOTD mentioned other places where developers could be located, so I imagine the IRC channel may not be the best place to drop-in.

FOSS Project Anatomy

Stage 1 Activities >>Intro to FOSS Project Anatomy (Activity)

Sugar Labs Project

Responses to the Sugar Labs Guided Tour:

Contributions The Roles that seem easiest for student involvement are Content Writer and Educator. There are maybe some aspects of Developer (like, trying to fix a bug) that I hope would be more accessible to a class project, but maybe this is naive. Good communication skills seems to be a commonality across all the roles.

Tracker Issue reporting is done at the repo-granularity, i.e. reporting the defect to the maintainers of the code associated with that defect. If its hard to figure out where to report the issue, there is a "catch call" in the general sugar repo.

• Types of tickets are bug, design, feature, needs work. There is also a "needs SLOBS" which, I assume, is discussion by the "Sugar Labs Oversight Board" discussed here.

Repository Date of last commit: Feb 5, 2017

Release cycle Each release has a roadmap, which is assessed at the start of the release cycle.

The Sahana Eden Project

Community Some of the roles are similar (documentation writers, translators, developers). It is interesting to see more specialized roles (newsletter writers, bug marshalls, GIS specialists). Some of this just reflects how the community has self-organized differently (how issues are managed) and some of it reflects the specialized nature of the data and skills being exercised in the project (like, the ecosystem of street map data).

Tracker This project is using TRAC rather than the GitHub issue tracker. They are organized by both "label" and "type" and organized into convenient reports. So, these combine in a variety of ways like "easy" "bugs", "easy" "enhancements", etc.

• Types/categories of active tickets are: defect / bug, documentation, enhancement, task

Repository Date of last commit: March 21, 2017

Release cycle They have planned releases with items associated with each release. Their 0.9.0 milestone is 5 years late right now. Its unclear how or when they decide what items are associated with which release. It looks like they triage releases effectively as "the next one", "after the next one" and "some distant future one."