[TOS] tos Digest, Vol 98, Issue 1

Hislop,Gregory hislopg at drexel.edu
Tue Mar 6 13:49:54 UTC 2018

It almost goes without saying, but it’s always nice when the instructions for setting up the development environment for a project work!  We often find that those instructions are out of date.

Greg Hislop

From: tos [mailto:tos-bounces at teachingopensource.org] On Behalf Of shivananda poojara
Sent: Tuesday, March 06, 2018 6:22 AM
To: Discussions about Teaching Open Source <tos at teachingopensource.org>
Subject: Re: [TOS] tos Digest, Vol 98, Issue 1

Hello All,

We are supporting and engaging my students to contribute or use open source software in the academics wherever required, starting from documentation, joining to mailing list, communicating in IRC and referring to wiki...

We normally conduct open source awareness sessions by students to their juniors like open source principles, philosophy, what is HFOSS, how to use got, IRC, identify open source projects and how to get connected.

I need to thank RedHat University Outreach program from Pune India, they are mentoring four open source projects from last 8 months, where students learnt many open source culture and contributed many patches.

These projects are under the verge of completion but again they are involving thier juniors to continue.

We are very much happy that within three years of span our open source club grown up from 11 memebers to 68 members.
Culture, environment and mindset about open source is initiated.

Shivananda R Poojara

On 6 Mar 2018 4:39 p.m., "Clif Kussmaul" <clifkussmaul at gmail.com<mailto:clifkussmaul at gmail.com>> wrote:
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 Kussmaul  clif at kussmaul.org<mailto:clif at kussmaul.org>  http://kussmaul.org<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkussmaul.org&data=02%7C01%7Chislopg%40drexel.edu%7C13df19aa8ae646e2f1af08d583555560%7C3664e6fa47bd45a696708c4f080f8ca6%7C0%7C1%7C636559324898915286&sdata=TCwkp6jf4N2i7ycCRg5bR5%2B749IC7s3h9Ln7xBEXwwU%3D&reserved=0>  +1-484-893-0255

-----Original Message-----
Date: Mon, 5 Mar 2018 15:00:29 -0500
From: Tom Callaway <tcallawa at redhat.com<mailto:tcallawa at redhat.com>>
To: tos at teachingopensource.org<mailto:tos at teachingopensource.org>
Subject: [TOS] What makes a "good" open source project for Academic
Message-ID: <909a2f7b-e86e-aa96-08ac-13450133713f at redhat.com<mailto:909a2f7b-e86e-aa96-08ac-13450133713f at 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,


tos mailing list
tos at teachingopensource.org<mailto:tos at teachingopensource.org>
TOS website: http://teachingopensource.org/<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fteachingopensource.org%2F&data=02%7C01%7Chislopg%40drexel.edu%7C13df19aa8ae646e2f1af08d583555560%7C3664e6fa47bd45a696708c4f080f8ca6%7C0%7C1%7C636559324898915286&sdata=7ERYAJVTkyuKz7BlmvRH6q6XUOTJKFmfznWk4Te%2BS8M%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.teachingopensource.org/pipermail/tos/attachments/20180306/d22b6c39/attachment.html>

More information about the tos mailing list