[jira] [Commented] (COMDEV-485) [GSOC] [SkyWalking] GSOC 2023 Tasks

2023-02-14 Thread Maxim Solodovnik (Jira) 


[ 
https://issues.apache.org/jira/browse/COMDEV-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688793#comment-17688793
 ] 

Maxim Solodovnik commented on COMDEV-485:
-

There is no specific deadline :)
The earlier ideas are created - more chances to get students ;)

> [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

Re: Patch for reporter.a.o

2023-02-14 Thread Andrew Musselman 
Looks good to me. Maybe similar language on this page too?
https://reporter.apache.org/wizard/statistics?lucene

This ticket could be a good link to point the "Patches welcome" to:
COMDEV-487 

On Tue, Feb 14, 2023 at 1:22 PM  wrote:

> I'd like to propose the attached patch to reporter.a.o so that people
> don't keep submitting the same mailing list stats, quarter after
> quarter, a year after that part of the reporter is broken.
>
> Thoughts?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Patch for reporter.a.o

2023-02-14 Thread rbowen 
I'd like to propose the attached patch to reporter.a.o so that people
don't keep submitting the same mailing list stats, quarter after
quarter, a year after that part of the reporter is broken.

Thoughts?
Index: source/generators.js
===
--- source/generators.js(revision 1907541)
+++ source/generators.js(working copy)
@@ -455,7 +455,7 @@
 // Append header IF there is data, otherwise nah.
 if (txt.length > 0) {
   txt = "See full metrics (new tab)".format(project) + txt;
-  txt = "Potentially useful observations on community 
health:" + txt + "";
+  txt = "Please note that this part of the report is broken. Patches 
welcome:" + txt + "";
   txt += "PLEASE DON'T COPY 
THESE METRICS INTO THE REPORT ALONE!While these metrics might offer 
insights into the wellbeing of the project, what the board of directors 
 wants to see is the story behind these 
metrics.Please take some time to explain why these metrics are the way 
they are, and what this means for the project. If you are unsure how to do 
this, please take a look at some of the examples provided above  (click the 
button!).";
 }
 return txt;
Index: wizard.js
===
--- wizard.js   (revision 1907541)
+++ wizard.js   (working copy)
@@ -1669,7 +1669,7 @@
 // Append header IF there is data, otherwise nah.
 if (txt.length > 0) {
   txt = "See full metrics (new tab)".format(project) + txt;
-  txt = "Potentially useful observations on community 
health:" + txt + "";
+  txt = "Please note that this part of the report is broken. Patches 
welcome:" + txt + "";
   txt += "PLEASE DON'T COPY 
THESE METRICS INTO THE REPORT ALONE!While these metrics might offer 
insights into the wellbeing of the project, what the board of directors 
 wants to see is the story behind these 
metrics.Please take some time to explain why these metrics are the way 
they are, and what this means for the project. If you are unsure how to do 
this, please take a look at some of the examples provided above  (click the 
button!).";
 }
 return txt;

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Resolved] (COMDEV-486) Copyright in footer not updated

2023-02-14 Thread Andrew Musselman (Jira) 


 [ 
https://issues.apache.org/jira/browse/COMDEV-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Musselman resolved COMDEV-486.
-
Resolution: Fixed

> 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
> Attachments: COMDEV-486.patch
>
>
> 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] [Commented] (COMDEV-486) Copyright in footer not updated

2023-02-14 Thread Andrew Musselman (Jira) 


[ 
https://issues.apache.org/jira/browse/COMDEV-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688677#comment-17688677
 ] 

Andrew Musselman commented on COMDEV-486:
-

Fixed in 1907662

Sendingsite/about.html
Sendingsite/addrelease.html
Sendingsite/wizard/index.html
Sendingsite/wizard/statistics.html

> 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
> Attachments: COMDEV-486.patch
>
>
> 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

2023-02-14 Thread Andrew Musselman (Jira) 


 [ 
https://issues.apache.org/jira/browse/COMDEV-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Musselman updated COMDEV-486:

Attachment: COMDEV-486.patch

> 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
> Attachments: COMDEV-486.patch
>
>
> 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

[GitHub] [comdev-site] ShaneCurcuru closed pull request #32: Update gsoc.md

2023-02-14 Thread via GitHub 


ShaneCurcuru closed pull request #32: Update gsoc.md
URL: https://github.com/apache/comdev-site/pull/32


-- 
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] ShaneCurcuru commented on pull request #32: Update gsoc.md

