User:Alan.rea
| Line 29: | Line 29: | ||
This is an extremely rich and productive meeting that takes place in a span of an hour. One can tell these individuals work with one another on a regular basis and are familiar with each others strengths. | This is an extremely rich and productive meeting that takes place in a span of an hour. One can tell these individuals work with one another on a regular basis and are familiar with each others strengths. | ||
| − | |||
| − | |||
==PartB: Project Evaluation Activity== | ==PartB: Project Evaluation Activity== | ||
OpenMRS Evaluation Rubric | OpenMRS Evaluation Rubric | ||
Revision as of 16:10, 14 August 2015
Alan Rea is a Professor of Computer Information Systems in the [Department of Business Information Systems] at the [Haworth College of Business], [Western Michigan University].
Dr. Rea regularly teaches courses in Application, Internet, and Mobile programming, as well as Information Security.
His research focuses on secure mobile application development. In particular, Dr. Rea explores the security and privacy implications intertwined in developing, deploying, and managing the Internet of Things.
Contents |
Response to IRC Activity
What is the pattern of communication?
There are three distinct phases to the meeting: introduction and pleasantries, work on particular challenges, organizing for next assignments. The bulk of the meeting are discussing and attempting to solve multiple challenges (VM issues, camera tracking, graphics challenges on documentation and the like, etc.).
The challenges all center around the FOSS MouseTrap application in varying degrees and center around functionality issues not only with the application but also the VM/Linux system. Collaborative brainstorming leads to some discussi of dependency issues that might be solved via various approaches.
Of special note are items such as the challenges of FOSS systems between various flavors and distributions (e.g., Fedora versys Ubuntu). There are also issues of potential missing support contacts (flapper87) and dead code forks.
Are there any terms that seem to have special meaning?
There are many terms relating to software offerings and dependencies, modules, and code commits. Many times these tend to scare potential users away. Instead of just noting to "update software" in FOSS we need to discuss repositories, potential kernel conflicts, open versus proprietary drivers, etc.
Can you make any other observations?
This is an extremely rich and productive meeting that takes place in a span of an hour. One can tell these individuals work with one another on a regular basis and are familiar with each others strengths.
PartB: Project Evaluation Activity
OpenMRS Evaluation Rubric
