chaoss:gsoc-ideas
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
chaoss:gsoc-ideas [2018/03/04 13:34] GeorgLink change order |
chaoss:gsoc-ideas [2018/03/21 15:56] (current) GeorgLink |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ====== Ideas for Google Summer of Code projects ====== | ====== Ideas for Google Summer of Code projects ====== | ||
| - | + | ===== Idea #1: Support of Standard CHAOSS Formats for Description of Projects ===== | |
| - | ===== Idea #1: Prototype New CHAOSS Metrics ===== | + | |
| - | + | ||
| - | [ [[https://github.com/OSSHealth/ghdata/issues/82|Micro-tasks and place for questions]] ] | + | |
| - | + | ||
| - | Create a library that can be used by CHAOSS Community Software projects like GHData to express open source software project level similarities. There are two components: A set of algorithms for integrating similarity measures on an array of project data and implementation of visualizations using our existing framework and possibly adding to the framework. | + | |
| - | + | ||
| - | + | ||
| - | The aims of the project are as follows: | + | |
| - | - Build new metrics in a Python/Flask/MetricsJS for the open source project [[http://www.github.com/OSSHealth/ghdata|GHData]]. This will create familiarity with different metrics as currently defined by the CHAOSS project, as well as introduce user interaction design goals of: | + | |
| - | - Enabling comparisons between GitHub, Mozilla, and other open source project repositories and projects as a default design mechanism. | + | |
| - | - Considering the different ways of building software to do temporal comparisons. | + | |
| - | - Build machine learning algorithms that identify candidate “toxic interactions” in open source mailing lists and IRC channels, with the aim of making open source a more welcoming environment for diverse populations. | + | |
| - | - Design and evaluate exploratory mechanisms for presenting project data, metrics, and analysis using a complex, hierarchical, and networked set of data structures. For example, there are two main ways a "commit" is defined in open source software: a) The explicit, individual "commit" record and b) "unique commits". For each of these metrics, which can be reasonably calculated from source repositories, there are interests in CHOASS project stakeholders in understanding them: | + | |
| - | - By project | + | |
| - | - Project organization | + | |
| - | - Foundation | + | |
| - | - Dependencies (including integration with libraries.io and other data sets) | + | |
| - | - Individual | + | |
| - | - Corporate organization | + | |
| - | - Roles in a project (including people evolving from the periphery to the core). | + | |
| - | + | ||
| - | Each of these are significant opportunities for a Google Summer of Code participant to engage and learn and become part of a project. | + | |
| - | + | ||
| - | + | ||
| - | * //Difficulty:// easy/medium | + | |
| - | * //Requirements:// Python programming. Networking Basics, JavaScript Basics | + | |
| - | * //Recommended:// Experience with Python HTTP and XML libraries would be convenient, but can be learned during the project. | + | |
| - | * //Mentors:// Sean Goggins, Jesus M. Gonzalez-Barahona, Josianne Marsan | + | |
| - | + | ||
| - | + | ||
| - | ===== Idea #2: Support of Standard CHAOSS Formats for Description of Projects ===== | + | |
| [ [[https://github.com/chaoss/grimoirelab/issues/71|Micro-tasks and place for questions]] ] | [ [[https://github.com/chaoss/grimoirelab/issues/71|Micro-tasks and place for questions]] ] | ||
| Line 61: | Line 30: | ||
| - | ===== Idea #3: Reporting of CHAOSS Metrics ===== | + | ===== Idea #2: Reporting of CHAOSS Metrics ===== |
| [ [[https://github.com/chaoss/grimoirelab/issues/70|Micro-tasks and place for questions]] ] | [ [[https://github.com/chaoss/grimoirelab/issues/70|Micro-tasks and place for questions]] ] | ||
| Line 81: | Line 50: | ||
| * //Recommended:// Experience with Python interfaces to databases would be convenient, but can be learned during the project. Experience with Latex and/or Python Jupyter Notebooks would help. | * //Recommended:// Experience with Python interfaces to databases would be convenient, but can be learned during the project. Experience with Latex and/or Python Jupyter Notebooks would help. | ||
| * //Mentors:// Jesus M. Gonzalez-Barahona, Matt Germonprez, Jordi Cabot | * //Mentors:// Jesus M. Gonzalez-Barahona, Matt Germonprez, Jordi Cabot | ||
| + | |||
| + | |||
| + | |||
| + | ===== Idea #3: Prototype New CHAOSS Metrics ===== | ||
| + | |||
| + | [ [[https://github.com/OSSHealth/ghdata/issues/82|Micro-tasks and place for questions]] ] | ||
| + | |||
| + | Create a library that can be used by CHAOSS Community Software projects like GHData to express open source software project level similarities. There are two components: A set of algorithms for integrating similarity measures on an array of project data and implementation of visualizations using our existing framework and possibly adding to the framework. | ||
| + | |||
| + | |||
| + | The aims of the project are as follows: | ||
| + | - Build new metrics in a Python/Flask/MetricsJS for the open source project [[http://www.github.com/OSSHealth/ghdata|GHData]]. This will create familiarity with different metrics as currently defined by the CHAOSS project, as well as introduce user interaction design goals of: | ||
| + | - Enabling comparisons between GitHub, Mozilla, and other open source project repositories and projects as a default design mechanism. | ||
| + | - Considering the different ways of building software to do temporal comparisons. | ||
| + | - Build machine learning algorithms that identify candidate “toxic interactions” in open source mailing lists and IRC channels, with the aim of making open source a more welcoming environment for diverse populations. | ||
| + | - Design and evaluate exploratory mechanisms for presenting project data, metrics, and analysis using a complex, hierarchical, and networked set of data structures. For example, there are two main ways a "commit" is defined in open source software: a) The explicit, individual "commit" record and b) "unique commits". For each of these metrics, which can be reasonably calculated from source repositories, there are interests in CHOASS project stakeholders in understanding them: | ||
| + | - By project | ||
| + | - Project organization | ||
| + | - Foundation | ||
| + | - Dependencies (including integration with libraries.io and other data sets) | ||
| + | - Individual | ||
| + | - Corporate organization | ||
| + | - Roles in a project (including people evolving from the periphery to the core). | ||
| + | |||
| + | Each of these are significant opportunities for a Google Summer of Code participant to engage and learn and become part of a project. | ||
| + | |||
| + | |||
| + | * //Difficulty:// easy/medium | ||
| + | * //Requirements:// Python programming. Networking Basics, JavaScript Basics | ||
| + | * //Recommended:// Experience with Python HTTP and XML libraries would be convenient, but can be learned during the project. | ||
| + | * //Mentors:// Sean Goggins, Jesus M. Gonzalez-Barahona, Josianne Marsan | ||
| + | |||
chaoss/gsoc-ideas.1520170462.txt.gz · Last modified: 2018/03/04 13:34 by GeorgLink
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
