24 Dec 2019
Speaker: Harish Pillay
Organization: Red Hat
Software drives everything. What drives software is algorithms. We have been able to measure how "good" or "bad" a piece of software is by various metrics as done by the Prospector project. Is there a higher level of consideration around the ethical basis of software and contrasting that with the morality of software and algorithms. How should developers be driven when it comes to crafting ethical solutions if the morality of the developer is challenged and vice versa? Is there an absolute moral code for developers? Ethical codes are crafted in many professions but there aren't moral codes. Is that an oversight. This talk will explore the nuances of ethics and morals and propose some mental strategies in navigating these. It is not meant to be exhaustive nor definitive. There does not seem to be much by way of research in this field and one of the outcomes of this talk is to trigger the discussion and potentially finding a way to quantify, measure and perhaps act on being ethical and moral in software development.
Organization: Red Hat
Software drives everything. What drives software is algorithms. We have been able to measure how "good" or "bad" a piece of software is by various metrics as done by the Prospector project. Is there a higher level of consideration around the ethical basis of software and contrasting that with the morality of software and algorithms. How should developers be driven when it comes to crafting ethical solutions if the morality of the developer is challenged and vice versa? Is there an absolute moral code for developers? Ethical codes are crafted in many professions but there aren't moral codes. Is that an oversight. This talk will explore the nuances of ethics and morals and propose some mental strategies in navigating these. It is not meant to be exhaustive nor definitive. There does not seem to be much by way of research in this field and one of the outcomes of this talk is to trigger the discussion and potentially finding a way to quantify, measure and perhaps act on being ethical and moral in software development.
- 1 participant
- 25 minutes
23 Oct 2019
Speaker: Sean Goggins
Organization: University of Missouri
Risk and Value metrics are initiating a process of aggregating CHAOSS metrics into new forms. Augur's integrated git, Issue tracker and code evaluation tools to address these needs in a new, consolidated data model, supported by GSoC students and ongoing development. This presentation will review Augur in the context of Risk and Value metric implementations.
Organization: University of Missouri
Risk and Value metrics are initiating a process of aggregating CHAOSS metrics into new forms. Augur's integrated git, Issue tracker and code evaluation tools to address these needs in a new, consolidated data model, supported by GSoC students and ongoing development. This presentation will review Augur in the context of Risk and Value metric implementations.
- 3 participants
- 21 minutes
23 Oct 2019
Speaker: Andy Leak
Organization: Mountain View Smart Contracts
The CHAOSS Value Metrics Group started in Spring 2019. In this talk, we will describe the Value Metrics and how they relate to Open Source Program Offices. We will describe new software tools for measuring Economic Value, present the results of an email survey, and describe lessons learned in a series of interviews with Open Source Program Offices. We'll discuss next steps, and potential efforts to build connections between OSPO offices for networking and learning.
Organization: Mountain View Smart Contracts
The CHAOSS Value Metrics Group started in Spring 2019. In this talk, we will describe the Value Metrics and how they relate to Open Source Program Offices. We will describe new software tools for measuring Economic Value, present the results of an email survey, and describe lessons learned in a series of interviews with Open Source Program Offices. We'll discuss next steps, and potential efforts to build connections between OSPO offices for networking and learning.
- 4 participants
- 24 minutes
23 Oct 2019
Speaker: Georg Link
Organization: Bitergia
Decision makers often face challenges to understand open source projects, especially as data is scattered across different collaboration platforms. Two tools - GrimoireLab and CROSSMINER - were developed to overcome this challenge but were started with different goals in mind. On the one hand, GrimoireLab focused on understanding software development process within open source projects. On the other hand, CROSSMINER focused on helping software developers select the right open source projects. The meaning of project health is different in both cases. This talk is about this philosophical difference in approaching open source project health metrics, how it shaped the tools, what this means for metrics that were implemented, and what lessons can be learned about measuring open source project health.
Organization: Bitergia
Decision makers often face challenges to understand open source projects, especially as data is scattered across different collaboration platforms. Two tools - GrimoireLab and CROSSMINER - were developed to overcome this challenge but were started with different goals in mind. On the one hand, GrimoireLab focused on understanding software development process within open source projects. On the other hand, CROSSMINER focused on helping software developers select the right open source projects. The meaning of project health is different in both cases. This talk is about this philosophical difference in approaching open source project health metrics, how it shaped the tools, what this means for metrics that were implemented, and what lessons can be learned about measuring open source project health.
- 3 participants
- 20 minutes
23 Oct 2019
Speaker: Matt Snell
Organization: University of Nebraska Omaha
This presentation is to explain the process of implementing the CII Best Practices API as a risk metric and a brief discussion of its implications. I will start with a program that performs a basic API call to CII. Next, I will examine the API call and explain some important parameters. Then, I will ask for some feedback on other parameters that may be useful. A combination of the predetermined metrics and audience suggestions will be used to create a CII dashboard. If we are short on time, example code will be ready to be used in the place of written code. I will end the presentation with a brief discussion with the audience, exploring potential use cases and implications of the CII Best Practices metric.
Organization: University of Nebraska Omaha
This presentation is to explain the process of implementing the CII Best Practices API as a risk metric and a brief discussion of its implications. I will start with a program that performs a basic API call to CII. Next, I will examine the API call and explain some important parameters. Then, I will ask for some feedback on other parameters that may be useful. A combination of the predetermined metrics and audience suggestions will be used to create a CII dashboard. If we are short on time, example code will be ready to be used in the place of written code. I will end the presentation with a brief discussion with the audience, exploring potential use cases and implications of the CII Best Practices metric.
- 3 participants
- 12 minutes
23 Oct 2019
Speaker: Jana Gallus
Organization: UCLA
Jana Gallus is an Assistant Professor of Strategy and Behavioral Decision Making at UCLA's Anderson School of Management. Her research interests lie in behavioral economics, innovation and strategy, with a focus on non-financial incentives and their effects on motivation and performance. She runs field experiments testing the effects of award schemes and other non-financial incentives for innovation with organizations and crowd-based communities including, among others, Wikipedia, NASA, and international code collaboration platforms.
Organization: UCLA
Jana Gallus is an Assistant Professor of Strategy and Behavioral Decision Making at UCLA's Anderson School of Management. Her research interests lie in behavioral economics, innovation and strategy, with a focus on non-financial incentives and their effects on motivation and performance. She runs field experiments testing the effects of award schemes and other non-financial incentives for innovation with organizations and crowd-based communities including, among others, Wikipedia, NASA, and international code collaboration platforms.
- 1 participant
- 31 minutes
23 Oct 2019
Speaker: Ray Paik
Organization: GitLab
There are plenty of metrics available to measure various aspects of your community ranging from contributors, contributors’ activities, followers on social media, event attendees, etc. However, what exactly are these metrics telling us and do they always tell the same story? Metrics (and numbers in general) can give people a false sense of clarity and even worse, people can draw wrong conclusions from metrics when they lack proper context. So how and when should metrics be used? In this session, Ray will discuss how metrics are used at GitLab to assess support for community members across different phases of the contributor journey. Ray will also discuss how community metrics at GitLab has evolved over time and how it needs to continue to evolve as the GitLab community grows.
Organization: GitLab
There are plenty of metrics available to measure various aspects of your community ranging from contributors, contributors’ activities, followers on social media, event attendees, etc. However, what exactly are these metrics telling us and do they always tell the same story? Metrics (and numbers in general) can give people a false sense of clarity and even worse, people can draw wrong conclusions from metrics when they lack proper context. So how and when should metrics be used? In this session, Ray will discuss how metrics are used at GitLab to assess support for community members across different phases of the contributor journey. Ray will also discuss how community metrics at GitLab has evolved over time and how it needs to continue to evolve as the GitLab community grows.
- 1 participant
- 30 minutes
17 Oct 2019
Speaker: Armstrong Foundjem
Organization: Polytechnique Montréal
Software ecosystems bring value by integrating projects related to a given domain, for example, open source projects in a Linux distribution or mobile apps in the Android platform. Since each project has its release cycle and roadmap, having to install compatible versions of each project manually puts an enormous burden on the users, and hence many ecosystems release a polished, well-integrated product to the end user. This paper empirically studies this release synchronization strategy in the context of the OpenStack ecosystem, in which a central release management team manages the six-month release cycle of the overall OpenStack product. By analyzing one year of release team IRC meeting logs, we identified nine major release synchronization activities, which we cataloged and documented. To validate our findings, we interviewed 8 active OpenStack practitioners (members of either the release team or project teams). Our results suggest that even though an ecosystem’s power lies in the interaction of independent projects, release synchronization is a non-trivial goal.
Organization: Polytechnique Montréal
Software ecosystems bring value by integrating projects related to a given domain, for example, open source projects in a Linux distribution or mobile apps in the Android platform. Since each project has its release cycle and roadmap, having to install compatible versions of each project manually puts an enormous burden on the users, and hence many ecosystems release a polished, well-integrated product to the end user. This paper empirically studies this release synchronization strategy in the context of the OpenStack ecosystem, in which a central release management team manages the six-month release cycle of the overall OpenStack product. By analyzing one year of release team IRC meeting logs, we identified nine major release synchronization activities, which we cataloged and documented. To validate our findings, we interviewed 8 active OpenStack practitioners (members of either the release team or project teams). Our results suggest that even though an ecosystem’s power lies in the interaction of independent projects, release synchronization is a non-trivial goal.
- 3 participants
- 23 minutes
