Outside of academic settings, I think it's rare for someone to pick a project and dive into its community. Most people get involved with a community because they use and care about the software, and gradually get more involved in the community, following an onion or pyramid model. First they use the software, then they ask & answer forum questions, then submit bug reports & feature requests, then patches / pull requests, etc.
It might be hard to follow this model in a course, but I think students would be more motivated and engaged in a project that they used and felt connected to. Clif --- Clif Kussmaul c...@kussmaul.org http://kussmaul.org +1-484-893-0255 EDT=GMT-5 -----Original Message----- Date: Mon, 5 Mar 2018 15:00:29 -0500 From: Tom Callaway <tcall...@redhat.com> To: tos@teachingopensource.org Subject: [TOS] What makes a "good" open source project for Academic involvement? Message-ID: <909a2f7b-e86e-aa96-08ac-134501337...@redhat.com> Content-Type: text/plain; charset=utf-8 Obviously, no teacher, class, or academic institution are the same, but I'm curious to know what aspects of an open source community make it "good" for you to connect your students with it. Not looking to make a list of "good" communities, but rather, interested in hearing what things that they do that made them a "good" fit. Are there things that you wish open source communities would do more often (or at all) to help make them more student/academic friendly? I've got my own ideas here, but I'm interested in hearing this from an academic perspective first. :) Thanks in advance, ~tom _______________________________________________ tos mailing list tos@teachingopensource.org http://lists.teachingopensource.org/mailman/listinfo/tos TOS website: http://teachingopensource.org/
