[jira] [Created] (COMDEV-333) pet school how to project

[Jira]

Murat Güngör created COMDEV-333:
---

 Summary: pet school how to project
 Key: COMDEV-333
 URL: https://issues.apache.org/jira/browse/COMDEV-333
 Project: Community Development
  Issue Type: New Feature
  Components: Website
Reporter: Murat Güngör


pet school professional dog training and dog hotel website
I

[https://petokulu.com/]

how do you think



--
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-341) Apache RocketMQ Scaler for KEDA

[Jira]

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

Ismaël Mejía commented on COMDEV-341:
-

Any particular reason for this issue to be in COMDEV instead of ROCKETMQ's 
JIRA? or is this just a mistake?

> Apache RocketMQ Scaler for KEDA
> ---
>
> Key: COMDEV-341
> URL: https://issues.apache.org/jira/browse/COMDEV-341
> Project: Community Development
>  Issue Type: Wish
>  Components: GSoC/Mentoring ideas
>Reporter: duheng
>Priority: Major
>  Labels: RocketMQ, gsoc2020
>
> h3. Context
> KEDA allows for fine-grained autoscaling (including to/from zero) for 
> event-driven Kubernetes workloads. KEDA serves as a Kubernetes Metrics Server 
> and allows users to define autoscaling rules using a dedicated Kubernetes 
> custom resource definition. KEDA has a number of “scalers” that can both 
> detect if a deployment should be activated or deactivated, and feed custom 
> metrics for a specific event source. In this topic, you need to implement the 
> RocketMQ scalers.
> h3. You should learn before applying for this topic
> Helm/Apache RocketMQ Operator/Apache RocketMQ Docker Image
> Apache RocketMQ multi-replica mechanism(based on DLedger)
> How KEDA works
> h3. Mentor
> [wlliqip...@apache.org|mailto:wlliqip...@apache.org], 
> [vongosl...@apache.org|mailto:vongosl...@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

[jira] [Created] (COMDEV-364) 3w 4d 12h

[Jira]

منصة شليله created COMDEV-364:
-

 Summary:  3w 4d 12h
 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: منصة شليله






--
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-363) مجموعةمنصةشليله

[Jira]

منصة شليله created COMDEV-363:
-

 Summary: مجموعةمنصةشليله
 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: منصة شليله
 Attachments: Screenshot_20200322-083758_Chrome.jpg, منصة شليله.pdf, 
نشاطي في Play - Google Play

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] [Commented] (COMDEV-364) 3w 4d 12h

[Jira]

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

منصة شليله commented on COMDEV-364:
---

منصةشليله 

Android web etc. 

Automatic All 

 3w 4d 12h

>  3w 4d 12h
> --
>
> 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] [Updated] (COMDEV-364) منصة شليله

[Jira]

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

منصة شليله updated COMDEV-364:
--
Summary: منصة شليله  (was:  3w 4d 12h)

> منصة شليله
> --
>
> 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] [Created] (COMDEV-370) CLONE - localhost.crt does not exist or is empty

[Jira]

منصة شليله created COMDEV-370:
-

 Summary: 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: منصة شليله


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:  
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) 
 File 
"/opt/eff.org/certbot/venv/lib64/python3.6/site-packages/certbot/plugins/selection.py",
 line 339, in diagnose_configurator_problem 
 raise errors.PluginSelectionError(msg) 
certbot.errors.PluginSelectionError: The apache plugin is not working; there 
may be problems with your existing configuration. 
The error was: MisconfigurationError("Error while running apachectl

[jira] [Created] (COMDEV-379) منصة شليله

[Jira]

منصة شليله created COMDEV-379:
-

 Summary: منصة شليله
 Key: COMDEV-379
 URL: https://issues.apache.org/jira/browse/COMDEV-379
 Project: Community Development
  Issue Type: Project
  Components: GSoC/Mentoring ideas, Website
Reporter: منصة شليله






--
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-380) منصة شليله

[Jira]

منصة شليله  created COMDEV-380:
--

 Summary: منصة شليله
 Key: COMDEV-380
 URL: https://issues.apache.org/jira/browse/COMDEV-380
 Project: Community Development
  Issue Type: Bug
  Components: Website
 Environment: مجموعةمنصةشليله 
https://docs.google.com/forms/d/e/1FAIpQLSdm6f8Qy7zQgTzmXsK5E2jDpQZYq1vxeoi23SonAA30pdHgUQ/viewform?chromeless=1&e
Reporter: منصة شليله 
 Attachments: trello-brand-assets.zip

[link 
title|http://example.com][mailto:m...@example.com][#anchor]??[^trello-brand-assets.zip]??



--
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-370) CLONE - localhost.crt does not exist or is empty

[Jira]

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

منصة شليله updated COMDEV-370:
--
Attachment: www.mnstshlylh.web.pdf

> 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
> Attachments: www.mnstshlylh.web.pdf
>
>
> 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 =

[jira] [Commented] (COMDEV-341) Apache RocketMQ Scaler for KEDA

[Jira]

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

رضا جزینانی  commented on COMDEV-341:
-

سلام 


> Apache RocketMQ Scaler for KEDA
> ---
>
> Key: COMDEV-341
> URL: https://issues.apache.org/jira/browse/COMDEV-341
> Project: Community Development
>  Issue Type: Wish
>  Components: GSoC/Mentoring ideas
>Reporter: duheng
>Priority: Major
>  Labels: RocketMQ, gsoc2020
>
> h3. Context
> KEDA allows for fine-grained autoscaling (including to/from zero) for 
> event-driven Kubernetes workloads. KEDA serves as a Kubernetes Metrics Server 
> and allows users to define autoscaling rules using a dedicated Kubernetes 
> custom resource definition. KEDA has a number of “scalers” that can both 
> detect if a deployment should be activated or deactivated, and feed custom 
> metrics for a specific event source. In this topic, you need to implement the 
> RocketMQ scalers.
> h3. You should learn before applying for this topic
> Helm/Apache RocketMQ Operator/Apache RocketMQ Docker Image
> Apache RocketMQ multi-replica mechanism(based on DLedger)
> How KEDA works
> h3. Mentor
> [wlliqip...@apache.org|mailto:wlliqip...@apache.org], 
> [vongosl...@apache.org|mailto:vongosl...@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

[jira] [Created] (COMDEV-413) GSoC: Apache CouchDB and Debezium integration

[Jira]

Balázs Donát Bessenyei created COMDEV-413:
-

 Summary: GSoC: Apache CouchDB and Debezium integration
 Key: COMDEV-413
 URL: https://issues.apache.org/jira/browse/COMDEV-413
 Project: Community Development
  Issue Type: New Feature
  Components: GSoC/Mentoring ideas
Reporter: Balázs Donát Bessenyei


Apache CouchDB software is a document-oriented database that can be queried and 
indexed in a MapReduce fashion using JavaScript. CouchDB also offers 
incremental replication with bi-directional conflict detection and resolution.

Debezium is an open source distributed platform for change data capture. Start 
it up, point it at your databases, and your apps can start responding to all of 
the inserts, updates, and deletes that other apps commit to your databases. 
Debezium is durable and fast, so your apps can respond quickly and never miss 
an event, even when things go wrong.

 

CouchDB has a change capture feed as a public HTTP API endpoint. Integrating 
with Debezium would provide an easy way to translate the _changes feed into a 
Kafka topic which plugs us into a much larger ecosystem of tools and alleviates 
the need for every consumer of data in CouchDB to build a bespoke “follower” of 
the _changes feed.

 

The project for GSoC 2021 here is to design, implement and test a CouchDB 
connector for Debezium.

 

Required skills:
 - Java

Nice-to-have skills:
 * Erlang



--
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-245) statistics.html does not describe what the data means

[Jira]

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

Jan Høydahl commented on COMDEV-245:


I just had an issue with the newly created Solr project - its commit stats and 
"busiest email threads" stats were missing, and Gruno did some magic in Kibble 
to fix it.

The README for reporter tool could mention in more detail that these stats are 
fetched from Kibble and who to contact if it is broken.

> 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: Reporter 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] [Commented] (COMDEV-434) Projects.apache.org - Statistics tab is not working

[Jira]

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

ECOR、one commented on COMDEV-434:
-

退订，叼NMD

发自我的iPad


-- Original --
From: Andrea Cosentino (Jira) https://issues.apache.org/jira/browse/COMDEV-434
 
Project: Community Development
  Issue Type: Bug
  Components: Website
    Reporter: 
Andrea Cosentino


https://projects.apache.org/statistics.html

I think it's in this situation since 15 days more or less.

Not sure what it's the problem.



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


> Projects.apache.org - Statistics tab is not working
> ---
>
> Key: COMDEV-434
> URL: https://issues.apache.org/jira/browse/COMDEV-434
> Project: Community Development
>  Issue Type: Bug
>  Components: Website
>Reporter: Andrea Cosentino
>Priority: Major
>
> https://projects.apache.org/statistics.html
> I think it's in this situation since 15 days more or less.
> Not sure what it's the problem.



--
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] [Created] (COMDEV-436) parsereleases produces false releases for solr

[Jira]

Jan Høydahl created COMDEV-436:
--

 Summary: 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


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.1#820001)

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

[jira] [Commented] (COMDEV-413) GSoC: Apache CouchDB and Debezium integration

[Jira]

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

Balázs Donát Bessenyei commented on COMDEV-413:
---

[~gimhana.ds] : please contact the developer community at 
[d...@couchdb.apache.org|mailto:d...@couchdb.apache.org] 

