[jira] [Commented] (COMDEV-485) [GSOC] [SkyWalking] GSOC 2023 Tasks
[ https://issues.apache.org/jira/browse/COMDEV-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688041#comment-17688041 ] Yihao Chen commented on COMDEV-485: --- There will be at least two tasks for students. Should I host the ideas in this one issue or create separate ones for each? > [GSOC] [SkyWalking] GSOC 2023 Tasks > --- > > Key: COMDEV-485 > URL: https://issues.apache.org/jira/browse/COMDEV-485 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: Yihao Chen >Priority: Major > Labels: SkyWalking, full-time, gsoc2023 > Original Estimate: 350h > Remaining Estimate: 350h > > This is a placeholder for Apache SkyWalking GSOC 2023 ideas, we are currently > brainstorming for projects and will update asap. > There will be at least two projects, one around AIOps algorithms. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] mjfoulks opened a new pull request, #84: Update etiquette.md
mjfoulks opened a new pull request, #84: URL: https://github.com/apache/comdev-site/pull/84 I suggested changing "One Member's Guidelines" to "General Communication Guidelines." I took the guidelines in this section and softened the language, while trying to keep the spirit of the guidelines in place. My goal was to make this section feel more warm and welcoming, as well as feel more helpful. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] clr-apache commented on pull request #82: Update newcommitter.md
clr-apache commented on PR #82: URL: https://github.com/apache/comdev-site/pull/82#issuecomment-1428478068 Can someone with commit privileges please merge patch1? Thanks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] bproffitt commented on pull request #82: Update newcommitter.md
bproffitt commented on PR #82: URL: https://github.com/apache/comdev-site/pull/82#issuecomment-1428482573 @sebbASF Do you still have outstanding review requests? GitHub thinks you do. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] rbowen commented on pull request #44: Update mentorprogrammeapplication.md
rbowen commented on PR #44: URL: https://github.com/apache/comdev-site/pull/44#issuecomment-1428666799 Closing the PR, since it's in conflict, and we don't have a mentoring program. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] rbowen closed pull request #44: Update mentorprogrammeapplication.md
rbowen closed pull request #44: Update mentorprogrammeapplication.md URL: https://github.com/apache/comdev-site/pull/44 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] rbowen merged pull request #81: [Fixed]: Updated the broken link for the ASF intro slide
rbowen merged PR #81: URL: https://github.com/apache/comdev-site/pull/81 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-454) Report Wizard gives "[object Response]" error with underlying 503
[ https://issues.apache.org/jira/browse/COMDEV-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688144#comment-17688144 ] Andrew Musselman commented on COMDEV-454: - Working for me too, [~curcuru] is this resolved? > Report Wizard gives "[object Response]" error with underlying 503 > - > > Key: COMDEV-454 > URL: https://issues.apache.org/jira/browse/COMDEV-454 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool > Environment: Mac/FF >Reporter: Shane Curcuru >Priority: Major > > As reported elsewhere, navigating to [https://reporter.apache.org/wizard/] > pops up a notification error, and does nothing else. > Console shows an underlying 503: > /*** ASF Board Report Wizard initializing / > [wizard.js:1792:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Fetching JSON resource at /reportingcycles.json > [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > putting /reportingcycles.json in escrow... > [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Successfully fetched /reportingcycles.json > [wizard.js:119:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Fetching JSON resource at /api/overview > [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > putting /api/overview in escrow... > [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > URL /api/overview returned HTTP code 503, snapping! > [wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-478) https://reporter.apache.org/addrelease.html?sling leads to page crash with Chrome
[ https://issues.apache.org/jira/browse/COMDEV-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688145#comment-17688145 ] Andrew Musselman commented on COMDEV-478: - [~kwin] is this still an open issue, not reproing here now > https://reporter.apache.org/addrelease.html?sling leads to page crash with > Chrome > - > > Key: COMDEV-478 > URL: https://issues.apache.org/jira/browse/COMDEV-478 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool > Environment: Chrome Version 104.0.5112.101 (Official Build) (arm64) > Mac OS 12.5.1 >Reporter: Konrad Windszus >Priority: Major > > When opening the page [https://reporter.apache.org/addrelease.html?sling] it > crashes in Google Chrome after a few seconds with Error Code 5 > ([https://support.google.com/chrome/answer/95669?visit_id=637966697117475835-2175500643&p=e_awsnap&rd=1#zippy=%2Cpage-loading-error-codes-and-issues]). > With Firefox it does load (but takes a while). > I assume this is due to the huge amount of past releases done by Sling. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-454) Report Wizard gives "[object Response]" error with underlying 503
[ https://issues.apache.org/jira/browse/COMDEV-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gruno closed COMDEV-454. --- Resolution: Fixed This is an occasionally occurring issue, it happens when the underlying service can't start up properly. It is addressed for now, but may crop up later. > Report Wizard gives "[object Response]" error with underlying 503 > - > > Key: COMDEV-454 > URL: https://issues.apache.org/jira/browse/COMDEV-454 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool > Environment: Mac/FF >Reporter: Shane Curcuru >Priority: Major > > As reported elsewhere, navigating to [https://reporter.apache.org/wizard/] > pops up a notification error, and does nothing else. > Console shows an underlying 503: > /*** ASF Board Report Wizard initializing / > [wizard.js:1792:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Fetching JSON resource at /reportingcycles.json > [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > putting /reportingcycles.json in escrow... > [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Successfully fetched /reportingcycles.json > [wizard.js:119:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Fetching JSON resource at /api/overview > [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > putting /api/overview in escrow... > [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > URL /api/overview returned HTTP code 503, snapping! > [wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
[
https://issues.apache.org/jira/browse/COMDEV-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688155#comment-17688155
]
Andrew Musselman commented on COMDEV-429:
-
[~szetszwo] are you sure this patch works? I tried it in a JS console online
and got an error that looks like it's complaining that a string doesn't have a
`.format` function:
{{> searchBestRatioString(10,3)}}
{{ TypeError { "roughly %u:%u".format is not a function } }}
> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
> Issue Type: New Feature
> Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give
> the best ratio. For example, in
> [https://reporter.apache.org/wizard/statistics?ratis] ,
> - There are currently 27 committers and 17 PMC members in this project.
> - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Comment Edited] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
[
https://issues.apache.org/jira/browse/COMDEV-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688155#comment-17688155
]
Andrew Musselman edited comment on COMDEV-429 at 2/13/23 10:02 PM:
---
[~szetszwo] are you sure this patch works? I tried it in a JS console online
and got an error that looks like it's complaining that a string doesn't have a
`.format` function:
{{> searchBestRatioString(10,3)}}
{{TypeError { "roughly %u:%u".format is not a function }}}
was (Author: akm):
[~szetszwo] are you sure this patch works? I tried it in a JS console online
and got an error that looks like it's complaining that a string doesn't have a
`.format` function:
{{> searchBestRatioString(10,3)}}
{{ TypeError { "roughly %u:%u".format is not a function } }}
> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
> Issue Type: New Feature
> Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give
> the best ratio. For example, in
> [https://reporter.apache.org/wizard/statistics?ratis] ,
> - There are currently 27 committers and 17 PMC members in this project.
> - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Comment Edited] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
[
https://issues.apache.org/jira/browse/COMDEV-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688155#comment-17688155
]
Andrew Musselman edited comment on COMDEV-429 at 2/13/23 10:03 PM:
---
[~szetszwo] are you sure this patch works? I tried it in a JS console online
and got an error that looks like it's complaining that a string doesn't have a
`.format` function:
> searchBestRatioString(10,3)
{{TypeError \{ "roughly %u:%u".format is not a function }}}
was (Author: akm):
[~szetszwo] are you sure this patch works? I tried it in a JS console online
and got an error that looks like it's complaining that a string doesn't have a
`.format` function:
{{> searchBestRatioString(10,3)}}
{{TypeError { "roughly %u:%u".format is not a function }}}
> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
> Issue Type: New Feature
> Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give
> the best ratio. For example, in
> [https://reporter.apache.org/wizard/statistics?ratis] ,
> - There are currently 27 committers and 17 PMC members in this project.
> - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
[ https://issues.apache.org/jira/browse/COMDEV-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688157#comment-17688157 ] Daniel Gruno commented on COMDEV-429: - the format string prototype is defined in https://svn.apache.org/repos/asf/comdev/reporter.apache.org/trunk/site/wizard/js/source/base-js-extensions.js There is a build.sh script in https://svn.apache.org/repos/asf/comdev/reporter.apache.org/trunk/site/wizard/js/source/ for compiling the end result. > The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio > - > > Key: COMDEV-429 > URL: https://issues.apache.org/jira/browse/COMDEV-429 > Project: Community Development > Issue Type: New Feature > Components: Reporter Tool >Reporter: Tsz-wo Sze >Priority: Minor > Attachments: 20220705_COMDEV-429.patch > > > Thanks a lot for providing the Board Report Wizard > ([https://reporter.apache.org/wizard/])! It is a great tool which helps save > a lot of time. > I notice that the Committer-to-PMC ratio computed by the tool may not give > the best ratio. For example, in > [https://reporter.apache.org/wizard/statistics?ratis] , > - There are currently 27 committers and 17 PMC members in this project. > - The Committer-to-PMC ratio is roughly 7:5. > We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
[
https://issues.apache.org/jira/browse/COMDEV-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688167#comment-17688167
]
Andrew Musselman commented on COMDEV-429:
-
Thanks [~humbedooh]
Seems to work fine on several inputs. Looks like a simple merge. +1
{{searchBestRatioString(10,3)}}
roughly 7:2
searchBestRatioString(3,10)
roughly 2:7
searchBestRatioString(100,3)
roughly 1:0
searchBestRatioString(3,100)
roughly 0:1
searchBestRatioString(9,3)
3:1
searchBestRatioString(3,9)
{{{}{}}}{{{}1:3{}}}
> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
> Issue Type: New Feature
> Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give
> the best ratio. For example, in
> [https://reporter.apache.org/wizard/statistics?ratis] ,
> - There are currently 27 committers and 17 PMC members in this project.
> - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Comment Edited] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
[
https://issues.apache.org/jira/browse/COMDEV-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688167#comment-17688167
]
Andrew Musselman edited comment on COMDEV-429 at 2/13/23 10:34 PM:
---
Thanks [~humbedooh]
Seems to work fine on several inputs. Looks like a simple merge. +1
searchBestRatioString(10,3)
{{roughly 7:2}}
{{searchBestRatioString(3,10) }}
{{roughly 2:7}}
{{searchBestRatioString(100,3)}}
{{roughly 1:0}}
{{searchBestRatioString(3,100) }}
{{roughly 0:1}}
{{searchBestRatioString(9,3) }}
{{3:1}}
{{searchBestRatioString(3,9)}}
1:3
was (Author: akm):
Thanks [~humbedooh]
Seems to work fine on several inputs. Looks like a simple merge. +1
{{searchBestRatioString(10,3)}}
roughly 7:2
searchBestRatioString(3,10)
roughly 2:7
searchBestRatioString(100,3)
roughly 1:0
searchBestRatioString(3,100)
roughly 0:1
searchBestRatioString(9,3)
3:1
searchBestRatioString(3,9)
{{{}{}}}{{{}1:3{}}}
> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
> Issue Type: New Feature
> Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give
> the best ratio. For example, in
> [https://reporter.apache.org/wizard/statistics?ratis] ,
> - There are currently 27 committers and 17 PMC members in this project.
> - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Comment Edited] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
[
https://issues.apache.org/jira/browse/COMDEV-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688167#comment-17688167
]
Andrew Musselman edited comment on COMDEV-429 at 2/13/23 10:35 PM:
---
Thanks [~humbedooh]
Seems to work fine on several inputs. Looks like a simple merge. +1
{{searchBestRatioString(10,3)}}
{{roughly 7:2}}
{{searchBestRatioString(3,10)}}
{{roughly 2:7}}
{{searchBestRatioString(100,3)}}
{{roughly 1:0}}
{{searchBestRatioString(3,100)}}
{{roughly 0:1}}
{{searchBestRatioString(9,3)}}
{{3:1}}
{{searchBestRatioString(3,9)}}
{{1:3}}
was (Author: akm):
Thanks [~humbedooh]
Seems to work fine on several inputs. Looks like a simple merge. +1
searchBestRatioString(10,3)
{{roughly 7:2}}
{{searchBestRatioString(3,10) }}
{{roughly 2:7}}
{{searchBestRatioString(100,3)}}
{{roughly 1:0}}
{{searchBestRatioString(3,100) }}
{{roughly 0:1}}
{{searchBestRatioString(9,3) }}
{{3:1}}
{{searchBestRatioString(3,9)}}
1:3
> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
> Issue Type: New Feature
> Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give
> the best ratio. For example, in
> [https://reporter.apache.org/wizard/statistics?ratis] ,
> - There are currently 27 committers and 17 PMC members in this project.
> - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-425) Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project
[
https://issues.apache.org/jira/browse/COMDEV-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688169#comment-17688169
]
Andrew Musselman commented on COMDEV-425:
-
[~sharan] and [~mikemccand] looks like this is still happening for lucene; is
there a ticket open on kibble that could be linked here?
> Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project
> --
>
> Key: COMDEV-425
> URL: https://issues.apache.org/jira/browse/COMDEV-425
> Project: Community Development
> Issue Type: Bug
> Components: Reporter Tool
>Reporter: Michael McCandless
>Priority: Minor
> Attachments: Screen Shot 2021-09-09 at 5.34.16 PM.png, Screen Shot
> 2021-10-21 at 8.55.58 AM.png, image-2021-10-21-08-56-15-016.png,
> lucene-kibble.png
>
>
> I am working on the quarterly board report for Apache Lucene, and noticed
> under the "Community Health" section that the "Busiest GitHub topics" seems
> to be missing the "lucene" GitHub repository.
> It seems to contain only {{lucene-solr}}, {{lucenenet}}, {{lucene-site}}.
> Likely something needs to be updated because Solr split out of Lucene, and
> Lucene's main (to be 9.0 release soon) branch is on a new(-ish) {{lucene}}
> repository: [https://github.com/apache/lucene]
> !Screen Shot 2021-09-09 at 5.34.16 PM.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-416) make reporter wizard send notifications to private@
[ https://issues.apache.org/jira/browse/COMDEV-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688172#comment-17688172 ] Andrew Musselman commented on COMDEV-416: - In the `https://reporter.apache.org/wizard` page the reporter data can be included directly into the board report editor. Does that satisfy this request as another solution? > make reporter wizard send notifications to private@ > --- > > Key: COMDEV-416 > URL: https://issues.apache.org/jira/browse/COMDEV-416 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Herve Boutemy >Priority: Major > > Reporter wizard is awesome to help the PMC chair prepare and submit board > reports. > The only key missing step is sending drafts and/or final submitted report to > the PMC, for review or just info -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-317) tabs hidden if maildata.json is empty
[ https://issues.apache.org/jira/browse/COMDEV-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688176#comment-17688176 ] Andrew Musselman commented on COMDEV-317: - [~sebb] is this a quick fix in `render.js`? I see `json.mail[pmc]` as a check among other things but it's not obvious where `data/maildata.json` would show up empty. > tabs hidden if maildata.json is empty > - > > Key: COMDEV-317 > URL: https://issues.apache.org/jira/browse/COMDEV-317 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Sebb >Priority: Minor > > See COMDEV-316 > The display tabs were hidden and there were other problems when the file > data/maildata.json was an empty JSON structure. > The Javascript render.js should be able to handle this better. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-317) tabs hidden if maildata.json is empty
[ https://issues.apache.org/jira/browse/COMDEV-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688178#comment-17688178 ] Sebb commented on COMDEV-317: - Sorry, I have no idea > tabs hidden if maildata.json is empty > - > > Key: COMDEV-317 > URL: https://issues.apache.org/jira/browse/COMDEV-317 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Sebb >Priority: Minor > > See COMDEV-316 > The display tabs were hidden and there were other problems when the file > data/maildata.json was an empty JSON structure. > The Javascript render.js should be able to handle this better. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-295) Consider whether to extract mod_mbox statistics locally
[ https://issues.apache.org/jira/browse/COMDEV-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688179#comment-17688179 ] Andrew Musselman commented on COMDEV-295: - [~sebb] Where would the "updating the mod_mbox indexes" happen, somewhere outside the `mailglomper2.py` script? Is this still open, there is a filter `c = re.match(b"^From \S+ (.+)", line) # match as binary` in that script now. > Consider whether to extract mod_mbox statistics locally > --- > > Key: COMDEV-295 > URL: https://issues.apache.org/jira/browse/COMDEV-295 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > At present the reporter tool uses the mailglomper script to extract > information about the number and timing of mails sent to each list. > To do this, it has to download the entire mailbox, even though it only needs > the ^From_ lines. > Whilst the code attempts to avoid unnecessary downloads (by checking dates > and sizes), for busy mbox files there can be a lot of network traffic. > It might make sense for some initial data extraction to be done locally and > cached in a file. > This could be done as part of updating the mod_mbox indexes. > For example, the script could extract just the ^From_ lines into a separate > file and store that alongside the .mbox file. Mailglomper would read the much > abbreviated file instead. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-317) tabs hidden if maildata.json is empty
[ https://issues.apache.org/jira/browse/COMDEV-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688180#comment-17688180 ] Andrew Musselman commented on COMDEV-317: - If this only happened after a mail server problem in 2019 and has not been an ongoing issue can we close this? > tabs hidden if maildata.json is empty > - > > Key: COMDEV-317 > URL: https://issues.apache.org/jira/browse/COMDEV-317 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Sebb >Priority: Minor > > See COMDEV-316 > The display tabs were hidden and there were other problems when the file > data/maildata.json was an empty JSON structure. > The Javascript render.js should be able to handle this better. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-294) scandist.py: detect and report deprecated hash types
[ https://issues.apache.org/jira/browse/COMDEV-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688182#comment-17688182 ] Andrew Musselman commented on COMDEV-294: - Is this still relevant? I remember infra doing a cleanup with projects a while back, maybe in 2020? > scandist.py: detect and report deprecated hash types > > > Key: COMDEV-294 > URL: https://issues.apache.org/jira/browse/COMDEV-294 > Project: Community Development > Issue Type: New Feature > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > scandist.py could be enhanced to detect deprecated hash types (.md5/.sha1) > and send an email to the committer linking to the policy. > For the earliest warning, it should be done for dist/dev. > However some projects may commit directly to dist/release, so it might be > necessary to check dist/release as well. > Generally, all the files for a release artifact are added as part of the same > commit, so it should be possible to detect where a project is providing > deprecated hashes in addition (e.g. for historic purposes). To avoid too many > messages, such commits could be ignored for the present. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-295) Consider whether to extract mod_mbox statistics locally
[ https://issues.apache.org/jira/browse/COMDEV-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688183#comment-17688183 ] Daniel Gruno commented on COMDEV-295: - The mail stats will, as alluded to on the dev list, need a complete rework. I don't have cycles for it right now, but the basic premise would be: for each project: grab last six months of stats from lists.apache.org for each of their lists > Consider whether to extract mod_mbox statistics locally > --- > > Key: COMDEV-295 > URL: https://issues.apache.org/jira/browse/COMDEV-295 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > At present the reporter tool uses the mailglomper script to extract > information about the number and timing of mails sent to each list. > To do this, it has to download the entire mailbox, even though it only needs > the ^From_ lines. > Whilst the code attempts to avoid unnecessary downloads (by checking dates > and sizes), for busy mbox files there can be a lot of network traffic. > It might make sense for some initial data extraction to be done locally and > cached in a file. > This could be done as part of updating the mod_mbox indexes. > For example, the script could extract just the ^From_ lines into a separate > file and store that alongside the .mbox file. Mailglomper would read the much > abbreviated file instead. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-295) Consider whether to extract mod_mbox statistics locally
[ https://issues.apache.org/jira/browse/COMDEV-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-295. - Resolution: Abandoned AFAICT mailglomper2.py is obsolete. > Consider whether to extract mod_mbox statistics locally > --- > > Key: COMDEV-295 > URL: https://issues.apache.org/jira/browse/COMDEV-295 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > At present the reporter tool uses the mailglomper script to extract > information about the number and timing of mails sent to each list. > To do this, it has to download the entire mailbox, even though it only needs > the ^From_ lines. > Whilst the code attempts to avoid unnecessary downloads (by checking dates > and sizes), for busy mbox files there can be a lot of network traffic. > It might make sense for some initial data extraction to be done locally and > cached in a file. > This could be done as part of updating the mod_mbox indexes. > For example, the script could extract just the ^From_ lines into a separate > file and store that alongside the .mbox file. Mailglomper would read the much > abbreviated file instead. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-294) scandist.py: detect and report deprecated hash types
[ https://issues.apache.org/jira/browse/COMDEV-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688189#comment-17688189 ] Sebb commented on COMDEV-294: - AFAIK there are still projects which release obsolete hashes. Whether it is worth the effort, I don't know. > scandist.py: detect and report deprecated hash types > > > Key: COMDEV-294 > URL: https://issues.apache.org/jira/browse/COMDEV-294 > Project: Community Development > Issue Type: New Feature > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > scandist.py could be enhanced to detect deprecated hash types (.md5/.sha1) > and send an email to the committer linking to the policy. > For the earliest warning, it should be done for dist/dev. > However some projects may commit directly to dist/release, so it might be > necessary to check dist/release as well. > Generally, all the files for a release artifact are added as part of the same > commit, so it should be possible to detect where a project is providing > deprecated hashes in addition (e.g. for historic purposes). To avoid too many > messages, such commits could be ignored for the present. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-293) scandist does not detect releases renamed from dist/dev
[ https://issues.apache.org/jira/browse/COMDEV-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688192#comment-17688192 ] Andrew Musselman commented on COMDEV-293: - Is this still relevant, are there people needing it, etc.? I see it's looking for this pattern `RELEASE_MATCH = r"^release/([^/]+)/" # match any name followed by /`. Not immediately clear why it's not catching the path in `A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901)` > scandist does not detect releases renamed from dist/dev > --- > > Key: COMDEV-293 > URL: https://issues.apache.org/jira/browse/COMDEV-293 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > The scandist script ignores commits which only affect a directory. > This is OK for simple directory creation, but means that releases which are > created by renaming/copying from dist/dev are ignored. > For example the following did not cause an email to be sent: > $ svn log -r27902 -v https://dist.apache.org/repos/dist/ > > r27902 | tgraves | 2018-07-03 19:08:54 +0100 (Tue, 03 Jul 2018) | 2 lines > Changed paths: >D /dev/spark/v2.2.2-rc2-bin >A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901) > Publish spark 2.2.2 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
[ https://issues.apache.org/jira/browse/COMDEV-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688193#comment-17688193 ] Sebb commented on COMDEV-429: - Note that the ratio is meaningless for projects which allow all ASF committers to update their code. e.g. Commons > The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio > - > > Key: COMDEV-429 > URL: https://issues.apache.org/jira/browse/COMDEV-429 > Project: Community Development > Issue Type: New Feature > Components: Reporter Tool >Reporter: Tsz-wo Sze >Priority: Minor > Attachments: 20220705_COMDEV-429.patch > > > Thanks a lot for providing the Board Report Wizard > ([https://reporter.apache.org/wizard/])! It is a great tool which helps save > a lot of time. > I notice that the Committer-to-PMC ratio computed by the tool may not give > the best ratio. For example, in > [https://reporter.apache.org/wizard/statistics?ratis] , > - There are currently 27 committers and 17 PMC members in this project. > - The Committer-to-PMC ratio is roughly 7:5. > We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-293) scandist does not detect releases renamed from dist/dev
[ https://issues.apache.org/jira/browse/COMDEV-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688194#comment-17688194 ] Sebb commented on COMDEV-293: - Either the tool is not needed at all, or it should report all releases. > scandist does not detect releases renamed from dist/dev > --- > > Key: COMDEV-293 > URL: https://issues.apache.org/jira/browse/COMDEV-293 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > The scandist script ignores commits which only affect a directory. > This is OK for simple directory creation, but means that releases which are > created by renaming/copying from dist/dev are ignored. > For example the following did not cause an email to be sent: > $ svn log -r27902 -v https://dist.apache.org/repos/dist/ > > r27902 | tgraves | 2018-07-03 19:08:54 +0100 (Tue, 03 Jul 2018) | 2 lines > Changed paths: >D /dev/spark/v2.2.2-rc2-bin >A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901) > Publish spark 2.2.2 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] sebbASF commented on pull request #82: Update newcommitter.md
sebbASF commented on PR #82: URL: https://github.com/apache/comdev-site/pull/82#issuecomment-1428892926 What happened to the Committer Accept Template? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
[ https://issues.apache.org/jira/browse/COMDEV-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688197#comment-17688197 ] Andrew Musselman commented on COMDEV-429: - If it were me I would just show the raw numbers. If there's additional commentary like [~sebb] mentions it could be noted as info on the page. > The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio > - > > Key: COMDEV-429 > URL: https://issues.apache.org/jira/browse/COMDEV-429 > Project: Community Development > Issue Type: New Feature > Components: Reporter Tool >Reporter: Tsz-wo Sze >Priority: Minor > Attachments: 20220705_COMDEV-429.patch > > > Thanks a lot for providing the Board Report Wizard > ([https://reporter.apache.org/wizard/])! It is a great tool which helps save > a lot of time. > I notice that the Committer-to-PMC ratio computed by the tool may not give > the best ratio. For example, in > [https://reporter.apache.org/wizard/statistics?ratis] , > - There are currently 27 committers and 17 PMC members in this project. > - The Committer-to-PMC ratio is roughly 7:5. > We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-291) Prefetch all data/JIRA/*.json files
[ https://issues.apache.org/jira/browse/COMDEV-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688198#comment-17688198 ] Andrew Musselman commented on COMDEV-291: - Is `readjira.py` still used? > Prefetch all data/JIRA/*.json files > --- > > Key: COMDEV-291 > URL: https://issues.apache.org/jira/browse/COMDEV-291 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > script/readjira.py keeps the data/JIRA/*.json files up to date as a cron job. > However it does not create them initially. > That is done by site/getjson.py which is called from the GUI. > This can result in a long wait (possibly causing a timeout failure) if there > are many missing files for the currently logged in user. > Also the code to create and parse the files is duplicated in the scripts. > It might be better for all the files to be fetched in the readjira.py cron > job. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-295) Consider whether to extract mod_mbox statistics locally
[
https://issues.apache.org/jira/browse/COMDEV-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688199#comment-17688199
]
Andrew Musselman commented on COMDEV-295:
-
It's still referred to in the readme fwiw, maybe that needs more TLC
{{crontab -l -u www-data: (Not currently stored in puppet)
# m h dom mon dow command
00 4,12,20 * * * cd /var/www/reporter.apache.org/scripts && ./python3logger.sh
parsepmcs.py
00 01 * * * cd /var/www/reporter.apache.org/scripts && ./python3logger.sh
mailglomper2.py
00 09 * * * cd /var/www/reporter.apache.org/scripts && ./python3logger.sh
readjira.py
10 00 * * * cd /var/www/reporter.apache.org/scripts && ./python3logger.sh
reportingcycles.py
20 00 * * * cd /var/www/reporter.apache.org/scripts && ./python3logger.sh
pmcdates.py
30 00 * * * cd /var/www/reporter.apache.org/scripts && ./python3logger.sh
bugzillastats.py
50 00 * * * cd /var/www/reporter.apache.org/scripts && ./python3logger.sh
health.py
32 * * * * cd /var/www/reporter.apache.org/scripts && ./python3logger.sh
readchecker.py
*/15 * * * * pgrep -f "gunicorn3.*wsgi:app" || (cd
/var/www/reporter.apache.org/scripts && gunicorn3 -b 127.0.0.1 -w 6 -D wsgi:app
&& echo "restarting gunicorn")}}
> Consider whether to extract mod_mbox statistics locally
> ---
>
> Key: COMDEV-295
> URL: https://issues.apache.org/jira/browse/COMDEV-295
> Project: Community Development
> Issue Type: Improvement
> Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> At present the reporter tool uses the mailglomper script to extract
> information about the number and timing of mails sent to each list.
> To do this, it has to download the entire mailbox, even though it only needs
> the ^From_ lines.
> Whilst the code attempts to avoid unnecessary downloads (by checking dates
> and sizes), for busy mbox files there can be a lot of network traffic.
> It might make sense for some initial data extraction to be done locally and
> cached in a file.
> This could be done as part of updating the mod_mbox indexes.
> For example, the script could extract just the ^From_ lines into a separate
> file and store that alongside the .mbox file. Mailglomper would read the much
> abbreviated file instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-288) Request "Projects Directory" migration to GIT
[
https://issues.apache.org/jira/browse/COMDEV-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688204#comment-17688204
]
Andrew Musselman commented on COMDEV-288:
-
I see a lot of activity in that thread in the archives; [~sebb] and [~hboutemy]
is this still underway?
> Request "Projects Directory" migration to GIT
> -
>
> Key: COMDEV-288
> URL: https://issues.apache.org/jira/browse/COMDEV-288
> Project: Community Development
> Issue Type: SVN->GIT Migration
> Components: Projects Tool, Reporter Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> Dear all,
> is it possible for you to plan SVN to GIT migration for "Projects Directory"
> project ?
> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/{color}]
> Thank you,
> Regards.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-295) Consider whether to extract mod_mbox statistics locally
[ https://issues.apache.org/jira/browse/COMDEV-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688205#comment-17688205 ] Sebb commented on COMDEV-295: - The mailglomper line can be deleted. There are probably other stale entries now that kibble is being used. > Consider whether to extract mod_mbox statistics locally > --- > > Key: COMDEV-295 > URL: https://issues.apache.org/jira/browse/COMDEV-295 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > At present the reporter tool uses the mailglomper script to extract > information about the number and timing of mails sent to each list. > To do this, it has to download the entire mailbox, even though it only needs > the ^From_ lines. > Whilst the code attempts to avoid unnecessary downloads (by checking dates > and sizes), for busy mbox files there can be a lot of network traffic. > It might make sense for some initial data extraction to be done locally and > cached in a file. > This could be done as part of updating the mod_mbox indexes. > For example, the script could extract just the ^From_ lines into a separate > file and store that alongside the .mbox file. Mailglomper would read the much > abbreviated file instead. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page
[ https://issues.apache.org/jira/browse/COMDEV-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688207#comment-17688207 ] Andrew Musselman commented on COMDEV-227: - It is slow to load but I do see the page filling up; [~rombert] is this something you're actively looking for still? > Only list last X releases and the add/remove release page > - > > Key: COMDEV-227 > URL: https://issues.apache.org/jira/browse/COMDEV-227 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Robert Munteanu >Priority: Major > > In the Apache Sling project we have a large number of releases as we have > many independent modules. When loading the > https://reporter.apache.org/addrelease.html?sling page, it takes upwards of > 10 seconds to load. It would be great if only the last X (50?) releases were > shown, and then a "load all" link would be available at the bottom. > This would greatly speed up our usage of this tool. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-295) Consider whether to extract mod_mbox statistics locally
[
https://issues.apache.org/jira/browse/COMDEV-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688210#comment-17688210
]
Andrew Musselman commented on COMDEV-295:
-
Is that crontab running here still?
{{The site runs on the host projects-vm3.a.o at present (May 2021)}}
> Consider whether to extract mod_mbox statistics locally
> ---
>
> Key: COMDEV-295
> URL: https://issues.apache.org/jira/browse/COMDEV-295
> Project: Community Development
> Issue Type: Improvement
> Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> At present the reporter tool uses the mailglomper script to extract
> information about the number and timing of mails sent to each list.
> To do this, it has to download the entire mailbox, even though it only needs
> the ^From_ lines.
> Whilst the code attempts to avoid unnecessary downloads (by checking dates
> and sizes), for busy mbox files there can be a lot of network traffic.
> It might make sense for some initial data extraction to be done locally and
> cached in a file.
> This could be done as part of updating the mod_mbox indexes.
> For example, the script could extract just the ^From_ lines into a separate
> file and store that alongside the .mbox file. Mailglomper would read the much
> abbreviated file instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] clr-apache commented on pull request #82: Update newcommitter.md
clr-apache commented on PR #82: URL: https://github.com/apache/comdev-site/pull/82#issuecomment-1428926714 @sebbASF The Committer Accept is no longer needed because the information it used to contain was moved. Information about getting account privileges was moved to the Committer Invite Template. Information about how-it-works and other general topics was moved to Committer Done Template. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-293) scandist does not detect releases renamed from dist/dev
[
https://issues.apache.org/jira/browse/COMDEV-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688213#comment-17688213
]
Andrew Musselman commented on COMDEV-293:
-
[~sebb] I agree.
In `scandist.py` there is an example commit from pubsub that looks like this:
# e.g. {"committer": "sebb", "log": "Ensure we exit on control+C",
"repository": "13f79535-47bb-0310-9956-ffa450edef68", "format": 1,
# "changed": {"comdev/reporter.apache.org/trunk/scandist.py": {"flags": "U
"}},
# "date": "2015-07-13 13:38:33 + (Mon, 13 Jul 2015)", "type": "svn",
"id": 1690668}
For the test case in the original description, what form would it take in the
pubsub-generated commit?
The regex in `scandist.py` catches the release string as shown below:
{{#!/usr/bin/env python3
import re
path = "release/spark/spark-2.2.2"
RELEASE_MATCH = r"^release/([^/]+)/"
match = re.match(RELEASE_MATCH, path)
print(match[0])
$ ./test-release.py
release/spark/}}
> scandist does not detect releases renamed from dist/dev
> ---
>
> Key: COMDEV-293
> URL: https://issues.apache.org/jira/browse/COMDEV-293
> Project: Community Development
> Issue Type: Bug
> Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> The scandist script ignores commits which only affect a directory.
> This is OK for simple directory creation, but means that releases which are
> created by renaming/copying from dist/dev are ignored.
> For example the following did not cause an email to be sent:
> $ svn log -r27902 -v https://dist.apache.org/repos/dist/
>
> r27902 | tgraves | 2018-07-03 19:08:54 +0100 (Tue, 03 Jul 2018) | 2 lines
> Changed paths:
>D /dev/spark/v2.2.2-rc2-bin
>A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901)
> Publish spark 2.2.2
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-216) Fixup styles so header/footer appear properly
[ https://issues.apache.org/jira/browse/COMDEV-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688214#comment-17688214 ] Andrew Musselman commented on COMDEV-216: - [~curcuru] is this still relevant? > Fixup styles so header/footer appear properly > - > > Key: COMDEV-216 > URL: https://issues.apache.org/jira/browse/COMDEV-216 > Project: Community Development > Issue Type: Wish > Components: Reporter Tool >Reporter: Shane Curcuru >Priority: Minor > > I spent a while trying to get the footer text - which now points to the new > /about.html page, that explains where the source is - to appear, to no avail. > - Why is the content div row-12? > - Why don't we have three foundation.css rows in the page? Header - which > would be just the static title, and a link to the About page; Contents - same > as now, but without the H2 element - and Footer - which includes license etc > and can get pushed off the page if contents needs to grow. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-206) Add "Any prospects for new committers/pmc members?" line if no changes in last year
[
https://issues.apache.org/jira/browse/COMDEV-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688215#comment-17688215
]
Andrew Musselman commented on COMDEV-206:
-
Not sure this is still relevant but there is already a warning if the last
committer was added over two years ago, see these lines in the newer
`site/js/render.js`:
{{ 471 if (ncn) {
472 if (nc < after.getTime() / 1000) {
473 addLine(pmc, " - Last committer addition was " + ncn +
" at " + new Date(nc * 1000).toDateString())
474 }
475 changes.innerHTML += "→ " + "Last committer
addition: " + new Date(nc * 1000).toDateString() + " (" + ncn + ")"
476 } else {
477 addLine(pmc, " - Last committer addition was more than 2
years ago")
478 changes.innerHTML += "→ " + "Last committer
addition: more than two years ago (not in the
archive!)"
479 }
480 changes.innerHTML += "→ " + "Currently " +
json.count[pmc][1] + " committers and " + json.count[pmc][0] + " PMC members."
481 addLine(pmc)}}
> Add "Any prospects for new committers/pmc members?" line if no changes in
> last year
> ---
>
> Key: COMDEV-206
> URL: https://issues.apache.org/jira/browse/COMDEV-206
> Project: Community Development
> Issue Type: Improvement
> Components: Reporter Tool
>Reporter: Mike Kienenberger
>Priority: Minor
>
> I've likely seen more than a hundred "No new contributers in last year -- any
> prospects?" board report comments posted in the last year. Could we add a
> prompt for this to the reporter template if no new contributors were detected
> in the last year?
> I took a look at the reporter source and got to
> /comdev/reporter.apache.org/trunk/site/render_proposed.js but I'm not much of
> a python / javascript hacker.
> I'd recommend adding it to these sections:
> ## PMC changes:
>
> ## Committer base changes:
> and phrase it like:
> It has been a year since the last [ new committer | PMC member ] was added.
> Any candidates on the horizon?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Comment Edited] (COMDEV-206) Add "Any prospects for new committers/pmc members?" line if no changes in last year
[
https://issues.apache.org/jira/browse/COMDEV-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688215#comment-17688215
]
Andrew Musselman edited comment on COMDEV-206 at 2/14/23 1:03 AM:
--
Not sure this is still relevant but there is already a warning if the last
committer was added over two years ago, see these lines in the newer
`site/js/render.js`:
471 if (ncn) {
472 if (nc < after.getTime() / 1000) {
473 addLine(pmc, " - Last committer addition was " + ncn +
" at " + new Date(nc * 1000).toDateString())
474 }
475 changes.innerHTML += "→ " + "Last committer
addition: " + new Date(nc * 1000).toDateString() + " (" + ncn + ")"
476 } else {
477 addLine(pmc, " - Last committer addition was more than 2
years ago")
478 changes.innerHTML += "→ " + "Last committer
addition: more than two years ago (not in the
archive!)"
479 }
480 changes.innerHTML += "→ " + "Currently " +
json.count[pmc][1] + " committers and " + json.count[pmc][0] + " PMC members."
481 addLine(pmc)
was (Author: akm):
Not sure this is still relevant but there is already a warning if the last
committer was added over two years ago, see these lines in the newer
`site/js/render.js`:
{{ 471 if (ncn) {
472 if (nc < after.getTime() / 1000) {
473 addLine(pmc, " - Last committer addition was " + ncn +
" at " + new Date(nc * 1000).toDateString())
474 }
475 changes.innerHTML += "→ " + "Last committer
addition: " + new Date(nc * 1000).toDateString() + " (" + ncn + ")"
476 } else {
477 addLine(pmc, " - Last committer addition was more than 2
years ago")
478 changes.innerHTML += "→ " + "Last committer
addition: more than two years ago (not in the
archive!)"
479 }
480 changes.innerHTML += "→ " + "Currently " +
json.count[pmc][1] + " committers and " + json.count[pmc][0] + " PMC members."
481 addLine(pmc)}}
> Add "Any prospects for new committers/pmc members?" line if no changes in
> last year
> ---
>
> Key: COMDEV-206
> URL: https://issues.apache.org/jira/browse/COMDEV-206
> Project: Community Development
> Issue Type: Improvement
> Components: Reporter Tool
>Reporter: Mike Kienenberger
>Priority: Minor
>
> I've likely seen more than a hundred "No new contributers in last year -- any
> prospects?" board report comments posted in the last year. Could we add a
> prompt for this to the reporter template if no new contributors were detected
> in the last year?
> I took a look at the reporter source and got to
> /comdev/reporter.apache.org/trunk/site/render_proposed.js but I'm not much of
> a python / javascript hacker.
> I'd recommend adding it to these sections:
> ## PMC changes:
>
> ## Committer base changes:
> and phrase it like:
> It has been a year since the last [ new committer | PMC member ] was added.
> Any candidates on the horizon?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-145) Duplicated data in generated json files
[ https://issues.apache.org/jira/browse/COMDEV-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688216#comment-17688216 ] Andrew Musselman commented on COMDEV-145: - +1 close it > Duplicated data in generated json files > --- > > Key: COMDEV-145 > URL: https://issues.apache.org/jira/browse/COMDEV-145 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > There is some duplication/overlap in the json data files. > For example, chairs.json has full names of both chairs and committee. > committees.json has full name of committee and availid of chair > pmcs.json has similar info to committees.json. > I would have thought one file would be sufficient here. > people_name.json has availid and full name > people.json has availid and full name plus other data > They could surely be combined. > releases.json and releases-files have some overlapping data -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-486) Copyright in footer not updated
Andrew Musselman created COMDEV-486: --- Summary: Copyright in footer not updated Key: COMDEV-486 URL: https://issues.apache.org/jira/browse/COMDEV-486 Project: Community Development Issue Type: Improvement Reporter: Andrew Musselman In reporter.apache.org and other pages the copyright is 2020. Either update to current year or pick up $current_year automatically. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-486) Copyright in footer not updated
[ https://issues.apache.org/jira/browse/COMDEV-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Musselman updated COMDEV-486: Component/s: Website > Copyright in footer not updated > --- > > Key: COMDEV-486 > URL: https://issues.apache.org/jira/browse/COMDEV-486 > Project: Community Development > Issue Type: Improvement > Components: Website >Reporter: Andrew Musselman >Priority: Minor > > In reporter.apache.org and other pages the copyright is 2020. > Either update to current year or pick up $current_year automatically. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-486) Copyright in footer not updated
[ https://issues.apache.org/jira/browse/COMDEV-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Musselman updated COMDEV-486: Component/s: Reporter Tool (was: Website) > Copyright in footer not updated > --- > > Key: COMDEV-486 > URL: https://issues.apache.org/jira/browse/COMDEV-486 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Andrew Musselman >Priority: Minor > > In reporter.apache.org and other pages the copyright is 2020. > Either update to current year or pick up $current_year automatically. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-487) Stats outdated on Project Statistics page
Andrew Musselman created COMDEV-487: --- Summary: Stats outdated on Project Statistics page Key: COMDEV-487 URL: https://issues.apache.org/jira/browse/COMDEV-487 Project: Community Development Issue Type: Improvement Components: Reporter Tool Reporter: Andrew Musselman https://reporter.apache.org/wizard/statistics?mahout Just seeing mismatches from what we see in mailing list archives and other tools. I am not sure if this is just a latency thing and if these will line up in a week or a month. CHI is still "Action required" though on the chi.py page it's upgraded to "unhealthy," mail activity is lagging behind actual, etc. Charts seem to have different figures than the text summaries as well. I heard this was a known set of issues but did not see an open ticket about it. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-485) [GSOC] [SkyWalking] GSOC 2023 Tasks
[ https://issues.apache.org/jira/browse/COMDEV-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688246#comment-17688246 ] Maxim Solodovnik commented on COMDEV-485: - [~yihaochen] I would recommend to create separate JIRAs :) > [GSOC] [SkyWalking] GSOC 2023 Tasks > --- > > Key: COMDEV-485 > URL: https://issues.apache.org/jira/browse/COMDEV-485 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: Yihao Chen >Priority: Major > Labels: SkyWalking, full-time, gsoc2023 > Original Estimate: 350h > Remaining Estimate: 350h > > This is a placeholder for Apache SkyWalking GSOC 2023 ideas, we are currently > brainstorming for projects and will update asap. > There will be at least two projects, one around AIOps algorithms. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
