[TOS] choosing projects for students to contribute to

[Joel Sherrill]

On Fri, May 8, 2009 at 1:52 PM, William Cohen <wcohen at redhat.com> wrote:

> tridge at samba.org wrote:
>
> In the NCSU open source course (CSC591W) had a similar list in the
> "Evaluating
> Open Source Software" lecture. Materials for the course are available at
> http://people.redhat.com/wcohen/ncsu_opensource_course.tar.gz. There was a
> written assignment to evaluate OSS projects. The students  addressed the
> items
> on the list in their write up fairly well. One thing that tripped up the
> students was some of the projects didn't have clear explanation on how to
> contribute to the project. When doing it over I would certainly have the
> students examine how new developers can get started on the project and
> whether
> there are writeup explaining how to contribute to the project.
>

I hope that the students who found issues with the projects they evaluated
gave
feedback to the project.  Would be interesting for the evaluation to include
feedback
from the project or a report that they addressed an issue. :)

Sometimes the documentation they are looking for isn't there, sometimes it
isn't
where they thought to look, and sometimes it exists but could stand to be
improved.
It is important to realize that people have different chains of thought and
what
might be easy to find to one person might be near impossible to another.

But in the end, I hope all FOSS projects would be open to hearing
constructive
criticism and try to improve.  I know we do.

--joel
RTEMS


>
> -Will
> _______________________________________________
> tos mailing list
> tos at teachingopensource.org
> http://teachingopensource.org/mailman/listinfo/tos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://teachingopensource.org/pipermail/tos/attachments/20090508/ddb68b2c/attachment-0002.html>