> GSoC: Apache CouchDB and Debezium integration
> -
>
> Key: COMDEV-413
> URL: https://issues.apache.org/jira/browse/COMDEV-413
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Balázs Donát Bessenyei
>Priority: Major
>  Labels: CouchDB, couchdb, gsoc2021, mentor
>
> Apache CouchDB software is a document-oriented database that can be queried 
> and indexed in a MapReduce fashion using JavaScript. CouchDB also offers 
> incremental replication with bi-directional conflict detection and resolution.
> Debezium is an open source distributed platform for change data capture. 
> Start it up, point it at your databases, and your apps can start responding 
> to all of the inserts, updates, and deletes that other apps commit to your 
> databases. Debezium is durable and fast, so your apps can respond quickly and 
> never miss an event, even when things go wrong.
>  
> CouchDB has a change capture feed as a public HTTP API endpoint. Integrating 
> with Debezium would provide an easy way to translate the _changes feed into a 
> Kafka topic which plugs us into a much larger ecosystem of tools and 
> alleviates the need for every consumer of data in CouchDB to build a bespoke 
> “follower” of the _changes feed.
>  
> The project for GSoC 2021 here is to design, implement and test a CouchDB 
> connector for Debezium.
>  
> Required skills:
>  - Java
> Nice-to-have skills:
>  * Erlang



--
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] [Comment Edited] (COMDEV-413) GSoC: Apache CouchDB and Debezium integration

[Jira]

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

Balázs Donát Bessenyei edited comment on COMDEV-413 at 1/17/22, 3:39 AM:
-

[~gimhana.ds] : I suggest contacting the developer community at 
[d...@couchdb.apache.org|mailto:d...@couchdb.apache.org] 


was (Author: bessbd):
[~gimhana.ds] : please contact the developer community at 
[d...@couchdb.apache.org|mailto:d...@couchdb.apache.org] 

> GSoC: Apache CouchDB and Debezium integration
> -
>
> Key: COMDEV-413
> URL: https://issues.apache.org/jira/browse/COMDEV-413
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Balázs Donát Bessenyei
>Priority: Major
>  Labels: CouchDB, couchdb, gsoc2021, mentor
>
> Apache CouchDB software is a document-oriented database that can be queried 
> and indexed in a MapReduce fashion using JavaScript. CouchDB also offers 
> incremental replication with bi-directional conflict detection and resolution.
> Debezium is an open source distributed platform for change data capture. 
> Start it up, point it at your databases, and your apps can start responding 
> to all of the inserts, updates, and deletes that other apps commit to your 
> databases. Debezium is durable and fast, so your apps can respond quickly and 
> never miss an event, even when things go wrong.
>  
> CouchDB has a change capture feed as a public HTTP API endpoint. Integrating 
> with Debezium would provide an easy way to translate the _changes feed into a 
> Kafka topic which plugs us into a much larger ecosystem of tools and 
> alleviates the need for every consumer of data in CouchDB to build a bespoke 
> “follower” of the _changes feed.
>  
> The project for GSoC 2021 here is to design, implement and test a CouchDB 
> connector for Debezium.
>  
> Required skills:
>  - Java
> Nice-to-have skills:
>  * Erlang



--
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-436) parsereleases produces false releases for solr

[Jira]

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

Jan Høydahl commented on COMDEV-436:


Hi. Anyone watching this space? :) 

> 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
>
> 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.1#820001)

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

[jira] [Commented] (COMDEV-170) issues in "Projects list by Number of Committers"

[Jira]

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

Jan Høydahl commented on COMDEV-170:


We noticed that projects lucene-core, lucene-pylucene are not listed on this 
page either, and found the bug. Here is a patch which fixes a bug where 
project-id (e.g. lucene-core) was used to lookup unixGroup. Now the list 
becomes much longer.

I agree this page may be misleading for the reasons above, and e.g. the Commons 
projects would better be listed as one project instead of 43 separate ones?
{code:java}
Index: site/js/projects.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===
diff --git a/site/js/projects.js b/site/js/projects.js
--- a/site/js/projects.js    (revision 1905309)
+++ b/site/js/projects.js    (date 1668463359422)
@@ -263,6 +263,24 @@
     return appendElementWithInnerHTML(ul,'li',html);
 }
 
