ふじこ/ISSRE2010
をテンプレートにして作成
[
トップ
] [
新規
|
一覧
|
検索
|
最終更新
|
ヘルプ
]
開始行:
[[ふじこ]]
***質疑メモ [#d27c5b6e]
- Peter Popov [Session Chair](City Univ)
--Q: "it is too normal that committers have higher NPR an...
---A: committersのほうが参加期間が長い場合が多いので、だ...
--comment: RQ3の分類にnon-committersを含めてやると面白い...
- Loizos Markides (Seattle Univ)
--Q: medianよりも多い（時間と回数）開発者が大量にいた場合...
---A: medianだけでcommitters選出を行うには現状では厳しい...
--Q: average NPR and NPE per "month" →月平均は妥当？
---A: とりあえず今回のpostgreSQLでは・・・。
***渡航の詳細など… [#o6f2cdce]
- フライト~
OSAKA/KANSAI 31 OCT 10 SUN 1735 UNITED UA ...
SAN FRANCISCO 1108 FLIGHT TIME- 9:33...
SAN FRANCISCO 05 NOV 10 FRI 1140 UNITED UA ...
OSAKA/KANSAI 06 NOV 1550 FLIGHT TIME-12:10...
- ホテル~
Ramada Limited San Jose Convention Center ~
Address: 455 South 2nd Street San Jose CA United States ~
Phone: 1-408-2983500 ~
Fax: 1-408-2982477 ~
URL: http://www.ramada.com ~
~
- ISSRE開催場所~
Cisco Campus~
Address: 225 East Tasman Drive, San Jose, California 95134~
Campus Map: http://www.issre2010.org/sites/default/files/...
* ISSRE2010 [#r79a5577]
#contents
ISSRE2010~
21st IEEE International Symposium on Software Reliability...
[[http://www.issre2010.org/:http://www.issre2010.org/]]~
[[http://www.issre2010.org/content/student-papers:http://...
Submission deadline Extended!!!!!!!!~
~
- Student Paper Submission: %%July 15%% August 15, 2010
- Acceptance Notification: %%August%% September 2010
- Camera Ready Copy: %%August 30%% %%September 24%% Oct...
~
タイトル：An Analysis of Committers toward Improving the ...
原稿：&attachref(An_Analysis_of_Committers.pdf);~
カメラレディ原稿: &attachref(An_Analysis_of_Committers_Ca...
班内発練スライド：&attachref(ISSRE606_v05.pptx);~
全体発練スライド：&attachref(ISSRE606_v08.pptx);~
発表スライド：&attachref(Shoji_ISSRE606_v10.pptx);
** 予定 [#b4efb562]
- 原稿
-- 7/30日本語版原稿（IPSJ関西支部大会）完成
-- 8/4英語第１版
-- 8/11英語第２版
-- 8/15完成
-- 10/1カメラレディ原稿提出
- 発表準備
-- 10/12-15 班内スライドチェック
-- 10/20 班内発練
-- 10/22 バーカー先生チェック
-- 10/27 全体発練
- 発表
-- 10/31 渡米
-- 11/1-4 当日
-- 11/5 帰国
-- 11/6 日本着
* 査読結果 [#n87e29b1]
accept!!!
---------------------------------------------------------...
** Reviewer #1's Scores [#gc465023]
---------------------------------------------------------...
Originality of the Work: 3
Overall Quality: 2
Presentation and English: 3
Overall recommendation: 2
---------------------------------------------------------...
This paper proposes an analysis of a large open source pr...
postgresql, to quantify the quality of the contributors, ...
their activity. The authors divide contributors into comm...
non-committers, and quantify their skills by looking at t...
the exchanges in the mailing lists.
I like the idea underlying this paper. The objective of t...
certainly ambitious and difficult to achieve. However, th...
the paper can be considered only a small first step: it i...
simplification, so big as to impact the credibility of i...
First and foremost, the authors start from the assumption...
generating patches is always a synonymous of quality. Thi...
opinion. Some bugs may be very easy to fix: unexperienced...
focus on these problems and quickly produce patches to th...
much more complex to fix, and may for instance require mo...
application core. Skilled developers may choose to focus ...
problems, and leave the surface ones to the less skilled ...
According to the assumptions introduced in this paper, th...
contributors would be of the highest quality! If reaction...
into account for the evaluation of the quality of the wor...
the easiness of the modification must be taken into accou...
change cannot be compared to a radical change to the appl...
Also, the authors never take into consideration the contr...
large projects such as postgresql the contributors are li...
over the world. Their location highly impacts their respo...
delay may be solely due to the fact that the patch is rep...
developer, and edited by an american one.
Finally, committers are likely to be the most stable cont...
personal hobby or passion. It is therefore absolutely nor...
whole mailing list lifetime, they are also the most proli...
more interesting to normalize the number of produced patc...
the period of activity.
In short, while the underlying idea is absolutely valid a...
interesting results, the authors have oversimplified a bi...
problem. I would strongly invite the authors to continue ...
required sophistication to make the ultimate results more...
- 論文のベースとなっているアイデアは面白い
- 目的は野心的で，達成するのが難しいが，この論文のsolutio...
-- ただし，結果の信憑性に影響を与えるくらい大幅に簡略化し...
- パッチの作成にかかる時間を品質と（ほぼ）同義に扱ってい...
-- 初心者のcontributorsは，修正が簡単なバグに取り組んで短...
-- 逆にコアなcontributorsは複雑なバグにのみ集中し，簡単な...
-- 反応速度で品質を測るのならば，修正の容易さも同時に考慮...
- 時差による要因を考慮していない
-- 特に12時間以内の遅れは開発者のエリアによるものかもしれ...
- コミッターは（非コミッターに比べて）長期間に渡って活動...
-- 一定期間あたりの回数を数えたほうが面白い
- この研究の根底にある考えは有効で面白い結果に繋がると思...
---------------------------------------------------------...
** Reviewer #2's Scores [#j442bdca]
---------------------------------------------------------...
Originality of the Work: 3
Overall Quality: 3
Presentation and English: 2
Overall recommendation: 4
---------------------------------------------------------...
The paper studies the patch review process of the Postgre...
to characterize the “performance” of committers and non-c...
of the time they take to develop a patch and the number o...
developed.
The study presented in the paper is very interesting and ...
data, which makes it even stronger. However, I found the ...
somewhat lacking and have some criticism regarding the as...
study.
In terms of presentation, the use of English is not good....
authors to find a native speaker or someone with more exp...
correct some “style bugs” on the paper (e.g., use Figure ...
Figure1) . Moreover, since figure 1 presents a cyclic pro...
edited and reviewed many times before being committed), i...
represent it as a flowchart or using other more formal me...
loops.
One of the key assumption of the work when comparing deve...
patches require the same effort. Besides the fact that co...
responsible, thus they spend more time making their patch...
Section VI), for me, it is clear that committers solve th...
problems, the ones that affect the core of the system. Th...
greatly improved if the authors try to classify the appli...
complexity (even if the classification is not perfect). O...
to look at patch description or the discussions regarding...
solving. Another way to do that is to interview some of t...
to identify the most complex parts of the code and use th...
classify these patches. The important point here is that ...
fundamental information to classify developers working on...
on the number of patches they are adding.
- 研究内容は非常に面白く，実データによって検証されている...
- 論文の書き方にいくつか問題がある
-- 英語がよくない．ネイティブか英語の熟練者を捕まえてチェ...
-- 図１のパッチレビュープロセスの図はフローチャート（もし...
--- レビューとパッチ編集は場合によってはループするものだ...
- この論文では全てのパッチは同じもの（評価基準）として扱...
-- コミッターは責任があることなどから，より重大なバグに着...
--- バグに対する説明や議論を見てみる
--- バグの修正にどれだけの人が関わったか（議論も含めて）
--- などで複雑さを分類できる
---------------------------------------------------------...
** Reviewer #3's Scores [#wd850085]
---------------------------------------------------------...
Originality of the Work: 3
Overall Quality: 3
Presentation and English: 3
Overall recommendation: 3
---------------------------------------------------------...
The paper studies the patch review process of the open-so...
database system.
I found the main aims of the study very interesting and i...
substantial amount of effort has been spent in processing...
data.
However, the analyses could be improved by analysing in m...
confounding variables that may effect the analysis. You c...
measuring the "size" of the bug and resulting patch (by l...
of lines of code that are changed in the patch or the num...
to be changed as part of the patch). This may then allow ...
measures of the good reviewers and "patchers" rather then...
response times. Also check how sensitive the results are ...
zones that the reviwers are working at. Do you get a comp...
ordering if you factor in the timezones?
Overall, despite the short commings, I believe the paper ...
Student paper, and would benefit from the discussion in t...
the above shortcommings would have to be addressed before...
to a regular paper stream.
- 研究の狙いが面白い
-- データ分析に相当な量のeffortがなされていたこともわかり...
- より詳細に分析を行うべき
-- パッチの規模（パッチの行数や影響しているファイルの数な...
-- パッチの規模と反応時間を見ると関係がわかるかも
- レビュアーのタイムゾーンによって結果が影響するかもしれ...
- 指摘はいくつかあるが，Student Paperとしては良い
-- 会議での議論によって利益を得る（ことができる内容だと思...
#comment
終了行:
[[ふじこ]]
***質疑メモ [#d27c5b6e]
- Peter Popov [Session Chair](City Univ)
--Q: "it is too normal that committers have higher NPR an...
---A: committersのほうが参加期間が長い場合が多いので、だ...
--comment: RQ3の分類にnon-committersを含めてやると面白い...
- Loizos Markides (Seattle Univ)
--Q: medianよりも多い（時間と回数）開発者が大量にいた場合...
---A: medianだけでcommitters選出を行うには現状では厳しい...
--Q: average NPR and NPE per "month" →月平均は妥当？
---A: とりあえず今回のpostgreSQLでは・・・。
***渡航の詳細など… [#o6f2cdce]
- フライト~
OSAKA/KANSAI 31 OCT 10 SUN 1735 UNITED UA ...
SAN FRANCISCO 1108 FLIGHT TIME- 9:33...
SAN FRANCISCO 05 NOV 10 FRI 1140 UNITED UA ...
OSAKA/KANSAI 06 NOV 1550 FLIGHT TIME-12:10...
- ホテル~
Ramada Limited San Jose Convention Center ~
Address: 455 South 2nd Street San Jose CA United States ~
Phone: 1-408-2983500 ~
Fax: 1-408-2982477 ~
URL: http://www.ramada.com ~
~
- ISSRE開催場所~
Cisco Campus~
Address: 225 East Tasman Drive, San Jose, California 95134~
Campus Map: http://www.issre2010.org/sites/default/files/...
* ISSRE2010 [#r79a5577]
#contents
ISSRE2010~
21st IEEE International Symposium on Software Reliability...
[[http://www.issre2010.org/:http://www.issre2010.org/]]~
[[http://www.issre2010.org/content/student-papers:http://...
Submission deadline Extended!!!!!!!!~
~
- Student Paper Submission: %%July 15%% August 15, 2010
- Acceptance Notification: %%August%% September 2010
- Camera Ready Copy: %%August 30%% %%September 24%% Oct...
~
タイトル：An Analysis of Committers toward Improving the ...
原稿：&attachref(An_Analysis_of_Committers.pdf);~
カメラレディ原稿: &attachref(An_Analysis_of_Committers_Ca...
班内発練スライド：&attachref(ISSRE606_v05.pptx);~
全体発練スライド：&attachref(ISSRE606_v08.pptx);~
発表スライド：&attachref(Shoji_ISSRE606_v10.pptx);
** 予定 [#b4efb562]
- 原稿
-- 7/30日本語版原稿（IPSJ関西支部大会）完成
-- 8/4英語第１版
-- 8/11英語第２版
-- 8/15完成
-- 10/1カメラレディ原稿提出
- 発表準備
-- 10/12-15 班内スライドチェック
-- 10/20 班内発練
-- 10/22 バーカー先生チェック
-- 10/27 全体発練
- 発表
-- 10/31 渡米
-- 11/1-4 当日
-- 11/5 帰国
-- 11/6 日本着
* 査読結果 [#n87e29b1]
accept!!!
---------------------------------------------------------...
** Reviewer #1's Scores [#gc465023]
---------------------------------------------------------...
Originality of the Work: 3
Overall Quality: 2
Presentation and English: 3
Overall recommendation: 2
---------------------------------------------------------...
This paper proposes an analysis of a large open source pr...
postgresql, to quantify the quality of the contributors, ...
their activity. The authors divide contributors into comm...
non-committers, and quantify their skills by looking at t...
the exchanges in the mailing lists.
I like the idea underlying this paper. The objective of t...
certainly ambitious and difficult to achieve. However, th...
the paper can be considered only a small first step: it i...
simplification, so big as to impact the credibility of i...
First and foremost, the authors start from the assumption...
generating patches is always a synonymous of quality. Thi...
opinion. Some bugs may be very easy to fix: unexperienced...
focus on these problems and quickly produce patches to th...
much more complex to fix, and may for instance require mo...
application core. Skilled developers may choose to focus ...
problems, and leave the surface ones to the less skilled ...
According to the assumptions introduced in this paper, th...
contributors would be of the highest quality! If reaction...
into account for the evaluation of the quality of the wor...
the easiness of the modification must be taken into accou...
change cannot be compared to a radical change to the appl...
Also, the authors never take into consideration the contr...
large projects such as postgresql the contributors are li...
over the world. Their location highly impacts their respo...
delay may be solely due to the fact that the patch is rep...
developer, and edited by an american one.
Finally, committers are likely to be the most stable cont...
personal hobby or passion. It is therefore absolutely nor...
whole mailing list lifetime, they are also the most proli...
more interesting to normalize the number of produced patc...
the period of activity.
In short, while the underlying idea is absolutely valid a...
interesting results, the authors have oversimplified a bi...
problem. I would strongly invite the authors to continue ...
required sophistication to make the ultimate results more...
- 論文のベースとなっているアイデアは面白い
- 目的は野心的で，達成するのが難しいが，この論文のsolutio...
-- ただし，結果の信憑性に影響を与えるくらい大幅に簡略化し...
- パッチの作成にかかる時間を品質と（ほぼ）同義に扱ってい...
-- 初心者のcontributorsは，修正が簡単なバグに取り組んで短...
-- 逆にコアなcontributorsは複雑なバグにのみ集中し，簡単な...
-- 反応速度で品質を測るのならば，修正の容易さも同時に考慮...
- 時差による要因を考慮していない
-- 特に12時間以内の遅れは開発者のエリアによるものかもしれ...
- コミッターは（非コミッターに比べて）長期間に渡って活動...
-- 一定期間あたりの回数を数えたほうが面白い
- この研究の根底にある考えは有効で面白い結果に繋がると思...
---------------------------------------------------------...
** Reviewer #2's Scores [#j442bdca]
---------------------------------------------------------...
Originality of the Work: 3
Overall Quality: 3
Presentation and English: 2
Overall recommendation: 4
---------------------------------------------------------...
The paper studies the patch review process of the Postgre...
to characterize the “performance” of committers and non-c...
of the time they take to develop a patch and the number o...
developed.
The study presented in the paper is very interesting and ...
data, which makes it even stronger. However, I found the ...
somewhat lacking and have some criticism regarding the as...
study.
In terms of presentation, the use of English is not good....
authors to find a native speaker or someone with more exp...
correct some “style bugs” on the paper (e.g., use Figure ...
Figure1) . Moreover, since figure 1 presents a cyclic pro...
edited and reviewed many times before being committed), i...
represent it as a flowchart or using other more formal me...
loops.
One of the key assumption of the work when comparing deve...
patches require the same effort. Besides the fact that co...
responsible, thus they spend more time making their patch...
Section VI), for me, it is clear that committers solve th...
problems, the ones that affect the core of the system. Th...
greatly improved if the authors try to classify the appli...
complexity (even if the classification is not perfect). O...
to look at patch description or the discussions regarding...
solving. Another way to do that is to interview some of t...
to identify the most complex parts of the code and use th...
classify these patches. The important point here is that ...
fundamental information to classify developers working on...
on the number of patches they are adding.
- 研究内容は非常に面白く，実データによって検証されている...
- 論文の書き方にいくつか問題がある
-- 英語がよくない．ネイティブか英語の熟練者を捕まえてチェ...
-- 図１のパッチレビュープロセスの図はフローチャート（もし...
--- レビューとパッチ編集は場合によってはループするものだ...
- この論文では全てのパッチは同じもの（評価基準）として扱...
-- コミッターは責任があることなどから，より重大なバグに着...
--- バグに対する説明や議論を見てみる
--- バグの修正にどれだけの人が関わったか（議論も含めて）
--- などで複雑さを分類できる
---------------------------------------------------------...
** Reviewer #3's Scores [#wd850085]
---------------------------------------------------------...
Originality of the Work: 3
Overall Quality: 3
Presentation and English: 3
Overall recommendation: 3
---------------------------------------------------------...
The paper studies the patch review process of the open-so...
database system.
I found the main aims of the study very interesting and i...
substantial amount of effort has been spent in processing...
data.
However, the analyses could be improved by analysing in m...
confounding variables that may effect the analysis. You c...
measuring the "size" of the bug and resulting patch (by l...
of lines of code that are changed in the patch or the num...
to be changed as part of the patch). This may then allow ...
measures of the good reviewers and "patchers" rather then...
response times. Also check how sensitive the results are ...
zones that the reviwers are working at. Do you get a comp...
ordering if you factor in the timezones?
Overall, despite the short commings, I believe the paper ...
Student paper, and would benefit from the discussion in t...
the above shortcommings would have to be addressed before...
to a regular paper stream.
- 研究の狙いが面白い
-- データ分析に相当な量のeffortがなされていたこともわかり...
- より詳細に分析を行うべき
-- パッチの規模（パッチの行数や影響しているファイルの数な...
-- パッチの規模と反応時間を見ると関係がわかるかも
- レビュアーのタイムゾーンによって結果が影響するかもしれ...
- 指摘はいくつかあるが，Student Paperとしては良い
-- 会議での議論によって利益を得る（ことができる内容だと思...
#comment
ページ名:
![[PukiWiki]](image/wadanyan.png "[PukiWiki]")
