HumIT ex2gr1
From Foss2Serve
Revision as of 16:42, 13 November 2021 by Heidi.ellis (Talk | contribs)
Contents |
Exercise 2 - Group 1
Sample learning activities mapped to particular courses
- Could use the entire sequence of activities in a Software Engineering course, or a Software Engineering 2 course.
- Could use some of these activities in an HCI' course, too.
- Earlier, easier activities could be used in the intro courses (data structures).
- Networking courses
- Could use the code libraries to illustrate concepts taught in a discrete math class (e.g., directory tree structure).
- Could use the code libraries to illustrate professional practice in a Technical Communication course.
PRO:
- motivation for students is a big plus.
- Very useful item to place on a resume.
CON:
- could be issues with FERPA regulations regarding putting student work in a public place.
- There could be Intellectual Property issues (Does the college assert ownership of all student work?)
- Shy students could be very intimidated by putting their work in a public forum, and by communicating with the developers.
- Faculty mindset (in favor of the status quo)
REMOTE HFOSS PROJECTS
PRO:
- institutional bragging rights
- access to a world-wide developer base
- public recognition
CON:
- lack of face-to-face communication with the "client".
- The source code project could use advanced features/idioms that make it harder for students to understand what the code is doing (e.g., ?: ++ callbacks )
RESOURCES
PRO:
- all of the tools are free.
- no in-house servers needed (can use GitHub, e.g.),
- no support from IT services needed
- students often have their own computers that are powerful enough to do development work
- students can download and configure FOSS development tools
CON:
- Students need to download and configure these tools.