[jira] [Resolved] (COMDEV-557) people.json often not available (HTTP/404)
[ https://issues.apache.org/jira/browse/COMDEV-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-557. - Resolution: Information Provided > people.json often not available (HTTP/404) > -- > > Key: COMDEV-557 > URL: https://issues.apache.org/jira/browse/COMDEV-557 > Project: Community Development > Issue Type: Bug > Components: PhoneBook >Reporter: Robert Stupp >Priority: Major > > In our build of Apache Polaris, we pull > https://projects.apache.org/json/projects/polaris.json to automatically > populate the generated Maven pom's `` and enrich it with the > right roles ((P)PMC member, committer, mentor). (Gradle build script code > [here|https://github.com/apache/polaris/blob/3c5d20e8ad816362c869dc5cfc7e6186afdec747/build-logic/src/main/kotlin/publishing/configurePom.kt#L177]) > However, the people.json file is often not available (HTTP/404), in turn > causing CI failures. > [Sample CI > failure|https://github.com/apache/polaris/actions/runs/12008432969/job/33471057987?pr=475] > Would it be possible to bring the file back / have it consistently available? -- 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-545) Reporter should self-host the files from FontAwesome
[ https://issues.apache.org/jira/browse/COMDEV-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved COMDEV-545. - Resolution: Fixed > Reporter should self-host the files from FontAwesome > > > Key: COMDEV-545 > URL: https://issues.apache.org/jira/browse/COMDEV-545 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > The code current downloads fonts from FontAwsome. > We don't (and won't) have a DPA with them, so this is not allowed. > The fonts need to be hosted locally. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-562) StormCrawler Missing from 'Your Projects' on reporter.a.o after Graduation
[ https://issues.apache.org/jira/browse/COMDEV-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17975474#comment-17975474 ] Sebb commented on COMDEV-562: - [~rzo1] Is this still an issue? > StormCrawler Missing from 'Your Projects' on reporter.a.o after Graduation > -- > > Key: COMDEV-562 > URL: https://issues.apache.org/jira/browse/COMDEV-562 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Richard Zowalla >Priority: Major > Attachments: Bildschirmfoto 2025-06-04 um 20.53.18.png, > Bildschirmfoto 2025-06-04 um 20.54.09.png > > > If I logging myself into reporter.a.o, I can see three projects (OpenNLP, > TomEE, Storm). > However, I am missing StormCrawler, which graduated recently. > If I click on "All projects" (see attached image), I can see StormCrawler. > I would expect to see StormCrawler under "Your Projects". -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-562) StormCrawler Missing from 'Your Projects' on reporter.a.o after Graduation
[ https://issues.apache.org/jira/browse/COMDEV-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed COMDEV-562. -- Resolution: Fixed Seems to be fixed now. > StormCrawler Missing from 'Your Projects' on reporter.a.o after Graduation > -- > > Key: COMDEV-562 > URL: https://issues.apache.org/jira/browse/COMDEV-562 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Richard Zowalla >Priority: Major > Attachments: Bildschirmfoto 2025-06-04 um 20.53.18.png, > Bildschirmfoto 2025-06-04 um 20.54.09.png > > > If I logging myself into reporter.a.o, I can see three projects (OpenNLP, > TomEE, Storm). > However, I am missing StormCrawler, which graduated recently. > If I click on "All projects" (see attached image), I can see StormCrawler. > I would expect to see StormCrawler under "Your Projects". -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [ALC] Request to establish ALC in Taipei
Hello ALC Taipei team, Hope you are doing well, it gives immense pleasure to us to update you that the vote is passed by ComDev PMC to establish ALC Taipei Chapter and Chia-Ping Tsai as ALC Taipei Chapter lead. Here are the placeholder pages created in ComDev space https://cwiki.apache.org/confluence/display/COMDEV/ALC+Taipei https://cwiki.apache.org/confluence/display/COMDEV/ALC+Taipei+Events https://cwiki.apache.org/confluence/display/COMDEV/ALC+Taipei+Reports https://cwiki.apache.org/confluence/display/COMDEV/ALC+Taipei+Team+meeting I have yet to give edit rights to the chapter lead and team members. Please feel free to mail on the dev list to request the edit rights with your confluence ID if you are not able to edit the pages. We would also like to connect you with Ted Liu and tison. Ted Liu and tison will be with you for an initial few months to support and assist you so that you will be familiar with the processes followed by ALC Chapter for its execution. Dear Chia-Ping Tsai and team, We have the following roles and responsibilities as ALC Chapter and ALC Chapter lead: [Online version of this is available at https://s.apache.org/ALC-Chapter-Lead-RR ] 1. Making sure the 'ALC Code of Conduct (https://s.apache.org/alc-code-of-conduct )'is followed by the ALC Chapter. 2. All the events organized by the ALC Chapter are following the Guidelines to organize ALC Event ( https://s.apache.org/alc-guidelines ). 3. Chapter lead will submit the status report ( https://s.apache.org/alc-reports ) to ComDev ( dev@community.apache.org ) in every *three months* based on their reporting cycle. For ALC Taipei the reporting cycle is June, September, December, March. 4. Chapter Lead will be the point of contact for the respective ALC Chapter. If you have any queries or questions, please feel free to post on dev list. Also, here is a link to ALC Resources, it contains the information and resources (presentations, media, etc.) that will be helpful for ALC chapters. https://s.apache.org/alc-resources You can also find the base ALC logos here: https://s.apache.org/alc-branding-materials All the very best team, and thank you for showing your kind interest in this initiative. Best, tison. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
