Re: [openstack-dev] [Stackalytics] 0.1 release [metrics]
Stefano Maffulli wrote: On 07/23/2013 07:25 AM, Roman Prykhodchenko wrote: I still think counting lines of code is evil because it might encourage some developers to write longer code just for statistics. Data becomes evil when you decide to use them for evil purposes :) I don't think that lines of code is a bad metric per se: like any other metric it becomes bad when used in an evile context. I'm getting more and more convinced that it's a mistake to show ranks and classifications in the dashboard and I'll be deleting all the ones that we may have on http://activity.openstack.org. (see https://bugs.launchpad.net/openstack-community/+bug/1205139) Counting anything in OpenStack, from commits to number of reviews is not a race, we don't need to *rank* top contributors. While I think those stats are useless to identify top contributors (since the precise metric used will influence who ends up in the top spots), I think they are useful to identify who does not contribute at all. In that case 0 commits = 0 lines of code = 0 reviews and the metric used does not matter that much. You could say we should not be in the business of shaming people, but remember that since we use a permissive license, societal pressures (rather than institutional pressures like the license) are the only way to force companies to contribute back. The Apache license lets you not contribute back, but that doesn't mean companies who claim to be an OpenStack open source team player can get away with not contributing anything at all... -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Stackalytics] 0.1 release
A suggestion: sort bugs number as int is much better than string, because '112' '8' but actually 112 8 http://stackalytics.com/companies/unitedstack On Thu, Jul 25, 2013 at 9:31 AM, Alex Freedland afreedl...@mirantis.comwrote: Roman, Thank you for your comment. I agree that is should not be the only way to look at the statistics and that is why Stackalytics also measures the number of contributions and soon will add the number of reviews. I do, however, think it a useful statistic as because not all commits are created equal. To your argument that the developers will write longer code just for the sake of statistics, I think this will not happen en mass. First and foremost, the developers care about their reputations and knowing that their code is peer-reviewed, very few will intentionally write inefficient code just to get their numbers up. Those few who will choose this route will lose the respect of their peers and consequently will not be able to contribute as much. Also, in order to deal with the situations where people can manipulate the numbers, Stackalytics allows anyone in the community to correct the line count where it does not make sense. ( https://wiki.openstack.org/wiki/Stackalytics#Commits_metrics_corrections_and_a_common_sense_approach ). We welcome any other improvements and suggestions on how to make OpenStack statistics more transparent, meaningful and reliable. Alex Freedland On Tue, Jul 23, 2013 at 7:25 AM, Roman Prykhodchenko rprikhodche...@mirantis.com wrote: I still think counting lines of code is evil because it might encourage some developers to write longer code just for statistics. On Jul 23, 2013, at 16:58 , Herman Narkaytis hnarkay...@mirantis.com wrote: Hello everyone! Mirantis http://www.mirantis.com/ is pleased to announce the release of Stackalytics http://www.stackalytics.com/ 0.1. You can find complete details on the Stackalytics wikihttps://wiki.openstack.org/wiki/Stackalytics page, but here are the brief release notes: - Changed the internal architecture. Main features include advanced real time processing and horizontal scalability. - Got rid of all 3rd party non-Apache libraries and published the source on StackForge under the Apache2 license. - Improved release cycle tracking by using Git tags instead of approximate date periods. - Changed project classification to a two-level structure: OpenStack (core, incubator, documentation, other) and StackForge. - Implemented correction mechanism that allows users to tweak metrics for particular commits. - Added a number of new projects (Tempest, documentation, Puppet recipes). - Added company affiliated contribution breakdown to the user's profile page. We welcome you to read, look it over, and comment. Thank you! -- Herman Narkaytis DoO Ru, PhD Tel.: +7 (8452) 674-555, +7 (8452) 431-555 Tel.: +7 (495) 640-4904 Tel.: +7 (812) 640-5904 Tel.: +38(057)728-4215 Tel.: +1 (408) 715-7897 ext 2002 http://www.mirantis.com This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Mirantis does not guarantee (that this email or the attachment's) are unaffected by computer virus, corruption or other defects. Mirantis may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Gareth *Cloud Computing, OpenStack, Fitness, Basketball* *OpenStack contributor* *Company: UnitedStack http://www.ustack.com* *My promise: if you find any spelling or grammar mistakes in my email from Mar 1 2013, notify me * *and I'll donate $1 or ￥1 to an open organization you specify.* ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Stackalytics] 0.1 release
Thank you Gareth, this makes total sense. We will make sure to include this in the next release. Alex Freedland Mirantis, Inc. On Thu, Jul 25, 2013 at 3:21 AM, Gareth academicgar...@gmail.com wrote: A suggestion: sort bugs number as int is much better than string, because '112' '8' but actually 112 8 http://stackalytics.com/companies/unitedstack On Thu, Jul 25, 2013 at 9:31 AM, Alex Freedland afreedl...@mirantis.comwrote: Roman, Thank you for your comment. I agree that is should not be the only way to look at the statistics and that is why Stackalytics also measures the number of contributions and soon will add the number of reviews. I do, however, think it a useful statistic as because not all commits are created equal. To your argument that the developers will write longer code just for the sake of statistics, I think this will not happen en mass. First and foremost, the developers care about their reputations and knowing that their code is peer-reviewed, very few will intentionally write inefficient code just to get their numbers up. Those few who will choose this route will lose the respect of their peers and consequently will not be able to contribute as much. Also, in order to deal with the situations where people can manipulate the numbers, Stackalytics allows anyone in the community to correct the line count where it does not make sense. ( https://wiki.openstack.org/wiki/Stackalytics#Commits_metrics_corrections_and_a_common_sense_approach ). We welcome any other improvements and suggestions on how to make OpenStack statistics more transparent, meaningful and reliable. Alex Freedland On Tue, Jul 23, 2013 at 7:25 AM, Roman Prykhodchenko rprikhodche...@mirantis.com wrote: I still think counting lines of code is evil because it might encourage some developers to write longer code just for statistics. On Jul 23, 2013, at 16:58 , Herman Narkaytis hnarkay...@mirantis.com wrote: Hello everyone! Mirantis http://www.mirantis.com/ is pleased to announce the release of Stackalytics http://www.stackalytics.com/ 0.1. You can find complete details on the Stackalytics wikihttps://wiki.openstack.org/wiki/Stackalytics page, but here are the brief release notes: - Changed the internal architecture. Main features include advanced real time processing and horizontal scalability. - Got rid of all 3rd party non-Apache libraries and published the source on StackForge under the Apache2 license. - Improved release cycle tracking by using Git tags instead of approximate date periods. - Changed project classification to a two-level structure: OpenStack (core, incubator, documentation, other) and StackForge. - Implemented correction mechanism that allows users to tweak metrics for particular commits. - Added a number of new projects (Tempest, documentation, Puppet recipes). - Added company affiliated contribution breakdown to the user's profile page. We welcome you to read, look it over, and comment. Thank you! -- Herman Narkaytis DoO Ru, PhD Tel.: +7 (8452) 674-555, +7 (8452) 431-555 Tel.: +7 (495) 640-4904 Tel.: +7 (812) 640-5904 Tel.: +38(057)728-4215 Tel.: +1 (408) 715-7897 ext 2002 http://www.mirantis.com This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Mirantis does not guarantee (that this email or the attachment's) are unaffected by computer virus, corruption or other defects. Mirantis may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Gareth *Cloud Computing, OpenStack, Fitness, Basketball* *OpenStack contributor* *Company: UnitedStack http://www.ustack.com* *My promise: if you find any spelling or grammar mistakes in my email from Mar 1 2013, notify me * *and I'll donate $1 or ￥1 to an open organization you specify.* ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org
Re: [openstack-dev] [Stackalytics] 0.1 release [metrics]
On 07/23/2013 07:25 AM, Roman Prykhodchenko wrote: I still think counting lines of code is evil because it might encourage some developers to write longer code just for statistics. Data becomes evil when you decide to use them for evil purposes :) I don't think that lines of code is a bad metric per se: like any other metric it becomes bad when used in an evile context. I'm getting more and more convinced that it's a mistake to show ranks and classifications in the dashboard and I'll be deleting all the ones that we may have on http://activity.openstack.org. (see https://bugs.launchpad.net/openstack-community/+bug/1205139) Counting anything in OpenStack, from commits to number of reviews is not a race, we don't need to *rank* top contributors. What we need is to identify trends. Practical example: in the report for Grizzly, most metrics put Red Hat and IBM visibly on top of many charts, while in Folsom their contributions were much lower. The story of those numbers was that IBM and Red Hat changed gear since Folsom and from 'involved' became visibly and concretely 'committed'. The story of those metrics was not that Red Hat was first or second in some sort of race. We should keep in mind that commits or bug resolutions to different projects are not directly comparable, that line charts can damage the appearance of some companies/people (loose face). Other charts need to be explored (punch cards?) and avoid direct comparisons, maybe? /stef -- Ask and answer questions on https://ask.openstack.org ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Stackalytics] 0.1 release
Roman, Thank you for your comment. I agree that is should not be the only way to look at the statistics and that is why Stackalytics also measures the number of contributions and soon will add the number of reviews. I do, however, think it a useful statistic as because not all commits are created equal. To your argument that the developers will write longer code just for the sake of statistics, I think this will not happen en mass. First and foremost, the developers care about their reputations and knowing that their code is peer-reviewed, very few will intentionally write inefficient code just to get their numbers up. Those few who will choose this route will lose the respect of their peers and consequently will not be able to contribute as much. Also, in order to deal with the situations where people can manipulate the numbers, Stackalytics allows anyone in the community to correct the line count where it does not make sense. ( https://wiki.openstack.org/wiki/Stackalytics#Commits_metrics_corrections_and_a_common_sense_approach ). We welcome any other improvements and suggestions on how to make OpenStack statistics more transparent, meaningful and reliable. Alex Freedland On Tue, Jul 23, 2013 at 7:25 AM, Roman Prykhodchenko rprikhodche...@mirantis.com wrote: I still think counting lines of code is evil because it might encourage some developers to write longer code just for statistics. On Jul 23, 2013, at 16:58 , Herman Narkaytis hnarkay...@mirantis.com wrote: Hello everyone! Mirantis http://www.mirantis.com/ is pleased to announce the release of Stackalytics http://www.stackalytics.com/ 0.1. You can find complete details on the Stackalytics wikihttps://wiki.openstack.org/wiki/Stackalytics page, but here are the brief release notes: - Changed the internal architecture. Main features include advanced real time processing and horizontal scalability. - Got rid of all 3rd party non-Apache libraries and published the source on StackForge under the Apache2 license. - Improved release cycle tracking by using Git tags instead of approximate date periods. - Changed project classification to a two-level structure: OpenStack (core, incubator, documentation, other) and StackForge. - Implemented correction mechanism that allows users to tweak metrics for particular commits. - Added a number of new projects (Tempest, documentation, Puppet recipes). - Added company affiliated contribution breakdown to the user's profile page. We welcome you to read, look it over, and comment. Thank you! -- Herman Narkaytis DoO Ru, PhD Tel.: +7 (8452) 674-555, +7 (8452) 431-555 Tel.: +7 (495) 640-4904 Tel.: +7 (812) 640-5904 Tel.: +38(057)728-4215 Tel.: +1 (408) 715-7897 ext 2002 http://www.mirantis.com This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Mirantis does not guarantee (that this email or the attachment's) are unaffected by computer virus, corruption or other defects. Mirantis may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Stackalytics] 0.1 release
Hello everyone! Mirantis http://www.mirantis.com/ is pleased to announce the release of Stackalytics http://www.stackalytics.com/ 0.1. You can find complete details on the Stackalytics wikihttps://wiki.openstack.org/wiki/Stackalytics page, but here are the brief release notes: - Changed the internal architecture. Main features include advanced real time processing and horizontal scalability. - Got rid of all 3rd party non-Apache libraries and published the source on StackForge under the Apache2 license. - Improved release cycle tracking by using Git tags instead of approximate date periods. - Changed project classification to a two-level structure: OpenStack (core, incubator, documentation, other) and StackForge. - Implemented correction mechanism that allows users to tweak metrics for particular commits. - Added a number of new projects (Tempest, documentation, Puppet recipes). - Added company affiliated contribution breakdown to the user's profile page. We welcome you to read, look it over, and comment. Thank you! -- Herman Narkaytis DoO Ru, PhD Tel.: +7 (8452) 674-555, +7 (8452) 431-555 Tel.: +7 (495) 640-4904 Tel.: +7 (812) 640-5904 Tel.: +38(057)728-4215 Tel.: +1 (408) 715-7897 ext 2002 http://www.mirantis.com This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Mirantis does not guarantee (that this email or the attachment's) are unaffected by computer virus, corruption or other defects. Mirantis may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
