[jira] [Commented] (COMDEV-546) project.apache.org uses google charts
[ https://issues.apache.org/jira/browse/COMDEV-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852713#comment-17852713 ] Sebb commented on COMDEV-546: - Digital Processing Agreement or similar > project.apache.org uses google charts > - > > Key: COMDEV-546 > URL: https://issues.apache.org/jira/browse/COMDEV-546 > Project: Community Development > Issue Type: Bug >Reporter: Sebb >Priority: Major > > p.a.o references Google charts. We don't (and won't) have a DPA with them. > The terms of Google charts do not allow for local hosting, so either prior > permission must be sought from the user, or the charting code must be > replaced. -- 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-546) project.apache.org uses google charts
Sebb created COMDEV-546: --- Summary: project.apache.org uses google charts Key: COMDEV-546 URL: https://issues.apache.org/jira/browse/COMDEV-546 Project: Community Development Issue Type: Bug Reporter: Sebb p.a.o references Google charts. We don't (and won't) have a DPA with them. The terms of Google charts do not allow for local hosting, so either prior permission must be sought from the user, or the charting code must be replaced. -- 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-545) Reporter should self-host the files from FontAwsome
Sebb created COMDEV-545: --- Summary: Reporter should self-host the files from FontAwsome Key: COMDEV-545 URL: https://issues.apache.org/jira/browse/COMDEV-545 Project: Community Development Issue Type: Bug Components: Reporter Tool Reporter: Sebb The code current downloads fonts from FontAwsome. We don't (and won't) have a DPA with them, so this is not allowed. The fonts need to be hosted locally. -- 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-544) Improve comdev website navigation to GSoC mentor resources
[
https://issues.apache.org/jira/browse/COMDEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838688#comment-17838688
]
Sebb commented on COMDEV-544:
-
Note that there is a Mentor link under GSoC menu item on most pages
> Improve comdev website navigation to GSoC mentor resources
> --
>
> Key: COMDEV-544
> URL: https://issues.apache.org/jira/browse/COMDEV-544
> Project: Community Development
> Issue Type: Task
> Components: Website
>Reporter: Lewis John McGibbney
>Priority: Minor
>
> h1. Purpose
> Improve comdev website navigation to Google Summer of Code (GSoC) mentor
> resources.
> h1. Context
> Having been ‘away’ for a few years, this year I decided to make an attempt to
> re-engage with the GSoC program.
> I quickly realized that I was totally out of touch having absolutely no idea
> where the mentor community conversations were happening (they happen on
> ment...@community.apache.org) and being hopelessly unable to locate GSoC
> mentoring documentation via the comdev website.
> Thankfully [~sanyam] [pointed me at the
> documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
> and I was able to get back up to speed. Thank you Sanyam :)
> h1. Challenges
> Looking at [https://community.apache.org/gsoc/], as of writing, although
> loads of content exists for students (which is great) no navigation exists to
> mentor resources.
> In my case, this meant that I couldn’t find and entirely missed the excellent
> content available at [https://community.apache.org/mentoring]/.
> h1. Proposal
> I think that a “{*}Mentors: read this{*}” Section should be added to
> [https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
> content from above.
--
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-539) chi report disagrees with mail stats
Sebb created COMDEV-539: --- Summary: chi report disagrees with mail stats Key: COMDEV-539 URL: https://issues.apache.org/jira/browse/COMDEV-539 Project: Community Development Issue Type: Bug Components: Reporter Tool Reporter: Sebb The chi analysis disagrees with the mailing list stats for several projects. e.g. chi score explanation says "No email sent to ANY ML in the past quarter" but the mailing list trends show that there were emails in the last quarter. This occurs for several projects. -- 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-531) Unable to submit report via reporter.a.org
[ https://issues.apache.org/jira/browse/COMDEV-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-531. - Resolution: Fixed > Unable to submit report via reporter.a.org > -- > > Key: COMDEV-531 > URL: https://issues.apache.org/jira/browse/COMDEV-531 > Project: Community Development > Issue Type: Bug >Reporter: Philipp Ottlinger >Priority: Major > > When I tried to file the Creadur report I was able to properly edit the > report, but when hitting "Publish via Whimsy" all I get is: > "Something went wrong, and we couldn't publish your report. > Please check with the Whimsy tool to see if there is already a report posted!" > Not sure what else to add ... thus so unspecific. -- 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-538) PMC information outdated at https://projects.apache.org/committee.html?maven
[ https://issues.apache.org/jira/browse/COMDEV-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776778#comment-17776778 ] Sebb edited comment on COMDEV-538 at 10/18/23 4:43 PM: --- Thanks for confirming it has been fixed. Interesting re the server behaviour. This could explain the unexpected caching of data by the browser. In the case of Safari, it serves much of the content from cache. This includes the JSON data that is displayed. Need to look into how to tell Safari to expire content. was (Author: s...@apache.org): Thanks for confirming it has been fixed. Interesting re the server behaviour. This could explain the unexpected caching of data by the browser. > PMC information outdated at https://projects.apache.org/committee.html?maven > > > Key: COMDEV-538 > URL: https://issues.apache.org/jira/browse/COMDEV-538 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Konrad Windszus >Priority: Major > > The PMC information is outdated in > https://projects.apache.org/committee.html?maven. > The official roster shows me (kwin) correctly as being PMC member: > https://whimsy.apache.org/roster/committee/maven > How often is the page in projects.a.o regenerated? -- 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-538) PMC information outdated at https://projects.apache.org/committee.html?maven
[ https://issues.apache.org/jira/browse/COMDEV-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776778#comment-17776778 ] Sebb commented on COMDEV-538: - Thanks for confirming it has been fixed. Interesting re the server behaviour. This could explain the unexpected caching of data by the browser. > PMC information outdated at https://projects.apache.org/committee.html?maven > > > Key: COMDEV-538 > URL: https://issues.apache.org/jira/browse/COMDEV-538 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Konrad Windszus >Priority: Major > > The PMC information is outdated in > https://projects.apache.org/committee.html?maven. > The official roster shows me (kwin) correctly as being PMC member: > https://whimsy.apache.org/roster/committee/maven > How often is the page in projects.a.o regenerated? -- 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-538) PMC information outdated at https://projects.apache.org/committee.html?maven
[ https://issues.apache.org/jira/browse/COMDEV-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-538. - Resolution: Fixed > PMC information outdated at https://projects.apache.org/committee.html?maven > > > Key: COMDEV-538 > URL: https://issues.apache.org/jira/browse/COMDEV-538 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Konrad Windszus >Priority: Major > > The PMC information is outdated in > https://projects.apache.org/committee.html?maven. > The official roster shows me (kwin) correctly as being PMC member: > https://whimsy.apache.org/roster/committee/maven > How often is the page in projects.a.o regenerated? -- 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-538) PMC information outdated at https://projects.apache.org/committee.html?maven
[ https://issues.apache.org/jira/browse/COMDEV-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776547#comment-17776547 ] Sebb commented on COMDEV-538: - Looks OK to me. Make sure you refresh your browser cache (or try a different browser). If using Safari, try Command+Option+E, then Command+R. > PMC information outdated at https://projects.apache.org/committee.html?maven > > > Key: COMDEV-538 > URL: https://issues.apache.org/jira/browse/COMDEV-538 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Konrad Windszus >Priority: Major > > The PMC information is outdated in > https://projects.apache.org/committee.html?maven. > The official roster shows me (kwin) correctly as being PMC member: > https://whimsy.apache.org/roster/committee/maven > How often is the page in projects.a.o regenerated? -- 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-538) PMC information outdated at https://projects.apache.org/committee.html?maven
[ https://issues.apache.org/jira/browse/COMDEV-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775942#comment-17775942 ] Sebb commented on COMDEV-538: - There was a bug in the code that fetched the data; now fixed. > PMC information outdated at https://projects.apache.org/committee.html?maven > > > Key: COMDEV-538 > URL: https://issues.apache.org/jira/browse/COMDEV-538 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Konrad Windszus >Priority: Major > > The PMC information is outdated in > https://projects.apache.org/committee.html?maven. > The official roster shows me (kwin) correctly as being PMC member: > https://whimsy.apache.org/roster/committee/maven > How often is the page in projects.a.o regenerated? -- 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-538) PMC information outdated at https://projects.apache.org/committee.html?maven
[ https://issues.apache.org/jira/browse/COMDEV-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-538. - Resolution: Information Provided > PMC information outdated at https://projects.apache.org/committee.html?maven > > > Key: COMDEV-538 > URL: https://issues.apache.org/jira/browse/COMDEV-538 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Konrad Windszus >Priority: Major > > The PMC information is outdated in > https://projects.apache.org/committee.html?maven. > The official roster shows me (kwin) correctly as being PMC member: > https://whimsy.apache.org/roster/committee/maven > How often is the page in projects.a.o regenerated? -- 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-538) PMC information outdated at https://projects.apache.org/committee.html?maven
[ https://issues.apache.org/jira/browse/COMDEV-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775826#comment-17775826 ] Sebb commented on COMDEV-538: - The jobs are run daily overnight > PMC information outdated at https://projects.apache.org/committee.html?maven > > > Key: COMDEV-538 > URL: https://issues.apache.org/jira/browse/COMDEV-538 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Konrad Windszus >Priority: Major > > The PMC information is outdated in > https://projects.apache.org/committee.html?maven. > The official roster shows me (kwin) correctly as being PMC member: > https://whimsy.apache.org/roster/committee/maven > How often is the page in projects.a.o regenerated? -- 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-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-436.
-
Resolution: Fixed
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
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-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765117#comment-17765117
]
Sebb commented on COMDEV-436:
-
DOAP files are not provided for all projects, and even if present, may not be
maintained.
Also I think the releases page is intended to include only current releases.
DOAP release entries don't have any indication of currency (and projects may
maintain several version streams, so numeric ordering does not help)
Note that there is already a collection of all the DOAP contents in
https://projects.apache.org/json/foundation/projects.json
This includes the releases section from the original DOAP.
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
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-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764752#comment-17764752
]
Sebb commented on COMDEV-436:
-
Please don't stop uploading items to the download area merely to fix a problem
with the release parsing! Maybe the charts don't belong there, but that is a
separate issue.
Whilst it is not ideal for the release listing to contain lots of spurious
files, IMO it is better to include a few extras rather than omit valid releases.
It's easy enough to filter out additional directories if required.
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
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-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764700#comment-17764700
]
Sebb commented on COMDEV-436:
-
The parser now runs off the find-ls listing which makes it very much quicker.
Also the matching of releases has been much simplified.
Several false positives and negatives have been addressed.
Hopefully the SOLR releases now look OK?
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
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-536) Reporter Tool should filter out stats for bots
[ https://issues.apache.org/jira/browse/COMDEV-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764418#comment-17764418 ] Sebb commented on COMDEV-536: - I agree it does not make sense to lump bot traffic with the rest. However, that does not appear to be something that can be solved by changes to the Reporter code. AFAICT the statistics come from Kibble, so changes will have to be addressed there. > Reporter Tool should filter out stats for bots > -- > > Key: COMDEV-536 > URL: https://issues.apache.org/jira/browse/COMDEV-536 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Brian Demers >Priority: Major > > Apache Shiro Recently migrated to GitHub. It would be useful to see the > project statistics excluding bot traffic, to better gauge community traffic. > For example, this quarter 103 Pull Requests were opened in `apache/shiro`, > only 23 of them were from a human. > > *NOTE:* Bot traffic IS still useful, for example if Pull Requests opened by > > a bot are not merged, or are sitting open for a long period of time, that > > may signal something to the PMC (or maybe the bot isn't useful). > Example GitHub issues/PR filter: > ``` > created:>2023-06-15 -author:app/dependabot > ``` -- 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-536) Reporter Tool should filter out stats for bots
[ https://issues.apache.org/jira/browse/COMDEV-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764382#comment-17764382 ] Sebb commented on COMDEV-536: - Which part of the reporter tool are you referring to? e.g. URL > Reporter Tool should filter out stats for bots > -- > > Key: COMDEV-536 > URL: https://issues.apache.org/jira/browse/COMDEV-536 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Brian Demers >Priority: Major > > Apache Shiro Recently migrated to GitHub. It would be useful to see the > project statistics excluding bot traffic, to better gauge community traffic. > For example, this quarter 103 Pull Requests were opened in `apache/shiro`, > only 23 of them were from a human. > > *NOTE:* Bot traffic IS still useful, for example if Pull Requests opened by > > a bot are not merged, or are sitting open for a long period of time, that > > may signal something to the PMC (or maybe the bot isn't useful). > Example GitHub issues/PR filter: > ``` > created:>2023-06-15 -author:app/dependabot > ``` -- 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-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763353#comment-17763353
]
Sebb commented on COMDEV-436:
-
In the meantime I have applied the patch.
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
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-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763352#comment-17763352
]
Sebb commented on COMDEV-436:
-
A release must contain a source package.
There are only a few extensions that are used for these, so I think the search
could be considerably simplified.
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
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-535) parsereleases.py should not always strip -parent- from names
Sebb created COMDEV-535: --- Summary: parsereleases.py should not always strip -parent- from names Key: COMDEV-535 URL: https://issues.apache.org/jira/browse/COMDEV-535 Project: Community Development Issue Type: Bug Components: Reporter Tool Reporter: Sebb parsereleases.py currently replaces -parent- with '-' when classifying releases. This is not always appropriate. For example: netbeans/netbeans/19/netbeans-19-source.zip becomes netbeans-19, which is fine, but netbeans/netbeans-parent/netbeans-parent-4/netbeans-parent-4-source-release.zip becomes netbeans-4, which is not Similarly for Commons and Maven. -- 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-302) add committe short description to committees listing
[ https://issues.apache.org/jira/browse/COMDEV-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-302. - Resolution: Fixed Fixed in r1912197 > add committe short description to committees listing > > > Key: COMDEV-302 > URL: https://issues.apache.org/jira/browse/COMDEV-302 > Project: Community Development > Issue Type: Wish > Components: Projects Tool >Reporter: Herve Boutemy >Priority: Major > > Committees by name show a list with the name only: > https://projects.apache.org/committees.html > adding the short description would help people find info, and would also > improve the rendering (the page is quite empty with this list on the left...) -- 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-302) add committe short description to committees listing
[ https://issues.apache.org/jira/browse/COMDEV-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762911#comment-17762911 ] Sebb commented on COMDEV-302: - Note that search works quite well to find projects > add committe short description to committees listing > > > Key: COMDEV-302 > URL: https://issues.apache.org/jira/browse/COMDEV-302 > Project: Community Development > Issue Type: Wish > Components: Projects Tool >Reporter: Herve Boutemy >Priority: Major > > Committees by name show a list with the name only: > https://projects.apache.org/committees.html > adding the short description would help people find info, and would also > improve the rendering (the page is quite empty with this list on the left...) -- 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-528) Retired projects in DOAP list
[ https://issues.apache.org/jira/browse/COMDEV-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-528. - Resolution: Fixed These projects are now shown as being in the Attic > Retired projects in DOAP list > - > > Key: COMDEV-528 > URL: https://issues.apache.org/jira/browse/COMDEV-528 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Claude Warren >Priority: Minor > > The DOAP file list [1] as listed the DOAP for Hivemind [2] which is a > retired project and the specified file has an error in it. I believe that it > should be commented out as other retired projects have been. > [1] > [https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml] > [2] > [http://svn.apache.org/repos/asf/hivemind/hivemind2/trunk/doap_Hivemind.rdf] > -- 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-328) Don't publish second-hand json files
[ https://issues.apache.org/jira/browse/COMDEV-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-328. - Resolution: Fixed > Don't publish second-hand json files > > > Key: COMDEV-328 > URL: https://issues.apache.org/jira/browse/COMDEV-328 > Project: Community Development > Issue Type: Improvement > Components: PhoneBook >Reporter: Sebb >Priority: Major > > Originally, home.a.o extracted its own data files which it published in > https://home.apache.org/public/ > However, the files there are now just copies of the ones created by Whimsy. > It would be better to direct users to the originals. > e.g. with a redirect? -- 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-534) 3rd party downloads not allowed by privacy policy
[ https://issues.apache.org/jira/browse/COMDEV-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761854#comment-17761854 ] Sebb commented on COMDEV-534: - The statistics page loads data from api.snoot.io. AFAICT, we don't have a privacy agreement with them, and their website privacy policy [1] says they may collect PII, and furthermore that the Policy can be changed at any time without notice. Furthermore, the link to the vendor's website is broken. [1] https://snoot.io/privacy.html > 3rd party downloads not allowed by privacy policy > - > > Key: COMDEV-534 > URL: https://issues.apache.org/jira/browse/COMDEV-534 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Sebb >Priority: Major > > The projects.a.o website relies on Google charts. > AFAIK, we don't have a privacy agreement for these, and according to the > terms of use, they cannot be used downloaded and used locally: > https://developers.google.com/chart/interactive/faq#offline > Some possible solutions: > - use an alternative charting library that is not in conflict with the > Privacy Policy > - ask the user's permission before making requests to such 3rd party sites; > if the user refuses, charts and graphs cannot be displayed, but the site > should otherwise continue to function > - find some way of proxying the requests via an ASF host that strips out all > client-specific headers. -- 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-534) 3rd party downloads not allowed by privacy policy
Sebb created COMDEV-534: --- Summary: 3rd party downloads not allowed by privacy policy Key: COMDEV-534 URL: https://issues.apache.org/jira/browse/COMDEV-534 Project: Community Development Issue Type: Bug Components: Projects Tool Reporter: Sebb The projects.a.o website relies on Google charts. AFAIK, we don't have a privacy agreement for these, and according to the terms of use, they cannot be used downloaded and used locally: https://developers.google.com/chart/interactive/faq#offline Some possible solutions: - use an alternative charting library that is not in conflict with the Privacy Policy - ask the user's permission before making requests to such 3rd party sites; if the user refuses, charts and graphs cannot be displayed, but the site should otherwise continue to function - find some way of proxying the requests via an ASF host that strips out all client-specific headers. -- 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-533) Inconsistency in membership data (CouchDB)
[ https://issues.apache.org/jira/browse/COMDEV-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759633#comment-17759633 ] Sebb commented on COMDEV-533: - The official date of joining is when the person is added to the roster. Sorry, but that cannot be changed, it is a fact of history. > Inconsistency in membership data (CouchDB) > -- > > Key: COMDEV-533 > URL: https://issues.apache.org/jira/browse/COMDEV-533 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Páli Gábor >Priority: Major > > When the quarterly report body is generated via > [https://reporter.apache.org/wizard/?couchdb] for the CouchDB project, the > "Membership Data" section contains information that is not exactly correct. > The latest PMC member was not Glynn Bird but Ronny Berndt and it was > announced on 2023-03-04 on the dev@ mailing list: > [https://lists.apache.org/list?d...@couchdb.apache.org:2023-3] . Glynn Bird > has joined the PMC on 2020-09-14: > [https://lists.apache.org/list?d...@couchdb.apache.org:2020-9] . -- 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-533) Inconsistency in membership data (CouchDB)
[ https://issues.apache.org/jira/browse/COMDEV-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759361#comment-17759361 ] Sebb commented on COMDEV-533: - Only PMC members are allowed to modify the file. This is normally done via the Whimsy PMC roster page, as that ensures the correct syntax is used and adjusts any related LDAP groups. A summary of the contents of the CI file can also be found here: https://whimsy.apache.org/public/committee-info.json Although Glynn Bird was voted to be invited to join the PMC in Sep 2020, it looks as though the PMC forgot to update the roster until March 2023. > Inconsistency in membership data (CouchDB) > -- > > Key: COMDEV-533 > URL: https://issues.apache.org/jira/browse/COMDEV-533 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Páli Gábor >Priority: Major > > When the quarterly report body is generated via > [https://reporter.apache.org/wizard/?couchdb] for the CouchDB project, the > "Membership Data" section contains information that is not exactly correct. > The latest PMC member was not Glynn Bird but Ronny Berndt and it was > announced on 2023-03-04 on the dev@ mailing list: > [https://lists.apache.org/list?d...@couchdb.apache.org:2023-3] . Glynn Bird > has joined the PMC on 2020-09-14: > [https://lists.apache.org/list?d...@couchdb.apache.org:2020-9] . -- 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-533) Inconsistency in membership data (CouchDB)
[ https://issues.apache.org/jira/browse/COMDEV-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-533. - Resolution: Information Provided > Inconsistency in membership data (CouchDB) > -- > > Key: COMDEV-533 > URL: https://issues.apache.org/jira/browse/COMDEV-533 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Páli Gábor >Priority: Major > > When the quarterly report body is generated via > [https://reporter.apache.org/wizard/?couchdb] for the CouchDB project, the > "Membership Data" section contains information that is not exactly correct. > The latest PMC member was not Glynn Bird but Ronny Berndt and it was > announced on 2023-03-04 on the dev@ mailing list: > [https://lists.apache.org/list?d...@couchdb.apache.org:2023-3] . Glynn Bird > has joined the PMC on 2020-09-14: > [https://lists.apache.org/list?d...@couchdb.apache.org:2020-9] . -- 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-533) Inconsistency in membership data (CouchDB)
[ https://issues.apache.org/jira/browse/COMDEV-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759341#comment-17759341 ] Sebb commented on COMDEV-533: - The official membership roster is the committee-info.txt file. Unless and until a person is added to the file, they are not officially a member of the PMC. The dates from committee-inf.txt can be seen in the Whimsy page for CouchDB: [https://whimsy.apache.org/roster/committee/couchdb] This shows: Glynn Bird 2023-03-14 Ronny Berndt 2023-03-03 > Inconsistency in membership data (CouchDB) > -- > > Key: COMDEV-533 > URL: https://issues.apache.org/jira/browse/COMDEV-533 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Páli Gábor >Priority: Major > > When the quarterly report body is generated via > [https://reporter.apache.org/wizard/?couchdb] for the CouchDB project, the > "Membership Data" section contains information that is not exactly correct. > The latest PMC member was not Glynn Bird but Ronny Berndt and it was > announced on 2023-03-04 on the dev@ mailing list: > [https://lists.apache.org/list?d...@couchdb.apache.org:2023-3] . Glynn Bird > has joined the PMC on 2020-09-14: > [https://lists.apache.org/list?d...@couchdb.apache.org:2020-9] . -- 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-532) Report Wizard gives "[object Response]" error with underlying 500
[ https://issues.apache.org/jira/browse/COMDEV-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-532. - Resolution: Fixed Works again. > Report Wizard gives "[object Response]" error with underlying 500 > - > > Key: COMDEV-532 > URL: https://issues.apache.org/jira/browse/COMDEV-532 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool > Environment: macOS Ventura 13.4.1 (c), Firefox 116.0.3 (64-bit) >Reporter: Páli Gábor >Priority: Major > > As reported by others, navigating to > [https://reporter.apache.org/wizard/?couchdb|https://reporter.apache.org/wizard/?couchdb] > pops up a blank notification error, and does nothing else. > Console shows an underlying 500: > /*** ASF Board Report Wizard initializing / > [wizard.js:1799:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Initializing escrow checks > [wizard.js:1825:17|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Fetching JSON resource at /api/overview?couchdb > [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > putting /api/overview?couchdb in escrow... > [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > URL /api/overview?couchdb returned HTTP code 500, snapping! > [wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > It might be related that I am not on the CouchDB PMC, but I believe it should > still respond sensibly. -- 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-532) Report Wizard gives "[object Response]" error with underlying 500
[ https://issues.apache.org/jira/browse/COMDEV-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated COMDEV-532: Description: As reported by others, navigating to [https://reporter.apache.org/wizard/?couchdb|https://reporter.apache.org/wizard/?couchdb] pops up a blank notification error, and does nothing else. Console shows an underlying 500: /*** ASF Board Report Wizard initializing / [wizard.js:1799:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] Initializing escrow checks [wizard.js:1825:17|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] Fetching JSON resource at /api/overview?couchdb [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] putting /api/overview?couchdb in escrow... [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] URL /api/overview?couchdb returned HTTP code 500, snapping! [wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] It might be related that I am not on the CouchDB PMC, but I believe it should still respond sensibly. was: As reported by others, navigating to [https://reporter.apache.org/wizard/?couchdb|https://reporter.apache.org/wizard/] pops up a blank notification error, and does nothing else. Console shows an underlying 500: /*** ASF Board Report Wizard initializing / [wizard.js:1799:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] Initializing escrow checks [wizard.js:1825:17|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] Fetching JSON resource at /api/overview?couchdb [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] putting /api/overview?couchdb in escrow... [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] URL /api/overview?couchdb returned HTTP code 500, snapping! [wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] It might be related that I am not on the CouchDB PMC, but I believe it should still respond sensibly. > Report Wizard gives "[object Response]" error with underlying 500 > - > > Key: COMDEV-532 > URL: https://issues.apache.org/jira/browse/COMDEV-532 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool > Environment: macOS Ventura 13.4.1 (c), Firefox 116.0.3 (64-bit) >Reporter: Páli Gábor >Priority: Major > > As reported by others, navigating to > [https://reporter.apache.org/wizard/?couchdb|https://reporter.apache.org/wizard/?couchdb] > pops up a blank notification error, and does nothing else. > Console shows an underlying 500: > /*** ASF Board Report Wizard initializing / > [wizard.js:1799:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Initializing escrow checks > [wizard.js:1825:17|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Fetching JSON resource at /api/overview?couchdb > [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > putting /api/overview?couchdb in escrow... > [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > URL /api/overview?couchdb returned HTTP code 500, snapping! > [wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > It might be related that I am not on the CouchDB PMC, but I believe it should > still respond sensibly. -- 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-532) Report Wizard gives "[object Response]" error with underlying 500
[ https://issues.apache.org/jira/browse/COMDEV-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759299#comment-17759299 ] Sebb commented on COMDEV-532: - Sorry, I'd not noticed that clicking on the link in the description did not include the query part of the URL. However, I have just tried the full URL: https://reporter.apache.org/wizard/?couchdb and that works fine for me even even with a relatively unprivileged login. > Report Wizard gives "[object Response]" error with underlying 500 > - > > Key: COMDEV-532 > URL: https://issues.apache.org/jira/browse/COMDEV-532 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool > Environment: macOS Ventura 13.4.1 (c), Firefox 116.0.3 (64-bit) >Reporter: Páli Gábor >Priority: Major > > As reported by others, navigating to > [https://reporter.apache.org/wizard/?couchdb|https://reporter.apache.org/wizard/] > pops up a blank notification error, and does nothing else. > Console shows an underlying 500: > /*** ASF Board Report Wizard initializing / > [wizard.js:1799:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Initializing escrow checks > [wizard.js:1825:17|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Fetching JSON resource at /api/overview?couchdb > [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > putting /api/overview?couchdb in escrow... > [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > URL /api/overview?couchdb returned HTTP code 500, snapping! > [wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > It might be related that I am not on the CouchDB PMC, but I believe it should > still respond sensibly. -- 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-532) Report Wizard gives "[object Response]" error with underlying 500
[ https://issues.apache.org/jira/browse/COMDEV-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759295#comment-17759295 ] Sebb commented on COMDEV-532: - Tried just now, and the wizard loads OK for me with macOS and FF, Chrome and Safari. > Report Wizard gives "[object Response]" error with underlying 500 > - > > Key: COMDEV-532 > URL: https://issues.apache.org/jira/browse/COMDEV-532 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool > Environment: macOS Ventura 13.4.1 (c), Firefox 116.0.3 (64-bit) >Reporter: Páli Gábor >Priority: Major > > As reported by others, navigating to [https://reporter.apache.org/wizard/] > pops up a blank notification error, and does nothing else. > Console shows an underlying 500: > /*** ASF Board Report Wizard initializing / > [wizard.js:1799:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Initializing escrow checks > [wizard.js:1825:17|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > Fetching JSON resource at /api/overview?couchdb > [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > putting /api/overview?couchdb in escrow... > [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] > URL /api/overview?couchdb returned HTTP code 500, 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-531) Unable to submit report via reporter.a.org
[ https://issues.apache.org/jira/browse/COMDEV-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751625#comment-17751625 ] Sebb commented on COMDEV-531: - Once the agenda file contains an invalid UTF-8 character, it looks like all subsequent updates by Whimsy will fail. As to the lack of error info shown by Reporter, that is what this issue is about. If Reporter gets an error from Whimsy when submitting an update, the app needs to show sufficient info to the user to be able to investigate further. This may possibly involve changes to the Reporter-Whimsy interface, but I think the starting point needs to be at the Reporter end - hence this issue. > Unable to submit report via reporter.a.org > -- > > Key: COMDEV-531 > URL: https://issues.apache.org/jira/browse/COMDEV-531 > Project: Community Development > Issue Type: Bug >Reporter: Philipp Ottlinger >Priority: Major > > When I tried to file the Creadur report I was able to properly edit the > report, but when hitting "Publish via Whimsy" all I get is: > "Something went wrong, and we couldn't publish your report. > Please check with the Whimsy tool to see if there is already a report posted!" > Not sure what else to add ... thus so unspecific. -- 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-531) Unable to submit report via reporter.a.org
[ https://issues.apache.org/jira/browse/COMDEV-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751343#comment-17751343 ] Sebb commented on COMDEV-531: - This is probably related to WHIMSY-404, however the lack of info shown by Reporter makes it hard to know. > Unable to submit report via reporter.a.org > -- > > Key: COMDEV-531 > URL: https://issues.apache.org/jira/browse/COMDEV-531 > Project: Community Development > Issue Type: Bug >Reporter: Philipp Ottlinger >Priority: Major > > When I tried to file the Creadur report I was able to properly edit the > report, but when hitting "Publish via Whimsy" all I get is: > "Something went wrong, and we couldn't publish your report. > Please check with the Whimsy tool to see if there is already a report posted!" > Not sure what else to add ... thus so unspecific. -- 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] [Moved] (COMDEV-531) Unable to submit report via reporter.a.org
[ https://issues.apache.org/jira/browse/COMDEV-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb moved WHIMSY-403 to COMDEV-531: Key: COMDEV-531 (was: WHIMSY-403) Workflow: classic default workflow (was: jira) difficulty-level: Easy Project: Community Development (was: Whimsy) > Unable to submit report via reporter.a.org > -- > > Key: COMDEV-531 > URL: https://issues.apache.org/jira/browse/COMDEV-531 > Project: Community Development > Issue Type: Bug >Reporter: Philipp Ottlinger >Priority: Major > > When I tried to file the Creadur report I was able to properly edit the > report, but when hitting "Publish via Whimsy" all I get is: > "Something went wrong, and we couldn't publish your report. > Please check with the Whimsy tool to see if there is already a report posted!" > Not sure what else to add ... thus so unspecific. -- 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-528) Retired projects in DOAP list
[ https://issues.apache.org/jira/browse/COMDEV-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723180#comment-17723180 ] Sebb commented on COMDEV-528: - An alternative is to create an override DOAP in the following directory: https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects-override/ But one or the other needs to be done. > Retired projects in DOAP list > - > > Key: COMDEV-528 > URL: https://issues.apache.org/jira/browse/COMDEV-528 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Claude Warren >Priority: Minor > > The DOAP file list [1] as listed the DOAP for Hivemind [2] which is a > retired project and the specified file has an error in it. I believe that it > should be commented out as other retired projects have been. > [1] > [https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml] > [2] > [http://svn.apache.org/repos/asf/hivemind/hivemind2/trunk/doap_Hivemind.rdf] > -- 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-437) Committer map loads with Google Maps error
[ https://issues.apache.org/jira/browse/COMDEV-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709461#comment-17709461 ] Sebb commented on COMDEV-437: - I think the source is here: https://svn.apache.org/repos/asf/comdev/nearby_people/ AFAICT, the website is served from the same box as projects.a.o and reporter.a.o The definition for which is in the private infrastructure-p6 repo. > Committer map loads with Google Maps error > -- > > Key: COMDEV-437 > URL: https://issues.apache.org/jira/browse/COMDEV-437 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Benjamin Marwell >Priority: Major > > The web page [https://community.zones.apache.org/map.html] loads with errors. > The error shown redirects to > [https://developers.google.com/maps/documentation/javascript/error-messages?utm_source=maps_js_medium=degraded_campaign=billing#api-key-and-billing-errors] > > Maybe it should be converted to using OpenStreetMap.org. -- 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-384) Tasks in the help page seems to have not been updated for a long time
[ https://issues.apache.org/jira/browse/COMDEV-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17702189#comment-17702189 ] Sebb commented on COMDEV-384: - There was an issue with searching the database, now resolved. > Tasks in the help page seems to have not been updated for a long time > - > > Key: COMDEV-384 > URL: https://issues.apache.org/jira/browse/COMDEV-384 > Project: Community Development > Issue Type: Improvement > Components: Help Wanted >Reporter: ningtao >Priority: Major > > https://helpwanted.apache.org/ > First, chose “Programming and Development”, pick “Java language”, then > “Found 26 items you might be interested in”, but these tasks looks too old, > 25 task is created at 2017, one task created at 2019. And some of these tasks > are already in “closed” status. > I guess there are a lots of Java project need help in Apache, just not > include by Help Wanted. -- 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-384) Tasks in the help page seems to have not been updated for a long time
[ https://issues.apache.org/jira/browse/COMDEV-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-384. - Resolution: Fixed There are no longer any outdated tasks -- there are now no tasks at all > Tasks in the help page seems to have not been updated for a long time > - > > Key: COMDEV-384 > URL: https://issues.apache.org/jira/browse/COMDEV-384 > Project: Community Development > Issue Type: Improvement > Components: Help Wanted >Reporter: ningtao >Priority: Major > > https://helpwanted.apache.org/ > First, chose “Programming and Development”, pick “Java language”, then > “Found 26 items you might be interested in”, but these tasks looks too old, > 25 task is created at 2017, one task created at 2019. And some of these tasks > are already in “closed” status. > I guess there are a lots of Java project need help in Apache, just not > include by Help Wanted. -- 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-499) Detect cron job failures
Sebb created COMDEV-499: --- Summary: Detect cron job failures Key: COMDEV-499 URL: https://issues.apache.org/jira/browse/COMDEV-499 Project: Community Development Issue Type: Bug Components: Projects Tool Reporter: Sebb The parseprojects script started failing a few days ago, but there don't seem to have been any notifications of this. Need to find a way to detect failures. For example, the UI could report if any of the data files are older than expected. -- 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=17689626#comment-17689626 ] Sebb commented on COMDEV-227: - Seems to me that the problem here is that the form is not designed for PMCs that have multiple products. Limiting the number of releases shown may mean that the product being added is not shown in the list, in which case it might as well not be shown at all. > 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 > Attachments: COMDEV-227.patch.txt > > > 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-291) Prefetch all data/JIRA/*.json files
[ 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
[ 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
[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=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-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=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
[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=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-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=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] [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-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=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-479) Report Wizard gives "[object Response]" error
[ https://issues.apache.org/jira/browse/COMDEV-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600479#comment-17600479 ] Sebb commented on COMDEV-479: - FTR, reports are sent to board@ and the private@ list > Report Wizard gives "[object Response]" error > -- > > Key: COMDEV-479 > URL: https://issues.apache.org/jira/browse/COMDEV-479 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Xiangdong Huang >Assignee: Daniel Gruno >Priority: Major > Attachments: image-2022-09-05-23-29-36-764.png > > > behavior: > !image-2022-09-05-23-29-36-764.png|width=394,height=202! > It seems some others also occur the same problem: > https://issues.apache.org/jira/browse/INFRA-23659 > Can this be fixed quickly? If not, I'd like to know how to submit report in > other way (I remember that we can send email to submit report, but I forget > where to find the guide to get the email list address). > Thanks. -- 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-477) Apache SpamAssassin mailing list
[ https://issues.apache.org/jira/browse/COMDEV-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17581301#comment-17581301 ] Sebb commented on COMDEV-477: - Whimsy provides this information. I think reporter.a.o may also. > Apache SpamAssassin mailing list > - > > Key: COMDEV-477 > URL: https://issues.apache.org/jira/browse/COMDEV-477 > Project: Community Development > Issue Type: Question >Reporter: Giovanni Bechis >Priority: Trivial > > To be able to give the idea of how wide our community is on various events, I > would like to know how many subscribers Apache SpamAssassin mailing lists has. -- 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-466) json files contain references to git-wip-us.apache.org
Sebb created COMDEV-466: --- Summary: json files contain references to git-wip-us.apache.org Key: COMDEV-466 URL: https://issues.apache.org/jira/browse/COMDEV-466 Project: Community Development Issue Type: Bug Components: Projects Tool Reporter: Sebb The host git-wip-us.apache.org is no longer recognised, which means all URLs that reference it are broken. It currently appears in the following files: site/json/projects/commons-beanutils.json site/json/projects/reef.json site/json/projects/incubator-datafu.json site/json/projects/commons-math.json site/json/projects/phoenix.json site/json/projects/crunch.json site/json/projects/attic-stratos.json site/json/projects/tapestry.json site/json/projects/lucene-solr.json site/json/projects/helix.json site/json/projects/metamodel.json site/json/projects/jclouds.json site/json/projects/trafodion.json site/json/projects/attic-mrunit.json site/json/projects/oodt.json site/json/projects/attic-lucy.json site/json/projects/servicemix.json site/json/projects/logging-log4j_2.json site/json/projects/incubator-taverna.json site/json/projects/commons-scxml.json site/json/projects/parquet.json site/json/projects/attic-vxquery.json site/json/projects/lucene-core.json site/json/projects/ambari.json site/json/projects/deltaspike.json site/json/projects/attic-falcon.json site/json/projects/cassandra.json site/json/projects/cloudstack.json site/json/projects/clerezza.json site/json/projects/commons-lang.json site/json/projects/guacamole.json site/json/projects/bookkeeper.json site/json/projects/incubator-edgent.json site/json/projects/flex.json site/json/projects/storm.json site/json/projects/flume.json site/json/projects/brooklyn.json site/json/projects/bigtop.json site/json/projects/trafficserver-traffic_server.json site/json/projects/sqoop.json site/json/projects/vcl.json site/json/projects/attic-deltacloud.json site/json/projects/logging-log4net.json site/json/projects/any23.json site/json/projects/climate-open_workbench.json site/json/projects/zeppelin.json site/json/projects/attic-polygene.json site/json/projects/syncope.json site/json/projects/lens.json site/json/foundation/projects.json data/projects-override/crunch.rdf data/projects-override/ambari.rdf data/projects-override/falcon.rdf data/projects-override/climate.rdf data/projects-override/lens.rdf data/projects-override/sqoop.rdf data/projects-override/trafodion.rdf data/projects-override/vxquery.rdf -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-432) home.apache.org phonebook: Could not find unix group: 'trafficcontrol'
[ https://issues.apache.org/jira/browse/COMDEV-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454296#comment-17454296 ] Sebb commented on COMDEV-432: - Sorry, I don't have time to test this or apply the patch, but it looks as thought it might work. I suggest you apply the patch and see if it works; if not revert and try again. > home.apache.org phonebook: Could not find unix group: 'trafficcontrol' > -- > > Key: COMDEV-432 > URL: https://issues.apache.org/jira/browse/COMDEV-432 > Project: Community Development > Issue Type: Task > Components: PhoneBook >Reporter: Zach Hoffman >Priority: Major > > Steps to reproduce: > 1. Go to [https://home.apache.org/committer-index.html] > 2. Click on one of the `trafficcontrol` links > 3. Arrive at [https://home.apache.org/phonebook.html?unix=trafficcontrol] > 4. See message: Could not find unix group: 'trafficcontrol' -- This message was sent by Atlassian Jira (v8.20.1#820001) - 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=17436741#comment-17436741 ] Sebb commented on COMDEV-429: - For the source code, read the About page, linked from every 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 > > 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.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Deleted] (COMDEV-419) Python Training in Pune
[ https://issues.apache.org/jira/browse/COMDEV-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb deleted COMDEV-419: > Python Training in Pune > --- > > Key: COMDEV-419 > URL: https://issues.apache.org/jira/browse/COMDEV-419 > Project: Community Development > Issue Type: Story >Reporter: Snehal Harshe >Priority: Minor > Labels: newbie > > It is very difficult to choose to go for which course. After completing > studies or while learning through the programming language which course you > should go for. There are different programming languages to learn so there > can be confusion, whether to go. But we would like to suggest you go > according to recent trends in the market so that what will happen is more > opportunities will be available and you can easily enhance your career too. > In the event that you wish to upgrade your scholastic learning in the field > of Python, at that point taking [Python Training in > Pune|https://www.sevenmentor.com/best-python-classes-in-pune.php] would be > the best decision ever. In spite of the fact that there are numerous Python > Training Institutes in Pune*,* there is something novel and exceptional about > SevenMentor. It grants preparing by showing hypothetical ideas also as > offering hands-on understanding. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Deleted] (COMDEV-420) Japanese Language Classes in Pune
[ https://issues.apache.org/jira/browse/COMDEV-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb deleted COMDEV-420: > Japanese Language Classes in Pune > - > > Key: COMDEV-420 > URL: https://issues.apache.org/jira/browse/COMDEV-420 > Project: Community Development > Issue Type: Story >Reporter: Snehal Harshe >Priority: Minor > > [Japanese Language Training in > Pune|https://www.sevenmentor.com/japanese-classes-in-pune.php] at SevenMentor > institute provides exhaustive courses in the Japanese language with faculty. > Any individual who wants to develop command over Japanese to pursue a career > can avail of these courses. These classes are all well equipped to train a > person for all 5 levels of the JLPT. [Japanese Language Course in > Pune|https://www.sevenmentor.com/japanese-classes-in-pune.php] at SevenMentor > is one among the well-renowned institutes and gives a vast assortment of > classes in Indian as well as foreign languages at its Pune campus.Japan is > among the fastest-growing markets in the world and it prominently features, > among the top 5 economies in the world. This is due to the manufacturing > capacities of the country and the technological prowess. Japan is also one of > the top sources of Foreign Direct Investment (FDI) in several growing markets > across the globe including India. Most of the top Japanese MNCs (notably in > Electronics and auto sectors) have a presence in India through joint ventures > or local subsidiaries in the nation. Popularity, growth and sustained > existence of Japanese brands have made learning Japanese terminology a common > phenomenon across the country. There is a demand for employees as well as. > This tendency has prompted many universities and language training institutes > to offer diplomas and degrees in Western Language. ** Japanese Language > Classes in Pune helps you in fluency in Japanese language speech can’t just > assist an individual in procuring a career opportunity as a translator with > business or embassies but also in something as creative as writing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Deleted] (COMDEV-417) Artificial Intelligence Classes in Pune
[ https://issues.apache.org/jira/browse/COMDEV-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb deleted COMDEV-417: > Artificial Intelligence Classes in Pune > --- > > Key: COMDEV-417 > URL: https://issues.apache.org/jira/browse/COMDEV-417 > Project: Community Development > Issue Type: Bug >Reporter: Lovekesh Jayant >Priority: Major > > Demand of professionals with AI Technology is growing exponentially and thus > SevenMentor is providing practical based Artificial intelligence courses in > Pune, India. Universities have also decided to include AI courses in the > academic syllabus of all Computer Science fields. > Artificial Intelligence Classes in Pune > [https://www.sevenmentor.com/artificial-intelligence-training-courses-in-pune.php|http://example.com] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Deleted] (COMDEV-418) The Best IT training provider
[ https://issues.apache.org/jira/browse/COMDEV-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb deleted COMDEV-418: > The Best IT training provider > - > > Key: COMDEV-418 > URL: https://issues.apache.org/jira/browse/COMDEV-418 > Project: Community Development > Issue Type: Story >Reporter: surbhi nahta >Priority: Major > > [*The Best IT training provider* |https://www.sevenmentor.com/]takes pride in > having instructors who are engrossed beyond Fifteen Years in enjoying as a > trainer for Various Verticles of Educationon. With that, they offer the > foremost Classroom And Online training As per trade standard. And assert as > one of the fastest-growing network training institutions in the world and has > a monopoly in the region. The Institute’s strong placement cell has magnified > its network amidst corporates over the years and is leveraged to realize > nearly 100% placements of its students. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-245) statistics.html does not describe what the data means
[ https://issues.apache.org/jira/browse/COMDEV-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated COMDEV-245: Description: statistics.html [1] looks very nice, but there is no info on where the data is sourced. For example: - language breakdown - is that derived from DOAP files or some other measure? - codebase lines of code - what is the codebase? does it include Git and SVN, and if code migrated does it include both repos? Does it include branches/tags? - repositories - does that include github and gitbox? what about SVN repos? The ASF uses a shared SVN source repo, is that broken down by project? What about the dist repo? - Mirror download activity : how is that measured? [1]https://projects.apache.org/statistics.html was: statistics.html looks very nice, but there is no info on where the data is sourced. For example: - language breakdown - is that derived from DOAP files or some other measure? - codebase lines of code - what is the codebase? does it include Git and SVN, and if code migrated does it include both repos? Does it include branches/tags? - repositories - does that include github and gitbox? what about SVN repos? The ASF uses a shared SVN source repo, is that broken down by project? What about the dist repo? - Mirror download activity : how is that measured? > statistics.html does not describe what the data means > - > > Key: COMDEV-245 > URL: https://issues.apache.org/jira/browse/COMDEV-245 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Sebb >Priority: Minor > > statistics.html [1] looks very nice, but there is no info on where the data > is sourced. > For example: > - language breakdown - is that derived from DOAP files or some other measure? > - codebase lines of code - what is the codebase? does it include Git and > SVN, and if code migrated does it include both repos? Does it include > branches/tags? > - repositories - does that include github and gitbox? what about SVN repos? > The ASF uses a shared SVN source repo, is that broken down by project? What > about the dist repo? > - Mirror download activity : how is that measured? > [1]https://projects.apache.org/statistics.html -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-245) statistics.html does not describe what the data means
[ https://issues.apache.org/jira/browse/COMDEV-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated COMDEV-245: Component/s: (was: Reporter Tool) Projects Tool > statistics.html does not describe what the data means > - > > Key: COMDEV-245 > URL: https://issues.apache.org/jira/browse/COMDEV-245 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Sebb >Priority: Minor > > statistics.html looks very nice, but there is no info on where the data is > sourced. > For example: > - language breakdown - is that derived from DOAP files or some other measure? > - codebase lines of code - what is the codebase? does it include Git and SVN, > and if code migrated does it include both repos? Does it include > branches/tags? > - repositories - does that include github and gitbox? what about SVN repos? > The ASF uses a shared SVN source repo, is that broken down by project? What > about the dist repo? > - Mirror download activity : how is that measured? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-400) Drop project keys files
[ https://issues.apache.org/jira/browse/COMDEV-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-400. - Resolution: Fixed Files have been dropped > Drop project keys files > --- > > Key: COMDEV-400 > URL: https://issues.apache.org/jira/browse/COMDEV-400 > Project: Community Development > Issue Type: Bug > Components: Comdev, PhoneBook, Website > Environment: https://people.apache.org/keys/group/ >Reporter: Sebb >Priority: Major > > The project keys files should be dropped. > On the face of it the project keys files could be useful, however that is not > the case in practise. This is because: > * not all release signers are members of the project group > * release signing keys need to be kept even after a project goes to the attic > or the signer leaves the pmc group. > Leaving the project keys files around has may result it inappropriate usage > (as it has previously). > [Note that the individual keys are still available.] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-400) Drop project keys files
[ https://issues.apache.org/jira/browse/COMDEV-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17286416#comment-17286416 ] Sebb commented on COMDEV-400: - > Do those individual keys remain available for ASF accounts that are disabled > or removed later? Not as far as I know > Once someone has signed a release I think their keys should remain available > for ever. Agreed, which is one reason why the project keys files are not useful. > Drop project keys files > --- > > Key: COMDEV-400 > URL: https://issues.apache.org/jira/browse/COMDEV-400 > Project: Community Development > Issue Type: Bug > Components: Comdev, PhoneBook, Website > Environment: https://people.apache.org/keys/group/ >Reporter: Sebb >Priority: Major > > The project keys files should be dropped. > On the face of it the project keys files could be useful, however that is not > the case in practise. This is because: > * not all release signers are members of the project group > * release signing keys need to be kept even after a project goes to the attic > or the signer leaves the pmc group. > Leaving the project keys files around has may result it inappropriate usage > (as it has previously). > [Note that the individual keys are still available.] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-400) Drop project keys files
Sebb created COMDEV-400: --- Summary: Drop project keys files Key: COMDEV-400 URL: https://issues.apache.org/jira/browse/COMDEV-400 Project: Community Development Issue Type: Bug Components: Comdev, PhoneBook, Website Environment: https://people.apache.org/keys/group/ Reporter: Sebb The project keys files should be dropped. On the face of it the project keys files could be useful, however that is not the case in practise. This is because: * not all release signers are members of the project group * release signing keys need to be kept even after a project goes to the attic or the signer leaves the pmc group. Leaving the project keys files around has may result it inappropriate usage (as it has previously). [Note that the individual keys are still available.] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-340) Surprising categories on "Projects by category" page
[ https://issues.apache.org/jira/browse/COMDEV-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239941#comment-17239941 ] Sebb commented on COMDEV-340: - https://issues.apache.org/jira/browse/KAFKA-10775 > Surprising categories on "Projects by category" page > > > Key: COMDEV-340 > URL: https://issues.apache.org/jira/browse/COMDEV-340 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Piotr Zygielo >Priority: Minor > Attachments: apache-categories.png > > > Page https://projects.apache.org/projects.html?category lists Kafka and > Commons-RNG under surprising categories: > "https://projects.apache.org/projects.html?category#big-data; > and > "https://projects.apache.org/projects.html?category#library; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-366) also generate project statistics for reporter.a.o
[ https://issues.apache.org/jira/browse/COMDEV-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-366. - Resolution: Information Provided > also generate project statistics for reporter.a.o > - > > Key: COMDEV-366 > URL: https://issues.apache.org/jira/browse/COMDEV-366 > Project: Community Development > Issue Type: Task > Components: Reporter Tool >Reporter: Mark Struberg >Priority: Major > > The old reporter.a.o site used to also generate the project statistics about > project members, releases, mailing list stats and issue tracker stats. This > feature got lost on the new site. There is now an extra page for those stats > which means the information is still accessible. > Some board members demanded those stats on one of my last report. It would be > great to have them back on the generated report template. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-282) Monitor http://{tlp}.apache.org/doap.rdf for releases
[
https://issues.apache.org/jira/browse/COMDEV-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-282.
-
Resolution: Won't Do
> Monitor http://{tlp}.apache.org/doap.rdf for releases
> -
>
> Key: COMDEV-282
> URL: https://issues.apache.org/jira/browse/COMDEV-282
> Project: Community Development
> Issue Type: Wish
> Components: Reporter Tool
>Reporter: William A. Rowe, Jr.
>Priority: Major
>
> Many projects, including apr.apache.org and httpd.apache.org, report their
> canonical release data as a doap resource, e.g.;
> [http://httpd.apache.org/doap.rdf]
> It would be helpful for the Reporter Tool to periodically scrape these
> resources and automatically populate the release tracking table.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-340) Surprising categories on "Projects by category" page
[ https://issues.apache.org/jira/browse/COMDEV-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-340. - Resolution: Information Provided This needs to be fixed by the Kafka project > Surprising categories on "Projects by category" page > > > Key: COMDEV-340 > URL: https://issues.apache.org/jira/browse/COMDEV-340 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Piotr Zygielo >Priority: Minor > Attachments: apache-categories.png > > > Page https://projects.apache.org/projects.html?category lists Kafka and > Commons-RNG under surprising categories: > "https://projects.apache.org/projects.html?category#big-data; > and > "https://projects.apache.org/projects.html?category#library; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-322) incubator-netbeans on Project Statistics page
[ https://issues.apache.org/jira/browse/COMDEV-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-322. - Resolution: Fixed Seems to have been fixed > incubator-netbeans on Project Statistics page > - > > Key: COMDEV-322 > URL: https://issues.apache.org/jira/browse/COMDEV-322 > Project: Community Development > Issue Type: Bug > Components: Projects Tool, Snoot Statistics >Reporter: Geertjan Wielenga >Priority: Major > > At https://projects.apache.org/statistics.html, I see 'incubator-netbeans' in > 'Repositories by Lines of Code' and in 'Language Treemap', which should now > be 'netbeans'. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-363) مجموعةمنصةشليله
[ https://issues.apache.org/jira/browse/COMDEV-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-363. - Resolution: Invalid > مجموعةمنصةشليله > --- > > Key: COMDEV-363 > URL: https://issues.apache.org/jira/browse/COMDEV-363 > Project: Community Development > Issue Type: Bug > Components: Comdev, GSoC/Mentoring ideas, Help Wanted, Nearby > People, PhoneBook, Projects Tool, Reporter Tool, Snoot Statistics, Website > Environment: Android web etc. >Reporter: منصة شليله >Priority: Major > Labels: منصةشليله > Attachments: Screenshot_20200322-083758_Chrome.jpg, منصة شليله.pdf, > نشاطي في Play - Google Play > > Original Estimate: 612h > Remaining Estimate: 612h > > h1. منصةشليله > !Screenshot_20200322-083758_Chrome.jpg! > > منصةشليله [link title|http://example.com]https://youtu.be/51QuAfUebsE[^منصة > شليله.pdf] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-364) منصة شليله
[ https://issues.apache.org/jira/browse/COMDEV-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-364. - Resolution: Invalid > منصة شليله > -- > > Key: COMDEV-364 > URL: https://issues.apache.org/jira/browse/COMDEV-364 > Project: Community Development > Issue Type: Bug > Components: Comdev, GSoC/Mentoring ideas, Help Wanted, Nearby > People, PhoneBook, Projects Tool, Reporter Tool, Snoot Statistics, Website > Environment: Android web etc. >Reporter: منصة شليله >Priority: Major > Labels: منصةشليله > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-334) localhost.crt does not exist or is empty
[
https://issues.apache.org/jira/browse/COMDEV-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-334.
-
Resolution: Invalid
Sorry, but we cannot help with questions about letsencrypt.
The software is not produced nor supported by the Apache Software Foundation.
Please visit the letsencrypt website for information on getting support.
> localhost.crt does not exist or is empty
>
>
> Key: COMDEV-334
> URL: https://issues.apache.org/jira/browse/COMDEV-334
> Project: Community Development
> Issue Type: IT Help
> Components: Help Wanted
> Environment: CentOS Linux release 8.0.1905 (Core) Minimal install.
>Reporter: Michael Miller
>Priority: Blocker
>
> I am setting up Certbot for my web and mail server and after starting the
> installation of Certbot I got the following:
>
> [root@mail ~]# /usr/local/bin/certbot-auto certonly --apache
>
> Saving debug log to /var/log/letsencrypt/letsencrypt.log
>
> Error while running apachectl configtest.
>
>
>
> AH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.conf:
>
> SSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not exist or
> is empty
>
>
> Could not choose appropriate plugin: The apache plugin is not working; there
> may be problems with your existing configuration.
> The error was: MisconfigurationError("Error while running apachectl
> configtest.\n\nAH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.con
> f:\nSSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not
> exist or is empty\n",)
> The apache plugin is not working; there may be problems with your existing
> configuration.
> The error was: MisconfigurationError("Error while running apachectl
> configtest.\n\nAH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.con
> f:\nSSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not
> exist or is empty\n",)
>
> Here is what I have in my /var/log/letsencrypt/letsencrypt.log:
> AH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.conf:
> SSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not exist or
> is empty
>
> 2019-10-13 00:16:26,264:DEBUG:certbot.plugins.selection:Single candidate
> plugin: * apache
> Description: Apache Web Server plugin
> Interfaces: IAuthenticator, IInstaller, IPlugin
> Entry point: apache = certbot_apache.entrypoint:ENTRYPOINT
> Initialized: 0x7f7549fdbdd8>
> Prep: Error while running apachectl configtest.
>
> AH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.conf:
> SSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not exist or
> is empty
>
> 2019-10-13 00:16:26,264:DEBUG:certbot.plugins.selection:Selected
> authenticator None and installer None
> 2019-10-13 00:16:26,265:INFO:certbot.main:Could not choose appropriate
> plugin: The apache plugin is not working; there may be problems with your
> existing configuration.
> The error was: MisconfigurationError("Error while running apachectl
> configtest.\n\nAH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.con
> f:\nSSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not
> exist or is empty\n",)
> 2019-10-13 00:16:26,266:DEBUG:certbot.log:Exiting abnormally:
> Traceback (most recent call last):
> File "/opt/eff.org/certbot/venv/bin/letsencrypt", line 11, in
> load_entry_point('letsencrypt==0.7.0', 'console_scripts', 'letsencrypt')()
> File
> "/opt/eff.org/certbot/venv/lib64/python3.6/site-packages/certbot/main.py",
> line 1378, in main
> return config.func(config, plugins)
> File
> "/opt/eff.org/certbot/venv/lib64/python3.6/site-packages/certbot/main.py",
> line 1244, in certonly
> installer, auth = plug_sel.choose_configurator_plugins(config, plugins,
> "certonly")
> File
> "/opt/eff.org/certbot/venv/lib64/python3.6/site-packages/certbot/plugins/selection.py",
> line 235, in choose_configurator_plugins
> diagnose_configurator_problem("authenticator", req_auth, plugins)
>
[jira] [Closed] (COMDEV-379) منصة شليله
[ https://issues.apache.org/jira/browse/COMDEV-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed COMDEV-379. --- > منصة شليله > -- > > Key: COMDEV-379 > URL: https://issues.apache.org/jira/browse/COMDEV-379 > Project: Community Development > Issue Type: Project > Components: GSoC/Mentoring ideas, Website >Reporter: منصة شليله >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-370) CLONE - localhost.crt does not exist or is empty
[
https://issues.apache.org/jira/browse/COMDEV-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-370.
-
Resolution: Invalid
Sorry, but we cannot help with questions about letsencrypt.
The software is not produced nor supported by the Apache Software Foundation.
Please visit the letsencrypt website for information on getting support.
> CLONE - localhost.crt does not exist or is empty
>
>
> Key: COMDEV-370
> URL: https://issues.apache.org/jira/browse/COMDEV-370
> Project: Community Development
> Issue Type: IT Help
> Components: Help Wanted
> Environment: CentOS Linux release 8.0.1905 (Core) Minimal install.
>Reporter: منصة شليله
>Priority: Blocker
>
> I am setting up Certbot for my web and mail server and after starting the
> installation of Certbot I got the following:
>
> [root@mail ~]# /usr/local/bin/certbot-auto certonly --apache
>
> Saving debug log to /var/log/letsencrypt/letsencrypt.log
>
> Error while running apachectl configtest.
>
>
>
> AH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.conf:
>
> SSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not exist or
> is empty
>
>
> Could not choose appropriate plugin: The apache plugin is not working; there
> may be problems with your existing configuration.
> The error was: MisconfigurationError("Error while running apachectl
> configtest.\n\nAH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.con
> f:\nSSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not
> exist or is empty\n",)
> The apache plugin is not working; there may be problems with your existing
> configuration.
> The error was: MisconfigurationError("Error while running apachectl
> configtest.\n\nAH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.con
> f:\nSSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not
> exist or is empty\n",)
>
> Here is what I have in my /var/log/letsencrypt/letsencrypt.log:
> AH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.conf:
> SSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not exist or
> is empty
>
> 2019-10-13 00:16:26,264:DEBUG:certbot.plugins.selection:Single candidate
> plugin: * apache
> Description: Apache Web Server plugin
> Interfaces: IAuthenticator, IInstaller, IPlugin
> Entry point: apache = certbot_apache.entrypoint:ENTRYPOINT
> Initialized: 0x7f7549fdbdd8>
> Prep: Error while running apachectl configtest.
>
> AH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.conf:
> SSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not exist or
> is empty
>
> 2019-10-13 00:16:26,264:DEBUG:certbot.plugins.selection:Selected
> authenticator None and installer None
> 2019-10-13 00:16:26,265:INFO:certbot.main:Could not choose appropriate
> plugin: The apache plugin is not working; there may be problems with your
> existing configuration.
> The error was: MisconfigurationError("Error while running apachectl
> configtest.\n\nAH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.con
> f:\nSSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not
> exist or is empty\n",)
> 2019-10-13 00:16:26,266:DEBUG:certbot.log:Exiting abnormally:
> Traceback (most recent call last):
> File "/opt/eff.org/certbot/venv/bin/letsencrypt", line 11, in
> load_entry_point('letsencrypt==0.7.0', 'console_scripts', 'letsencrypt')()
> File
> "/opt/eff.org/certbot/venv/lib64/python3.6/site-packages/certbot/main.py",
> line 1378, in main
> return config.func(config, plugins)
> File
> "/opt/eff.org/certbot/venv/lib64/python3.6/site-packages/certbot/main.py",
> line 1244, in certonly
> installer, auth = plug_sel.choose_configurator_plugins(config, plugins,
> "certonly")
> File
> "/opt/eff.org/certbot/venv/lib64/python3.6/site-packages/certbot/plugins/selection.py",
> line 235, in choose_configurator_plugins
> diagnose_configurator_problem("authenticator", req_auth,
[jira] [Resolved] (COMDEV-379) منصة شليله
[ https://issues.apache.org/jira/browse/COMDEV-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-379. - Resolution: Incomplete > منصة شليله > -- > > Key: COMDEV-379 > URL: https://issues.apache.org/jira/browse/COMDEV-379 > Project: Community Development > Issue Type: Project > Components: GSoC/Mentoring ideas, Website >Reporter: منصة شليله >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-381) gunicorn failing on projects-vm3
Sebb created COMDEV-381: --- Summary: gunicorn failing on projects-vm3 Key: COMDEV-381 URL: https://issues.apache.org/jira/browse/COMDEV-381 Project: Community Development Issue Type: Bug Reporter: Sebb Since the move to vm3, gunicorn has not been running properly. I have fixed the restarting error, which was due to gunicorn not being on the path for the cron job. Gunicorn now starts, but fails almost immediately with: urllib.error.URLError: This is invoked from: File "/var/www/reporter.apache.org/scripts/pdata.py", line 92, in charters = loadJson(DESCRIPTIONS) File "/var/www/reporter.apache.org/scripts/pdata.py", line 84, in loadJson resp = uc.get(url, name=None, encoding='utf-8', errors=None) However I have been unable to determine why the request is failing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-377) Http crashes observed during fuzzing testing
[ https://issues.apache.org/jira/browse/COMDEV-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-377. - Resolution: Information Provided COMDEV is not responsible for Apache httpd. Please contact the HTTPD project: https://httpd.apache.org/ and https://httpd.apache.org/support.html https://httpd.apache.org/bug_report.html > Http crashes observed during fuzzing testing > > > Key: COMDEV-377 > URL: https://issues.apache.org/jira/browse/COMDEV-377 > Project: Community Development > Issue Type: Bug >Reporter: mark >Priority: Major > Attachments: coredumps.zip > > > Hi, > http crashes was observed during the fuzzing testing. The http version is > Apache/2.4.41 (Unix). See logs attached. Please check it what is the cause of > this problem. > Note: Fuzzing testing is to send malformed packets targets to the service > to verify the http service robustness under this situation. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-375) repositories.json data source not updated since 2016
Sebb created COMDEV-375: --- Summary: repositories.json data source not updated since 2016 Key: COMDEV-375 URL: https://issues.apache.org/jira/browse/COMDEV-375 Project: Community Development Issue Type: Bug Reporter: Sebb The file https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/site/json/foundation/repositories.json has not been updated since 2016. I cannot find any details of how the file was created. Either the file needs to be maintained regularly, or it should be dropped. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Assigned] (COMDEV-375) repositories.json data source not updated since 2016
[ https://issues.apache.org/jira/browse/COMDEV-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reassigned COMDEV-375: --- Assignee: Herve Boutemy > repositories.json data source not updated since 2016 > > > Key: COMDEV-375 > URL: https://issues.apache.org/jira/browse/COMDEV-375 > Project: Community Development > Issue Type: Bug >Reporter: Sebb >Assignee: Herve Boutemy >Priority: Major > > The file > https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/site/json/foundation/repositories.json > has not been updated since 2016. > I cannot find any details of how the file was created. > Either the file needs to be maintained regularly, or it should be dropped. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-373) Projects doesn't find Daffodil DOAP file
[ https://issues.apache.org/jira/browse/COMDEV-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-373. - Resolution: Fixed The DOAP is now being shown again > Projects doesn't find Daffodil DOAP file > - > > Key: COMDEV-373 > URL: https://issues.apache.org/jira/browse/COMDEV-373 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Steve Lawrence >Priority: Major > > The [Apache Daffodil > project|https://projects.apache.org/project.html?incubator-daffodil] page > says that Daffodil does not have a DOAP file available and so doesn't provide > a lot of information that our DOAP file includes. > But the DOAP file is listed as > [https://daffodil.incubator.apache.org/doap.rdf] in the > [projects.xml|https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml] > file and can be accessed. However, it looks like no json file is generated > in [https://projects.apache.org/json/projects/] > I also noticed there's nearly 300 projects listed in projects.xml, but just > under 200 json files. Maybe this isn't specific to Daffodil and about 100 > projects are missing? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-373) Projects doesn't find Daffodil DOAP file
[ https://issues.apache.org/jira/browse/COMDEV-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125065#comment-17125065 ] Sebb commented on COMDEV-373: - There have been issues with SSL certificate processing that have affected the Python code on that host. Some temporary fixes have been applied, but the data may not be fully refreshed for a day or so. > Projects doesn't find Daffodil DOAP file > - > > Key: COMDEV-373 > URL: https://issues.apache.org/jira/browse/COMDEV-373 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Steve Lawrence >Priority: Major > > The [Apache Daffodil > project|https://projects.apache.org/project.html?incubator-daffodil] page > says that Daffodil does not have a DOAP file available and so doesn't provide > a lot of information that our DOAP file includes. > But the DOAP file is listed as > [https://daffodil.incubator.apache.org/doap.rdf] in the > [projects.xml|https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml] > file and can be accessed. However, it looks like no json file is generated > in [https://projects.apache.org/json/projects/] > I also noticed there's nearly 300 projects listed in projects.xml, but just > under 200 json files. Maybe this isn't specific to Daffodil and about 100 > projects are missing? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-371) Apache httpd Module: How to retain original POST "response body" when using SetHandler?
[
https://issues.apache.org/jira/browse/COMDEV-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb closed COMDEV-371.
---
Resolution: Information Provided
Sorry, but this is not the appropriate forum for such a question.
The HTTPD server is maintained by the HTTPD project.
Please subscribe to the HTTPD user list and post the query there:
https://httpd.apache.org/lists.html
> Apache httpd Module: How to retain original POST "response body" when using
> SetHandler?
> ---
>
> Key: COMDEV-371
> URL: https://issues.apache.org/jira/browse/COMDEV-371
> Project: Community Development
> Issue Type: Question
> Components: Comdev, Help Wanted
> Environment: DEV
>Reporter: Harshil Fadia
>Priority: Major
> Labels: Apache, Proxy, apache, c, module
>
> *QUESTION*: How can I trigger my C code and set variable in response header
> *BUT still retain original Response body which server is generating for
> client.*
> *Requirement*: Write custom Apache module to read POST request body >> Take
> out data from request body >> Set particular response header attribute using
> request body >> Send response back to client
> *Details*: I am using Apache as proxy for my ElasticSearch. I have
> successfully developed Apache Module in C and added it to httpd.conf. I have
> used "*SetHandler*" directive to trigger my custom C code.
> It is all working fine. Request generated from client browser is going
> through my custom C Apache Module and in my C code, I am able to read POST
> request body from request_rec. I am also able to set response header with
> that value I am readying from request body.
> *Issue*: If I invoke my module/code using SetHandler, when it comes out it
> does not have any response body and blank response body is sent to client
> browser. Where as when I disable my module/code, response is well generated a
> sent to client. So looks like by using SetHandler, *response is lost*.
>
> My config/code are below:
> h1. 1. httpd.conf
> {code:java}
> LoadModule example_module/usr/lib64/httpd/modules/mycustommodule.so
>
>
> #SetHandler readbody-handler #calling my custom module
>
> #My KIBANA application is running on 5601 on same machine
> ProxyPass/ http://localhost:5601/
> ProxyPassReverse / http://localhost:5601/
>
> {code}
> h1. 2. My custom C module
> {code:java}
> module AP_MODULE_DECLARE_DATA readbody_module = {
> STANDARD20_MODULE_STUFF,
> NULL, /*Per-directory configuration handler */
> NULL, /*Merge handler for per-directory configurations */
> NULL, /*Per-server configuration handler */
> NULL, /*Merge handler for per-server configurations */
> NULL,
> regiter_hooks /*Our hook registering function */
> };
> static void register_hooks(apr_pool_t *pool)
> {
> ap_hook_handler(readbody_handler, NULL, NULL, -10);
> }
> static int readbody_handler(request_rec *r)
> {
> const char *buffer;
> if (!r->handler || strcmp(r->handler, "readbody-handler")) return
> (DECLINED);
> if (util_read(r, ) == OK) //reading the body and assigning it into
> buffer
> {
> char s[2] = ":";
> char s2[2] = "\"";
> char *indexname;
> indexname = strtok(buffer, s);
> indexname = strtok(NULL, s);
> indexname = strtok(indexname, s2);
> indexname = strtok(NULL, s2);
> apr_table_setn(r->headers_out, "IndexPattern", indexname); //setting
> up response header
> }
> return OK;
> }
> static int util_read(request_rec *r, const char **rbuf)
> {
> int rc;
> if ((rc = ap_setup_client_block(r, REQUEST_CHUNKED_ERROR)) != OK)
> {
> return rc;
> }
> if (ap_should_client_block(r))
> {
> char argsbuffer[HUGE_STRING_LEN];
> int rsize, len_read, rpos = 0;
> long length = r->remaining;
> *rbuf = apr_pcalloc(r->pool, length + 1);
> while ((len_read = ap_get_client_block(r, argsbuffer,
> sizeof(argsbuffer))) > 0)
> {
> if ((rpos + len_read) > length)
> {
> rsize = length - rpos;
> }
> else
> {
> rsize = len_read;
> }
> memcpy((char*) *rbuf + rpos, argsbuffer, rsize);
> rpos += rsize;
> }
> }
> }
> return rc;{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Moved] (COMDEV-366) also generate project statistics for reporter.a.o
[ https://issues.apache.org/jira/browse/COMDEV-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb moved WHIMSY-307 to COMDEV-366: Component/s: (was: BoardAgenda) Reporter Tool Key: COMDEV-366 (was: WHIMSY-307) Workflow: classic default workflow (was: jira) Project: Community Development (was: Whimsy) > also generate project statistics for reporter.a.o > - > > Key: COMDEV-366 > URL: https://issues.apache.org/jira/browse/COMDEV-366 > Project: Community Development > Issue Type: Task > Components: Reporter Tool >Reporter: Mark Struberg >Priority: Major > > The old reporter.a.o site used to also generate the project statistics about > project members, releases, mailing list stats and issue tracker stats. This > feature got lost on the new site. There is now an extra page for those stats > which means the information is still accessible. > Some board members demanded those stats on one of my last report. It would be > great to have them back on the generated report template. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-340) Surprising categories on "Projects by category" page
[ https://issues.apache.org/jira/browse/COMDEV-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061560#comment-17061560 ] Sebb commented on COMDEV-340: - As per https://projects.apache.org/about.html, the DOAP files are listed in https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml > Surprising categories on "Projects by category" page > > > Key: COMDEV-340 > URL: https://issues.apache.org/jira/browse/COMDEV-340 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Piotr Zygielo >Priority: Minor > Attachments: apache-categories.png > > > Page https://projects.apache.org/projects.html?category lists Kafka and > Commons-RNG under surprising categories: > "https://projects.apache.org/projects.html?category#big-data; > and > "https://projects.apache.org/projects.html?category#library; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-340) Surprising categories on "Projects by category" page
[ https://issues.apache.org/jira/browse/COMDEV-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061542#comment-17061542 ] Sebb commented on COMDEV-340: - FTR, fixed in URL: http://svn.apache.org/viewvc?rev=1874754=rev Log: Fix category syntax Modified: commons/cms-site/trunk/doap/doap_rng.rdf > Surprising categories on "Projects by category" page > > > Key: COMDEV-340 > URL: https://issues.apache.org/jira/browse/COMDEV-340 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Piotr Zygielo >Priority: Minor > Attachments: apache-categories.png > > > Page https://projects.apache.org/projects.html?category lists Kafka and > Commons-RNG under surprising categories: > "https://projects.apache.org/projects.html?category#big-data; > and > "https://projects.apache.org/projects.html?category#library; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-340) Surprising categories on "Projects by category" page
[ https://issues.apache.org/jira/browse/COMDEV-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050644#comment-17050644 ] Sebb commented on COMDEV-340: - If you want to find out, just change the setting in a DOAP in one of your projects and see what happens. > Surprising categories on "Projects by category" page > > > Key: COMDEV-340 > URL: https://issues.apache.org/jira/browse/COMDEV-340 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Piotr Zygielo >Priority: Minor > Attachments: apache-categories.png > > > Page https://projects.apache.org/projects.html?category lists Kafka and > Commons-RNG under surprising categories: > "https://projects.apache.org/projects.html?category#big-data; > and > "https://projects.apache.org/projects.html?category#library; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-340) Surprising categories on "Projects by category" page
[ https://issues.apache.org/jira/browse/COMDEV-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050596#comment-17050596 ] Sebb commented on COMDEV-340: - I don't know if the protocol matters. The code and website are open to all to fix. > Surprising categories on "Projects by category" page > > > Key: COMDEV-340 > URL: https://issues.apache.org/jira/browse/COMDEV-340 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Piotr Zygielo >Priority: Minor > Attachments: apache-categories.png > > > Page https://projects.apache.org/projects.html?category lists Kafka and > Commons-RNG under surprising categories: > "https://projects.apache.org/projects.html?category#big-data; > and > "https://projects.apache.org/projects.html?category#library; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-340) Surprising categories on "Projects by category" page
[ https://issues.apache.org/jira/browse/COMDEV-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050536#comment-17050536 ] Sebb commented on COMDEV-340: - Note that there is already a page to create DOAPs https://projects.apache.org/create.html This has a drop-down list of categories > Surprising categories on "Projects by category" page > > > Key: COMDEV-340 > URL: https://issues.apache.org/jira/browse/COMDEV-340 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Piotr Zygielo >Priority: Minor > Attachments: apache-categories.png > > > Page https://projects.apache.org/projects.html?category lists Kafka and > Commons-RNG under surprising categories: > "https://projects.apache.org/projects.html?category#big-data; > and > "https://projects.apache.org/projects.html?category#library; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-340) Surprising categories on "Projects by category" page
[ https://issues.apache.org/jira/browse/COMDEV-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050534#comment-17050534 ] Sebb commented on COMDEV-340: - As per the first comment, the problem is that the DOAPs have used incorrect / unexpected syntax for the categories. The expected syntax is described here: https://projects.apache.org/guidelines.html The projects have used a valid category name, but presented it in the wrong syntax. I can sort out Commons-RNG. Perhaps someone else can get Kafka to fix their DOAP? > Surprising categories on "Projects by category" page > > > Key: COMDEV-340 > URL: https://issues.apache.org/jira/browse/COMDEV-340 > Project: Community Development > Issue Type: Improvement > Components: Projects Tool >Reporter: Piotr Zygielo >Priority: Minor > Attachments: apache-categories.png > > > Page https://projects.apache.org/projects.html?category lists Kafka and > Commons-RNG under surprising categories: > "https://projects.apache.org/projects.html?category#big-data; > and > "https://projects.apache.org/projects.html?category#library; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-339) understanding some stuff
[ https://issues.apache.org/jira/browse/COMDEV-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018195#comment-17018195 ] Sebb commented on COMDEV-339: - Help Wanted is also a COMDEV responsibility; see the bottom of the page here: https://helpwanted.apache.org > understanding some stuff > > > Key: COMDEV-339 > URL: https://issues.apache.org/jira/browse/COMDEV-339 > Project: Community Development > Issue Type: Question > Components: Help Wanted >Reporter: Tommaso >Priority: Major > > Hi everybody, > i have some questions i would like to ask: > 1) I noticed that last update can go beyond closure date, so probably it > changes even if i just comment under the issue (i'm not sure), is there > another reason? > 2)I don't understand if i can use Days in current status to assert resolution > time for closed issues, or if i have to consider the delta resolutiondate - > creationdate > thanks for the attention > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-337) Are the beta files still relevant?
[ https://issues.apache.org/jira/browse/COMDEV-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-337. - Resolution: Fixed Thanks > Are the beta files still relevant? > -- > > Key: COMDEV-337 > URL: https://issues.apache.org/jira/browse/COMDEV-337 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > Are these still in use? > site/wizard/beta.html > site/wizard/js/wizard-beta.js > They seem to be much the same as: > site/wizard/index.html > site/wizard/js/wizard.js > It's confusing to have both -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-337) Are the beta files still relevant?
[ https://issues.apache.org/jira/browse/COMDEV-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed COMDEV-337. --- > Are the beta files still relevant? > -- > > Key: COMDEV-337 > URL: https://issues.apache.org/jira/browse/COMDEV-337 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > Are these still in use? > site/wizard/beta.html > site/wizard/js/wizard-beta.js > They seem to be much the same as: > site/wizard/index.html > site/wizard/js/wizard.js > It's confusing to have both -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-337) Are the beta files still relevant?
Sebb created COMDEV-337: --- Summary: Are the beta files still relevant? Key: COMDEV-337 URL: https://issues.apache.org/jira/browse/COMDEV-337 Project: Community Development Issue Type: Bug Components: Reporter Tool Reporter: Sebb Are these still in use? site/wizard/beta.html site/wizard/js/wizard-beta.js They seem to be much the same as: site/wizard/index.html site/wizard/js/wizard.js It's confusing to have both -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-326) Committer invite template omits PMC role details
[ https://issues.apache.org/jira/browse/COMDEV-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972732#comment-16972732 ] Sebb commented on COMDEV-326: - Furthermore, the page does not make clear that an invite to become a PMC member is conditional on acceptance by the board. If the invite is sent before the NOTICE period has elapsed, the invite should make it clear that it subject to approval by the board. Generally it's simpler to delay sending any PMC invitation until after the NOTICE period. > Committer invite template omits PMC role details > > > Key: COMDEV-326 > URL: https://issues.apache.org/jira/browse/COMDEV-326 > Project: Community Development > Issue Type: Bug > Components: Website > Environment: > https://community.apache.org/newcommitter.html#committer-invite-template >Reporter: Sebb >Priority: Major > > The committer invite template [1] is not very clear on the distinction > between an invitation as a committer, and invitation as a committer + PMC > member. > In particular, it describes the role of the committer, but largely ignores > the PMC role. > As a result, I have seen at least one acceptance reply that said "I accept to > become a committer" [2] - leaving unstated whether or not they agree to > become a PMC member. > I think any template needs to make very clear what is involved in the PMC > role, and also that the invitee has 3 choices: > - decline both invites > - accept the committer invite and decline the PMC invite > - accept both committer invite and PMC invite > [1] https://community.apache.org/newcommitter.html#committer-invite-template > [2] > https://lists.apache.org/thread.html/796c4b3e8c0f191add39c7d1b6cc154a5e316910df8120db1151c739@%3Cprivate.jackrabbit.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-332) Reporter landing page does not show contact details
Sebb created COMDEV-332: --- Summary: Reporter landing page does not show contact details Key: COMDEV-332 URL: https://issues.apache.org/jira/browse/COMDEV-332 Project: Community Development Issue Type: Bug Components: Reporter Tool Reporter: Sebb The reporter landing page does not show any contact details. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-331) Only store output files in SVN if the cannot be recreated
Sebb created COMDEV-331: --- Summary: Only store output files in SVN if the cannot be recreated Key: COMDEV-331 URL: https://issues.apache.org/jira/browse/COMDEV-331 Project: Community Development Issue Type: Improvement Components: Projects Tool Reporter: Sebb There are lots of output files under site/sjon. Do they all need to be stored in SVN? If the file can be recreated easily, and there is no need for the history, then it seems wasteful to store it in SVN. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-330) parsereleases gets the wrong dates for releases
[ https://issues.apache.org/jira/browse/COMDEV-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated COMDEV-330: Component/s: (was: Reporter Tool) Projects Tool > parsereleases gets the wrong dates for releases > --- > > Key: COMDEV-330 > URL: https://issues.apache.org/jira/browse/COMDEV-330 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Sebb >Priority: Major > > parsereleases.py uses dates parse from www.apache.org/dist. > These may change if the site is refreshed (as happened recently). > It might be better to get the dates from an SVN listing of dist.apache.org. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
