Changes were made to project doap processing and now I get spammed with errors
once a day.
Please fix this asap or I’ll have to unsubscribe to site-...@apache.org! Why is
a Comdev process sending errors there?
Best,
Dave
Sent from my iPhone
Begin forwarded message:
> From: Projects
> Date:
Desubscribe
> Am 08.09.2023 um 21:34 schrieb Jan Høydahl :
>
>
> [
> 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 vie
[
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", ther
[
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
[
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
>
[
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
> -
Sebb created COMDEV-535:
---
Summary: parsereleases.py should not always strip -parent- from
names
Key: COMDEV-535
URL: https://issues.apache.org/jira/browse/COMDEV-535
Project: Community Development
Iss
[
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
[
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-pro
[
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
On Fri, 8 Sept 2023 at 14:17, Peter Hunsberger
wrote:
>
> You could standardize on website located data with something like:
>
> project.apache.org/doap
This has long been the suggestion, as the location is unlikely to
change - unlike repo URLs.
> using the current data format, maybe with an ext
[
https://issues.apache.org/jira/browse/COMDEV-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-302.
-
Resolution: Fixed
Fixed in r1912197
> add committe short description to committees listing
> ---
On Fri, 2023-09-08 at 15:30 +0100, sebb wrote:
> On Fri, 8 Sept 2023 at 15:10, wrote:
> >
> > On Thu, 2023-09-07 at 23:26 +0100, sebb wrote:
> > > I think it would be worth considering setting up a central store
> > > for
> > > DOAPs.
> > > This was suggested in the past, but was rejected, I thin
On Fri, 8 Sept 2023 at 15:10, wrote:
>
> On Thu, 2023-09-07 at 23:26 +0100, sebb wrote:
> > I think it would be worth considering setting up a central store for
> > DOAPs.
> > This was suggested in the past, but was rejected, I think mainly
> > because PMCs were expecting to have to make regular u
On Fri, 2023-09-08 at 07:20 -0700, Dave Fisher wrote:
> >
> > If, on the other hand, we are able to extract the frequently-
> > changing
> > stuff (ie, releases) from this data, and reduce it just to the
> > seldom-
> > changing stuff, as you suggest, this would be worth doing. It's not
> > clear
from mobile (sorry for typos ;)
On Fri, Sep 8, 2023, 21:10 wrote:
> On Thu, 2023-09-07 at 23:26 +0100, sebb wrote:
> > I think it would be worth considering setting up a central store for
> > DOAPs.
> > This was suggested in the past, but was rejected, I think mainly
> > because PMCs were expec
Sent from my iPhone
> On Sep 8, 2023, at 7:11 AM, rbo...@rcbowen.com wrote:
>
> On Thu, 2023-09-07 at 23:26 +0100, sebb wrote:
>> I think it would be worth considering setting up a central store for
>> DOAPs.
>> This was suggested in the past, but was rejected, I think mainly
>> because PMCs w
On Thu, 2023-09-07 at 23:26 +0100, sebb wrote:
> I think it would be worth considering setting up a central store for
> DOAPs.
> This was suggested in the past, but was rejected, I think mainly
> because PMCs were expecting to have to make regular updates to DOAPs,
> e.g. when releases are made, so
You could standardize on website located data with something like:
project.apache.org/doap
using the current data format, maybe with an extra layer of subproject in
there somewhere.
Even if the project frequently updates the site (including that location
for some reason) it doesn't mean you have
Please don't embed in HTML, this is Metadata that should be easily
consumable by external tools IMO.
Gary
On Fri, Sep 8, 2023, 6:28 AM Christopher wrote:
> I think many projects already have their doap files on their website, do
> that's not really improving anything. It doesn't make much diffe
On Fri, 8 Sept 2023 at 11:28, Christopher wrote:
>
> I think many projects already have their doap files on their website, do
> that's not really improving anything. It doesn't make much difference
> editing the fields embedded in HTML or in its own separate file.
It's useful to be able to submit
I think many projects already have their doap files on their website, do
that's not really improving anything. It doesn't make much difference
editing the fields embedded in HTML or in its own separate file.
On Fri, Sep 8, 2023, 05:41 Bertrand Delacretaz
wrote:
> Hi,
>
> On Fri, Sep 8, 2023 at 1
On Fri, 8 Sept 2023 at 10:41, Bertrand Delacretaz
wrote:
>
> Hi,
>
> On Fri, Sep 8, 2023 at 12:26 AM sebb wrote:
> > ...I think it would be worth considering setting up a central store for
> > DOAPs...
>
> As we require our projects to have a website anyway, wouldn't it be
> better to get that i
bdelacretaz commented on PR #128:
URL: https://github.com/apache/comdev-site/pull/128#issuecomment-1711411156
Looks good to me, thank you!
I'd just add tags to the decision making page, suggest
tags: ["pmc","governance","voting"]
--
This is an automated message from the A
Hi,
On Fri, Sep 8, 2023 at 12:26 AM sebb wrote:
> ...I think it would be worth considering setting up a central store for
> DOAPs...
As we require our projects to have a website anyway, wouldn't it be
better to get that information from the project's homepage instead of
a separate file ?
As yo
On Thu, 7 Sept 2023 at 10:17, sebb wrote:
>
> The duplicated copies of the lists have been replaced with a single JSON file:
> https://projects.apache.org/validation.json
>
> There is also a script to process that plus the list of committees
> into create.html:
> scripts/update_create.py
>
> The i
26 matches
Mail list logo