2023-02-14 Thread via GitHub 


ShaneCurcuru commented on PR #32:
URL: https://github.com/apache/comdev-site/pull/32#issuecomment-1430146263

   The GSOC page has had multiple updates covering some of these improvements, 
so it's not practical to merge the remaining minor text clarifications here.


-- 
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] ShaneCurcuru closed pull request #52: Update etiquette.md

2023-02-14 Thread via GitHub 


ShaneCurcuru closed pull request #52: Update etiquette.md
URL: https://github.com/apache/comdev-site/pull/52


-- 
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] ShaneCurcuru commented on pull request #52: Update etiquette.md

2023-02-14 Thread via GitHub 


ShaneCurcuru commented on PR #52:
URL: https://github.com/apache/comdev-site/pull/52#issuecomment-1430140476

   Sorry! This page has already had similar and more extensive changes made, so 
closing this PR as no longer relevant.


-- 
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] ShaneCurcuru closed pull request #55: Update 101.md

2023-02-14 Thread via GitHub 


ShaneCurcuru closed pull request #55: Update 101.md
URL: https://github.com/apache/comdev-site/pull/55


-- 
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] ShaneCurcuru commented on pull request #55: Update 101.md

2023-02-14 Thread via GitHub 


ShaneCurcuru commented on PR #55:
URL: https://github.com/apache/comdev-site/pull/55#issuecomment-1430138057

   "mailing list" is indeed the term we use elsewhere in documentation, closing 
this minor tweak.


-- 
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] ShaneCurcuru merged pull request #84: Update etiquette.md

2023-02-14 Thread via GitHub 


ShaneCurcuru merged PR #84:
URL: https://github.com/apache/comdev-site/pull/84


-- 
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] ShaneCurcuru closed pull request #84: Update etiquette.md

2023-02-14 Thread via GitHub 


ShaneCurcuru closed pull request #84: Update etiquette.md
URL: https://github.com/apache/comdev-site/pull/84


-- 
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] ShaneCurcuru commented on pull request #84: Update etiquette.md

2023-02-14 Thread via GitHub 


ShaneCurcuru commented on PR #84:
URL: https://github.com/apache/comdev-site/pull/84#issuecomment-1430133891

   Thanks for getting started on cleaning up and "welcoming-ness" to our docs!


-- 
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] [Closed] (COMDEV-145) Duplicated data in generated json files

2023-02-14 Thread Shane Curcuru (Jira) 


 [ 
https://issues.apache.org/jira/browse/COMDEV-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane Curcuru closed COMDEV-145.

Resolution: Implemented

json tooling has improved a lot since then.

> 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] [Commented] (COMDEV-485) [GSOC] [SkyWalking] GSOC 2023 Tasks

2023-02-14 Thread Yihao Chen (Jira) 


[ 
https://issues.apache.org/jira/browse/COMDEV-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688617#comment-17688617
 ] 

Yihao Chen commented on COMDEV-485:
---

[~solomax] Thank you! Btw, is there a specific deadline for the ideas? 

> [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

[jira] [Closed] (COMDEV-216) Fixup styles so header/footer appear properly

2023-02-14 Thread Shane Curcuru (Jira) 


 [ 
https://issues.apache.org/jira/browse/COMDEV-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane Curcuru closed COMDEV-216.

Resolution: Cannot Reproduce

> 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-216) Fixup styles so header/footer appear properly

2023-02-14 Thread Shane Curcuru (Jira) 


[ 
https://issues.apache.org/jira/browse/COMDEV-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688616#comment-17688616
 ] 

Shane Curcuru commented on COMDEV-216:
--

Works for me fine now!

> 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-291) Prefetch all data/JIRA/*.json files

2023-02-14 Thread Sebb (Jira) 


[ 
https://issues.apache.org/jira/browse/COMDEV-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688569#comment-17688569
 ] 

Sebb commented on COMDEV-291:
-

I think so.
Daniel Gruno should know for sure, as he is responsible for the move to using 
Kibble etc.

> 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

2023-02-14 Thread Sebb (Jira) 


[ 
https://issues.apache.org/jira/browse/COMDEV-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688561#comment-17688561
 ] 

Sebb commented on COMDEV-295:
-

Mailglomper crontab entry has been dropped.

> 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