Skip to content

11th NSF Funded POSSE!

March 31, 2019

The foss2serve team hosted the 10th NSF-funded POSSE (Professors’ Open Source Software Experience) workshop in January in NYC.  A huge “Thank You” to the folks at John Jay College for hosting and to Susan Imberman for getting us started and helping with all of the arrangements. The 11th POSSE is planned for Philadelphia, PA, June 17-19. Join us if you can!

When I started with HFOSS (Humanitarian FOSS) in 2006,  I had no idea how student engagement  in HFOSS would impact both faculty members and students.  Since then, I have seen both instructors and students be excited, motivated and generally get hooked by the ability to “do good” via open source.  I’m delighted to be part of a group that shows others how to support student learning in HFOSS. And I’m amazed that we are hosting our eleventh NSF-funded POSSE workshop!


Encouraging Participation

September 12, 2017

I’m currently at the Open Source Summit in LA and I’ve been reflecting on our progress so far in our Freshman Seminar class. This is the third week of class and students are attending a required two-class sequence on Information Literacy put on by our library while I’m gone.

In the past two weeks, I’ve been concerned about how to foster more participation. In an ideal world, students would participate because they’re vested in the outcome of decisions made in class. However, I’ve had low participation, anywhere from 10 to 15 out of 27 students, in several recent online activities. Many students also seem to be reluctant to participate in class.

For instance, We’ve been brainstorming things like the grading distribution for three different kinds of deliverables to fulfill a Personal Development course outcome. We had a good conversation in class and came up with four different point distribution options with two modifications based on dropping the lowest grade. However, only 10 out of 27 students voted on the result. At this point, I can’t tell if this low response is because students are having difficulty navigating the course management system to fill out the surveys, if they don’t have time to fill out the surveys, or if they don’t care enough to find them.

This has left me wondering how to get students to stand up and take control over their learning experience. I’ve provided them with multiple opportunities to direct their own learning path, but students haven’t taken advantage of these opportunities and I’m not sure why. I understand that the experience in our Freshman Seminar is different than their high school experience and I also understand that this is a typical transition for freshman. When I get back next week, I will announce that I’ve rewarded two early contributors to our community with 1% extra credit on their final grade. I’m hoping that this will gain students’ attention, but I’d like to create some intrinsic motivations that go beyond course grades. Still pondering….

Getting Started….

September 1, 2017

This first week has been an adjustment week for all of us. My Freshman Seminar class (2 sections) meets twice a week for 50 minutes. I have two upper-classmen who help with the class and serve as a combination of TA and peer mentor. I’m used to teaching twice a week for 75 minutes and 50 minutes goes by very quickly. In addition, I drastically underestimated the time that it would take to walk through the syllabus. This was compounded by the fact that I’m using an open source-based  Code of Conduct as part of the syllabus which is new to freshman. The result of this was that we spent the entire first class going over course organization.

In the spirit of Open Organization, in the second class we collaboratively designed the Late Assignment policy and the Absence policy, one per section. I outlined the problem and the constraints and teams of students proposed ideas. We then listed all of the ideas and discussed briefly and eliminated the ones that wouldn’t work. In one class we voted on a solution and we’ll vote electronically on the other as we ran out of time.

This was an interesting exercise and gave me insight into student thoughts. I learned that coming to consensus when doing design in large groups (13 students per section) is difficult and that having more time to focus and refine ideas would be helpful. For instance, one initial proposed solution for the Late Assignment policy was “Two days after the due date you lose points” which resulted in a discussion about what is an appropriate due date and time and how many points should be lost. I’m now debating the value of more clearly defining the problem versus allowing students to work through these issues.

Another difference in thinking between myself and my student assistants and the freshman is the idea of “lateness”. The proposals for when someone was late for class included:

  • Being late means 5-15 minutes is late, after 15 minutes is absent
  • 3-20 minutes is late, after 20 minutes is absent
  • 5-20 minutes is late, after 20 minutes is absent

We’ll talk next week about what does it mean to arrive 3-5 minutes after the start of class. What do we call that time after the beginning of class but before one is late? In addition, students thought that up to six total absences and latenesses should be allowed, not including legitimate absences/lateness for things like illness and sports travel.

We’ll do continuous improvement and revisit these policies in five weeks to see how they are working and to adjust as needed.

On an Adventure

August 28, 2017

Today I’m starting on an adventure. I’m teaching two sections of Freshman Seminar using Open Organization principles. My goals are to see how Open Org principles can fit the classroom and to see if using those principles will impact student engagement.

I really want students to own their learning and the beginning of the freshman year is an ideal place to introduce a new culture.  At what point in ones life are you more ready for change?  I’ve been working with Bryan Behrenshousen who has provided very helpful insights int0 how this might work as he preps an Open Source course for Duke.

First up is collaboratively defining the late and absence policies.  I’ll keep you posted!

