User:Sbradley
(Difference between revisions)
| Line 26: | Line 26: | ||
'''Bio:''' I like computer science, teaching, and music. And combining all three I like to sing and play to my students in lectures, and also initiated an open source project [https://github.com/stevenaeola/node-red-contrib-music node red music] | '''Bio:''' I like computer science, teaching, and music. And combining all three I like to sing and play to my students in lectures, and also initiated an open source project [https://github.com/stevenaeola/node-red-contrib-music node red music] | ||
| − | POSSE Project Evaluation | + | POSSE Project Evaluation for OpenMRS |
| Line 75: | Line 75: | ||
| | | | ||
|} | |} | ||
| + | |||
| + | ===Learning activities=== | ||
| + | |||
| + | ====Activity 1 (group): Identify a project==== | ||
| + | |||
| + | * Identify open source products that some/all use (preferably smaller than Linux!) Choose two to evaluate as potential targets | ||
| + | |||
| + | * Discuss general areas that you are interested from in the humanitarian area (do we have a list?) Are there any that are interesting to all? Search for open source projects in this/these area(s) and choose three to evaluate as potential targets, make it up to one evaluation per student. | ||
| + | |||
| + | * Combine the results of the evaluations and come up with a ranked set of candidate projects. If none of them are good enough the loop again | ||
| + | |||
| + | * Find relevant user and dev information channels (mailing list/slack channel/google group/stackexchange) and join | ||
| + | |||
| + | |||
| + | ====Activity 2 (in pairs): Read the documentation ==== | ||
| + | |||
| + | * Preferably work on different architectures | ||
| + | |||
| + | * Find the source of the documentation. Make sure you understand the format and practice making a change on a forked version | ||
| + | |||
| + | * In pairs, follow the documentation to install and run, using an example given. Once you've mastered it, make a video and screenshots of the process. If there are any errors/omissions in the documentation, correct them in your forked version | ||
| + | |||
| + | * Combine any documentation corrections into one repository and submit a pull request of the changes | ||
| + | |||
| + | * Publish your video(s), link them from the docs and submit a pull request of that (independent of the docs changes) | ||
| + | |||
| + | * Do the same thing for the build process | ||
| + | |||
| + | * Write a new example and document that in the same way | ||
[[Category:POSSE 2019-06]] | [[Category:POSSE 2019-06]] | ||
Revision as of 17:11, 15 June 2019
Name: Steven Bradley
Position: Associate Professor (teaching), Computer Science, Durham University University, UK
email: s.p.bradley@durham.ac.uk
Page: https://www.dur.ac.uk/research/directory/staff/?mode=staff&id=106
GitHub: https://github.com/stevenaeola
IRC: server: freenode.net nick: stevenaeola channels: foss2serve
HFOSS Projects:
- None yet
HFOSS-Related Courses:
- None yet
Grants:
- google CS4HS
Publications: [1]
Other Organizations:
Bio: I like computer science, teaching, and music. And combining all three I like to sing and play to my students in lectures, and also initiated an open source project node red music
POSSE Project Evaluation for OpenMRS
| Evaluation Factor | Level (0-2) |
Evaluation Data |
|---|---|---|
| Licensing | 2 | Mozilla Public License 2.0 |
| Language | 1 | Java, SQLPL |
| Level of Activity | 2 | Active all quarters |
| Number of Contributors | 2 | 324 |
| Product Size | 1 | 223.36MB |
| Issue Tracker | ||
| New Contributor | ||
| Community Norms | ||
| User Base | ||
| Total Score |
Learning activities
Activity 1 (group): Identify a project
- Identify open source products that some/all use (preferably smaller than Linux!) Choose two to evaluate as potential targets
- Discuss general areas that you are interested from in the humanitarian area (do we have a list?) Are there any that are interesting to all? Search for open source projects in this/these area(s) and choose three to evaluate as potential targets, make it up to one evaluation per student.
- Combine the results of the evaluations and come up with a ranked set of candidate projects. If none of them are good enough the loop again
- Find relevant user and dev information channels (mailing list/slack channel/google group/stackexchange) and join
Activity 2 (in pairs): Read the documentation
- Preferably work on different architectures
- Find the source of the documentation. Make sure you understand the format and practice making a change on a forked version
- In pairs, follow the documentation to install and run, using an example given. Once you've mastered it, make a video and screenshots of the process. If there are any errors/omissions in the documentation, correct them in your forked version
- Combine any documentation corrections into one repository and submit a pull request of the changes
- Publish your video(s), link them from the docs and submit a pull request of that (independent of the docs changes)
- Do the same thing for the build process
- Write a new example and document that in the same way
