User:Pmasson
Patrick Masson currently serves as the General Manager and a Board Director for the Open Source Initiative (OSI). Prior to the OSI Patrick worked in higher education technology for over twenty years: first as a Programmer Analyst at The University of California Los Angeles (UCLA), and Director of the UCLA Media Lab, then Chief Information Officer at The State University of New York, College of Technology at Delhi (SUNY Delhi), and most recently, as the Chief Technology Officer for UMassOnline within the University of Massachusetts' Office of the President.
In addition to his role with the OSI, Patrick also an Adjunct Professor at the University at Albany, teaching Open Source Principles and Practices within the College of Engineering and Applied Sciences' Department of Informatics.
He served on the Jasig Foundation's Board of Directors, and is currently on the Apereo Foundation's Advisory Council as well as Brandeis University's Graduate Professional Studies Advisory Board. He is the co-founder and current chair of the Educause Constituent Group on Openness. Patrick was also elected to his local Board of Education in 2014.
Patrick is an active user of a variety of open source software applications--from the desktop to the enterprise--and has contributed to the Sakai Project, Moodle, uPortal, and a variety of other open source projects specific to higher education.
For fun, Patrick plays in a variety of ice hockey leagues.
Links and references:
POSSE Activities
Intro to FOSS Project Anatomy (Activity)
The Sugar Labs Project
- Roles most applicable for your students: Content Writer, People Person, Developer, Designer, and Translator.
- Commonalities/differences across roles: While each role, and the tasks undertaken, require different/unique skill sets, each participant will need to undertake their activities in an open, transparent, collaborative way. Developers and designers, translators and community managers (People Persons), will all need to communicate, share, etc. The outputs may be different, but the principles and practices that generate those outputs are the same. These roles also require individuals to accept feedback, with an honest and receptive manor, accepting the the project's success and community are more valuable than any one idea, contribution, etc.
- General process for submitting a bug:
- (NOTE: while this tutorial points to Simon Tatham's "How to Report Bugs Effectively", the Sugar bug tracker points to a differnt wiki page, "BugSquad/Bug Report." I am assuming you're interested in how to communicate an issue, not the nuts and bolts of how to create and submit a ticket in Trac.)
- (NOTE: Also, the instructions on "Submit Bugs/Problems states bug reports should be posted to GitHub, while this tutorial points to Trac. Also the number of issues and activity in Trac compared to Github makes me think that Trac is in use now, and a migration to Github is underway, or that this tutorial is out of date/incorrect)"
- Visit Sugar's relevant repo on GitHub (join GitHub if needed)
- Provide the developers with enough detailed instructions so that they can replicate the issue for themselves.
- Describe what went wrong (what you expected, vs. what was observed).
- Include any error messages
- You can include your own diagnosis, but always include the symptoms you observed as well.
- Be responsive if the developers follow up, be patient if they do not.
- Write clearly, be precise.
- Types/categories of tickets listed & information available for each ticket:
- Sugar seems to be using two tools for bug/issue reporting/tracking, GitHub's "issues" feature for their website and their own instance of Trac for the Sugar platform
- Issues specific to GitHub seem to be specific to the Sugar website, and most repos have 0 issues. Sugar's use of Github seems to be dedicated to code distribution and related content/activities (e.g. documentation, issues with builds, etc.)
- The issues in Trac include the various components of Sugar and even the tools used to develop/manage Sugar (e.g IRC). Other information included in a ticket include the status of the project, type, owner, etc.
- Date of SugarLabs' last commit:
- Feb 5, 2017
- Relationship between release cycle and roadmap:
- The roadmap is updated at the beginning of each release cycle.
The Sahana Eden Project
- Summary of community information:
- Developers' link provides information on how to contact/communicate (i.e. the mailing list), training resources, a development environment (and documentation), developer guidelines and a CLA.
- Testers' link provides three types of QA needed: technical issues related to the application itself; installation/integration issues, and; test cases from non-technical users.
- Designers
- Sahana vs. Sugar Labs tracker page:
- Both use Trac (again, I'll note confusion over use of Github with Sugar).
- Information available for each ticket:
- Ticket number, summary of the issue, component affected, version of Sahana affected, priority of the issue, type of issue, owner of the issue, status, who created the issue/ticket.
- Date of last commit (an update of the repository
- Mar 5, 2017
- Information about Sahana Eden's release cycle and roadmap:
- Next release is 0.9.0 Medway, which is 92% complete.
- 1.0 Avon is also under development and is 73% complete.
- The page includes a variety of new and enhanced features as well as bug fixes.
FOSS Field Trip (Activity)
- Number of repositories in "education": 12,071
- Information related to "Commits": Commits per week, and per day of week.
- Number of repositories in "humanitarian": 285
- The last updates for HTBox/crisischeckin: Latest commit Aug 7, 2016; last issue opened, Oct 21, 2016; last pull request, opened Nov 4, 2016, last wiki update, Jun 17, 2016.
- Number of repositories in "disaster management": 139
