community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <ja...@carmanconsulting.com>
Subject Re: the doap processing is busted for people.a.o
Date Mon, 27 Apr 2015 22:48:30 GMT
A perfect opportunity for Apache Camel
On Mon, Apr 27, 2015 at 7:53 AM Shane Curcuru <asf@shanecurcuru.org> wrote:

> Just a quick note: I'm pretty confident the medium term plan is to
> replace the entire projects.a.o build system (rather complicated,
> involving multiple steps in Perl and XSLT) with the software behind the
> projects-new.apache.org site.  Thus, I highly recommend looking at the
> below work instead of doing anything with the old Perl!
>
> Discussion on making changes to the code:
>
> https://mail-archives.apache.org/mod_mbox/community-dev/201503.mbox/%3C1935041.Ku0l4cXdRX%40herve-desktop%3E
>
> Vote thread to start the process:
>
> https://mail-archives.apache.org/mod_mbox/community-dev/201503.mbox/%3C54F9DB53.1030005%40redhat.com%3E
>
> Sources and docs for projects-new:
> https://projects-new.apache.org/about.html
>
> - Shane
>
> On 4/27/15 4:51 AM, Sergio Fernández wrote:
> > Hi David,
> >
> > I could help on the doap part, but I see that part of the site is built
> > using Perl, so I have an issue with that: on the one hand it's language I
> > never felt comfortable with, on the other the RDF support is very
> limited.
> >
> > Therefore, before jumping to the see, I'd like to ask you guys a couple
> of
> > details: how much that part of the site is build on doap? and how
> actively
> > maintained is it? Before I could commit some time to branch it and
> refactor
> > it to Python for instance, where I'm more skilled and I can warranty
> better
> > RDF pipeline.
> >
> > So comments from you are welcomed.
> >
> > Cheers,
> >
> >
> >
> >
> >
> > On Sat, Apr 25, 2015 at 3:20 AM, David Crossley <crossley@apache.org>
> wrote:
> >
> >> The 3-hourly processing of the list of DOAP files for people.apache.org
> >> site
> >> has been spewing errors for many days.
> >>
> >> I do not know enough about how the site build works
> >> (see
> >>
> https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects)
> >> and i do not have it installed locally.
> >>
> >> I have done some investigation.
> >> This error message on 2015-04-17 at 15:30 was the first:
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/www-site-dev/201504.mbox/%3c20150417153422.0B7C817BF9@minotaur.apache.org%3e
> >>
> >> These are the only likely changes that i can find
> >> leading up to the error:
> >>
> >> Author: hboutemy
> >> Date: Tue Apr 14 00:31:26 2015
> >> URL: http://svn.apache.org/r1673325
> >> Log: s/asfext:PMC/asfext:pmc/ to match the extension
> >>
> >> Author: gmcdonald
> >> Date: Tue Apr 14 10:28:09 2015
> >> URL: http://svn.apache.org/r1673402
> >> Log: remove zookeeper entry for now
> >> Modified: infrastructure/site-tools/trunk/projects/pmc_list.xml
> >> (Note that there is still a zookeeper entry in
> >> site-tools/trunk/projects/files.xml if that matters.
> >> The commit comment is not useful.)
> >>
> >> However those were a few days before this error started, so they
> >> do not seem likely.
> >>
> >> Perhaps it is coming from a remote project DOAP file,
> >> but the build system does not report which file it is having
> >> trouble with.
> >>
> >> These files also are utilised for people-new.apache.org with a manual
> >> import at present.
> >>
> >> That is all that i have time to do, so hopefully this helps
> >> someone else to go further.
> >>
> >> -David
> >>
> >
> >
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message