User:Michael

(Redirected from User:Mjdowney)

Contents

[edit]

Michael Downey

[edit]

About me

My introduction to computer technology came back in 1987, when my parents purchased a Tandy 1000 EX. Since then, I've been actively involved in computers and online technology. I was a system operator (sysop) for Traders’ Connection (TCON) BBS, in some ways a predecessor to the Internet as we know it today. TCON eventually became one of the first dial-up internet services providers in the region.

I received two undergraduate degrees from Purdue University, majoring in electrical engineering technology (2000) and computer engineering technology. In 2000, I started a career in IT, working for not only Fortune 500 and Global 500 corporations, but also as an industry consultant for small and large projects.

As a graduate student at the Indiana University School of Informatics, my research has focused on user-centered design and testing, usability of open-source software, three-dimensional visualization of file systems, and HCI4D/ICT4D. I was a key member of the MountainView research team and was co-principal investigator for FOSSUL – Indiana’s Free and Open Source Software Usability Laboratory.

I am involved with multiple technology-based development projects in West & Middle Africa. My research is focused on the application of user-centered design principles and methods to international development projects, with specific attention to mobile health-care (mHealth) initiatives.

[edit]

Memberships

American Medical Informatics Association (AMIA), Free Software Foundation (FSF), Electronic Frontier Foundation (EFF), Internet Society (ISOC), Association for Computing Machinery (ACM), IEEE Computer Society, charter member of the Usability Professionals’ Association (UPA)

[edit]

Research interests

  • information and communication technology for international development (ICT4D)
  • user-centered design
  • usability of open-source software
[edit]

Professional experience

[edit]

Stuff to read

[edit]

What's on my "plate"

[edit]

Somewhat complete or steady-state

[edit]

In progress

  • Secure new infrastructure at OSUOSL for web apps
    • In process: WordPress (openmrs.org), Confluence, JIRA
    • Forthcoming in summer: Crowd, Bamboo, Crucible
  • Master OpenMRS web strategy (including rollout of new branding materials)
    • Design/development of HTML themes
  • Distributed meeting and collaboration tools
    • Design and deployment of OpenMRS public web site (potential users & interested parties - not the same as the wiki)
    • Some kind of info sharing between discussion formats (mailing lists, IRC, Forum, etc.)
    • Restructuring of development community resources (wiki, blogs, etc.)
    • Narrowing the focus of and "re-branding" the wiki
    • Aggregation and development of new marketing collateral (video, case studies, etc.) for public web site
    • Evaluate a knowledge base model for FAQ's and support questions (waiting on leadership meeting)
  • Explicitation of OpenMRS mission & vision statements
  • Google Summer of Code 2010 admin
  • Implementation of Amazon EC2 instance for future OpenMRS labs
[edit]

To be started

  • Central authentication/single sign-on for all OpenMRS community web applications (Crowd)
[edit]

Web Strategy Proposal

[edit]

Introduction

Rationale: The audience of people seeking information about OpenMRS online has been segmented into four categories - each category is represented by an element of the circular OpenMRS logo. From a psychological study of the elements of the logo based on position and color theory, a concept of color-coding each segment developed. Although each segment of the site will use 4 subtle/conservative color schemes, each of those schemes will be complementary and will feature similar graphic designs to link all the components together in one cohesive online presence.

Cross-segment content and usage: Some material will be re-used on multiple sections of the site (e.g., a map of OpenMRS implementations). However, wherever possible, such content will centrally managed, requiring only a single update. Additionally, a global single-sign-on solution (e.g., CAS) will be implemented wherever possible to reduce the number of user accounts. Access to different applications will be centrally managed using group and role-based permissions.

Technology: This proposal is currently in the "what" phase. Once some level of consensus within the community is reached, the "how" (technical platforms) will be developed further. OpenMRS has licensed the Atlassian product suite, and the current intent is to leverage those products as much as possible. IU has also offered expertise on CAS, an open source single-sign-on technology used on its campuses, and may also be offering use of its Knowledge Base platform. The technology goals of this project are to embrace open source where possible and also utilize tools that are well-supported within the community. More technical details will be coming in the days and weeks ahead.

This is an early draft of the proposal. Your feedback is welcome and encouraged!
[edit]

Decision-Makers, Media, Funding Organizations, Casually Interested (Purple)

This section will become the "front door" for OpenMRS to the world. It will primarily consist of information about the system and its use around the world, as well as serving to direct newcomers to appropriate places based on their interest and needs. Materials in this segment will be branded with an purple-based color scheme, the first color encountered in the OpenMRS logo, which represents its leadership and rank as leader in its space.

  • Project history & overview
  • Marketing collateral
  • Press releases, leadership blogs
  • Case studies
  • Implementation map
  • Social media (Twitter, Facebook, YouTube, podcasts, etc.)
  • Demo application
[edit]

Users & Support Resources (Teal)

Support materials will be formalized and easier to search and locate. The ticketing system will be expanded to better handle non-code/bug issues. Materials in this segment will be branded with an teal-based color scheme, which is a calming color that promotes patience and lowers frustration levels.

  • Basic end-user training and documentation
  • Support Knowledge Base
  • FAQ's
  • Bug/Issue tracking, feature request, and project management tools (JIRA replaces Trac)
[edit]

Implementers (Orange)

These materials will have a technical focus and are intended for people who are architecting & implementing OpenMRS systems, as well as providing ongoing implementation site support. Materials in this segment will be branded with an orange-based color scheme, which is an energizing color that promotes social interaction.

  • Implementer materials
  • Support Knowledge Base
  • Implementation map
  • Community feed aggregator
  • Social media (Twitter, Facebook, YouTube, podcasts, etc.)
[edit]

Developers (Gold)

Developer materials currently comprise the bulk of information for OpenMRS, so this section will initially be the largest. The MediaWiki platform will be migrated to Confluence to support easier, more effective communication and cooperation. The portfolio of developer tools will be extended to module developers as well as core/trunk developers, and will all be accessed through a single OpenMRS account. Materials in this segment will be branded with an gold-based color scheme, which promotes concentration and analytical thinking.

  • Developer documentation & training materials
  • Developer mailing list & web-based IRC client
  • Source/revision control
  • Continuous integration (Bamboo)
  • Code review (Crucible) & analysis (Clover)
  • Module repository
Retrieved from "http://openmrs.org/wiki/User:Michael"