POSSE Moves to the West Coast!

January 28, 2017



After hosting six Professors’ Open Source Software Experience (POSSE) workshops on the east coast, several at Red Hat’s headquarters in Raleigh, the next POSSE will be held at Google’s San Francisco office, April 20-22, 2017.  I’m really excited that Google is interested in hosting POSSE!  The workshop focuses on helping instructors support students involved in Humanitarian Free and Open Source Software (HFOSS) projects.

There is so much to learn that we run the POSSE in three stages:

  • Stage 1 consists of 8 weeks of online activities to learn HFOSS tools and concepts. The effort is 2-3 hours per week.
  • Stage 2 is a 2.5 day face-to-face meeting, this time in San Francisco.
  • Stage 3 consists of additional online activities and group interactions.

These workshops are run by the foss2serve team which comprises includes Greg Hislop  from Drexel University, Stoney Jackson from Western New England University, Darci Burdge and Lori Postner from Nassau Community College, and Clif Kussmaul from Muhlenberg College. We now have a growing community of over 100 faculty members who have attended POSSE workshops and we are looking for additional instructors to expand our community further. Oh, and for faculty members looking for publications, POSSE alums have generated a growing number of papers, posters, and panels.

If you are a full-time faculty member at a U.S. institution interested in supporting student participation in HFOSS, apply now! More information may be found on the foss2serve site. Because much of the funding for the workshop is coming from the National Science Foundation, we can only accept full-time faculty members at U.S. institutions. However, if you are interested in joining us and can self-fund, please do apply!



Building a Pathway to HFOSS Contribution

February 14, 2016

Our most recent NSF proposal was funded! In September we heard that our project, “OpenPath – Improving Student Pathways to Computing Professions via Humanitarian Free and Open Source Software”, had been funded. This is a collaborative grant with Nassau Community College, Drexel University and Muhlenberg College. The focus of the grant is to create a pathway of course materials and activities that involve students in HFOSS. The activities span from freshman through senior year with the goal of producing open-source-ready students upon graduation. The effort builds on collaborative relationships with the Red Hat University Outreach team , the GNOME Accessibility team, and the OpenHatch project.


Most recently we had a meeting of the minds between FOSS community members and academics to start to figure out what knowledge and skills students need to gain during their academic career in order to be productive FOSS community members. Participants included:

  • Devin Balkind – President, Sahana Software Foundation
  • Saptarshi Purkayastha – Visiting Assistant Professor at IUPUI and contributor to OpenMRS API and web core
  • Mel Chua – Ph.D. candidate in Engineering Education at Purdue University and former member of the Red Hat Education Outreach team
  • Sara Terp – Data Scientist at ThoughtWorks and contributor to Ushahidi
  • Avni Khatri – Program Manager, Knowledge and Learning Technologies, Lab of Computer Science at Massachusetts General Hospital and President of Kids On Computers
  • Gina Likins – University Outreach, Open Source & Standards Team at Red Hat
  • Karl Wurst – Professor at Worcester State University
  • Team members Greg Hislop  from Drexel University and Darci Burdge and Lori Postner from Nassau Community College

While the need for students to gain technical skills such as version control and coding were obvious, I found it interesting that one of the main themes that occurred during the meeting was the need for students to gain soft skills. The need for students to become proficient in communication, problem solving, and critical thinking became apparent throughout the meeting. Another observation was the need for students to understand open source communities in general and to have the skills to navigate individual communities. Thank you to everyone who participated and we will continue to build on what we learned from the meeting.

Summer opportunities in FOSS

March 18, 2015

Two opportunities for summer internships in FOSS:

Google Summer of Code is a global program that offers students stipends to write code for projects from 137 participating FOSS organizations. Applicants must be able to make the project their primary focus during the summer. Participants work remotely from home, while getting guidance from an assigned mentor and collaborating within their project’s community. The application deadline for Google Summer of Code is March 27 and the program dates are May 25 to August 21. The stipend for the program is $5,500 (USD).

The Software Freedom Conservancy has an effort to improve diversity in FOSS. The Outreachy program involves a number of organizations offering remote and mentored internships. These internships are open to women (cis and trans), trans men, and genderqueer people. Applicants must be available for full-time, 40-hours a week, internships. The application deadline for Outreachy is March 24 and the program dates are May 25 to August 25. The stipend for the program is also $5,500 (USD). Unlike in Google Summer of Code, participants do not need to be students and non-coding projects are available. In addition to coding, projects include such tasks as graphic design, user experience design, documentation, bug triage and community engagement.

To apply for either program, you need to connect with a participating organization early, select a project you want to work on, create a project plan, and make a few relevant contributions. I encourage you to apply, even if you haven’t had the chance to make contributions.

Mentorship opportunities are also available throughout the year for anyone interested in getting started contributing to FOSS outside of the internship program.