On Fri, Oct 30, 2026, 17:44 sebb <[email protected]> wrote:

> On Fri, 30 Oct 2026 at 13:18, Rich Bowen <[email protected]> wrote:
> >
> >
> >
> > > On Oct 30, 2026, at 8:40 AM, Rich Bowen <[email protected]> wrote:
> > >
> > > Ok, I’ve pushed it out, and everything seems to be working. A few
> comments:
> > >
> > > 1) I added toggles (per PMC, and on the projects.html page) to show
> retired projects.
> > > 2) There’s some cache-buster stuff going on, because I couldn’t get
> the updated js/css to load
> > > 3) I’ve committed the .json files to svn. This should probably be a
> temporary measure, until we’re sure that the cronjobs are working
> correctly. I don’t think we want generated files in svn.
> > >
> > > Other than that, the “what’s new” in my original message should be
> accurate.
> > >
> > > https://projects.apache.org/chooser.html is still not linked
> anywhere. I’ll add that in once we’ve had some actual new folks run through
> it and deem it useful.
> > >
> > >
> > > Still to do - find projects that are still dutifully putting their
> releases into their DOAP files, and tell them they don’t need to do that
> any more.
> >
> >
> > As far as I can tell, that’s these:
> >
> > Accumulo, Ant (Ant, AntUnit, CycloneDX, Ivy, Props), APR, Arrow,
> > Axis2, Causeway, Cayenne, Commons (Daemon, Numbers, RNG, Statistics),
> > Cordova, Daffodil, FreeMarker, Hadoop, HTTP Server, Hudi, Iceberg,
> > Impala, IoTDB, Libcloud, Lucene, ManifoldCF, Maven, NetBeans, Nutch,
> > OFBiz, OpenMeetings, OpenNLP, OpenOffice, PDFBox, Pinot, PLC4X,
> > Polaris, Rivet (Tcl), Solr, Storm, Subversion, Thrift, Tika, Tomcat,
> > TsFile, Unomi, YuniKorn, Zeppelin
>
> I wonder if it would now make sense to centralize the DOAPs, rather
> than having them scattered around in project areas where they
> sometimes get lost when repos and websites are re-arranged?
>
> In the past, I know projects wanted to keep DOAPs alongside their
> code, because of the need to keep DOAPs updated.
> But that is no longer a consideration.
>
> Sebb
>

We certainly could, but I'm not sure that they're needed at all anymore.
I've talked with a handful of these projects and they're updating these
files because they were told they were supposed to (mostly by me). But if
projects.a.o isn't using them anymore, I'd like to understand if they feel
there's any other value to them.

I'll reach out to these projects next week, and if they tell me that
there's any value to the files beyond the projects site, then we can figure
out how to proceed at that point, and centralizing them definitely seems
like the right approach in that case.

Reply via email to