+function projectIdToUnixGroup(projectId, pmcName) {
+    // Rerig the unix name and committee id
+    var unixgroup = projectId.split("-")[0];
+    /*
+      Temp hack for podling names. TODO need to sort out generated names
+    */
+    if (projectId.indexOf("incubator-") === 0) {
+      unixgroup = projectId.split("-")[1]
+    }
+    // special cases
+    if (unixgroup === "empire") unixgroup = "empire-db";
+    if (unixgroup === "community") unixgroup = "comdev";
+    if (pmcName === "attic") {
+      unixgroup = "attic";
+    }
+    return unixgroup;
+}
+
 function renderProjectPage(project, projectId) {
     var obj = document.getElementById('contents');
 
@@ -278,20 +296,7 @@
     fixProjectName(project);
     var isIncubating = project && (project.podling || (project.pmc == 
'incubator'));
 
-    // Rerig the unix name and committee id
-    var unixgroup = projectId.split("-")[0];
-    /*
-      Temp hack for podling names. TODO need to sort out generated names
-    */
-    if (projectId.indexOf("incubator-") == 0) {
-        unixgroup = projectId.split("-")[1]
-    }
-    // special cases
-    if (unixgroup == "empire") unixgroup = "empire-db";
-    if (unixgroup == "community") unixgroup = "comdev";
-    if (project && project.pmc == "attic") {
-        unixgroup = "attic";
-    }
+    var unixgroup = projectIdToUnixGroup(projectId, project && project.pmc);
 
     var committeeId = isIncubating ? 'incubator' : unixgroup;
     if (!committees[unixgroup]) {
@@ -825,9 +830,10 @@
 
     var lens = [];
     var lcount = {};
-    for (i in projects) {
-        if (unixgroups[i] && i != 'incubator') {
-            var len = unixgroups[i].length;
+    for (projectId in projects) {
+        let unixGroup = projectIdToUnixGroup(projectId);
+        if (unixgroups[unixGroup] && projectId !== 'incubator') {
+            let len = unixgroups[unixGroup].length;
             if (lens.indexOf(len) < 0) {
                     lens.push(len);
                     lcount[len] = 0;
@@ -842,15 +848,16 @@
 
     for (l in lens) {
         var len = lens[l];
-        var i;
-        for (i in projectsSorted) {
-            i = projectsSorted[i];
-            if (unixgroups[i]) {
-                var xlen = unixgroups[i].length;
+        var projectId;
+        for (projectId in projectsSorted) {
+            projectId = projectsSorted[projectId];
+            let unixGroup = projectIdToUnixGroup(projectId);
+            if (unixgroups[unixGroup]) {
+                var xlen = unixgroups[unixGroup].length;
                 if (xlen == len) {
-                    var html = projectIcon(projects[i].name) + projectLink(i) 
+ ": " + len + " committers";
-                    if (unixgroups[i+'-pmc']) {
-                        html += ", " + unixgroups[i+'-pmc'].length + " PMC 
members";
+                    var html = projectIcon(projects[projectId].name) + 
projectLink(projectId) + ": " + len + " committers";
+                    if (unixgroups[unixGroup+'-pmc']) {
+                        html += ", " + unixgroups[unixGroup+'-pmc'].length + " 
PMC members";
                     }
                     appendLiInnerHTML(ul,html);
                 }
 {code}

> issues in "Projects list by Number of Committers"
> -
>
> Key: COMDEV-170
> URL: https://issues.apache.org/jira/browse/COMDEV-170
> Project: Community Development
>  I

[jira] [Created] (COMDEV-481) Projects tool "Projects by number of committers" lacks many projects

[Jira]

Jan Høydahl created COMDEV-481:
--

 Summary: Projects tool "Projects by number of committers" lacks 
many projects
 Key: COMDEV-481
 URL: https://issues.apache.org/jira/browse/COMDEV-481
 Project: Community Development
  Issue Type: Bug
  Components: Projects Tool
Reporter: Jan Høydahl
 Attachments: comdev-projects_js.patch

This page only lists 179 projects, and turns out those are only the ones that 
happen to have the same unixgroup as project-ID. E.g. 'lucene-core' with 97 
committers is not listed since its unixgroup is 'lucene'.

The fix is in the attached patch, applying the same projectId-to-unixgroup 
function as is used elsewhere in the same script. This brings the number of 
projects listed up to 377.

I agree with some of the comments in related issue COMDEV-170, that some 
projects may have committership != unixgroup, but that should be solved 
separately.



--
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-239) ASF Information Brochure - French Translation

[JIRA]

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

Hervé Boutemy commented on COMDEV-239:
--

a few complementary proposals I'd like to discuss before modifying content:

Outside
- "L'ASF est une société privée américaine, une association sans but lucratif." 
-> "L'ASF est une association américaine à but non-lucratif." (pas de notion de 
"société privée")
- "Pour des cadeaux uniques ou récurrents" -> "Pour des versements 
exceptionnels ou récurrents"
- "Parrainage de l'ASF" -> "Un parrainage de l'ASF"
- "L'Apache Software Foundation (ASF) fournit un support à la communauté Apache 
qui elle même propose des logiciels libres pour le bien public" -> "L'Apache 
Software Foundation (ASF) fournit un support à la communauté des projets 
Apache, qui eux-même proposent des logiciels libres pour le bien public"
- "Les "projets Apache" sont définis par un processus basé sur un consensus 
collaboratif, une licence logicielle pragmatique et une volonté de créer des 
logiciels de haute qualité, qui ouvre la voie dans son domaine" -> "Les 
"projets Apache" sont définis par un processus collaboratif basé sur le 
consensus, une licence logicielle pragmatique et une volonté de créer des 
logiciels de haute qualité, qui ouvrent la voie dans leur domaine"

Inside:
- pour les 6 points, rajouter "En" ("En fournissant une base...")
- je ne suis pas trop à l'aide avec "des infrastructures de communication 
pro-business": d'ailleurs, même en version anglaise, je ne comprends pas 
pourquoi "business infrastructure"
- et pas mal de petites fautes de frappe ou légères améliorations de mise en 
page

Please confirm it makes sense, and I'll update content

> ASF Information Brochure - French Translation
> -
>
> Key: COMDEV-239
> URL: https://issues.apache.org/jira/browse/COMDEV-239
> Project: Community Development
>  Issue Type: Improvement
>Reporter: Jacques Le Roux
>Assignee: Ignasi Barrera
>Priority: Minor
> Attachments: brochure-fr.pdf, brochure-fr.pdf, 
> brochure-inside-fr.xcf, brochure-outside-fr.xcf
>
>
> There are some possible improvements for the French Translation of the ASF 
> Information Brochure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (COMDEV-239) ASF Information Brochure - French Translation

[JIRA]

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

Hervé Boutemy commented on COMDEV-239:
--

if the will is the most important part, I propose to rephrase like this:
"Les "projets Apache" sont définis par un processus collaboratif basé sur le 
consensus, une licence logicielle pragmatique et une volonté d'ouvrir la voie 
dans leur domaine en créant des logiciels de haute qualité"

> ASF Information Brochure - French Translation
> -
>
> Key: COMDEV-239
> URL: https://issues.apache.org/jira/browse/COMDEV-239
> Project: Community Development
>  Issue Type: Improvement
>Reporter: Jacques Le Roux
>Assignee: Ignasi Barrera
>Priority: Minor
> Attachments: brochure-fr.pdf, brochure-fr.pdf, 
> brochure-inside-fr.xcf, brochure-outside-fr.xcf
>
>
> There are some possible improvements for the French Translation of the ASF 
> Information Brochure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (COMDEV-239) ASF Information Brochure - French Translation

[JIRA]

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

Hervé Boutemy commented on COMDEV-239:
--

or
"Les "projets Apache" sont définis par un processus collaboratif basé sur le 
consensus, une licence logicielle pragmatique et une volonté de créer des 
logiciels de haute qualité qui ouvre la voie dans son domaine"
(just removing the coma helps)

> ASF Information Brochure - French Translation
> -
>
> Key: COMDEV-239
> URL: https://issues.apache.org/jira/browse/COMDEV-239
> Project: Community Development
>  Issue Type: Improvement
>Reporter: Jacques Le Roux
>Assignee: Ignasi Barrera
>Priority: Minor
> Attachments: brochure-fr.pdf, brochure-fr.pdf, 
> brochure-inside-fr.xcf, brochure-outside-fr.xcf
>
>
> There are some possible improvements for the French Translation of the ASF 
> Information Brochure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (COMDEV-239) ASF Information Brochure - French Translation

[JIRA]

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

Hervé Boutemy commented on COMDEV-239:
--

I just published with the last proposal, in r1813946

> ASF Information Brochure - French Translation
> -
>
> Key: COMDEV-239
> URL: https://issues.apache.org/jira/browse/COMDEV-239
> Project: Community Development
>  Issue Type: Improvement
>Reporter: Jacques Le Roux
>Assignee: Ignasi Barrera
>Priority: Minor
> Attachments: brochure-fr.pdf, brochure-fr.pdf, 
> brochure-inside-fr.xcf, brochure-outside-fr.xcf
>
>
> There are some possible improvements for the French Translation of the ASF 
> Information Brochure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (COMDEV-239) ASF Information Brochure - French Translation

[JIRA]

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

Hervé Boutemy commented on COMDEV-239:
--

"une volonté de création qui ouvre la voie dans le domaine des logiciels de 
haute qualité "
+1: we got it!

another little proposal: "faire partie des efforts faits à l'ASF" -> "faire 
partie des efforts soutenus par l'ASF"?

> ASF Information Brochure - French Translation
> -
>
> Key: COMDEV-239
> URL: https://issues.apache.org/jira/browse/COMDEV-239
> Project: Community Development
>  Issue Type: Improvement
>Reporter: Jacques Le Roux
>Assignee: Ignasi Barrera
>Priority: Minor
> Attachments: brochure-fr.pdf, brochure-fr.pdf, 
> brochure-inside-fr.xcf, brochure-outside-fr.xcf
>
>
> There are some possible improvements for the French Translation of the ASF 
> Information Brochure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (COMDEV-239) ASF Information Brochure - French Translation

[JIRA]

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

Hervé Boutemy commented on COMDEV-239:
--

perfect!
thank you

> ASF Information Brochure - French Translation
> -
>
> Key: COMDEV-239
> URL: https://issues.apache.org/jira/browse/COMDEV-239
> Project: Community Development
>  Issue Type: Improvement
>Reporter: Jacques Le Roux
>Assignee: Ignasi Barrera
>Priority: Minor
> Attachments: brochure-fr.pdf, brochure-fr.pdf, 
> brochure-inside-fr.xcf, brochure-outside-fr.xcf
>
>
> There are some possible improvements for the French Translation of the ASF 
> Information Brochure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (COMDEV-135) improve css to have the head banner stay visible when scrolling down

[JIRA]

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

Hervé Boutemy updated COMDEV-135:
-
Description: 
see W3Schools CSS tutorial banner to see this in action: 
http://www.w3schools.com/css/

this would ease navigation from tab to tab in http://projects.apache.org/

  was:
see W3Schools CSS tutorial banner to see this in action: 
http://www.w3schools.com/css/

this would ease navigation


> improve css to have the head banner stay visible when scrolling down
> 
>
> Key: COMDEV-135
> URL: https://issues.apache.org/jira/browse/COMDEV-135
> Project: Community Development
>  Issue Type: Improvement
>  Components: Projects Website
>Reporter: Hervé Boutemy
>
> see W3Schools CSS tutorial banner to see this in action: 
> http://www.w3schools.com/css/
> this would ease navigation from tab to tab in http://projects.apache.org/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Reopened] (COMDEV-135) improve css to have the head banner stay visible when scrolling down

[JIRA]

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

Hervé Boutemy reopened COMDEV-135:
--

I was not clear by simply marking "components: Projects Website"
the http://community.apache.org redesign has the feature, yes
but this issue is about http://projects.apache.org

> improve css to have the head banner stay visible when scrolling down
> 
>
> Key: COMDEV-135
> URL: https://issues.apache.org/jira/browse/COMDEV-135
> Project: Community Development
>  Issue Type: Improvement
>  Components: Projects Website
>Reporter: Hervé Boutemy
>
> see W3Schools CSS tutorial banner to see this in action: 
> http://www.w3schools.com/css/
> this would ease navigation from tab to tab in http://projects.apache.org/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (COMDEV-60) Apache Ant Development

[JIRA]

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

Jan Matèrne commented on COMDEV-60:
---

Long forgotten ticket from GSoC 2011.
But I can't "close" this (maybe because it's a "New Feature"-ticket).

> Apache Ant Development
> --
>
> Key: COMDEV-60
>     URL: https://issues.apache.org/jira/browse/COMDEV-60
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Antoine Levy-Lambert
>  Labels: gsoc2011
>
> Participate in the development of Apache Ant, ( http://ant.apache.org ). We 
> would like to find one or several students interested in helping us solve the 
> open issues submitted in bugzilla. 
> This web page http://ant.apache.org/bugs.html provides pointers to the open 
> bugs of ant.
> The mentor will help the student define a process to solve the bug reports, 
> and navigate with the students the requirements of the Apache Ant project 
> (code quality, tests, documentation).
> The student and the mentor will discuss which bugs to pick for this exercise, 
> trying to match what is interesting for the student together with what is 
> feasible in the available time, with an eye to usefulness for the user 
> community.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (COMDEV-257) Reporter does not calculate next report date correctly at month end

[JIRA]

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

Jan Matèrne commented on COMDEV-257:


Cool. Works now.

> Reporter does not calculate next report date correctly at month end
> ---
>
> Key: COMDEV-257
> URL: https://issues.apache.org/jira/browse/COMDEV-257
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Sebb
>Assignee: Sebb
>Priority: Major
>
> The page for Ant via https://reporter.apache.org/ shows:
> * Reporting schedule: February, May, August, November
> * Next report date: Wed Mar 21 2018
> This is clearly wrong.
> A quick scan shows the getWednesdays method does not work if the current day 
> of the month does not exist in the next month: e.g. 31st (Jan) does not exist 
> in Feb.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-288) Request "Projects Directory" migration to GIT

[JIRA]

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

Hervé Boutemy commented on COMDEV-288:
--

Let's start by adding a svn2git read-only mirror, like those visible on 
http://git.apache.org/
You'll be able to propose PRs (that committers will have to merge to canonical 
svn repo)

> Request "Projects Directory" migration to GIT
> -
>
> Key: COMDEV-288
> URL: https://issues.apache.org/jira/browse/COMDEV-288
> Project: Community Development
>  Issue Type: SVN->GIT Migration
>  Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> Dear all,
> is it possible for you to plan SVN to GIT migration for "Projects Directory" 
> project ?
> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/{color}]
> Thank you,
> Regards.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-287) Projects Directory About. Link broken

[JIRA]

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

Hervé Boutemy commented on COMDEV-287:
--

oh no, links to Jira components like 
https://issues.apache.org/jira/browse/COMDEV/component/${component id} have 
been disabled during Jira upgrades
thanks for the report, since I have such links in a lot of locations, not only 
on projects.apache.org...

does anybody know if this is a purely removed feature or if it can be enabled?
And is there a recommended new link template to have equivalent pointer to open 
issues of a component?

> Projects Directory About. Link broken
> -
>
> Key: COMDEV-287
> URL: https://issues.apache.org/jira/browse/COMDEV-287
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> On "About" Projects Directory page : [https://projects.apache.org/about.html]
> Link "{color:#0066cc}COMDEV Jira issue in the "Projects" component{color}" is 
> broken.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-288) Request "Projects Directory" migration to GIT

[JIRA]

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

Hervé Boutemy commented on COMDEV-288:
--

FYI, see discussion 
https://lists.apache.org/thread.html/3efa0dbbab20417ad0b89961aed49012698f1a2476771164f4b70756@%3Cdev.community.apache.org%3E

> Request "Projects Directory" migration to GIT
> -
>
> Key: COMDEV-288
> URL: https://issues.apache.org/jira/browse/COMDEV-288
> Project: Community Development
>  Issue Type: SVN->GIT Migration
>  Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> Dear all,
> is it possible for you to plan SVN to GIT migration for "Projects Directory" 
> project ?
> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/{color}]
> Thank you,
> Regards.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Closed] (COMDEV-287) Projects Directory About. Link broken

[JIRA]

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

Hervé Boutemy closed COMDEV-287.

Resolution: Fixed
  Assignee: Hervé Boutemy

fixed in [r1848283|http://svn.apache.org/r1848283]

> Projects Directory About. Link broken
> -
>
> Key: COMDEV-287
> URL: https://issues.apache.org/jira/browse/COMDEV-287
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Vincent Tuybens
>Assignee: Hervé Boutemy
>Priority: Trivial
>
> On "About" Projects Directory page : [https://projects.apache.org/about.html]
> Link "{color:#0066cc}COMDEV Jira issue in the "Projects" component{color}" is 
> broken.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-286) Projects Directory: multiple JavaScript categories

[JIRA]

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

Hervé Boutemy updated COMDEV-286:
-
Summary: Projects Directory: multiple JavaScript categories  (was: Projects 
Directory)

> Projects Directory: multiple JavaScript categories
> --
>
> Key: COMDEV-286
> URL: https://issues.apache.org/jira/browse/COMDEV-286
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> On Projects Directory Website, on Projects list by Programming Language :
> [https://projects.apache.org/projects.html?language]
> 2 "Javascript" groups : JavaScript + Javascript.
> Workaround :
> Request to owners the modification of  balise on :
> [{color:#ff}http://milagro.incubator.apache.org/doap.rdf{color}]
> [{color:#ff}http://svn.apache.org/repos/asf/vcl/trunk/doap_vcl.rdf{color}]
>  
> Possible Fix : scripts/cronjob/parsecommitteeinfo.py to manage character case.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-286) Projects Directory: multiple case for JavaScript language

[JIRA]

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

Hervé Boutemy updated COMDEV-286:
-
Summary: Projects Directory: multiple case for JavaScript language  (was: 
Projects Directory: multiple JavaScript categories)

> Projects Directory: multiple case for JavaScript language
> -
>
> Key: COMDEV-286
> URL: https://issues.apache.org/jira/browse/COMDEV-286
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> On Projects Directory Website, on Projects list by Programming Language :
> [https://projects.apache.org/projects.html?language]
> 2 "Javascript" groups : JavaScript + Javascript.
> Workaround :
> Request to owners the modification of  balise on :
> [{color:#ff}http://milagro.incubator.apache.org/doap.rdf{color}]
> [{color:#ff}http://svn.apache.org/repos/asf/vcl/trunk/doap_vcl.rdf{color}]
>  
> Possible Fix : scripts/cronjob/parsecommitteeinfo.py to manage character case.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (COMDEV-302) add committe short description to committees listing

[JIRA]

Hervé Boutemy created COMDEV-302:


 Summary: 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: Hervé Boutemy


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
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-286) Projects Directory: multiple case for JavaScript language

[JIRA]

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

Hervé Boutemy commented on COMDEV-286:
--

[~jfthomps] doap url updated from svn to git in projects configuration in 
[r1848316|http://svn.apache.org/r1848316]

> Projects Directory: multiple case for JavaScript language
> -
>
> Key: COMDEV-286
> URL: https://issues.apache.org/jira/browse/COMDEV-286
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> On Projects Directory Website, on Projects list by Programming Language :
> [https://projects.apache.org/projects.html?language]
> 2 "Javascript" groups : JavaScript + Javascript.
> Workaround :
> Request to owners the modification of  balise on :
> [{color:#ff}http://milagro.incubator.apache.org/doap.rdf{color}]
> [{color:#ff}http://svn.apache.org/repos/asf/vcl/trunk/doap_vcl.rdf{color}]
>  
> Possible Fix : scripts/cronjob/parsecommitteeinfo.py to manage character case.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-301) No tasks found when searching Help Wanted

[JIRA]

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

Hervé Boutemy commented on COMDEV-301:
--

Hi [~humbedooh], looks like Help Wanted database content was lost...
is there any backup?

> No tasks found when searching Help Wanted
> -
>
> Key: COMDEV-301
> URL: https://issues.apache.org/jira/browse/COMDEV-301
> Project: Community Development
>  Issue Type: Bug
>  Components: Help Wanted
>Reporter: Eyal Allweil
>Priority: Major
>
> If you search for tasks in Help Wanted (specifically, I searched for Java 
> tasks) none are found. (there were a couple dozen the last time I checked, 
> and I put in a few that definitely haven't been closed)
>  
> To reproduce:
> 1) Go to [Help Wanted|https://helpwanted.apache.org/].
> 2) Click "I want to help out!"
> 3) Click "Programming and Development"
> 4) Select "Java" and click the "Find me something to do" button
>  
> UPDATE: It appears that the elastic search with all the old tasks has been 
> erased, because when I add a new task it's visible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (COMDEV-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor

[Jira]

Nicolás Vázquez created COMDEV-483:
--

 Summary: CloudStack GSoC 2023 - Extend Import-Export Instances to 
the KVM Hypervisor
 Key: COMDEV-483
 URL: https://issues.apache.org/jira/browse/COMDEV-483
 Project: Community Development
  Issue Type: New Feature
Reporter: Nicolás Vázquez


Github issue: [https://github.com/apache/cloudstack/issues/7127]

 

Description:

The Import-Export functionality is only allowed for the Vmware hypervisor. The 
functionality is developed within a VM ingestion framework that allows the 
extension to other hypervisors. The Import-Export functionality consists on few 
APIs and the UI to interact with them:
 * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in 
CloudStack but existing on the hypervisor side)
 * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this 
implies populating the database with the corresponding data)
 * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it on 
the hypervisor side

The complexity on KVM should be parsing the existing XML domains into different 
resources and map them in CloudStack to populate the database correctly.



--
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-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor

[Jira]

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

Nicolás Vázquez updated COMDEV-483:
---
Component/s: GSoC/Mentoring ideas

> CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor
> ---
>
> Key: COMDEV-483
> URL: https://issues.apache.org/jira/browse/COMDEV-483
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Nicolás Vázquez
>Priority: Major
>  Labels: gsoc2023
>
> Github issue: [https://github.com/apache/cloudstack/issues/7127]
>  
> Description:
> The Import-Export functionality is only allowed for the Vmware hypervisor. 
> The functionality is developed within a VM ingestion framework that allows 
> the extension to other hypervisors. The Import-Export functionality consists 
> on few APIs and the UI to interact with them:
>  * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in 
> CloudStack but existing on the hypervisor side)
>  * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this 
> implies populating the database with the corresponding data)
>  * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it 
> on the hypervisor side
> The complexity on KVM should be parsing the existing XML domains into 
> different resources and map them in CloudStack to populate the database 
> correctly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Closed] (COMDEV-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor

[Jira]

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

Nicolás Vázquez closed COMDEV-483.
--
Resolution: Invalid

> CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor
> ---
>
> Key: COMDEV-483
> URL: https://issues.apache.org/jira/browse/COMDEV-483
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Nicolás Vázquez
>Priority: Major
>  Labels: gsoc2023
>
> Github issue: [https://github.com/apache/cloudstack/issues/7127]
>  
> Description:
> The Import-Export functionality is only allowed for the Vmware hypervisor. 
> The functionality is developed within a VM ingestion framework that allows 
> the extension to other hypervisors. The Import-Export functionality consists 
> on few APIs and the UI to interact with them:
>  * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in 
> CloudStack but existing on the hypervisor side)
>  * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this 
> implies populating the database with the corresponding data)
>  * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it 
> on the hypervisor side
> The complexity on KVM should be parsing the existing XML domains into 
> different resources and map them in CloudStack to populate the database 
> correctly.



--
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-483) CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor

[Jira]

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

Nicolás Vázquez commented on COMDEV-483:


HI [~solomax] I had initially created under the Comdev project instead of 
CloudStack, closed it in favour of: 
https://issues.apache.org/jira/browse/CLOUDSTACK-10456

> CloudStack GSoC 2023 - Extend Import-Export Instances to the KVM Hypervisor
> ---
>
> Key: COMDEV-483
> URL: https://issues.apache.org/jira/browse/COMDEV-483
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Nicolás Vázquez
>Priority: Major
>  Labels: gsoc2023
>
> Github issue: [https://github.com/apache/cloudstack/issues/7127]
>  
> Description:
> The Import-Export functionality is only allowed for the Vmware hypervisor. 
> The functionality is developed within a VM ingestion framework that allows 
> the extension to other hypervisors. The Import-Export functionality consists 
> on few APIs and the UI to interact with them:
>  * listUnmanagedInstances: Lists unmanaged virtual machines (not existing in 
> CloudStack but existing on the hypervisor side)
>  * importUnmanagedInstance: Import an unmanaged VM into CloudStack (this 
> implies populating the database with the corresponding data)
>  * unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it 
> on the hypervisor side
> The complexity on KVM should be parsing the existing XML domains into 
> different resources and map them in CloudStack to populate the database 
> correctly.



--
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-481) Projects tool "Projects by number of committers" lacks many projects

[Jira]

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

Jan Høydahl updated COMDEV-481:
---
Description: 
This page ([https://projects.apache.org/projects.html?number)] only lists 179 
projects, and turns out those are only the ones that happen to have the same 
unixgroup as project-ID. E.g. 'lucene-core' with 97 committers is not listed 
since its unixgroup is 'lucene'.

The fix is in the attached patch, applying the same projectId-to-unixgroup 
function as is used elsewhere in the same script. This brings the number of 
projects listed up to 377.

I agree with some of the comments in related issue COMDEV-170, that some 
projects may have committership != unixgroup, but that should be solved 
separately.

  was:
This page only lists 179 projects, and turns out those are only the ones that 
happen to have the same unixgroup as project-ID. E.g. 'lucene-core' with 97 
committers is not listed since its unixgroup is 'lucene'.

The fix is in the attached patch, applying the same projectId-to-unixgroup 
function as is used elsewhere in the same script. This brings the number of 
projects listed up to 377.

I agree with some of the comments in related issue COMDEV-170, that some 
projects may have committership != unixgroup, but that should be solved 
separately.


> Projects tool "Projects by number of committers" lacks many projects
> 
>
> Key: COMDEV-481
> URL: https://issues.apache.org/jira/browse/COMDEV-481
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: comdev-projects_js.patch
>
>
> This page ([https://projects.apache.org/projects.html?number)] only lists 179 
> projects, and turns out those are only the ones that happen to have the same 
> unixgroup as project-ID. E.g. 'lucene-core' with 97 committers is not listed 
> since its unixgroup is 'lucene'.
> The fix is in the attached patch, applying the same projectId-to-unixgroup 
> function as is used elsewhere in the same script. This brings the number of 
> projects listed up to 377.
> I agree with some of the comments in related issue COMDEV-170, that some 
> projects may have committership != unixgroup, but that should be solved 
> separately.



--
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-481) Projects tool "Projects by number of committers" lacks many projects

[Jira]

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

Jan Høydahl commented on COMDEV-481:


Hi, any thoughts on this bug?

> Projects tool "Projects by number of committers" lacks many projects
> 
>
> Key: COMDEV-481
> URL: https://issues.apache.org/jira/browse/COMDEV-481
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: comdev-projects_js.patch
>
>
> This page ([https://projects.apache.org/projects.html?number)] only lists 179 
> projects, and turns out those are only the ones that happen to have the same 
> unixgroup as project-ID. E.g. 'lucene-core' with 97 committers is not listed 
> since its unixgroup is 'lucene'.
> The fix is in the attached patch, applying the same projectId-to-unixgroup 
> function as is used elsewhere in the same script. This brings the number of 
> projects listed up to 377.
> I agree with some of the comments in related issue COMDEV-170, that some 
> projects may have committership != unixgroup, but that should be solved 
> separately.



--
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-481) Projects tool "Projects by number of committers" lacks many projects

[Jira]

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

Jan Høydahl resolved COMDEV-481.

Resolution: Fixed

Verified that it works

> Projects tool "Projects by number of committers" lacks many projects
> 
>
> Key: COMDEV-481
> URL: https://issues.apache.org/jira/browse/COMDEV-481
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: comdev-projects_js.patch
>
>
> This page ([https://projects.apache.org/projects.html?number)] only lists 179 
> projects, and turns out those are only the ones that happen to have the same 
> unixgroup as project-ID. E.g. 'lucene-core' with 97 committers is not listed 
> since its unixgroup is 'lucene'.
> The fix is in the attached patch, applying the same projectId-to-unixgroup 
> function as is used elsewhere in the same script. This brings the number of 
> projects listed up to 377.
> I agree with some of the comments in related issue COMDEV-170, that some 
> projects may have committership != unixgroup, but that should be solved 
> separately.



--
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-481) Projects tool "Projects by number of committers" lacks many projects

[Jira]

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

Jan Høydahl commented on COMDEV-481:


Thanks. Looks smashing :) 

> Projects tool "Projects by number of committers" lacks many projects
> 
>
> Key: COMDEV-481
> URL: https://issues.apache.org/jira/browse/COMDEV-481
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: comdev-projects_js.patch
>
>
> This page ([https://projects.apache.org/projects.html?number)] only lists 179 
> projects, and turns out those are only the ones that happen to have the same 
> unixgroup as project-ID. E.g. 'lucene-core' with 97 committers is not listed 
> since its unixgroup is 'lucene'.
> The fix is in the attached patch, applying the same projectId-to-unixgroup 
> function as is used elsewhere in the same script. This brings the number of 
> projects listed up to 377.
> I agree with some of the comments in related issue COMDEV-170, that some 
> projects may have committership != unixgroup, but that should be solved 
> separately.



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

[Jira]

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

Jan Høydahl commented on COMDEV-436:


Looks like we need to commit this fix ourselves [~houston]  :) Do all 
committers have commit bit for comdev?

> 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
>
> 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-532) Report Wizard gives "[object Response]" error with underlying 500

[Jira]

Páli Gábor created COMDEV-532:
-

 Summary: 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: Mac/FF
Reporter: Páli Gábor


As reported elsewhere, navigating to [https://reporter.apache.org/wizard/] pops 
up a notification error, and does nothing else.

Console shows an underlying 503:
/*** ASF Board Report Wizard initializing / 
[wizard.js:1792:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
Fetching JSON resource at /reportingcycles.json 
[wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
putting /reportingcycles.json in escrow... 
[wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
Successfully fetched /reportingcycles.json 
[wizard.js:119:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
Fetching JSON resource at /api/overview 
[wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
putting /api/overview in escrow... 
[wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
URL /api/overview returned HTTP code 503, snapping! 
[wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (COMDEV-532) Report Wizard gives "[object Response]" error with underlying 500

[Jira]

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

Páli Gábor updated COMDEV-532:
--
Description: 
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!
 

  was:
As reported elsewhere, navigating to [https://reporter.apache.org/wizard/] pops 
up a notification error, and does nothing else.

Console shows an underlying 503:
/*** ASF Board Report Wizard initializing / 
[wizard.js:1792:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
Fetching JSON resource at /reportingcycles.json 
[wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
putting /reportingcycles.json in escrow... 
[wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
Successfully fetched /reportingcycles.json 
[wizard.js:119:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
Fetching JSON resource at /api/overview 
[wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
putting /api/overview in escrow... 
[wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
URL /api/overview returned HTTP code 503, snapping! 
[wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]


> 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: Mac/FF
>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!
>  



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

[Jira]

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

Páli Gábor updated COMDEV-532:
--
Description: 
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]
 

  was:
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!
 


> 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: Mac/FF
>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] [Updated] (COMDEV-532) Report Wizard gives "[object Response]" error with underlying 500

[Jira]

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

Páli Gábor updated COMDEV-532:
--
Environment: macOS Ventura 13.4.1 (c), Firefox 116.0.3 (64-bit)  (was: 
Mac/FF)

> 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] [Updated] (COMDEV-532) Report Wizard gives "[object Response]" error with underlying 500

[Jira]

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

Páli Gábor updated COMDEV-532:
--
Description: 
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]
 

  was:
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]
 


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



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

[Jira]

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

Páli Gábor updated COMDEV-532:
--
Description: 
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.

  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]
 


> 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

[Jira]

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

Páli Gábor commented on COMDEV-532:
---

Thanks for checking [~sebb].  The site still gives me the same response with 
Firefox, Chrome, and Safari as well.  [https://reporter.apache.org/wizard/] is 
fine, the issue happens only when I append a project name, such as 
[https://reporter.apache.org/wizard/?couchdb] .  It might be because I am not 
on CouchDB PMC.

> 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] [Comment Edited] (COMDEV-532) Report Wizard gives "[object Response]" error with underlying 500

[Jira]

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

Páli Gábor edited comment on COMDEV-532 at 8/26/23 11:43 PM:
-

Curiously, it worked for me on Thursday (August 24, ~22:10 CEST).


was (Author: JIRAUSER301974):
Curiously, it worked for on Thursday (August 24, ~22:10 CEST).

> 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

[Jira]

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

Páli Gábor commented on COMDEV-532:
---

Curiously, it worked for on Thursday (August 24, ~22:10 CEST).

> 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

[Jira]

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

Páli Gábor commented on COMDEV-532:
---

Sorry, I was editing the description left and right...  That is why you 
probably did not see the extra information I provided.  Either way it goes, now 
the site has healed for me and I can access the report skeleton 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/]
>  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] [Created] (COMDEV-533) Inconsistency in membership data (CouchDB)

[Jira]

Páli Gábor created COMDEV-533:
-

 Summary: 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


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] [Comment Edited] (COMDEV-533) Inconsistency in membership data (CouchDB)

[Jira]

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

Páli Gábor edited comment on COMDEV-533 at 8/27/23 12:46 PM:
-

Thanks for the quick reply [~Sebb]!  Could you please tell me where I can find 
this {{committee-info.txt}} file?  Is this something that only PMC members can 
modify?


was (Author: JIRAUSER301974):
Thanks for the quick reply [~Sebb]!  Could you please tell me where I can find 
this {{committee-info.txt}} file?  Is this something that PMC member can modify 
only?

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

[Jira]

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

Páli Gábor commented on COMDEV-533:
---

Thanks for the quick reply [~Sebb]!  Could you please tell me where I can find 
this {{committee-info.txt}} file?  Is this something that PMC member can modify 
only?

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

[Jira]

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

Páli Gábor commented on COMDEV-533:
---

Excellent, thank you.  I will notify CouchDB PMC about this.

> 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] [Updated] (COMDEV-425) Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project

[Jira]

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

Jan Høydahl updated COMDEV-425:
---
Attachment: COMDEV-425.patch

> Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project
> --
>
> Key: COMDEV-425
> URL: https://issues.apache.org/jira/browse/COMDEV-425
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Michael McCandless
>Priority: Minor
> Attachments: COMDEV-425.patch, Screen Shot 2021-09-09 at 5.34.16 
> PM.png, Screen Shot 2021-10-21 at 8.55.58 AM.png, 
> image-2021-10-21-08-56-15-016.png, lucene-kibble.png
>
>
> I am working on the quarterly board report for Apache Lucene, and noticed 
> under the "Community Health" section that the "Busiest GitHub topics" seems 
> to be missing the "lucene" GitHub repository.
> It seems to contain only {{lucene-solr}}, {{lucenenet}}, {{lucene-site}}.
> Likely something needs to be updated because Solr split out of Lucene, and 
> Lucene's main (to be 9.0 release soon) branch is on a new(-ish) {{lucene}} 
> repository: [https://github.com/apache/lucene]
> !Screen Shot 2021-09-09 at 5.34.16 PM.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (COMDEV-425) Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project

[Jira]

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

Jan Høydahl commented on COMDEV-425:


I filed PR [https://github.com/apache/comdev-projects/pull/3] - not for the 
reporter but similar bug in bottom of 
[https://projects.apache.org/committee.html?lucene] where lucenenet repos show 
up.

> Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project
> --
>
> Key: COMDEV-425
> URL: https://issues.apache.org/jira/browse/COMDEV-425
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Michael McCandless
>Priority: Minor
> Attachments: COMDEV-425.patch, Screen Shot 2021-09-09 at 5.34.16 
> PM.png, Screen Shot 2021-10-21 at 8.55.58 AM.png, 
> image-2021-10-21-08-56-15-016.png, lucene-kibble.png
>
>
> I am working on the quarterly board report for Apache Lucene, and noticed 
> under the "Community Health" section that the "Busiest GitHub topics" seems 
> to be missing the "lucene" GitHub repository.
> It seems to contain only {{lucene-solr}}, {{lucenenet}}, {{lucene-site}}.
> Likely something needs to be updated because Solr split out of Lucene, and 
> Lucene's main (to be 9.0 release soon) branch is on a new(-ish) {{lucene}} 
> repository: [https://github.com/apache/lucene]
> !Screen Shot 2021-09-09 at 5.34.16 PM.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (COMDEV-425) Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project

[Jira]

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

Jan Høydahl commented on COMDEV-425:


I had a look at the reporter scripts and found 
[kibble.py|http://svn.apache.org/viewvc/comdev/reporter.apache.org/trunk/scripts/rapp/kibble.py?view=markup]
 which seems to have a regex bug, including all github repos with same prefix,  
e.g lucene matches lucenenet. Uploaded a patch in [^COMDEV-425.patch]

> Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project
> --
>
> Key: COMDEV-425
> URL: https://issues.apache.org/jira/browse/COMDEV-425
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Michael McCandless
>Priority: Minor
> Attachments: COMDEV-425.patch, Screen Shot 2021-09-09 at 5.34.16 
> PM.png, Screen Shot 2021-10-21 at 8.55.58 AM.png, 
> image-2021-10-21-08-56-15-016.png, lucene-kibble.png
>
>
> I am working on the quarterly board report for Apache Lucene, and noticed 
> under the "Community Health" section that the "Busiest GitHub topics" seems 
> to be missing the "lucene" GitHub repository.
> It seems to contain only {{lucene-solr}}, {{lucenenet}}, {{lucene-site}}.
> Likely something needs to be updated because Solr split out of Lucene, and 
> Lucene's main (to be 9.0 release soon) branch is on a new(-ish) {{lucene}} 
> repository: [https://github.com/apache/lucene]
> !Screen Shot 2021-09-09 at 5.34.16 PM.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (COMDEV-436) parsereleases produces false releases for solr

[Jira]

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

Jan Høydahl updated COMDEV-436:
---
Attachment: COMDEV-436.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
>
>
> 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] [Updated] (COMDEV-436) parsereleases produces false releases for solr

[Jira]

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

Jan Høydahl updated COMDEV-436:
---
Attachment: releases.json

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

[Jira]

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

Jan Høydahl commented on COMDEV-436:


Uploaded a patch [^COMDEV-436.patch]

I ran the patched script locally and got the attached [^releases.json] file as 
result, and it looks good. Solr section looks like
{code:java}
"solr": {
  "solr-0.7.1": "2023-07-17",
  "solr-9.3.0": "2023-07-17",
  "solr-9.3.0-slim": "2023-07-17",
  "solr-operator-0.7.1": "2023-07-17",
  "solr-operator-v0.7.1": "2023-07-17"
} {code}
It's a bit sad that "solr-0.7.1" (solr helm chart) has the same prefix as the 
main solr release. 

Also, we have both a "solr-operator-0.7.1" (helm chart) and 
"solr-operator-v0.7.1" (operator binaries). Not much to do with it unless there 
is some hierarchy in the JSON and some standard way of detecting file types. 
But the input of the script is simply a bunch of download folders and files, so 
not easy,

> 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
>
>
> 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] [Updated] (COMDEV-436) parsereleases produces false releases for solr

[Jira]

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

Jan Høydahl updated COMDEV-436:
---
Description: 
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}

  was:
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}


> 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

[Jira]

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

Jan Høydahl commented on COMDEV-436:


Thanks. Solr release section still looks ok. Except the inclusion of two helm 
charts that are not official source releases of the project (solr-0.7.1 and 
solr-operator-0.7.1), see 
[https://downloads.apache.org/solr/solr-operator/v0.7.1/helm-charts/]

I suppose, if we required {{-src}} tgz files next to the convenience binaries, 
we could use that to weed these out. Or perhaps we should stop uploading our 
helm charts to the download area?

> 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

[Jira]

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

Jan Høydahl commented on COMDEV-436:


I suppose we're good for now and this issue can be closed if you want.

PS: Could not this releases.json file be generated from DOAP files instead?

> 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-561) migrate projects to Git

[Jira]

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

Hervé Boutemy commented on COMDEV-561:
--

I don't have access to the machine, I don't know how I can concretely help
but I see that content commit is centralized in 
https://github.com/apache/comdev-projects/blob/trunk/scripts/cronjobs/svnadd.sh 
, it should clearly help change the source control system

on authentication, on one of my personal projects, I do some commits from a 
script on a server with GitHub using a GH token that is stored in ~ 
/.gitcredentials
nothing that seems very complex: I just can't tell how my manual machin config 
case would fit in projects case with some part in Puppet and perhaps some other 
on the machine, I don't really know how that's done in svn

what I know is that Git PR would be so useful to continue team working, instead 
of direct svn commit with email discussions on -1...
that's why I'm begging for update, no idea how to act myself

> migrate projects to Git
> ---
>
> Key: COMDEV-561
> URL: https://issues.apache.org/jira/browse/COMDEV-561
> Project: Community Development
>  Issue Type: Improvement
>  Components: Projects Tool
>Reporter: Hervé Boutemy
>Priority: Major
>
> in COMDEV-288, we let the source code in svn but created a svn2git Git mirror 
> https://github.com/apache/comdev-projects
> next step is to make Git read-write
> full impact analysis to be done, but we can immediately list a few topics:
> - cronjobs update to commit to Git instead of svn
> - switch to ASF website publication from Git instead of svn (probably through 
> .asf.yaml)
> anything else?



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

[Jira]

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

Hervé Boutemy commented on COMDEV-534:
--

https://lists.apache.org/thread/stf2n8nc4spv9x9jkz4ofrphtvqt4gow
replacing with Apache ECharts https://echarts.apache.org/

> 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] [Closed] (COMDEV-560) projects list is inconsistent between UI and generated .json file: missing no-tlp-doap in json

[Jira]

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

Hervé Boutemy closed COMDEV-560.

Resolution: Fixed

> projects list is inconsistent between UI and generated .json file: missing 
> no-tlp-doap in json
> --
>
> Key: COMDEV-560
> URL: https://issues.apache.org/jira/browse/COMDEV-560
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
>
> while working on https://github.com/apache/tooling-trusted-release/issues/117
> we discovered that projects's list in UI = 
> https://projects.apache.org/projects.html
> is not consistent with list in .json = 
> https://projects.apache.org/json/foundation/projects.json
> json does not contain no-tlp-doap category = 
> https://projects.apache.org/projects.html?category#no-tlp-doap
> this auto-generated minimal project description for committees that did not 
> write a DOAP file for their TLP should be consistent



--
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-560) projects list is inconsistent between UI and generated .json file: missing no-tlp-doap in json

[Jira]

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

Hervé Boutemy commented on COMDEV-560:
--

done in 
https://github.com/apache/comdev-projects/commit/d70af06164ccd18dbb2d3626a625979be7caf339

now these auto-generated projects from committees that did not declare any 
projects are stored in projects.json: no need to do the same magic in js

> projects list is inconsistent between UI and generated .json file: missing 
> no-tlp-doap in json
> --
>
> Key: COMDEV-560
> URL: https://issues.apache.org/jira/browse/COMDEV-560
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
>
> while working on https://github.com/apache/tooling-trusted-release/issues/117
> we discovered that projects's list in UI = 
> https://projects.apache.org/projects.html
> is not consistent with list in .json = 
> https://projects.apache.org/json/foundation/projects.json
> json does not contain no-tlp-doap category = 
> https://projects.apache.org/projects.html?category#no-tlp-doap
> this auto-generated minimal project description for committees that did not 
> write a DOAP file for their TLP should be consistent



--
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-563) publish DOAP validation WARN

[Jira]

Hervé Boutemy created COMDEV-563:


 Summary: publish DOAP validation WARN
 Key: COMDEV-563
 URL: https://issues.apache.org/jira/browse/COMDEV-563
 Project: Community Development
  Issue Type: New Feature
  Components: Projects Tool
Reporter: Hervé Boutemy


working on COMDEV-560, I ran for the first time since a long time ago 
parseprojects.py that parses and checks DOAP files

I was was surprised to see a lot of WARN that looked interesting

we need an approach:
1. to make these visible
2. to communicate with project in charge of the affected DOAP

and anticipate that some committees will need help, and perhaps evolution of 
our DOAP conventions (like for example the list of languages and categories)



--
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-561) migrate projects to Git

[Jira]

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

Hervé Boutemy commented on COMDEV-561:
--

want to help or want to block?

> migrate projects to Git
> ---
>
> Key: COMDEV-561
> URL: https://issues.apache.org/jira/browse/COMDEV-561
> Project: Community Development
>  Issue Type: Improvement
>  Components: Projects Tool
>Reporter: Hervé Boutemy
>Priority: Major
>
> in COMDEV-288, we let the source code in svn but created a svn2git Git mirror 
> https://github.com/apache/comdev-projects
> next step is to make Git read-write
> full impact analysis to be done, but we can immediately list a few topics:
> - cronjobs update to commit to Git instead of svn
> - switch to ASF website publication from Git instead of svn (probably through 
> .asf.yaml)
> anything else?



--
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-561) migrate projects to Git

[Jira]

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

Hervé Boutemy commented on COMDEV-561:
--

with ATR going forward and promoting declaring every software project released 
at Apache, if we do it well, these projects will be declared with DOAP for 
projects.a.o to have a more realistic view than what is displayed for 20 years 
(that was "as complete as possible")
I'm convinced that our 200 Committees are releasing more something like 2000+ 
projects than the current 300
=> clearly we'll have a bunch of work in projects.a.o to manage that growth and 
adapt our approach

I think svn will be a strong problem to push p.a.o collaboration from all ASF 
committers

we need to switch to Git
[~sebb] how do you want us to work on it? I don't have access to the underlying 
machine = what restricts me on doing anything without breaking
should I start by getting ssh access to be able to help on the migration?
[~humbedooh] is there anything I should do to be able to see this machine 
running? (I know updating is done by Puppet, so I expect only being able to 
debug if anything does not work as I expect)

> migrate projects to Git
> ---
>
> Key: COMDEV-561
> URL: https://issues.apache.org/jira/browse/COMDEV-561
> Project: Community Development
>  Issue Type: Improvement
>  Components: Projects Tool
>Reporter: Hervé Boutemy
>Priority: Major
>
> in COMDEV-288, we let the source code in svn but created a svn2git Git mirror 
> https://github.com/apache/comdev-projects
> next step is to make Git read-write
> full impact analysis to be done, but we can immediately list a few topics:
> - cronjobs update to commit to Git instead of svn
> - switch to ASF website publication from Git instead of svn (probably through 
> .asf.yaml)
> anything else?



--
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-561) migrate projects to Git

[Jira]

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

Hervé Boutemy commented on COMDEV-561:
--

usual nitpicking: projects.a.o is not "everything has to be DOAP", but "we 
consolidate data about software projects" whatever the format and the location
and we try it to be a place where everybody wants to contribute

I'll work on moving forward

> migrate projects to Git
> ---
>
> Key: COMDEV-561
> URL: https://issues.apache.org/jira/browse/COMDEV-561
> Project: Community Development
>  Issue Type: Improvement
>  Components: Projects Tool
>Reporter: Hervé Boutemy
>Priority: Major
>
> in COMDEV-288, we let the source code in svn but created a svn2git Git mirror 
> https://github.com/apache/comdev-projects
> next step is to make Git read-write
> full impact analysis to be done, but we can immediately list a few topics:
> - cronjobs update to commit to Git instead of svn
> - switch to ASF website publication from Git instead of svn (probably through 
> .asf.yaml)
> anything else?



--
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-321) incubator-netbeans on Project Statistics page

[Sebb (JIRA)]

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

Sebb commented on COMDEV-321:
-

The code is here:

https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/site/

Looking at statistics.html suggests this is all produced by Snoot so you 
probably need to contact them.

> incubator-netbeans on Project Statistics page
> -
>
> Key: COMDEV-321
> URL: https://issues.apache.org/jira/browse/COMDEV-321
> Project: Community Development
>  Issue Type: Bug
>Reporter: Geertjan Wielenga
>Priority: Minor
>
> 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
(v7.6.3#76005)

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

[jira] [Resolved] (COMDEV-321) incubator-netbeans on Project Statistics page

[Sebb (JIRA)]

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

Sebb resolved COMDEV-321.
-
Resolution: Duplicate

No point having both issues open

> incubator-netbeans on Project Statistics page
> -
>
> Key: COMDEV-321
> URL: https://issues.apache.org/jira/browse/COMDEV-321
> Project: Community Development
>  Issue Type: Bug
>Reporter: Geertjan Wielenga
>Priority: Minor
>
> 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
(v7.6.3#76005)

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

[jira] [Created] (COMDEV-323) Not clear how to raise issues with Snoot data (statistics.html)

[Sebb (JIRA)]

Sebb created COMDEV-323:
---

 Summary: Not clear how to raise issues with Snoot data 
(statistics.html)
 Key: COMDEV-323
 URL: https://issues.apache.org/jira/browse/COMDEV-323
 Project: Community Development
  Issue Type: Bug
  Components: Projects Tool
Reporter: Sebb


The statistics.html page gets its data from snoot.io.
It's not clear whom to contact if there are any queries on/issues with the data.

When known, this info should be added to the statistics page and/or the About 
page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Resolved] (COMDEV-323) Not clear how to raise issues with Snoot data (statistics.html)

[Sebb (JIRA)]

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

Sebb resolved COMDEV-323.
-
Resolution: Fixed

Info added to site

> Not clear how to raise issues with Snoot data (statistics.html)
> ---
>
> Key: COMDEV-323
> URL: https://issues.apache.org/jira/browse/COMDEV-323
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Sebb
>Priority: Major
>
> The statistics.html page gets its data from snoot.io.
> It's not clear whom to contact if there are any queries on/issues with the 
> data.
> When known, this info should be added to the statistics page and/or the About 
> page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-322) incubator-netbeans on Project Statistics page

[Sebb (JIRA)]

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

Sebb updated COMDEV-322:

Component/s: Projects Tool

> 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
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-322) incubator-netbeans on Project Statistics page

[Sebb (JIRA)]

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

Sebb commented on COMDEV-322:
-

See COMDEV-323 for how to raise issues with the data

> 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: 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
(v7.6.3#76005)

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

[jira] [Reopened] (COMDEV-323) Not clear how to raise issues with Snoot data (statistics.html)

[Sebb (JIRA)]

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

Sebb reopened COMDEV-323:
-
  Assignee: Daniel Gruno

Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
:
195.201.103.244 does not like recipient.

> Not clear how to raise issues with Snoot data (statistics.html)
> ---
>
> Key: COMDEV-323
> URL: https://issues.apache.org/jira/browse/COMDEV-323
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Sebb
>Assignee: Daniel Gruno
>Priority: Major
>
> The statistics.html page gets its data from snoot.io.
> It's not clear whom to contact if there are any queries on/issues with the 
> data.
> When known, this info should be added to the statistics page and/or the About 
> page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-323) Not clear how to raise issues with Snoot data (statistics.html)

[Sebb (JIRA)]

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

Sebb commented on COMDEV-323:
-

The comment on press@ suggests that it is not the place [1] for queries about 
Snoot.
Is there another ASF mailing list or other resource that should be used to 
track issues?

[1] 
https://lists.apache.org/thread.html/bdf49089135d90ab3e7ac2cc85ef116bcfe093b32292591236fef814@%3Cpress.apache.org%3E

> Not clear how to raise issues with Snoot data (statistics.html)
> ---
>
> Key: COMDEV-323
> URL: https://issues.apache.org/jira/browse/COMDEV-323
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Sebb
>Assignee: Daniel Gruno
>Priority: Major
>
> The statistics.html page gets its data from snoot.io.
> It's not clear whom to contact if there are any queries on/issues with the 
> data.
> When known, this info should be added to the statistics page and/or the About 
> page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-323) Not clear how to raise issues with Snoot data (statistics.html)

[Sebb (JIRA)]

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

Sebb commented on COMDEV-323:
-

[~humbedooh] I think you were the person who created the page originally. So 
who set up the monitoring with snoot.io?

> Not clear how to raise issues with Snoot data (statistics.html)
> ---
>
> Key: COMDEV-323
> URL: https://issues.apache.org/jira/browse/COMDEV-323
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Sebb
>Assignee: Daniel Gruno
>Priority: Major
>
> The statistics.html page gets its data from snoot.io.
> It's not clear whom to contact if there are any queries on/issues with the 
> data.
> When known, this info should be added to the statistics page and/or the About 
> page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (COMDEV-324) IOS app crashes on multiple upload of files

[mehthab (JIRA)]

mehthab created COMDEV-324:
--

 Summary: IOS app crashes on multiple upload of files
 Key: COMDEV-324
 URL: https://issues.apache.org/jira/browse/COMDEV-324
 Project: Community Development
  Issue Type: Bug
 Environment: -IOS
-Reactjs and Redux
 
Reporter: mehthab


IOS app crashes when uploading multiple file(especially those captured in iOS 
camera).

i created the Cordova project using

-Reactjs and Redux

-Axios for server calls

the App crashes when there is too much to sent to server side.for eg: App 
crashed when i upload more than 10 photos at time, but wont have any issue when 
uploading less than 8 photos.

in Xcode its showing there is a memory pressure and app gets crashed.

So i don't know how to debug this, tried to cut down memory leak by reducing 
the loops.

but still no hope

has anyone had the same issue or do you guys know how to solve it?

--



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-324) IOS app crashes on multiple upload of files

[mehthab (JIRA)]

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

mehthab updated COMDEV-324:
---
Issue Type: Question  (was: Bug)

> IOS app crashes on multiple upload of files
> ---
>
> Key: COMDEV-324
> URL: https://issues.apache.org/jira/browse/COMDEV-324
> Project: Community Development
>  Issue Type: Question
> Environment: -IOS
> -Reactjs and Redux
>  
>Reporter: mehthab
>Priority: Critical
>
> IOS app crashes when uploading multiple file(especially those captured in iOS 
> camera).
> i created the Cordova project using
> -Reactjs and Redux
> -Axios for server calls
> the App crashes when there is too much to sent to server side.for eg: App 
> crashed when i upload more than 10 photos at time, but wont have any issue 
> when uploading less than 8 photos.
> in Xcode its showing there is a memory pressure and app gets crashed.
> So i don't know how to debug this, tried to cut down memory leak by reducing 
> the loops.
> but still no hope
> has anyone had the same issue or do you guys know how to solve it?
> --



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-324) IOS app crashes on multiple upload of files

[mehthab (JIRA)]

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

mehthab updated COMDEV-324:
---
Labels: cordova ios reactjs redux  (was: )

> IOS app crashes on multiple upload of files
> ---
>
> Key: COMDEV-324
> URL: https://issues.apache.org/jira/browse/COMDEV-324
> Project: Community Development
>  Issue Type: Question
> Environment: -IOS
> -Reactjs and Redux
>  
>Reporter: mehthab
>Priority: Critical
>  Labels: cordova, ios, reactjs, redux
>
> IOS app crashes when uploading multiple file(especially those captured in iOS 
> camera).
> i created the Cordova project using
> -Reactjs and Redux
> -Axios for server calls
> the App crashes when there is too much to sent to server side.for eg: App 
> crashed when i upload more than 10 photos at time, but wont have any issue 
> when uploading less than 8 photos.
> in Xcode its showing there is a memory pressure and app gets crashed.
> So i don't know how to debug this, tried to cut down memory leak by reducing 
> the loops.
> but still no hope
> has anyone had the same issue or do you guys know how to solve it?
> --



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-324) IOS app crashes on multiple upload of files

[mehthab (JIRA)]

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

mehthab commented on COMDEV-324:


[~solomax] hi, actually im new this apache issues. 

Sorry, i didn't understand what you mentioned above.

i couldn't see anything to in that link you shared above.

can you clarify it more.

thanks

> IOS app crashes on multiple upload of files
> ---
>
> Key: COMDEV-324
> URL: https://issues.apache.org/jira/browse/COMDEV-324
> Project: Community Development
>  Issue Type: Question
> Environment: -IOS
> -Reactjs and Redux
>  
>Reporter: mehthab
>Priority: Critical
>  Labels: cordova, ios, reactjs, redux
>
> IOS app crashes when uploading multiple file(especially those captured in iOS 
> camera).
> i created the Cordova project using
> -Reactjs and Redux
> -Axios for server calls
> the App crashes when there is too much to sent to server side.for eg: App 
> crashed when i upload more than 10 photos at time, but wont have any issue 
> when uploading less than 8 photos.
> in Xcode its showing there is a memory pressure and app gets crashed.
> So i don't know how to debug this, tried to cut down memory leak by reducing 
> the loops.
> but still no hope
> has anyone had the same issue or do you guys know how to solve it?
> --



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-324) IOS app crashes on multiple upload of files

[mehthab (JIRA)]

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

mehthab commented on COMDEV-324:


thanks [~solomax] and [~swapnilmmane]

il switch this issue to cordova

> IOS app crashes on multiple upload of files
> ---
>
> Key: COMDEV-324
> URL: https://issues.apache.org/jira/browse/COMDEV-324
> Project: Community Development
>  Issue Type: Question
> Environment: -IOS
> -Reactjs and Redux
>  
>Reporter: mehthab
>Priority: Critical
>  Labels: cordova, ios, reactjs, redux
>
> IOS app crashes when uploading multiple file(especially those captured in iOS 
> camera).
> i created the Cordova project using
> -Reactjs and Redux
> -Axios for server calls
> the App crashes when there is too much to sent to server side.for eg: App 
> crashed when i upload more than 10 photos at time, but wont have any issue 
> when uploading less than 8 photos.
> in Xcode its showing there is a memory pressure and app gets crashed.
> So i don't know how to debug this, tried to cut down memory leak by reducing 
> the loops.
> but still no hope
> has anyone had the same issue or do you guys know how to solve it?
> --



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Moved] (COMDEV-325) New "wizard" missing one of my projects...

[Sebb (JIRA)]

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

Sebb moved WHIMSY-287 to COMDEV-325:


Component/s: (was: General)
 Reporter Tool
   Workflow: classic default workflow  (was: jira)
Key: COMDEV-325  (was: WHIMSY-287)
Project: Community Development  (was: Whimsy)

> New "wizard" missing one of my projects...
> --
>
> Key: COMDEV-325
> URL: https://issues.apache.org/jira/browse/COMDEV-325
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Daniel Kulp
>Priority: Minor
> Attachments: ScreenShot.png
>
>
> The new wizard style reporter tool doesn't list all of my projects when "Your 
> projects" is selected.   In particular, it's missing one of the projects for 
> which I'm the chair.(Web Services)If I click on "show all projects", 
> it does list it there so it's a minor inconvenience.   



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[jira] [Created] (COMDEV-326) Committer invite template omits PMC role details

[Sebb (JIRA)]

Sebb created COMDEV-326:
---

 Summary: 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
 Environment: 
https://community.apache.org/newcommitter.html#committer-invite-template
Reporter: Sebb


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
(v7.6.14#76016)

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

[jira] [Resolved] (COMDEV-324) IOS app crashes on multiple upload of files

[Sebb (JIRA)]

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

Sebb resolved COMDEV-324.
-
Resolution: Invalid

See https://github.com/apache/cordova-ios/issues/634

> IOS app crashes on multiple upload of files
> ---
>
> Key: COMDEV-324
> URL: https://issues.apache.org/jira/browse/COMDEV-324
> Project: Community Development
>  Issue Type: Question
> Environment: -IOS
> -Reactjs and Redux
>  
>Reporter: mehthab
>Priority: Critical
>  Labels: cordova, ios, reactjs, redux
>
> IOS app crashes when uploading multiple file(especially those captured in iOS 
> camera).
> i created the Cordova project using
> -Reactjs and Redux
> -Axios for server calls
> the App crashes when there is too much to sent to server side.for eg: App 
> crashed when i upload more than 10 photos at time, but wont have any issue 
> when uploading less than 8 photos.
> in Xcode its showing there is a memory pressure and app gets crashed.
> So i don't know how to debug this, tried to cut down memory leak by reducing 
> the loops.
> but still no hope
> has anyone had the same issue or do you guys know how to solve it?
> --



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[jira] [Updated] (COMDEV-309) GSoC2019 Implement C++ database client adapters for Apache Arrow

[Sebb (JIRA)]

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

Sebb updated COMDEV-309:

Summary: GSoC2019 Implement C++ database client adapters for Apache Arrow  
(was: Implement C++ database client adapters for Apache Arrow)

> GSoC2019 Implement C++ database client adapters for Apache Arrow
> 
>
> Key: COMDEV-309
> URL: https://issues.apache.org/jira/browse/COMDEV-309
> Project: Community Development
>  Issue Type: Improvement
>  Components: GSoC/Mentoring ideas
>Reporter: Wes McKinney
>Priority: Major
>  Labels: gsoc2019
>
> A self contained and useful summer project would be building a bridge between 
> SQLite3 or libpq within the Arrow C++ project



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[jira] [Updated] (COMDEV-249) GSoC [RocketMQ]Message Delivery Once Semantic Implementation

[Sebb (JIRA)]

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

Sebb updated COMDEV-249:

Summary: GSoC [RocketMQ]Message Delivery Once Semantic Implementation  
(was: [RocketMQ]Message Delivery Once Semantic Implementation)

> GSoC [RocketMQ]Message Delivery Once Semantic Implementation
> 
>
> Key: COMDEV-249
> URL: https://issues.apache.org/jira/browse/COMDEV-249
> Project: Community Development
>  Issue Type: Wish
>  Components: GSoC/Mentoring ideas
>Reporter: vongosling
>Priority: Major
>
> The duplicated messages will impose the extra cost if the user needs 
> non-repeating messages.
> In most cases, the user needs to store the consumer records to determine if a 
> message is duplicated, and the store stage should guarantee consistency. So 
> we need to support a strict and non-redundant message delivery mechanism.
> In this context, we hope to design a delivery once plugin, say, you could 
> design a global(but need raft guarantee multi-copy data) storage, using the 
> hooker of RocketMQ ConsumeMessageHook to finish the task.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[jira] [Updated] (COMDEV-217) GSoc AJP client library and command line tools

[Sebb (JIRA)]

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

Sebb updated COMDEV-217:

Summary: GSoc AJP client library and command line tools  (was: AJP client 
library and command line tools)

> GSoc AJP client library and command line tools
> --
>
> Key: COMDEV-217
> URL: https://issues.apache.org/jira/browse/COMDEV-217
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Mark Thomas
>Priority: Major
>  Labels: gsoc, gsoc2017, gsoc2018
>
> Apache Tomcat supports the AJP protocol for communication between reverse 
> proxies (httpd, IIS, etc) and Tomcat. It would be useful for various purposes 
> (bug investigation, testing, load testing, etc.) to have an wget/curl/ab etc. 
> equivalent for AJP.
> A good starting point exists in the Apache JMeter project. This task is to 
> produce (probably but not necessarily starting from the JMeter code):
> - A Java library that provides AJP client functionality
> - integrate that client with JMeter
> - provide a command line wrapper for that client library
> and then use the library to (stress) test Tomcat's AJP implementations, 
> identify bugs and provide patches for those bugs.
> For the history see https://bz.apache.org/bugzilla/show_bug.cgi?id=47242



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[jira] [Updated] (COMDEV-256) GSoC Allura - importers / sync for Bitbucket and Gitlab

[Sebb (JIRA)]

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

Sebb updated COMDEV-256:

Summary: GSoC Allura - importers / sync for Bitbucket and Gitlab  (was: 
Allura - importers / sync for Bitbucket and Gitlab)

> GSoC Allura - importers / sync for Bitbucket and Gitlab
> ---
>
> Key: COMDEV-256
> URL: https://issues.apache.org/jira/browse/COMDEV-256
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Dave Brondsema
>Priority: Major
>  Labels: gsoc2018, mongodb, python
>
> Allura has a solid framework for doing imports, and has implemented this for 
> services like GitHub, Google Code and Trac.  It covers aspects from 
> Git/Hg/SVN to tickets and wikis.
> It would be great to enhance this to support importing & converting data from 
> Bitbucket and Gitlab.  The level of integration & conversion may vary 
> depending on the format and structure of the services.
> Beyond that, related improvements could be made in supporting ongoing 
> synchronization of Git/Hg/SVN repositories (not just a one-time import).  Or 
> importers for JIRA, or improving importing of Allura's own formats.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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